Skip to main content
How-To · 13 min read

GST on Warranty Replacements for Auto Components: Buyer-Seller-OEM Three-Party Treatment

The two-party warranty mechanic (supplier ships FOC replacement to OEM) is well understood. The three-party chain — end-customer claims at dealer, dealer rolls to OEM, OEM debits Tier-1 — is where most mid-sized suppliers carry quiet GST exposure. Four documents move across three parties on every claim. CBIC Circular 195/07/2022 governs each leg differently. Get one leg wrong and the audit position breaks on all four.

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 12 June 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 Tier-1 auto-component suppliers honouring end-customer warranty claims through the three-party Mahindra dealer to Mahindra OEM to Tier-1 chain face a four-document GST flow that CBIC Circular 195/07/2022 governs differently at each leg: the dealer-to-customer leg sits outside GST as a B2C original-sale coverage, the OEM-to-dealer leg is a supplier-borne non-supply under circular paragraph 2, the OEM-to-Tier-1 FOMP back-charge is a non-GST financial flow, and the Tier-1-to-OEM replacement leg is again a supplier-borne non-supply. A Tier-1 processing 1,800 three-party warranty claims per month must run a six-artefact documentation discipline across the chain, tie the FOMP back-charge to the warranty claim ID, preserve input ITC on the warranty production run, and reconcile the four-document flow on every claim — with ₹6 lakh per month of reclassification exposure if any of the artefacts is missed.

How It's Resolved

On every warranty claim received from the OEM warranty system, open a unique warranty-claim ID; trigger the production-run pull for the replacement part; raise the Rule 55 delivery challan to the OEM with the warranty-replacement narration and the OEM original-sale-invoice reference; tie the Rule 55 challan to the warranty-claim ID; receive the OEM's FOMP back-charge debit-note against the warranty-claim ID and post the back-charge in the Tier-1's books as either revenue reduction or warranty-cost charge per accounting policy; preserve the input ITC trace on the production run; reconcile the four-document flow at month-end against the OEM warranty system extract; build the six-artefact pack live throughout the year for audit defence.

Configuration

Warranty-claim ID master keyed by OEM warranty system reference, dealer reference, end-customer reference, failure mode and original sale invoice; Rule 55 delivery challan series for warranty replacements separate from production despatch; FOMP back-charge ingestion rule mapping OEM debit-note to warranty-claim ID; accounting rule for back-charge treatment (revenue reduction versus warranty-cost charge); input-ITC trace rule for warranty production runs; six-artefact reconciliation rule at month-end.

Output

A monthly three-party warranty reconciliation report tying every claim ID to four documents and six artefacts; a FOMP back-charge ledger keyed to warranty-claim ID with OEM debit reconciliation; a Rule 42 ITC-preservation defence file; a year-end GSTR-9 warranty replacement audit pack; and an exception queue for any claim where any of the four documents or six artefacts is missing.

A Tier-1 brake-pad supplier in Pune opens its monthly three-party warranty reconciliation at 14:00 IST. The OEM warranty system extract for the trailing month shows 1,810 brake-pad warranty claims raised by Mahindra dealers across India against vehicles in the XUV and Scorpio programmes. For each claim the OEM warranty system carries the dealer reference, the vehicle VIN, the failure-mode code, the original-sale-date of the part to the dealer, and the date of customer claim at the dealer. The Tier-1’s warranty-claim register shows 1,810 corresponding warranty-claim IDs opened, 1,810 Rule 55 delivery challans raised, and 1,786 FOMP back-charge entries received on the OEM’s monthly settlement statement. The CFO’s first question on the desk: 24 of the 1,810 claims are missing the FOMP back-charge debit-note. Are those 24 stale claims that Mahindra has not yet booked into the FOMP cycle (operational lag, low-risk) or are they claims that the OEM is disputing (commercial dispute, separate handling required). The CFO’s second question: of the 24, how many tie back to a Rule 55 challan that has already shipped — and if some have shipped without a backing FOMP back-charge, what is the GST classification position. GST warranty replacement auto component India in the three-party flow is a documentation discipline that mid-sized Tier-1s typically under-resource until the first GST audit finds the gap.

Quick reference

