Skip to main content
How-To · 12 min read

How Indian Auto Component Suppliers Handle OEM Short-Pays: A Finance Team Guide

Indian Tier-1 auto-component suppliers see 5-12% of monthly OEM billing arrive as short-pay through auto-debit. This is the operational playbook — decomposing the payment advice, classifying every debit by reason, deciding accept vs contest within the dispute window, issuing GST credit notes inside the Section 34 cutoff, and ageing every short-pay against the 180-day Rule 37 ITC reversal clock.

Terra Insight
Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 23 May 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Indian auto-component suppliers face structural OEM short-pay of 5-12% of monthly billing through auto-debit mechanisms, with seven debit-reason categories spanning FOMP, JIT shortage, quality penalty, line-stop, tooling adjustment, technical service, and transport recovery. Each debit must be tied to the source invoice via claim ID, classified by reason, decided as accept or contest within a 30-day window, issued a Section 34 GST credit note if accepted before 30 November of the next FY, aged against the 180-day Rule 37 ITC reversal clock, and tracked through the Tier-2 passthrough register.

How It's Resolved

Decompose each OEM payment advice into base invoice net plus n discrete debit memos, link each debit memo to its source invoice through the claim ID or rejection slip, classify by reason taxonomy (FOMP / JIT shortage / quality / line-stop / tooling / technical service / transport), route to the accept-or-contest workflow based on evidence strength, issue the GST credit note within Section 34's 30 November cutoff if accepted, age unpaid short-pays in 60 / 90 / 150 / 180-day buckets against Rule 37, and trigger the Tier-2 passthrough entry where the root cause is sub-vendor attributable.

Configuration

OEM customer master keyed by plant code and vehicle programme, debit-memo reason taxonomy with claim-ID-to-invoice mapping, FOMP running account per OEM keyed to warranty claim ID, GST credit-note workflow with Section 34 30-November calendar trigger, Rule 37 ageing buckets at 60 / 90 / 150 / 180 days, accept-vs-contest decision matrix per reason code, Tier-2 passthrough register linking each accepted OEM debit to a Tier-2 back-charge candidate.

Output

A daily OEM short-pay decomposition view showing billed vs paid vs reason-coded debit variance per customer, a Section 34 GST credit-note action queue keyed by approaching cutoff, a Rule 37 ITC-reversal risk register by short-pay age band, a Tier-2 passthrough debit register matched to each accepted OEM back-charge, and a contested-debit queue with evidence trail and dispute-window timer.

A finance controller at a ₹400 crore Tier-1 brake-system supplier in Pune opens the Maruti Suzuki settlement statement for the September quarter. Gross billing ₹120 crore. Bank credit ₹110.4 crore. Eight percent short-pay — ₹9.6 crore — sitting against a settlement run that lists 47 FOMP warranty claim IDs, 23 JIT shortage events, 18 quality rejection slips, 8.5 hours of line-stop charges, and three tooling over-cap adjustments. The settlement window to dispute closes in 30 days. The Section 34 GST credit-note cutoff for any accepted debit is 30 November of the next FY. And every unpaid residual is now ageing against the 180-day Rule 37 ITC reversal clock at the Maruti end.

This is the operational baseline for OEM short pay auto component India finance teams. The pattern repeats every month, every OEM, every Tier-1 in the country. This guide walks the end-to-end reconciliation workflow — payment-advice decomposition, reason taxonomy, accept-vs-contest decision logic, GST credit-note issuance, Rule 37 ageing, Tier-2 passthrough — at the level of detail a controller actually needs to close month-end on time.

Quick reference

ItemStandardRegulatorCode / Threshold
Typical short-pay band5% to 12% of monthly OEM billingIndustry (ACMA)n/a
FOMP back-charge range1% to 3% of trailing monthly billingCommercial termn/a
Section 34 GST credit-note window30 November of next FY or annual return filingCBICCGST Act Section 34
Rule 37 ITC reversal trigger180 days from invoice date if unpaidCBICCGST Rules Rule 37
GST rate on most auto components28% (select 18%, EV 5%)CBICHSN 8708 family
Contractor TDS on Tier-2 job work1% individual / 2% companyCBDTSection 393(1)(a) code 1002
Purchase TDS on raw material0.1% on aggregate above ₹50 lakhCBDTSection 393(1)(k) code 1012
Scrap TCS on skeleton scrap sale1%CBDTSection 394 code 1071

