Maruti e-Nagare for Delivery Schedule Reconciliation: A Finance Team Guide

A Tier-1 stamping and brake-system supplier in Manesar runs a ₹180-crore annual Maruti Suzuki book across four plants — Gurgaon, Manesar Plants A and B, Suzuki Motor Gujarat Hansalpur — and seven active vehicle programmes including Brezza, Swift, Baleno, Dzire, WagonR, Ertiga and the recently launched Grand Vitara. The October monthly close lands. e-Nagare exports for October run to 2,140 firm call-off lines across 34 part numbers, 1,820 ASN entries, 1,805 GRN confirms, 184 debit-note lines and two settlement runs (fortnightly cadence for the Manesar PV programmes; monthly for Gurgaon utility programmes). The finance controller has 16 working days to close. The discipline that makes that close-out land on time is a daily e-Nagare extract that flows into a weekly reconciliation routine — not an end-of-month catch-up sprint. This is the Maruti e-Nagare delivery schedule reconciliation India operating discipline for a Tier-1 finance team.

Quick reference

What e-Nagare is — the supplier-side flow portal

e-Nagare (the kana means “flow”) is Maruti Suzuki’s primary supplier-side touchpoint, supplementing the EDI/IDoc transport for SAP-integrated suppliers and serving as the sole transport for non-SAP supplier estates. The portal carries the full delivery-schedule lifecycle — forecast, firm call-off, ASN, GRN, debit notes, payment advices — keyed per part per Maruti plant. The Japanese-origin name reflects Maruti’s Suzuki heritage and the Toyota Production System derivative discipline that underlies Maruti’s JIT and JIS supply-chain practice.

For a Tier-1 finance team, e-Nagare is operationally inescapable. The portal is the daily input — and the daily output — of the supplier’s interaction with Maruti’s procurement and supply-chain operations. Every dispatch needs an ASN logged in e-Nagare. Every GRN reflects in e-Nagare. Every debit note lands in e-Nagare. Every payment advice ships via e-Nagare. The finance team’s reconciliation engine must treat e-Nagare as the canonical input.

For the broader Maruti commercial-term context, see the Maruti Suzuki supplier settlement process deep dive.

The e-Nagare data model — daily firm plus weekly forecast

e-Nagare’s call-off model carries two distinct horizons:

• Daily firm call-off. The next-day to next-few-days firm quantity. Authorised dispatch. The supplier ships against this. Each daily firm carries CUM-required for the part-plant-programme combination as of the call-off date.
• Weekly forecast horizon. The 4–12 week planning quantity. Non-binding. Used by the supplier for capacity planning, raw-material booking (typically against the prevailing JPC HR coil index or LME aluminium index for steel and aluminium parts), and workforce shift scheduling.

For finance, the two horizons map to different uses:

• The daily firm is the receivables-build basis (subject to dispatch and GRN confirmation, with Ind AS 115 control transfer at GRN).
• The weekly forecast is cash-flow forecasting input only — never recognised as committed receivable.

A common finance error is to use the weekly forecast as a receivable-build basis. The forecast is not a commitment. Receivable builds only as the daily firm firms up, the dispatch happens, and the GRN confirms. The EDI 830/862/856 finance primer covers this distinction at the EDI layer; e-Nagare carries the same logical distinction at the portal layer.

The four-plant distinction in e-Nagare

Maruti’s current production footprint in e-Nagare:

A Tier-1 supplying across multiple plants runs separate call-off streams, separate ASN logs, separate GRN confirmations, separate debit-note cycles and separate payment advices per plant. The reconciliation discipline: per-plant close first, programme-level roll-up next, customer-level aggregation last. SMG Hansalpur is operated by the Suzuki Motor Gujarat joint-venture entity — billing and TDS deduction flow through SMG, not directly through Maruti Suzuki India — which adds a separate TDS receivable register.

JIS sequencing — line-side delivery and e-Nagare sequence data

For parts on JIS supply (typically interior trim, seat assemblies, instrument-panel sub-assemblies, exhaust systems, fuel-tank assemblies, headlamp assemblies on premium programmes), e-Nagare carries sequence data on the firm call-off and ASN acknowledgement. The supplier must dispatch the parts in the exact sequence the OEM assembly line will consume — typically keyed to chassis number or vehicle build sequence within a takt-time window.

For finance reconciliation, JIS supply does not change the periodic-invoice cycle (billing remains against confirmed-received quantity for the billing window) but tightens the operational discipline:

• A sequence mismatch (right part, wrong sequence) at the line can trigger a line-stop event.
• A line-stop FOMP claim from Maruti can run into substantial debit-note amounts depending on duration and downstream impact.
• The FOMP claim is debited against the next settlement run and decomposed in e-Nagare’s debit-note register.

The finance team must monitor the operational JIS-mismatch register feeding into FOMP debits, and the FOMP debit cycle must be reconciled per-plant per-programme rather than aggregated at customer level.

The daily-extract to weekly-reconciliation routine

The discipline that makes Maruti month-end close land on time is daily extraction with weekly reconciliation. The routine:

Daily (every working day):

• Extract daily firm call-off CSV per plant from e-Nagare. Land into reconciliation engine keyed by part-plant-programme.
• Extract ASN log per plant. Reconcile to dispatches authorised against the firm call-off (delivery-tolerance applied).
• Extract GRN confirm log per plant. Reconcile to ASN with the CUM-shipped-vs-CUM-received four-way check.
• Flag any same-day CUM drift exception to a standing queue.

Weekly (Monday close-out for prior week):