DocumentFrom → ToDocument TypeGST Position
Doc 1 — Replacement to customerDealer → End-customerRule 55 challan or Section 34 credit noteOutside GST (B2C original-sale)
Doc 2 — Replacement to dealerOEM → DealerRule 55 challan with warranty narrationNon-supply (CBIC 195/07/2022 para 2)
Doc 2 (alt) — Credit note to dealerOEM → DealerSection 34 credit noteReverses original OEM-dealer sale
Doc 3 — FOMP back-chargeOEM → Tier-1Financial debit-note, not GST documentNo GST consequence
Doc 4 — Replacement to OEMTier-1 → OEMRule 55 challan with warranty narrationNon-supply (CBIC 195/07/2022 para 2)
Input ITC on warranty stockTier-1 booksRule 42 ITC preservationNo reversal (CBIC 195/07/2022 para 3)
Section 34 credit-note windowSection 34 CGST Act30 November of following FYApplies only to credit-note leg
Common HSN — friction partsHSN 6813CBIC18% on positive supplies
Common HSN — auto partsHSN 8708CBIC18% on positive supplies
TDS on FOMP-equivalent service flowsSection 393(1)(j) code 1011CBDT2% on paid-warranty contract services only

The three parties and the four documents — step by step

The three-party warranty chain in Indian automotive aftermarket service runs:

Party A — End-customer owns the vehicle. The vehicle is under OEM warranty (or extended warranty). A part fails. The customer drives to a Mahindra-authorised dealer.

Party B — Dealer receives the customer, diagnoses the failure, raises a warranty claim in the OEM’s warranty system, and either fits a replacement brake-pad from dealer stock or orders one from the OEM. The customer is not billed for the replacement (parts and labour are warranty-covered).

Party C — OEM (Mahindra) receives the warranty claim, approves it (or rejects it for non-warranty failures), supplies a replacement part to the dealer if one was ordered, and raises a FOMP back-charge against the Tier-1 supplier whose part originally failed.

Party D (the Tier-1 supplier) receives the FOMP back-charge and ships a replacement brake-pad to the OEM to replenish OEM stock.

The four documents that move across this chain:

Document 1 — Dealer-to-customer. Either the customer takes a replacement part out of the door at zero charge (no fresh GST document is raised — the original vehicle-sale invoice from dealer to customer is treated as having absorbed the warranty obligation), or the customer prefers a refund and the dealer raises a Section 34 credit note. In the brake-pad replacement case the part-replacement path is almost universal; the credit-note path applies more often to whole-vehicle warranty claims or to recall situations.

Document 2 — OEM-to-dealer. Either the OEM ships a replacement brake-pad to the dealer on a Rule 55 delivery challan with explicit warranty replacement against original OEM-dealer sale invoice and date narration, no GST, no fresh supply under CBIC Circular 195/07/2022 paragraph 2. Or the OEM raises a Section 34 credit note against the original OEM-to-dealer sale invoice that covered the brake-pad consignment in the first place. In OEM-dealer brake-pad replenishment the Rule 55 replacement path dominates; Section 34 credit notes apply for whole-vehicle claims.

Document 3 — OEM-to-Tier-1 FOMP back-charge. Mahindra’s monthly settlement statement to the Tier-1 carries a debit line for each warranty replacement at a tabled rate (typically Mahindra’s standard cost for the brake-pad, not the supplier’s actual cost or actual sales price). This is a financial debit, not a GST document. It reduces the supplier’s cash receivable from Mahindra for the month. No GSTIN-to-GSTIN flow happens at this leg. The Tier-1’s accounting policy decides whether the back-charge is a revenue-reduction (against the original sale revenue) or a warranty-cost P&L charge.

Document 4 — Tier-1-to-OEM replacement. The Tier-1 ships a fresh brake-pad to Mahindra’s consignment warehouse (or directly to the relevant dealer in some operational variants) on a Rule 55 delivery challan with explicit warranty replacement against original sale invoice and date narration, no GST, no fresh supply under the circular. The full FOC-supply mechanic at this leg is in GST warranty replacement FOC supply for auto components.

How the FOMP back-charge is operationally different from a Section 34 credit note

A common mistake at mid-sized Tier-1s is to treat the FOMP back-charge as a Section 34 credit-note trigger. It is not. Section 34 of the CGST Act allows a supplier to issue a credit note where the taxable value or tax shown in the original invoice is found to exceed the actual value, or where the goods are returned, or where goods supplied are found to be deficient. None of these conditions apply at the Tier-1-to-OEM original sale that triggered the brake-pad consignment to OEM. The brake-pad went to production, was fitted to a vehicle, was sold to a customer — the sale stands.