How does an OEM payment advice actually decompose?

Indian OEMs run settlement against the supplier’s running invoice ledger at a fortnightly or monthly cadence. A single bank credit hits the supplier’s account on the settlement date, accompanied by a structured payment advice (PDF, Excel or portal-export). The advice is never one row per invoice. It is one row per invoice plus one row per debit memo plus one row per credit note plus one row per netted recovery. A typical mid-month Maruti settlement at a ₹400 crore Tier-1 carries 600 to 1,200 lines.

The reconciliation engine’s first job is decomposition. Every line is classified into one of four buckets:

  1. Clean invoice payment — the OEM paid the invoice in full at the contracted GST-inclusive amount. No action.
  2. Partial invoice payment — the OEM paid less than invoice. The shortfall must tie back to one or more debit memos on the same advice or held against a prior period.
  3. Pure debit memo — a standalone deduction that does not net against a current-period invoice (typical for FOMP from prior dispatches, line-stop charges from prior weeks, tooling over-cap clawbacks).
  4. Credit memo from OEM — a rare but real category, typically RMPV price-rise releases or tooling shortfall settlements.

The decomposition output is a one-row-per-invoice ledger of billed amount vs paid amount, plus a parallel debit-memo ledger of every deduction tied to its source claim ID and source invoice. Without this two-ledger split, the reason analysis cannot start.

The seven debit reason categories — what each looks like

FOMP — Field-Originated Material Performance

A vehicle in the field fails warranty inspection at an OEM dealer. The dealer files a warranty claim. The OEM’s quality engineering traces the failure to a specific part supplied 4 to 18 months earlier, raises a FOMP debit note citing the warranty claim ID, vehicle VIN range, dealer ID, technical service deduction analysis, and the per-unit recovery amount. FOMP is the highest-value, highest-volume, longest-ageing debit category at most Tier-1s. Reconciliation must hold FOMP debits in a running per-OEM account keyed by claim ID, because individual claims can be disputed, withdrawn, reduced, or fully closed over a 12 to 18-month tail.

JIT shortage

The OEM’s daily kanban call-off says 4,800 brake pads on the morning truck. The supplier’s truck arrives with 4,720. The OEM either starts the line short (rare, costly) or pulls from emergency reserve stock. The JIT shortage debit covers the un-supplied 80 units at contracted rate plus an expediting premium — sometimes 2x the part value if the OEM had to airlift from an alternate plant. JIT shortages settle on the next billing cycle and rarely age beyond 60 days.

Quality penalty

Quality penalties have three sub-types: line rejection (a part rejected at OEM incoming inspection or assembly line — returned on the next return-trip truck), PPM excess (rolling 12-month parts-per-million defect rate breaches the contractual threshold), and audit non-conformance (ASES, QSB, or PSI audit findings). Line rejection debits flow with the rejected part’s value plus a handling/rework fee. PPM penalties flow as a contractual penalty per ppm point over threshold, applied to trailing 90 or 180-day billing.

Line-stop charge

When a quality issue or JIT shortage causes the OEM line to actually stop, the OEM raises a line-stop charge by the hour. Indian OEMs encode line-stop rates contractually — typically ₹1 lakh to ₹5 lakh per hour depending on vehicle programme and plant. A single 4-hour line-stop on a Maruti Manesar Brezza line can be a ₹16 lakh debit.

Tooling amortisation adjustment

The supplier recovers tooling cost on a per-part basis over a committed volume. If cumulative parts shipped exceed the contractual cap, the over-recovery is clawed back as a tooling adjustment debit on the next settlement. See Tooling amortisation reconciliation in India for the underlying recovery mechanics.

Technical service deduction

OEM engineers from quality, supplier-development and supply-chain teams visit supplier plants for line trials, audits, and incident investigations. The OEM debits supplier-caused visit hours at a contractual hourly rate, typically ₹3,500 to ₹8,000 per engineer-hour.

Transport debit

When the OEM arranges premium freight (airfreight, dedicated truck) to cover a supplier-caused shortage, the freight differential is debited on the next settlement. Often coupled with a JIT shortage event but tracked separately because the GST treatment differs.

