A synthetic operations demonstration built around one question: which receipts can be linked without guessing, and what still needs an owner decision?
The reproducible Python workflow validates 17 invoice records and 24 receipt records, holds all occurrences of duplicate invoice IDs or payment IDs, and matches only unique invoice references with exact customer IDs in USD. All amounts use integer cents. Partial payments accumulate against the referenced invoice; excess stays unapplied rather than spilling to another invoice.
The actual fixture produces 11 allocation records applying $4,615.74, with $405.00 unapplied and $600.01 remaining across four eligible invoices. Source-held amounts stay outside those totals. Both eligible-dollar equations balance to the cent, including a visible $0.01 invoice remainder.
The handoff includes source ledgers, an allocation ledger, a 20-row owner-review queue, remaining invoice balances and a three-page static report. All 37 regression and edge tests pass; repeated executions produce byte-identical data outputs.
All records are fictional. Applied means an allocation within this fixture, not money collected or a bank/accounting-system posting. Scope excludes FX, fees, refunds, aging and live platform integration.
0 likes · 1 view · Oct 26, 2026
Synthetic USD demo: 17 invoice rows and 24 receipts reconciled with exact-cent allocations, explicit exceptions and a traceable CSV handoff.
