Process Discovery
Part of Finance process automation
Handling duplicate documents before financial posting
A duplicate invoice can enter through email, a portal and a scanned paper copy.
A duplicate invoice can arrive by email, portal or scanned paper copy. Catching it before posting is easier than reversing an entry or recovering a payment. Run a candidate check, then a human review for ambiguous matches.
Compare supplier identity, invoice number, date, amount, currency and line details. Normalise harmless formatting differences, but do not assume a matching amount proves duplication: recurring charges can look alike.
If the invoice number matches but a corrected invoice has new lines, inspect the supplier's revision and credit history before rejecting it.
Hold suspected duplicates in a visible state. Record the original document, competing record, reviewer and final decision. If you accept a duplicate as a legitimate separate charge, note the evidence.
Microsoft Dynamics 365 Finance documents matching invoices to orders and receipts; that match checks purchase context, while duplicate detection is a separate control the team must design and verify.
Test two-channel submission, resubmission after rejection and a credit note. Check whether the system blocks posting, only warns, or allows an override. A red banner everyone ignores is not a reliable control.