The supplier’s reconciliation workflow — step by step

Once the payment advice is decomposed and every debit is classified, the workflow runs five sequential stages:

Stage 1 — Link each debit to its source invoice. Every debit memo carries a claim ID (FOMP), rejection slip number (quality), shortage event ID (JIT), line-stop event ID, tooling programme ID, or visit log reference. The reconciliation engine matches each ID to the originating invoice or dispatch record in the supplier’s books.

Stage 2 — Validate the debit against contractual terms. Is the per-unit rate the contracted rate? Is the warranty claim within the supplier’s warranty obligation period? Is the line-stop rate per the agreement? Is the PPM calculation method correct? Industry data suggests 12-18% of OEM debits fail this validation at first pass — the OEM has miscalculated, applied a stale rate, or attributed the failure incorrectly.

Stage 3 — Decide accept vs contest. Strong-evidence debits (clean claim ID, validated calculation, supplier-attributable root cause) go to accept. Weak-evidence debits (unclear root cause, calculation error, prior-period coverage already exhausted) go to contest. The decision must be made inside the OEM’s dispute window — typically 30 days from settlement date.

Stage 4 — Issue the GST credit note on accepted debits. Under Section 34 of the CGST Act, the supplier issues the GST credit note. The OEM’s debit memo is not a tax-effective document. The supplier-issued GST credit note reverses output GST and flows to GSTR-1. The window: 30 November of the next FY or annual return filing date. Miss it and the GST liability stands even if the commercial deduction has flowed.

Stage 5 — File the Tier-2 passthrough. If the root cause traces to a Tier-2 vendor (most FOMP, line-rejection-on-Tier-2-part, JIT shortage caused by Tier-2 delivery delay), raise a back-charge on the Tier-2 vendor for the recovery amount. See Tier-2 sub-vendor job-work reconciliation for the upstream chain.

Rule 37 ITC reversal — why aged short-pays are radioactive

Rule 37 of the CGST Rules requires the recipient (the OEM) to reverse Input Tax Credit if the supplier is not paid within 180 days of invoice date. The reversal applies to the unpaid portion. For a ₹100 lakh invoice short-paid by 12% with the ₹12 lakh sitting in open dispute, the OEM faces Rule 37 reversal on the ₹12 lakh × 28% GST = ₹3.36 lakh ITC at day 180.

OEMs do not absorb Rule 37 reversals. They force resolution at day 150 to 170 — typically by either unilaterally releasing the disputed residual (rare) or demanding a supplier-issued GST credit note (common). The supplier’s reconciliation engine must therefore age every short-pay in 60 / 90 / 150 / 180-day buckets and escalate at each band: at 60 days, document the dispute; at 90 days, escalate to OEM commercial team; at 150 days, prepare credit-note draft; at 180 days, force final accept-or-contest. See Rule 37 / 37A ITC reversal on supplier default for the full mechanics.

Interactive Tool

Three-Way Match Exception Cost Calculator

Quantify the carrying cost of unreconciled OEM short-pays at your Tier-1 — ageing buckets, Rule 37 exposure on the unpaid residual, and Tier-2 passthrough recovery leakage at typical Indian Tier-1 volumes.

Open the Three-Way Match Calculator →

Section 34 GST credit notes — the 30-November cutoff

Section 34 of the CGST Act puts a hard timing window on GST credit notes. The supplier may issue a credit note to reduce output GST if goods are returned, found deficient, or the originally charged value or tax is reduced. The deadline: 30 November of the financial year following the year of supply, or the date of filing the annual return, whichever is earlier.

A short-pay accepted in October 2026 against an FY 2025-26 invoice has until 30 November 2026. A short-pay accepted in February 2027 against an FY 2025-26 invoice is already past the window — the GST credit note cannot be issued and the GST liability on the accepted reduction stands. The commercial recovery still flows through the books, but the supplier carries an unrecoverable GST expense equal to the GST on the accepted debit.

This is why reason-coded ageing matters. A controller running Excel cannot see at a glance which accepted debits are within window and which have lapsed. A reconciliation engine that calendars every accept decision against the Section 34 cutoff per source invoice surfaces the urgent ones automatically.

The Excel reality vs config-driven reconciliation

