Maruti Suzuki Supplier Settlement Process: Payment Terms, Debit Notes, and Reconciliation

A Tier-1 brake-system supplier in Manesar with ₹150 crore annual Maruti Suzuki billing closes the September quarter. Settlements landed against four Maruti plants: Gurgaon, Manesar Plants A and B, and Suzuki Motor Gujarat Hansalpur. Five vehicle programmes — Brezza, Swift, Baleno, Dzire, and the recently launched Grand Vitara — each with its own scheduling agreement and FOMP running account. e-Nagare export shows 1,847 invoices for the quarter, 312 debit-memo lines, four settlement statements per plant, and a separate quality dashboard tracking rolling PPM per part across 38 part numbers. The controller is closing month-end. The question is not “is the data complete” but “have we matched everything, and is the programme-level margin per Maruti programme actually what we think it is.”

This is the operational reality of being a Maruti Suzuki Tier-1. Maruti carries roughly 40% of the Indian passenger-car market, which means almost every brake, transmission, suspension, electrical, and interior Tier-1 in India has Maruti as their single largest customer. The settlement regime is specific. This guide is the Maruti Suzuki supplier settlement India operating playbook for a Tier-1 finance team.

Quick reference

How does Maruti’s payment cycle actually run from GRN to bank credit?

The Maruti payment clock starts at GRN — the moment the receiving plant confirms goods receipt in its system. Not invoice date. Not dispatch date. This matters because the supplier’s invoice date may be the dispatch date, but the GRN can lag by days (transit time, queue at receiving dock, weekend pauses). A dispatch on 1 October that GRN-confirms on 8 October starts the payment cycle on 8 October — at T+60 the cash lands on 7 December.

The T+45 to T+60 band varies by programme and supplier rating. Higher-rated suppliers on critical programmes (Brezza, Grand Vitara) typically sit at T+45; lower-rated suppliers on legacy programmes (WagonR, S-Presso) typically sit at T+60. New suppliers in the first 12 months of relationship are sometimes started at T+60 and migrate to T+45 as supplier rating stabilises.

Settlement cadence is fortnightly or monthly. A high-volume programme like Brezza or Swift typically runs fortnightly settlement; a lower-volume programme like Ciaz or Invicto typically runs monthly. The settlement statement is published on e-Nagare on the settlement date with a 30-day dispute window from publication.

e-Nagare — Maruti’s supplier portal touchpoint

e-Nagare is the public-facing name for Maruti Suzuki’s supplier-side delivery and settlement interface. Tier-1 suppliers use it as the primary daily interaction point. The supplier login lets the finance and operations teams pull:

• Daily call-off schedules per part per ship-to plant (the next 7-14 days of required delivery)
• Cumulative shipment position per scheduling agreement
• Advance shipment notice (ASN) submission
• GRN confirmation status by part by date
• Settlement statements per plant per period
• Debit-memo details per claim ID, reason code, and amount
• Payment advice download per settlement run

The reconciliation engine’s input is the settlement-statement export. The structured CSV/Excel export from e-Nagare per settlement period is the canonical input that feeds the supplier’s OEM payment decomposition. Reconciliation reads each line, classifies it as invoice payment / partial payment / pure debit memo / credit memo, and routes the debits to the reason-taxonomy classifier.

We will not describe e-Nagare’s portal-internal endpoints, URL structures, or screen layouts here — those are Maruti’s operational machinery, not public reference, and details can change between portal revisions. The reconciliation engine integrates against the structured export, not against scraped page state.

The Maruti debit-note format and reason coding

Maruti’s debit notes follow a structured format aligned to the seven-category reason taxonomy that ACMA has codified across Indian OEMs:

1. FOMP — field warranty back-charges with warranty claim ID, vehicle VIN range, dealer ID
2. Quality penalty — line rejection (rejection slip ID + plant), PPM excess (per-part PPM and threshold breach), audit non-conformance
3. JIT shortage — shortage event ID, called-off quantity, dispatched quantity, expediting premium
4. Line-stop charge — line-stop event ID, plant, programme, hours stopped, hourly rate applied
5. Tooling amortisation adjustment — tool ID, programme, cumulative shipped, cap, over-recovery amount
6. Technical service deduction — visit log reference, plant, engineer-days, hourly rate
7. Transport debit — freight event reference, dispatch lane, premium freight differential

