Finance Index
How do you switch corporate card providers without breaking everything?
Reference guide to card program migration switching providers, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.
Card migration is a project, not a swap: plan for recurring vendor charges sitting on old card numbers, ERP feed remapping, open disputes, in-flight transactions, and rebate true-ups. A realistic migration runs weeks to a few months depending on card count and subscription sprawl, and it succeeds or fails on one thing - whether you have an inventory of what's billing to the old cards before you cancel them.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Corporate card policy | Card migration is a project, not a swap: plan for recurring vendor charges sitting on old card numbers, ERP feed remapping, open disputes, in-flight transactions, and rebate true-ups. | Keeps vendor records and payment decisions reliable. |
| Card control | The predictable failures: recurring subscriptions charged to old card numbers stop paying and services lapse, the ERP feed mapping breaks. | Keeps accounting records aligned with the ERP. |
| How do we migrate | Build the inventory first - pull 12 months of recurring charges per old card to catch annual renewals - then reissue per-vendor (ideally merchant-locked) numbers, update card-on-file at each merchant before cancelling the old card, and verify the first successful charge on. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Old and new programs run | Yes, for a bounded overlap - long enough to migrate every recurring charge and catch trailing credits (often one to two statement cycles), short enough that you're not policing two live programs indefinitely. | Helps finance decide what to do next. |
| How do we close out | Run a final statement reconciliation, hold the account open for trailing refunds and merchant credits, settle the final rebate, confirm zero recurring activity remains, then retire the GL clearing account once it returns to zero. | Keeps accounting records aligned with the ERP. |
What breaks when you switch card providers?
The predictable failures: recurring subscriptions charged to old card numbers stop paying and services lapse, the ERP feed mapping breaks because the new provider's file format differs, open disputes on the old program need tracking to resolution, in-flight (authorized-but-unposted) transactions land after cutover, and the final rebate has to be trued up against the old program's tiers. Each is manageable with a checklist; together, unplanned, they're a bad month.
How do we migrate hundreds of subscriptions and card-on-file merchants without service interruptions?
Build the inventory first - pull 12 months of recurring charges per old card to catch annual renewals - then reissue per-vendor (ideally merchant-locked) numbers, update card-on-file at each merchant before cancelling the old card, and verify the first successful charge on the new number. Cancel the old card only after every recurring charge has demonstrably moved.
Should old and new programs run in parallel during migration?
Yes, for a bounded overlap - long enough to migrate every recurring charge and catch trailing credits (often one to two statement cycles), short enough that you're not policing two live programs indefinitely. A defined cutover date per card prevents the overlap from becoming permanent confusion about which card to use.
How do we close out the old program cleanly?
Run a final statement reconciliation, hold the account open for trailing refunds and merchant credits, settle the final rebate, confirm zero recurring activity remains, then retire the GL clearing account once it returns to zero. Closing too early strands refunds and orphans late credits with nowhere to post.
What should make US actually switch vs renegotiate?
Price the switching cost honestly - migration labor, feed rework, subscription re-pointing, service-interruption risk - against the real gain. A rebate or feature improvement has to clear that bar, and incumbents often match a credible switch threat at renewal, so get the competing offer before deciding the incumbent can't improve.
Mid-migration, some employees have two active cards and are using the wrong one - how do we enforce cutover discipline?
Set a hard per-employee cutover date, suspend (don't just deprioritize) the old card on that date, communicate which card is live for whom, and monitor the old feed for stragglers. Two live cards with no enforced switch date is how a "two-week overlap" becomes a six-month parallel program.
Stampli perspective
Stampli's position is that payment controls work best when the payment is tied to the invoice, the vendor record, and the approval trail that made the liability payable. That connection gives finance a clearer way to review who approved the spend, which payment method is being used, and what changed before money moves.