
- When to switch business bank accounts
- Before you switch: inventory your money flows
- The 12-step bank-to-bank migration
- Common gotchas
- How to switch business bank accounts faster
- The switch is yours to control

Most finance leaders consider switching business bank accounts at some point. The triggers are usually the same: fees that outpace your revenue, integrations that stop working, a service tier you've outgrown. It's a growth move, not a chore. But it can feel like one.
Moving from one bank to another typically means rerouting everything connected to your account: payroll, vendor payments, accounting feeds, card statement debits. Being intentional protects you during the switch. It's what separates a clean migration from a messy one.
The short version: how to switch business bank accounts
- Open the new account: have your EIN, formation documents, and ownership info ready. KYB approval ranges from same-day to several business days.
- Fund it: move a starter deposit from the old account. Don't move everything yet.
- Reroute inbound: update routing details with customers on ACH auto-pay, payment processors, and anyone sending funds to you.
- Reroute outbound: update payroll, tax authorities, vendors, and subscriptions with the new account details.
- Close the old account: only after monitoring both accounts for at least 30 days and confirming every recurring flow has moved.
The rest of this guide covers each step in detail, including what to inventory before you start, common failure points, and how to sequence the reroute without disrupting payroll or vendors.
When to switch business bank accounts
It’s time to switch business bank accounts when your current setup is actively costing you. That usually means fees that scale faster than your revenue, integrations that drop weekly, a service tier you've outgrown, or an inability to get a working line of credit.
Small businesses are increasingly looking beyond their primary bank for credit: among applicants, the share seeking financing from online fintech lenders grew from 17% to 29% between 2020 and 2025, according to the Federal Reserve's 2026 Report on Employer Firms. When your bank can't underwrite your growth, the relationship starts to cost you even more than the fees do.
The triggers
- Fees outgrew you. Monthly minimums, transaction caps, and wire fees that add up to thousands per quarter.
- Integrations broke. Your bank's API doesn't connect cleanly to your accounting software, your spend platform, or your accounts payable tool.
- You can't get a line of credit. Your bank doesn't underwrite businesses like yours, or your relationship banker left and nothing replaced them.
- You outgrew the service tier. You're a Series A company on a sole-proprietor product, or a small business on an enterprise tier that costs more than the value it delivers.
How to time the switch
A switch is one moving part. Avoid layering it on top of another. Skip these windows:
- Mid-fundraise. Investors will ask for clean bank statements. A switch mid-process creates fragmented records.
- Mid-audit. Don't introduce a new account during a 10-K or seed-stage audit.
- Mid-payroll quarter-close. The payroll rails fund the people who keep the lights on. Don't reroute them in a quarter you're closing.
- During year-end. Closing the books across two banks is its own audit problem.
Before you switch: inventory your money flows
Before you open the new account, write down everywhere your money currently moves. The audit is your single most useful pre-switch artifact. Once you have a complete picture of where money moves, the reroute is mechanical.
What's coming in
- Customer payments (ACH, wire, check, payment-processor payouts)
- Investor capital calls or tranche disbursements
- Loan disbursements
- Refunds and reimbursements from third parties
What's going out
- Payroll (the highest-stakes line item)
- Tax payments (federal, state, sales tax, payroll tax)
- Vendor bill pay (every recurring vendor)
- Subscriptions (SaaS, utilities, services)
- Card statement payments
- Loan servicing
What's connected
- Accounting software (the bank feed connection)
- Payment processors (Stripe, Square, and similar)
- Payroll provider
- AP automation tool
- Spend management platform
- Expense reimbursement system
That list is usually longer than teams expect. Write it down before you do anything else.
The 12-step bank-to-bank migration
A bank-to-bank switch is roughly 12 sequenced steps. Each one looks small in isolation. Most of the work is sequencing them right: don't close the old account before recurring payments reroute, and don't move payroll before the new account is fully funded.
- Open the new business bank account. Apply through whichever channel the bank supports. Have your Employer Identification Number (EIN), formation documents, and beneficial-ownership info ready. Know Your Business (KYB) approval can take from same-day to several business days.
- Submit KYB documentation. Banks ask for entity documents, ID for owners over 25% ownership, and proof of address. Have these scanned and ready before you start.
- Fund the new account. Move a starter deposit over from the old account. Don't move everything yet: the goal is enough liquidity to test, not enough to strand you if something goes wrong.
- Update payroll routing. Push the new account info to your payroll provider. Most providers need several days' lead time before the next payroll run.
- Update tax payment routing. Federal, state, sales tax, and payroll tax all pull from a designated account. Update each one separately.
- Update vendor ACH details. For every recurring vendor, send a formal notice with the new routing and account number. Vendors keep your old info in their AP system until you proactively replace it.
- Update customer-facing ACH instructions. If you invoice with bank details, update your invoice templates and notify customers on auto-pay. Send the new wire instructions to anyone who pays you by wire.
- Reconnect accounting software. Bank feeds are tied to credentials, not just account numbers. Reconnect the new account inside your accounting platform. Run a test sync.
- Reconnect spend management and AP tools. Your card program and bill-pay tool need to know which account to fund. Update the connection inside each tool.
- Monitor both accounts. For at least 30 days, watch the old account for stray transactions: a vendor that wasn't updated, a customer who didn't switch, a recurring debit you forgot.
- Confirm all flows moved. After a full month of running on the new account, look at the prior month's transaction list and confirm every recurring flow has switched.
- Close the old account. Only after step 11 is clean. Most banks require a written closure request and will return any remaining balance by check.
| Flow type | Action needed |
|---|---|
| Customer payments (ACH) | Send updated routing details |
| Payroll | Update before next pay run |
| Federal tax payments | Update in EFTPS profile |
| State tax payments | Update before next due date |
| Vendor bill pay (recurring) | Send formal notice with new details |
| SaaS subscriptions | Update payment method per vendor |
| Loan servicing | Contact lender directly |
| Accounting software | Reconnect bank feed |
| AP automation | Update funding account |
| Spend management | Update connected account |
| Payment processor payouts | Update in platform settings |
Common gotchas
These are the connections to double-check during a traditional bank-to-bank switch. They're predictable, so they're easy to plan around.
- Payroll routing drops. Your payroll provider holds onto old account numbers in its routing tables. Even after you update the primary, individual employees or tax payments can keep routing to the old account if the provider's batch hasn't refreshed. Verify on the first payroll run after the switch.
- Vendor payments to the old account number. Vendors keep your old bank info on file in their AP systems. Any vendor you don't proactively notify will keep pulling from the old account. Until you close it, those payments succeed silently and your reconciliation goes sideways.
- Accounting-software reconnection. Bank feed connections are tied to credentials. When you close the old account, the feed breaks. Reconnect the new feed during the overlap window so historical transactions keep flowing into your accounting system.
- Customer ACH details. Customers on auto-pay using your old account info will keep paying the wrong place. Send an update notice to every customer with the new routing and account numbers. Expect a few stragglers to need a manual reminder.
- Reconciliation during the overlap. With two accounts running for 30 days or more, your books need to track transactions across both. Make sure your accounting feed syncs both accounts during the overlap, and reconcile each against statements weekly. A stray vendor pull or customer payment hitting the old account is easy to miss if you're only watching the new one.
How to switch business bank accounts faster
Most of what makes a bank-to-bank switch take 6 weeks isn't the new account. It's reconnecting your card program, your AP tool, your accounting feed, your spend platform, and your expense reimbursement system to the new account.
When your operating account is part of a platform that already includes those tools, the connections come built in. There's nothing to rebuild during a switch. Fewer connections mean fewer places the switch can break, and fewer weeks spent on cleanup.
Ramp Treasury is designed around exactly this shape: moving cash, not rebuilding plumbing. Here's how the same migration collapses into four phases instead of twelve steps.
Phase 1: Open and fund the Ramp Business Account
Apply for the Ramp Business Account, your primary operating account¹: where cash sits, where payments run from, where your finance team works day to day.
Owners and admins typically handle the application. Once approved, fund it with a starter deposit from your existing operating account. This combines two product steps: opening the account and putting cash in it.
Phase 2: Move inbound flows
Update routing and account details with the parties that send money your way: customers on ACH auto-pay, payment processors paying out from platforms like Stripe or Square, and any party running tax refunds back to you. This is one phase because inbound activity routes to one place inside the platform.
Phase 3: Move outbound flows
Update the payment rails for what goes out: payroll provider, tax authority direct debits, vendor bill pay, subscriptions. Inside Ramp, bill pay and card statement payments already run from the operating account when it's available, so reconnecting them isn't a separate step.
Phase 4: Set up automations and controls
Configure sweeps, target balance thresholds, and approval workflows. This is the phase that doesn't exist in a bank-to-bank switch, because most standalone banks don't have these controls baked in. Inside an integrated platform like Ramp, they're configuration, not custom build.
The switch is yours to control
The discipline that matters in switching business bank accounts isn't picking a new bank. It's keeping the money moving while you do. Write down every flow, sequence the reroute, and monitor both accounts before you close the old one. Whether you go bank-to-bank or move to an integrated platform, that discipline is what separates a clean switch from a messy one.
Ramp Treasury fits businesses that have outgrown their bank — whether you're opening your first account, consolidating a finance stack post-fundraise, or leaving a bank that doesn't connect cleanly to your other tools.
See how Ramp handles the switch.
1 Ramp Business Corporation is not a bank. Bank deposit services are provided by First Internet Bank of Indiana, Member FDIC.

