Duplicate payments in Xero: what it checks and what gets through

What Xero checks for you

Xero flags possible duplicate bills and credit notes when the Contact, Reference and Total all match. That is a narrow check: the supplier or customer record, the reference text and the total must line up. When you export bill data, the supplier invoice number sits in the Reference field. A possible duplicate appears in a notification or through the Review duplicate bills option, and you choose to keep, void or delete it.

The check does not block saving. A bill that Xero flags can still be saved and later approved, so the flag is a prompt for review, not a lock. Bills created from the same repeating template are not compared. If your AP team uses a template for a regular bill, add a manual check for that bill.

The flag also covers credit notes. Review both the bill side and the credit note side before you decide. Xero is telling you that three fields match; it is not telling you whether the charge is valid, whether the supplier issued a credit, or whether a payment already went out. Keep the decision with the AP person who has the supplier history.

What gets through

One common gap is a re-keyed supplier invoice number. A supplier sends INV-1043 on the first pass, and one clerk enters INV-1043 in the Reference field. Later another clerk enters the same invoice as 1043, or with a different prefix or spacing. The Contact and Total can match, but Reference does not, so the Xero condition is not met. Treat INV-1043 and 1043 as the same supplier invoice when you review.

A second gap is the same supplier set up twice. If the vendor record is duplicated under two contact records, the Contact field differs on the two bills. Reference and Total can match without a Xero flag. This is why vendor master cleanup belongs in AP: compare supplier name, remit address, bank details and tax identity before creating a record, and merge or block duplicates in your ERP.

A third gap is paying a supplier statement as well as the invoices. The statement reference is not the same as the invoice reference, and the statement total may be a net balance, so the duplicate check may not see a match. AP then pays the statement and later pays the same bills again. Reconcile the statement to open bills and credits before releasing payment. A fourth gap is a re-sent payment run: the bill record is not duplicated, so a duplicate bill flag cannot catch the second payment. Compare each run with the prior run by vendor, amount and a date window.

Finding duplicates already paid

Start with the reports that show exposure. The Aged Payables Detail report, called Accounts Payable Aging Detail in the US edition, and the Aged Payables Summary show what is owed by supplier and age. The Payable Invoice Detail report lists bills with their amounts and payments. Use them to narrow the supplier list, then look for repeated amounts and repeated references. When you export bill data, the supplier invoice number sits in the Reference field, which gives you the text to compare.

Match on vendor, amount and a date window rather than on invoice number alone. Normalize the Reference values before comparing: INV-1043 and 1043 are the same supplier invoice, and spacing or prefix changes are entry noise. A date window should cover normal entry lag; a duplicate entered weeks later will not sit beside the original. Check the vendor record for a second contact record, and check whether a statement payment overlaps with bill payments.

Statement reconciliation is the practical test. Put the supplier statement beside the open bills and credits for that supplier. If the statement shows a balance cleared but your records show unpaid bills, or the reverse, investigate before paying. Paying a statement plus the underlying invoices creates a credit due from the supplier. Ask the supplier for a credit back or refund, with the payment date, amount, reference and remittance advice. Record the credit against the vendor in your ERP and keep the supplier confirmation with the payment evidence.

Preventing the next one

Keep the vendor master clean. Create one vendor record per supplier, check for an existing record before adding a new one, and review names, remit addresses and bank details. A duplicate contact record defeats the Xero Contact match. Train AP to enter the supplier invoice number exactly as printed in the Reference field, and use one team convention for prefixes, spaces and leading zeros. INV-1043 and 1043 should be treated as the same invoice before any bill is approved.

Review the duplicate prompts. Because Xero does not block saving, a possible duplicate can sit in the ledger unless someone reviews the notification or uses the Review duplicate bills option and chooses keep, void or delete. Do that review before payment, not after month end. For bills created from the same repeating template, add a manual comparison because those bills are not compared. Review credit notes on the same schedule.

Control payment runs. Before releasing a run, compare it with the prior run by vendor, amount and a date window, and check that a re-sent run is not paying bills already paid. Reconcile supplier statements before payment, and clear statement balances against bills and credits rather than paying both. Use the Payable Invoice Detail report to see bills with their amounts and payments when a supplier query arrives. Ask suppliers for credits back when a duplicate is confirmed, and record the credit promptly in your ERP so the next run does not pay it again.

Questions