Mahindra & Mahindra Supplier Payment and Debit-Note Handling for Auto-Component Suppliers

A Tier-1 brake-and-clutch supplier in Pune with ₹180 crore annual Mahindra & Mahindra billing closes the September quarter. The M&M book splits across two business units: Automotive Sector (Chakan plant supplying XUV 3XO, Scorpio-N and Thar 5-door programmes) at roughly ₹138 crore, and Farm Equipment Sector (Nagpur plant supplying tractor-platform brake assemblies for Yuvo and OJA ranges) at roughly ₹42 crore. The M&M Supplier Portal export shows 1,720 invoices for the quarter, 318 debit-memo lines split across the two businesses, four settlement statements (Auto Chakan fortnightly, FES Nagpur monthly), and a quality dashboard tracking rolling PPM across 36 part numbers. The controller is closing month-end. The question is whether the Auto Sector and FES Sector books have been correctly kept separate, whether each SUV programme’s FOMP account ties out, whether Form 168 TDS deductions under Section 393(1)(a) code 1002 reconcile against the books, and whether the accepted-debit pipeline has the Section 34 GST credit-note action queue properly calendared.

This is the operational reality of being a Mahindra Tier-1. Mahindra is structurally different from a single-business OEM because the parent corporate customer master spans two materially different businesses — Automotive Sector and Farm Equipment Sector — that share only a vendor master, not a commercial framework. This guide is the Mahindra supplier payment debit note auto India operating playbook.

Quick reference

How does Mahindra organise its supplier book across Automotive Sector and Farm Equipment Sector?

The first reconciliation question is structural: a Tier-1 that supplies both Mahindra Automotive Sector (MAS) and Mahindra Farm Equipment Sector (FES) is dealing with two materially different businesses. They share a vendor master and the M&M Supplier Portal login, but the commercial framework underneath is separate:

• Automotive Sector (MAS) — Chakan (the flagship multi-line plant — XUV 3XO, XUV700, XUV 9e, Scorpio-N, Thar 5-door, BE 6), Nashik (XUV 3XO, Bolero, Bolero Neo, LCV programmes), Igatpuri (engine plant — sources engine sub-assemblies), Haridwar (Scorpio Classic, Bolero, LCV programmes). SUV-nameplate scheduling agreements with monthly or fortnightly settlement.
• Farm Equipment Sector (FES) — Nagpur (flagship FES plant — Arjun, Yuvo, OJA platforms), Rudrapur (tractor and FES platforms for North India), Zaheerabad (Jivo, NOVO ranges). Tractor-platform scheduling agreements with monthly settlement.

Inside the Tier-1’s customer master, MAS and FES typically sit as separate parent records with shared vendor-master linkage but distinct commercial terms, distinct debit-note formats, and distinct FOMP attribution. A reconciliation engine that collapses both into a single “Mahindra” record loses programme-level visibility — a profitable XUV700 book inside MAS can hide a loss-making Yuvo book inside FES.

The M&M Supplier Portal — Mahindra’s touchpoint

The M&M Supplier Portal is Mahindra’s supplier-side delivery, quality and settlement interface. The supplier login exposes:

• Daily call-off schedules per part per ship-to plant for the next 7-14 days
• Cumulative shipment position per scheduling agreement (CUM tracking)
• Advance shipment notice (ASN) submission against scheduled call-offs
• GRN confirmation status by part by date by plant
• Settlement statements per plant per period
• Debit-memo details per claim ID with reason code, amount and underlying calculation
• Payment advice download per settlement run
• Form 168 TDS certificates per period (deducted by Mahindra, deposited against supplier PAN)
• Quality dashboards with rolling PPM per part-per-programme

The portal exposes MAS and FES as separate organisation hierarchies inside a single login. The reconciliation engine’s primary inputs are the structured settlement-statement and debit-memo exports per period per business per plant. Portal screens are operational machinery — reconciliation runs against structured exports.

SUV programme accounting — XUV, Scorpio, Thar, Bolero, BE 6

