Verify Every Vendor Invoice Before a Duplicate Payment Leaves Twice

The Signal

A vendor calls asking why their invoice is thirty days late. Accounts payable pulls the record and finds it was paid three weeks ago — along with a second payment for the same amount, sent eleven days later when the same invoice arrived through a different inbox. Nobody approved a double payment on purpose. One copy came from the vendor's normal billing address, the second from a project manager who forwarded it "just in case," and the system had no way to recognize they were the same bill.

That is the signal: duplicate payments are rarely a one-time accident. They are the predictable output of a process that pays whatever invoice lands in front of someone, without checking it against what was ordered and received. Paying twice is real cash leaving the business for work already settled, and it is usually never caught until a vendor flags it or a reconciliation turns up a credit nobody expected.

A vendor-payment verification step closes that gap. Before any invoice is paid, it gets checked against the purchase order and the delivery or completion record — a three-way match — and every invoice gets a unique identifier tied to the vendor and invoice number, so a repeat submission is flagged automatically instead of processed automatically.

Why this matters now

Growing businesses add vendors, approvers, and payment channels faster than they add controls. A company that once had one person approving every invoice now has department heads approving their own vendors, invoices arriving by email, portal, and mail at once, and an accounting system built for volume, not scrutiny. Each new approver is a new path an invoice can travel unchecked against what the other paths already paid.

Wikipedia's overview of accounts payable describes three-way matching — comparing the purchase order, the receiving report, and the vendor invoice — as the standard control against exactly this failure mode, with duplicate-payment detection as one of the specific risks the practice exists to prevent. Reference: https://en.wikipedia.org/wiki/Accounts_payable

Without that check, the business cannot answer a basic question during a cash crunch or an audit: how many vendors were paid for something nobody can produce a delivery record for, and how much of that money is recoverable. By the time a vendor's own accounting catches the overpayment and offers a credit, the business has already operated for a stretch with less cash than its books implied.

The mistake to avoid

The mistake is routing invoice approval entirely through people instead of through a record. If approval depends on a department head recognizing "this looks familiar," the business is relying on memory across however many invoices that person processes each month — a method that fails quietly and often as volume grows.

A related mistake is treating multiple invoice-submission channels as a convenience without reconciling them into one system of record. A vendor who emails a copy, uploads to a portal, and mails a paper statement is not trying to defraud anyone — but three separate entry points without a shared invoice-number check is how the same bill gets paid from two different approvals.

Do not confuse payment verification with distrust of vendors. The goal is not to slow legitimate billing relationships. It is to make sure every dollar leaving the business matches an order and a confirmed delivery, so a repeat submission gets caught by the process instead of by luck.

Run the duplicate-payment test

Pull the last ninety days of payments to your ten highest-volume vendors. For each one, check whether the invoice number is unique in your system, whether it is tied to a purchase order, and whether a receiving record confirms the work or goods arrived.

Flag any vendor where the same amount was paid more than once in a short window, or where an invoice has no linked purchase order. Those accounts most likely carry an undetected duplicate or a payment with no verification trail behind it.

Assign one person or one system field as the single source of truth for invoice numbers per vendor, so a second submission of the same bill — by any channel — gets caught before it reaches approval, not after the check clears.

What stays protected

Protect vendor relationships by keeping verification fast for legitimate invoices. A three-way match should confirm a clean invoice in minutes, not hold every payment hostage to a lengthy review.

Protect approver authority by keeping the match a precondition to approval, not a replacement for it. The system catches duplicates and mismatches; the approver still decides whether the underlying spend was right.

Protect cash visibility by keeping the match connected to what was actually ordered and received, not just what a vendor claims. A verification step that trusts the invoice alone defeats its own purpose.

The first move

Pick your highest-volume vendor and pull every invoice paid to them in the last six months. Check each one against a purchase order and a receiving record, and note how many have no linked order at all — that gap is where a duplicate payment is most likely to pass through unnoticed.

The move this week

Build the invoice-number check for every vendor currently paid without a purchase-order match. Assign an owner to the three-way-match process and flag any vendor with more than one payment at the same amount in the past quarter — those are the accounts to audit first.