Three-Way Match Delays: How to Stop Purchase Orders, Receipts and Supplier Invoices Fighting Each Other

A supplier invoice arrives, and it should take minutes to clear. The purchase order says what was ordered, the goods receipt says what showed up, and the invoice says what is owed. Instead it lands in an exceptions queue, where it sits for three weeks while a buyer, a warehouse lead and an AP clerk trade emails about whose record is right.

That is the three-way match problem, and it is rarely about the invoice. It is about three records, created in three systems by three teams, that were never built to agree with each other. At a single site, someone can bridge the gap by walking to the dock. Across many locations, the gap becomes a backlog, and the backlog turns into supplier invoice delays, late-payment friction and early-payment discounts that expire unclaimed.

This article covers why invoice matching problems happen, how to find where yours are stuck, what the delay really costs, and the steps that fix it, several of which need no new software. Then we explain where The Ninjaz Group fits, and where it does not.

What a three-way match actually checks

A three-way match compares three documents before payment is released:

• The purchase order (PO): what you agreed to buy, in what quantity, at what price and on what terms.
• The goods receipt: what physically arrived, or what service was confirmed, and when.
• The supplier invoice: what the supplier is asking to be paid.

If quantities, prices and terms agree within tolerance, the invoice is approved for payment without anyone touching it. If they do not, it becomes an exception and a person has to intervene. The control is sound. It stops you paying for goods that never arrived, for duplicate billing and for quiet price creep.

But it depends on all three records being present, current and comparable at the moment the invoice lands. When one is missing or described differently, the match fails even though nothing is wrong with the purchase. Many purchase order mismatch exceptions are not disputes at all. They are data-timing and data-identity problems: the systems cannot see each other, so the people have to.

Why supplier invoices get stuck

The same handful of causes account for most stuck invoices:

• Receipts not posted. The goods are on the shelf, but nobody has booked them in, or they were booked days after the invoice arrived.
• Partial deliveries. A PO for 100 units arrives in three shipments, and the invoice bills the full 100 or each shipment separately, so the system matches against the wrong balance.
• Price and unit differences. The PO prices by the case, the invoice by the each, or a negotiated price never reached the procurement system.
• Orders placed outside the system. A manager phones a supplier, no PO exists, and the invoice has nothing to match against.
• Inconsistent identity. One supplier under two vendor records, or item codes that differ between procurement and the warehouse system.
• Extra charges. Freight, tax and surcharges appear on the invoice but were never on the PO.
• Unclear ownership. Exceptions land in a shared queue and everyone assumes someone else is handling them.

Notice how few of these are supplier mistakes. Most originate inside your own business, in the handoffs between purchasing, receiving and finance.

How fragmented systems create the mismatch

Consider a group with twelve locations. Purchase orders are raised in a central procurement system. Each site runs its own receiving routine: some scan deliveries into an inventory or warehouse system, others write quantities on a delivery note and key them in later. The ERP holds the ledger and the AP process, and an AP automation tool captures incoming invoices from a shared mailbox.

A supplier delivers a pallet to site seven on Tuesday. The receiver counts it but only books it into the warehouse system on Thursday, when the dock is quiet. The nightly batch that passes receipts to the ERP fails that night without raising an alert. The invoice arrived Wednesday, was read correctly by the AP tool and compared with the PO. There is no receipt in the ERP, so it drops into exceptions.

The AP clerk emails the buyer. The buyer says the goods were delivered and suggests asking the site. The site manager is on leave. Eleven days later the supplier's collections team asks about payment, the ten-day early-payment discount has lapsed, and the supplier has quietly put the next order on hold.

No single system was wrong. Each held a partial truth, and nothing connected them. Approval workflows make it worse: the invoice may be routed to a cost center owner who cannot see the receipt, so they either approve blind or reject out of caution. A supplier portal that shows invoice status but not PO and receipt status leaves the supplier unable to see why payment is stuck, so they phone instead.

How to diagnose where your invoices are stalling

You do not need a new tool to find the problem. You need a few weeks of exception data and some patience.

1. Categorize the exceptions. Export the last 90 days of failed matches and label each by reason: no receipt, quantity variance, price variance, no PO, duplicate supplier or other.
2. Time each stage. Measure days from invoice received to captured, matched, exception resolved, approved and paid. The stage where days pile up is your bottleneck.
3. Cut by location and supplier. Exceptions concentrated at certain sites point to receiving habits. Exceptions concentrated on certain suppliers point to catalog, pricing or unit-of-measure data.
4. Trace five stuck invoices by hand. Follow each from PO to payment, noting every system opened, every person involved and every time data was retyped.
5. Audit missed discounts. List invoices with early-payment terms and check how many were paid after the window, and why.
6. Measure receipt latency. Find out how many hours pass between goods arriving at the dock and that receipt being visible to AP.