Mahindra runs each SUV nameplate as a distinct commercial unit. The active passenger portfolio:

• XUV 3XO — Chakan and Nashik-built compact SUV, the volume small-SUV programme
• XUV700 — Chakan-built mid-SUV, flagship volume programme
• XUV 9e — Chakan-built electric SUV (BEV)
• Scorpio Classic — Haridwar-built legacy SUV (continues as a volume programme)
• Scorpio-N — Chakan-built body-on-frame SUV, the flagship rugged-SUV programme
• Thar 3-door — Chakan-built lifestyle SUV
• Thar 5-door — Chakan-built family-rugged SUV (the newer Thar Roxx programme)
• Bolero — Nashik / Haridwar-built workhorse SUV, longest-running active programme
• Bolero Neo — Nashik-built sub-4m SUV
• BE 6 — Chakan-built electric SUV (BEV)

Each programme has its own scheduling agreement, tooling cap, FOMP running account and PPM threshold matrix. A Tier-1 supplying brake systems across XUV 3XO, XUV700, Scorpio-N, Thar 5-door and Bolero runs five parallel reconciliation streams.

A common part number that runs across three programmes (e.g., a common brake calliper that fits XUV 3XO / Bolero Neo / Scorpio Classic in the small-SUV family) generates three separate programme-level entries even though the part dispatch is from a single production line. The supplier’s reconciliation engine must key dispatch to programme via the call-off reference, not the part number alone.

Farm Equipment Sector — tractor-platform accounting

Mahindra FES runs scheduling agreements at the tractor-platform level rather than the model level (because each platform spawns multiple model variants for different horsepower bands and market segments):

• Arjun — high-horsepower platform (45-75 HP class)
• Jivo — small-tractor platform (20-30 HP class, orchard / vineyard / inter-cultivation use cases)
• Yuvo — mid-horsepower platform (35-45 HP class)
• OJA — modern lightweight platform launched in 2023, multi-horsepower variants (25-40 HP)
• NOVO — high-horsepower platform (50-75+ HP class) for large-farm and export segments

Tractor PPM thresholds and warranty windows differ from automotive — tractors carry longer warranty windows on power-train components and field-warranty failures follow seasonal patterns (peak claim volume in monsoon and post-harvest periods). The FES FOMP running account therefore needs seasonality-aware ageing rather than uniform monthly attribution.

Mahindra’s debit-note reason taxonomy

Mahindra’s debit notes follow a structured format with explicit line-stop coding as a distinct reason category — a Mahindra-specific design that some other OEM portals fold into general quality penalty:

1. FOMP — field warranty back-charge with claim ID, vehicle registration range, dealer reference, programme reference
2. JIT shortage — shortage event ID, called-off quantity, dispatched quantity, expediting premium
3. Quality penalty — line rejection (rejection slip ID + plant), PPM excess (rolling 12-month PPM and threshold breach), audit non-conformance from supplier-site audit
4. Line-stop charge — line-stop event ID, plant, programme, hours stopped, hourly rate applied (distinct reason code at Mahindra, not folded into quality penalty)
5. Tooling amortisation adjustment — tool ID, programme, cumulative shipped vs committed volume, over-recovery or under-recovery adjustment
6. Technical service deduction — visit log reference, plant, engineer-days, hourly rate
7. Premium freight differential — freight event reference, dispatch lane, premium-freight gap

The explicit line-stop reason code matters operationally: line-stop events at Mahindra Chakan can run ₹2-4 lakh per hour at the body-shop level for the XUV700 / Scorpio-N high-volume lines. A 4-hour line stop attributed to a brake-system supplier produces an immediate ₹8-16 lakh debit that must be validated tightly against the contracted hourly rate and the actual stop duration.

Worked example — Tier-1 with ₹180 crore annual Mahindra billing

A brake-and-clutch Tier-1 supplying Mahindra across Auto Sector (Chakan) and FES Sector (Nagpur):

Quarterly decomposition of the Auto Sector short-pay (Q2 illustrative):

