Prevent and Resolve Duplicate Transactions

Prevent and Resolve Duplicate Transactions
Overview
This guide will help you prevent duplicate entry and compare and confirm suspected duplicates without deleting audit history.
If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.
One valid business event remains with an auditable correction chain for any duplicate.
Who can do this
You need access to Source inquiry access; correction/reversal requires transaction-specific authority.
Before you start
Have source reference, party, amount, date/time, external ID, terminal/user, response/log, and expected record count.
Before saving, check that the correct company is open and that you have permission to complete this task.
Where to find it
Open the relevant module inquiry and linked external/history reports.
Prevent and Resolve Duplicate Transactions
Step 1: Search by stable document/external/reference ID before entry or retry
Step 2: After timeout, treat outcome as unknown rather than failed
Step 3: Compare suspected records across party, lines, amounts, times, user/terminal, and
Compare suspected records across party, lines, amounts, times, user/terminal, and links.
Step 4: Identify the valid original and downstream effects
Step 5: Reverse/correct the duplicate through approved workflow
Step 6: Preserve external and local evidence
Check your work
Source, stock, party, payment, tax, external-provider, and journal controls include the event once.
Take a moment to check your work before closing the window. This small check can save time later.
If something goes wrong
Never delete one side of an integrated transaction to make counts match.
Use supplier/customer invoice and external IDs as duplicate controls where needed.
Related guides
Recover from an Interrupted Save, Finalize, or Conversion
Retry a Partially Successful Integration Safely
Correct Data without Deleting History
What to do next
Recover from an Interrupted Save, Finalize, or Conversion.