Banking Reconciliation

Part 4 of the Complete Guide to Reconciliation Systems in BFSI

At 5:45 p.m., a branch manager begins the day-close process. The teller system reports $184,500 of physical cash. The vault and teller counts total $184,400. An automated teller machine (ATM) beside the branch reports $52,000 remaining in its cassettes, while the cash-loading record implies $52,100. The customer-account system shows all deposits and withdrawals processed, but one late cash deposit has not yet reached the general ledger.

The branch is not facing one difference. It is facing several control questions about one business day:

• Does physical cash agree with the branch’s operational records?
• Do ATM transactions and cassette balances explain the machine’s cash?
• Do customer-account movements support the branch totals?
• Has the general ledger received the expected accounting entries?
• Are late entries still within an approved processing window?

The manager should not combine the differences into one net number. A $100 teller shortage and a $100 delayed ledger credit might cancel arithmetically while representing unrelated risks. Each must be traced through the systems and lifecycle stage that created it.

This branch-day-close story reveals the central idea of banking reconciliation: a bank must connect physical value, customer obligations, internal books, external accounts, and accounting records without assuming that all of them update at the same time or level of detail.

What Banking Reconciliation Establishes

#

A bank records both its own assets and liabilities and activity performed for customers. Cash in a vault is an asset of the bank. A positive customer deposit balance is generally an amount the bank owes the customer, subject to the account’s terms. A transfer may move value between customer accounts, between branches, between banks, or between currencies. Each event can produce operational records, cash movements, settlement instructions, and ledger postings.

Banking reconciliation tests whether those representations form a coherent account of the underlying activity. The source systems vary by institution, but the universal architecture from Part 2 remains:

1. Collect the required records and prove that the population is complete.
2. Validate dates, counts, totals, account scope, and data quality.
3. Normalize identifiers, currencies, signs, and date meanings.
4. Match related transactions or balances.
5. Compare them under approved business rules.
6. Classify breaks, investigate exceptions, and preserve evidence.

The important phrase is under approved business rules. A cash count should ordinarily agree at a point in time. A transfer initiated near a cutoff may legitimately appear externally on a later date. The control must know which relationship it is testing.

Balances and Transactions Answer Different Questions

#

A transaction reconciliation compares individual movements or related groups of movements. It can reveal a missing deposit, duplicate withdrawal, incorrect fee, or payment posted to the wrong account.

A balance reconciliation compares positions at a defined point in time. It asks whether an ending balance is supported by an opening balance and the movements in between:

opening balance + inflows - outflows ± adjustments = closing balance

Suppose the branch began with $200,000, received $35,000, and paid out $50,500. Its expected close is $184,500. A physical count of $184,400 produces a $100 balance break. Transaction records may then help locate the cause: perhaps one $100 withdrawal was paid but not entered, or a teller bundle was counted incorrectly.

The reverse problem is also possible. Opening and closing balances can agree even when two transaction errors offset each other. A missing $500 deposit and a missing $500 withdrawal leave the net balance unchanged. Transaction reconciliation detects the omissions; balance reconciliation alone may not.

Observation: Agreement of balances does not prove that every transaction is correct, and agreement of transactions does not prove that the opening balance was valid.

Concept: Banks use transaction and balance controls together because they test different risks.

Cash and Teller Reconciliation

#

Cash reconciliation connects physical notes and coins to controlled records. At a branch, relevant sources may include teller journals, vault records, cash transfer logs, customer transactions, denomination counts, and the general ledger.

Each teller commonly begins with an assigned amount, processes receipts and payments, transfers cash to or from the vault, and ends with a physical count. A teaching equation is:

opening teller cash + customer receipts + vault receipts - customer payments - vault returns = expected teller cash

The expected amount is compared with the count by denomination. A difference may result from a data-entry error, an incorrect denomination, a transaction processed twice, cash handed over without a completed record, counterfeit-note treatment, or a counting mistake. The institution’s procedures determine recounts, approvals, limits, and escalation.

Cash in transit needs separate attention. If one branch dispatches cash to another, the sender may record an outflow before the receiver confirms arrival. That difference can be expected while the shipment is within its controlled delivery window. It becomes a genuine break when required evidence is absent, the amount differs, or the confirmation is overdue.

Netting teller differences is unsafe. A $200 overage at one counter and a $200 shortage at another may suggest a transfer posted to the wrong teller, but the hypothesis requires evidence. Closing both merely because the branch total is zero would conceal the individual accountability trail.

Observation: Physical cash has no automatic system status; control depends on counts, custody records, and transaction evidence.

Concept: Cash reconciliation links physical possession to recorded responsibility at each handoff.

ATM Reconciliation

#

An automated teller machine dispenses or accepts cash while producing several representations. Its electronic journal records events. A switch routes transaction messages. The core banking system updates customer accounts. Cash-loading teams record cassette amounts. Physical or device-reported cassette counts represent remaining inventory. Network and settlement records may represent transactions involving other banks’ customers.

Consider an ATM loaded with $100,000. It reports successful withdrawals of $47,900, no deposits, and $52,000 remaining. The arithmetic leaves $100 unexplained:

