Maruti e-Nagare Integration for Auto-Component Suppliers
Maruti Suzuki transmits daily firm call-offs, weekly rolling forecasts, JIS sequence files, GRN acknowledgements, and payment advices through the e-Nagare supplier portal. TransactIG ingests, normalises, and reconciles every artifact against supplier SAP, Oracle, or Tally. Stateful CUM accounting per Maruti plant (Manesar, Gurgaon, Kharkhoda) and reason-coded debit decomposition closes the settlement loop.
The e-Nagare data model
e-Nagare is Maruti's supplier-facing portal for delivery scheduling, dispatch acknowledgement, GRN visibility, and payment-advice publication. Suppliers receive daily firm call-offs against an active scheduling agreement, with a weekly rolling forecast published separately for capacity planning. For sequenced parts on the assembly line, JIS sequence files publish multiple times per day. The portal also publishes the GRN acknowledgement once Maruti's plant has received and accepted the dispatch.
Payment advices arrive per Maruti payment run with base invoice amounts net of auto-debits. Most Indian Tier-1s see eight to twelve percent of monthly Maruti billing short-paid through reason-coded debits — FOMP (forced outage of Maruti production), JIT shortage, quality penalty, line-stop, tooling adjustment, transport recovery. Tying each debit back to the originating invoice with a Section 34 credit-note action is the daily settlement workload.
What we extract and reconcile
| e-Nagare artifact | Cadence | Reconciliation purpose |
|---|---|---|
| Daily firm call-off | Daily (next-day requirement) | Becomes CUM-required for the four-way match per part per Maruti plant (Manesar, Gurgaon, Kharkhoda). |
| Weekly rolling forecast | Weekly | Tracked separately for capacity planning. Excluded from invoiceable CUM until firmed in a subsequent call-off. |
| JIS / sequence files | Multiple times per day for sequenced parts | Sequence-position-aware variance — a missed sequence is a line-stop risk, not just a delivery shortfall, and surfaces on the FOMP debit register. |
| GRN acknowledgement | Daily | OEM-side CUM-received reconciled to supplier-side CUM-shipped. Drift surfaces as a standing exception within 24 hours. |
| Payment advice | Per Maruti payment run | Decomposed into base invoice plus reason-coded debits (FOMP, JIT shortage, quality penalty, tooling, transport). Each debit linked to originating invoice with Section 34 credit-note action queue. |
| Debit-note PDF / file | On debit issue | Reason code parsed, claim ID extracted, linked to rejection slip or shortage report where available; routed into dispute or accept queue with ageing. |
Portal access uses supplier-issued credentials. Schema and login-flow changes on the Maruti side are absorbed in the connector layer.
Payment-advice match
Every Maruti payment advice is decomposed into base invoice plus reason-coded debit memos. The decomposition uses the FOMP / JIT shortage / quality penalty / line-stop / tooling / transport taxonomy that Maruti publishes on the advice itself. Each debit memo is linked back to the originating supplier invoice via claim ID, rejection slip number, or debit-note reference, then routed to either the accept queue (Section 34 credit note issued within the GST window, Rule 37 ITC reversal aged) or the dispute queue (evidence attached, ageing tracked, recovery target set).
The output writes back to supplier SAP, Oracle Fusion, or Tally as journal references and exception-queue entries. No customer-side code change required.
Pilot on one Maruti plant
Share the e-Nagare credentials and one quarter of payment advices for one Maruti plant. We will return a reason-coded debit decomposition and a CUM-drift register.
Request pilot