What is payment reconciliation?
Making your books and the bank agree — and why the best reconciliation is the kind you never run.
Reconciliation is the process of confirming that what your records say happened matches what actually happened at the bank — that every payout, return and fee is accounted for, to the cent.
Why it's hard
Money moves asynchronously. A payment is created, held, submitted, and settles or returns days later. Fees appear. Timing differs between your system and the bank's. Reconciliation is the ongoing work of keeping those two views in agreement.
Reconciliation as an invariant
The best reconciliation is the kind you rarely have to run, because the ledger is designed so the numbers can't drift: a hold posts at creation, settlement posts at completion, and a return reverses the hold. Pending, posted and available always tie out.
On DigitalTreasury
Because every rail posts to one double-entry ledger with holds and settlements modeled explicitly, reconciliation is an invariant the platform maintains — not a nightly batch job that might disagree.
Double-entry accounting for software platforms
Why the 500-year-old accounting model is exactly right for a modern payments ledger.
What is an FBO account?
One bank account, many customers' money — held for their benefit and reconciled to the penny.
ACH return codes explained (R01, R02, R03…)
Why a payment came back — and why 'insufficient funds' and 'account closed' should be different branches in your code.