Switching AP Automation Providers: A Migration Checklist
When switching AP automation providers, move the vendor master and bank data first, then open invoices and scheduled payments, card enrollment status, approval rules and history. Run both systems in parallel for a full payment cycle, then exit the old contract.
The order matters because the risks stack. A bank account entered wrong in week one becomes a misdirected payment in week three, and a payment scheduled in both systems becomes a refund you spend a month chasing. Choosing the new platform took a quarter of meetings. The move itself has to be planned just as carefully, and it usually gets a fraction of the attention.
Key Takeaways
Verify every supplier bank account as it's loaded into the new system, because fraudsters watch for transitions.
Freeze scheduled payments in the old system before the new one goes live, so no invoice can be paid twice.
Virtual card numbers don't transfer between providers, so card-enrolled suppliers need new cards and a clear message.
Pull the full payment history and audit trail before you lose access, including what you'll need for 1099s.
Settle the exit terms with the outgoing provider early, while the notice window is still open.
When does switching AP automation providers make sense?
Switching makes sense when the current provider can't pay your suppliers the way they accept payment, can't hold the controls your auditors expect, or leaves supplier enrollment to your staff. A dated interface on its own is rarely worth a migration.
Most switches start with outgrowth. A platform built for a small team runs out of room on entities, approval rules or payment rails, and the finance team starts reading lists of Bill.com alternatives or Tipalti alternatives. Others come from consolidation, where a company running separate tools for invoices, cards and checks decides that payment vendor consolidation is worth a single migration.
My view is that the case for switching should be written in payment terms. If you can't say which suppliers will be paid differently, which control gets stronger or which hours come back to your team, the switch is probably a software preference, and preferences don't survive a hard cutover month.
What should you settle before you announce the switch?
Settle the timing, the notice date on the old contract and your export rights before anyone outside finance hears about the switch. Your leverage with the outgoing provider drops the day it knows you're leaving.
Timing has two hard edges. One is the renewal date, because Gartner research published in October 2025 found enterprise SaaS costs often rise 10% to 20% or more at renewal, and missing the notice window can lock you into another term at a higher price. The other is year-end. The IRS requires Form 1099-NEC by January 31, so a cutover in December puts your migration and your 1099 run in the same six weeks. Start in the spring or early fall if you can.
What do you move, and in what order?
Move data in the order a payment depends on it, starting with suppliers and bank details, then the invoices and payments in flight, card enrollment, approval rules, and finally the history. Each step should be verified before the next one starts.
Data | Why it matters | How to verify it |
Vendor master and bank details | Every payment depends on it, and it's the fraud target | Reverify bank accounts out of band and match TINs before the first payment |
Open invoices and scheduled payments | The source of missed and duplicate payments | Reconcile counts and totals between systems on cutover day |
Card enrollment status | Card numbers don't move, and rebates depend on enrollment | List every card-paid supplier and its new card status |
Approval rules and user roles | Controls lapse if roles are rebuilt loosely | Compare the old and new approval matrix line by line |
Payment history and audit trail | Auditors, 1099s and disputes all need it | Export, store and test-read the files before access ends |
Verify each step before starting the next.
Step 1: Vendor master and bank data
Clean the vendor master before you load it, then reverify every bank account as it enters the new system. Duplicates, inactive suppliers and missing tax IDs are easier to fix once than to migrate twice.
Bank data deserves the most care, because a migration is exactly the moment a fraudster would choose. According to AFP's 2026 Payments Fraud and Control Survey, 74% of organizations were affected by business email compromise in 2025. The FBI's 2025 Internet Crime Report counted 24,768 business email compromise complaints and $3,046,598,558 in reported losses. A supplier email saying "we hear you're changing systems, here are our updated details" is the kind of request that slips through in a busy cutover week.
Nacha's fraud monitoring rules, phased in on March 20 and June 19, 2026, add a formal reason to be careful. They require risk-based processes to catch payments authorized under false pretenses, which Nacha defines to include misrepresenting "the ownership of an account to be credited." Use a written process for vendor bank verification on every account you load, and run TIN matching on the file before go-live. Don't trust the old system's bank data just because it paid last month.
Step 2: Open invoices and scheduled payments
Pick a cutover date, stop scheduling payments in the old system before it, and move every open invoice with its approval status intact. Anything already scheduled in the old system should either run there or be cancelled there, never both.
The duplicate payment is the classic switching failure. It's a common failure in go-live week. The old platform's scheduled ACH goes out, the new platform's first run pays the same invoice two days later, and getting the money back takes weeks of calls. Turn on duplicate payment detection in the new system from the first run, and update your positive pay files with the bank if the new provider prints checks from a different account or check range.
Step 3: Card enrollment status
Card enrollment doesn't transfer, because virtual card numbers belong to the issuing provider. Every supplier you pay by card today will need a new card arrangement, and some will need to be asked again whether they accept cards at all.
Start with a list of card-paid suppliers that records, for each one:
Annual card spend
How the supplier receives card details today
Who on the supplier's side processes card payments
Whether the supplier charges a card acceptance fee
High-spend suppliers deserve a personal call, since they're where the rebate sits and the ones most likely to notice a change in how they're paid. Vendor enrollment for virtual cards works the same way the second time, but suppliers are less patient with it. Corpay's fully managed AP has its own team contact and enroll suppliers during a switch, which keeps that outreach off your AP staff's desks. Ask the incoming provider how rebate tiers are set in year one, since your old card volume won't automatically count.
Protect cash flow with modern AP
Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.
Download the whitepaper
Step 4: Approval rules and user roles
Rebuild the approval matrix from your written policy, not from what the old system happened to enforce. Migrations are a good time to find out the two have drifted apart.
Map every role in the old system to a role in the new one and check that no single user can create a supplier, approve an invoice and release the payment. Segregation of duties in AP is easy to weaken during setup, when the implementation team gives one administrator broad rights to move faster. Remove those rights before the first live payment.
Step 5: Payment history and the audit trail
Export the full payment history, approval records and audit logs before your access to the old system ends, and test that someone can actually read the files. A history you can't open is no history at all.
Your auditors will want evidence that controls operated for the full year, across both systems. Ask the outgoing provider for its latest SOC 1 report too. The AICPA describes a SOC 1 as "an examination of controls at a service organization that are likely to be relevant to user entities' internal control over financial reporting," and it covers the months the old provider was running your payments. Keep the exports next to your AP audit trail from the new system.
Tax reporting is the other reason. A mid-year switch splits each supplier's payments across two systems, so 1099 totals have to be combined. The IRS's current instructions for Forms 1099-MISC and 1099-NEC set the reporting threshold at $2,000 for tax years beginning after 2025 and require e-filing once you have 10 or more information returns in the aggregate. They also note that card payments are reported on Form 1099-K by the payment settlement entity, not on 1099-NEC, so suppliers that moved between card and ACH during the year need careful handling.
How do you run both systems in parallel?
Run both systems for at least one full payment cycle, and hold to the rule that each invoice belongs to exactly one system. Before the new system pays any imported invoice, freeze or cancel that invoice's scheduled payment in the old system and confirm the cancellation. Cut over by supplier group or by payment rail, and reconcile both systems against the bank every day of the overlap.
The most common split is by rail. ACH tends to move first because it carries most of the volume and the dollars, with Nacha reporting close to 8.1 billion B2B payments on the ACH Network in 2025 and the Federal Reserve finding ACH reached almost three quarters of noncash payment value in 2024. Card suppliers follow as they're re-enrolled. Checks often go last, and they won't go away entirely. AFP's 2026 survey found 72% of check users plan to keep writing checks, with 68% of those citing vendor requirements, so the new provider has to handle the paper too.
How long should the parallel run last?
The parallel run should last one full payment cycle at minimum and one month-end close if you can manage it. A weekly payer can finish in two to four weeks; a monthly payer needs longer.
Ending the run is a decision, not a date. Close it when the new system has paid every supplier group at least once, the bank reconciliation ties out for the whole period, and the month-end close ran on the new system's postings without manual fixes.
How do you keep suppliers from being paid twice?
Keep suppliers from being paid twice by locking each invoice to one system and checking for duplicates across both. In practice that means these controls:
A cutover date after which the old system can't schedule new payments
A hold on every scheduled payment in the old system, cancelled and confirmed before the new system pays the same invoice
A shared invoice list showing which system owns each open item
Duplicate checks on invoice number, amount and supplier across both systems
A daily reconciliation of both systems against bank activity
One named person who approves any exception to the ownership rule
How do you exit the old contract cleanly?
Exit cleanly by giving notice inside the contract's window and taking a full export before cutover, verified against the old system, because the new provider needs that data during the parallel run. Then let every scheduled and in-flight payment in the old system settle or be cancelled, stop processing and intake there, and get written confirmation that both have stopped. Only then take a final delta export, reconcile the final position, collect earned rebates, and authorize the provider to delete your data.
The exit is where an ERP migration and an AP provider switch differ most. In an ERP migration, you usually keep the AP layer and change the ledger underneath. In a provider switch, the ledger stays and a contract ends, which brings a counterparty with its own interests into the project. Some providers make leaving easy. Some don't, and you won't know which until you ask for the export.
What should you request from the outgoing provider?
Request everything you'll need to pay, audit and report without them, in writing and before the notice period ends.
A full pre-cutover export of suppliers, invoices, payments, approvals and audit logs in a standard format, verified against the old system before the parallel run starts.
Supplier bank and enrollment data, with the date each record was last verified.
Confirmation of any card rebates earned and the date they'll be paid.
Transition support for a defined period, at an agreed rate.
Confirmation that every scheduled and in-flight payment has settled or been cancelled, with a final delta export and a final reconciliation report.
A certificate of data deletion, issued only after the delta export is confirmed and the final reconciliation ties out.
What do suppliers need to hear during the switch?
Suppliers need to know what changes for them, when it changes and how to confirm a request is real. Tell them before the first payment arrives from the new system, not after.
A short notice should name the go-live date, any change in remittance format or payment method, and how they'll receive card details if they're paid by card. It should also say plainly that you'll never ask them to change bank details by email, and that they should call a known number if anyone does. Suppliers paid by check will want to know whether the payer name or check stock changes, because a different-looking check gets held. Corpay pays suppliers by virtual card, ACH or check from one approval flow, which keeps the message simple when every payment method moves at once. The internal side matters as much, and AP automation change management covers bringing your own team along.
Switch to Corpay AP automation with a managed cutover
A switch puts the most strain on supplier outreach, bank verification and payment delivery, and those are the parts a fully managed AP provider takes on.
Corpay AP automation connects through 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central and Acumatica, so your ledger stays where it is. Corpay's team enrolls and follows up with suppliers, then pays each one by virtual card, ACH or check. Card payments use single-use virtual cards and earn rebates, with Corpay paying its customers more than $800M in rebates each year. AP teams save about 40% of the time they spend on processing, and most customers are live in weeks.
Frequently Asked Questions
How long does it take to switch AP automation providers?
Most switches take a few weeks to a few months, depending on supplier count, ERP complexity and how many suppliers need re-enrollment. Plan for setup, data loading, at least one full payment cycle in parallel and a clean month-end close.
Do suppliers have to re-enroll when you change AP providers?
Card-paid suppliers do, because virtual card numbers belong to the issuing provider. ACH suppliers usually don't need to re-enroll, but their bank details should be reverified before the new system pays them.
Can you run two AP automation systems at the same time?
Yes, during a parallel run. The rule is that each invoice belongs to exactly one system, with a cutover date for new scheduling and daily reconciliation of both systems against the bank.
What happens to 1099 reporting if you switch mid-year?
Each supplier's payments are split across two systems, so you'll need to combine totals from both. Export the old system's payment history before access ends, and keep card payments separate, since those are reported on Form 1099-K.
What is the safest way to change how you pay suppliers?
Verify any new bank details through a known phone number, never through the email that requested the change, and require a second person to approve the update before any payment is released.
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.