Blog · Procurement and supply chain · Procurement
Build a traceable invoice candidate review that distinguishes repeated imports, legitimate recurring charges and unresolved document similarities.
Treat apparent duplicate invoices as candidate groups for review. Similar supplier names, document numbers and amounts can indicate a repeated import, a legitimate recurring charge or a second posting of the same document. The report should make those alternatives inspectable before anyone describes the amount as a loss or saving.
Microsoft's accounts payable overview describes invoice review and approval as an AP process. The analytical shortlist below supports that review; it does not replace authorized posting or payment decisions.
Keep three identities where available: the extracted row, the supplier's document and the organization's accounting posting. One supplier document may have several line rows, while one posting may appear in several overlapping exports. Counting every row as a separate invoice creates candidates before any actual document is duplicated.
Inputs include source system, extraction batch, company, posting key, supplier key, raw document number, document type, invoice date, currency, amount basis, line key and links to reviewed supporting evidence. Use a dated cutoff, such as October 6, 2026, at 5:00 p.m. Eastern.
Resolve aliases through supplier-name normalization. Retain the raw identifiers and mapping confidence. Two similarly named suppliers must not be merged merely to improve candidate recall.
Begin with repeated stable posting keys across batches. Those suggest extraction duplication and can be reviewed independently of duplicate accounting documents. Reconcile source counts before constructing invoice-level comparisons.
Then group known supplier documents by company, reviewed supplier, normalized document number, currency and document type. Preserve the raw number alongside any normalization. Removing punctuation or leading zeros may combine legitimately different numbers, so explain exactly what the rule changes.
Broader amount-and-date-window comparisons can identify near matches, but label them lower-confidence candidates. A synthetic date window is a chosen review parameter, not a universal AP control. Do not apply it across currencies or gross/net amount bases without an approved conversion and classification method.
The following records and USD amounts are synthetic. Amounts use the same invoice-header basis and each group has sufficient supporting evidence for the illustrative classification.
| DEMO group | Extracted rows | Amount per apparent invoice | Reviewed explanation | Invoice obligations retained |
|---|---|---|---|---|
| A | 2 | $1,200 | Same posting imported twice | 1 |
| B | 2 | $500 | Separate monthly service periods | 2 |
| C | 2 | $800 | Distinct postings; same document evidence needs AP review | Unresolved |
The raw candidate rows sum to $5,000: $2,400 + $1,000 + $1,600. Removing A's verified repeated extraction row leaves $3,800 of unique posting amounts in this limited set. That $1,200 adjustment corrects the analytical population; it is not demonstrated cash recovery.
B remains two legitimate obligations totaling $1,000. C's $1,600 stays in the observed posting total with an unresolved classification. The next decision is to request its supporting document and posting history from AP, rather than suppress one $800 row on similarity alone.
A credit and replacement invoice need their documented relation preserved. Netting them before review can hide a sequence that matters, while treating the credit as a positive duplicate can inflate candidate totals. Follow the credits, tax and FX method for signed amounts and the selected spend basis.
Partial invoices against one order, split billing and several companies purchasing from the same supplier are separate exceptions to investigate. Missing document numbers should produce an evidence status, not a fabricated normalized key. An unreviewed fuzzy match is never a confirmed duplicate.
For each group, record the candidate rule, reviewer, evidence reference, disposition date and explanation. Useful dispositions include repeated extraction, legitimate separate document, linked credit/reissue, confirmed posting issue and unresolved. Preserve the original candidate group for auditability.
Use PO, invoice and paid-spend populations to keep invoiced amounts distinct from settlement evidence. A duplicate posting candidate does not show that both postings were paid or that a payment can be recovered.
Start with one company and a bounded invoice period. Review both flagged examples and unflagged examples to discover where the rules fail. Report group counts and amounts separately, with unresolved evidence visible.
The procurement review example shows how a scoped decision pack can retain reconciliation and limitations. Contact Covirage to discuss a candidate review using the authorized fields and evidence available.
No. They are a review signal. Recurring charges, separate orders and repeated imports can share those fields; inspect document and posting evidence.
No. It supplies evidence for the responsible AP reviewer. Payment decisions follow the organization's authorized process and underlying records.