Duplicate vendors in Business Central: finding and merging them

Why duplicate vendors happen

Duplicate vendors usually start with an urgent invoice and a quick search that comes up empty. An AP clerk sets the supplier up again from the invoice or statement, using a slightly different name, address or contact detail. The next invoice lands on the new record. Nothing looks wrong until a statement arrives or a payment runs twice. Re-keyed invoice numbers such as INV-1043 and 1043 are a warning sign: the vendor sent one invoice, but the AP process created two references.

The same supplier gets set up twice when a second location, a new remit-to address or changed bank details are treated as a new vendor rather than an update. Staff turnover makes it worse because the person who knew the original record has left. Statements paid as well as invoices are another common cause: AP clears the statement balance and later pays the individual invoices again. Re-sent payment runs do the same damage when a run is repeated without checking what already posted. In Business Central, duplicate records split the vendor history, so an open credit sits on one record while the invoice it should offset sits on another.

The cost is not only administrative. A duplicate vendor can hold an unapplied credit while the main record shows a past-due balance, which leads to a duplicate payment or a missed discount. When the supplier later issues a credit, AP has to ask for it back and trace which vendor record received it. Duplicate vendors belong in the same review as duplicate payments, overpayments and unapplied vendor credits.

Finding them

Start with the vendor record, not the invoice. Search name variants, remit-to addresses, contact details and payment terms, then compare the results side by side. A vendor record with no activity that shares an address or contact with an active vendor is a candidate. So is a record that carries an open credit while a near-identical record carries open invoices. In Business Central, check the vendor card before you change anything.

Reconcile supplier statements to vendor records on a schedule. Match on vendor, amount and date window rather than invoice number alone, because re-keyed numbers such as INV-1043 and 1043 will not match in a simple search. A payment that matches two open invoices, or a statement balance that clears while the invoices remain open, points to a duplicate payment or a duplicate vendor. Re-sent payment runs look the same: the same amount leaves twice inside a short date window.

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 useful discipline, but 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 catches missing references, not 1043 re-keyed against INV-1043.

Build a duplicate candidate list from three signals: near-identical names and addresses, open credits on a low-activity record, and payments that match more than one invoice. Ask AP clerks to report suspected duplicates, and ask suppliers to confirm which credits they still show as open.

Merging vendors in Business Central

Before you merge, decide which vendor record will survive. Confirm the open invoices, credits, payments and balances on both records, and record the vendor numbers and open items. The merge cannot be undone, so a careful check is worth more than a fast cleanup. If the two records have different remit-to addresses or bank details, confirm which details the supplier currently uses before you choose the survivor.

On the vendor card, Merge With opens the Merge Duplicate page, where the duplicate can be removed or renamed. The action needs the MERGE DUPLICATES permission set. If you do not have it, ask the person who administers permissions; do not work around it by creating another vendor record. Decide in advance whether the duplicate should be removed or renamed, and tell the AP team which vendor number will remain in use.

A worked situation: one vendor record holds invoice INV-1043 and another holds the same supplier's invoice 1043. The supplier statement shows one invoice open, but the AP records show two. Merge the records in Business Central after you confirm which record holds the payment and which holds the credit. If the payment sits on the record you plan to remove, stop and resolve that first. After the merge, check that the surviving vendor record shows the correct open balance and that the duplicate no longer appears in your working lists.

Do not use a merge to hide a payment problem. If a duplicate payment has already left, contact the supplier and ask for a credit or repayment. Keep the vendor records, invoice references, payment dates and statement line. Merge only after the open items are understood.

Keeping the vendor list clean

New vendor setup is where the cycle starts. Search for the supplier before creating a record, using the name on the invoice, the remit-to address and the contact details. Require a second person to approve new vendors when bank details differ from an existing record. A simple rule helps: one vendor record per remit-to address, with name variants recorded as notes rather than new records.

Run a periodic vendor master review against supplier statements. Match vendor, amount and date window, and look for open credits that have not been applied. Re-sent payment runs and statements paid as well as invoices belong on the same review. When a supplier asks for a credit back, check for a duplicate vendor as well as a duplicate payment.

After any merge, update recurring invoice templates, payment instructions, statement contacts and the AP team's working lists. Confirm with the supplier which vendor record they will use for future invoices. If a credit is still open, ask the supplier for a credit note or written confirmation of the balance before you apply it.

Use Ext. Doc. No. Mandatory in Purchases & Payables Setup to require a supplier invoice number on every posted invoice and credit memo, but do not treat it as a duplicate control. Microsoft's documentation notes that Business Central doesn't check whether external document numbers are unique. Pair the required field with statement reconciliation, a duplicate candidate list and a named owner for the vendor master.

Questions