FAQs
Most teams take 4 to 6 weeks for a traditional bank-to-bank switch. Most of that time is rerouting payroll, vendor payments, customer ACH, and accounting feeds, then monitoring both accounts for 30 days. Switching to a platform that bundles those tools with the operating account is faster because the connections come built in.
There's no hard requirement to keep an external bank account to run day-to-day banking workflows. Some teams keep a legacy bank for edge cases like cash deposits, certain check-deposit workflows, or branch needs.
Yes. Most teams choose a quieter period (post-quarter-end, between fundraises, outside year-end close) to minimize the number of concurrent moving parts. Mid-year is fine if you avoid mid-fundraise, mid-audit, and mid-payroll quarter-close windows.
Notify your lender before you switch. If the loan is on auto-debit, you'll need to update the account on file. If the loan was originated through your current bank as a relationship product, ask whether closing the account triggers any covenants. Most won't. Confirm before you switch.
ACH payments (both inbound and outbound) are tied to your routing and account numbers, not to you as a business. Most won't route automatically to the new account, so each one needs a manual update. Vendors with ACH pull authorization will keep pulling from the old account until you send them updated details. Customers paying you via ACH will keep sending to the old account until you update your invoice templates and notify them directly. Payment processors like Stripe require their own update process and may take a few days to reverify the new account before payouts resume. This is the main reason to keep the old account open and funded for at least 30 days after the switch — ACH stragglers are predictable, and the old account is your safety net while they catch up.
There's no form to file with the IRS specifically for a bank account change, but you do need to update several systems that pull tax payments on your behalf:
- EFTPS (Electronic Federal Tax Payment System) for federal taxes, including payroll and estimated taxes
- State tax portals for state income, sales, and franchise tax
- State unemployment insurance accounts if they auto-debit
- Your payroll provider, which handles federal and state payroll tax deposits on your behalf
The practical rule is: anywhere taxes move automatically, you need to push the new account info before the next scheduled pull.
Don't miss these
“We used to pay up to $20k a year for our AP platform. With Ramp, we’re earning back well over that amount. That's money that belongs to the mission now, not to the back-office software.”
Heidi Coffer
Chief Financial Officer, Boys & Girls Clubs of San Francisco

