Exact amount matching is a useful starting point for transaction reconciliation. But it makes an...
Exact amount matching is a useful starting point for transaction reconciliation.
But it makes an important assumption:
One transaction on one side corresponds to one transaction on the other.
That assumption breaks quickly in real-world reconciliation.
Consider:
Both tables had 16 rows and differed by 400. The full outer join that finds what is on each side only, the value comparison for…
A payment can be booked internally, settled by a processor and absent from the bank. Use three invariants to locate the broken…
A local-first matching engine for bank vs books and invoices vs payments — built for accountants who cannot put client ledgers in…
A test proves your code does what you meant. It cannot prove that what you meant was correct. I...
Expense tracking usually fails not because of the interface, but because of the hidden friction in reconciliation and audit…
Order matching has dropped in Shitcoin Swap in ~100 lines of Ruby. Most crypto exchanges reach for...
