Supplementary Invoices for RMPV Price Escalation: GST Section 34 Treatment for Auto Suppliers

A wire-harness Tier-1 supplying to Mahindra at Chakan closes the H1 RMPV review on Friday. The JPC copper composite for the April-September dispatch window has moved up sharply, and the agreed pass-through formula clears an upward revision of ₹38 lakh against ₹4.8 crore of base invoices already raised, paid and posted. The OEM’s RMPV letter is countersigned. The commercial flow is clean. But the GST output liability on the ₹38 lakh escalation has not yet been pushed through any document, and the controller’s question on Monday morning is the only one that matters: do we raise a supplementary invoice or a debit note?

The question looks like a documentation detail. It is not. The wrong choice on the supplementary invoice price escalation auto component GST decision breaks the IRN flow at the Invoice Registration Portal, breaks the GSTR-1 Table 9B linkage to the original invoice number, and breaks the OEM-side GSTR-2B reflection that lets the OEM accept the document and avail the additional ITC. The supplier gets a one-time pass; the OEM finance team raises a query on the next reconciliation cycle; and the document has to be reissued under the right section — by which time the cohort has aged into multiple GSTR-1 periods and the cleanup is materially harder.

Quick reference

What Section 34(3) actually does and how it differs from Section 31(3)(c)

Section 34(3) of the CGST Act 2017 reads in operative terms: where a tax invoice has been issued for the supply of any goods or services and the taxable value or tax charged in that invoice is found to be less than the taxable value or tax payable in respect of such supply, the registered person, who has supplied such goods or services, shall issue to the recipient a debit note containing such particulars as may be prescribed.

Section 31(3)(c) reads differently. It allows the supplier to issue a revised tax invoice (in pre-registration cases) or a supplementary tax invoice (in defined scenarios) where the original invoice was issued before the actual taxable value or rate was crystallised — provisional invoices, rate-clarification cases, or where the original document was deficient on its face. The distinction in practice:

• Original invoice was correct at issue, subsequent event raised the value → Section 34(3) debit note.
• Original invoice was provisional or deficient at issue → Section 31(3)(c) supplementary invoice.

An RMPV upward revision settled six months after dispatch falls squarely in the first case. The original invoices were correct at the time of supply — they carried the contractually agreed base rate as of the dispatch period. The upward adjustment did not exist at the time of supply and could not have been included on the original invoice. It crystallised on the RMPV settlement when the index reference and the look-back period combined to produce the differential. That is the textbook Section 34(3) condition.

The supplementary invoice would be the correct instrument only where the original dispatch invoices themselves carried a “provisional rate, subject to RMPV finalisation” clause and the original document was deficient by design at the time of issue. A small subset of auto-component OEM contracts run on that model — most do not.

Why the document choice matters operationally

Four operative consequences flow from the document choice and break if the choice is wrong.

1. IRN flow at the Invoice Registration Portal. For suppliers above the e-invoice turnover threshold, the document must be registered on the IRP. The IRP accepts document types INV (tax invoice), CRN (credit note) and DBN (debit note). A debit note carries document type DBN with the original invoice’s IRN as the linked reference in the document-reference field. A supplementary invoice routed as INV has no such backward reference and breaks the linkage at the IRP. The reverse — a true supplementary invoice routed as DBN — picks up an IRN but mis-signals the legal basis.

2. GSTR-1 Table 9B linkage. Table 9B (CDNR — Credit/Debit Notes Registered) on the supplier’s GSTR-1 captures debit notes against registered recipients with original-invoice number, original-invoice date, debit-note number, debit-note date, taxable value of the differential only, tax breakup and reason code. The auto-population picks up the document from the IRP. A document routed as INV does not flow into Table 9B; it tries to flow into Table 4A (B2B regular invoices) and breaks the recipient match because the recipient’s books and GRN show no fresh receipt for that value.

3. OEM-side GSTR-2B reflection. The OEM receives the document in its GSTR-2B. For a debit note the IMS allows the OEM to accept, reject or hold the document; the accepted differential adds to the OEM’s ITC for the period. A document routed as a fresh tax invoice tries to surface as a new B2B inward supply against a GRN that doesn’t exist. The OEM’s three-way match rejects it.

4. Time of supply and interest. Section 50 interest exposure does not run on a Section 34(3) debit note where the escalation crystallised on settlement — the obligation did not exist before the settlement, and the document reports in its own issue period. A document that masquerades as a corrective amendment of an under-reported original liability could pull interest from the original supply date. The label matters.

