Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian Tier-1 and Tier-2 manufacturers supplying automotive, capital goods, and appliances OEMs absorb 2-4% annual leakage on their OEM receivables because the OEM applies short-pay deductions at month-end aggregated cash settlement without per-invoice debit-note traceability. Standard deduction categories — Raw Material Price Variance pending, quality debit, line-stop, FOMP, freight-on-own-account, advance-recovery — are contractually valid in principle but applied at incorrect rupee values in practice. Without an ageing workflow that surfaces the cash-credit variance per invoice within the dispute window, more than half of disputable short-pay ages out of recovery.
Maintain an OEM receivable ledger keyed by invoice number, taxable value, GST split, expected payment date per OEM contract, actual credit date, actual credited value, and computed cash variance. On every OEM cash credit, auto-allocate to oldest open invoices first, surfacing the residual short-pay per invoice. Match the residuals against the OEM's debit-note register by month — invoices with a matching debit note enter the disputable-or-accepted queue; invoices without a debit note enter the structural-short-pay queue. Age each queue in 60 / 90 / 150 / 180-day buckets keyed to invoice date. Flag short-paid invoices for Section 34 credit-note generation if dispute is abandoned.
OEM receivable ledger with invoice-level granularity. Cash-credit allocation engine on oldest-open-first or contract-specified order. Debit-note reconciliation pipeline by OEM by month. Short-pay decomposition classifier with categories RMPV pending, quality debit, line-stop, FOMP, freight-on-own-account, advance-recovery, structural. Ageing buckets 60 / 90 / 150 / 180 days with bucket-specific dispute action. Section 34 credit-note generator for accepted short-pays within window. Audit trail of every dispute filed, accepted, rejected, settled.
A daily OEM short-pay dashboard by OEM and invoice with rupee variance, age, debit-note status, and dispute window remaining. A weekly dispute pack ready to send to OEM AR-AP desk. A monthly Section 34 credit-note queue with arithmetic prepared. A quarterly OEM-wise leakage trend feeding the Discovered Money register on partial-payment and unexplained-variance classes. A standing recovery register tracking disputable vs structural classifications and recovery rates.
A CFO at a Tier-1 forging supplier in Faridabad with ₹220 crore of annual OEM receivables across three large customers — a passenger-vehicle OEM, a two-wheeler OEM, and a commercial-vehicle OEM — runs a FY26 audit on cash-versus-invoice. Aggregate invoiced: ₹220 crore. Aggregate credited: ₹212.9 crore. Aggregate short-pay: ₹7.1 crore, 3.2% of receivable.
Decomposition. ₹3.4 crore of the ₹7.1 crore carries a matching OEM debit note (disputable or accepted with reason). ₹3.7 crore is structural — settled below invoice value with no debit-note explanation. Of the ₹3.4 crore disputable, the supplier has actively disputed ₹1.1 crore and recovered ₹0.74 crore — leaving ₹2.6 crore of disputable short-pay that aged out unresolved in last year’s books. Of the ₹3.7 crore structural, recovery is at zero. Total leakage that ages out of recoverability under last year’s workflow: ₹6.3 crore — 2.9% of receivable, a structurally typical band for a Tier-1 OEM-dependent supplier.
This is the leakage class that costs Indian manufacturers more than every other category combined. This guide decomposes the standard short-pay categories, walks the 60/90/150/180-day ageing workflow that recovers the disputable band, and shows the Section 34 credit-note discipline that prevents leakage from cascading into a layered GST loss.
Quick reference: OEM short-pay decomposition map
| Short-pay category | Source artefact | Typical contract anchor | Recovery action |
|---|---|---|---|
| Raw Material Price Variance pending | Monthly RMPV settlement note | Contract RMPV clause | Wait for closure period, then dispute residual |
| Quality debit | OEM SQA debit note | Quality clause with per-unit rate | Verify per-unit rate, dispute over-application |
| Line-stop charge | OEM production-line incident report | Line-stop clause with cap | Verify caused-by attribution, dispute |
| FOMP (formula-based pricing) | Monthly FOMP table | Contract formula reference | Recompute against formula, dispute math |
| Freight on own account | Incoterm change notice | Incoterm clause | Verify shipment incoterm, dispute incorrect application |
| Advance recovery | Earlier advance ledger | Advance recovery schedule | Verify schedule alignment |
| Tooling amortisation recovery | Tooling agreement | Tooling amortisation clause | Verify schedule alignment |
| Structural — no debit note | Cash variance with no OEM note | Section 73, Indian Contract Act | Formal AR demand, escalate |
Why OEM short-pay is the manufacturer’s biggest leakage class
A standard OEM-supplier cash relationship has three settlement events. Event one: the supplier raises an invoice for delivered goods at contracted price. Event two: the OEM books the invoice in its AP at the contracted price (rare contests at this stage). Event three: the OEM settles the AP at month-end in a single net entry per supplier — gross of all invoices in the period, less all debits the OEM has applied in the same period.
The leakage problem lives in event three. The OEM’s single-entry net settlement does not carry per-invoice deduction context. The supplier sees a ₹4.7 crore credit against ₹4.95 crore of expected invoicing and no per-invoice deduction note. The supplier’s AR controller has two choices: chase the OEM AR-AP desk for the per-invoice attribution (time-intensive, low success without senior escalation), or close all invoices proportionally and accept the variance as a single-line “cash variance” entry (operationally efficient, but breaks the audit trail and forfeits the dispute window).
In the absence of a reconciliation engine that auto-allocates the cash credit against open invoices and surfaces the per-invoice residual, almost every Indian manufacturer defaults to the second choice. The result is the 2-4% leakage band that sits structurally on the receivable.
The seven standard short-pay categories — and the recovery action for each
Category 1 — Raw Material Price Variance pending. The contract prices the supplier’s product as a base price plus RMPV — a monthly adjustment based on actual raw-material index movement. The OEM short-pays in anticipation of an upcoming RMPV settlement that will close the variance. Recovery action: track the RMPV closure period, validate the settled rupee against the index movement, dispute any residual.
Category 2 — Quality debit. The OEM’s supplier-quality-assurance team rejected a portion of a delivered lot and debited the supplier at the per-unit rate in the quality clause. Standard recovery: cross-check the rejected-unit count against the OEM’s quality reject note, multiply by the contracted per-unit debit rate, dispute any over-application.
Category 3 — Line-stop charge. The supplier caused the OEM’s production line to halt. The contract specifies per-hour line-stop charges with a per-incident cap. Recovery action: validate caused-by attribution (was it truly the supplier’s fault, or shared with logistics, OEM’s own line, or another supplier), validate hours-of-line-stop, validate against the cap.
Category 4 — FOMP (formula-based pricing) adjustment. The contract uses a pricing formula tied to inputs that adjust periodically. The OEM applies the formula and debits the difference. Recovery action: recompute the formula independently, surface any math errors.
Category 5 — Freight on own account. Goods were shipped on incorrect incoterm (the supplier paid freight that the contract said the OEM would pay, or vice versa). Recovery action: validate shipment incoterm against contract, recover freight where mis-attributed.
Category 6 — Advance recovery. The OEM provided an earlier advance to the supplier (tooling investment, capacity reservation) and is amortising it through deductions. Recovery action: validate against the advance-recovery schedule, surface any over-recovery.
Category 7 — Structural short-pay. The OEM settled below invoice value with no debit-note reference at all. This is the hardest category to recover because there is no contractual anchor; the recovery action is a formal AR demand letter and senior escalation. Section 73 of the Indian Contract Act preserves the right.
The 60/90/150/180-day ageing workflow
Day 60 — the cash settlement for the relevant period has occurred. Any open residual on an invoice is checked against the OEM’s debit-note register for the period. If a debit note exists, the invoice enters the dispute classification workflow. If no debit note exists, the invoice enters the structural-short-pay workflow.
Day 90 — the standard dispute window opens. For disputable short-pay, raise a formal dispute with the OEM AR-AP desk citing invoice number, expected value, credited value, debit-note reference, and dispute rationale. For structural short-pay, raise a formal AR demand letter.
Day 150 — escalate to the OEM CFO office for any disputable short-pay still unresolved. Prepare Section 34 credit-note arithmetic for the cases where dispute looks unlikely to succeed — better to clean the GST exposure on accepted short-pay than to let it cascade.
Day 180 — final escalation. The Rule 37 ITC reversal clock on the supplier’s own payables side is starting (the supplier may be unable to pay Tier-2 suppliers if the OEM short-pay has not been resolved). The receivable is now at high working-capital risk. See the Rule 37 ITC reversal article for the cascade mechanics.
Worked example — Tier-1 forging supplier in Faridabad
Setup. ₹220 crore of annual OEM receivables across three customers. Average monthly billing ₹18.3 crore. Short-pay band: 3.2% of receivable = ₹7.1 crore per year.
Decomposition. ₹3.4 crore disputable, ₹3.7 crore structural.
Pre-workflow recovery. ₹1.1 crore actively disputed of which ₹0.74 crore recovered. ₹6.36 crore aged out.
Post-workflow scenario. Within two quarters of operating the 60/90/150/180-day ageing workflow with per-invoice cash allocation: disputable short-pay surfaced systematically with per-invoice context and OEM debit-note cross-reference. Disputes raised on ₹3.1 crore of the ₹3.4 crore disputable band, recovered ₹2.18 crore (70% recovery). Structural short-pay raised as formal AR demand on ₹3.7 crore, recovered ₹0.92 crore through escalation (25% recovery). Section 34 credit notes raised on the ₹3.92 crore accepted as final short-pay, preventing ₹70 lakh of output GST cascade-leakage.
Total annual recovery: ₹3.10 crore plus ₹70 lakh GST cascade avoided = ₹3.80 crore. Recovery rate on standing leakage: 54%. Residual: ₹3.30 crore, mostly structural and tied to weak contractual leverage on two of the three OEMs.
Model OEM short-pay leakage on your receivable base
Enter receivable base, observed short-pay band, and disputable-vs-structural split to project recovery upside under the 60/90/150/180-day workflow.
Open the Revenue Leakage Calculator →The Section 34 credit-note discipline
For every short-pay finally accepted as settlement (whether disputable that was abandoned or structural that could not be recovered), the supplier must raise a Section 34 credit note within the GST window — closing by 30 November of the next FY. Failing this, the supplier permanently pays 18% output GST on a rupee never received. On the Faridabad supplier’s ₹3.92 crore accepted short-pay band, that is roughly ₹70 lakh of GST exposure if the credit notes are not raised.
The credit-note workflow ties back into the supplier’s own GSTR-1. The OEM, on receipt of the credit note, can adjust their GSTR-2B and consequently their input claim. This keeps both sides clean. Without the workflow, the supplier pays GST on the un-received amount permanently.
Putting OEM short-pay leakage on the audit committee agenda
Standard quarterly pack. OEM receivable position per customer. Short-pay band by OEM and trend. Disputable-vs-structural decomposition. Recovery rate per category. Section 34 credit-note queue with rupees in window. Working-capital cost of unrecovered short-pay (see linked article). Top three disputes by rupee and resolution status. This is the single artefact that turns “OEM is squeezing us” into a structured recovery program with quarterly improvement metrics.
Continue reading on the leakage backbone
For the umbrella framing, see Revenue leakage and the Seven Classes framework. The companion piece on the buyer-side ITC reversal cascade is Rule 37 ITC reversal on OEM unpaid invoices. The working-capital arithmetic is at Working capital leakage from reconciliation delays. The Stop Revenue Leakage pillar page anchors the broader story.