Practical insight

Why a Balanced Ledger Can Still Contain Incorrect Postings

Why balancing does not establish correct account attribution, dates, references or completeness—and what a bounded posting diagnostic should examine.

General diagnostic guidance. Examples and questions do not establish the treatment or readiness of a particular client landscape.

What balancing tells you

Equal debits and credits establish one arithmetic property of the entries being considered. They do not, on their own, establish that the right event was recorded in the right accounts, entity, period or currency.

Where errors can remain

A debit and credit can be posted twice. A complete pair can be omitted. A mapping can route the debit to an unintended account while the credit remains correct. A reference can be lost, leaving clearing and exception processes unable to match the entry. Each case requires a different evidence question.

Start with an agreed expectation

Define the business event and the applicable accounting requirement before comparing results. Identify the authorised rule, its effective period and the sources that show how the observed posting was produced. A difference is a finding to investigate; it should not automatically be called a defect or an intended design change.

Make the tested population explicit

Record the period, systems, event types, currencies and exceptions included. Completeness checks need a defined source population and appropriate control evidence. A single successful trace demonstrates that example; it does not establish coverage of every variant.

Use the finding to assign the next action

A useful diagnostic identifies the difference, its evidence, the unresolved explanation, the accountable reviewer and the decision it affects. The aim is an explanation that finance, technology and programme owners can inspect together.

Inspect the method

See a clearly labelled synthetic example of the corresponding finding and the next evidence it requires.

View the worked example