Why exceptions define the process
Most AP effort sits in exceptions. If you only design the happy path, you design a brochure, not an operation.
P2P
10 min read
The P2P Exception Matrix Starter Kit
Happy path is not enough. Design the exception matrix that AP actually lives in — holds, mismatches, and approvals.
Insight article from the Kavya Project knowledge library. Educational content only — not employment history or certification claims.
Core exception types
Price/quantity mismatch, missing receipt, duplicate invoice, incomplete supplier data, tax mismatch, coding errors, approval timeout.
For each exception define four things
Detection signal, owner, resolution path, and time SLA. Without SLA, exceptions age quietly into close risk.
Holds are controls, not punishments
Train users on why a hold exists. Provide a clear release checklist. Mystery holds create shadow process.
UAT must include negatives
Duplicate invoice, over-receipt, and forced override scenarios prove the design. Capture evidence for each.