How to Switch Business Bank Accounts Without Missing Payroll or Triggering a Fraud Hold

You finally decided your business bank has to go. Maybe the monthly fees just jumped again, the wire cutoff is still 3 p.m., or the support line keeps you on hold long enough to file your quarterlies. The switch itself sounds simple — open a new account, move the money — until you picture payday landing on a closed account, a vendor's ACH bouncing, or your new bank freezing a client payment for "fraud review."

You can change banks without any of that drama, but not by treating it like a personal account. A business account has at least a dozen invisible connections — payroll, card processing, tax deposits, ACH approvals, and fraud filters — and each one needs to be moved deliberately. Get the order right and you will run two accounts in parallel for a few weeks, reconcile cleanly, and close the old one with no surprises. Get it wrong and you will spend the next month chasing returned payments.

Here is the migration that keeps your team paid and your money moving.

Why Businesses Switch in 2026 — and Why Timing Matters​

Fees are the trigger, but rarely the whole reason. Most owners move because the current bank no longer fits how they get paid and pay others: caps on free ACH transactions, no same-day ACH, no integrated Positive Pay, or treasury services that charge extra for what a competitor includes. The UK's Current Account Switch Guarantee promises seven working days for small businesses; the U.S. has no equivalent. In practice, U.S. consultants and community banks estimate four to six weeks to fully reroute automatic payments and deposits, because you — not the banks — must notify every counterparty.

The worst time to switch is the last week of a month or the week before sales tax, payroll tax, or VAT filings. Your accountant needs a clean bank feed for the full period. The best time is the first two weeks of a month, right after you have closed the prior month, with no payroll tax deposit due in the next ten days.

Phase 1: Map Every Connection Before You Move a Dollar​

Do not open the new account and then figure out what is attached to the old one. Inventory first. The most expensive failures come from the payment you forgot existed until it bounced.

Use this as your working checklist. Export a full year of bank statements and your accounting system's bill pay and bank-feed rules to catch recurring items.

The inventory to build​

Incoming money:

• Client ACH credits and wires
• Merchant services and payment processor settlements (Stripe, Square, PayPal, Shopify)
• Lockbox or remote deposit
• Recurring subscription billing

Outgoing money:

• Payroll direct deposit and payroll tax deposits (federal via EFTPS, state withholding, unemployment, 401(k)/benefits)
• Vendor ACH debits and bill pay checks
• Rent, utilities, and insurance paid by ACH pull
• Credit card autopays, loan payments, line-of-credit sweeps
• Sales tax and estimated income tax payments

Treasury and risk controls:

• Check Positive Pay and Payee Positive Pay issue files
• ACH Positive Pay or ACH debit filters and allowed originators
• Wire templates and dual-approval users
• Positive Pay decision windows and default pay/return settings
• Sweep accounts or zero-balance accounts

System connections:

• Accounting software bank feed (QuickBooks, Xero, Wave — see your dashboard at /fava/ if you use Beancount with Fava)
• Expense card feeds (Ramp, Brex, Amex)
• Payroll provider bank routing (Gusto, ADP, Rippling)
• Accounts payable automation (Bill, Melio)

Put it in a single spreadsheet: counterparty, direction (in/out), method (ACH debit/credit, wire, check), frequency, next due date, and who owns the change. That sheet becomes your migration tracker for the next six weeks.

Phase 2: Open and Seed the New Account the Right Way​

Open the new account well before you need it, and do not immediately push your full operating balance into it.

Banks hold new-account deposits longer under Regulation CC and their own fraud controls. A sudden large ACH credit to a brand-new business account — especially from an unrelated account — is the classic trigger for an extended hold or manual review. Same-day ACH can clear within hours, but standard ACH credits often show as "pending" for two to three business days while the receiving bank verifies funds and checks for fraud, with full availability on day three to five. Larger or irregular transfers and accounts with a history of overdrafts face longer holds.

Seed it instead:

1. Fund the new account with a small test transfer from the old account, titled exactly as your legal entity name.
2. Verify the micro-deposits and that online banking, wire, and ACH origination are enabled.
3. Confirm operating limits: daily ACH origination cap, wire cutoff time, mobile deposit limit, and negative-balance fees.
4. Order checks if you still use them, and enable Positive Pay on the new account from day one.

Keep the old account fully funded while you test. You want two funded, fully functional accounts in parallel — not a drained old account and a frozen new one.

Phase 3: Move the Money Movers in the Right Order​

Order prevents the most common payroll and vendor failures. Move low-risk, reversible items first; move payroll and tax payments only after you have proven the rails.

