In short
- It usually follows a failed or timed-out upload that actually went through.
- Every payment in the run is duplicated, so it shows as a cluster of same-day pairs.
- The bank's confirmation and the ERP payment run should agree before the run is closed.
- Suppliers paid twice this way usually return the money quickly when shown both remittances.
- File naming, upload logs and a check for a file already sent stop it.
How it happens
The most common path is an upload that fails or times out but actually went through. The clerk sees an error, assumes nothing was sent, and uploads the same file again. The bank processes both files, and every supplier in the run is paid a second time.
The second path is a payment run re-created after an error. The first run is approved and released, something looks wrong in the ERP, and a colleague rebuilds the run from the same invoice selection and releases it again. Nobody voids the original, because nobody is sure the original went out. Both files reach the bank.
Because the duplication is at run level, it does not look like one odd invoice. Every payment in the run is duplicated, so it shows as a cluster of same-day pairs: the same supplier, the same amount, the same remittance reference, twice. That pattern is what separates a double-sent run from ordinary duplicate invoice payments, which arrive on scattered dates.
The control that fails is the handshake between the bank and the ERP. The bank's confirmation and the ERP payment run should agree before the run is closed. When the run is closed on the strength of the ERP screen alone, or on the strength of a bank file the clerk believes failed, a second file can sit at the bank unnoticed until suppliers start calling.
Finding it in your payment history
Start with the batch, not the invoice. Pull the payment run in the ERP, then pull the bank statement lines for the same value date and compare them line by line. If the bank shows the run twice, the pairs will line up cleanly: same supplier, same amount, same day, same reference.
Search your payment history for same-day pairs to the same vendor at the same amount. Filter by value date rather than invoice date, because a failed-and-retried upload can land a day or two after the original, and invoice dates will not show it. Check the whole run period, not just the days around the error message.
Watch the vendor record for the quieter signals. A balance that swings to a debit position, an unapplied credit sitting on the account, or a supplier email asking why they received two remittances for one invoice. Suppliers often spot this before the AP team does, because they receive two remittance advices and two bank credits.
If the supplier has already applied the second payment to other open invoices, the vendor record will look clean and the bank will still show the duplicate. That is why the bank-side comparison matters more than the aging report. Reconcile the run to the bank statement, then reconcile the statement to the vendor record, in that order.
Getting the money back
Contact the supplier with both remittances: payment date, amount and reference for each. Suppliers paid twice this way usually return the money quickly when shown both remittances, because the second credit is obviously not against an open invoice and leaving it on the account creates work for them too. Ask for the return to reference the original payment so it can be matched cleanly.
If the second payment has not yet cleared, ask your bank about a recall. Whether a recall is possible, how long it takes and what it costs depends on the payment rail, the bank and the jurisdiction, so treat the timing as variable and confirm the position with the bank rather than assuming. Do not wait for the recall to resolve before contacting the supplier; run both routes at once.
If the supplier will not return the funds, or proposes to offset them against future invoices, get a credit note or written confirmation of the offset and apply it deliberately in the vendor record. Do not net it silently against the next run, because the next clerk will not see why the amount changed. Where the supplier disputes the position, the answer depends on the contract and the jurisdiction; take advice from an adviser rather than deciding it internally.
If repayment is offered over time, compare the proposed terms with your own cost of funds before agreeing. A slow repayment is a financing decision, not just an administrative one, and it should be sized against what the money costs you to be without.
Stopping the next one
Name files so the name carries the run date and a sequence that changes every time the file is generated. A file called the same thing as last week's file invites exactly this error, because a clerk retrying an upload cannot tell from the name whether the bank already has it. Record every upload in a log: file name, time, user and the bank reference returned.
Before any retry, check whether a file has already been sent. That check should be a step, not a memory test: look for a bank acknowledgement against the run reference before pressing upload a second time. A timed-out upload is not a failed upload, and the only reliable evidence is the bank's reference, not the absence of a success message on screen.
Make the bank confirmation and the ERP payment run agree before the run is closed, and have someone sign that agreement. The person who released the file should not be the only person confirming it landed once. Keep the batch view open until the count of payments in the run matches the count of payments at the bank.
For re-created runs, void the original in the ERP before releasing the replacement, and attach the evidence that the original was cancelled. Limit release of bank files to one named person per run, with a second check for any retry. Review same-day pairs to the same vendor weekly as a standing check, so the cluster shows up in your own reporting rather than in a supplier's inbox.
Questions
How do I tell whether my payment file went to the bank twice?
Pull the bank statement lines for the value date and compare them against the ERP payment run supplier by supplier. A double-sent run shows as same-day pairs at the same amount with the same reference. If the bank shows every payment in the run twice, the file was sent twice.
A supplier says they were paid twice. What do I send them?
Send both remittance advices with the payment date, amount and reference for each, and ask them to return the second credit against the original reference. Suppliers paid twice this way usually return the money quickly once they can see both remittances.
Will the bank reverse a duplicate payment for us?
Ask, but do not assume. Whether a recall is possible, how long it takes and what it costs depends on the payment rail, the bank and the jurisdiction. Contact the supplier in parallel rather than waiting on the bank.
Who should approve a re-created payment run?
One named person should release the replacement, after the original run has been voided in the ERP and the cancellation has been evidenced. The clerk who rebuilt the run should not be the only person confirming the original never went out.
Updated Nov 8, 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.