Skip to content

Payments · 5 of 6

Step 1 · The pattern

Two records of the same money

Each £5 payment lands in the settlement account at the bank, and our service writes a ledger entry for it. The bank's total and our ledger's total should always match.

  • payment
  • ledger entry
  • done

In short

Reconciliation: how it works and how it breaks

Tests, code review and alerts catch bugs that fail loudly. The dangerous ones in payments fail quietly: a step is skipped for a small share of payments, no exception is thrown and every dashboard stays green. Detective controls look at outcomes instead of errors. A coherence check is a rule about one system's own data, for example that a payment which was not returned must have a payout scheduled. Reconciliation compares two independent records of the same money, such as your ledger and the statement of the settlement account at the bank. Their totals must agree. Any difference is a break: an engineer is alerted, finds the cause, repairs it and records the evidence. Reconciliation catches almost anything, including bugs nobody imagined, but only as often as it runs. Coherence checks are narrower and faster. Teams that move money run both.

How this comes up in interviews

"Every dashboard is green, yet the bank says it holds more money than your ledger does. How could that happen, and how would you catch it?"

Then they ask

  1. What is the difference between a coherence check and a reconciliation, and when do you use each?
  2. A break appears. Walk me through what happens next, from alert to closure.
  3. Reconciliation runs once a day. How do you shorten the time a quiet bug goes unnoticed?

A strong answer covers

  • The dangerous payment bugs fail quietly: a step is skipped, no exception is thrown and no alert fires.
  • Reconciliation compares two independent records of the same money, such as the ledger and the bank statement.
  • Any difference is a break: someone is alerted, finds the cause, repairs the record and keeps the evidence.
  • Coherence checks are rules about one system's own data. They are narrower and faster.
  • Reconciliation catches almost anything, but only as often as it runs, so teams run both.

Points to cover, not a script. Say them in your own words and tie them to a system you have worked on.

On one page: the track cheat sheet.

Last updated: Engineering write-up

Diagrams are our own simulations: the timings, rates and counts in them are illustrative, not measurements. Captions are original wording.