The Procurement-AP Gap: Where Supplier Overcharges Hide in Plain Sight

Supplier overcharges are rarely hidden because someone is not doing their job. They are hidden because the work is split across teams that each see only part of the truth.

Procurement negotiates pricing and terms. Operations focuses on keeping projects moving. Accounts payable focuses on processing invoices accurately and on time. Finance focuses on clean closes and reliable reporting.

Each function is doing what it is measured on. The problem is that supplier pricing accuracy lives in the space between them.

This is the procurement-AP gap. It is one of the most common places for overcharges and pricing drift to hide in plain sight because no single team owns “pricing truth” end to end.

For the deeper explanation of why workflows process invoices but still miss errors over time, start here: https://www.3rd-armor.com/post/why-erp-systems-miss-invoice-errors

Why the gap forms

The gap forms because procurement and AP are optimized for different outcomes.

Procurement is optimized to secure good pricing and availability. AP is optimized to pay correctly, on time, with clean documentation. Both are necessary. But the measures create a subtle reality: procurement focuses on the agreement, AP focuses on the invoice.

Overcharges usually appear where those two do not connect cleanly.

If pricing terms are not easily visible at the time of invoice approval, AP cannot realistically validate them. If procurement does not see pricing behavior across invoices, it cannot spot drift or inconsistency early.

The result is predictable. The agreement exists, but it does not consistently protect the payment.

The overcharge patterns that thrive in the handoff

This gap is not theoretical. It shows up in a handful of repeat patterns.

1) Contract pricing exists but is hard to reference during approval

Even when pricing is negotiated, it can live in a PDF, an email thread, a vendor portal, or someone’s memory. AP reviewers do not have time to hunt for it on every invoice, so approvals default to “looks reasonable.”

2) Substitutions and backorders change the pricing story

Operations accepts substitutions to keep work moving. Procurement may or may not be involved. AP receives an invoice that technically reflects what was delivered, but the substitution can change packaging, units, and effective cost. Everyone thinks it is handled, yet pricing may drift.

3) Units and pack sizes shift while everything still “matches”

A case becomes a different case. A box count changes. The invoice can match the PO, and the PO can match receiving, while the effective unit cost increases quietly. This is why overcharges can pass clean workflows without triggering mismatch flags.

4) Fees become the gray zone nobody owns

Freight, fuel, handling, and service charges often fall into “somebody else’s responsibility.” Procurement assumes AP will flag odd fees. AP assumes fees are part of purchasing terms. Operations assumes it is just shipping reality. That is how fee creep becomes normalized.

5) Payment speed becomes the priority

When the business is moving fast, the incentive is to pay and move on. The moment anyone slows the process down to validate pricing, they are seen as creating friction. This is why the gap expands as volume increases.

Why this is a leadership problem, not a departmental problem

When procurement and AP are not aligned on pricing verification, the business ends up with a common symptom: supplier spend rises, and nobody can explain exactly why. Teams can explain throughput and close health. They cannot explain pricing behavior.

That lack of explanation is not just annoying. It makes leadership decisions weaker.

Pricing decisions, bids, margin targets, hiring plans, and growth investments depend on job cost truth. If supplier pricing is not verified consistently, job cost truth is compromised.

This is why the procurement-AP gap is a margin strategy issue, not a back-office process detail.

What closes the gap: shared pricing rules and verification

The fix is not asking AP to become procurement or asking procurement to become AP. The fix is establishing shared rules that define what should be verified and how exceptions are handled.

A practical approach includes:

1) Shared definitions of “right”

Define acceptable variance thresholds, fee expectations, unit-of-measure stability rules, and substitution guidelines. These become shared guardrails, not tribal knowledge.

2) A single exception language

When something is out of band, there should be a consistent way to flag it and route it. Not a debate. Not an email hunt. A defined path.

3) Verification based on patterns, not one-off review

Pricing behavior has to be validated across time and across suppliers. That is where drift, inconsistency, and overcharges actually show up. When verification is based on patterns, the business stops relying on memory and starts relying on evidence.

This is also where supplier price comparison becomes powerful. When comparable items can be evaluated across suppliers, “normal” pricing becomes anchored to reality, not habit.

A practical starting point

Closing this gap starts by measuring exposure. A baseline makes it easier for procurement and AP to align because the conversation becomes about risk areas instead of opinions.

Supplier Billing Risk Scorecard: https://www.3rd-armor.com/post/billing-risk-assessment

Once the baseline exists, leadership can decide where verification rules should tighten and which supplier categories deserve the most attention first.