Investigate two transactions that look like duplicates

Compare source identities before calling an item a duplicate

Deleting the wrong one creates more work than the check itself. Compare the source evidence before deciding what needs correction.

When an exception needs a supplier invoice schedule, ParseMill can extract the invoice PDFs into Excel and keep source references available for checking. That gives the reviewer a concrete starting point. Bank reconciliation, accounting judgments and posting stay in your accounting system.

The review may identify two legitimate purchases, a repeated import or a duplicate financial record. Those outcomes require different handling. Intake or operations staff should assemble the comparison and route the decision to an authorized reviewer rather than deleting the second-looking item to clear the queue.

Build a side-by-side comparison

Record internal record IDs, bank or source references where available, amounts, currencies, date meanings, descriptions, creation history and evidence links. Mark unavailable identifiers explicitly. A blank source reference should not be interpreted as a match, and two different internal IDs do not necessarily prove two real-world transactions.

Intuit: Audit log describes recorded changes and actors. Intuit: Reconcile an account describes comparing transactions with statements. These records can support the investigation, while the proposed worksheet keeps source identity separate from application history. An entry created twice may still need source-level confirmation before the reviewer chooses a correction.

Test three candidate pairs

The following fictional examples illustrate why matching amount and date are insufficient. Each comparison produces a different evidence question.

Do not use the labels in the last column as final conclusions. For C and D, compare the original bank source and import history. For A and B, verify that the distinct references actually identify separate events. For E and F, inspect the original purchase-refund chain rather than removing one as a duplicate.

Preserve the investigation and decision

Record which sources were checked, what they established and what remains unknown. If the reviewer authorizes a correction, retain the specific records affected and the implementation evidence. A task marked resolved before the authorized change is verified can leave the books and exception register inconsistent.

• Compare source references where available.
• Keep account and currency context attached.
• Distinguish event dates from import or creation dates.
• Inspect supporting documents and relevant history.
• Record the reviewer's decision before correction.

If the same amount recurs frequently, avoid treating recurrence itself as suspicious. Subscription payments, regular purchases and repeated customer receipts can produce legitimate similarities. The investigation should be proportionate to the observed conflict and the firm's review process, with uncertainty retained where evidence is insufficient.

Check the outcome against the original source

After any authorized correction, confirm that the resulting records still represent the underlying events supported by the source. Recheck the relevant reconciliation rather than assuming fewer rows means a better result. Preserve the rejected candidate relationship for future reference if similar questions recur.

Use the related workflow guide for the broader exception process and the workflow audit checklist to review duplicate investigations. A good test set includes legitimate same-amount transactions, repeated imports and a refund, so the workflow must distinguish identity and event role rather than relying on a simple similarity rule.