Supplier Invoice Duplicate Screening

A supplier can send an invoice twice, or an internal team can enter one document twice, and if both records are paid the company loses cash and may need a recovery effort. Duplicate screening looks for possible repeats before payment, beginning with the supplier identity, because the same legal vendor may appear under two names or accounts and a screen limited to one vendor ID can miss that case.

Compare invoice numbers, since exact repeats are an obvious clue but formatting may differ through leading zeros, spaces, slashes or OCR errors, so normalise carefully without erasing meaningful distinctions. Use other fields as well: Oracle's duplicate-check documentation describes combinations of supplier, invoice type, amount, currency and date, and the configured feature is a screening aid, not proof that two invoices are identical.

Check currency, because 1,000 in one currency is not the same as 1,000 in another and conversion can produce misleading near matches, and compare invoice dates and periods, since two recurring monthly invoices for the same amount may both be valid and their service periods and order references distinguish them. Match line details where possible, because the same purchase order, goods receipt and line descriptions increase suspicion, yet a supplier can legitimately bill separate partial deliveries under one order.

Watch credit notes, since a credit note and invoice with the same amount can be opposite entries, and keep original documents, because an OCR field can be wrong and the actual invoice image should be reviewed before holding or releasing a suspected duplicate. Check payment state, since one duplicate may already have been paid and the next step could be a hold, supplier query or recovery request rather than simply deleting a record.

Separate exact and fuzzy candidates, because an exact invoice number and supplier match is stronger than a similar amount and date, and set a practical review queue in which high-value and near-payment candidates get fast attention, since a flood of weak matches can delay legitimate suppliers. An illustrative flagged rate is 20 possible duplicate records among 2,000 invoices screened, or 1%, which is not the confirmed duplicate rate because reviewers must classify each flag.

Measure confirmed results separately: if five of those 20 flags represent the same underlying invoice twice, the confirmed count is five records under the chosen counting rule, so state whether you count pairs or duplicate payments. Check vendor statements, which can reveal an invoice the supplier thinks remains unpaid or a credit due, without relying on them alone to decide whether internal invoices are duplicated.

Maintain a resolution trail recording the reviewed pair, evidence, reviewer and decision, and mark valid recurring bills clearly so the same false alert does not recur without reason. Prevent reruns from creating duplicates, since an email attachment may be ingested automatically and then keyed manually, so define one entry channel or a pre-entry check, and investigate root causes such as repeat copies from one mailbox, poor OCR or duplicate vendor accounts, because recovering a payment without fixing ingestion leaves the risk.

Test false negatives by sampling paid invoices with the same amount, similar number or same purchase order even if the tool did not flag them, since screening performance matters both ways. Avoid treating a match as fraud, because duplicate entry is often an error and suspected misconduct should be escalated only with appropriate evidence and company procedure.

Match at the right granularity and monitor late changes, since a consolidated invoice can resemble several service-line bills and a corrected invoice may replace an earlier one, so confirm whether the original was voided, credited or still open before paying the replacement. For owners, duplicate screening is a preventive cash control that should find plausible repeats while allowing genuine recurring and partial bills to be paid on time.