• Reconcile per-plant CUM-required vs CUM-shipped vs CUM-received per scheduling-agreement line.
• Apply delivery-tolerance to ASN-vs-GRN gaps; resolve outside-tolerance gaps via joint reconciliation with Maruti inbound team.
• Update CUM-drift exception register with originating-ASN traceability (see the CUM drift article).
• Process JIS sequence-mismatch exceptions and link to any operational FOMP risk.
• Generate periodic GST e-invoices per plant for the prior week, billed against confirmed-received quantity. IRN from IRP, e-way bills linked.

Fortnightly or monthly (per settlement cadence):

• Reconcile settlement-statement extract per plant per programme.
• Decompose debit-note register by reason: quality reject (Section 34 candidate), line-stop FOMP, PPM penalty, tooling clawback, freight, premium freight.
• Match payment advice to invoices net of debits and Section 393 TDS deduction.
• Match net bank remittance.
• Update programme-level cumulative margin tracker.

Quarterly:

• Reconcile Section 393(1)(a) and 393(1)(k) TDS deducted across e-Nagare advices to Form 168 and Form 26AS.
• Verify rolling-12-month PPM per part is within contractual threshold; flag near-breach to operations.

Year-end (around 1 April reset):

• Carry-forward CUM agreement with Maruti per plant per scheduling-agreement line.
• Reset CUM-required and CUM-shipped to zero for the new FY.
• Reset programme-level FOMP, tooling cap and PPM windows per agreement.

Worked example — Tier-1 supplying ₹180 crore annually to Maruti

A Tier-1 brake-system supplier in Manesar runs a ₹180-crore annual Maruti book. Four plants served: Gurgaon (₹35 crore), Manesar Plant A (₹62 crore — Swift, Baleno, Dzire), Manesar Plant B (₹48 crore — Brezza, Grand Vitara), SMG Hansalpur (₹35 crore — Baleno, Brezza, Fronx). Seven active programmes. Monthly billing average ₹15 crore.

October mechanic (representative month):

November payment advice mechanic (against October invoices):

• Fortnightly settlement for Manesar Plants A and B, SMG Hansalpur: two payment advices each.
• Monthly settlement for Gurgaon: one payment advice.
• Gross invoice ₹15.4 crore − ₹62 lakh debits − Section 393(1)(a) TDS (where applicable on conversion charges, code 1002) of, say, ₹15 lakh on ₹7.5 crore conversion portion at 2% − Section 393(1)(k) TDS (where applicable on straight supply, code 1012) of, say, ₹6 lakh − other deductions ₹4 lakh = ₹14.13 crore net.
• Bank receipt matched per plant.

Quarterly reconciliation to Form 168 and Form 26AS:

• Section 393(1)(a) TDS for Q3 deducted by Maruti and SMG Hansalpur reconciled to TDS receivable register and to Form 168 visibility.
• Section 393(1)(k) TDS for Q3 reconciled to Form 26AS.
• Section 34 GST credit notes raised against ₹18 lakh accepted quality-reject debits, calendared to 30 November of next FY.

Programme-level cumulative margin tracker:

• Per-programme tracker: cumulative parts shipped × per-part margin minus programme-attributable FOMP / tooling / PPM penalty. The Grand Vitara programme is showing a tighter margin than Brezza because of higher FOMP attribution during the model launch period; the Swift programme is steady-state at expected margin band.

For the broader Maruti commercial-term mechanics, see the Maruti Suzuki supplier settlement process deep dive. For the underlying delivery-schedule and ASN reconciliation primer, see the EDI 830/862/856 finance primer. For the sub-pillar and broader context, see the automotive component manufacturing reconciliation sub-pillar and the manufacturing reconciliation pillar. For all-India PV production statistics that shape Maruti’s scheduling cadence, see the Society of Indian Automobile Manufacturers (SIAM).

Tax overlay — Section 393(1)(a), Section 393(1)(k), Form 168 visibility

Under the Income Tax Act 2025, Maruti and SMG Hansalpur deduct TDS on the conversion-charge portion of auto-component supply at Section 393(1)(a) — payment code 1002 where the supply is structured as a works contract or job-work flow. Where the supply is a straight goods supply with no labour conversion content, Section 393(1)(k) — 2%, payment code 1012 applies on the periodic invoice value. The legacy Section 194C reference survives only for transitional cross-era Form 168 / Form 131 / Form 141 reconciliations.

Form 168 visibility — the supplier’s tax dashboard view of TDS deducted by the payer — reflects the deduction-code mapping at the OEM end. A Tier-1 with both works-contract conversion content and straight goods supply across different parts will see Form 168 and Form 26AS together, with the payment code distinguishing 1002 from 1012. For the broader cross-references see the TDS payment codes 1001–1092 reference, the Section 393 master guide and the Form 168 reconciliation guide.

GST is unchanged by the Income Tax Act 2025 — Section 17(5), Section 34, Rule 36(4), Rule 37, Rule 43 and Rule 55 still govern. Section 34 GST credit notes against accepted quality-reject debits must be raised by 30 November of next FY.

What automated reconciliation changes

A Maruti-aware reconciliation engine ingests daily e-Nagare extracts per plant, applies the four-way CUM match per scheduling-agreement line, runs JIS sequence-mismatch exception queues, generates periodic GST e-invoices against confirmed-received quantity, and decomposes debit-note registers by reason for per-plant per-programme close-out. TransactIG ships 24+ industry presets including the auto-component OEM-portal-aware preset configured for Maruti’s plant-and-programme model. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). See auto-component reconciliation software India and three-way matching software India for the broader stack.

Continue reading

• Automotive component manufacturing reconciliation in India (sub-pillar)
• Maruti Suzuki supplier settlement process
• EDI 830, 862 and 856 finance primer
• Manufacturing reconciliation in India (pillar)