lars/finance-duck
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Distinguish debit and credit postings sharing an upstream reference

Browse Source
This commit is contained in:
Lars Nolden
2026-09-10 15:48:42 +02:00
parent 964b9dfc15
commit bec6d0b444
3 changed files with 119 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
OPERATIONS.txt
+8 -4
View File
@@ -227,10 +227,14 @@ Use the original export, not spreadsheet-reformatted dates/numbers. Foreign
original amounts/exchange-rate columns are not mistaken for account amounts.
The initial application preserves currency but never converts or sums currencies.
Stable provider entry references are preferred. Enable Banking transaction_id
is NOT guaranteed stable and is not used as the primary identity. Fallback
fingerprints retain identical-record occurrence counts: two identical rows
remain two transactions, and repeat imports do not add two more. Without stable
Stable provider entry references are scoped by account, source and debit/credit
direction: a debit and credit can share a reference without being collapsed.
Conflicting booking dates, amounts or currencies within one direction still
fail closed. Existing journal IDs and raw references are retained.
Enable Banking transaction_id is NOT guaranteed stable and is not used as the
primary identity. Fallback fingerprints retain identical-record occurrence
counts: two identical rows remain two transactions, and repeat imports do not
add two more. Without stable
IDs, identical records from separately truncated exports are intrinsically
ambiguous. Import consistent overlapping/full exports. Uncertain cross-source
collisions are rejected rather than silently double counted; retain the error