Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian manufacturer's three-way match exception queue runs at 60-75% of invoices, ages into the 60-90+ day buckets, breaches MSME Section 43B(h) deadlines, and risks ITC claims crossing the Section 16(4) deadline — but the AP team cannot work the queue down because there is no priority routing, no tolerance configuration per vendor category, no escalation SLA, and no maker-checker on resolutions.
Bucket every open exception by ageing (0-30, 31-60, 61-90, 90+) and by priority (Critical/High/Medium based on MSME flag, invoice value, ITC deadline proximity); apply per-vendor-category tolerance bands at the matching engine to reduce inflow; route exceptions by variance code to a documented owner with an SLA; require maker-checker sign-off on every resolution with value-banded approval thresholds; trigger weekly aged-exception escalation to the finance head.
Ageing buckets, priority tier rules (MSME, value, ITC deadline), variance-code-to-owner routing map, SLA per priority tier, maker-checker approval matrix by value band, write-off thresholds per variance code, and weekly escalation report to finance leadership.
A daily AP dashboard showing exceptions by bucket and priority, MSME 43B(h) breach alerts, ITC at-risk alerts, an owner accountability view, a write-off log with GL posting trail, and a monthly trend chart showing exception rate decline from 70% baseline toward sub-15% target.
A finance manager at a precision engineering company in Pune opens the AP exception report on the first of May and counts 1,041 open exceptions across the queue — 318 invoices in the 30-60 day bucket, 187 in the 60-90 day bucket, 124 beyond 90 days, and 412 in the recent 0-30 day bucket. Of the 90+ day pile, 23 are MSME vendors already past the Section 43B(h) 45-day window. Eight of the 60-90 day items carry March-dated invoices whose ITC must be claimed by 30 September or be lost under Section 16(4) of the CGST Act. AP exception management India done well is not glamorous work, but it is the only path from the 60-75% industry-norm exception rate to a sub-15% rate. This guide covers the operational discipline.
What AP exception management is
AP exception management is the day-to-day work of taking the output of three-way matching — the invoices that fail to clear automatically — and resolving them within documented SLAs, with the right ownership, the right approval trail, and a written-off vs pursued decision on every variance. At an Indian manufacturer it sits between procurement, stores, quality, vendor management, finance, and tax. The discipline is not about reducing the matching engine’s output of exceptions (that is the matching engine’s job — see PO-GRN-invoice three-way matching in India); it is about working what comes through the engine to resolution before it ages.
Exception ageing
Every open exception has an age, calculated from the date the invoice was first booked against the GRN. The standard ageing buckets at Indian manufacturers are:
| Bucket | Days | Typical population at baseline | Risk |
|---|---|---|---|
| Fresh | 0-30 days | 40-50% of queue | Manageable; in-process resolution |
| Ageing | 31-60 days | 25-30% | MSME 43B(h) clock active |
| Aged | 61-90 days | 15-20% | Vendor traction declining; relationship strain |
| Stale | 90+ days | 10-15% | ITC at risk, escalation required |
The 90+ bucket is the most damaging part of the queue. These are usually disputes that have lost vendor engagement, MSME 43B(h) breaches that have already happened (triggering Income Tax Act 2025 disallowance of the expense for the year), and ITC claims that may now be time-barred under Section 16(4) of the CGST Act — credit for FY24-25 invoices must be claimed by 30 November 2025 (per recent amendments) or by filing of annual return, whichever is earlier. Driving the 90+ bucket toward zero is the highest-impact control finance can run.
Priority routing
Not every exception is equal. A ₹12 lakh invoice from an MSME vendor with 38 days on the 45-day clock is materially different from a ₹47,000 RATE_VARIANCE on a commodity item with 8 days of age. Priority routing tiers the queue:
Critical — Must clear within 48 hours.
- MSME vendors approaching the 45-day Section 43B(h) window (within 7 days of breach)
- Single line items above ₹10 lakh
- ITC claims approaching the Section 16(4) deadline (within 30 days)
- VENDOR_PAN_MISMATCH on the next payment run
High — Must clear within 5 working days.
- Any item in the 31-60 day bucket
- OVER_INVOICED exceptions above the documented tolerance band
- GST_MISMATCH cases (these affect ITC directly)
- Quality-hold items past the documented Q-hold window
Medium — Must clear within 15 working days.
- Standard 0-30 day RATE_VARIANCE within or near tolerance
- PARTIAL_QTY waiting on second-lot GRN
- UNDER_INVOICED (small auto-accept cases pending vendor follow-up)
Each tier has its own dashboard view and its own escalation path. The Critical tier is on the finance head’s daily report; the High tier is on the AP manager’s daily report; the Medium tier is on the AP team-lead’s queue.
Tolerance configuration per vendor category
Reducing exception inflow is as important as resolving the existing backlog. The matching engine’s tolerance bands should be set per vendor category, not globally:
- Engineered components (precision parts, electronics, brand-specified items): price tolerance 0%, quantity tolerance 0%, GST 0%
- Raw materials, stable price (chemicals, packaging, fasteners): price tolerance 2%, quantity tolerance 1%, GST 0%
- Commodity-indexed (steel, copper, polymer, fuel): price tolerance 5%, quantity tolerance 2%, GST 0%
- Bulk weighed at gate (scrap, ore, aggregate): price tolerance 2%, quantity tolerance 3%, GST 0%
- Services / contractor work (under Section 393(1)(a), payment code 1002): price tolerance per contract, GST 0%, TDS code verification mandatory
A factory running a single global 3% / 3% tolerance band will overload its queue with engineered-component exceptions that should have been zero-tolerance, while quietly passing scrap variances that should have been investigated. The configuration must reflect the commercial reality of each category. For the full configuration framework, see PO-GRN-invoice three-way matching in India.
Escalation workflow
Every exception has an owner determined by its variance code:
| Variance code | Owner | Escalation after SLA |
|---|---|---|
| RATE_VARIANCE | Purchase head | Finance head at day 7 |
| PARTIAL_QTY | Stores in-charge | AP manager at day 5 |
| GST_MISMATCH | Tax / GST cell | Finance head at day 3 |
| VENDOR_PAN_MISMATCH | Vendor master / onboarding | AP manager at day 2 |
| OVER_INVOICED | Purchase head | Finance head at day 5 |
| UNDER_INVOICED | AP clerk | AP manager at day 10 |
The escalation rule is not punitive — it is the mechanism by which aged exceptions surface to the next level of decision-making before they cross the MSME or ITC clock. Weekly, the AP manager produces an aged-exception report for the finance head: total open, distribution by bucket, items breaching SLA, items approaching MSME 43B(h) breach, items approaching ITC deadline. The finance head’s review converts pending items into actions: escalate to vendor MD, raise debit note, write off within threshold, or accept and pay.
Maker-checker on resolved exceptions
Every resolution must pass through a maker-checker control, with approval thresholds banded by value:
- Up to ₹2 lakh per invoice — AP clerk (maker), AP manager (checker)
- ₹2 lakh to ₹10 lakh — AP manager (maker), finance head (checker)
- Above ₹10 lakh — finance head (maker), CFO (checker)
The control matters because resolution often involves a tax-relevant decision: writing off a variance affects expense recognition under Section 393, raising a debit note affects GST output liability, approving a rate variance affects the Section 393 TDS new Income Tax Act reconciliation base. ICAI Standards on Auditing — see the Institute of Chartered Accountants of India — require segregation of duties on AP processing, and the maker-checker pattern is how that requirement gets operationalised.
Write-off thresholds
Some variances are not worth pursuing. Documented write-off thresholds keep the queue clean:
- Rate variances below ₹500 per invoice line on commodity-indexed items where the index has moved between PO and invoice
- Quantity variances below 0.5% on bulk weighed-at-gate material
- GST rounding-off differences within ₹10 per invoice
- Aged exceptions beyond 180 days where the vendor has not responded to three documented follow-ups
Every write-off must be approved by the checker, posted to a specific GL account (“Procurement variance — within tolerance” or “Aged AP write-off”), and tracked monthly for trend analysis. A spike in write-offs on a specific vendor or item category is a signal that the underlying tolerance band or contract terms need revision.
The path from 70% to under 15%
A realistic 90-day implementation profile for an Indian manufacturer moving from spreadsheet-based AP to a structured matching engine with the discipline above:
| Day | Exception rate | Action |
|---|---|---|
| Day 0 (baseline) | 60-75% | Spreadsheet matching, no tolerance bands, no priority |
| Day 30 | Under 25% | Vendor master cleaned, tolerance bands configured by category |
| Day 60 | Under 20% | GRN-side discipline in place (status codes, matching window) |
| Day 90 | Under 15% | Maker-checker live, aged-exception escalation working, write-off thresholds applied |
The match-rate improvement curve (51% → 88%) at the broader reconciliation level is consistent with what published customer outcomes show across reconciliation software India deployments. The manufacturing-specific instance of that curve, when delivered with three-way matching software India, is the AP exception reduction profile above.
For the broader umbrella of all five manufacturing reconciliation rails, see manufacturing reconciliation in India. For the GRN-side mechanics that feed this queue, see goods receipt note (GRN) reconciliation in India. For the broader reconciliation pattern view across industries, see the patterns library. For TDS-specific compliance on the codes that surface in exception resolution, see TDS payment codes 1001-1092 India.