How to Merge Duplicate Vendor and Customer Records

Start with a review list, not a bulk merge. Compare legal names, trading names, GSTINs, PAN where held, addresses, contact details and existing bills. Treat spelling differences, abbreviations and extra spaces as clues. A similar name alone is not enough to approve a merge.

Ask why each record exists. One may belong to a branch, an earlier business arrangement or a separate registration. Compare the records with the underlying invoices and party details rather than relying only on what someone typed into the master.

Compare the GSTIN on each record with the relevant invoices and verify registration details through the official GST portal. Resolve conflicting identifiers before merging. Do not assume a matching PAN makes different GST registrations interchangeable.

Choose the surviving record deliberately. Prefer the record with verified identity details, established document links and the correct registration. Do not automatically choose the oldest entry, the tidiest name or the record showing the largest balance.

• ✓Confirm the legal name, trading name and registration details to retain.
• ✓Check billing and delivery addresses, contact details and agreed payment terms.
• ✓Verify bank details through your usual approval process; merging records must not approve a bank-detail change.
• ✓Identify connections to purchasing, sales, collections and other connected systems.
• ✓Record both old party codes, the surviving code, the reason for merging and the approver.

Keep alternative names as searchable references where supported. The aim is to help staff find the correct party without recreating the retired record.

Choose a quiet period and pause entries against both records. Take a complete backup using the software's supported method and confirm the restore procedure. Keep exports as comparison evidence, but do not assume a spreadsheet export can restore attachments, allocations or transaction links.

1. Save each party ledger and its opening and closing balances.
2. Export open invoices, bills, credit notes, advances, unapplied receipts and payments.
3. Save receivable or payable ageing reports with a common cut-off.
4. List outstanding orders, delivery documents, returns and disputed items.
5. Record attachment counts and check that supporting files can be opened.
6. Have another authorised person review the proposed survivor, unresolved differences and backup arrangements.

If fresh transactions arrive during the review, refresh the comparison before proceeding. For the wider control routine, read the finance operations guides and the monthly bank reconciliation guide.

Reconcile individual open items before comparing totals. Identify duplicate bills, missing allocations, advances and disputed amounts. Do not delete a transaction merely because it appears under a duplicate party record; first establish whether the transaction itself was duplicated.

Illustrative example: one vendor record contains an unpaid bill of Rs 12,500. A second contains another unpaid bill of Rs 7,500 and an unapplied payment of Rs 5,000. The combined net payable is Rs 15,000, but that total alone does not prove the merge is correct. Both bills and the payment must remain traceable, with any allocation supported by the actual payment details.

Keep customer receivables and vendor payables separate during this exercise. Do not net one against the other simply because the party supplies to you and buys from you. Seek a separate accounting review for any proposed settlement or adjustment.

The receivables collection routine and weekly supplier payment run guides provide related checks for following up and settling open items.

Check the instructions for your exact product and version. Establish whether its merge moves transactions, changes only future use or leaves separate histories. Confirm whether it can be reversed, which fields it overwrites and how connected systems handle the retired code.

• Confirm that original document numbers, dates and tax details remain intact.
• Check links between orders, invoices, credit notes, receipts and payments.
• Check attachments, notes, approvals and the available change history.
• Confirm what happens to bank matching and payment allocations.
• Test the result on a restored copy where supported, including opening linked documents.

If preservation cannot be demonstrated, keep the historical record and prevent new entries against it where supported. Direct future use to the verified record. Ask the software provider how to retain access to history without forcing an unsupported merge.

Repeat the saved reports with the same cut-off and compare them. The surviving party's net balance must reconcile to the pre-merge balances, while the overall receivable or payable total must remain unchanged. Investigate every unexplained difference before resuming normal entry.

• ✓Compare every open item, including advances, credits and unapplied amounts.
• ✓Check ageing dates and disputed-item notes.
• ✓Open documents from both former records and follow their linked receipts or payments.
• ✓Open supporting attachments and confirm access to historical entries.
• ✓Check that connected systems use the surviving code and staff cannot casually recreate the duplicate.
• ✓Record the review result and retain the old-to-new code mapping with the comparison reports.

Avoid bulk merging by name, treating shared contact details as proof, checking only the net balance or deleting old records to make the list look clean. A tidy master is useful only when its history remains reliable.

Do not combine this cleanup with unexplained write-offs, opening-balance adjustments or bank-detail changes. Review those separately. Where identity, registration or document ownership remains uncertain, leave the records separate and assign someone to resolve the specific question.