$100,000 - $47,900 = $52,100 expected

The $52,000 device balance is not automatically the wrong side. Investigation may identify a partial dispense, a note retained or rejected by the machine, a reversal sent to the customer system, a cash-loading error, or an incomplete journal. If a customer was debited but received no cash, transaction and customer-impact controls matter in addition to cassette balancing.

ATM reconciliation may therefore include:

• Cash loaded versus cash acknowledged by the machine
• Successful dispenses versus customer-account debits
• Failed or partial dispenses versus reversals
• Other-bank transactions versus network settlement
• Electronic journal totals versus switch records
• Expected cassette balance versus physical count
• Fees and adjustments versus ledger postings

A transaction marked successful by the switch may still have a later reversal. A machine may go offline and upload its journal after connectivity returns. These are timing and status questions, not permission to leave items unexplained indefinitely.

Observation: One ATM withdrawal can affect physical cash, a customer balance, network settlement, and accounting at different times.

Concept: ATM reconciliation follows both the cash inventory and the transaction lifecycle; neither view is sufficient alone.

Branch and Customer-Account Reconciliation

#

Branch reconciliation aggregates activity while retaining the ability to trace it to source transactions. Deposits, withdrawals, transfers, checks, fees, interest, cash shipments, and internal adjustments may all contribute to the branch result.

The branch operating system may summarize activity by product or teller. The core banking system maintains customer accounts. A general ledger interface converts operational events into accounting entries. The totals should relate, but the records need not be identical. One customer transfer can create a debit and credit in the core system while producing summarized ledger postings.

Return to the late $100 deposit in the opening story. The customer-account system shows the credit, and the teller’s cash includes the receipt. The general ledger interface runs after the branch cutoff, so the accounting entry is scheduled for the next batch. If policy explicitly permits that sequence and the item appears in a controlled pending population, it is an expected timing difference.

If the interface batch completed and omitted the transaction, the same $100 is a genuine break. The amount did not change; the evidence and timing context did.

Branch controls should avoid declaring completion when a required source failed. If a customer-account extract is partial, matching the available records against the ledger produces false confidence. File counts, control totals, cutoff, and extraction status are prerequisites to comparison.

General Ledger Reconciliation

#

The general ledger (GL) is the accounting record that organizes the institution’s financial effects by account and reporting period. Operational systems often maintain more detailed subledgers for customer deposits, loans, cards, fixed assets, or other products.

GL reconciliation asks whether subledger activity and balances support the summarized accounting entries. A typical relationship is:

subledger opening balance + controlled movements = subledger closing balance

and

subledger closing balance = corresponding GL control-account balance

Sign conventions require care. A customer deposit can appear as a positive amount in a customer interface but as a credit liability balance in accounting. Normalization must preserve economic meaning rather than simply forcing signs to look alike.

Common GL breaks include missing interface batches, duplicate postings, wrong account mapping, incorrect currency conversion, manual journals not reflected in the subledger, or entries posted to different periods. A manual journal may be valid, but it needs authority, purpose, and supporting evidence.

Ledger reconciliation is not only a month-end exercise. Frequency should follow risk and data availability. High-volume or high-risk interfaces may be controlled daily or intraday, while formal financial-close controls add review and certification.

Observation: A ledger can balance mathematically while an amount sits in the wrong account or period.

Concept: GL reconciliation tests completeness, classification, valuation, and timing—not merely equal totals.

Treasury and Liquidity Reconciliation

#

Treasury manages the bank’s funding, liquidity, market transactions, and financial resources. Treasury reconciliation can connect deal-capture systems, confirmations, settlement instructions, cash forecasts, bank accounts, market data, and the GL.

Suppose treasury expects a $5 million deposit to mature today. The deal system shows principal and interest due. The cash forecast includes the receipt. The external bank account has not yet been credited. Before calling it missing, operations must establish the value date, currency, settlement route, local cutoff, and counterparty confirmation.

Controls may compare:

• Approved deals with confirmations
• Maturing obligations with settlement instructions
• Forecast cash with actual cash
• Treasury positions with accounting balances
• Interest calculations with contract terms
• Foreign-exchange settlements with currency accounts

A forecast difference is not identical to an accounting break. Forecasts contain expected future flows and may change legitimately. Actual settlement and ledger records represent realized stages. The reconciliation design should label each stage rather than compare all treasury numbers as though they were the same balance.

Nostro and Vostro Accounts

#

Correspondent banking allows one bank to hold an account with another bank so it can make and receive payments in places or currencies where it needs access.

From Bank A’s perspective, Nostro means “our account with you”: Bank A’s account held on Bank B’s books. Bank A treats the Nostro balance as its asset and reconciles its internal record against statements supplied by Bank B.

From Bank B’s perspective, the same relationship is Vostro, meaning “your account with us”: Bank B holds an account for Bank A and records the amount it owes Bank A as a liability.

The words describe perspective, not two separate pools of money. Teams should define whose viewpoint a report uses before interpreting a debit, credit, or balance.

