Your ERP Approved It. That Doesn’t Mean You Should Have Paid It

The structural gap in ERP 3-way match that costs US industrial and manufacturing companies millions annually — why it exists, where it hides, and what it takes to close it.

Let’s say your AP team runs a clean three-way match. Purchase order, goods receipt, vendor invoice — three documents, one approval, payment released. It’s the bedrock control of every mid-market finance function. Your ERP enforces it automatically. Your auditors check for it. You believe it’s working.

Now let’s say that same company spends $4.2M a year on freight. Another $1.8M on maintenance contractors. A further $900K on calibration and safety services. None of that spend has a Goods Received Note. There is no physical item to receive, no warehouse scan, no three-way match to enforce. The PO goes out, the vendor sends an invoice, AP pays it — and the only thing standing between your contracted rate and whatever the vendor decided to charge is whoever happened to look at the invoice that day.

For most US industrial and manufacturing companies in the $30M–$150M revenue range — particularly in Texas, the Midwest, and the Southeast — this structural gap in AP controls runs between 1.5% and 3.5% of total service spend annually. It is not an edge case. It is the default operating condition.

That is not a gap in your team’s diligence. It is a gap in how ERP systems were designed.

“The only thing standing between your contracted rate and whatever the vendor decided to charge is whoever happened to look at the invoice that day.”

Why 3-Way Match Was Never Designed for Service Spend

Three-way match is an elegant control for goods. You ordered 50 units. The warehouse logged 50 units received. The invoice says 50 units. Approve. It works because there is an objective, time-stamped record of delivery — the goods receipt — that sits between the purchase order and the payment.

Services don’t work that way. When a maintenance contractor completes a repair at a Texas industrial facility, there is no system-generated receipt of services rendered. When a freight carrier delivers a load along a Gulf Coast lane, the bill of lading confirms the load moved — not that the rate charged matches the rate contracted. When a calibration vendor runs a safety certification, the certificate confirms the work was done — not what scope was agreed or what the overage threshold was.

The ERP sees a PO, sees an invoice within tolerance, and approves. It has no way of knowing whether:

the rate on the invoice matches the rate in the contract signed nine months ago

the scope billed includes work that was never authorized in the SOW

a service-level credit was triggered that should offset the amount owed

an early-payment discount the company negotiated is being silently ignored

the same job was invoiced twice under different reference numbers

These are the ERP 3-way match limitations that mid-market manufacturing finance teams live with every day — not because anyone chose to accept them, but because no standard AP control was ever designed to catch them. Your ERP wasn’t built to know any of this. It was built to match documents. If the documents pass tolerance, the payment goes out.

The vendor contract is stored somewhere else — typically a shared drive, a filing cabinet, or a contract management tool that does not connect to the AP workflow. No system is actively comparing it against what gets billed.

The Scale That Makes Mid-Market Manufacturers Most Exposed

Large enterprises have dedicated procurement operations. Coupa, Ariba, Ivalua — enterprise procurement platforms that add a contract-to-invoice enforcement layer on top of the ERP. They are expensive, complex to implement, and built for organizations with hundreds of procurement professionals to operate them.

Small businesses mostly work with a handful of vendors and can manage exposure manually. The owner often reviews invoices directly.

Mid-market industrial and manufacturing companies — $30M to $150M in annual revenue — sit in exactly the wrong position. Vendor spend is large enough that manual review is impossible. The company is too small to justify, staff, or configure enterprise procurement software. The AP team is two to four people processing hundreds of invoices a month across freight, maintenance, contracted services, and professional spend categories. Contract enforcement is not their job. It is not anyone’s job.

That structural position is where margin drift concentrates.

This Is Not a Vendor Integrity Problem

It is tempting to frame margin drift as vendors behaving badly. Some are. Rate escalation that exceeds contract terms without notice is a vendor behavior issue. But most margin drift in manufacturing accounts payable is not the result of deliberate overbilling — it is the result of a system that makes drift structurally invisible.

