Best Practices for Handling Invoice Exceptions

A company processing 500 invoices a month with a 20% exception rate has 100 invoices every month that cannot be processed automatically. At 45 to 60 minutes of AP team time per exception, that’s up to 100 hours monthly spent on investigations, vendor calls, and rework.

That’s the equivalent of more than two full working weeks, every month, on invoices that could have been clean with the right vendor onboarding and PO discipline in place.

The indirect costs compound it: delayed payments strain vendor relationships, early payment discounts are missed, and cash flow forecasting becomes unreliable when a significant portion of payables are stuck in exception queues.

Most exceptions are predictable, preventable, and processable. The ones that aren’t can be handled in a fraction of the time with a structured resolution workflow. This guide covers both.

What Is an Invoice Exception?

An invoice exception is any invoice that cannot be processed automatically because it contains an error, discrepancy, or missing information that requires human intervention.

Exception Type	Description	Frequency
PO mismatch	Invoice amount, quantity, or line items don’t match the PO	Very High
Missing PO reference	Invoice received without a valid PO number	High
Incorrect TDS deduction	TDS not deducted, wrong section applied (194C vs 194J), or rate incorrect	High (India)
GSTIN mismatch	GSTIN on invoice doesn’t match vendor master or billing entity	High (India)
Missing or invalid IRN	e-Invoice IRN absent or not validated for vendors above ₹5Cr turnover	Medium-High (India)
Duplicate invoice	Same invoice submitted more than once	Medium
Vendor not in system	Invoice from unapproved or unregistered vendor	Medium
Incorrect GST calculation	GST rate or amount calculated incorrectly	Medium
Wrong entity or address	Invoice billed to wrong legal entity or branch	Low-Medium
Currency or exchange mismatch	For international vendors, FX rate disagreements	Low

The three India-specific exception types in the middle of this table deserve particular attention. TDS deduction errors create a tax liability that falls on the buyer, not the vendor. A missing IRN on an e-invoice from a vendor above the ₹5 crore threshold means the invoice is not GST-compliant and the ITC claim will fail. GSTIN mismatches between the invoice and vendor master are among the most common causes of GSTR-2B reconciliation failures. None of these are caught by standard global AP automation tools without India-specific configuration.

Prevention: The First Line of Defence

The cheapest exception is the one that never happens. The majority of exception volume traces back to two root causes that are fixable before the first invoice arrives.

1. Vendor onboarding gaps

Most exceptions originate here. A vendor who doesn’t know your PO reference requirement, correct billing entity, or invoice submission channel will invoice you incorrectly, consistently, until someone tells them otherwise.

Before processing a single invoice from any vendor, confirm in writing:

• The exact legal entity name and GSTIN to bill
• The mandatory PO reference requirement
• The correct invoice format (including TDS and GST line item requirements)
• The submission channel (portal, dedicated AP email)
• What happens to invoices submitted incorrectly (they will not be processed)

For a full vendor onboarding framework, see our Vendor Onboarding Checklist.

2. PO discipline

A “no PO, no pay” policy with defined exceptions (utilities, rent, statutory payments) eliminates the majority of missing reference exceptions. Two additional disciplines matter:

• POs must be raised before goods or services are received, not after the invoice arrives
• PO line items must be specific enough to match against invoice line items. A PO for “consulting services at ₹2L” that gets invoiced as three separate line items will exception every time

For a detailed guide on PO types and when to use each, see our Guide to Purchase Order Types.

3. Supplier portal

A self-service portal where vendors submit invoices in your required format, check PO status, and track payment eliminates most formatting and reference errors before the invoice reaches the AP queue. Vendors who can see their invoice status don’t call to chase payment.

Detection: Catching Exceptions Early

The faster an exception is identified, the cheaper it is to resolve. An exception caught at submission takes minutes to fix. The same issue caught after an invoice has been approved and queued for payment can take hours.

Automated 3-way matching: match invoice line items against PO and GRN automatically. Route only genuine discrepancies for human review, not every invoice that needs a second look.

OCR and data extraction at submission: extract invoice data the moment it arrives. Catch missing fields, invalid GSTINs, and absent PO references before the invoice enters the processing queue.

Duplicate detection: check vendor, invoice number, and amount combinations against at least 18 months of payment history. Duplicate submissions are often innocent (vendor resends after chasing) but occasionally fraudulent.

Rules engine with tolerance bands: configure acceptance thresholds so invoices within a defined variance of PO value (typically 2 to 3%) process automatically without exception routing. Not every ₹50 rounding difference needs human review.

IRN validation: for vendors above the ₹5 crore e-invoicing threshold, validate the Invoice Reference Number against the IRP portal at submission. An invalid or missing IRN should exception immediately, not after the invoice has been approved.

Resolution: A Structured Workflow

When an exception is identified, structure matters. An unstructured exception queue where invoices sit until someone picks them up is the most common AP bottleneck.

1. Classify and assign immediately

Each exception type should have a defined owner before the exception ever occurs:

• PO mismatch: Procurement team to confirm or amend
• Missing PO: Budget owner to provide or raise retrospectively
• TDS error: AP team to calculate correct deduction and notify vendor
• Vendor master issue: AP or Finance ops to resolve same day
• Tax or IRN issue: AP team with vendor support

