An invoice exception is a discrepancy, missing item or failed control that prevents an invoice from moving through its normal validation, approval or payment path. The exception is not the invoice itself; it is the specific condition that requires investigation, correction or authorized acceptance.
What causes invoice exceptions?
- Missing or invalid purchase order
- Price, quantity, tax or currency mismatch
- Receipt or service-acceptance evidence not recorded
- Duplicate invoice number or suspected duplicate charge
- Supplier details that differ from the approved vendor record
- Approval, coding or budget information that is incomplete
How should an exception be handled?
- Identify the failed rule and preserve the original invoice.
- Route the exception to the owner able to verify the underlying fact.
- Obtain corrected evidence, a supplier credit or authorized variance.
- Record the decision and update the invoice status.
- Return the invoice to the controlled workflow without bypassing prior checks.
Invoice exception vs. invoice dispute
An exception is an internal workflow condition that blocks processing. A dispute is a disagreement between parties about the charge, goods, service or contractual obligation. One event can be both: a price mismatch may create an internal exception and prompt a supplier dispute.
What should exception reporting measure?
Track exception type, source, owner, age, resolution and repeat frequency. A high exception rate may point to weak purchase-order data, supplier onboarding, receiving discipline or invoice capture. Counting only closed exceptions can hide the value and age of unresolved invoices.
