Balance Sheet Reconciliations in Practice

2026-10-05

Every reconciliation, whatever the account, follows the same five steps. The handbook pairs each step with the evidence an auditor expects to see.

How the steps depend on one another

Explain must come before Age. A total difference of ₹20,000 has no date of its own; only individual items do. An outstanding cheque of ₹15,000 may be three days old while a bank charge of ₹5,000 arose on another date, and the two cannot be averaged into a meaningful age. Age cannot be calculated until the difference has been broken into named items.

Agree is not a prerequisite for Explain, but it controls completeness. An analyst may already know from the cheque register that ₹15,000 of cheques are outstanding before any balances are compared. When the comparison then shows a ₹20,000 difference, the ₹5,000 residual shows that at least one item is still unidentified and prompts the search for it. Agree therefore confirms when Explain is finished.

Which accounts to reconcile, and how often

Not every GL account needs a monthly reconciliation. Companies scope by risk.

Materiality threshold

Not every difference is investigated individually. The company sets a threshold, either a fixed amount (for example ₹10,000) or a percentage of the account balance (for example 0.5%), below which items may be cleared in aggregate as immaterial. Without a threshold, analysts spend their time chasing differences of a few rupees.

The standard template

Whether kept in Excel (smaller companies) or in dedicated reconciliation software (larger ones), the layout is largely fixed: GL balance, supporting-schedule balance (subledger, bank statement, register or count), variance, a list of reconciling items each with amount, age, owner and target date, preparer signature and date, and independent reviewer signature and date.

When the review fails

If the reviewer finds an unexplained item or missing evidence, the reconciliation returns to the preparer and is not signed off until the point is resolved. Because this loop can delay the close, mature teams start reconciliations early in the close calendar rather than on the final day.

Common mistakes auditors look for

1. Plugging. Adding a reconciling item such as "miscellaneous adjustment ₹3,200" with no identified cause, purely to make the figures agree. This hides the underlying error and is a major audit red flag.
2. Self-certification. The preparer signs as reviewer, or the reviewer sits in the same team and is not independent.
3. Stale reconciliations. The reconciliation exists, but sign-off has been pending for months, so no review has actually taken place.

The bank statement is an external, independently produced record. In a bank reconciliation the books are adjusted to the bank, with one exception: where the bank itself has made an error, the company raises a dispute and the bank corrects it.

Typical reconciling items

Worked example: bank balance to cash book balance

At 31 March the bank statement shows ₹12,68,000 and the cash book shows ₹12,45,000.

The same items, worked in the opposite direction, run from the cash book balance of ₹12,45,000 back up to the bank statement balance of ₹12,68,000, with every add and deduct reversed.

Rule for the signs. Starting from the bank balance, apply the effect of items the books have recorded and the bank has not (outstanding cheques are deducted; deposits in transit are added), and reverse the effect of items the bank has recorded and the books have not (charges, auto-debits and dishonoured cheques are added back; interest and direct credits are deducted). Working from the cash book to the bank applies the mirror image.

Adjusting entries

Only items that the books have not yet recorded need entries.

After these entries the cash book balance is ₹12,45,000 − 1,000 − 8,500 + 2,500 − 12,000 + 25,000 = ₹12,51,000. The bank side, adjusted for the outstanding cheques and the deposit in transit, is ₹12,68,000 − 35,000 + 18,000 = ₹12,51,000. Both sides now agree. The two remaining reconciling items are timing differences that clear on their own.

Stale and post-dated cheques

Stale cheques. In India a cheque is valid for three months from its date. An outstanding cheque that passes this limit can no longer be encashed. The original payment entry is reversed (debit Bank, credit the vendor or payable account), which restores the liability, and a fresh payment is made. The age of the outstanding-cheque list should be reviewed in every cycle; cheques left outstanding for six months or a year are a common audit finding.

Post-dated cheques. A cheque received with a future date is not a receipt until that date. Track it in a memo register of post-dated cheques in hand and post it to the ledger on its date; recording it earlier overstates cash.

Operating considerations

• Statement source. Larger companies receive bank statements electronically every day (MT940 or camt.053 files over a host-to-host link or SWIFT). Smaller companies often download and upload statements manually each month.
• Auto-matching. In mature setups the system commonly clears 70-90% of statement lines automatically. The remainder needs manual review, which is where analyst time is spent.
• Segregation of duties. A person who initiates or approves payments should not prepare the bank reconciliation, otherwise an improper payment could be concealed in their own reconciliation.
• Overdraft and cash credit accounts. The mechanics are identical; the bank balance is a liability, so the signs reverse.
• Multiple accounts and sweeps. Each account is reconciled separately. A master-account reconciliation is not enough, because timing differences arise at individual account level.

