FOMP Warranty Back-Charge Accounting for Indian Auto Component Tier-1 Suppliers

A brake-pad Tier-1 in Pune with ₹240 crore annual Maruti Suzuki billing closes November 2026 and pulls the FOMP exposure register: 184 open claim IDs, ₹4.2 crore cumulative debit aged across the previous 18 months, 23 claims with overdue 8D responses, and a Section 34 GST credit-note cutoff approaching for 67 of them. The pattern is industry-standard. Any FOMP warranty back charge auto component India function operating against Maruti Suzuki, Tata Motors, Mahindra & Mahindra, Hyundai or Toyota Kirloskar has to account for the back-charge regime end-to-end — from claim-ID receipt to 8D to debit-note posting to Ind AS 37 provision to GST credit-note to Tier-2 passthrough.

Quick reference

What is FOMP and where does the term come from

FOMP — Field Operating Manufacturing Plant — is the OEM-internal designation for a confirmed warranty back-charge that has been traced through the manufacturing plant chain back to a specific supplier. The OEM dealer logs a field complaint. The OEM warranty system processes the customer claim under the OEM’s customer warranty (so the customer is made whole at the dealer). The failed part is sent to the OEM technical service team for failure-mode analysis. If the failure is root-caused to the supplier’s component — material defect, dimensional deviation, surface treatment failure, sub-assembly error — the OEM raises a FOMP debit on the supplier’s running account.

The supplier sees the FOMP debit on the next settlement cycle 6-9 months after vehicle sale on average. Slow-failure modes — corrosion in coastal climates, fatigue cracking in heavy-load applications, polymer degradation in high-temperature environments — can extend the lag to 18 months.

The FOMP timeline from field failure to debit note

1. Day 0 — Field failure. Customer reports the issue at the OEM dealer. Dealer raises a warranty claim under the OEM’s customer warranty.
2. Day 7-30 — Part return. Failed part is sent from the dealer to the OEM’s technical service centre. The OEM identifies the part number and supplier through the batch code or VIN-linked bill-of-materials.
3. Day 30-90 — Failure-mode analysis. OEM technical service team conducts the failure-mode and effects analysis (FMEA). If the failure is supplier-attributable, the OEM raises an internal claim ID against the supplier.
4. Day 90 — Claim ID notification. The supplier receives the claim ID on the OEM vendor portal (Maruti’s eSCM, Tata Motors’ iCMS-style ledger, Mahindra’s vendor portal) with the failure mode, vehicle VIN, dispatched part batch number, and 8D response deadline.
5. Day 90-120 — 8D response. Supplier engineering team submits the eight-disciplines root-cause analysis covering containment, root cause, corrective action, and prevention.
6. Day 120-180 — OEM acceptance or contest. OEM technical service either accepts the 8D as supplier-attributable (FOMP debit confirmed), re-categorises as design-attributable (FOMP withdrawn), or pushes back for further analysis.
7. Day 180-270 — Debit-note posting. Confirmed FOMP debits hit the next OEM settlement cycle. Supplier sees the back-charge on the running account.

The lag from field failure to running-account hit is therefore 6-9 months in the standard case. For the supplier’s FOMP register, this means open claim IDs are tracked across multiple ageing bands — notified but pre-8D, 8D submitted pending OEM decision, accepted pending posting, posted pending Section 34 action.

Ind AS 37 — the provisioning framework

Ind AS 37 (Provisions, Contingent Liabilities and Contingent Assets) governs how the supplier provisions for FOMP exposure at the balance-sheet date. The standard requires recognition when three conditions are met: a present obligation (legal or constructive) arising from a past event, probable outflow of resources, and reliable estimation of the amount.

For FOMP back-charges:

• Past event — the dispatch of the part into the OEM’s supply chain. Once the part is at the OEM and incorporated into a vehicle that has been sold, the supplier has supplied a defectible component into the warranty pool.
• Present obligation — constructive rather than legal. The master supply agreement creates the back-charge obligation, but the obligating event for provisioning is the established practice of the OEM raising FOMP debits on supplier-attributable failures. The supplier’s historic acceptance of these debits creates the constructive obligation.
• Probable outflow — yes for the population. While any individual part may or may not fail, the population dispatched in a period will produce a predictable FOMP claim rate.
• Reliable estimation — derived from the trailing 12-24 month FOMP run rate per OEM and per part family.

Indian Tier-1s with material OEM exposure typically carry a 4-6% FOMP provision against trailing revenue. For a ₹400 crore revenue supplier, that is ₹16-24 crore on the balance sheet, refreshed quarterly against actual closure rates.

Section 34 GST credit-note treatment on returned parts

When the OEM raises a FOMP debit and the part is physically returned, the supplier must issue a GST credit note under Section 34 of the CGST Act to reverse the original output GST. Section 34 vests the credit-note right with the supplier (not the buyer), and runs against a hard calendar window — 30 November of the next financial year or the date of filing the annual return, whichever is earlier.

Three operational implications follow:

1. FOMP claims raised against FY 2024-25 invoices have until 30 November 2025 to be credit-noted. A FOMP debit posted to the running account in December 2025 against an October 2024 dispatch invoice is out of window — the supplier can still recover commercially but cannot reverse output GST.
2. Physical return is not strictly required for the Section 34 credit note, but supports the documentation if the credit is challenged at GST audit. FOMP claims where the part is scrapped at the OEM or reworked in field need stronger ancillary documentation (claim ID, 8D response, OEM-side acceptance memo).
3. The credit note must reference the original tax invoice. Each FOMP debit traces to a specific dispatch invoice through batch code → claim ID → debit memo. The reconciliation system must hold that link.