Week 1-2: Merchant and low-risk inflows​

Update one low-volume processor or client ACH instruction to the new account and confirm the first settlement arrives and reconciles. If you use Stripe or similar, remember that changing the payout account can trigger a short verification hold or a reserve on the new bank — Stripe and other processors often treat a new payout destination as higher risk for the first few payouts.

Week 2-3: Vendor ACH debits and bill pay​

Notify vendors who pull by ACH debit (often utilities, lenders, or software subscriptions) about the new routing and account number. Many ACH debit authorizations require 10 to 14 days notice to update, and a vendor who pulls from a closed account will generate a returned ACH, an NSF fee, and a potential late payment mark. Send the new voided check letter or bank letter and get written confirmation of the effective date.

For vendors you pay by ACH credit or bill pay, update the banking details in your AP system but do not close the old payment method until you have confirmed one successful cycle on the new account.

Week 3-4: Payroll — move it deliberately​

Payroll is the least forgiving rail. A failed direct deposit on payday is not a bookkeeping error; it is a trust error.

• Tell your payroll provider at least two weeks before the next pay date. Providers need to re-verify the new account and update the ACH company ID/originator.
• Run a $0 or $1 prenote if your provider supports it. A prenote is a zero-dollar ACH that validates the routing and account without moving money.
• Keep the old account open with enough cash to cover one full payroll as a backup. Do not fund the new payroll account at the last minute with a large same-day transfer that could be held.
• Update every payroll tax destination separately: federal EFTPS, state withholding, state unemployment, local taxes, garnishments, child support, 401(k), and benefits carriers. Missing one creates a late-deposit penalty that is far more expensive than a wire fee.
• Run the first real payroll from the new account while the old account remains open and funded. Verify that net pays posted, taxes debited, and the provider's debit cleared.

If you pay 401(k) or HSA contributions by ACH, confirm the new routing with each custodian — they often have their own verification window that is separate from payroll.

Throughout: Credit cards, loans, and tax payments​

Move loan and credit-line autodrafts last, after payroll, because a missed loan debit can trigger a default or a sweep failure. For sales tax and estimated payments, update the payment source in each portal (state DOR, IRS Direct Pay/EFTPS) and keep a one-time manual payment method ready in case an automated pull fails during cutover.

Phase 4: Rebuild Your Fraud Defenses on Day One​

A new account with no Positive Pay is an open window. Check fraud remains the most common form of payment fraud against businesses, and a fresh account number that has just been shared with dozens of vendors is exactly when you are most exposed.

What Positive Pay actually does​

• Check Positive Pay: You upload an issue file — check number, amount, payee — each time you issue checks. When a check is presented, the bank compares it to the file. If anything does not match — number, amount, or, with Payee Positive Pay, the payee name — it is flagged as an exception. You log in and decide to pay or return. Most banks require decisions Monday through Friday between about 8 a.m. and 3 p.m. ET. If you do nothing, the item is processed according to your default election (pay or return) — so choose that default deliberately.
• Reverse Positive Pay: Suited for low check volume. The bank shows you every check presented the previous day as an image, and you approve or deny.
• ACH Positive Pay / ACH filters: Separately from checks, you can block all ACH debits by default and allow only pre-approved originator IDs, or set amount caps per originator. Without this, anyone who learns your new routing and account number — for example, from a check you sent — can attempt an ACH pull.

Actions on the new account:

1. Enable Check Positive Pay and ACH Positive Pay before you issue the first check or authorize the first vendor debit.
2. Upload your first issue file (even if it is empty) and confirm your exception-review workflow and backup approver.
3. Configure ACH debit blocks: block all, then explicitly allow payroll provider, benefits, and any vendor authorized to pull.
4. Set realistic exception and reporting emails, and test them with a small check.

The account transition itself creates two additional fraud risks: email interception and "bank change" spoofing. If a vendor suddenly sends new wiring instructions by email claiming they changed banks, verify by phone using a number you already have on file — never the number in the email that announced the change.

Phase 5: Run Parallel, Reconcile Daily, Then Close​

The parallel period is the control. Plan to run both accounts for at least 30 to 45 days, and 60 days if you issue checks.

Daily during parallel:

• Review both accounts for exceptions, returned items, and unexpected debits.
• Match settlements to invoices and processor reports. A common error is to book the processor's 1099-K gross settlement as revenue without subtracting fees and refunds — reconcile to the net that actually hit the bank and track fees separately.
• Watch for duplicate debits: a vendor who missed your update may debit the old account while your AP system also pays from the new account.
• Track outstanding checks on the old account separately. Do not close the old account until every outstanding check has cleared or been reissued from the new account.