“We're accountable to our funders, our partners, and the families we serve. That accountability starts with how we manage every dollar. Ramp makes it easy for our team to spend wisely, track in real time, and keep overhead low so more resources reach the families navigating infertility.”
Rachel Fruchtman
CFO, Jewish Fertility Foundation

“Each member of our team has an outsized impact due to our focus on using high-leverage tools like Ramp.”
Lauren Feeney
Controller, Perplexity

“With Ramp, we haven’t had to add accounting headcount to keep up with growth. The biggest takeaway is that instead of hiring our way through it, we fixed the workflow so we can keep supporting the organization as we scale.”
Melissa M.
VP of Accounting at Brandt Information Services

“In the public sector, every hour and every dollar belongs to the taxpayer. We can't afford to waste either. Ramp ensures we don't.”
Carly Ching
Finance Specialist, City of Ketchum

“Compared to our previous vendor, Ramp gave us true transaction-level granularity, making it possible for me to audit thousands of transactions in record time.”
Lisa Norris
Director of Compliance & Privacy Officer, ABB Optical

“We chose Ramp because it replaced several disparate tools with one platform our teams actually use—if it’s not in Ramp, it’s not getting paid.”
Michael Bohn
Head of Business Operations, Foursquare

“Ramp gives us one structured intake, one set of guardrails, and clean data end‑to‑end— that’s how we save 20 hours/month and buy back days at close.”
David Eckstein
CFO, Vanta