The FOMP back-charge is a separate commercial arrangement between the OEM and the supplier that the warranty cost is to be borne by the supplier rather than by the OEM. It is implemented as a monthly receivable reduction with no GST document, no Section 34 credit note, no GSTR-1 amendment.

If the Tier-1 mistakenly issues a Section 34 credit note in response to the FOMP back-charge, two things happen. First, the original sale invoice GST liability gets reduced — this looks like a reduction of the supplier’s output tax in the GSTR-1 of the credit-note month. Second, the OEM’s ITC on the original purchase invoice gets a downstream reduction in the OEM’s GSTR-2B — which the OEM does not want because the original sale stands. The OEM will reject the Section 34 credit note, the Tier-1 will end up amending GSTR-1 in a subsequent period, and the audit-time position becomes complicated. The full back-charge mechanic is in FOMP warranty back-charge accounting for auto components.

Interactive Tool

Reconcile three-party warranty claims against FOMP back-charge and Rule 55 dispatch

Plug in your monthly warranty claim volume, FOMP back-charge value and Rule 55 dispatch count to size the reconciliation gap and the audit-defence exposure.

Open the three-way match exception calculator →

Worked example — Mahindra XUV brake-pad warranty claim, four documents, three parties

A specific claim through the chain.

Day 1 — End-customer claim at dealer. Customer drives Mahindra XUV-700 to a Mahindra-authorised dealer in Indore. Brake-pad noise. Diagnosis confirms a defective front brake-pad set. Vehicle is 14 months old, original purchase date 1 March 2024. Vehicle warranty is 24 months on parts — claim is in window. Dealer raises a warranty claim in Mahindra’s warranty system with a unique claim reference (MD-2025-IND-08471).

Day 2 — Replacement to customer. Dealer fits a replacement brake-pad set from dealer stock. No customer invoice for the replacement parts (original vehicle sale invoice covers warranty). Dealer raises a stock-out entry against the brake-pad set.

Day 5 — Dealer to OEM order. Dealer raises a replenishment order on Mahindra for the consumed brake-pad set, citing the warranty claim reference.

Day 8 — OEM to dealer dispatch. Mahindra ships a replacement brake-pad set to the dealer on a Rule 55 delivery challan. Narration: warranty replacement against MD-2025-IND-08471. No GST. The dealer’s stock is replenished. CBIC Circular 195/07/2022 paragraph 2 governs — non-supply.

Day 30 — Monthly FOMP back-charge cycle. Mahindra’s monthly settlement statement to the Pune Tier-1 carries a debit line for MD-2025-IND-08471 at Mahindra’s tabled brake-pad cost of ₹180 per set. The supplier’s receivable from Mahindra is reduced by ₹180. No GST document. The Tier-1’s books post ₹180 as a warranty-cost P&L charge.

Day 45 — Tier-1 to OEM replenishment. The Pune Tier-1 ships a fresh brake-pad set to Mahindra’s Chakan consignment warehouse on a Rule 55 delivery challan. Narration: warranty replacement against MD-2025-IND-08471 and Tier-1 original-sale-invoice number INV-2024-0345 dated 12 January 2024 (the original sale on which this brake-pad reached Mahindra). Standard cost ₹148 per set, no GST. CBIC Circular 195/07/2022 paragraph 2 governs — non-supply at this leg too.

Day 45 onwards — Input ITC preservation. The Tier-1’s production run that produced the warranty-replacement brake-pad consumed ₹86 of friction material, backing plate and bonding agents. Input ITC on that production run at 18% is roughly ₹15.5 per set. The ITC is preserved under CBIC Circular 195/07/2022 paragraph 3.

Aggregate financial impact at the Pune Tier-1 on this single claim: ₹180 FOMP back-charge (warranty cost in P&L) plus ₹148 standard cost of the replacement (treated as cost of warranty-replacement production), minus ₹0 GST output tax on the replacement, plus ₹15.5 of input ITC preserved. Net P&L impact: roughly ₹313 of warranty cost per claim. Across 1,810 claims per month: ₹5.67 lakh per month, ₹68 lakh annualised on the Mahindra XUV programme.

How the six-artefact pack defends the position at audit

At GST audit the position has to be defended document by document. The six-artefact pack:

Artefact 1 — Rule 55 delivery challan for the Tier-1 to OEM replacement. With explicit warranty replacement narration, warranty-claim ID, OEM original-sale-invoice reference and date. Without artefact 1 the audit can re-classify the Rule 55 challan as a fresh supply and demand GST on the standard cost (₹148 times 18% = ₹26.6 per set, times 1,810 per month = ₹4.8 lakh per month, times 12 = ₹57.6 lakh per year).