The answer to the last step is often the most revealing number in the exercise. If it is measured in days, no amount of AP effort will fix the matching rate.

The real cost of stuck invoices

The cost rarely appears as one line item, which is why it persists.

Time. Every exception is touched by several people, often through email. The invoice is the same; the effort multiplies.

Discounts and terms. Early-payment discounts are only available if the invoice clears inside the window. Slow matching hands that money back, invoice after invoice.

Supplier goodwill. Repeated late payment leads to credit holds, delayed shipments and tougher terms at renewal. A supplier who pauses deliveries can leave a field site waiting on parts or a service bay waiting on stock.

Inventory. When receipts are not posted, stock looks lower than it is. Buyers reorder what is already on the shelf, tying up cash and space.

Mistakes. Under pressure to clear a backlog, people override holds. That is how duplicate payments and unverified charges slip through, the exact risks the control exists to prevent.

People and customers. AP teams become full-time chasers, which wears on them. And when a held shipment becomes a delayed repair or a late delivery, the customer feels it and may take their business elsewhere.

Finance also loses visibility. Unmatched invoices are harder to accrue accurately, so cash forecasts are less trustworthy than they appear.

Fixes you can make before buying anything

Many improvements are about rules and ownership rather than technology.

• Set a receipt deadline. Require goods to be posted within one business day of arrival, and report compliance by site.
• Clean the master data. Merge duplicate vendor records and align item codes and units of measure between the procurement catalog and the warehouse system.
• Tune tolerances. Let small price and quantity variances pass automatically, and keep human review for variances that matter.
• Name an owner for each exception type. Route no-receipt exceptions to the site and price exceptions to the buyer, and put a clock on each.
• Require a PO for in-scope spend. Keep a quick route for genuinely urgent purchases so people are not tempted to work around the system.
• Fast-track discount invoices. Flag early-payment terms at capture so those invoices jump the queue.
• Tell suppliers where they stand. Ask them to quote the PO number on every invoice, and use a supplier portal or automated status messages so they can see progress without calling.
• Use two-way match selectively. For low-value or service spend, matching invoice to PO alone may be enough, which keeps the three-way check for where risk justifies it.

These changes reduce exceptions. They do not remove the underlying lag between systems, and that is where most multi-location groups hit a ceiling.

When the real fix is connecting the systems

If receipt data still takes days to reach the ledger, or buyers, receivers and AP still work from three different views of the same order, process rules will only go so far. At that point the problem is integration.

The Ninjaz Group is a managed-services partner for multi-location enterprises, and this is the kind of gap its Managed Link layer is built for: an integration layer that Ninjaz builds, owns and maintains between the systems you already run. Engagements begin with a Blueprint, where Ninjaz maps the operation from purchase order to payment, finds where work is done twice, data goes stale or money leaks, and the client keeps the map. Build & Link follows, with no rip-and-replace. The ERP, procurement system, warehouse tools and AP automation you have already paid for stay in place.

The Ninjaz Operating Platform is the hub that does the connecting. Its connectors reach ERP, inventory and WMS, and finance systems, and its unified data layer keeps one record per order, so a PO, its receipts and its invoices can be viewed together. Workflow automations can alert a site when a delivered item has not been booked in or route an exception to the right owner. The Command Center can be set up to show exceptions and invoice aging by location, and team chat boards tied to records let buyer, receiver and AP settle a query on the order itself instead of in email threads. Roles and an audit trail keep approvals accountable.

To be clear about limits: a platform does not make a receiving team book goods in, and it will not decide your tolerances or discount policy for you. Those decisions still need owners. What it removes is the part that should never have depended on someone remembering to send an email. After go-live, Managed Business Operations can keep the integrations and day-to-day running in hand.

Start with one invoice

Pick a single stuck invoice and trace it from purchase order to payment. Write down every system, every person and every delay. That one exercise usually shows whether you have a discipline problem, a data problem or a connection problem, and most groups have some of each.

If you would like help mapping it across your locations, book a consultation and we will talk through where your invoices are stalling. If you would rather see how connected PO, receipt and invoice records look in practice, watch the platform demo.