5.5 Operational SRM: Invoice & Payment Issue Resolution and the Liaison Role
Key Takeaways
- The supply manager acts as the liaison between suppliers and internal functions, keeping forecasts, specifications, engineering changes, and documentation flowing accurately in both directions.
- Most invoice and payment problems are symptoms of upstream data or process failures — price master mismatches, missing receipts, freight-term errors — not supplier malice.
- Three-way match exceptions (PO vs. receipt vs. invoice) are resolved by fixing the mismatch at its root cause, then paying correctly and on time.
- Payment timeliness is an SRM lever: chronic late payment damages trust, invites supply priority loss, and can breach contract terms.
5.5 Operational SRM: Invoice & Payment Issue Resolution and the Liaison Role
Strategic SRM (Sections 5.1-5.3) fails quietly when the operational layer breaks: invoices blocked, payments late, engineering changes never transmitted, receipts unbooked. Two Core tasks — 1-E-9 (resolve invoice and payment problems) and 1-E-10 (act as liaison between suppliers and functional areas) — test whether the supply manager can keep this daily machinery running.
1. The Liaison Role (Task 1-E-10)
The supply manager is the single point of accountability for the information flowing between the supplier and the enterprise:
- Outbound to supplier: demand forecasts and releases, specifications and revisions, engineering change notices (ECNs), quality requirements, delivery schedules, and policy/compliance updates.
- Inbound from supplier: capacity constraints, cost/price pressures, quality issues, innovation proposals, and delivery risk warnings — routed to the right internal owner with context.
- Documentation integrity: the current revision of drawings, SOWs, and SLAs is what the supplier builds to; version confusion is a defect factory.
- Product flow coordination: expediting/de-expediting signals (Section 8.5), ASN accuracy, and receiving-dock readiness.
[!NOTE] Practical rule: when an internal function and a supplier disagree, the liaison's first job is to establish one authoritative version of the facts — current spec revision, current PO terms, current schedule — before negotiating who is right.
2. Anatomy of Invoice & Payment Problems (Task 1-E-9)
The three-way match compares the purchase order, the goods receipt, and the supplier invoice (Section 12.1). Exceptions fall into a small set of recurring root causes:
| Exception | Typical Root Cause | Correct Resolution |
|---|---|---|
| Price variance | Invoice price ≠ PO price; contract price master not updated after negotiation | Verify agreed price; correct invoice or fix the price master/catalog — and fix the upstream update process |
| Quantity variance | Billed quantity > received quantity (partial delivery, ASN mismatch) | Pay per receipt; resolve the shortage as a delivery issue (Section 8.5) |
| Missing receipt | Goods received but not booked in the ERP | Chase the dock entry — do not force-pay without evidence of receipt |
| Freight/terms mismatch | Invoice adds freight or surcharges the PO terms exclude (or vice versa) | Enforce the Incoterms®/freight terms of the PO; reject unauthorized surcharges (value leakage, Section 3.3) |
| Duplicate invoice | Resubmission after slow payment, or fraud signal | Pay once; investigate duplicates — they are also a classic fraud red flag (Section 10.5) |
| No-PO invoice | Maverick purchase bypassing process | Route through compliance channels; do not quietly legitimize it |
The Resolution Workflow
- Identify and classify the exception from the match report.
- Establish facts: PO terms, receipt evidence, contract price, and communications.
- Fix the transaction: corrected invoice, credit memo, receipt booking, or payment release.
- Fix the root cause: price-master governance, ECN discipline, receiving SLA, catalog maintenance — otherwise the same exception recurs monthly.
- Communicate the resolution to the supplier's AR contact and internal AP so both ledgers agree.
3. Payment Timeliness as an SRM Lever
- Contract compliance: payment terms are contract terms; chronic late payment can itself be a breach.
- Customer-of-choice effects: suppliers ration capacity, service, and innovation toward customers who pay predictably (Section 5.1).
- Working-capital balance: legitimate term extensions are negotiated (Sections 3.3, 3.5), not achieved by silently paying late.
- Supply chain finance: approved early-payment programs can give cash-strapped suppliers liquidity at the buyer's credit cost — a structured alternative to unilateral term stretching.
CPSM Exam Focus
Expect a blocked-invoice or mismatch scenario. The credited answer verifies facts against the PO/receipt/contract first, fixes the specific mismatch, pays the correct amount on time, and closes the upstream process gap. Answers that 'just pay it' or 'just reject it' skip the investigation step.
4. Engineering Change Notice (ECN) Discipline
The single most expensive liaison failure is the uncontrolled engineering change. Sound ECN practice between buyer and supplier:
- Written ECN with revision level, effective date/serial-effectivity (cut-in point), and disposition of existing inventory (use-as-is, rework, scrap).
- Supplier acknowledgment confirming the revision, quoting any cost/lead-time impact, and certifying which revision open orders will deliver.
- Synchronized systems: the revision updates PLM, ERP drawings, open POs, and incoming-inspection criteria simultaneously — the failure mode in Section 5.5's scenario is one channel moving without the others.
- Obsolete-revision control: old drawings are withdrawn or watermarked; suppliers building to a superseded revision without an ECN deviation produce nonconforming goods at their own risk.
5. Payment Terms as Working Capital — A Numbers Illustration
Extending terms with a cooperative supplier from Net 30 to Net 60 on $24M of annual spend frees approximately $24M × (30/365) ≈ $1.97M of cash on a continuing basis (Section 13.3). The liaison's job is to make that a negotiated, documented outcome — ideally traded for value the supplier wants (longer agreement, volume commitment, forecast sharing) — rather than an unlegislated pay-late habit that erodes trust, invites supply deprioritization, and can breach the very contract the procurement team negotiated.
AP blocks a $212,000 invoice: the supplier billed 4,000 units at the correct contract price, but the ERP shows only 3,400 units received. The supplier's POD signed by the buyer's dock shows 4,000 units unloaded. What should the supply manager do FIRST?
A supplier complains that every invoice since the January price renegotiation is being short-paid: AP pays the old price because the ERP price master was never updated, and the supplier must issue monthly credit-and-rebill cycles. What is the correct resolution?
Engineering issued Revision C of a drawing to the supplier by email, but the planner's scheduled releases still referenced Revision B from the ERP. The supplier produced 8,000 Revision B parts now rejected at incoming inspection. Which liaison failure caused this, and what prevents recurrence?