Industry observation across the 25,000-supplier Indian auto-component base: roughly 90% of Tier-1 OEM settlement reconciliation today runs in Excel workbooks per OEM per stream. A typical setup has one workbook for FOMP claims (one sheet per OEM, one row per claim ID, manual carry-forward each month), one for quality debits, one for JIT shortages, a cross-workbook pivot for total reason-coded variance, and a separate sheet for the GST credit-note action queue.

The structural failure modes are well known: claim IDs drop between months when staff change; FOMP ageing carries forward incorrectly when new entries are pasted over old ones; the Section 34 calendar trigger is forgotten until the November payroll close discovers ₹40 lakh in lapsed GST recoveries; the Rule 37 ageing buckets are nominal but not actually monitored; and the Tier-2 passthrough register is the single biggest leakage source — at least 30% of legitimate passthrough back-charges never get raised.

Purpose-built reconciliation software India treats each debit reason code as a structured variance stream and surfaces only the lines that fail to match. TransactIG carries 24+ industry presets including an auto-component configuration that handles OEM auto-debits, FOMP running accounts, GST credit-note timing under Section 34, Rule 37 ageing buckets, and Section 393(1)(a) code 1002 deductions on Tier-2 job-work. Customer outcomes include match-rate improvement from 51% to 88% and exception rates moving into the sub-15% band post-implementation. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022).

Tax overlay — Section 393(1)(a), Section 393(1)(k), Section 394

The short-pay workflow sits inside a tax overlay that affects the Tier-2 passthrough leg directly:

  • Section 393(1)(a) code 1002 — Contractor TDS at 1% individual / 2% company applies to every Tier-2 job-work conversion-charge invoice raised in the passthrough recovery process. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India for the full code map.
  • Section 393(1)(k) code 1012 — Purchase TDS at 0.1% on aggregate purchase value above ₹50 lakh per supplier per FY applies on raw-material recoveries from Tier-2.
  • Section 394 code 1071 — Scrap TCS at 1% applies on skeleton scrap recoveries if the Tier-1 retains and sells scrap generated through the passthrough chain.

These are the new framework codes effective from 1 April 2026 under the Income Tax Act 2025. Legacy Section 194C / 194Q / 206C(1) references apply only to cross-era reconciliation of dispositions started before that date.

Worked example — ₹120 crore quarterly Maruti billing, full decomposition

A ₹400 crore Tier-1 brake-system supplier with the September 2026 Maruti Suzuki quarter:

LineAmount
Gross Maruti billing for the quarter₹120.0 crore
OEM auto-debit aggregate (8% short-pay)₹9.6 crore
→ FOMP back-charges (47 claim IDs)₹1.80 crore
→ JIT shortage debits (23 events)₹0.52 crore
→ Quality penalty deductions₹0.38 crore
→ Line-stop charges (8.5 hours at ₹1.65 lakh/hr)₹0.14 crore
→ Tooling adjustment clawback₹0.12 crore
→ Technical service deductions₹0.04 crore
→ Transport debit₹0.05 crore
→ Other / unclassified (residual netting against prior-period RMPV claim release)₹6.55 crore
Net Maruti receipt for the quarter₹110.4 crore

Of the ₹9.6 crore short-pay, the accept-vs-contest decision split runs:

  • Accepted (clean claim ID, validated calculation, supplier-attributable): ₹6.2 crore → triggers Section 34 GST credit notes by 30 November 2027 = ₹1.74 crore GST output reversal at 28%
  • Contested (weak evidence or calculation error): ₹2.1 crore → enters 60 / 90 / 150 / 180-day Rule 37 ageing
  • Pending evidence collection: ₹1.3 crore → must clear within 30 days or escalate

Tier-2 passthrough on the accepted ₹6.2 crore: roughly ₹4.4 crore (71%) is upstream-traceable to specific Tier-2 vendors. At full recovery, this is ₹4.4 crore of back-charge revenue that an Excel-driven shop will leak at least 30% of (₹1.3 crore) through dropped claim linkage.

Net quarterly cost of inadequate short-pay reconciliation at this Tier-1: ₹1.3 crore of leaked Tier-2 passthrough plus roughly ₹40 lakh of lapsed Section 34 GST recoveries on FOMP claims that closed after the 30 November cutoff. ₹1.7 crore per quarter, ₹6.8 crore annualised, against a four-OEM book of similar size.

