Duplicate payments in Business Central: what it checks and what gets through

What Business Central checks for you

Turning on Ext. Doc. No. Mandatory in Purchases & Payables Setup means a purchase invoice or credit memo cannot be posted without the vendor's invoice or credit memo number. That is a presence check at posting. It forces an entry in External Document No., but it does not ask whether the same number has been used before.

Microsoft's documentation notes that Business Central doesn't check whether external document numbers are unique, so making the number required does not by itself catch a duplicate. The control depends on what the AP clerk types and what review happens before posting. A required number is useful discipline, not a duplicate prevention system.

For visibility, the Aged Accounts Payable report (322) shows open vendor balances by age. The Vendor - Detail Trial Balance report (304) lists each vendor's ledger entries for a period. Both help review open and posted activity, but neither is a duplicate detector. They show what was recorded, not whether two records describe the same invoice.

What gets through

The most common failure is a re-keyed invoice number. One record carries INV-1043 and another carries 1043. If Ext. Doc. No. Mandatory is on, both records satisfy the requirement. Business Central does not check whether the two external document numbers are unique, so the difference between the strings is enough to get past the only built-in control. A clerk looking at a list can also read them as two invoices.

The same supplier set up twice is another route. A payment posted under one vendor record and a second payment posted under the other can look like two vendors rather than one supplier paid twice. A report grouped by vendor will not necessarily show the connection. The duplicate is easier to see when you compare supplier name, remittance details and external document number rather than vendor code alone.

Statements paid as well as invoices are a third route. The monthly statement summarizes invoices that are already in the ledger, but AP enters the statement as a new invoice. The statement reference may not match any invoice number, so a uniqueness check on External Document No. would not catch it even if one existed. Re-sent payment runs are a fourth route: a run is repeated or re-released after a change, and the same invoices go out again as new payment entries.

Credit memos add a related gap. If a credit memo is not applied, or is entered with a different external document number from the invoice it relates to, the payment side can still go out in full. None of these failures requires a product defect. They require a gap between a required field and a real matching process.

Finding duplicates already paid

Start with the Vendor - Detail Trial Balance report (304) for a period that covers the payment. It lists each vendor's ledger entries for the period. Export the entries and keep vendor, amount, posting date and External Document No. together. The supplier invoice number in the export is often the External Document No. Build a normalized key that turns INV-1043 and 1043 into the same value, for example by ignoring a prefix, spaces, punctuation and leading zeros.

Match on vendor, amount and a date window. Do not match on invoice number alone, because duplicates often carry different strings. Do not match on amount alone, because the same amount can recur legitimately. Flag pairs where the vendor is the same, the amount is the same, the normalized external document numbers agree and the entries fall inside the date window. Then check the invoice copy and payment record before calling it a duplicate.

Use the Aged Accounts Payable report (322) alongside the detail report. It shows open vendor balances by age, which helps spot balances that look doubled or items that should have cleared. Reconcile vendor statements to open invoices, not just to the closing balance. If a statement includes an invoice already paid, ask the supplier for a credit back and keep a record of the request.

When the same supplier is set up twice, repeat the match across both vendor records using supplier name and remittance details. A duplicate that crosses two vendor records will not appear in a single-vendor review. Work with the controller on whether to request a refund, apply a credit or offset a future invoice. The earlier the duplicate is identified, the more options remain.

Preventing the next one

Turn on Ext. Doc. No. Mandatory in Purchases & Payables Setup if it is not already on. It prevents posting a purchase invoice or credit memo without the vendor's invoice or credit memo number. Because Business Central doesn't check uniqueness, pair it with a standard entry rule. Choose one convention for invoice numbers and enforce it, so INV-1043 and 1043 are not both treated as acceptable versions of the same invoice.

Before posting, check the vendor's existing entries in Business Central. The Vendor - Detail Trial Balance report (304) for a recent period can show whether the external document number is already recorded. For suppliers with repeated statements or many credits, compare the invoice to the statement before posting. Keep one vendor record per supplier and review new vendor requests against existing names and remittance details.

Control payment runs at the run level. Reconcile the selected invoices to the run before release, and after any re-run compare the new run with the prior run. Do not treat a re-sent run as a fresh approval. For credits, require the credit memo to reference the original invoice and apply it before the next payment.

Reconcile statements every month and treat the statement as a summary, not an invoice. Ask suppliers for credits back when a duplicate is confirmed, and track the credit until it is applied or refunded. A duplicate caught before payment is a correction. One caught after payment becomes a recovery task.

Questions