Artefact 2 — Tier-1’s warranty-claim register. Keyed by warranty-claim ID, tying each Rule 55 challan to a single OEM claim reference. Without artefact 2 the audit cannot verify that the Rule 55 dispatches actually correspond to warranty claims rather than to regular production replenishment.

Artefact 3 — OEM warranty system extract. The dealer-side claim that triggered the chain. Obtained from the OEM (typically through the supplier-portal warranty download). Without artefact 3 the audit-side challenge that the Tier-1 cannot independently verify the warranty claim is valid is hard to rebut.

Artefact 4 — OEM FOMP back-charge debit-note. Tied to the warranty-claim ID. Without artefact 4 the position that the OEM has charged the supplier for the warranty cost (and that the supplier is therefore acting on the OEM’s instruction in the replacement) is not documented.

Artefact 5 — Input ITC trace on the warranty production run. Defends the Rule 42 non-reversal under CBIC Circular 195/07/2022 paragraph 3. Without artefact 5 the audit can demand proportionate Rule 42 reversal on the warranty production share of total production.

Artefact 6 — Dealer-side warranty record. Typically obtained from the OEM if needed at audit. Confirms that the customer-end claim was genuine.

Tax overlay — adjacent flows

The three-party warranty flow itself does not trigger fresh TDS or TCS. The adjacent flows:

  • Section 393(1)(j), payment code 1011 — TDS by the OEM on any paid-warranty service contract with the supplier (services contract under new Section 393 from 1 April 2026 replacing Section 194C). Applies only to the paid-warranty-extension programmes that some OEMs run separately from the standard warranty.
  • Section 393(1)(k), payment code 1012 — TDS by the supplier on inputs purchased for warranty stock at 0.1% on aggregate purchases above ₹50 lakh per FY from any single seller. Same mechanic as for production stock.
  • GST law is unchanged by the Income Tax Act 2025. CBIC Circular 195/07/2022 continues to govern. The cross-era reconciliation with legacy 194C entries in Form 26AS for FY 2025-26 is in Form 26AS reconciliation for auto-component suppliers.

How does the three-party flow interact with GSTR-9?

Three things must tie at year-end:

  • GSTR-1 / GSTR-9 Table 4 — outward supplies on Mahindra brake-pad sales at full GST; warranty replacement dispatches do not appear because they are non-supplies.
  • GSTR-9 Table 5N — supplier-borne warranty replacements disclosed as supplies on which no GST is payable, with CBIC Circular 195/07/2022 reliance documented.
  • Tier-1 books — FOMP back-charge P&L accumulation tied to warranty-claim IDs.

The wider GSTR-9 reconciliation cycle is in GSTR-9 filing for auto-component manufacturers.

Continue reading — the auto-component reconciliation cluster

What automated reconciliation changes

Running 1,810 three-party warranty claims per month across the four-document, six-artefact discipline, tying the OEM warranty system extract to the Tier-1’s Rule 55 challan to the FOMP back-charge to the input-ITC trace, and defending the position at GSTR-9 audit with the artefact pack pre-built is where mid-sized Tier-1s spend three to six days of finance team capacity per month — and where the audit-time re-classification exposure of ₹57 lakh per year on a single OEM programme silently builds when the discipline is missing. Purpose-built auto component reconciliation software India ingests the OEM warranty system extract, opens warranty-claim IDs, ties Rule 55 dispatch to FOMP back-charge to input-ITC trace on a single ID, and produces the six-artefact pack for year-end audit defence. TransactIG carries 24+ industry presets including configurations for three-party warranty reconciliation and FOMP back-charge handling. Customer outcomes include match-rate improvement from 51% to 88% on warranty-claim to FOMP-back-charge ties. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the wider GST-side discipline see GST reconciliation software.

Primary reference: CBIC GST portal — for CBIC Circular 195/07/2022 on warranty replacement across multi-party chains, Section 31 time-of-supply rules, and Section 34 credit-note framework.

Frequently Asked Questions