ACMA standardisation reference

The Automotive Component Manufacturers Association of India (ACMA) publishes commercial-term templates and supplier-rating frameworks that encode standardised debit-reason taxonomies, line-stop rate bands, and OTIF (on-time-in-full) score methodologies. Most Tier-1 ERP configurations align their vendor master debit-reason codes to ACMA’s taxonomy, which is also referenced in OEM supplier handbooks (Maruti’s Supplier Quality Manual, Tata Motors’ Supplier Excellence Programme materials, M&M’s Supplier Council guidelines).

Continue reading

Sibling articles in the auto-component cluster:

Up the chain:

Primary reference: Automotive Component Manufacturers Association of India (ACMA) — for industry-standard back-charge taxonomies, OEM supplier-rating frameworks, and the published commercial-term templates that govern auto-debit regimes between OEMs and their Tier-1 base.

Frequently Asked Questions

What share of monthly OEM billing typically shows up as short-pay at an Indian Tier-1 auto component supplier?
Across Maruti Suzuki, Tata Motors, Mahindra, Hyundai and Toyota Kirloskar, monthly short-pay at Tier-1 suppliers runs in a 5% to 12% band. The mid-point is roughly 8%. Of that 8%, FOMP warranty back-charges typically account for 1% to 3% of trailing monthly billing, JIT shortage debits 0.5% to 1.5%, quality penalty deductions 0.5% to 1.5%, line-stop charges 0.2% to 0.7%, and tooling adjustment plus transport recovery debits the residual 0.5% to 1%. A Tier-1 on ₹120 crore quarterly Maruti billing therefore expects ₹6 to ₹14.4 crore of quarterly short-pay against Maruti alone.
When must a supplier issue a GST credit note after accepting an OEM short-pay?
Under Section 34 of the CGST Act, the supplier issues the GST credit note (not the OEM, despite the OEM having raised the commercial debit note). The statutory window is 30 November of the next financial year or filing of the annual return, whichever is earlier. A short-pay accepted in October 2026 against an FY 2025-26 invoice has until 30 November 2026 to be converted to a GST credit note. Beyond that date the commercial recovery still flows, but the supplier cannot reverse output GST on the accepted reduction — the GST liability stands.
When does an aged short-pay become a Rule 37 ITC reversal risk?
Rule 37 of the CGST Rules requires the recipient (the OEM) to reverse Input Tax Credit if the supplier is not paid within 180 days of the invoice date. For a short-pay where the unpaid residual sits in dispute, the 180-day clock runs against the unpaid portion only — but OEMs do not absorb the reversal. In practice OEMs force resolution at day 150 to 170 by either releasing the disputed amount or demanding a supplier-issued credit note. The supplier's reconciliation must age every short-pay in 60 / 90 / 150 / 180-day buckets with escalation triggers at each band.
What is the typical debit-reason taxonomy that Indian OEMs use for auto-debits?
Seven reason categories cover effectively all OEM auto-debits in Indian passenger-car, two-wheeler and commercial-vehicle programmes: FOMP (field-originated material performance — warranty back-charges), JIT shortage (called-off vs dispatched quantity gap), quality penalty (PPM excess and line rejection), line-stop charge (₹1 to ₹5 lakh per hour by programme), tooling amortisation adjustment (over-cap recovery clawback), technical service deduction (OEM engineer time on supplier-caused issues), and transport debit (premium freight billed back). ACMA's commercial-term templates align to this taxonomy and most Tier-1 ERP configurations encode these as the master reason codes.
What's the difference between an OEM auto-debit and a back-charge raised by the supplier on a Tier-2?
An auto-debit is OEM-initiated — the OEM deducts the amount from the supplier's running settlement before the payment is released, and the supplier reconciles after the fact. A back-charge is supplier-initiated — the Tier-1 raises a debit note on its Tier-2 vendor for an upstream-traced quality, FOMP or JIT failure. The two are linked through the Tier-1's passthrough register: every accepted OEM auto-debit that traces to a Tier-2-caused failure must trigger a corresponding back-charge on that Tier-2, otherwise the recovery leaks. Industry data suggests at least 30% of legitimate Tier-2 back-charge opportunities are never raised in Excel-based reconciliation environments.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.