rubber stamp, wooden stamp, duplicate, office, paper, duplicate, duplicate, duplicate, duplicate, duplicate
Photo by Bru-nO on Pixabay

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.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Process.

Why duplicate documents reach financial posting

Invoices reach accounts payable in several ways at once: by email, by mail, or both. With no single entry point, staff must check each document to confirm it is new before processing.

Delivery into individual staff inboxes, not a shared accounts payable queue, is a common gap. It makes a consistent new-document check difficult to run.

Some vendors send billing data as plain text or HTML in the email body, not as an attachment. That kind of charge is easy to miss at capture and easy to re-enter later from a statement.

Decentralised purchasing compounds the problem. Staff buy software, supplies and equipment on their own corporate accounts. Finance sees the invoices only at month-end, after logging into multiple vendor portals to pull them.

Manual vendor statement reconciliation is also where duplicate payments, missed invoices and pricing discrepancies tend to surface. It often leads to disputes with the supplier.

Define what counts as a duplicate before posting

Set the definition before configuring checks. In accounts payable invoice matching, vendor invoice, purchase order and product receipt information is compared. Any difference between those documents is treated as a matching discrepancy.

Practical triggers for a duplicate include a supplier invoice number already captured. Another is an invoice whose purchase order or product receipt has already been consumed by another invoice. A third is receipt lines whose matched quantity exceeds the quantity on the invoice they are matched to.

Price agreement alone is not a reliable test. Two entries can match on unit price and still be the same document. The check must also compare document identity: supplier, invoice number, invoice date and the purchase order or receipt drawn on.

Catch duplicates at capture, not at posting

The cheapest point to stop a duplicate is capture, before the invoice is coded, matched or posted. Each new document is checked against existing records the moment it arrives.

That check depends on consolidated delivery. Invoices should land in a shared accounts payable queue rather than in personal inboxes, so one team sees every document once.

Sourcing the purchase order and packing slip that match the invoice number is how the team verifies accuracy and confirms the purchase. Where those documents cannot be found, purchasing staff have to retrieve them. That retrieval becomes a bottleneck.

Coding and entry into the accounting system or ERP should follow the match and confirmation, not precede it.

Pros and Cons of Manual vs Automated Invoice Capture

Manual Capture – Pros
Allows human review of ambiguous documents; flexible for ad-hoc entries
Manual Capture – Cons
High risk of duplicates; time-consuming; prone to error and inconsistency
Automated Capture – Pros
Reduces duplicates; faster processing; consistent rules application
Automated Capture – Cons
Requires upfront configuration; may miss non-standard formats without tuning

Match invoices against purchase orders and product receipts

Invoice matching can run at several levels of detail. Invoice totals matching compares invoice totals with purchase order totals. Two-way matching compares price information. Three-way matching also compares invoice quantities with the quantities on the product receipts selected for the invoice. Charges matching compares charge amounts on the invoice with those on the purchase order.

Two-way and three-way matching always match price by unit price, although they can be configured to match by price total. Net unit price matching compares the net unit price of each invoice line with the corresponding purchase order line.

Discrepancies are compared with configured tolerances. When a discrepancy exceeds the tolerance percentage or amount, match variance icons are displayed on the vendor invoice page and on the invoice history and matching details page.

For example, a purchase order for 1,000 batteries at 1.00 each, invoiced at 1.10 each, breaches a 5 per cent net unit price tolerance for that item category: 1.05 would be acceptable, 1.10 is not. The invoice can be saved and held until the discrepancy is resolved.

Invoice Matching Levels: Two-Way vs Three-Way

Two-Way Matching
Compares invoice price with purchase order price
Three-Way Matching
Adds product receipt quantity verification to price match

Control automated product receipt matching

Automatically matching posted product receipts to invoice lines requires a defined three-way matching policy, and depends on the vendor invoice automation feature being enabled.

The matching process runs until the matched product receipt quantity equals the invoice quantity. Where several product receipts relate to a single invoice line, the process has to run more than once to reach a full quantity match.

A retry limit can be specified for how many times the system should try to match product receipts to an invoice line before it concludes the process failed. This is the control that prevents repeated attempts against the same receipt lines.

The process runs in the background, hourly or daily, either as part of submitting invoices to the workflow system or as a stand-alone process.

Hold suspected duplicates in an exception workflow

Unmatched documents and those outside tolerance belong in an exception queue, not in posting. Holding them keeps the suspected duplicate out of the ledger while it is investigated.

Automated matching flags mismatches and prompts for the discrepancy, which routes the document to a reviewer rather than releasing it. An invoice can be recalled from the workflow system by the user whose ID was entered for the invoice submission background task.

Where a discrepancy is confirmed, the next step is to work through it with the vendor and obtain a corrected invoice.

If the purchase order or packing slip cannot be located at all, the purchasing team or purchaser has to retrieve the proper documents before the invoice can be cleared.

Run a pre-posting duplicate review

The final check before release looks for invoice numbers already captured, receipt matches already consumed, and invoices already sitting in the approval workflow.

Confirm every document is either new or clearly linked to an existing transaction. The manual process starts exactly here, checking for duplicates and confirming each invoice is new as it is received.

Coding and entry into the accounting system or ERP, and preparation of payment or hand-off to an approver, come after the match is complete and the purchase is confirmed.

Automated capture tools follow the same order, capturing, coding, matching and routing invoices before posting them to the ERP, which places the duplicate review ahead of the posting step.

Keep an audit trail of duplicate decisions

Record who reviewed the document, what it was matched against, and why it was held or cleared. Exception notes should state the discrepancy and the resolution.

Automated accounts payable systems maintain a complete audit trail with timestamped actions, so approvals, holds and releases carry a time and a user.

Match variance icons on the vendor invoice page and on the invoice history and matching details page show where a discrepancy breached tolerance, which documents the reason for the hold.

On invoices submitted automatically, the submitted-by value is the user ID entered for the background task, so the submission itself is attributed rather than anonymous.

Monitor recurring duplicate sources to tighten controls

Review duplicates by where they came from: inbox capture, portal fetching, manual entry or over-matched receipts. The pattern points to which control needs adjusting.

Capture rules, tolerances, retry limits and workflow routing are the levers. A tolerance is set by legal entity policy per item category, so it can be tightened where the same price discrepancy keeps recurring.

Automated portal fetching on a set schedule, and parsing invoices from email attachments and inline billing emails into one feed, reduces the chasing that leads to re-entry.

Recurring over-matching of receipt lines is answered by the retry limit and by monitoring matched quantities against invoice quantities.

Key Controls to Prevent Duplicate Invoices

Centralised capture queue
Reduces risk of multiple entries from individual inboxes
Automated portal fetching
Scheduled retrieval reduces manual re-entry
Retry limit on receipt matching
Prevents infinite loops in automated matching
Tolerance thresholds by item category
Enables tighter control on recurring discrepancies

More from Process Discovery