Balance Reconciliation

Balance reconciliation is the process of comparing the balance of an account, wallet or pool of funds as recorded in one system with the balance recorded for the same thing in another system, or with a balance recalculated from its transactions, at a fixed point in time. If the balances agree, the records are consistent at that moment; if not, the difference must be traced. It is used by accountants closing the books, by banks and payment firms checking their ledgers against bank and central-bank accounts, and by crypto firms checking internal records against the blockchain.

It complements transaction reconciliation, which matches individual records. Balance checks are fast and catch large problems early; transaction checks explain where a problem comes from. Payment and e-money firms use balance reconciliation to prove that the money they owe customers is fully covered by the funds they hold, a requirement of safeguarding rules in the UK and EU and of reserve rules for stablecoin issuers.

Imagine a club treasurer who keeps a tally of what each member has paid into a shared holiday fund. The bank account holding that money should contain at least the total of all members' tallies. Once a week the treasurer adds up the tallies and looks at the bank balance. If the bank holds less than the members are owed, money is missing or a payment was recorded wrongly.

That weekly comparison is a balance reconciliation. It does not check every payment, only whether the totals line up. It is quick, so it can be done often. When the totals disagree, the treasurer then goes through the individual payments to find the cause.

Cross-system comparison. The balance in system A is compared with the balance in system B: a company's general ledger against the bank, a bank's internal record of its reserve account against the central bank's statement, or a customer ledger total against an omnibus account.

Roll-forward check. The closing balance is recalculated from the opening balance and the period's movements:

• $B_{\text{open}}$ is the confirmed opening balance.
• $\sum \text{Credits}$ and $\sum \text{Debits}$ are the totals of money in and money out during the period.
• $B_{\text{close}}$ is the expected closing balance, compared with the reported one.

Worked example: a wallet opens the day at 10,000, receives 4,000 and sends 3,000, so the expected closing balance is 10,000 + 4,000 − 3,000 = 11,000. If the system reports 11,200, a credit of 200 has been recorded in the balance but not in the movements, or a debit is missing. The roll-forward check is especially useful in software ledgers where balances are stored separately from transactions; a cached balance that drifts from the sum of its entries is a classic bug.

Firms that hold customer funds without being banks must keep them separate from their own money and prove it regularly. The core test is:

If customers are owed 5,000,000 and the safeguarding account holds 4,980,000, there is a shortfall of 20,000 that the firm must top up from its own money. In the United Kingdom, the FCA's new safeguarding rules for payment and e-money institutions (policy statement PS25/12, in force from 7 May 2026) require reconciliations of safeguarded funds on each business day, a monthly safeguarding return and, for most firms, an annual safeguarding audit. Investment firms holding client money under the FCA's CASS 7 rules perform an internal client money reconciliation each business day. In the United States, fintechs that hold customer money in for-benefit-of accounts at a partner bank face the same practical need: the sum of individual customer balances in the fintech's ledger must equal the money in the FBO account.

Exchanges and custodians compare the total of customer balances in their internal ledger with the on-chain balances of the wallets they control. Because a public blockchain shows wallet balances openly, this check can be run continuously, and it underpins proof of reserves publications. Stablecoin issuers reconcile the circulating supply of tokens, which changes through minting and burning, with the value of reserve assets held. In the United States the GENIUS Act of July 2025 requires permitted stablecoin issuers to publish monthly reserve reports, certified by the chief executive and chief financial officers and examined by a registered public accounting firm.

Accounting teams reconcile balances monthly as part of account reconciliation; treasury and payment operations do it daily or intraday using balance reporting feeds; crypto platforms may do it every few minutes. The main limitation is that a balance match proves only that totals agree. Offsetting errors, such as a missing payment and an unrelated duplicate of the same amount, pass a balance check undetected, which is why it is usually paired with line-level matching and, in complex flows, with multi-step reconciliation. Timing also matters: both balances must be taken at the same cut-off, or in-flight payments will show as false differences.

• FCA PS25/12: Changes to the safeguarding regime for payments and e-money firms
• FCA Handbook CASS 7.15: Records, accounts and reconciliations