Vendor Communications & Disputes
Your Accounts Payable team has been chasing the same invoice variance for three weeks. The vendor insists the price was agreed verbally. Your category manager disagrees. The emails back and forth have become increasingly defensive, and no one can find a clear record of what was agreed. Meanwhile, the invoice sits unpaid, the vendor is threatening to put your account on hold, and your operations team is asking whether the next delivery is at risk.
This situation is entirely avoidable. Every supplier relationship, at some point, produces a discrepancy — a price that does not match the PO, a delivery that falls short of the SLA, a contract nearing expiry with no decision made. What determines whether a discrepancy becomes a manageable administrative matter or a relationship-damaging dispute is not the size of the variance. It is the quality and speed of the communication.
The /vendor-communicate skill provides five communication templates for the five most common procurement scenarios. Each template is built on the same principle: state facts, reference specific data, state what you need, and state when you need it by. No blame, no emotion, no ambiguity. This lesson teaches when to use each type — and what the output should contain.
The Five Communication Types
Type 1: Invoice Dispute Notice
When to use: An invoice has a discrepancy that cannot be approved — a price that does not match the PO, a quantity invoiced that exceeds the goods receipt, or an unauthorised charge with no purchase order reference. Payment is held until the dispute is resolved.
The Invoice Dispute Notice is an accounting document. Its purpose is to trigger a specific resolution (credit note, revised invoice, or supporting evidence) within a defined timeframe, while confirming that the undisputed portion will be paid normally.
Required elements:
- Invoice number and date
- PO reference number
- Specific discrepancy with figures (invoiced vs. our records vs. variance amount)
- Contractual or PO basis for the disputed amount
- Required action (credit note / revised invoice / evidence)
- Deadline (typically 5 business days)
- Confirmation that undisputed amount will be processed on standard terms
Authority level: Category Manager sign-off
Type 2: Corrective Action Request (CAR)
When to use: A vendor's performance has breached a contractual KPI — on-time delivery below threshold, quality rejection rate above threshold, or another measurable SLA — and the breach has persisted beyond your informal escalation path. The CAR is a formal notice under the supply agreement requiring the vendor to produce a documented corrective action plan.
A CAR is not a complaint letter. It is a legal document that starts a clock. If the vendor fails to respond or fails to implement the plan, you have documented grounds for contract termination or compensation claims.
Required elements:
- CAR reference number (CAR-[Year]-[N]) — for tracking
- KPI name, contractual threshold, actual performance, shortfall
- Period covered with supporting data reference (ERP report, QMS record)
- Deadline for written corrective action plan (typically 10-14 calendar days)
- The four items the plan must address: root cause, containment actions already taken, corrective actions with target dates, monitoring approach
- Proposed review meeting date
- Contractual clause under which the notice is issued
Authority level: CPO sign-off
Type 3: Contract Non-Renewal Notice
When to use: You are exercising the right not to renew a contract upon expiry — because you are retendering, consolidating to another vendor, or ending the relationship for strategic reasons. The notice must be sent before the contractual notice deadline (typically 60-90 days before contract expiry).
Missing the notice deadline can legally extend the contract for a further full term — often 12 months. The Procurement Calendar Agent (Lesson 12) exists specifically to ensure this never happens. If you are approaching a notice deadline with no decision, that is a CPO-level escalation, not a category manager task.
Required elements:
- Contract reference and agreement date
- Contractual notice period and notice deadline date (must confirm sent before this date)
- Contract expiry date
- Confirmation that all POs issued before the notice will be honoured
- Request for transition support and timeline
- Positive close (where appropriate — preserve the relationship professionally)
Authority level: CPO sign-off, with Legal review recommended
Type 4: Emergency Supply Assurance Request
When to use: You have received a signal — financial news about the vendor, a restructuring announcement, disruption at one of their key raw material suppliers, or an industry event — that could potentially affect their ability to supply you. You are not certain there is a problem. You are asking the vendor to formally confirm there is not.
The Emergency Supply Assurance Request is a risk management tool, not a confrontation. Its purpose is to obtain written confirmation of supply capability on the record. If the vendor subsequently fails to supply, you have evidence that they formally confirmed capacity and the failure was unexpected.
Required elements:
- Brief, factual description of the triggering signal (no speculation, no accusation)
- Specific questions about production capacity, raw material inventory, and confirmed order fulfillment
- Response deadline (3-5 business days)
- Reference to the possibility of a follow-up call with senior management
Authority level: Category Manager or CPO, depending on vendor tier
Type 5: Vendor Exit Notice (Planned Transition)
When to use: You have made the decision to transition a category to a different vendor or supply model. This notice initiates the planned wind-down of the current relationship. It is distinct from a non-renewal notice (which exercises a contractual right) — an exit notice covers the transition mechanics: timeline, outstanding orders, and the recovery of any company-owned tooling, intellectual property, or documentation.
Before sending any exit notice, confirm what company-owned assets — tooling, moulds, specifications, intellectual property — are in the vendor's possession. The notice must include explicit requirements for their return by a specific date. Failing to address tooling recovery before exit can create legal disputes that outlast the commercial relationship by years.
Required elements:
- Decision to transition and the nature of the alternative arrangement
- Transition period and final purchase order date
- Fulfilment requirements through the transition period
- Explicit list of transition requirements: tooling return, IP transfer, documentation handover — each with a specific date
- Reference offer (where appropriate)
Authority level: CPO and Finance Director sign-off
Using /vendor-communicate
The /vendor-communicate command activates the vendor-communication skill. You specify the communication type and provide the relevant data — the skill formats the communication to the correct template standard.
Worked example — Invoice Dispute Notice.
You have received Invoice INV-2024-1147 from AlphaSteel Corp for £48,250. Your PO (PO-2024-0892) was for £46,800. The goods receipt confirms delivery matched the PO specification. The overage of £1,450 has no contractual basis.
/vendor-communicate type:"dispute-notice"
vendor:"AlphaSteel Corp"
contact:"James Holbrook, Finance Director"
invoice:"INV-2024-1147"
invoice-date:"2026-03-10"
invoice-amount:"£48,250"
po-reference:"PO-2024-0892"
po-amount:"£46,800"
goods-receipt:"GR-2024-1103 (confirmed delivery matches PO)"
discrepancy:"£1,450 overcharge — no contractual basis for variance"
required-action:"Credit note for £1,450"
deadline:"2026-03-20"
undisputed-amount:"£46,800"
What to verify in the output:
| Element | Check |
|---|---|
| Invoice number and date | Correctly referenced |
| PO reference | Included as the contractual basis |
| Discrepancy breakdown | Invoiced (£48,250) vs. PO (£46,800) vs. variance (£1,450) |
| Basis for dispute | GR confirmation that delivery matched PO |
| Required action | Credit note for specific amount |
| Deadline | Specific date, 5 business days |
| Undisputed payment | Confirmed for processing on standard terms |
The communication the skill produces will have the correct structure and professional tone. Your job is to verify that all the factual elements are present and accurate. The exact phrasing is less important than the completeness of the data references.
Worked example — Corrective Action Request.
Your OTD monitoring shows that PrecisionCast Ltd, a Bottleneck vendor, has delivered on time in only 71% of shipments over the past 8 weeks, against a contractual SLA of 92%.
/vendor-communicate type:"corrective-action-request"
vendor:"PrecisionCast Ltd"
contact:"Sarah Chen, Operations Director"
car-reference:"CAR-2026-004"
kpi:"On-time delivery"
contractual-sla:"92%"
actual-performance:"71% (8-week average)"
shortfall:"21 percentage points"
period:"2026-01-13 to 2026-03-10"
data-reference:"ERP goods receipt report GR-RPT-2026-Q1-W10"
plan-deadline:"14 calendar days"
review-date:"2026-04-01"
contract-clause:"Clause 8.3 of Supply Agreement dated 2024-06-01"
The output should produce a formal CAR document with the CAR reference number, performance data table, four-point plan requirements, and review meeting invitation. This document should be reviewed by the CPO before sending.
Communication Standards: What to Verify in Every Output
Regardless of communication type, verify these standards in every /vendor-communicate output:
| Standard | What to Check |
|---|---|
| Factual | All numbers, dates, and references are accurate — no estimates or approximations |
| Specific | PO number, invoice number, CAR reference — all cited explicitly |
| Actionable | The required action is unambiguous — there is no room for the vendor to ask "what do you need from us?" |
| Time-bound | A deadline is stated — not "as soon as possible" but a specific date |
| Proportionate | The tone matches the severity — a first dispute notice is not the same as a final notice before termination |
| Sign-off | The correct authority level has reviewed and signed before sending |
Tone Calibration
Every communication the skill produces will use professional, factual language. This is intentional — procurement communications should read like accounting documents, not like complaints.
| Wrong | Right |
|---|---|
| "We are disappointed with your continued failure to meet delivery targets" | "OTD against the 92% contractual SLA averaged 71% during the 8-week period to 10 March 2026" |
| "Your invoice is clearly wrong and we refuse to pay it" | "Invoice INV-2024-1147 contains a discrepancy of £1,450 not supported by PO-2024-0892 or goods receipt GR-2024-1103" |
| "We need this fixed immediately" | "Please provide a credit note for £1,450 by 20 March 2026" |
| "This is unacceptable and reflects poorly on your organisation" | "This notice is issued under Clause 8.3 of our Supply Agreement dated 1 June 2024" |
The left column gives the vendor an opening to dispute your process or tone rather than your substance. The right column leaves them only one option: address the specific data.
Try With AI
Reproduce: Apply what you just learned to a simple case.
Draft an invoice dispute notice for the following scenario:
Vendor: GlobalParts Ltd
Invoice: INV-2026-0551, dated 12 March 2026, amount £23,400
PO reference: PO-2026-0218, amount £22,000
Goods receipt: GR-2026-0412 — delivery confirmed 80 units as per PO
Discrepancy: £1,400 — vendor has invoiced 87 units; goods receipt confirms 80 units
Required action: Credit note for £1,400 (7 units × £200/unit)
Deadline: 5 business days from today
Undisputed payment: £22,000 to be processed on standard 30-day terms
The communication should be addressed to the vendor's Accounts team. Category Manager to sign.
What you are learning: The dispute notice formula — specific invoice reference, PO basis, quantity/price data, required action, deadline, undisputed payment confirmation. Every element that is missing gives the vendor room to ask a question rather than resolve the issue.
Adapt: Modify the scenario to match your organisation.
Think of an invoice discrepancy from your own organisation — or a
realistic one for your industry. Describe:
- The invoice amount and what was invoiced
- The PO amount and what was agreed
- The goods receipt confirmation (what was actually received/delivered)
- The discrepancy type: price variance, quantity variance, or unauthorised charge
- The required resolution
Draft an invoice dispute notice for this scenario. Then evaluate:
Does the output contain a specific PO reference? A specific variance
amount with basis? A clear required action with a deadline?
Adjust the prompt until the output meets all five standards.
What you are learning: Translating a real discrepancy into a structured dispute notice requires you to separate the facts from the frustration. The prompt structure forces that discipline.
Apply: Extend to a new situation the lesson didn't cover directly.
Your Vendor Health Monitor has flagged that one of your Strategic
suppliers (annual spend £2.4M, sole-source for a critical component)
has been mentioned in a financial news article reporting that their
parent company is under review for a potential sale.
No confirmation of supply impact yet. But this vendor has no backup
supplier and a 90-day qualification timeline for any alternative.
Draft the appropriate vendor communication for this scenario.
Then answer: What type of communication is this? What authority level
is required before sending? What specific written assurance are you
seeking?
What you are learning: The Emergency Supply Assurance Request is a pre-emptive risk tool — sent when there is a signal, not a confirmed problem. Knowing when to send it (and what to request) is a judgment call that balances relationship management against operational risk.
Flashcards Study Aid
Continue to Lesson 12: Persistent Agents & Schedule →