Maruti’s debit memos cite the contractual per-unit rate, the calculation, and the underlying claim ID. The supplier’s reconciliation engine validates each component:

• Is the rate the contracted rate per scheduling agreement?
• Is the claim ID valid in Maruti’s tracking system (cross-checked via e-Nagare)?
• Is the calculation arithmetically correct?
• Does the warranty claim fall within the supplier’s contractual warranty period for that part?

Industry observation: 12-18% of OEM debits across Indian OEMs fail this validation at first pass, with Maruti debit-note error rates typically at the lower end (10-14%) given Maruti’s more mature settlement infrastructure.

FOMP running account at Maruti — per-programme management

Maruti runs a separate FOMP running account per vehicle programme per Tier-1 supplier. A brake-system supplier carrying Brezza, Swift, Baleno, Dzire, and Grand Vitara has five parallel FOMP accounts. New warranty claims from the field hit the relevant programme’s account; closed claims (resolved through dispute, withdrawn, or absorbed) exit the same account.

The supplier’s reconciliation engine must mirror this structure. A single combined FOMP register collapsing across programmes loses the management visibility — a profitable Brezza programme can hide an unprofitable WagonR programme inside the combined number. The per-programme view enables:

• Per-programme cumulative parts shipped × per-part rate = programme revenue
• Per-programme FOMP exposure = open claims × claim amount
• Per-programme tooling cap status (cumulative shipped vs committed volume)
• Per-programme PPM trend
• Programme-level margin: revenue minus material minus conversion minus FOMP provision minus tooling clawback minus PPM penalty

This is the canonical management report a Maruti Tier-1 CFO needs to make programme-level decisions (rate negotiation at programme refresh, decision to bid on new programmes, allocation of capacity).

Maruti’s PPM threshold regime — rolling 12-month

The PPM threshold is a contractual quality metric: parts-per-million defect rate over a rolling 12-month window. Maruti sets the threshold per part based on safety-criticality and historical defect baselines:

• Safety-critical parts (brake systems, airbag components, steering, seatbelts, fuel system): 50 PPM is typical
• Functional-critical parts (transmission, suspension, electrical, cooling): 200-500 PPM
• Non-critical body and trim: 500-1,000 PPM

The calculation: (line-rejection parts in trailing 12 months + field-warranty failures traceable to that part) ÷ parts dispatched in trailing 12 months × 1,000,000.

Breach triggers a contractual penalty applied to trailing 90 or 180-day billing on that part, plus mandatory 8D corrective action with a 30-day response cycle. Persistent breach (multiple consecutive months) can trigger Maruti supplier-rating downgrade and exclusion from new programme bidding — a strategic risk far larger than the immediate penalty.

The supplier’s reconciliation engine maintains rolling PPM per part per programme with alerts at 60% / 80% / 95% / 100% of threshold. The 80% alert is the practical action trigger — by 100% the contractual penalty has already started accruing.

Vehicle programme accounting — Brezza, Swift, Baleno and the rest

Maruti operates each vehicle programme as a distinct commercial unit:

• Brezza — Manesar-built compact SUV, high-volume programme, typical safety-critical part programmes (brake, airbag) at 50 PPM
• Swift — Manesar-built hatch, the heritage volume programme
• Baleno — Manesar-built premium hatch, Nexa channel
• Dzire — Manesar/Gurgaon-built compact sedan
• WagonR — Gurgaon-built entry hatch, longest-running programme
• S-Presso — Gurgaon-built micro-SUV
• Ertiga — SMG Hansalpur-built MPV
• Ciaz — SMG Hansalpur-built sedan
• Grand Vitara — SMG Hansalpur-built mid-SUV, includes the strong-hybrid variant (5% GST on EV components)
• Jimny — SMG Hansalpur-built lifestyle SUV
• Fronx — Manesar-built crossover, Nexa channel
• Invicto — SMG Hansalpur-built premium MPV

Each programme has its own scheduling agreement, tooling, FOMP running account, and PPM threshold matrix. The reconciliation engine keys every transaction to the programme. A part number that runs across three programmes (e.g., a common brake calliper variant on WagonR / S-Presso / Dzire) generates three separate programme-level entries even though the part dispatch is from a single production line.

The Manesar / Gurgaon / SMG Hansalpur / Kharkhoda plant distinction