What are the four documents in a three-party warranty replacement chain?
On a typical end-customer warranty claim that travels Mahindra dealer to Mahindra OEM to brake-pad Tier-1, four GST-relevant documents move. Document 1 — the dealer issues either a replacement part to the customer free of charge (no GST document needed, the original sale invoice from dealer to customer covers the consideration), or a Section 34 credit note if the customer prefers a refund. Document 2 — the OEM either ships a replacement brake-pad to the dealer free of charge (a Rule 55 delivery challan with warranty-replacement narration, no GST), or raises a Section 34 credit note against the OEM's original sale invoice to the dealer. Document 3 — the OEM debits the Tier-1 supplier through the FOMP back-charge mechanism (a financial debit, not a GST document, accounted as receivable reduction). Document 4 — the Tier-1 ships a replacement brake-pad to the OEM on a Rule 55 delivery challan with warranty-replacement narration, no GST under CBIC Circular 195/07/2022. The four-document trail is reconciliation surface across three GSTINs.
How does CBIC Circular 195/07/2022 govern each leg of the three-party chain?
Paragraph 2 of the circular says that supplier-borne warranty replacements are not fresh supplies and no GST is payable — this applies at the Tier-1 to OEM leg (document 4) and at the OEM to dealer leg (document 2 if the OEM ships a replacement rather than crediting). Paragraph 3 says the ITC on inputs used to manufacture warranty stock is preserved — applies at both legs. The dealer-to-end-customer leg (document 1) is outside the circular because the end-customer is typically a B2C unregistered party and the original sale invoice is treated as a B2C sale; the warranty replacement is part of the original consideration. The FOMP back-charge from OEM to Tier-1 (document 3) is a financial flow, not a supply — no GST document, no GSTR-1 line. The circular's two operational paragraphs cover the two B2B legs cleanly; the dealer-to-customer leg and the back-charge are outside the GST framework entirely.
What is the time of supply for each document in the three-party chain?
Document 1 (dealer to customer): the original sale invoice from dealer to customer was issued at the time of original sale, typically months or years before the warranty claim. No fresh time-of-supply applies at the warranty replacement because the supply was already taxed. Document 2 (OEM to dealer): for a replacement supply, no time-of-supply because there is no fresh supply under the circular; for a Section 34 credit note, the credit-note date governs but Section 34 caps the credit-note window at 30 November of the following FY or the annual return filing date, whichever is earlier. Document 3 (FOMP back-charge): not a supply, no time-of-supply. Document 4 (Tier-1 to OEM): no time-of-supply because no fresh supply. The replacement-supply legs simply do not generate fresh tax-points. The Section 34 credit-note leg if used has the standard Section 34 timing rules.
How is the FOMP back-charge accounted in the Tier-1 supplier's books and does it have any GST consequence?
The FOMP (Free-of-Material-Performance) back-charge is the OEM's mechanism for transferring the cost of a warranty replacement from the OEM's books back to the supplier whose part failed. Operationally the OEM debits the Tier-1's monthly settlement statement by the OEM's standard part cost (often a tabled rate, not the actual replacement-part value), reducing the Tier-1's cash receivable. In the Tier-1's books the back-charge is recorded as a reduction of revenue or as a warranty-cost charge against P&L; the exact accounting treatment depends on whether the original sale revenue is reclassified or whether a separate warranty-cost line is opened. The GST consequence is zero because the back-charge is a financial flow against an existing receivable, not a fresh supply or a return of an existing supply. There is no Section 34 credit-note from the Tier-1 against the back-charge because no original sale has been reversed — the parts physically went to production and the original sale stands. The full mechanic is in [FOMP warranty back-charge accounting for auto components](/insights/fomp-warranty-back-charge-accounting-auto-india/).
What documentation discipline defends the three-party chain at audit?
Six artefacts together: (1) the Tier-1's Rule 55 delivery challan for the replacement part to the OEM with warranty replacement against OEM original-sale-invoice and date narration; (2) the Tier-1's warranty-claim register tying the Rule 55 challan to a unique warranty-claim ID; (3) the OEM's warranty-claim system extract showing the dealer-side claim that triggered the chain; (4) the OEM's monthly FOMP back-charge debit-note tied to the warranty-claim ID; (5) the Tier-1's input-ITC trace showing the production run from which the warranty replacement was drawn (preserves the Rule 42 non-reversal under circular paragraph 3); (6) the dealer-side warranty claim record (typically obtained through the OEM if required at audit, not directly from the dealer). A Tier-1 maintaining the six-artefact pack live throughout the year defends the position cleanly; one that builds it retrospectively at audit usually surfaces material gaps in artefacts 3 and 6 and faces re-classification risk on the warranty replacements as fresh supplies subject to GST.

See how TransactIG handles reconciliation for your industry

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