- Open and test the new account before moving anything critical
- Inventory every incoming payment route
- Move outgoing payments in controlled groups
- Keep a controlled overlap balance at the old bank
- Rebuild security, controls and accounting connections
- Close the old account only after evidence is clean
- Editorial Verdict
- Sources
Open and test the new account before moving anything critical
Complete account opening, online banking enrollment, user roles and required treasury setup before changing incoming or outgoing payments. Confirm the new routing and account numbers and test that authorized employees can sign in using their own credentials. If the company needs ACH origination, wires, remote deposit capture or positive pay, make sure those services are approved and operational rather than assuming they activate automatically with checking.
Fund the account with a modest test amount and run low-risk transactions first. A migration should not begin with payroll or a six-figure vendor wire. Testing reveals holds, payment limits, approval settings and accounting-feed issues while the old bank is still available as a fallback.
Confirm the new bank’s transaction limits against the company’s largest normal day. A successful $100 test transfer does not prove the account is ready for a $200,000 payroll file or a month end concentration transfer.
Inventory every incoming payment route
List card-processor settlements, marketplace payouts, customer ACH credits, checks, lockbox instructions, payment links and any direct deposits. For each flow, record the payer, current account, change procedure and expected first date at the new bank. Customers may need new remittance instructions, and merchant processors can require verification before changing the settlement account.
Do not judge the migration complete because a routing change was submitted. Confirm the first actual credit in the new account. Keep the old account open until recurring and slow-moving sources have been observed at least once, especially customers that pay monthly or quarterly.
Give major customers a dated instruction sheet and verify receipt when the payment is material. Relying on a footer note on an invoice is risky if an accounts payable department continues using old stored banking instructions.
Move outgoing payments in controlled groups
Catalog payroll, payroll taxes, federal and state tax debits, rent, insurance, loan payments, card payments, subscriptions, ACH debits, check runs, wires and bank bill-pay instructions. Move the highest-consequence payments first with enough lead time to correct problems. Payroll and tax payments deserve special attention because missed deadlines can create immediate operational or financial consequences.
For vendor debits, change the authorization with the vendor rather than relying only on a stop-payment instruction at the old bank. For bank-originated bill pay, recreate the instructions at the new institution and check scheduled dates. Maintain a migration tracker showing submitted, pending and verified status for each payment.
Coordinate the payment move with the accounting close. Changing bank details in the middle of a reconciliation period can create duplicate entries, unmatched transactions and uncertainty about which account should contain an expected debit.
Keep a controlled overlap balance at the old bank
An old account should normally retain enough money to cover checks and automatic debits that have not yet cleared. FDIC and CFPB switching guidance for checking accounts emphasizes opening the new account first, updating automatic transactions and waiting for outstanding withdrawals to post before closing the old account. The same sequencing is operationally useful for businesses even though business accounts can have different legal protections.
Estimate the overlap balance from the outstanding-check list, recurring debits and a buffer for unknown items. Review the old account every day during the transition. A premature closure can turn an otherwise clean migration into returned payments, vendor confusion and emergency transfers.
Set an explicit date for reviewing whether the overlap balance is still necessary. Otherwise companies often leave large idle balances at the old bank for months because no one owns the final clean up decision.
Rebuild security, controls and accounting connections
Do not copy old permissions blindly. Use the switch to remove stale users, set transaction limits and enforce dual approval where appropriate. Configure alerts, ACH debit controls, positive pay and beneficiary restrictions before moving large transaction volume. Update accounting software, ERP bank feeds, reconciliation rules and payment templates using verified bank information.
Document which employee owns each treasury function. A migration often exposes hidden dependencies, such as a former employee still receiving alerts or a controller using a shared credential. Correct those weaknesses while both banks remain accessible.
Rebuild recurring reports as well as transaction access. Treasury staff may depend on daily balance emails, BAI files, accounting feeds or merchant reports that stop working when the old account is retired.
Close the old account only after evidence is clean
Wait until incoming deposits are consistently landing at the new bank, outgoing payments have cleared correctly and the outstanding-check list is empty or deliberately handled. Then transfer the remaining funds, download statements and transaction records needed for accounting, and request closure using the bank’s required process. Obtain written confirmation of closure.
After closure, continue monitoring vendor notices and accounting records for attempted transactions against the old account. Destroy unused checks and debit cards securely. Keep the final statement and closure confirmation with the company’s banking records so future reconciliations or audits can explain where the account ended.
Archive the migration tracker with the closure confirmation. If a vendor later claims a missed payment or an auditor asks when the account changed, the company can show when each instruction was updated and verified.
Keep a written migration log with the old account, new account, payment owner, change date and verification date for each recurring flow. That sounds administrative, but it gives the finance team a single place to confirm what moved and what still depends on the old bank. For a growing company, that record is much safer than relying on individual employees to remember which vendor or platform was updated.
Editorial Verdict
Run the switch as a staged migration.
Open and test first, move incoming and outgoing flows in tracked groups, maintain a controlled overlap balance, then close only after the evidence is clean. The goal is not the fastest possible switch. It is a switch with no missed payroll, taxes, customer receipts or vendor payments.