When the supplementary invoice route is right

Three narrow scenarios in auto-component contracts call for the Section 31(3)(c) supplementary invoice.

First, provisional-rate dispatches. Some OEM Schedule-A agreements run on a provisional-rate clause where the dispatch invoices carry an indicative base rate explicitly marked provisional, with the final rate to be confirmed at month-end review. The original document is deficient on its face. When the final rate is determined the supplier issues a Section 31(3)(c) supplementary invoice for the differential. This is the textbook Section 31(3)(c) case.

Second, rate-clarification cases. Where an HSN reclassification or a GST Council rate-revision applies retrospectively and the original invoices were issued under the now-superseded rate, a supplementary invoice is the cleaner instrument because the original tax charged was incorrect against the (retrospectively) applicable rate. The document curing this is a supplementary invoice, not a debit note.

Third, cross-year consolidated escalation where the supplier and OEM elect, by mutual agreement and with tax workpaper backing, to issue a single supplementary invoice for the FY 2025-26 dispatches once the cumulative RMPV review for the year completes. This is a practical-conformance position rather than a strict-statutory reading. It needs careful documentation in the RMPV settlement letter and the supplier’s tax workpapers because the audit defence rests on the agreed protocol, not the section text.

Outside these three, an RMPV upward revision after the dispatch period closes is a Section 34(3) debit note.

How the IRN flow works for a debit note

The IRP payload for a debit note under document type DBN carries the same shape as a tax invoice JSON with three structural differences. The document-type field reads DBN. The document-reference object carries the original invoice’s IRN, document number and document date as a linked reference. The taxable value reflects only the escalation differential — not the original invoice value plus the differential.

Practically the supplier’s billing system generates one debit-note document per original tax invoice in the cohort. A six-month RMPV upward revision against ₹4.8 crore of base dispatches typically spans 120 to 180 original invoices. Each gets a proportionate share of the ₹38 lakh escalation, computed pro-rata on base value, and a debit-note IRN keyed to the original invoice IRN. The IRP returns one IRN per debit note and the documents flow into GSTR-1 Table 9B as 120 to 180 line items in the same return period.

An alternative — a single consolidated debit note against a “schedule of original invoices” attached as a working — is operationally simpler but breaks the GSTR-1 Table 9B per-invoice linkage and the OEM-side three-way match. Most disciplined Tier-1s carry the per-invoice line and absorb the document volume.

Worked example — Mahindra wire-harness supplier, six-month RMPV settlement

A Tier-1 wire-harness supplier dispatched to Mahindra Chakan over the April-September 2026 H1 window. Base invoices: 152 documents totalling ₹4.80 crore. The RMPV clause references the JPC copper composite with a six-month look-back and a pass-through factor of 70% on the copper-content portion of each programme code.

The H1 RMPV review completes on 8 October 2026. The JPC composite has moved up over the look-back period; the differential, applied to copper content per programme code per dispatch line, totals ₹38 lakh. The OEM RMPV settlement letter is countersigned on 11 October.

Document construction:

• Base cohort: 152 original invoices, totalling ₹4.80 crore base taxable value at 18% GST (HSN 8544 — insulated electrical conductors / wire harnesses).
• Original output GST already remitted: ₹86.40 lakh against the cohort.
• Escalation: ₹38 lakh on the cohort, pro-rata apportioned across the 152 invoices.
• Additional output GST: ₹38 lakh × 18% = ₹6.84 lakh, to be reported in October 2026 GSTR-1 Table 9B and GSTR-3B Table 3.1(a).
• Document choice: Section 34(3) debit note. Original invoices were correct at issue against the then-applicable base rate; the upward escalation crystallised on the RMPV settlement.
• IRN flow: 152 DBN documents on the IRP, each linked to one original invoice IRN, generated 11–13 October.
• GSTR-1 October 2026: 152 lines in Table 9B (CDNR), reason code “price revision” (06).

OEM-side flow at Mahindra:

• The 152 debit notes appear in Mahindra’s GSTR-2B for October 2026.
• IMS acceptance: Mahindra’s finance team accepts the cohort against the settled RMPV letter.
• ITC pickup: ₹6.84 lakh additional ITC available against the wire-harness GRNs.
• Three-way match: each debit note is matched as a value-only addition to the original GRN line, not a fresh receipt.

