import * as core from './core/index.js'; import type { IJournalEntry, IJournalEntryLine, ITransactionData, ITransactionView, IReportParams, TSKRType } from './skr.types.js'; export declare function mapNumericPostingKey(postingKey?: number): core.TBuKey; /** * v1 postTransaction input -> two-line v2 draft. The amount is NOT split into * net/VAT (v1 semantics: vatAmount was informational) so ledger figures stay * identical across the migration. */ export declare function transactionDataToDraft(data: ITransactionData): core.IJournalDraft; /** * v1 postJournalEntry input -> v2 draft. Gegenkonto derivation: when one side * of the entry has exactly one line, it is the counter account for every line * of the other side (the dominant v1 usage); otherwise the first line of the * opposite side is used (documented heuristic — v1 stored no Gegenkonto). */ export declare function journalInputToDraft(entry: IJournalEntry): core.IJournalDraft; interface IEntryDocLike { id: string; journalNumber?: string; date: Date; description: string; reference?: string; skrType: TSKRType; status: string; period?: string; fiscalYear?: number; postedAt?: Date | null; reversalOf?: string; lines: IJournalEntryLine[]; } /** * Project a two-line v2 entry back into the classic transaction shape. * Returns null for entries with more than two lines (journal-only view). */ export declare function entryToTransactionView(entry: IEntryDocLike): ITransactionView | null; /** * Load v2 entries of a date range as core drafts (for DATEV export). */ export declare function loadDraftsForExport(skrType: TSKRType, dateFrom: Date, dateTo: Date): Promise; /** * Per-account activity as transaction-shaped line views from v2 entries — * the data source for reports (trial balance, general ledger, cash flow). * Each view carries the line's own side and its Gegenkonto. */ export declare function accountLineViews(accountNumber: string, skrType: TSKRType, params?: IReportParams): Promise; export {};