Nostro reconciliation commonly compares the bank’s internal cash ledger and payment records with the correspondent statement. Items may include outgoing and incoming payments, fees, interest, foreign-exchange settlements, reversals, and value-date adjustments.

For example, Bank A instructs a $250,000 payment from its account at Bank B. Bank A records the expected reduction when it releases the instruction. Bank B posts it after validation and processing. During the interval, the internal and external balances differ for an expected reason. The item should remain visible with an expected settlement date. If Bank B rejects the instruction, applies an unexplained fee, or fails to post it within the agreed window, investigation is required.

Vostro reconciliation is performed from the account-holding bank’s perspective. It confirms that customer-bank instructions, account entries, statements, fees, and GL liability balances agree. Sanctions screening, payment repair, and other controls may affect processing, but reconciliation should report status accurately rather than assume every delayed item is erroneous or acceptable.

Observation: A correspondent-account difference often reflects two institutions recording different lifecycle moments.

Concept: Nostro and Vostro reconciliation aligns internal books with the account servicer’s evidence while preserving perspective, value date, and settlement status.

Expected Timing Differences Versus Genuine Breaks

#

A timing difference is expected only when a defined rule supports it. “The systems update at different times” is an explanation to test, not a permanent closure reason.

An expected timing rule should identify:

• The event or status that starts the clock
• Relevant business calendars, time zones, and cutoffs
• The source expected to update later
• The normal and maximum window
• Evidence that the item is progressing
• What happens when the window expires

Examples include a late branch batch scheduled for the next run, an ATM journal delayed by a known outage, cash in transit before confirmed delivery, or a correspondent payment awaiting the stated value date.

A genuine break exists when a defined relationship fails: cash is short, a transaction is missing after its window, amounts or currencies differ, a posting is duplicated, an account mapping is wrong, or evidence cannot support the expected explanation.

Aging changes classification. An unmatched Nostro item may be an expected timing item on day one and an overdue exception on day two under the institution’s rule. Systems should preserve its original detection date rather than recreate it as new each day.

Escalation and Resolution

#

Escalation directs an unresolved or material exception to the right level of ownership. It should depend on more than amount. Customer impact, liquidity effect, age, recurrence, account sensitivity, and reporting deadlines can all matter.

A practical workflow records:

1. The failed control, source records, and business date
2. The expected relationship and actual difference
3. Initial classification, value, age, and owner
4. Investigation evidence and communications
5. Correction, natural clearing, approved explanation, or other disposition
6. Rerun result and required approval

Some items need immediate action, such as unexplained physical cash shortages or high-value settlement failures. Others can be monitored within an approved timing window. The policy, not analyst intuition alone, should determine the response.

Resolution should address the source of the break. If an interface omitted a ledger posting, changing the reconciliation result manually does not repair the ledger. The source or controlled accounting process should correct the entry, after which the reconciliation should demonstrate agreement. Repeated exceptions should feed root-cause analysis: a recurring late branch file, ATM reversal defect, or correspondent fee difference may require a process or system change.

Designing a Banking Control

#

For each reconciliation, state the control question narrowly. “Reconcile the branch” is too broad. Better questions include:

• Does physical teller and vault cash agree with recorded custody at close?
• Did every successful ATM dispense produce the correct customer debit and cash movement?
• Do customer subledger balances support the related GL control accounts?
• Do internally recorded correspondent-account movements agree with the external statement after approved timing?

Then define sources, populations, point-in-time or transaction basis, keys, comparison rules, timing windows, owners, and evidence. Separate controls may be necessary because a single green total cannot prove cash, customer accounts, external settlement, and accounting are all correct.

Chapter Summary

#

Banking reconciliation connects physical cash, channel activity, customer records, subledgers, the general ledger, treasury systems, and external correspondent accounts. Cash, ATM, branch, GL, treasury, Nostro, and Vostro controls apply the same universal architecture, but each tests a distinct business relationship.

Balances show a position at a point in time; transactions explain movements and can expose offsetting errors. Timing differences are acceptable only under explicit windows and evidence. When a relationship fails or a window expires, the item becomes a genuine break requiring owned investigation, escalation, resolution, and an audit trail.

Key Takeaways

#

• Banking reconciliation links physical value, operational records, external evidence, and accounting.
• Balance and transaction reconciliations test different risks and should complement each other.
• Cash and ATM controls must follow custody as well as electronic transaction status.
• General-ledger agreement requires correct classification, period, currency, and sign—not just equal totals.
• Treasury forecasts, actual cash, deal records, and accounting represent different lifecycle stages.
• Nostro is “our account with you”; Vostro is “your account with us,” viewed by the account-holding bank.
• Expected timing differences need defined cutoffs, windows, evidence, and expiry.
• A difference becomes a genuine break when the approved relationship or timing condition fails.
• Escalation should consider age, value, customer impact, liquidity, recurrence, and deadlines.
• Resolution corrects or explains the underlying difference and preserves reconstructable evidence.

Previous: Part 3 — The Language of Reconciliation · Series landing page · Next: Part 5 — Payment Reconciliation