The Record MustBalance AfterThe Systems Disagree.
Reconciliation is not two exports compared at month end, and a ledger is not a log of what the operational systems already did. Financial facts are appended as entries, balances are derived rather than stored, and a difference between two records is raised as a break somebody owns.
Next Step / Technical Discovery
- Financial facts are appended
- An invariant, not a report
- Named, aged and owned
- Reconstructable afterwards
Where this system fits
The financial ledger sits beneath every system that moves value and above every account somebody has to defend: it decides what each event did to the books, and whether that answer survives being questioned.
- Late arrival, replay and restatement, without discarding the answer already given.
- The contracts financial events arrive on, and what a second delivery must not do.
- Roles, approval thresholds, and who may post an adjustment at all.
- Every entry has a counter-entry. An unbalanced write is refused.
- A balance resolves to the entries and events beneath it.
- A closed period is fixed. Later facts land in the open one.
- Nothing is edited. A wrong entry is answered by another entry.
- The evidence for a resolution outlives the person who resolved it.
- Proposing an adjustment and approving one are different permissions.
Why the books stop agreeing
- 01
The ledger is a table somebody updates
A row is corrected in place and the value it held is gone. The balance looks right this morning and cannot be explained next quarter.
- 02
Balance is something a job checks at night
Nothing stops an entry that does not balance being written. A report finds it hours later, with thousands more written on top of it.
- 03
The difference belongs to nobody
A mismatch appears in a spreadsheet with no assignee and no age. It survives close after close until it is large enough to escalate.
- 04
The adjustment that made it go away
A break was cleared with a manual entry and a one-line note. The entry is still there a year later; the reason it was right is not.
Actors and boundaries
Transaction source
Emits the events that carry financial meaning.
The source owns what happened, under whatever name it uses. This system owns which obligation moved, and between which accounts.
Payment or banking provider
Produces statements and settlement records on its own schedule.
Nothing inward. Their file is evidence to match against, never the balance itself.
Ledger
Turns each financial event into balanced entries against mapped accounts.
All of it: event identity, denomination, entry creation, account mapping, and the refusal to write what does not balance.
Reconciliation engine
Matches internal entries to external records and raises what will not match.
Matching rules, break creation and ageing, the policy an adjustment must satisfy, and the history kept behind each resolution.
Finance operations
Decides materiality, approves adjustments, signs a period off.
Outward. The system presents a break and its evidence. The decision is theirs.
ERP or general ledger
Holds the chart of accounts and the books the business reports on.
It owns accounting policy. This system produces postings that fit it, and never posts around it.
Where the financial record should live
Three places it can sit. Each is right under conditions the other two are not.
- In the application that wrote the record, if anywhere.
- In the accounting system, on the postings it receives.
- At the write. An entry that does not balance is refused.
- Whatever the operational model happens to hold.
- Summarised. Detail stays in the systems that fed it.
- Per event, with a summarised posting for the statutory books.
- Manual, and it grows with every source added.
- An import routine per source, maintained by finance.
- A designed rule, whose output is a classified break.
- Application code, deployed by engineers.
- Configuration owned by finance — often the whole reason to choose it.
- Mapping configuration; the policy behind it stays with finance.
- One source, low volume, a close that fits in a morning.
- The statutory books are the only ledger anybody queries.
- Several sources disagree, and each answer must be defensible alone.
When it fails
Five ordinary conditions. None of them is an incident, and each has a defined destination.
- A financial event never reached the ledger
The external record carries a movement with no entry standing behind it.
A break opens against the source, not the statement, and the close cannot complete while it is open.
- The same financial event arrives twice
The second copy carries an identity the ledger has already posted against.
It is recorded as seen and not posted again. Both arrivals stay in the history.
- The two records agree on everything but the money
A match is found on identity and then rejected on value or currency.
A break carrying both figures, classified by size and by whether a conversion sits between them.
- A settlement record arrives late, or arrives changed
A record already matched returns with a different amount or a different date.
The earlier match is superseded, never rewritten. If the period closed, the correction lands in the current one.
- A break is cleared by an adjustment nobody can evidence
The adjustment references none of the records that would justify it.
It cannot be posted. An adjustment is an entry with an author, an approver and its evidence.
What you own afterwards
- An entry that does not balance is refused where it is written, so the books are never briefly wrong and quietly repaired.
- Differences are raised with a classification, an assignee and a clock, so a close is a list that shortens rather than an investigation that starts.
- Entries, the events behind them and the evidence for each adjustment survive the close, so a question asked a year later is answered from the record, not from memory.
- Sources, providers and the accounting package itself can be replaced without restating what an entry means, because the mapping from event to account is configuration rather than code.
Related pages
Payment Platforms
The system that owns a payment's state from initiation to settlement, routes across providers, and produces a ledger that reconciles.
Data Engineering
The layer between operational records and everyone who depends on them — definitions with owners, lineage that reconstructs, and corrections that stay explainable.
Bring a month end that runs on exported spreadsheets, a balance three systems answer differently, or an adjustment nobody can explain a year after it was posted.