What reconciliation means in finance
In finance, to reconcile means to show that two independent records of the same money agree, or to explain exactly why they do not. Financial reconciliation is the name for that work across the finance function: treasury reconciles cash, payments teams reconcile processor settlements, and accounting reconciles ledger balances before the close. The general concept, independent of the finance setting, is covered under reconciliation in accounting.
The word has other meanings outside finance. In everyday language, reconciliation is restoring a relationship after a conflict; in US politics, budget reconciliation is a procedure Congress uses to pass certain tax and spending bills. Neither is related to the financial control described here. In personal finance, reconciling usually means checking a bank or card statement against one’s own records, a small version of the same control.
Why financial reconciliation matters
A reconciliation does more than look for equal totals. It asks whether each source covers the same period, entity, account, currency and transaction population. Differences can be timing items, missing records, duplicate postings, classification errors or legitimate scope differences.
Financial reconciliation is an umbrella term. Account reconciliation may substantiate an ending balance, bank reconciliation compares book cash with a bank statement, payment reconciliation compares transaction and settlement data (see this guide to modern payments reconciliation), and general-ledger reconciliation checks detail against the ledger. Their evidence and correction paths differ.
Financial reconciliation process, step by step
- Set the scope and sources. Define the account or activity, reporting period, entity, currency and comparison point. Gather the general ledger, subledger, statement, settlement file or other source that should explain the balance.
- Compare and identify differences. Compare totals and, where useful, individual records using keys such as date, reference, amount, account or counterparty. List unmatched, duplicate, missing or out-of-period items instead of hiding them in a net difference.
- Investigate and resolve. Classify each difference as a timing item, source error, missing entry, duplicate, scope issue or accounting judgment. Obtain support, request a correcting entry or document why the item remains open under the applicable process.
- Document and review. Record the adjusted balance, reconciling items, owner, explanation, action and review date. A reviewer checks the support and conclusion so the reconciliation can be used in close or financial reporting.
Financial reconciliation example: a card settlement that arrives short
The figures are illustrative. A retailer’s sales system records USD 48,500 in card sales for one day, and the company books a receivable from its card processor for that amount. Two days later, the processor’s settlement file and the bank statement both show a deposit of USD 46,960.
The gap is USD 48,500 – USD 46,960 = USD 1,540. Matching the settlement file line by line explains it: USD 1,240 in processing fees deducted from the payout, and a USD 300 refund the processor issued that the sales system never recorded. USD 1,240 + USD 300 = USD 1,540, so nothing is left unexplained. After the team validates both items against the processor’s statement, it records them and clears the receivable.
| Account | Debit | Credit |
|---|---|---|
| Cash | USD 46,960 | |
| Card processing fees expense | USD 1,240 | |
| Sales refunds | USD 300 | |
| Receivable from card processor | USD 48,500 | |
| Total | USD 48,500 | USD 48,500 |
Caught at the transaction level, the refund is a single identified item. Found weeks later as an unexplained gap in the receivable balance, it would have to be traced back through every payout behind that balance.
Types of financial reconciliation: transaction, account and entity level
Financial reconciliations are easiest to organize by the level at which the comparison happens. Each level uses different sources and catches different problems.
| Level | What is compared | Typical examples |
|---|---|---|
| Transaction level | Individual records between two systems or parties | Sales against processor settlements, payouts against bank credits, invoices against payments |
| Account level | A ledger balance against its supporting detail | Bank accounts, receivables and payables, subledgers against the general ledger, balance sheet accounts |
| Entity level | Balances between entities and up to the statements | Intercompany balances, consolidation inputs, financial statement reconciliation |
The transaction level is often called transaction reconciliation, and it feeds the account level, where general ledger reconciliation confirms each balance against its detail. At the entity level, intercompany reconciliation confirms that reciprocal balances agree. Financial statement reconciliation then checks that the statements tie to the reconciled balances and to each other, for example that cash on the balance sheet equals the reconciled bank accounts.
These activities can sit in the same close workflow, but they should retain their own source definitions, evidence and investigation steps. A bank timing item and a duplicated ledger entry require different actions even when they produce the same net difference.
What evidence a reconciliation should show
A useful record identifies the account or activity, source systems, period, balances before adjustment, reconciling items, supporting documents, responsible preparer, reviewer and conclusion. The format can vary, but the evidence should let another person understand how the adjusted balance was reached.
How to handle an open difference
An unmatched amount is not automatically an error. It may reflect a timing difference or a source that closes on a different schedule. The reconciler should state the reason, amount, age, owner and next action, then follow up until the item is corrected, supported or accepted under policy.
How Simetrik supports financial reconciliation
Simetrik, an AI-native financial control platform, focuses on the transaction level, where financial reconciliation starts. It brings together transaction and operational data from banks, processors, internal systems and other third parties, and its deterministic engine applies the matching rules and tolerances the team configures, the basis of automated reconciliation. The same inputs and rules give the same result, and records that do not match stay open as exceptions for review. That is the core of its financial reconciliation software.
The financial check goes beyond pairing records: Simetrik can compare fees, withholdings, refunds and settlements against configured rules, so a short payout like the one in the example surfaces as specific items. Those are its fee and settlement controls. Payment service providers apply the same checks to merchant payouts through PSP reconciliation. Detecting a one-sided refund, a fee deduction or a chargeback at the transaction level is faster and more traceable than correcting it later at the balance level. Simetrik can also organize recorded balances, supporting evidence, exceptions and review responsibilities by period, with a preparer and a certifier for each account. The accounting or finance team remains responsible for treatment and approval.