Wallet Reconciliation

Wallet reconciliation is the regular comparison of a digital wallet provider's internal records with external sources of truth, to confirm that every customer balance is backed by real funds and that every transaction has been recorded correctly. E-money institutions, mobile money operators, payment apps, prepaid card programmes and crypto custodians all reconcile their wallets, usually every day and in some cases continuously. Differences found in the process, known as breaks, must be investigated and resolved.

The basic test is simple: the sum of all customer balances in the wallet ledger should equal the funds held for customers in bank, trust or safeguarding accounts, after allowing for items in transit. In practice the work is complex, because money enters and leaves through many channels, each with its own reports, timings and fees. Wallet reconciliation is a specific application of reconciliation and is a core control for any business that holds customer money.

A wallet provider typically runs several reconciliations, each comparing a different pair of records:

• Ledger to bank. Movements in the provider's bank and safeguarding accounts, taken from bank statements such as camt.053 files, are matched to top-ups, withdrawals and transfers recorded in the ledger.
• Ledger to processors and schemes. Card top-ups, card spending and payouts are matched against settlement reports from acquirers, issuer processors and card networks.
• Ledger to agents and partners. In mobile money, the electronic value held by agents is matched with their cash-in and cash-out activity, and partner banks' and remittance partners' records are checked against the ledger.
• Ledger to blockchain. For crypto and stablecoin wallets, balances recorded for customers are compared with the on-chain balances of the provider's addresses.
• Customer balances to safeguarded funds. The overall test that customer liabilities are fully covered by the assets held to protect them.

Automated reconciliation tools import data from each source, normalise it into a common format and match items using references, amounts, dates and identifiers. A top-up made by bank transfer, for example, should appear once in the bank statement and once in the ledger with the same reference and amount. Items that match are cleared; items that do not are placed in an exception queue. Matching can be one-to-one, one-to-many, as when a processor pays a single net settlement for thousands of card transactions, or many-to-many, which requires more advanced logic. Settlement reports and settlement files from processors are the main source for these grouped matches.

Common reasons for breaks include timing differences between systems, fees deducted at source, failed or returned payments that were recorded as successful, duplicated entries, manual adjustments and, in the worst case, fraud or system errors that create balances without money behind them. Each break must be explained, corrected and documented, and ageing breaks are escalated.

Regulators treat reconciliation as essential to protecting customer funds. In the UK and EU, payment and e-money institutions must safeguard customer money and carry out frequent reconciliations to show that the amount safeguarded matches what they owe customers. The UK Financial Conduct Authority has tightened its safeguarding regime, with stronger expectations for daily reconciliation, monthly reporting and annual audits, after several firm failures left customers waiting for their money. US money transmitters must hold permissible investments equal to their outstanding obligations, which requires an accurate and reconciled view of balances. In banking-as-a-service arrangements, sponsor banks increasingly require fintech partners to reconcile their ledgers with the bank's records daily, after cases in which shortfalls were discovered only when an intermediary failed.

Weak reconciliation has been at the centre of several high-profile collapses. When a provider's ledger shows more customer money than it actually holds, the gap may be the result of fraud, errors or the use of customer funds for other purposes, and it often comes to light only during insolvency. Customers may then receive only part of their money back, or face long delays. The lesson drawn by regulators and banks is that reconciliation must be frequent, independent of the operations team, automated wherever possible and reviewed by senior management.

Effective wallet reconciliation programmes share several features. They run at least daily, with real-time monitoring for high-volume channels. They use a single, immutable ledger with double-entry records, so balances can be rebuilt. They track float held across banks, agents and partners. They define clear tolerances, ownership and deadlines for resolving breaks, and they keep evidence for auditors. Many firms also link reconciliation to transaction posting controls, so that unmatched incoming funds are held in a suspense account rather than credited to a wallet until they are identified. Specialised reconciliation APIs and software help firms scale the process as transaction volumes grow.