How the MT940 feed works

MT940 is the SWIFT standard format for an electronic bank statement. Its structure explains why automated bank reconciliation works and where it stops.

The format carries a built-in integrity check: the opening balance plus the net of all statement lines must equal the closing balance. A file that fails this check is incomplete or corrupt and should be rejected or flagged at parsing.

How an auto-match engine typically ranks candidates. Matching rules are usually configured in tiers, from most to least certain. The exact weights differ between ERP and treasury tools, but the common pattern is a unique reference with an exact amount (for example a UTR or invoice number in the :86: narrative), cleared automatically; amount plus counterparty within a date window where only one open item qualifies, also cleared automatically; grouped matches, where one bank line settles several open items or several lines settle one item, which usually needs specific rule configuration and often goes to review; and tolerance matches, where the amount differs slightly (for example a bank charge netted from a receipt) or the date falls just outside the window, normally flagged for review rather than cleared.

When more than one open item qualifies at the same tier, a well-configured engine does not guess; it leaves the line in the exception queue. The unmatched share is typically the same set of items listed in the reconciling-items table above (bank charges, standing instructions, dishonoured cheques, direct credits): the bank has recorded them, but the books have no corresponding entry to match against.

Workflow

This reconciliation compares the AR aging (the sum of open invoices by customer, taken from the subledger) with the GL accounts receivable control account.

Why differences arise when the subledger is integrated

When a transaction is entered through the AR module, the system posts to the customer subledger and to the GL control account in a single step, so the two agree by design. Differences arise only where a transaction reaches one side and not the other: a journal posted directly to the control account in the GL, bypassing the AR module; a subledger transaction whose GL posting has failed or is held in a batch; postings dated in different periods on each side; foreign-currency revaluation posted at control-account level; or migration or opening-balance differences.

The probability for any single transaction is low, but volume turns a small percentage into a few items every month. Some situations, such as a legal settlement or the merging of customer accounts after an acquisition, have no standard AR transaction type and can only be posted through the GL. This is why the reconciliation is monthly and why manual journals to control accounts are the first thing checked.

Worked example

In each case below the GL is lower than the subledger.

Aging-quality issues

Two common AR problems do not necessarily create a difference between subledger and GL, but they distort the aging and should be cleaned in the same cycle.

Unapplied cash. A customer pays, but the payment cannot be matched to specific invoices: the remittance advice is missing, one payment covers several invoices without a breakdown, or the customer sent a round figure. Until it is matched, the receipt sits as an unapplied credit, so open invoices look overdue while the cash is already in the bank. Unapplied cash is also a tracked collections KPI, because an accumulating balance understates real collections performance.

Misapplied credit notes. A credit note applied to the wrong invoice, or left unapplied, leaves the customer's total correct but misstates the aging by invoice.

Why AR has no routine counterparty check

Accounts payable benefits from a second, external check because vendors send statements to protect their own interest in being paid. Customers have no equivalent incentive: if a customer is under-billed, nothing prompts them to say so. AR reconciliation therefore depends mainly on internal control over billing accuracy. The main outside checks are the auditors' year-end debtor confirmations and customer disputes.

Workflow

The order is deliberate: manual journals are the most common cause and the easiest to find, while interface failures are the least common and the most time-consuming to investigate.

AP reconciliation works at two levels. Level 1 is internal: the AP subledger against the GL AP control account. Level 2 is external: the company's open items against the vendor's own statement. Level 2 is the structural difference from AR.

Level 1: subledger to GL

The integrated-posting logic is the same as for AR: an invoice or payment entered through the AP module updates the vendor ledger and the control account together.

In each case below the GL is lower than the subledger.

GRNI/GRIR is a separate clearing account and is reconciled and aged on its own (see 6.10). A GRNI balance that was cleared incorrectly does not appear as an AP subledger-to-GL difference, but it misstates accruals, expense and inventory.

Level 2: company records to vendor statement

Vendors send statements because they want to be paid in full, so this check runs largely on the vendor's initiative.

The handbook classifies differences as missing invoice, payment in transit, credit, dispute or timing, with an owner and target date for each. A duplicate payment is usually spotted by the vendor first, because the extra cash arrives in their account.

Statement reconciliation is applied by materiality: companies typically request statements from their high-value vendors (for example the top 20 to 30 out of a few hundred), not from every supplier.

Level 1 compares the company's subledger with its own GL. Level 2 compares the same subledger with the vendor's records. Both are matching exercises at invoice level, but the other side of the comparison changes.

Workflow

