A backup bank relationship is a second banking path that is already open, approved, funded, tested, and documented before the primary bank becomes unavailable. It matters because payroll, ACH files, wires, card settlements, processor deposits, and customer refunds usually fail at the worst possible time: after the business already needs the money to move.
The point is not to create an unmanaged second operating bank. The point is to have a narrow continuity option with a clear job: keep the business able to pay people, receive money, move emergency funds, and prove what happened afterward.
Short Answer: What to Set Up First
- Open the backup account while the primary relationship is healthy.
- Confirm the bank’s legal identity, insurance status, public financial condition, and enforcement history.
- Fund the account for the specific job it must perform, such as payroll, emergency wires, refunds, or deposit concentration relief.
- Activate treasury-management access, ACH permissions, wire controls, alerts, reporting, and fraud controls.
- Run controlled ACH, wire, login, alert, and reporting tests before relying on the account.
- Write the switching procedure so finance, operations, and executive approvers can use it without searching old emails or depending on the unavailable bank portal.
The reason is practical. The FDIC failed bank list shows Silicon Valley Bank closed on March 10, 2023, Signature Bank closed on March 12, 2023, and First Republic Bank closed on May 1, 2023.[1] That matters because the operational question was not only whether deposits would ultimately be protected; it was whether companies could fund payroll, move balances, and change payment instructions under pressure.
Sponsor-bank and fintech-program risk can create a different kind of disruption. Federal Reserve and OCC actions involving Evolve Bank & Trust and Blue Ridge Bank show how bank-partner oversight, fintech programs, and compliance controls can become continuity issues even when the bank itself has not failed.[2][3] For a fintech, the backup operating account and the backup sponsor-bank plan are related, but they are not the same thing.
Decide What the Backup Bank Must Do
A backup account should have a written job description. A token balance is not a continuity plan; a tested payroll, ACH, wire, and settlement path is a plan that can be used.
- Payroll continuity: confirm the payroll provider can accept the backup routing and account number, and record the deadline for switching the funding account.
- Vendor payments: decide whether emergency vendors will be paid by ACH, wire, card, or check, because each rail has different setup and approval work.
- Customer or processor deposits: identify which merchant processor, payment facilitator, marketplace, or invoicing system would need new settlement instructions.
- Sponsor-bank continuity: fintechs should separate backup operating cash from backup program sponsorship, because a sponsor-bank change can require compliance, ledger, card, lending, disclosure, and customer-notice work.
- Deposit concentration relief: decide whether the backup bank will hold excess deposits, payroll-only cash, or only a tested payment path.
Vet the Bank Once, Then Reuse the File
Keep the public-source review in one file instead of repeating it in every procedure. Confirm the bank’s legal identity and active status in FDIC BankFind or the Federal Reserve’s National Information Center, pull recent Call Report data from the FFIEC Central Data Repository, and search the FDIC, OCC, and Federal Reserve enforcement pages for the bank, its holding company, and any public program names that matter to the relationship.[4][5][6][7][8][9]
The screen does not need to become a full bank-stock research note. For continuity planning, the useful question is whether the institution is legally the bank you think it is, whether recent public filings show obvious balance-sheet or capital concerns, whether uninsured-deposit concentration or credit quality deserves a closer look, and whether public orders point to operational, compliance, fintech-program, or payments risk.
When comparing candidates, use the bank profile search to identify institutions, the peer comparison view to keep alternatives in context, and the public-data context view only when the team needs the underlying public-data basis behind the comparison.
Open the Account Early
Business onboarding can be slow because the bank is not just opening a checking account. It is verifying the entity, beneficial ownership, signers, expected activity, ACH exposure, wire controls, and fraud controls. For fintech and sponsor-bank relationships, the June 6, 2023 Interagency Guidance on Third-Party Relationships: Risk Management is the right source to cite because it covers planning, due diligence, contract negotiation, ongoing monitoring, and termination.[10]
| Setup item | What to have ready before disruption | Source or check |
|---|---|---|
| Entity documents | Formation documents, EIN record, ownership details, and board or manager authorization for the backup account. | Bank onboarding file; verify institution identity in the bank-vetting file. |
| Authorized signers | Current signer list, backup approver, and written removal process after staff changes. | Bank signature card and online banking entitlement report. |
| Online banking users | Role-based access for payment entry, approval, reporting, and statement download. | Access review record kept with the continuity plan. |
| ACH permissions | Originator approval, exposure limit, file approval path, and payroll-provider compatibility. | Nacha rules and bank ACH agreement. |
| Wire limits | Internal approval workflow, callback rules, template controls, and cutoff times. | Bank wire agreement and customer cutoff schedule. |
| Fraud controls | ACH debit blocks or filters, positive pay if checks remain in use, alerts, and dual approval for new payees. | Bank treasury-management setup; AML/CFT control expectations can be cross-checked against FDIC FIL-42-2024.[11] |
If the backup relationship is a sponsor-bank candidate, ask for the bank’s process for approving fintech programs, new products, transaction monitoring, consumer compliance, BSA/AML review, and termination support. A bank that cannot explain those steps before signing is not a good emergency option.
Fund the Backup Account
An unfunded backup account is mainly paperwork. The funding decision should state what the account is protecting: payroll funding, vendor payments, customer refunds, chargeback exposure, or temporary deposit diversification.
Use published limits as hard gates. The FDIC insured-deposits brochure sets the standard maximum deposit insurance amount at $250,000 per depositor, per insured bank, for each ownership category; Nacha’s Same Day ACH rule sets a $1 million per-payment cap; and the Federal Reserve’s Fedwire information explains the network business day and third-party transfer deadline.[12][13][14] Those limits do not replace the bank’s own customer cutoffs, exposure limits, or approval rules.
For deposit concentration, do not confuse another branch with another insured bank. The backup account should be at a separately chartered insured bank if insurance diversification is part of the reason for opening it.
If the account is only for payroll, the balance may be small but the ACH authority must be real. If the account is for emergency liquidity, the balance and wire permissions need to match the amount the company would actually move. If the account is for customer refunds or processor settlement, the instructions must be stored and tested in the systems that control those flows.
Example: Payroll Is Due in Two Days
Assume the primary bank portal is frozen two days before payroll funding. The controller opens the switching procedure outside the primary bank portal, confirms the backup account balance, checks the payroll provider’s deadline, changes the funding account, and asks the backup approver to release the ACH file. A second person confirms that alerts, ACH reports, and payroll confirmation can be downloaded after acceptance. That is the difference between owning a backup account and owning a usable backup bank relationship.
A Simple Backup Banking Workflow
- Name the failure mode: primary bank online banking is unavailable, primary bank has a fraud review hold, or the company needs to reduce deposit concentration.
- Pick the needed rail: payroll ACH, emergency wire, processor settlement, customer refund, or vendor payment.
- Use the saved bank-vetting file to confirm the institution, public filings, and enforcement search results.
- Open the account, activate treasury-management permissions, and document who can enter, approve, and release payments.
- Run controlled ACH, wire, login, alert, and reporting tests, then record the result in the switching procedure.
- Review the procedure after staff changes, payment-provider changes, new product launches, and updated public filings.
This workflow gives the board, founder, analyst, or reporter a repeatable file: source checks, account status, payment rails tested, user permissions, and the exact switch path if the primary relationship is unavailable.
Test the Rail Before You Need It
Testing should prove both the external payment network and the bank’s permissions for your account. A bank may support ACH or wires in general while your specific account still lacks origination approval, daily exposure, template approval, or user entitlement.
- ACH: send a controlled ACH credit or provider-supported test file, confirm settlement, and verify that the backup bank’s originator limit fits the payroll or vendor use case.
- Same Day ACH: document whether the bank allows Same Day ACH for your account, then compare the payment need with the per-payment rule and the bank’s own cutoff.
- Wire: test the wire template and approval path before relying on Fedwire, because the network deadline is not the same thing as your bank’s customer cutoff.
- Payroll processor: confirm that the backup account can be stored, verified, and activated without a new underwriting cycle during a payment emergency.
- Processor deposits: document where settlement instructions are changed and who can approve the change inside the processor or marketplace dashboard.
- Reporting: confirm that statements, balance reports, ACH return reports, wire confirmations, and alert history can be downloaded by the people named in the plan.
A test that only logs into online banking is not enough. The rail is ready only when a user can initiate the payment, a separate approver can release it, the bank accepts it, and the company can prove what happened afterward.
Document Switching Procedures
During a disruption, staff should not be searching old emails for routing numbers, bank contacts, or processor settings. The switching procedure should live in a secure location that finance, operations, and executive approvers can reach without depending on the unavailable bank.
| Procedure | Include | Trigger |
|---|---|---|
| Payroll switch | Backup account details, payroll-provider path, funding deadline, approver, and last test result. | Primary payroll funding path is unavailable or under review. |
| Vendor payment switch | Payment rail, payee verification script, approval workflow, and bank limit confirmation. | A required vendor payment cannot wait for the primary bank. |
| Customer deposit switch | Processor or customer instructions, communications owner, reconciliation owner, and rollback path. | Incoming deposits need a temporary destination. |
| Emergency transfer | Transfer purpose, approver, destination bank, payment rail, and source of supporting balance data. | Deposit concentration or operational risk requires moving funds. |
| Fraud response | Bank contact, internal escalation owner, ACH block status, wire template status, and evidence log. | Primary or backup account has suspected unauthorized activity. |
Do not store the procedure only inside the primary bank portal. If the outage or review affects portal access, the continuity plan should still provide the legal bank name, routing number, account nickname, approvers, support contacts, and tested payment steps.
Review the Relationship Periodically
A backup bank relationship becomes stale when the company grows, signers leave, ACH limits lag payroll, processor instructions change, or the bank’s public risk profile changes. Keep the review short and tied to actual operating risk.
- Refresh the saved bank-vetting file when new public data is available or when the bank’s condition becomes material to the continuity decision.
- Search enforcement sources again for the bank, holding company, and public sponsor-bank program names.
- Retest ACH, wire, login, alerts, reporting access, and processor or payroll compatibility after any treasury-management change.
- Update signer and user access immediately after role changes, terminations, finance-team restructuring, or board-authority changes.
- Reconfirm that the account’s funding level still matches the job it is supposed to perform.
Backup Banking Is Continuity Planning
A backup bank relationship protects against bank failure, but it also protects against outages, fraud reviews, payment delays, sponsor-bank disruption, and deposit concentration. The relationship is ready when the file contains the bank’s legal identity, public-source checks, funding decision, tested rails, user permissions, fraud controls, and switching procedures.
If any of those fields are blank, the backup bank is still an idea. Finish the setup while the primary bank is healthy, because the hardest time to negotiate ACH access, wire controls, signers, processor changes, and board approvals is after the business already needs them.
Source note: This post was reviewed on April 23, 2026. The workflow above uses public FFIEC, FDIC, OCC, Federal Reserve, and Nacha sources; verify current filings, limits, schedules, and enforcement updates before citing the material in a credit memo, board packet, or investor document.
FAQ
How much money should sit in the backup account?
Enough to support the job assigned to the account. A payroll-only backup account may need a smaller standing balance plus a tested funding path, while an emergency liquidity account may need a larger balance, higher wire limits, and tighter approval controls.
Is a backup sponsor bank the same as a backup operating account?
No. A backup operating account can help with cash movement, payroll, wires, and deposits. A backup sponsor-bank plan is broader because it may affect customer accounts, card issuing, lending, ledger operations, compliance ownership, disclosures, and termination support.
Sources
- [1] FDIC failed bank list: https://www.fdic.gov/bank-failures/failed-bank-list
- [2] Federal Reserve enforcement action involving Evolve Bancorp, Inc. and Evolve Bank & Trust: https://www.federalreserve.gov/newsevents/pressreleases/enforcement20240614a.htm
- [3] OCC release involving Blue Ridge Bank, N.A.: https://www.occ.gov/news-issuances/news-releases/2024/nr-occ-2024-15.html
- [4] FDIC BankFind Suite: https://banks.data.fdic.gov/bankfind-suite/
- [5] Federal Reserve National Information Center: https://www.ffiec.gov/NPW
- [6] FFIEC Central Data Repository: https://www.ffiec.gov/node/31
- [7] FDIC enforcement decisions and orders: https://orders.fdic.gov/s/
- [8] OCC enforcement actions: https://www.occ.gov/topics/laws-and-regulations/enforcement-actions/index-enforcement-actions.html
- [9] Federal Reserve enforcement actions: https://www.federalreserve.gov/supervisionreg/enforcementactions.htm
- [10] Interagency Guidance on Third-Party Relationships: Risk Management: https://www.fdic.gov/news/financial-institution-letters/2023/fil23029.html
- [11] FDIC FIL-42-2024 on AML/CFT program rule issuance: https://www.fdic.gov/news/financial-institution-letters/2024/issuance-anti-money-launderingcountering-financing
- [12] FDIC insured-deposits brochure: https://www.fdic.gov/resources/deposit-insurance/brochures/insured-deposits/
- [13] Nacha Same Day ACH rule and per-payment limit: https://www.nacha.org/million
- [14] Federal Reserve Fedwire Funds Service information: https://www.federalreserve.gov/paymentsystems/fedfunds_about.htm