Duplicate detection

Duplicate detection before the bill posts

Duplicate invoices are caught twice, once when the invoice is checked and again at the moment of posting.

Book a walkthroughInvoiceIQ AP by Analytos
A 92-second product tour of InvoiceIQ by Analytos: reading a supplier invoice, matching it, and posting it to the ERP.

The question: How can AP detect duplicate invoices before payment?

The short answer

InvoiceIQ AP by Analytos checks for duplicates twice: once when the match report is built, and again at the moment of posting. Invoice numbers are normalised first, so “VS-4410”, “vs 4410” and “VS4410” are the same invoice. A purchase order that is already fully billed is also raised as a possible duplicate. Duplicates are blocked, never quietly paid.

Posting Log
GX-88412Posted · VB-4410j.doe
CF-1189Refused · price variance 6.2%j.doe
INV-1001Posted · VB-4411a.rao
NW-5531Waiting · receipt expectedsystem
Illustrative screen with demo data

How it works

  1. Step 1

    Normalise

    Strip case, spaces and punctuation from the invoice number.

  2. Step 2

    Compare

    Check the vendor and normalised number against invoices already processed.

  3. Step 3

    Check the order

    Flag a PO that has already been billed in full.

  4. Step 4

    Re-check at posting

    Run the guard again at the moment of posting, in case a copy arrived meanwhile.

  5. Step 5

    Block and explain

    Hold the invoice with the earlier match named.

Why duplicates slip through

  • The same invoice is emailed twice, or emailed and uploaded.
  • A reminder copy is sent with a slightly different number format.
  • A second person keys an invoice already in someone else’s queue.

Controls

  • Exactly-once email intake: a message-id ledger means the same email is never ingested twice
  • The duplicate guard cannot be bypassed by switching policy
  • Every refusal is on the Posting Log

Is this a fit?

A good fit when

  • Invoices arrive by several channels
  • Several people process the same vendors

Not the right tool when

  • You need cross-entity duplicate detection across separate ERPs (scope it with us)

Evidence

  • CapabilityNormalised duplicate guard on the report and again at posting.

How we label claims: evidence and claims policy.

Frequently asked questions

  • Yes. Numbers are normalised before comparison.

  • It is held for review with the earlier invoice shown, so a person decides.

  • The duplicate guard runs under every policy, including the non-PO tier.

Related questions

InvoiceIQ AP by AnalytosAI Accounts Payable AutomationInvoice exception managementHow do I reduce invoice exceptions and clear the AP exception queue faster?AP controls and audit trailWhat controls should AP automation have?3-way invoice matchingHow do I automate invoice matching against the PO and the goods receipt?

See InvoiceIQ AP on your own documents

InvoiceIQ AP by Analytos: ai accounts payable automation. A walkthrough starts with your real supplier invoices, purchase orders and receipts.

Book a walkthrough