The fixed asset register holds one record per asset (tag, location, custodian, depreciation schedule). The GL holds aggregate accounts: gross cost, and accumulated depreciation as a contra account. Net book value (NBV) is simply cost less accumulated depreciation. It is a computed figure, not a ledger account, and gross cost stays at original cost until the asset is removed. For that reason the register is reconciled to the GL on cost and accumulated depreciation separately, not on NBV alone.

Why the net figure is not enough

A reconciliation closed on NBV would show nothing wrong, yet a ₹1,20,000 problem sits in each component and happens to offset.

The cause here: an asset costing ₹1,20,000 had been fully depreciated (accumulated depreciation also ₹1,20,000, NBV zero). It was disposed of and removed from the register, but the disposal journal was never posted in the GL. Both GL accounts therefore stayed at their old values, and because the asset's NBV was already zero, the net figure showed no difference. Disposals of fully depreciated assets are the easiest to miss for exactly this reason, which is why they are checked separately.

Other common causes

Journal entries from purchase to disposal

Assumptions: cost ₹1,00,000, useful life five years, no residual value, straight-line depreciation of ₹20,000 a year.

Debits and credits both total ₹1,05,000. If the asset is scrapped for nothing, the entry is simply Dr Accumulated depreciation ₹1,00,000, Cr Fixed asset ₹1,00,000, with no effect on profit.

Why both accounts must be cleared even though NBV is zero. At the end of Year 5, the gross account still stands at ₹1,00,000 and accumulated depreciation also stands at ₹1,00,000. NBV of zero is the difference between them, not a balance in its own right. When the asset leaves the company, both balances must be removed, and the system does not do this on its own: the disposal entry has to be posted. On the balance sheet the two accounts normally appear on separate lines, with NBV shown as the net subtotal.

Over the asset's life the company recognised ₹1,00,000 of depreciation and a ₹5,000 gain, a net cost of ₹95,000: the market paid slightly more than the schedule assumed.

Workflow

Inventory differs from the other reconciliations in what it is compared against. The support is not another ledger; it is the physical count of stock in the warehouse. The count is treated as the authoritative figure, and the books are adjusted to it. Large variances are recounted before any adjustment is posted.

Worked example

SKU: steel rod, 10 mm. Standard cost ₹200 per unit.

The variance has two causes, and they are treated very differently.

Shrinkage: 10 units, ₹2,000. Theft, damage or spoilage confirmed by a security review or damage report. This is a genuine economic loss.

Unrecorded transfer: 5 units, ₹1,000. The stock was sent to the retail counter, but the transfer slip was never processed in the system. Nothing was lost; the stock is simply recorded in the wrong place.

Shrinkage reaches the P&L, while the transfer does not. Writing off every shortage as shrinkage would book more expense than the real loss, so each variance is traced to its root cause before the entry is chosen.

Errors the count cannot detect

If quantities agree (book 500, physical 500) the value can still be wrong. A receipt posted at the wrong unit cost (for example ₹220 keyed in where the batch cost ₹200) leaves quantity correct and valuation overstated. A count only counts units; it does not test rates. Costing errors are found by verifying unit costs against purchase records, as a separate exercise on sampled SKUs. Under standard costing the difference surfaces as a purchase price variance that then needs investigation; under actual costing (such as FIFO) it can stay embedded in inventory value until someone audits the cost layers.

Segregation of duties

Whoever performs the physical count must not approve the book adjustment. Warehouse staff count; the finance team reviews and approves the adjustment entries. Otherwise a shortage could be hidden, or a count falsified to cover an earlier mistake.

Workflow

Payroll reconciliation also works at two levels. Level 1 is internal: the payroll register against the GL. Level 2 is external: GL payables for statutory dues against what has actually been filed on the statutory portals (for example EPFO for provident fund, and the income-tax portal for TDS).

Level 1: payroll register to GL

Other common causes are further pay cycles (another entity or country), statutory deduction rates that differ between the payroll system and the GL posting, and post-payroll adjustments for bonus or tax corrections that reach the register but not the GL.

Level 2: statutory filings to GL payables

Cause: a mid-month joiner's PF was calculated for the full month in the GL postings, while the filed return used the correctly prorated amount. Statutory portals keep their own independent record and may levy interest or penalties on mismatches, so this check cannot be skipped.

The accrual reversal trap

If a month's payroll run completes after the close, the close needs an estimated accrual, which must then be reversed when the actual payroll is booked. Example: March payroll is processed in April; the March accrual is ₹19,50,000 and the actual payroll is ₹19,80,000.

Across the two months the expense totals ₹19,80,000: ₹19,50,000 in March and a net ₹30,000 in April. If the reversal is missed, both the accrual and the actual stay in the ledger and the expense totals ₹39,30,000, a double count. Because reversal is a separate step and not automatic, it is easy to miss.

