Skip to content
NewParallel Run is here.See how it works →

What should a duplicate invoice check compare besides the invoice number?

Four things: the number with its formatting cleaned off, the vendor’s tax ID instead of the vendor record, every entity in the group at once, and the amount and date whatever the number says. The check most AP systems run matches the vendor record and the exact invoice number in one entity. In our example quarter, that caught 19% of the duplicate money. The other four checks caught the rest.

Where the standard check stops.

Nearly every AP system refuses a second bill with the same vendor and the same invoice number. Oracle Payables does, and its own help page lists what gets past it: the same invoice under a different supplier name, or the same number in a different case. The Washington State Auditor makes the same point from the other side: most software only finds a repeated number within one vendor number, so duplicate vendor records and numbers keyed inconsistently both slip through. It puts duplicate payments, from industry estimates, at 0.8% to 2% of total payments.

It happens to careful teams too. A 2021 Federal Reserve inspector general reviewof one agency’s vendor payments found three cases where a vendor sent the same invoice number twice, once with zeros in front. Oracle’s automatic check let all three through. None became an overpayment there, because the two parts added up to what was owed. The gap was still open.

Current answers, such as Ramp’s guide, list these causes well. What they leave out is which comparison catches which case, and the one that matters most for a group: an invoice entered in two entities, where a check scoped to one entity cannot see the other.

Eight suspect pairs from one quarter.

An example group: a US parent and a Canadian subsidiary, each with its own AP ledger, sharing a few vendors. A quarter’s review turns up eight pairs of bills that look alike. Seven are true duplicates worth 82,445.00. One is two real orders.

Every vendor, number and amount is an example. The last column is the first check, in the order below, that catches the pair.
PairWhat happenedInvoice numbersAmountCaught by
1The same PDF arrives by email and through the vendor portalINV-3308 and INV-33083,200.00Check 1
2A paper copy is keyed after the PDF was already entered771204 and 77120412,480.00Check 1
3Two people key the same number differentlyINV-4471 and inv 44717,950.00Check 2
4The vendor adds leading zeros on a resend00012345 and 1234518,600.00Check 2
5One vendor, two vendor records in the same entityA-2231 on each record4,375.00Check 3
6A group invoice entered by both entitiesSW-9902 in each entity26,000.00Check 4
7Two real orders for the same amount in one week6610 and 66182,150.00Flagged by check 5, cleared
8A corrected copy reissued under a new number5120 and 5120-R9,840.00Check 5
Every vendor, number and amount is an example. The last column is the first check, in the order below, that catches the pair.

Five checks, and what each one adds.

Each check runs on top of the ones before it. Share is of the 82,445.00 in true duplicates. Check 5 also flags pair 7, a 2,150.00 repeat order that a reviewer clears with the second purchase order.
CheckAddsCaught so farShare
1. Vendor record and exact invoice number, one entity15,680.0015,680.0019%
2. Vendor record and cleaned invoice number26,550.0042,230.0051%
3. Vendor tax ID and cleaned number, across vendor records4,375.0046,605.0057%
4. Check 3 run across every entity in the group26,000.0072,605.0088%
5. Same tax ID, same amount, dates within 30 days, any number9,840.0082,445.00100%
Each check runs on top of the ones before it. Share is of the 82,445.00 in true duplicates. Check 5 also flags pair 7, a 2,150.00 repeat order that a reviewer clears with the second purchase order.

The exact check does its job on pairs 1 and 2, the plain re-entries. Cleaning the number before comparing it, check 2, more than doubles what is caught, and costs almost nothing.

The cleaned number

How to clean an invoice number before you compare it

  1. Upper case every letter
  2. Remove everything that is not a letter or a digit
  3. Drop zeros at the very start

  INV-4471    becomes   INV4471
  inv 4471    becomes   INV4471
  00012345    becomes   12345
  12345       becomes   12345
  5120-R      becomes   5120R      (still different from 5120)

