Bank account rationalisation: close duplicate accounts without breaking payments or collections

Growing companies often accumulate bank accounts after acquisitions, old projects, foreign-market launches and changes of provider. Rationalising those accounts can reduce fees, fraud exposure and administration, but closing an account too quickly can break payroll, tax Direct Debits, customer collections or lender requirements.

Start with a complete bank-account inventory

List legal owner, bank, currency, purpose, users, balance, inbound receipts, Direct Debits, standing orders, cards, lending links and restrictions. Include dormant accounts with zero balance because they still create user and fraud risk.

Use the inventory to identify duplicates, temporary project accounts and accounts whose original commercial purpose has ended.

Map every payment and collection dependency

Before closure, identify payroll, HMRC instructions, merchant payouts, customer standing payments, refunds and supplier Direct Debits linked to the account.

Do not rely only on the last month's statement. Annual subscriptions, corporation tax or one-off customer payments can use an account only once or twice a year.

Check whether the account is tied to finance or security

A lender can require operating revenue to flow through a charged account, maintain a debt-service reserve or use a particular account for facility drawings.

Obtain lender consent before closing or migrating secured accounts. A low transaction volume does not mean the account is commercially unnecessary.

Move instructions in a controlled sequence

Update suppliers, customers, payroll and tax authorities before the old account closes. Keep both accounts open for an overlap period where practical and monitor residual transactions.

Use Confirmation of Payee and controlled communications when distributing new bank details. A genuine bank-account migration can resemble invoice-redirection fraud to customers.

Remove users and cards as accounts are retired

Close related cards, revoke online users and remove API or Open Banking connections after final reconciliation. Leaving an old portal active defeats part of the security benefit.

Archive statements and audit logs before access disappears, following record-retention requirements.

Reconcile to zero and obtain closure evidence

Resolve outstanding cheques, merchant adjustments, fees and interest before closing. Transfer the final balance under approved treasury instructions.

Keep written bank confirmation showing the account was closed. Review incoming queries for several months because customers can continue using historic details despite notice.

Worked example: an acquired subsidiary has six sterling accounts, but only two are needed after integration. Treasury maps one payroll Direct Debit, two customer collection accounts, an annual insurance debit and one lender-controlled account before deciding which four can actually close.

Score accounts by cost, operational need and risk. A zero-fee account can still be worth closing if it has dormant administrators and no current business purpose.

Repeat the rationalisation annually. New projects and acquisitions can quickly rebuild the account population unless the group requires approval for every new bank account.

Build a dependency matrix before approving closure. For each account, list incoming customer references, merchant settlements, payroll files, tax instructions, card programmes, finance facilities, API connections and named users. Mark each dependency as migrated, tested or still outstanding. This turns closure into a controlled project rather than a collection of emails to different departments.

Use a two-stage shutdown for important collection accounts. First stop creating new instructions that point to the old account, then leave it open for a defined monitoring period while finance contacts customers who continue paying historic details. Only close once residual receipts are immaterial and the company has a documented process for any late payment that still appears.

Worked example: a group wants to reduce twelve sterling accounts to six. One apparently dormant account receives a quarterly insurance refund, another is the destination for an old marketplace payout and a third secures a lender facility. The account inventory prevents treasury from closing them merely because last month's transaction volume was zero.

Measure the result after migration. Track bank fees eliminated, users removed, dormant credentials closed and reconciliation time saved. Rationalisation should produce an observable control and cost benefit, not simply a smaller list of account numbers.

Set a freeze date for creating new activity on accounts marked for closure. Without that rule, teams can continue adding Direct Debits, new customer instructions or card settlements while treasury is trying to migrate away from the account.

For international accounts, consider whether local regulatory, tax or payroll obligations require a domestic account even when group treasury prefers consolidation. Rationalisation should remove duplication, not force every country into an unsuitable central banking model.

Keep closure authority separate from the person preparing the migration. A second approver should confirm that balances are zero, dependencies are cleared and archival requirements are met before treasury sends the final closure instruction to the bank.