Single-source risk

Proprietary tooling, regulatory qualifications, long ramp times for alternates, or geographic concentration. Sometimes single-source is valid after qualification; risk is unmanaged dependence, not sole sourcing per se.

Qualify a second source even at higher unit cost, hold safety stock, negotiate escrow for IP or tooling, and embed exit assistance in contracts. Link backup RFQs in sourcing systems before crises.

Dollar spend, revenue at risk if supply stops, and time to switch. A $200k spend supplier can still be critical if switchover takes nine months.

One carrier handles 80% of inbound lanes; a cyber incident pauses bookings. Exposure spans $712k annual spend and open PO-1047—trigger backup RFQ and customer communication plans immediately.

Document why a sole source is qualified and when dual qualification will be attempted. Quantify time-to-switch, not only spend, when rating exposure.

Negotiate tooling escrow, spare inventory, or priority allocation clauses where dual source is impossible short term. Link contingency RFQs in sourcing tools before disruptions occur.

Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.

Internal audit samples single-source risk by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.

Leading indicators for single-source risk include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.

Pilot changes to single-source risk on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.

Technology helps single-source risk only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.

Stakeholder alignment matters: publish a one-page RACI for single-source risk that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.

Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear single-source risk issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.

Maintain a playbook with ERP screenshots and named examples updated after each release. Retain match packets, award memos, screening results, and approval history for the period your auditors expect so reconstructions do not depend on tribal knowledge.

Quarterly, sample three transactions and ask a new analyst to rebuild the decision trail without administrator access. If they cannot, fix attachments, naming, and workflow history before expanding automation or supplier self-service further.