Business bank outage contingency plan: keep critical payments moving safely

An online-banking outage can block payroll, supplier payments, card access or account visibility even when the company has enough money. The safest response is prepared in advance: know which payments are truly critical, which alternative routes are authorised and how to avoid creating duplicates while systems recover.

Identify which banking functions become critical after one hour, one day and three days

The FCA defines operational resilience as the ability to prevent, adapt to, respond to, recover from and learn from operational disruption. Its rules apply to many banks, payment firms and e-money institutions, and require in-scope firms to identify important business services and plan how to remain within impact tolerances.

A customer business can use the same logic internally even though it is not subject to those FCA resilience rules. List payroll, same-day property payments, supplier cut-offs, card settlement, tax deadlines and access to working cash. Not every payment deserves an emergency workaround after a 30-minute app outage, but some transactions genuinely cannot wait until tomorrow.

Keep an authorised secondary route rather than relying on one banking login

A secondary business bank account can provide resilience when the primary provider is unavailable. It should already be KYC-complete, funded to an agreed minimum and integrated into the company's approval policy. A backup account opened during a crisis is rarely useful for a payment due in the next hour.

Do not use a director's personal account as the emergency route. That blurs ownership, weakens controls and complicates reconciliation. The secondary account should belong to the same business entity and have named authorised users. Review it periodically so cards, security tokens and user permissions still work.

Confirm the provider incident and payment state before pressing send again

During an outage, check the bank's official service-status page or support channel and record the incident reference where available. If a payment submission produced an error message, do not assume it failed. The instruction may have reached the bank even though the confirmation screen did not load.

Check transaction history, pending-payment screens and bank support before retrying a material payment. The FCA's operational-resilience observations emphasise recovery planning, communications and manual workarounds because disruption can affect several connected systems at once. A manual workaround is only useful if it does not create a second error.

Prioritise obligations by economic and legal consequence

If several payments are blocked, rank them. Payroll due today, a CHAPS property completion and a tax liability at its deadline can deserve priority over a supplier invoice that is not due for five more days. Call counterparties early if the outage threatens a deadline and preserve evidence that the business attempted to pay.

For high-value CHAPS, speak to the bank about its contingency process rather than switching rails casually. The Bank of England maintains contingency arrangements within the RTGS and CHAPS environment for participant disruption, but a corporate customer's practical options still depend on its own bank. Ask the provider what route is available rather than inventing one.

Use one incident log to prevent the same payment being released twice

Record every attempted payment with beneficiary, amount, reference, time, user, channel and status. If finance switches to the backup account, mark which instructions are being replaced and who approved the reroute. This becomes essential when the primary bank returns to service and previously queued payments begin to process.

Do not upload the same payroll file at two banks unless the first bank has confirmed it will not execute. If a payment later duplicates, contact the provider and beneficiary immediately, but prevention is far better than recovery. Outages create time pressure, which is exactly when payment controls need to become more explicit.

After service returns, reconcile the incident before closing it

Download statements from both primary and backup accounts, identify every payment attempted during the outage and match them to the accounting ledger. Check rejected, duplicate, delayed and manually rerouted items. Also review bank fees and any contractual consequences from late payment.

Then improve the contingency plan. The FCA's March 2026 resilience observations stress lessons-learned exercises and continuing remediation after incidents. A normal business can apply the same discipline: ask which dependency failed, what information was missing and whether the backup route genuinely worked. The next outage should be easier to manage than the last one.

Keep a short contact sheet as part of that plan. It should include the bank's business-support number, relationship manager, backup-bank details, payroll provider, accountant and any legal or transaction contact involved in time-critical payments. During an outage, finding trusted contact details should not depend on one employee's phone or inbox.

Also test the backup process periodically when nothing is wrong. A small authorised transfer from the secondary account can confirm that credentials, approvals and beneficiary setup still work. A contingency route that has not been touched for two years can fail at exactly the moment the business assumes it is available.