What goes wrong if the document is routed as a supplementary invoice:

• The 152 documents try to flow into GSTR-1 Table 4A (B2B regular) as fresh tax invoices.
• Mahindra’s GSTR-2B picks them up as 152 new B2B receipts with no GRN reference.
• Mahindra’s three-way match rejects the cohort; IMS holds it as “pending clarification”.
• Supplier finance team has to reverse-out the documents, reissue as debit notes, and refile both periods.
• Cleanup time on a 152-document cohort: typically 4–8 weeks of joint reconciliation calls.

The ₹6.84 lakh of output liability does not move — but the document audit trail breaks, the OEM’s books and the supplier’s books decouple for that period, and the next quarter’s GSTR-2B reconciliation carries the cleanup overhead. None of that arises if the document choice is correct on day one.

Tax overlay — Section 393 framework, no change at debit-note issue

The Section 34(3) debit note adds GST output liability on the escalation. It does not pull any TDS adjustment at the OEM end — TDS under Section 393(1)(a) on the original component supply already attached to the original invoice flow at payment time, computed on the original invoice value. The debit note is processed as a value-only addition for output-tax and ITC purposes, not as a fresh contract trigger.

If the OEM pays the escalation as a separate settlement on receipt of the debit note — typically as a one-line addition to the next monthly settlement run — the TDS already applied on the base cohort does not get topped up at the OEM end either. The Section 393 framework applies on the contract value as defined; an RMPV pass-through escalation against a defined formula is treated as an integral part of the original contract value, not a fresh contract trigger. The wider Section 393 frame is in Section 393 TDS under the new Income Tax Act and the payment-code stack in TDS payment codes 1001-1092.

Where the RMPV settlement instead clears as a separate purchase order at the OEM end — unusual but not unheard of in older Schedule-A constructions — the TDS attaches on the separate PO settlement at the applicable rate. The OEM’s tax workpapers will identify the routing.

How the debit-note flow cross-checks against GSTR-2B at the OEM

The OEM’s GSTR-2B for October 2026 will carry the 152 debit notes in the CDNR section against the supplier’s GSTIN. The OEM finance team runs three checks before accepting:

• Original invoice reference matches the OEM’s purchase order and GRN ledger.
• Escalation amount matches the RMPV settlement letter for that period.
• Tax breakup matches the OEM’s expected ITC pickup at 18%.

The acceptance flows through the Invoice Management System. Accepted documents move into the OEM’s ITC for October 2026. Rejected or held documents trigger a joint reconciliation call between the supplier’s tax team and the OEM’s accounts payable team. The wider GSTR-2B reconciliation discipline at the auto-component end is dissected in GSTR-2B reconciliation for auto-component manufacturers with job-work inputs.

Continue reading — the auto-component reconciliation cluster

• Sub-pillar: Automotive component manufacturing reconciliation in India.
• Downward leg: GST credit note on OEM price reduction (Section 34) — the mirror case where the index moves down.
• RMPV mechanics: RMPV clause for auto-components in India — the underlying formula that drives the document.
• OEM-side GSTR-2B: GSTR-2B reconciliation for auto-component manufacturers.
• External authority: the GST Portal — Central Board of Indirect Taxes and Customs for Sections 31(3)(c) and 34(3) of the CGST Act and the e-invoice debit-note specification.

What automated reconciliation changes

Manual handling of a 152-document RMPV debit-note cohort across the IRP, GSTR-1 Table 9B, GSTR-3B Table 3.1(a) and the OEM-side IMS acceptance is where the document-choice error quietly enters and the next quarter’s reconciliation carries the cost. Purpose-built auto component reconciliation software India ingests the RMPV settlement letter, classifies the upward versus downward direction, selects the Section 34(3) debit note as the default document for finalised originals, apportions the escalation across the base cohort pro-rata, generates the IRN payloads with original-invoice linkage, queues the GSTR-1 Table 9B export with reason code, tracks OEM-side IMS acceptance, and produces a board-visible RMPV cycle dashboard tied to the document audit trail. TransactIG carries 24+ industry presets including configurations for RMPV upward and downward cycles and the debit-note versus supplementary-invoice decision. Customer outcomes include match-rate improvement from 51% to 88% on RMPV-driven document cohorts. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound match discipline see three-way matching software India.