A ledger reconciliation checklist for month-end
By Mrunal Walke2 min read
Use supporting records and an exception register to explain ledger differences instead of posting adjustments simply to make totals match.
On this page
Ledger reconciliation means explaining why an account balance agrees with its supporting records, or documenting the differences that remain. Matching two totals is a useful check, but it is not enough when both reports contain the same missing or duplicated transaction.
Define the account and period
Choose the ledger account, reporting date, currency and source of supporting evidence. For a clearing account, that evidence might be a payment-provider settlement report. For a control account, it may be the relevant subsidiary ledger. Record whether the reports use transaction, posting or settlement dates.
Save the report filters with the reconciliation. If two reviewers use different dates or include different entities, the same account can appear to have two valid balances. A repeatable extraction is the starting point for a repeatable close.
Build a difference register
| Difference | Evidence to inspect | Next action |
|---|---|---|
| Timing | Transaction and settlement dates | Confirm expected clearing date |
| Duplicate | Source reference and posting history | Review the duplicate posting |
| Missing item | Source record without ledger match | Investigate the failed handoff |
| Classification | Correct amount in wrong account | Obtain posting review |
Give every unresolved item an owner and a reason. Do not hide unexplained amounts in a generic adjustment line just to produce a zero difference.
Work through a small example
Suppose a hypothetical clearing balance is 10,500 currency units and the settlement report explains 10,000. Inspection finds a 500 transaction recorded on the last day of the month but due to settle in the next period. The explanation is supported by the transaction and settlement references, not by assuming that every 500 difference is timing.
If the expected settlement never appears, reopen the item. Ageing an unresolved difference is useful because a once-plausible explanation can stop being plausible as time passes.
Review changes after the first pass
Late postings can invalidate an earlier reconciliation. Record when the source reports were generated and rerun the affected checks after authorised changes. Retain the original report and the revised result so the reviewer can understand what moved.
Zoho Books provides a chart of accounts and manual-journal functions. Having a journal entry feature is not a reason to use it as an automatic balancing tool. The responsible finance reviewer should decide whether an adjustment is appropriate and retain its supporting evidence.
A practical close pack contains the source reports, matching logic, exception register and review sign-off. It should allow another authorised person to reproduce the conclusion without relying on the preparer's memory.
Further reading
Primary reference. The workflow examples above are illustrative implementation guidance, not customer results.
Explore the related Dood resource. To discuss your workflow, contact Dood System.