Each Maruti plant operates its own GRN, settlement, and debit-note flow:

• Gurgaon (IMT Gurgaon) — the original Maruti plant, runs WagonR, S-Presso, Dzire variants
• Manesar Plants A / B / C — multi-line site, runs Brezza, Swift, Baleno, Fronx, Dzire variants
• Suzuki Motor Gujarat (SMG) Hansalpur — operated by SMG (the Suzuki-owned manufacturing joint-venture), runs Brezza, Baleno, Ertiga, Ciaz, Grand Vitara, Jimny, Invicto. Billing entity is SMG, not Maruti Suzuki India Limited (MSIL).
• Kharkhoda — the new site, ramping production

The SMG distinction matters for finance: SMG is a separate billing entity from MSIL. Tier-1 invoices for parts dispatched to Hansalpur are billed to SMG, not MSIL. GSTIN, payment terms, debit-note format, and settlement statements run on the SMG instance, with similar but not identical commercial terms to the MSIL plants. The supplier’s customer master must carry both MSIL and SMG as separate parent records with shared scheduling-agreement linkage.

Worked example — Tier-1 with ₹150 crore annual Maruti billing

A brake-system Tier-1 supplying five Maruti programmes across three plants (Manesar, Gurgaon, SMG Hansalpur):

Across the ₹10.78 crore annual short-pay:

• Accepted (clean evidence, supplier-attributable): ₹7.0 crore → Section 34 GST credit notes = ₹1.96 crore output GST reversal at 28% per FY, must be processed by 30 November of next FY
• Contested (weak evidence, calculation error): ₹2.7 crore → enters 60 / 90 / 150 / 180-day Rule 37 ageing
• Pending evidence: ₹1.08 crore → must clear within 30-day dispute window

Tier-2 passthrough on the accepted ₹7.0 crore: roughly ₹4.9 crore (70%) traces to specific Tier-2 vendors. At full recovery, ₹4.9 crore of Tier-2 back-charge revenue. Excel-driven shops leak at least 30% (₹1.47 crore annually).

Programme-level margin visibility — without the per-programme decomposition, the controller cannot see that Dzire (9% short-pay) is dragging the book down while Brezza (7%) is profitable. Re-negotiation conversations with Maruti’s purchase team at programme refresh need the per-programme number, not the blended ₹10.78 crore.

Tax overlay — Section 393 / 394 on the Tier-2 chain

The Tier-2 back-charge leg sits inside the new Income Tax Act 2025 framework effective from 1 April 2026:

• Section 393(1)(a) code 1002 — Contractor TDS at 1% / 2% on every Tier-2 heat-treatment, plating, machining, and assembly job-work payment. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India for the full code map. The TDS code 1002 deduction applies on every passthrough recovery cycle where the Tier-2 provides job-work services.
• Section 393(1)(k) code 1012 — Purchase TDS at 0.1% on aggregate Tier-2 raw-material purchase above ₹50 lakh per FY.
• 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.

ACMA reference for Maruti suppliers

The Automotive Component Manufacturers Association of India (ACMA) is the canonical industry reference for Maruti Tier-1 commercial frameworks. ACMA’s Supplier Excellence Programme materials, OTIF score methodologies, and back-charge taxonomies align directly to Maruti’s Supplier Quality Manual outputs, and most Tier-1 ERP configurations use ACMA’s standardised reason codes as the master vendor-master debit-reason taxonomy. ACMA Annual Session is the primary industry forum where Maruti Vendor Development and the Tier-1 community converge.

What automated reconciliation changes for a Maruti Tier-1

Manual reconciliation of a five-programme, three-plant, ₹150 crore Maruti book typically runs 8-12 days of controller time per month-end with material recovery leakage on Tier-2 passthrough and lapsed Section 34 windows. 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 Maruti’s plant-coded settlement structure, programme-level FOMP running accounts, rolling 12-month PPM tracking, Section 34 GST credit-note timing, Rule 37 ageing, and Section 393(1)(a) 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). For the inbound procurement side see three-way matching software India.

Continue reading

Sibling articles in the auto-component cluster:

• OEM-Tier 1 settlement and debit-note reconciliation
• How Indian auto-component suppliers handle OEM short-pays
• OEM delivery schedule and EDI/ASN reconciliation

Up the chain:

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