The Tier-2 passthrough question

If the FOMP debit is root-caused to a sub-component supplied by a Tier-2 — a forging that cracked, a casting with inclusions, a sub-assembly with a wrong torque value — can the Tier-1 pass the back-charge through?

Yes, subject to two conditions. First, the 8D root-cause analysis must establish the Tier-2 attribution unambiguously, with documentation traceable to the Tier-2 batch through the Tier-1’s own batch-to-batch traceability. Second, the master supply agreement between the Tier-1 and the Tier-2 must contain a warranty back-charge clause aligned to the OEM regime. Most major Tier-2 contracts include such a clause but at varying caps — sometimes 100% of the OEM debit, sometimes a contractual cap of 50-60% of accepted OEM FOMP.

Operationally, the Tier-1 raises a back-charge on the Tier-2 mirroring the accepted OEM debit, supported by the OEM’s claim ID, the 8D response, and the batch traceability. The Tier-2 then raises a Section 34 GST credit note on the Tier-1. This passthrough recovery is one of the highest-leakage areas in manual reconciliation environments — industry data suggests at least 30% of legitimate Tier-2 passthrough opportunities are never raised because the OEM claim ID is not linked to the Tier-2 batch in time and the recovery window expires.

Job-work TDS overlay on Tier-2 settlements

Where the Tier-2 is providing a job-work service to the Tier-1 — heat treatment, electroplating, induction hardening, painting, surface treatment, machining of supplied inputs — Section 393(1)(a) TDS applies at payment code 1002, the successor to legacy Section 194C from 1 April 2026. Rate is 1% for individual/HUF payees, 2% for company/firm payees, with thresholds ₹30,000 per transaction and ₹1 lakh aggregate per FY. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India for the full code reference.

The Tier-2 back-charge from FOMP passthrough does not itself attract TDS — it is a recovery of damages on supplied goods, not a payment for services. But where the Tier-2 invoice covers both goods supplied and job-work service in a composite line, the TDS applies on the service portion only and the recovery must be netted in the right tax bucket.

Worked example — ₹240 crore Maruti Suzuki annual billing, ₹4.2 crore FOMP exposure

A Pune-based Tier-1 brake-pad supplier with ₹240 crore annual Maruti Suzuki billing, closing November 2026:

• 18-month trailing FOMP exposure: 184 claim IDs, ₹4.2 crore cumulative debit
• FOMP run rate: 1.75% of trailing monthly billing (within the 1-3% industry band)
• Ind AS 37 provision held on balance sheet: ₹13.2 crore (5.5% of annual revenue × ₹240 crore)
• Open 8D responses pending: 23 claim IDs in 14-30 day window, 4 overdue
• Accepted FOMP debits eligible for Section 34 credit notes: ₹2.8 crore against 142 claim IDs
• Section 34 GST reversal opportunity at 28% rate: ₹78 lakh — but 67 claim IDs (₹1.4 crore) fall against FY 2024-25 invoices with 30 November 2025 cutoff already passed
• Recoverable Section 34 GST: ₹39 lakh against the remaining ₹1.4 crore eligible
• Tier-2 passthrough candidates: 47 claim IDs root-caused to forgings or castings from three Tier-2 vendors, ₹1.1 crore back-charge potential
• Tier-2 back-charges actually raised in the period: ₹68 lakh (62% capture rate, leaving ₹42 lakh of legitimate recovery on the table)
• Section 393(1)(a) code 1002 TDS on outsourced heat-treatment Tier-2 settlements for the period: ₹6.4 lakh quarterly challan

Without a claim-ID-linked FOMP register, the November cutoff costs the supplier ₹39 lakh of GST reversal that could have been preserved with earlier processing, and the Tier-2 passthrough leakage runs at ₹42 lakh per quarter compounding annually.

ICAI guidance on Ind AS 37 disclosure

The Institute of Chartered Accountants of India (ICAI) provides Ind AS 37 application guidance covering the recognition criteria for constructive warranty obligations, the discounted-cash-flow approach where the obligation extends beyond 12 months, and the disclosure requirements in the notes to financial statements. For Indian Tier-1 auto-component suppliers, the FOMP provision typically discloses the opening balance, additions, utilisations, releases, and closing balance by OEM customer family in the warranty provision note.

What automated reconciliation changes

Manual FOMP back-charge handling at a multi-OEM Tier-1 is a 8-12 day month-end exercise spread across engineering (8D responses), finance (provisioning, GST credit notes), and procurement (Tier-2 passthrough). Purpose-built reconciliation software India treats each FOMP claim ID as a structured exception keyed by OEM and links it to the source dispatch invoice, the 8D response workflow, the Section 34 cutoff calendar, and the Tier-2 passthrough register in a single record. TransactIG carries 24+ industry presets including a configuration that handles OEM FOMP regimes with claim-ID-to-invoice batch traceability, Section 34 calendar triggers, Ind AS 37 provision roll-forward, and the Tier-2 passthrough chain. Customer outcomes include match-rate improvement from 51% to 88% on OEM settlement decomposition and Tier-2 passthrough capture moving from the typical 60-70% band into the 90%-plus band post-implementation. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement equivalent see three-way matching software India. For the broader pillar see automotive component manufacturing reconciliation in India and manufacturing reconciliation in India. For the related quality cluster see auto line rejection PPM quality debit reconciliation.

Continue reading the automotive-components cluster

• OEM-Tier 1 settlement and debit-note reconciliation — the seven-category OEM debit taxonomy with FOMP as one stream
• How Indian auto component suppliers handle OEM short-pays — the finance-controller playbook on the broader auto-debit regime
• Automotive component manufacturing reconciliation in India — the sub-pillar