Accept a supplier-account merge without losing credits or payment history

Two records with similar names are candidates for investigation, not permission to combine their balances. This guide begins after the responsible owner has verified that consolidation is appropriate and approved the intended surviving account. The next task is to prove that the ledger and operational references survive the change correctly.

Record the reason for the merge, the entities and sites involved, the old identifiers and the destination identifier. Separate a duplicate record from an acquisition, a new trading relationship or a change in payment instructions. Those events can require different approvals even when the software offers the same merge action.

Oracle's supplier-merge documentation describes different transaction-transfer options and states that a completed merge cannot be undone through that process. The exact behavior depends on the application and version. Establish the supported method, test evidence and recovery arrangements before executing an approved production change.

Create a scope map for invoices, credits, payments, prepayments, purchase orders, receipts and supplier sites. Identify whether historical transactions move, remain under the old record or become accessible through a cross-reference. The acceptance criteria should describe the intended result for each population.

Oracle Financials, for example, distinguishes transferring all invoices from transferring only unpaid invoices. Its unpaid option excludes partially paid invoices and partially applied prepayments. That specific limitation is a reason to inspect transaction states before choosing an option, rather than assume that every open amount will move because its balance is nonzero.

List operational links that users still need after consolidation. Purchasing may need an order's original supplier reference, while a tax or accounting reviewer may need the historical payee information associated with a payment. Do not replace those facts with today's master record merely to make the supplier screen look uniform.

Payment details require their own control. A merge should not become an indirect route for accepting new bank instructions or removing an existing verification requirement. Preserve the approved destination and authorization records through the company's established process.

Extract invoice-level balances for both records at the agreed cutoff, including credit notes and partially settled documents. Save gross invoice amounts, remaining balances, currencies and settlement references. A net supplier balance alone can conceal an omitted credit or a duplicate invoice.

In a hypothetical example, Supplier A's record contains $20,000 of open invoices and $2,000 of open credits, giving $18,000 net payable. Supplier B's record contains $15,000 of open invoices and $1,000 of credits, giving $14,000 net payable. Before resolving any errors, the combined net is $32,000.

Review finds that B's invoices include a confirmed $3,000 duplicate already recorded on A. After the authorized correction, B has $12,000 of invoices less $1,000 of credits, or $11,000 net. The corrected combined balance is $29,000. That is the expected amount to preserve through the merge under the example's assumptions.

Do not accept $32,000 merely because it matches the sum before cleanup, or claim the merge itself recovered $3,000. The duplicate correction and the account consolidation are different changes. Retain both references so the post-change total has an understandable origin.

Compare supplier invoice numbers, dates, currencies, amounts and source evidence across the records. The same number can identify a genuine duplicate, but it can also recur legitimately under different document types or commercial histories. Investigate the actual documents before deciding what should be transferred or corrected.

Oracle notes that its merge will not transfer invoices when the result would create a duplicate invoice on the destination supplier. Treat any rejected transfer as an exception to resolve. Changing an invoice number simply to bypass a collision can preserve a duplicate liability or destroy the link to the supplier's original document.

Keep credits associated with the invoices or arrangements they affect. An open credit may remain valid even when its original invoice is paid, and a credit already applied should not reappear as a fresh deduction on the consolidated account. Review application history, not just the sign of the document.

Check prepayments separately. Their original amount, remaining application and related order can matter to future invoicing. A balance transferred without its application history can later be used twice or fail to offset the invoice it was intended to cover.

Identify invoices selected for payment, payment files generated but not confirmed, bank instructions awaiting execution and payments posted but not yet reconciled. Establish a controlled cutoff with the payment owner. The merge should not create a second eligible copy of an invoice already committed to a payment process.

Suppose $4,000 of the corrected $29,000 payable in the example is marked for an authorized payment that has not yet been posted. The open ledger balance remains $29,000. The amount available for another payment proposal may be $25,000 under the intended reservation, but that is not the same as a settled closing balance.

After the $4,000 payment is confirmed and posted correctly, the remaining payable becomes $25,000, assuming no other activity. Preserve the payment's identity across the supplier change. Otherwise a reviewer may think a $4,000 fall was caused by the merge or may reselect the invoice because its previous reservation is no longer visible.

Coordinate new invoice entry during the change window. Record transactions that arrive after the saved extract and decide how they join the accepted population. A disappearing difference caused by untracked new activity is not a reliable reconciliation.

Compare the post-change open items with the corrected pre-change list. Every invoice and credit should have its expected destination or a documented reason for remaining elsewhere. Reconcile both counts and amounts by currency; an omitted invoice and omitted credit can cancel in the net total.

Inspect partially paid documents, prepayments, held invoices and old credits as deliberate samples. Confirm that settlement history, approvals and attachments remain accessible through the supported system. A supplier summary showing $29,000 does not prove that users can still explain the balance.

Review rejected or skipped records from the merge output. Keep their amounts in the reconciliation until resolved. An application message saying the process completed may mean the job finished running, not that every intended transaction transferred successfully.

Verify that new purchasing and invoicing use the approved account while the old identifiers remain traceable. Inactivation should prevent unintended new activity without making the historical trail inaccessible. Have the operational owners test the actual inquiries they use rather than rely solely on a technical completion log.

Ask the provider for an approved mapping, corrected opening population, transaction-state exceptions, execution evidence and post-change reconciliation. Require it to distinguish identity decisions, accounting corrections and system transfers. Those activities need different evidence and should not be presented as one unexplained cleanup adjustment.

Use an acceptance sample containing a credit on a paid invoice, a partial payment, a prepayment and a document-number collision. The provider should demonstrate how each remains understandable after consolidation. Confirm that it will escalate an ambiguous relationship instead of broadening the merge to make a duplicate count reach zero.

Retain the approved mapping and final reconciliation with the relevant close. The completed assignment should make the supplier account easier to use while preserving the ability to explain who was owed, which documents were settled and how the remaining balance was established.