Ledgers

The money-truth shelf, and the heart of this blog. Why balances drift, how double-entry makes loss impossible to hide, what idempotency protects, and reconciliation as a daily discipline rather than a monthly ritual.

Read in this order and it builds: Why Your Ledger Drifts for the diagnosis, Double-Entry for Engineers for the intuition, Ledger Design for the schema, Idempotency Done Right for the write path, Reconciliation at Scale for the net beneath all of it.

Five articles, one khata philosophy: hisaab barabar, by construction rather than by discipline. The fintech practice is where this gets built for money.

The shortest version of the whole shelf: a balance is not a fact about an account, it is a summary of facts about movements — and everything else follows from taking that literally.

Double-Entry for Engineers Double-entry explained as an invariant system rather than accounting jargon: a five-hundred-year-old consistency protocol that assumes humans make mistakes. Ledger Design Why double-entry wins for any product that moves money, and what goes wrong the moment you try to store balances instead of deriving them from the entries. Reconciliation at Scale Matching millions of transactions nightly without a queue of unresolved breaks: how to rank exceptions by value and resolve them from a guided audit workflow. Why Your Ledger Drifts Ledger drift is never random. Where the difference actually comes from, how to prove it with a reconciliation query, and what to change so it cannot recur. The T+1 Problem Settlement time and business reality rarely agree. How to model T+1 properly so your customer balance, your bank statement and your ledger tell one story.