The invoice matched the PO. You paid for 60 that never arrived.

What looked normal

Purchase order approved. Invoice in tolerance. Payment run cleared. On paper, three-way match worked—or close enough.

In the warehouse, quantity was short, timing was wrong, or the goods receipt never existed. That is the three-way match problem: AP pays on two documents while the third is missing, inflated, or delayed.

Why people should care

Three-way match is the control most companies say they run—and the one leakage most often slips through.

ERP tolerances, two-way shortcuts, and “pay first, resolve later” exceptions quietly turn match into a rubber stamp. Sampling a few invoices finds the obvious. Population analytics find the pattern: chronic short receipts, price creep, and invoices that never meet a goods movement.

Seven analytics that catch three-way match gaps

These tests join purchase orders, goods receipts (or service entries), and vendor invoices— data most ERP and AP systems already hold.

  1. Invoice with no goods receipt

    Flag invoices posted or paid against a PO with no GR / service entry for the line.

    Business impact: Stops payment when nothing was received.

  2. Invoice quantity above received quantity

    Compare billed quantity to cumulative GR quantity by PO line—beyond tolerance.

    Business impact: Catches overbilling on short or partial deliveries.

  3. Invoice price above PO price

    Unit price or extended amount exceeds PO (and tolerance) without an approved change order.

    Business impact: Surfaces price creep that two-document reviews miss.

  4. Full invoice paid on partial receipt

    Payment cleared at 100% while GR remains open or partial on the same PO lines.

    Business impact: Finds “pay in full, receive later” leakage.

  5. Goods receipt after invoice payment

    GR posted after the invoice was paid—or backdated to look like a match.

    Business impact: Flags match repaired after cash left the company.

  6. Duplicate invoice against the same PO / GR

    Same vendor, amount, or reference billed more than once to one PO or receipt.

    Business impact: Blocks double pay dressed as a clean match.

  7. Chronic match exceptions by vendor

    Vendors with repeated quantity, price, or missing-GR exceptions versus peer baselines.

    Business impact: Prioritizes suppliers where “exceptions” are the operating model.

Why AP reviews miss this

Traditional

Tolerance and workflow

Is the invoice in tolerance? Was someone approved? Two documents can look fine while the receipt is thin.

What risk needs

PO + GR + invoice joins

Quantity, price, timing, and open receipts— across every line, not a sample of exceptions.

Key takeaway

The paperwork can look easy. The arithmetic is the risk: ordered vs received vs paid.

How foretale.ai helps

foretale.ai runs three-way match analytics across PO, goods receipt, and invoice data— missing receipts, quantity and price overbills, full pay on partial GR, post-payment receipts, duplicate invoice-to-PO links, and chronic vendor exceptions—with explainable evidence for every finding.

Controllers and auditors review prioritized match breaks across 100% of AP lines—not a tolerance sample.

How often does “matched” still mean overpaid?

Most companies don’t know—until they join PO, GR, and invoice at line level. Continuous AI analytics can surface three-way match gaps before the next payment run.

Request a demo