Invoice exception

Exceptions protect cash and audit integrity. Rather than paying and clawing back, AP parks the invoice until the facts align. Each exception should carry a reason code: price variance, quantity variance, missing PO, missing receipt, tax mismatch, duplicate suspect, or non-PO spend.

Reason codes power dashboards: if 40% of holds are "receipt not posted," the fix is operational receiving, not more AP headcount.

AP triages but usually cannot fix root data. Buyers adjust POs; receivers post GRNs; requesters confirm services; contract owners confirm rates. SLAs and escalation prevent invoices from aging past supplier terms.

Good workflow tools attach images of the invoice, PO snapshot, and receipt lines so resolvers do not re-key data.

Invoice line shows 10 units at $120 ($1,200). PO allows 10 at $115 ($1,150). A 1% price tolerance on $115 is $1.15; the $5 per unit gap ($50 total) exceeds tolerance. Exception routes to the buyer to accept a contract-driven price change or reject the overrun.

Upstream fixes beat downstream firefighting: accurate POs from catalog, timely receipts, supplier portal validation, and contract rate feeds. Machine-assisted capture reduces typos on PO numbers.

Track touch time per exception and dollars on hold; prioritize suppliers or categories with repeat patterns for quarterly business reviews.

Use reason codes consistently and review top five codes each month with process owners. Attach PO, receipt, and contract excerpts to the exception record so resolvers do not re-query ERP.

Measure aging buckets and escalate per bucket. After resolution, feed root cause into supplier scorecards and catalog updates.

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 invoice exceptions 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 invoice exceptions 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 invoice exceptions 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 invoice exceptions 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 invoice exceptions 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 invoice exceptions issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.