A receiving clerk reports a physical discrepancy to the operations team

Guide

Duplicate supplier invoices: catch resends before they become a second posting

Three attachments can represent one invoice. Preserve the arrival history, compare the business identity and confirm the destination before retrying.

Read the guide

Published

Order, delivery, acceptance and invoice records with one discrepancy

Duplicate supplier invoices can enter through different channels: the original email, a reminder attachment and a photo sent to a colleague. Detecting the same file is useful, but the operational goal is to avoid a second accounting entry for the same obligation.

Finance needs three separate controls: recognize repeated source files, identify a potentially repeated invoice and prevent a technical retry from creating another posting. None replaces the others.

A file fingerprint does not identify every invoice duplicate

An exact-copy fingerprint can recognize an unchanged attachment. It will not reliably recognize the same invoice after rescanning, photographing or saving it again.

Keep a source identity for each attachment and a business identity for the invoice. Multiple source files can belong to one invoice record, with their channel and arrival history preserved.

Do not delete a suspected duplicate before review. The second document may contain a correction or explain why the supplier resent it.

Compare the invoice inside the supplier context

A useful candidate check considers supplier identity, original invoice reference, date, currency and amount. The policy must account for your suppliers' numbering conventions.

Preserve the raw reference. Normalizing spaces or letter case can improve searching; removing meaningful characters can merge different invoices. Uncertain OCR should produce a review candidate rather than an automatic deletion.

Illustrative example: supplier V-17 sends invoice F-1048 for MAD 8,400. A photo later extracts as F-IO48 with the same date and amount. Show both sources and the matching reasons to a reviewer. The letter O and digit zero ambiguity does not establish either a new payable or a confirmed duplicate.

What OCRAgent supplies, and what the pilot must add

OCRAgent supplies invoice extraction and a reviewable document-processing foundation. Its source storage and queue/review controls help preserve the material being examined.

A business-level supplier-invoice duplicate register is a separate implementation requirement. The reviewed invoice matching function compares orders, prices and receipts; it does not establish a complete duplicate-payment control. Kaliits scopes the supplier identity rules, candidate search and destination checks with your team.

This boundary matters commercially. Buying a PDF extractor does not mean you have acquired duplicate posting prevention.

Treat an import timeout as an unknown outcome

Suppose an ERP accepts an invoice but the response is lost. Repeating “create invoice” can produce a second entry unless the integration can identify the first attempt.

Use a stable transaction reference, a supported idempotency mechanism or a confirmed destination lookup before retrying. A successful CSV export is not evidence that the accounting import completed. Where the destination lacks the required capability, define a reviewed recovery process.

The reviewer also needs the first invoice's status. “Previously received,” “imported,” “approved” and “paid” are different facts.

Test exceptions that look like duplicates

The pilot should include an exact resend, a photo, an OCR reference error, a revised invoice, a credit note and the same invoice number used by two suppliers. Include a timeout after successful import.

A credit note is not a duplicate to suppress. A correction should be linked under an agreed revision rule rather than silently replace the original record. Shared amounts and dates can be coincidental.

Review false alerts as well as missed duplicates. Too many weak warnings recreate the workload you intended to remove.

Time released and financial risk are different measures

Illustrative calculation: thirty monthly duplicate investigations reduced from ten to four hands-on minutes release three hours. That is a handling-time opportunity under assumed inputs.

If a duplicate payment is demonstrably prevented, record its confirmed outcome separately. A flagged invoice worth MAD 8,400 is not automatically MAD 8,400 saved. It may already have been blocked by the ERP, or may be a valid correction.

Wawa Creative's reported 98% time reduction concerns product preparation and WooCommerce insertion. It supports experience with repetitive destination work, not a measured duplicate-invoice outcome. See the actual client workflow.

Scope one destination before rolling out

Start with one invoice intake flow, an agreed supplier register and your accounting software's native duplicate checks. Test candidate review and recovery before allowing operational imports.

Review the complete invoice workflow, then map our duplicate invoice control. Describe the arrival channels, destination software and how your team distinguishes a resend from a corrected invoice.

All articles

Related reading