The buyer created two vendor IDs for the same merchant

Classify the duplication before touching either record

Start with the buyer-side context: two vendor IDs may be true duplicates, separate supplier sites with different purposes, different legal entities, or an old and new record created during a system migration. Oracle E-Business Suite documentation notes that different names for the same supplier can result in separate supplier records, that a supplier merge can update selected associated purchase orders and invoices, and that supplier sites and purposes can differ even within one supplier. Those possibilities are exactly why name similarity cannot settle the question.

This is not the same problem as two provider customer records sharing an email or a storefront naming mismatch. The owner of the record is the buyer’s accounts-payable or vendor-master function. The merchant can supply evidence and request correction, but it should not present its preference as the buyer’s master-data decision.

Map each vendor ID to commercial and payment records

For each buyer vendor ID, record the buyer entity, vendor name as shown, site or address purpose already held, purchasing contacts, purchase orders issued, invoices submitted, approval or dispute history, and remittance references. Keep bank details, tax identifiers and identity documents out of the shared worksheet; note only which authorized record holds them and who confirmed it. Compare invoices to vendor IDs one by one so a paid invoice under one ID is not used to justify moving every document.

If the buyer uses Coupa, its supplier guidance says the buyer manages supplier setup, purchase-order changes, invoice approval and payment. For an invoice and purchase-order amount mismatch, the supplier is directed to request a buyer change order, and invoice comments or history can explain a disputed status. Approval and a payment instruction date still are not confirmation that funds reached the supplier account, so keep remittance evidence separate from portal status.

Decide what evidence would make one ID authoritative

Ask which facts would distinguish the records: same seller legal name used commercially with different buyer sites, same site duplicated by error, or different entities that happen to share a trading name. The answer can change the correction. A duplicate site may need reassignment of open invoices; two entities may need no merge at all; a migration pair may need one surviving ID with historical documents left traceable.

Oracle’s mention that a supplier merge can update selected associated purchase orders and invoices shows that the buyer may have a supported master-data action, but it does not authorize the merchant to choose it. The buyer administrator must decide scope, including which purchase orders, invoices, sites and payment instructions move, remain, or are rejected. Record any buyer instruction and its date rather than relying on a verbal preference from a purchasing contact.

Request a bounded correction and keep trading cleanly meanwhile

Send the buyer a concise request naming both vendor IDs, the associated purchase orders and invoices, the observed remittance or dispute symptoms, and the specific decision needed: surviving vendor ID, treatment of open documents, and where future invoices should be submitted. Use the buyer’s secure supplier channel for anything sensitive. Do not send new bank details or identity documents through an email thread just because the vendor master is being corrected.

Until the buyer confirms, submit only against the vendor ID and instructions the buyer has authorized for that transaction, and flag invoices that cannot be confidently routed. The buyer decides master data and payment routing; the merchant’s finance owner decides whether its receivables records correctly reflect that routing. Legal entity, tax and accounting conclusions belong with qualified review. If the duplication is being caused by how the website or checkout presents the merchant identity to business buyers, describe that narrow concern for a scoped Prism consultation and confirm scope, responsibilities, fees and terms before work.

Buyer vendor-ID comparison

Complete one comparison for the affected buyer. Keep sensitive identifiers in authorized systems and record only their location and confirmation status here. A name match opens the investigation; it does not prove duplication or authorize a merge.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.