02 / General ledger reconciliationThe operational system and the ledger disagree.
Activity recorded in an operational system, such as billing, a trading platform or a point of sale, does not agree with the general ledger. Comparing headline totals leaves a difference to explain every month.
Common causes
- Failed or partial imports from the operational system.
- Corrections made in one system but not the other.
- Inconsistent account, product or entity coding.
- Different cut-offs: the system’s day against the ledger’s period.
- Records that correctly sit outside the comparison but are not documented as such.
What to check first
- Reconcile at the level where both systems share a key, not at the total.
- List the record types that should not reach the ledger, and why.
- Check whether the difference is stable, growing or reversing month to month.
- Compare the import log with the number of records posted.
What I can deliver
An explanation of where operations and the ledger diverge, then a reconciliation that runs each period: data connections, comparison rules, an exception queue and checked corrections. It can start as a one-off investigation.
How it is solved
Establish a common basis for comparison.
Connect to both systems through supported APIs or repeatable file imports. Define how each activity type should reach the accounts, then align entity, period, currency and classification. Document which records fall outside the comparison and why.
Explain differences at the right level.
Run the comparison in code, at a level where meaningful groups and their detail stay visible. Show missing, unmapped and excluded records with reasons. Quantify corrections separately, so review covers both the financial effect and the cause.
Wider benefits
- Reporting confidence
The ledger ties back to the activity it represents.
- Earlier intervention
Mapping gaps and failed imports surface before the next close.
- Review and cover
A colleague can pick up an exception with its source detail, explanation and proposed correction.
Is this the problem in front of your team?
Describe how it shows up in your business. The next step is a focused investigation, a review of one workflow, or a wider finance systems assessment.