Skip the check when the cleaned number is one character,
or a placeholder such as 1, 001, NA, TBD or INV. Those
match each other by accident and teach people to click
past the warning.

Check 3 moves the match from the vendor record to the vendor itself. A tax ID, or a bank account if you do not hold tax IDs for everyone, ties two records for one supplier together even when their names differ. It is also the start of cleaning the vendor file, which the Washington State Auditor puts first.

Check 4 is the one a group needs and a single company never misses. Pair 6 is a software invoice sent to the group and keyed by both entities. Each ledger, on its own, holds exactly one copy, so any check inside one entity passes it. Running check 3 across every entity catches it, and in this example it was the largest single duplicate.

Check 5 ignores the number altogether. It is the only one that sees pair 8, where the vendor reissued a corrected copy as 5120-R. It is also the only one that raises a false alarm.

Which checks block, and which go on a list.

  • Checks 1 to 4 can stop the bill at entry. A match on the vendor and a cleaned number is almost never two real invoices, so a hard stop with a link to the first bill is the right answer.
  • Check 5 belongs on a review list before each payment run. It catches real repeat orders too, and a reviewer with the purchase orders open clears those in seconds.
  • Run all five backwards once over the last twelve months of paid bills. Compare each suspect with the vendor’s statement, and where you paid twice ask for a refund or a credit against the next invoice.

What Rivane checks today.

Rivane runs check 1 at two points, when the invoice arrives and when the bill is created, and adds a file fingerprint that catches pair 1 even before anyone reads the number.

Duplicate checks in Rivane, as built

# Duplicate checks in Rivane, as built.

intake      a vendor invoice arriving as a document is
            compared with earlier documents in the same
            entity, first by file fingerprint (SHA-256),
            then by vendor and invoice number
skipped     placeholder numbers such as 1, 001, N/A, TBD
            and INV, so they never match each other
logged      every decision, match or no match, with its
            reason
blocked     a document marked Duplicate cannot become a bill
bill        the same vendor invoice number cannot be used
            twice for one vendor in one entity; a database
            constraint enforces it, and the migration that
            added it refused to run over existing duplicates
vendor      a new or edited vendor is checked for a tax ID
            already on file in the entity, with spaces,
            dashes, dots and slashes removed first

The limits, as of today. Invoice numbers are compared exactly, after trimming spaces at the ends, so pairs 3 and 4 would get through. Every check runs inside one entity, so pair 6 would too. The tax ID check warns when a second vendor record is created; it does not join two existing records when matching invoices. Checks 2 to 5 are, for now, a review you run yourself from your bill list.

The short version.

Keep the exact check. Add a cleaned number, match vendors by tax ID, run it across every entity, and put same amount, same vendor, close dates on a list before each payment run. In the example, that took the catch from 19% to all of it, for one false alarm.

To see how Rivane handles vendor invoices from intake to payment, read Rivane accounts payable.

Frequently asked questions.

Should a cleaned invoice number match block the entry or only warn?

Block it when the vendor and the cleaned number both match, because two different invoices from one vendor almost never clean to the same number. Keep the amount and date check as a review list before the payment run, because it also catches real repeat orders.

Does stripping punctuation create false matches?

Rarely within one vendor. The false matches come from placeholder numbers such as 1, 001, N/A or INV, which match each other once cleaned. Skip the check for those and for any cleaned number of one character.

How do we find duplicates we have already paid?

Run the same five comparisons over the bills paid in the last twelve months, then check each suspect pair against the vendor’s own statement. Where the vendor shows one invoice and you paid two, ask for a refund or a credit note against the next invoice.

Sources

A note on how this was researched. The inspector general report was read from the PDF itself, not from a summary. The other pages were read as they stand today. The group, the vendors and every amount are examples. The Rivane section describes the product as built today, checked against the bill, vendor document and vendor code rather than marketing copy.

On embedded social posts: we looked for public posts from auditors or practitioners on duplicate invoice matching and found none we could verify as current and relevant, so this article uses ordinary citations instead.