Invoice Exception Rate

Invoice exception rate is the percentage of invoices that fail to complete normal processing without manual intervention. An exception occurs when an invoice triggers a hold, a validation failure, a coding query, a missing document flag, or any other condition that requires a person to review and resolve it before processing can continue. Exception rate is the inverse of the straight-through processing rate: an STP rate of 70 percent implies an exception rate of 30 percent.

Exception rate is important because exceptions are expensive. Every invoice that falls into an exception queue requires AP staff time to investigate, communicate with the supplier or internal stakeholder, resolve the underlying issue, and return the invoice to the processing workflow. In AP environments with high exception rates, a significant portion of total AP staff time is spent on exception management rather than on normal processing -- which is a key reason why cost per invoice in high-exception environments can be three to five times higher than in best-in-class environments.

Categories of AP exceptions and their root causes

The largest category of exceptions in most AP environments is purchase order mismatch: the invoice references a purchase order but the amount, quantity, or line item description does not match the PO within the configured tolerance. PO mismatch exceptions are caused by supplier invoicing errors, PO amendments that were not communicated to the supplier, or suppliers invoicing beyond the agreed scope. The root cause is almost always in the procurement process rather than the AP process -- better PO discipline upstream reduces PO mismatch exceptions downstream.

Missing information exceptions occur when the invoice lacks data required for processing: no ABN, no invoice number, a missing line item description, a total that does not reconcile to line items, or a missing cost centre reference. These are most common with suppliers that use manual or low-quality invoice software and with occasional suppliers who do not have a relationship with the business's standard invoicing requirements.

Duplicate detection holds are raised when an incoming invoice matches a recently processed invoice within the system's matching tolerance. Some of these are genuine duplicates; some are legitimate re-invoices after a credit note or payment dispute. Each requires human review to classify correctly. A high rate of duplicate detection holds often indicates a supplier-side invoice management problem that warrants a direct conversation.

Coding exceptions occur when the AP system cannot automatically assign an invoice to the correct account with sufficient confidence. This is most common for first-time suppliers, invoices with unusual line item combinations, or businesses with complex chart of accounts structures where multiple valid coding options exist for a single invoice type.

Reducing exception rate

Exception rate reduction requires working on both the AP process and the upstream processes that generate exceptions. Supplier communication programs that share invoice format requirements, PO referencing standards, and ABN requirements with new and occasional suppliers reduce formatting-related exceptions. Procurement process improvements that ensure POs are raised before invoices arrive and that PO amendments are communicated to suppliers before they invoice reduce PO mismatch exceptions. Improved coding rules and historical data in the AP system reduce coding exceptions over time as the system learns from manual coding decisions.

Monthly exception rate analysis by category and by supplier identifies the highest-impact improvement opportunities. If 40 percent of all exceptions come from five suppliers, addressing invoice quality with those five suppliers delivers more exception rate improvement than any system configuration change.