Why the ledger matters
A ledger is the canonical record. Every dollar movement, fee, accrual, and reversal lands on a ledger entry, and the balance of every account is derived from those entries, not stored separately. Double-entry bookkeeping enforces correctness by construction: every transaction has equal debits and credits, and the entire system always balances to zero.
If you cannot answer "what's my customer's balance?" from your ledger history alone, you do not have a ledger; you have a database with balance fields.
When ledger design matters
- At founding — choose a real ledger architecture before you have customers. Retrofitting is brutal.
- At reconciliation — your ledger must tie to the sponsor bank's core ledger and to the network/rail clearing files.
- At audit — auditors will trace transactions through the ledger; a sloppy ledger is an audit failure waiting to happen.
Common pitfalls
- Mutable balance fields. Storing a balance that can be edited is a recipe for drift. Derive from entries.
- Single-sided entries. Any "transaction" that isn't double-entry is a bug.
- Conflating sub-ledger with general ledger. The sub-ledger tracks one product or pool; the general ledger reconciles everything.
A clean ledger is the most underrated piece of fintech infrastructure. Get it right and everything else gets easier.