Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian Tier-1 component manufacturers carry significant unrecovered tail of OEM debit notes on their books each quarter. The debit notes arrive in distinct operational classes — quality reject, quantity short, raw-material price variance pending, fitment or modification pending, line-stop penalty, tooling amortisation — but get pooled into a single dispute queue, routed to the wrong OEM counterparty, evidenced with the wrong documents, and aged past the dispute window. The result is that disputable debit notes harden into write-offs, the Section 34 credit-note window closes leaving tax-neutral settlement impossible, and the finance team accepts a structurally lossy operating equilibrium where 60 to 80 per cent of debit-note rupees are simply absorbed.
Build a five-class classification matrix that names each OEM debit-note type with its evidence requirement, dispute window, and owner. Maintain a dispute documentation library so every class has the right artefacts attached at filing time. Operate a four-tier escalation route from SQA to plant finance to corporate AP to the CFO office with SLAs at each tier. Issue Section 34 GST credit notes within the GSTR-1 amendment window for any commercially conceded debit note. Track disputes in four ageing buckets with class-weighted recovery probabilities. Feed the OEM debit-note sub-register into the broader Discovered Money register and the quarterly audit-committee leakage pack.
Five-class classification matrix (quality, quantity, RMPV-pending, FOMP, line-stop, tooling amortisation) with evidence list, dispute window, and OEM-side owner per class. Dispute documentation library per class (rejection slip, QC report, ASN, GRN, weighbridge slip, line-stop notification, RMPV registration, engineering change order, tooling amortisation schedule). Four-tier escalation route (SQA, plant finance, corporate AP, CFO office) with SLAs at each tier. Section 34 GST credit-note workflow with GSTR-1 amendment cycle. Four ageing buckets (0-30, 30-60, 60-90, 90-plus) with class-weighted recovery probabilities. OEM debit-note sub-register feeding the broader Discovered Money register.
A live OEM debit-note dispute register with class, OEM counterparty, evidence status, dispute tier, ageing bucket, Section 34 credit-note status, and recovery state. A monthly recovery-rate report by class and by OEM. A quarterly OEM debit-note pack for the audit committee covering disputed value at start of quarter, rupees recovered, rupees moved to write-off, and trend versus prior quarters. An annual class-mix review that drives engineering change-order discipline, RMPV registration hygiene, and tooling amortisation contracting practice.
A finance head at a Pune-based Tier-1 component manufacturer sits with the plant CFO at the end of the September quarter. The debit-note ledger from the three OEM customers shows ₹3.6 crore booked in the quarter. The disputed pile from the prior three quarters sits at ₹11 crore. The team has been working the queue, but the recovery rate is hovering at 18 per cent, and the audit-committee chair has asked why a Tier-1 of this size is structurally absorbing two to three per cent of revenue as OEM deductions. The honest answer is that no one owns the queue by class, the evidence library is thin, the SQA-to-CFO escalation path is unwritten, and most of the disputed pile has already aged past the window where the OEM counterparty is willing to engage.
This article gives the operating model for the recovery: the five-class classification matrix, the documentation library, the escalation route, the Section 34 GST credit-note workflow, the ageing-bucket recovery probabilities, and the integration into the broader revenue-leakage recovery program. The umbrella framing is the Seven Classes framework on the Stop Revenue Leakage pillar; OEM debit-note recovery is a specialisation of class-5 short-settlement for Tier-1 manufacturers where OEM concentration is high.
Quick reference: the five OEM debit-note classes
| Class | Typical trigger | Year-one recovery band |
|---|---|---|
| Quality reject | OEM line-side or incoming-QC rejection on supplied component | 25 to 35 per cent |
| Quantity short | ASN vs GRN delta, weighbridge mismatch, partial dispatch | 50 to 65 per cent |
| RMPV-pending | Raw-material price variance indexation owed under contract | 70 to 85 per cent |
| FOMP — fitment or modification pending | Engineering change order or modification cost charged back | 35 to 50 per cent |
| Line-stop penalty | OEM assembly-line stoppage attributed to supplier shortage or defect | 20 to 30 per cent |
| Tooling amortisation | Disputed amortisation recovery against tooling investment | 60 to 75 per cent |
The five-class classification matrix
Every disputed OEM debit note must be assigned to one of these classes within seven days of receipt. The classification drives every subsequent step.
Quality-reject class. Definition: OEM-side QC inspection (incoming or line-side) flags a defective component, raising a rejection slip and a debit note for the supplied value plus any reverse-logistics cost. Evidence required: the OEM rejection slip, the supplier QA dispatch QC report for the same lot, the photographic record where available, and the AQL sampling plan. Dispute window: typically 30 to 45 days from rejection-slip date per most OEM supplier manuals. Owner inside the OEM: SQA (supplier quality assurance) lead for the part.
Quantity-short class. Definition: OEM GRN records a quantity less than the ASN (advance shipping notification) or invoice, and the OEM raises a debit note for the shortfall. Evidence required: the supplier-side ASN, the dispatch weighbridge slip where weight-based, the transporter LR, the GRN copy from the OEM, and the gate-pass log. Dispute window: 15 to 30 days from GRN date. Owner inside the OEM: plant finance with material-control input.
RMPV-pending class. Definition: the supplier is contractually owed a raw-material price variance indexation (typically steel, aluminium, copper, plastics) that has not yet been settled, and the OEM raises a debit note while the indexation is in registration. Evidence required: the RMPV contractual clause, the registered indexation formula, the index-source publication (JPC, LME, or contract-named source) for the period, and the prior settled RMPV trail. Dispute window: per the indexation cycle contractually defined, usually quarterly or monthly. Owner inside the OEM: program management or purchase finance.
FOMP class — fitment or modification pending. Definition: the OEM has incurred a modification or rework cost on the component to bring it to fitment specification and charges the cost back, usually because an engineering change order (ECO) is in flight but unsigned, or because the supplier executed the ECO at a different revision than the OEM expected. Evidence required: the ECO trail, the drawing revision at dispatch, the dispatch quality certificate referencing the revision, and any engineering correspondence. Dispute window: 30 to 60 days from modification-cost notification. Owner inside the OEM: program management with engineering input.
Line-stop class. Definition: the OEM attributes an assembly-line stoppage to a supplier shortage or defect and raises a penalty debit note. Evidence required: the line-stop notification with timestamp, the supplier dispatch record for the part-number on the same date, the inventory snapshot at the OEM consignment location if applicable, and any prior shortage warnings. Dispute window: 15 to 30 days from notification. Owner inside the OEM: plant manager and corporate AP.
Tooling amortisation class. Definition: the OEM disputes a tooling amortisation recovery (per-piece recovery against an upfront tooling investment) by claiming under-utilisation, end-of-life, or model-change. Evidence required: the tooling-investment contract, the amortisation schedule, the production volumes versus contracted volumes, and the model-change correspondence. Dispute window: 30 to 90 days depending on the contractual structure. Owner inside the OEM: tooling controllership.
The dispute documentation library
A class is only as recoverable as the evidence packaged with the dispute. The documentation library is the single largest leverage point in OEM debit-note recovery — it converts a class assignment into a defensible filing.
Standard artefacts to maintain at the dispatch unit. Rejection-slip register cross-indexed by OEM, part-number, and date. Supplier QA dispatch QC report for every lot, retained for at least two years. Weighbridge slip and dispatch LR scanned at dispatch gate. ASN copy filed against the GRN on receipt. Drawing-revision-at-dispatch log indexed to part-number and dispatch date. Line-stop notification register with timestamp and OEM acknowledgement. RMPV registration document with effective date and source-index publication trail.
Class-specific evidence packs. For quality reject: rejection slip, QA dispatch QC, photographic record, AQL plan, prior acceptance history for the part. For quantity short: ASN, weighbridge, LR, GRN, gate-pass. For RMPV-pending: contract clause, registration, source-index publication, prior settlement trail. For FOMP: ECO trail, drawing revision at dispatch, dispatch QC referencing revision, engineering correspondence. For line-stop: notification with timestamp, dispatch record, consignment inventory snapshot, prior warnings. For tooling amortisation: contract, amortisation schedule, volumes, model-change correspondence.
A Tier-1 with a mature library files disputes within 7 to 10 days of debit-note receipt; a Tier-1 without one files at 25 to 40 days, by which point the recovery probability has already halved.
The escalation route — SQA to CFO office
A four-tier escalation route with named SLAs at each tier. The tier shift happens on a calendar trigger, not when the controller “gets around to it”.
Tier one — SQA. Quality-reject and FOMP classes start here. The filing is routed to the OEM SQA lead for the part. SLA at this tier: 15 to 20 working days for the SQA to confirm the rejection or reverse it. If no movement, escalate.
Tier two — plant finance. Quantity-short and line-stop classes start here; quality-reject and FOMP classes escalate here from SQA. The filing is routed to the OEM plant finance controller. SLA at this tier: 15 working days for confirmation or reversal. If no movement, escalate.
Tier three — corporate AP. All classes can land here. The filing is routed to the OEM corporate accounts payable head or the supplier finance head at the OEM headquarters. SLA at this tier: 20 working days. RMPV-pending and tooling amortisation classes often skip directly to this tier when the contractual anchor is corporate rather than plant.
Tier four — CFO office. Reserved for high-value disputes (typically above ₹50 lakh per debit note) or pattern disputes (a single class repeatedly debited despite documented refutation). The filing goes from supplier CFO office to OEM CFO office through the key-account lead. SLA at this tier: a board-period or quarter-end deadline rather than a working-day count.
The discipline that matters: the tier shift is the controller’s job, not the salesperson’s job. The dispute does not sit at tier one until the relationship manager remembers to ask about it.
Section 34 GST credit-note action
When the dispute is commercially conceded — either at supplier admission or at OEM enforcement after escalation — the tax-side settlement runs through Section 34 of the CGST Act. The supplier issues a credit note for the original invoice value being reversed, declares it in the next GSTR-1, and the OEM reverses the corresponding input tax credit it had claimed.
The operating constraint is the time window. A Section 34 credit note can be issued up to the September following the financial year of the original invoice, or the date of filing the annual return for that year, whichever is earlier. A commercially conceded debit note from a March invoice has a credit-note window that closes by the September of the next financial year at the latest. A debit note that hardens after that window forces the supplier to absorb the GST loss as well as the commercial loss because the tax-neutral path is shut.
The recovery program must run a parallel calendar on the credit-note window for every disputed debit note, even those still in dispute, because a dispute that drags past the credit-note window becomes operationally lossier. The standard rule for a Tier-1: any debit note unresolved at six months ages must have a provisional credit note staged with the tax team, ready to release in the next GSTR-1 cycle if commercial concession arrives. See the CBIC guidance for the operative text on credit-note issuance and the GSTR-1 amendment cycle.
Ageing buckets and recovery probability
Four buckets, with class-weighted recovery probabilities that collapse across the buckets.
| Ageing bucket | Average recovery probability | Operating action |
|---|---|---|
| 0 to 30 days | 55 to 70 per cent | Active dispute, evidence pack filed, tier-one SQA or plant finance engagement |
| 30 to 60 days | 35 to 50 per cent | Tier-two or tier-three escalation, credit-note provisioning prepared |
| 60 to 90 days | 20 to 30 per cent | Tier-four CFO-office route, write-off provision raised |
| 90-plus days | Below 15 per cent | Provision crystallised, structural-loss review |
The 0-to-30 band is the recovery zone. A Tier-1 with a mature library and escalation route files into this band consistently. A Tier-1 without one operates predominantly in the 60-plus bands and absorbs the rupee.
Worked example — a ₹220 crore Tier-1 with ₹14.6 crore of disputed debit notes
A Pune Tier-1 supplying body-in-white components to three OEM platforms. Annual revenue ₹220 crore. Standing disputed OEM debit-note pile at programme start: ₹14.6 crore across the financial year. Decomposition by class: ₹5.1 crore quality-reject, ₹3.4 crore quantity-short, ₹2.8 crore RMPV-pending, ₹1.9 crore FOMP, ₹1.4 crore line-stop. (Tooling amortisation was not material in this particular customer’s mix; in many Tier-1s it is a ₹0.5 to ₹2.5 crore line.)
Year-one programme outcome. Quality-reject recovered ₹1.5 crore against the ₹5.1 crore pile (29 per cent). Quantity-short recovered ₹2.0 crore against ₹3.4 crore (59 per cent). RMPV-pending recovered ₹2.1 crore against ₹2.8 crore (75 per cent), driven by current registration hygiene and a clean indexation contract. FOMP recovered ₹0.78 crore against ₹1.9 crore (41 per cent), with most of the loss in pre-programme ECO trail gaps. Line-stop recovered ₹0.35 crore against ₹1.4 crore (25 per cent), with two of the three OEMs declining engagement after tier-three escalation. Total recovered: ₹5.55 crore, or 38 per cent of the standing pile.
Section 34 settlement on the ₹9.05 crore conceded portion ran clean because the credit-note window for the financial year’s debit notes had been calendared by the tax team at programme start; no GST loss was added to the commercial loss. Year-two trajectory: with the documentation library mature and the SQA-to-CFO route established, the team is modelling 52 to 58 per cent recovery on the year-two pile, lifted by the quality-reject and FOMP classes where the evidence discipline now exists at dispatch.
This is a specific customer’s outcome under their specific class mix and OEM concentration. Other Tier-1s will see different splits driven by part mix, OEM portfolio, and prior evidence hygiene.
Size your OEM debit-note leakage before the programme
Plug in revenue, OEM concentration, and rough class mix to project recoverable leakage under a structured Tier-1 debit-note programme.
Open the Revenue Leakage Calculator →Common pitfalls to avoid
Pitfall one — pooling all OEM debit notes into a single dispute queue. The wrong evidence goes to the wrong counterparty; the recovery rate plateaus at 15 to 20 per cent. The five-class classification matrix is the first discipline.
Pitfall two — filing disputes without the class-specific evidence pack. A quality-reject dispute filed without the QA dispatch QC report, AQL plan, and photographic record gets dismissed at SQA tier-one. The documentation library at dispatch is the second discipline.
Pitfall three — letting the escalation tier shift happen on a “controller remembers to chase” basis. The tier shift must be calendar-driven; if SLA at tier one is 20 working days, the dispute auto-escalates to tier two on day 21 regardless of who is in the room. The escalation route SLAs are the third discipline.
Pitfall four — ignoring the Section 34 credit-note window. A conceded debit note from an April invoice with a credit-note window closing on the following September must be credit-noted by the GSTR-1 of August at the latest. The parallel tax-side calendar is the fourth discipline.
Pitfall five — running the ageing buckets monthly instead of weekly. A debit note that drifts from the 0-to-30 bucket to the 30-to-60 bucket halves the recovery probability; a weekly cadence catches this, a monthly cadence does not. The ageing cadence is the fifth discipline.
Pitfall six — treating line-stop class as recoverable rather than as a deterrent the OEM will defend hard. Year-one recovery on line-stop is 20 to 30 per cent at best; the operating muscle is to prevent line-stop debits at source through inventory-buffer and dispatch-quality discipline rather than to argue them after the fact.
Closing — link back to the leakage backbone
OEM debit-note dispute recovery is a Tier-1 specialisation of class-5 short-settlement in the Seven Classes of revenue leakage framework. The umbrella playbook for the broader recovery operating model is in the Revenue leakage recovery playbook; the audit-committee and board approval case is in Building the board case for revenue leakage recovery; the OEM settlement and debit-note workflow at the upstream end is in Automotive Tier-1 reconciliation. For Tier-1 finance heads, the OEM debit-note pile is usually the single largest visible leakage class on the books — and the one with the most recoverable rupees once the class-specific operating discipline is in place.