The check is simple: the accrued salary payable account should be zero after the April close. If it is not, the reversal was missed. This is the highest-value single check in payroll reconciliation, because the impact is large and nothing flags it automatically.

Segregation of duties

The HR or payroll team that produces the register must not sign off the GL reconciliation. Finance verifies independently, because payroll data is both sensitive and error-prone.

Workflow

This section is intentionally brief. The handbook treats tax reconciliation as the same five-step method applied to tax accounts, and places the tax-specific controls in Section 12 (tax and statutory accounting interfaces), which has not yet been worked through in detail. Those controls are listed in the handbook as: reconcile tax subledgers to the GL; validate tax codes and rates against policy; track input and output taxes and withholding; separate book and tax adjustments; and maintain filing and payment evidence. A full treatment with worked examples will be added once Section 12 is covered.

Unlike AR and AP, intercompany has no external statement to compare against; both sides belong to the same group. The practical substitute is a confirmation of balances between the two entities, and matching is done pair by pair (for example India and US, India and Singapore, US and Singapore). The handbook's control point is that amounts match, or differences are explicitly explained. The reconciliation is performed in the transaction currency first, so that exchange-rate effects do not mix with real mismatches.

Worked example: one pair, in USD

Resolution entries

After entries 1 and 2, India's ICAR is $60,000 and the US ICAP is $58,000. The remaining $2,000 is fully explained as cash in transit and is adjusted at group level (entry 3) so the balances eliminate. Where the amounts differ because of a keying error, the correct figure is set by the underlying invoice, not by negotiation between the entities.

The foreign-currency layer

FX arises only in the entity whose functional currency differs from the transaction currency. India's functional currency is the rupee, so its $60,000 receivable is a foreign-currency balance. Suppose it was booked at ₹82.50 (₹49,50,000) and the closing rate is ₹83.50 (₹50,10,000).

The US entity's functional currency is the dollar, so its dollar payable creates no FX.

Worked example: three-entity matrix

When two pairs show equal and opposite differences (−$500 and +$500), check for a wrong counterparty first. Here the US invoiced Singapore $500, but Singapore booked it against India by mistake. Singapore corrects it:

Other practical causes

• A transfer-pricing true-up booked by one side and not the other (common at year-end).
• Different exchange-rate sources: one entity uses the bank rate, the other the group treasury rate (visible in the local-currency view).
• A credit note processed by one entity and not the other.

Controls

Group policy varies, but common practice is to set the intercompany cut-off one or two days before the normal close so that fewer items are in transit, to require both entities' controllers to confirm balances (not just one side), and to ensure the person who posts intercompany invoices does not sign off the reconciliation.

Link to elimination

An unreconciled difference does not eliminate. After elimination, the intercompany balance should be zero; whatever remains appears on the group balance sheet as an intercompany difference that must be explained to the auditors.

Workflow

Suspense and clearing accounts are temporary parking accounts. They hold entries whose correct account is not yet known, or whose other half has not yet arrived. Common examples: bank suspense (unidentified receipts and debits), interface-failure suspense, payroll clearing, card clearing, GRNI/GRIR, and leftover data-migration balances.

The rule: at period end these accounts should be zero, or supported by a fully itemised and aged schedule.

Worked example (31 March)

Gross against net. The same trap seen in fixed assets applies here.

The net figure of ₹2,35,000 hides ₹3,85,000 of items awaiting resolution. Debit and credit items are therefore always listed separately.

Age buckets and escalation

Thresholds follow company policy and may differ.

Resolution entries

Debits to suspense total ₹3,10,000 (items 1, 3, 4) and credits total ₹75,000 (items 2, 5), a net debit of ₹2,35,000 that exactly offsets the net credit balance, leaving the account at zero.

Writing off the 350-day item. Before writing off, document what was done to find support (old files, migration logs, questions to the previous team), then obtain independent senior approval. Quietly clearing such items is an audit red flag.

GRNI aging

GRNI is the most common clearing account.

The same bucket logic applies to aged reconciling items in other reconciliations: unapplied cash, unmatched intercompany items, and old outstanding cheques (stale after three months). An aged item without an owner and target date prevents the reconciliation from being signed off.

Prevention

• Block manual postings to suspense accounts; typically only the system or interface should post to them.
• Require a description on every suspense entry (source and reference number).
• Track the trend: gross balance, number of items, and the percentage of items older than 60 days.

Segregation of duties

The person who posts to suspense must not alone clear or write off the same item. A write-off needs independent approval.

Workflow