2. Set SLAs by exception type

Exception Type	Resolution SLA
Missing PO reference	1 business day
PO mismatch (minor, within tolerance)	Same day
PO mismatch (material)	2 business days
TDS deduction error	2 business days
Vendor master or GSTIN issue	Same day
IRN validation failure	1 business day
Duplicate invoice	Same day

3. Notify vendors proactively

The moment an exception is created, the vendor should receive an automated notification specifying exactly what is wrong and what action is required from them. A clear, specific message prevents the inevitable payment chasing call and gives the vendor the information they need to resubmit correctly.

A good exception notification includes: the invoice reference, the specific error, the action required from the vendor, and the expected resolution timeline. A generic “your invoice has been rejected” notification creates more calls, not fewer.

4. Document every exception and resolution

The audit trail matters for two reasons: vendor disputes (proof of what was wrong and when the vendor was notified) and process improvement (the data you need to identify which vendors and exception types are driving volume).

5. Escalate automatically on SLA breach

Any exception that exceeds its SLA without resolution should auto-escalate to the AP manager. Exceptions that sit in a queue without a deadline are exceptions that never get resolved.

Continuous Improvement: Exception Analytics

Exception handling is not a static process. The metrics tell you where the process is breaking.

Track monthly:

• Exception rate by vendor: vendors with consistently high rates need retraining, a formal review meeting, or in persistent cases, a commercial conversation about whether the relationship is worth the AP overhead
• Exception rate by type: a spike in a specific type signals a process or system issue, not a vendor issue
• Average resolution time by type: identifies bottlenecks in your workflow and SLA compliance
• Re-exception rate: this is the metric most teams don’t track, and the most instructive one. An invoice that gets corrected and exceptions again means the root cause was never addressed, only the symptom. High re-exception rates on a specific vendor or exception type point to a communication failure, not a processing failure

Best-in-class AP operations achieve exception rates below 5%. If your rate is above 15%, the problem is upstream: fix vendor onboarding and PO compliance before investing in automation. Automating a broken process makes it faster, not better.

How open.money Handles Invoice Exceptions

Open’s AP automation module is built around the reality that exceptions are inevitable but manageable, and that the cost of exceptions scales with how long they sit unresolved.

• OCR extraction at submission: invoice data captured the moment it arrives, missing fields flagged before the invoice enters the queue
• Automated 3-way matching: invoice matched against PO and GRN automatically; only genuine discrepancies routed for review
• India-specific validation: GST rate checking, GSTIN verification against vendor master, IRN validation for e-invoice-eligible vendors, and TDS section verification at the invoice level
• Duplicate detection: vendor, invoice number, and amount checked against 18 months of payment history
• Exception classification and routing: each exception classified by type and assigned to the correct owner automatically, with a clear description of the discrepancy
• Automated vendor notifications: vendor receives a specific, actionable notification the moment an exception is created
• Live exception dashboard: aging analysis, SLA tracking, and exception rate by vendor and type visible to the AP manager in real time

Finance teams using Open’s AP module report measurable reductions in exception volume within the first 90 days, primarily driven by the vendor portal reducing formatting and reference errors at source.

Frequently Asked Questions

1. What is an acceptable invoice exception rate?

Best-in-class AP operations run exception rates below 5%. A rate between 5% and 15% is common but indicates room for improvement in vendor onboarding or PO discipline. Above 15% consistently signals a systemic process problem that automation alone will not fix. Start with vendor communication and PO compliance before investing in additional tooling.

2. What is the difference between an invoice exception and an invoice rejection?

An exception is an invoice that cannot be automatically processed and requires human intervention to resolve. It stays in the queue while the issue is investigated. A rejection is a final determination that the invoice cannot be accepted and must be resubmitted by the vendor. Exceptions should be resolved where possible; rejections should be communicated clearly and quickly so the vendor can resubmit correctly.

3. How do you handle recurring exceptions from the same vendor?

A single exception is a processing issue. Three or more exceptions of the same type from the same vendor is a communication failure. The fix is a direct conversation with the vendor’s accounts team, a written summary of the specific requirements they are repeatedly missing, and a clear statement that continued exceptions will delay payment until the issue is resolved. Document the conversation. If exceptions persist after formal communication, it is a commercial relationship issue.

4. What causes TDS-related invoice exceptions in India?

The most common causes: the vendor applies the wrong TDS section (194C for contractors vs 194J for professional services is a frequent confusion), the TDS rate is calculated on the gross amount when it should apply to the taxable amount only, or the vendor doesn’t deduct TDS at all because they believe their turnover exempts them from it. The buyer is ultimately responsible for correct TDS deduction and deposit. An incorrect TDS deduction on a vendor invoice creates a liability for the buyer, not just an accounting error. TDS profiles configured at vendor onboarding prevent most of these at source.

5. Should invoice exceptions be approved or rejected before the vendor is notified?

Notify the vendor as soon as the exception is identified, not after the AP team has completed its internal review. Early notification gives the vendor time to gather information or prepare a corrected invoice while the AP team investigates. Waiting until internal review is complete adds days to the resolution cycle without any benefit. The notification should be specific about what is wrong; a generic rejection message is not useful to the vendor and generates a follow-up call.