• Accepted FOMP (clean warranty evidence, supplier-attributable): ₹1.18 crore → Section 34 GST credit note workflow trigger
• Accepted line-stop charges (3 events at Chakan validated against contracted hourly rate): ₹0.42 crore
• Accepted PPM penalty (1 part breached rolling 12-month threshold on Scorpio-N programme): ₹0.21 crore
• Contested JIT shortage debits (calculation error on expediting premium): ₹0.31 crore → Rule 37 ITC ageing tracker
• Pending evidence: ₹0.18 crore → must clear within contracted dispute window

Across the ₹13.12 crore full-year short-pay:

• Accepted (clean evidence, supplier-attributable): ₹8.6 crore → Section 34 GST credit notes of roughly ₹2.41 crore output-GST reversal at 28% per FY (Auto leg) plus roughly ₹0.36 crore at 18% (FES leg), must be processed by 30 November of next FY
• Contested: ₹3.4 crore → enters 60 / 90 / 150 / 180-day Rule 37 ageing
• Pending evidence: ₹1.12 crore → must clear within contracted dispute window

Form 168 TDS reconciliation on the ₹180 crore book: Section 393(1)(a) code 1002 at 2% applied to roughly 28% job-work component yields expected annual TDS of about ₹1.01 crore. Reconcile against TML-equivalent Form 168 reflected against the supplier’s PAN with monthly cadence.

Tax overlay — Section 393 and Section 394 across the M&M book

The M&M book sits inside the Income Tax Act 2025 framework effective from 1 April 2026:

• Section 393(1)(a) code 1002 — Contractor TDS at 1% / 2% deducted by Mahindra on the job-work component of the supplier’s invoices. 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 Tier-2 raw-material purchase above ₹50 lakh per FY on the supplier’s pay-side.
• Section 394 code 1071 — Scrap TCS at 1% on skeleton scrap or process-loss recoveries from Tier-2.

Legacy 194C / 194Q / 206C(1) references apply only to cross-era reconciliation of dispositions started before 1 April 2026.

SIAM reference for Mahindra suppliers

The Society of Indian Automobile Manufacturers (SIAM) is the canonical industry reference for OEM-side commercial framework benchmarks. Mahindra Automotive Sector engagement with SIAM working groups on supplier-engagement standards, OTIF KPI definitions, and quality-systems alignment maps directly to the Tier-1 commercial-term templates in use across the M&M book. The Farm Equipment Sector aligns separately to Tractor Manufacturers Association (TMA) frameworks. Most M&M Tier-1 ERP configurations use ACMA-codified reason taxonomies on the Auto Sector book and a parallel TMA-aligned taxonomy on the FES book.

What automated reconciliation changes for a Mahindra Tier-1

Manual reconciliation of a two-plant, two-business, ₹180 crore Mahindra book typically runs 9-12 days of controller time per month-end with material recovery leakage on contested line-stop and FOMP debits, plus Form 168 TDS mismatches that go un-escalated. Purpose-built auto-component reconciliation software India treats each debit reason code (including the Mahindra-specific explicit line-stop reason) as a structured variance stream, decomposes settlement at the business-plant-programme level, and runs Form 168 TDS reconciliation against books. TransactIG carries 24+ industry presets including an auto-component configuration that handles plant-coded settlement, programme-level FOMP, Mahindra’s explicit line-stop reason coding, FES tractor-platform decomposition, Section 34 GST credit-note timing, Rule 37 ageing, and Section 393(1)(a) code 1002 deductions. Customer outcomes include match-rate improvement from 51% to 88% post-implementation. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement side see three-way matching software India.

Continue reading

Sibling articles in the auto-component cluster:

• Maruti Suzuki supplier settlement process
• OEM-Tier 1 settlement and debit-note reconciliation
• OEM delivery schedule and EDI/ASN reconciliation

Up the chain:

• Sub-pillar: Automotive component manufacturing reconciliation in India
• Money pages: auto-component reconciliation software India · three-way matching software India