Keep your books clean during the transition​

This is where many businesses create a mess they spend months untangling.

• Do not book bank-to-bank moves as income or expense. A transfer between your own operating accounts is a balance-sheet transfer. In double-entry books, that is a debit to the new bank and a credit to the old bank, with no P&L impact. Create a dedicated transfer account or use your accounting software's transfer function so the move does not inflate revenue or expenses.
• Maintain two distinct bank ledgers. If you use plain-text accounting, keep Assets:Bank:OldBank and Assets:Bank:NewBank as separate accounts, and record each transaction against the account that actually cleared it. The migration then becomes a set of auditable transfers, not a mysterious lump. You can read the full history with bean-doctor or visualize the overlap period in your dashboard at /fava/.
• Reconcile both accounts to the bank, not to each other. For each business day, your ledger balance for OldBank should equal OldBank's online balance plus outstanding checks minus deposits in transit, and the same for NewBank. Do not net the two accounts together.
• Document the cutoff. Save the final statement for the old account, the opening confirmation for the new account, and a dated log of when each counterparty confirmed the new instructions. If the IRS or a lender later questions a missed tax deposit or a duplicate deduction, that log is your reasonable-cause evidence.

When the parallel period ends:

1. Confirm zero pending ACH instructions on the old account with the old bank's treasury team.
2. Move any residual balance by wire or official check, not by ACH, for immediate good funds and a clear paper trail.
3. Request written account-closure confirmation and confirmation that debit filters and Positive Pay are disabled.
4. Update your accounting software bank feed to stop polling the old account, and archive the old feed's credentials. For help mapping feeds and rules without the books drifting, see the technical guide at /docs/.

Five Mistakes That Actually Cost Money​

1. Closing the old account after the first successful payroll. One payroll does not prove every quarterly and annual rail moved. Keep the old account through one full sales tax cycle and one quarter-end.

2. Funding the new account with a single large check from the old account. That check can be held for several business days, leaving you short on payroll eve. Use a wire or a series of smaller ACH pushes once the new account is seasoned.

3. Forgetting the portals that store your old routing number. Beyond payroll, check: sales tax, city business license, workers' comp, 401(k), HSA, merchant cash advance, line-of-credit sweep, and any state grant or incentive portal that ACHs your subsidy. Each stores your routing number separately.

4. Not testing exception handling. If your Positive Pay default is "pay" and no one checks exceptions for two days, a fraudulent check will clear. Set the default to "return" during the transition if your bank allows it, and assign a backup approver.

5. Letting processors or marketplaces update the payout account without notifying accounting. The payout may arrive net of a new reserve or on a different settlement lag, and the bookkeeping entry will be wrong for weeks. Book the net settlement and the fee split correctly from day one.

A Six-Week Timeline You Can Copy​

Week 1 — Inventory and open: Build the connection map, open the new account, seed with a small test transfer, enable Positive Pay and ACH filters.

Week 2 — Low-risk move: Shift one processor or low-volume client to the new account; confirm settlement and reconciliation.

Week 3 — Vendors: Update vendor ACH debit authorizations and AP vendor records; move one vendor payment cycle to the new account.

Week 4 — Payroll: Update payroll provider, run prenote, execute first live payroll from the new account while keeping the old account funded; update EFTPS and state tax portals.

Week 5 — Remaining rails: Move loan drafts, credit card autopays, and tax payments; update accounting feeds and expense cards.

Week 6 — Parallel close: Run daily reconciliations on both accounts, resolve outstanding checks, confirm no pending ACH on the old account, then wire remaining balance and close with written confirmation.

Adjust by one to two weeks if you have high check volume, international wires, or multiple payroll schedules. The principle does not change: map, seed, move in order, protect, parallel, then close.

Simplify Your Financial Management​

Switching banks is a good prompt to clean up what the bank does not see: how every payment is categorized, reconciled, and backed up. Maintaining a separate, version-controlled ledger for each account — with explicit transfers instead of hidden bank-feed edits — is what makes the next migration, audit, or disaster recovery trivial instead of chaotic.

Beancount.io gives you plain-text accounting that is transparent, version-controlled, and AI-ready, so your books stay yours no matter which bank holds the cash. Your ledger lives in git, your reports build from text, and your bank history remains readable years later. Get started for free and keep the move — and every move after it — fully in your control.