AP Exception Resolution: A Complete Guide

What Are AP Exceptions?

An AP exception occurs when an invoice cannot be processed automatically because it fails one or more validation checks. These checks include 3-way matching (PO vs. GRN vs. invoice), duplicate detection, tax verification, missing data fields, or policy violations.

Invoices that pass all checks are "touchless," flowing from receipt to payment-ready without human intervention. Invoices that fail become exceptions, requiring manual investigation before they can proceed.

The problem isn't that exceptions exist. Some level of exception handling is a sign of healthy controls. The problem is that exception resolution is where AP team time actually disappears, and most automation tools are optimized for the happy path, not the exception path.

Why Exceptions Matter More Than You Think

The downstream effects of unresolved exceptions compound quickly:

For a deeper look at why this happens in practice, see Why Invoice Automation Stalls Once Exceptions Take Over.

The Exception Resolution Process

Step 1: Detection

The system flags an invoice that fails a validation check. Common triggers:

• Quantity mismatch: Invoice shows 100 units, GRN shows 95 received.
• Price variance: Unit price differs from the PO by more than tolerance.
• Missing PO: Invoice references a PO that doesn't exist or has been closed.
• Duplicate signal: Invoice number, amount, or vendor pattern matches a recent payment.
• Tax discrepancy: Calculated tax doesn't match the invoiced tax amount.
• Missing data: Required fields (vendor tax ID, cost center, GL code) are blank or invalid.

Step 2: Classification

Not all exceptions are equal. Effective exception management classifies by:

• Severity: Blocking (cannot process) vs. warning (can override with justification).
• Type: Matching, data quality, compliance, duplicate.
• Resolution owner: AP team, procurement, budget owner, vendor.
• Historical pattern: First occurrence vs. recurring issue with this vendor.

Step 3: Investigation

The AP specialist reviews the exception against source documents. This is where time is consumed:

• Pulling up the original PO and comparing line items
• Checking the GRN for partial delivery notes
• Contacting the vendor for clarification on pricing changes
• Reaching out to internal teams for budget or GL code confirmation
• Reviewing prior invoices from the same vendor for pattern context

Step 4: Correction

Once the root cause is identified, the resolution path depends on the exception type:

• Data correction: Fix the GL code, cost center, or tax amount and resubmit.
• Tolerance override: Approve the variance with documented justification.
• Credit request: Ask the vendor for a credit note or corrected invoice.
• PO amendment: Update the PO to reflect agreed price or quantity changes.
• Rejection: Reject the invoice as a genuine duplicate or unauthorized charge.

Step 5: Re-routing

The corrected invoice re-enters the approval workflow and proceeds to payment. The resolution should be documented for audit trail and pattern analysis.

Common Root Causes

Understanding why exceptions occur is more valuable than just fixing them faster:

Vendor-side issues (40-50% of exceptions)

• Incorrect pricing on invoices (doesn't match contracted rates)
• Duplicate submissions (same invoice sent via email and portal)
• Missing or incorrect tax information
• Invoice format changes that break automated data extraction

Internal process gaps (30-40% of exceptions)

• POs not created before ordering (no-PO invoices)
• GRNs not recorded promptly (goods received but not logged)
• Verbal approvals for price or scope changes not reflected in the PO
• Budget codes or cost centers entered incorrectly by requesters

System configuration issues (10-20% of exceptions)

• Tolerance thresholds set too tightly, flagging trivial variances
• Vendor master data inconsistencies (duplicate vendor records, outdated tax IDs)
• Matching rules that don't account for freight, tax, or currency rounding

How to Reduce Exception Rates

The most effective approach is upstream prevention, not faster resolution:

1. Enforce PO discipline

Require POs before ordering. No-PO invoices are the single largest source of exceptions because there's nothing to match against.

2. Configure tolerances appropriately

Review your invoice tolerance settings quarterly. If the same type of minor variance keeps generating exceptions that are always approved, the tolerance is too tight.

3. Standardize vendor onboarding

Capture correct tax IDs, payment terms, and contact information upfront. Validate against government databases at registration, not at invoice time.

4. Close the GRN gap

Work with operations to record goods receipts promptly. A 24-hour GRN target eliminates the most common matching delay.

5. Analyze patterns, not just individual exceptions

Track exception rates by vendor, category, and type. If 60% of your exceptions come from 5 vendors, the fix is a vendor conversation, not a faster exception queue.

6. Automate resolution where possible

AI-powered systems can auto-resolve common exceptions: rounding differences within tolerance, known partial delivery patterns, and duplicate submissions with matching invoice numbers.

When to Automate Exception Handling

Manual exception resolution works when volume is low and patterns are unpredictable. Automation becomes essential when:

• Exception volume exceeds what your team can process without delays
• The same types of exceptions recur weekly from the same vendors
• Month-end close is regularly extended due to unresolved exceptions
• Your team spends more time on investigation than on analysis

For the broader context on how exception handling fits into the AP automation stack, see AP Automation 101: The Complete Guide.

FAQ

What is a good AP exception rate?

Industry benchmarks suggest 15-25% is typical for partially automated environments. Best-in-class teams achieve under 10% through upstream prevention (PO enforcement, vendor data quality, appropriate tolerances). Zero exceptions isn't the goal; some level of exception handling is a sign of healthy controls.

How long should exception resolution take?

Target resolution within 48 hours for standard exceptions, same-day for high-value or time-sensitive invoices. If average resolution time exceeds 5 days, investigate whether the root cause is process (missing information), people (insufficient staffing), or system (poor exception routing).

What's the difference between an exception and a rejection?

An exception is an invoice that needs investigation before it can be processed. A rejection is a final determination that the invoice should not be paid (e.g., confirmed duplicate, unauthorized purchase, fraudulent submission). Most exceptions are resolved and eventually paid; rejections are returned to the vendor.

How do exceptions affect month-end close?

Unresolved exceptions at month-end require accrual estimates, which add manual work and reduce accuracy. Companies with high exception backlogs often extend close by 2-4 days just to clear the queue. Real-time exception resolution throughout the month is the most effective way to compress close cycles.