In short
- Open bills migrated to the new system and also paid from the old one in the last runs are the main risk.
- Vendor records are often re-created, so duplicate vendors appear at the same time.
- Payment histories from both systems need to be compared for the months around cut-over.
- Freezing payment runs in the old system on a set date closes the window.
- Duplicate-bill checks in the new ERP start without history, so they miss invoices paid before go-live.
How it happens
The risky window opens when open bills are migrated to the new system but the old system still runs. AP keeps paying from the old system because that is where the vendor record and the payment history live. The new system sees the same bill as open because it has no payment history yet. A packaging supplier with an open invoice can end up paid from both sides in the same week. The duplicate is not a data entry slip. It is the migration design.
Vendor records get re-created during the migration, often by a different team or a script. The same supplier can appear as two vendor records with slightly different names, a new remit-to address, or a new vendor ID. AP pays one record from the old system and the other from the new. The duplicate vendor hides the duplicate payment because the invoice numbers may not line up on a report. A freight broker with a name change during the migration is a familiar version of this.
Duplicate-bill checks in the new ERP start without history. They can catch a bill entered twice in the new system, but they cannot catch a bill paid before go-live in the old system. That gap is the point. If AP treats the new check as proof that nothing was missed, the old-system payments never get compared. The mistake is treating go-live as the start of history when payables need the months around cut-over.
Finding it in your payment history
Pull the payment history from both systems for the months around cut-over. Do not just look at open bills. Paid invoices are where duplicate payments hide. Line the histories up by vendor and invoice number. Where the invoice number changed during migration, match on vendor and payment date, then check the amount by eye. A spreadsheet is fine. The point is to compare, not to trust one system's report.
Start with the last payment run in the old system and the first payment run in the new system. Then work outward. Look for the same supplier paid from both systems, even when the invoice numbers differ. A packaging supplier paid once from the old system on the final run and once from the new system on the first run is the pattern to hunt. Do the same for the duplicate vendor records created during migration.
Ask the AP clerk who ran the old system to walk the final runs. They know which vendors were paid by hand, which bills were on hold, and which payments were reissued after a failed transmission. Those manual fixes are where duplicates survive. A payment that failed in the old system and was reissued in the new one can look like a single payment in each system until you read the notes.
Write down every match you find with the vendor, invoice number, both payment dates, and the payment method. You need that detail for the vendor conversation and for the controller. Keep the list short and factual. Do not combine the duplicate vendor cleanup with the duplicate payment recovery. They are different jobs and they need different owners.
Getting the money back
Contact the supplier with both payment records. Say what you see: the invoice was paid from the old system and again from the new one. Ask for a refund or a credit against the next bill. Keep the message plain and attach the payment detail. Most suppliers want to resolve it because their own records show the double payment.
If the supplier offers a credit, get it in writing and apply it before the next payment run. Track unapplied vendor credits like cash. A credit that sits in the vendor record is easy to lose after a migration, especially if the vendor record was duplicated. Put the credit on the same vendor record that will receive the next invoice.
If the supplier nets the duplicate against an open invoice without telling you, the payment history will look odd. Ask for a statement and reconcile it to both systems. If the supplier refuses or the amount is disputed, pass it to the controller with the payment evidence and the contract terms. How far back you can recover depends on the contract and the jurisdiction, so take advice where the amount matters.
Do not reissue a payment because a vendor says it never arrived. Check both systems first. A missing payment in the new system may be a payment that went out from the old one. Reissuing before you check creates the second duplicate.
Stopping the next one
Freeze payment runs in the old system on a set date before go-live. Write the date down and give it to everyone who can release a payment. The freeze must include manual payments and one-off checks, not just the scheduled run. If the old system stays live for reporting, that is fine. It just cannot pay.
Reconcile every open bill before cut-over. For each bill, decide: paid in the old system or migrated to the new system. Then prove it. A bill that is marked open in both systems is the one that gets paid twice. Assign one owner for this reconciliation. Split ownership between AP and IT is how the gap opens.
Clean up duplicate vendor records before go-live, not after. Compare the vendor list from both systems on name and remit-to address. Where a supplier has a pair of records, pick the record that will carry the open bills and the payment history. Close or block the other one. If you cannot merge them, note the pair on a watch list and check both records in the first payment runs.
Feed the new system's duplicate-bill check with paid invoice history from the old system, or run a manual comparison until the history is there. The new check starts empty, so it cannot see pre-go-live payments. After the first new payment run, compare it to the last old run. Do that again after the next run. The repeat is what catches the late duplicate.
Questions
How soon after an ERP migration do duplicate payments show up?
They often show up in the first payment runs after go-live, when open bills from both systems are still live. Some appear later, when a supplier credit or a manual payment is reissued. Compare the last old runs with the first new runs and keep checking until the old system is frozen.
What should I check first for duplicate payments after go-live?
Start with the last payment run from the old system and the first run from the new system. Look for the same vendor paid from both, even if the invoice numbers differ. Then check the duplicate vendor records created during migration.
Can I rely on the new ERP's duplicate invoice check?
No. The check starts without payment history, so it misses invoices paid in the old system before go-live. Use it as one control, then compare both payment histories around cut-over by hand. Backfill the paid invoice history when you can.
A vendor says it was not paid. Should I pay it again?
Check both systems before you reissue anything. The payment may have gone out from the old system and not appear in the new one. If it was paid twice, ask for a refund or a credit and keep the evidence.
Updated Nov 9, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.