Reconciliation Process and Steps

The reconciliation process compares two records that should agree, explains any difference, and leaves an evidence trail for review. In finance operations, the records might be a bank statement and a cash ledger, an internal trade record and a custodian statement, or a sub-ledger and the general ledger. Reconciliation is not just finding a matching number. A sound process identifies the population, preserves the source records, investigates exceptions, records the reason, and escalates anything that cannot be resolved within the authorised procedure. The examples in this article are fictional and are designed for learning, not for changing a live ledger.

What reconciliation means in finance

A reconciliation asks whether two views of an activity are complete, accurate and aligned for a defined date or cycle. Matching can be one-to-one, one-to-many, or based on a controlled tolerance. The analyst should know what each source represents before comparing values. A bank statement may show cleared cash movements while an internal ledger may include pending entries. A trade record may contain economic terms while a settlement statement shows the movement that actually reached an account. Differences are therefore signals to investigate, not automatically errors.

Reconciliation process: six practical steps

1. Define the scope: source systems, account or portfolio, date, currency, population, owner and expected completion time.
2. Collect and protect the evidence: retain the source files, extraction time, version and any approved data-quality notes.
3. Standardise the fields used for matching, such as reference, value date, amount, currency, account and transaction type.
4. Match the population using the approved rules, then separate exact matches, probable matches, duplicates, missing records and breaks.
5. Investigate each break by tracing both sides to supporting evidence and recording a specific root cause rather than a vague comment.
6. Close, carry forward or escalate the exception according to policy, with reviewer sign-off, ageing and an owner for every unresolved item.

A fictional reconciliation example

Imagine a fictional operations team comparing a daily cash ledger with a bank statement. The ledger contains a debit of Rs 18,500 with reference CX104, while the statement contains the same reference for Rs 18,050. The correct response is not to edit the ledger until the totals match. The analyst records the 450 difference, checks the source instruction, verifies currency and value date, searches for a fee or partial posting, and asks the authorised owner for evidence. If the difference is a bank fee, it may need a separate approved accounting entry. If the source record is wrong, the correction and approval path should be recorded.

What a useful break note contains

• A unique reference and the amount, currency and relevant dates.
• The two source values and the calculated difference.
• The checks completed, evidence reviewed and likely root cause.
• The next action, owner, due date, ageing and escalation status.

Controls that make reconciliation reliable

Good controls separate preparation from review where the process requires it, restrict access to sensitive files, preserve an immutable source copy, and use a clear ageing report. A tolerance should be documented rather than silently built into a spreadsheet. Common weak practices include overwriting source data, deleting unmatched rows, using a plug entry without evidence, and carrying the same break forward without an owner. Equal totals are useful, but they are not proof that the population is complete or that every item is classified correctly.

Read the accounting basics resource for debit, credit and ledger context

Compare reconciliation types and examples in finance

Explore the Finance Operations training module

Practise reconciliation questions for finance interviews

Browse all finance career insights

Review the IFRS Accounting Standards Navigator

Reconciliation is valuable career preparation because it combines accounting logic, data handling, investigation and written communication. Learn the workflow with fictional records, then compare the exact procedures and approval limits used by the organisation. Centaur Careers publishes this article for education; it is not accounting, audit or legal advice, and it does not promise qualification or employment outcomes.