Vendors bill based on their own systems. If their rate schedule updates and the contract has not been formally renegotiated, they charge the new rate. If a field technician spends four hours on a job scoped for two, the invoice reflects actual time. If no one on your side tracks SLA performance against payment terms, no one calls in the credit.

The root cause, in almost every diagnostic run on a US mid-market manufacturer, is the same: there is no systematic comparison happening between what was contracted and what is being billed. The contract is a static document. The invoice is a live transaction. Nothing is bridging them.

“Most margin drift is not the result of deliberate overbilling. It is the result of a system that makes drift structurally invisible.”

What a Services Receipt Actually Looks Like

The fix to the ERP 3-way match gap for services is not to force services into a goods receipt workflow. It is to reconstruct what a services receipt would contain — and build the comparison against it.

For freight, this means mapping the contracted lane rate, fuel surcharge formula, and accessorial schedule against each line of the carrier invoice. For maintenance contractors, it means mapping the labor rate, parts markup ceiling, and authorized scope against the work order invoice. For contracted IT or professional services, it means mapping the agreed day rate, retainer terms, and not-to-exceed thresholds against what is billed.

This is what a Virtual GRN (Goods Received Note for services) does — it reconstructs the digital service receipt from contracts and operational evidence, then runs the comparison at the line level rather than just the total. None of this requires new vendor systems or ERP integration. It requires pulling together what the company already has — the contract, the PO, the invoice — and running a structured comparison.

When that comparison runs systematically across 90 days of live AP and contract data, the patterns become visible quickly. Rate drift that looks like noise at the invoice level reveals itself as a consistent behavior at the vendor level. Scope expansions that seem like legitimate change orders reveal themselves as recurring overcharges against the same contract clause. SLA credits that were never claimed show up as unpaid receivables buried in the company’s own contract terms.

For a $60M Texas industrial manufacturer running this comparison for the first time across freight and maintenance vendors, the annualized gap is typically in the $150,000 to $320,000 range. Not because the company is poorly managed. Because the control that would have caught it was never built.

What Finance Leaders Who Get This Right Do Differently

CFOs at mid-market industrial and manufacturing companies who have closed this gap share three practices that their peers typically do not have in place.

First, they treat the vendor contract as an active data source, not a filed document. Contracted rates, SLA terms, scope boundaries, and payment discount triggers are logged in a system — not a drawer — and referenced at invoice time, not only at contract renewal.

Second, they separate invoice approval from contract compliance review. AP approves invoices within tolerance. A separate control — automated where possible, structured manual where not — flags invoices that deviate from contracted terms before payment releases, not after.

Third, they run a periodic margin drift diagnostic in procurement and payables— at minimum annually — that goes beyond what the ERP can see. Not to find fraud. To surface the systemic drift that no one intended to create but that compounds in the background regardless.

These are not expensive practices. They do not require enterprise procurement software or additional headcount. But they do require acknowledging that ERP 3-way match, as implemented in most mid-market manufacturing operations, was never designed to protect against the category of spend where most margin drift actually lives.

The diagnostic question worth asking this quarter is not whether your AP team is doing their job. It is whether the controls you have were actually designed for the spend categories carrying your highest exposure. For most US industrial and manufacturing companies at this scale, the honest answer is: they were not. The gap is structural. And it is almost certainly running right now.

To know more, please write to [email protected].

Data/Evidence: What the data shows across mid-market industrial supply chain diagnostics: — Rate variance (invoiced rate exceeds contracted rate): present in 78% of freight and maintenance vendor relationships reviewed — Unauthorized scope charges: found in 61% of maintenance and contracting engagements sampled — Unclaimed SLA credits: identified in 44% of service contracts with defined penalty clauses — Duplicate or near-duplicate invoices: detected in 23% of vendors with monthly recurring charges — Payment term discount leakage: confirmed in 38% of contracts with negotiated early-pay terms Average annualized exposure across these five categories: $140,000–$380,000 per company reviewed. Geography: Texas, Midwest, and Southeast industrial and manufacturing companies, $30M–$150M revenue.