Hyundai Motor India Supplier Settlement: Reconciliation for Tier-1 and Tier-2 Auto Suppliers

A Tier-1 door-panel supplier in Sriperumbudur with ₹120 crore annual Hyundai Motor India billing closes the September quarter. The HMI book spans Sriperumbudur (current operating plant) with a small ramp-up volume to the new Talegaon site (the ex-GM facility HMI acquired and is bringing online for the Creta and Venue body-shop). Vaatika export shows 1,420 invoices for the quarter, 198 debit-memo lines, three settlement statements, a rolling PPM dashboard across 28 part numbers, and an RMPV register tracking aluminium-content variance on the die-cast brackets that go into the Creta front-end module. The controller is closing month-end. The question is not “is the data complete” — Vaatika gives clean structured exports. The question is whether the plant-by-plant, programme-by-programme decomposition has actually been done, whether the RMPV claim has been computed against the contracted LME formula, and whether the Mobis-routed module business has been kept separate from the HMI-direct book.

This is the operational reality of being a Hyundai Motor India Tier-1. HMI is structurally distinct from the Maruti and Tata books because it carries a Korean-parent operating discipline — tighter JIT release, Mobis-routed module supply as a parallel commercial channel, and a payment cycle that sits at the longer end of the OEM range. This guide is the Hyundai Motor India supplier reconciliation operating playbook for a Tier-1 finance team.

Quick reference

How does the HMI payment cycle actually run from GRN to bank credit?

The HMI payment clock starts at GRN — the moment the receiving plant (Sriperumbudur or Talegaon) confirms goods receipt in its system. Not invoice date. Not dispatch date. The supplier’s invoice date may match the dispatch date, but the GRN can lag by days (transit time from supplier yard to receiving dock, dock queue at Sriperumbudur during the morning rush window, weekend pauses). A dispatch on 30 September that GRN-confirms on 4 October starts the payment cycle on 4 October — at T+60 the cash lands on 3 December.

The T+60 number is the typical contracted term, with some new programmes and higher-rated suppliers running at T+45 to T+55 depending on the commercial framework negotiated at programme entry. New suppliers in the first 12 months of relationship are sometimes started at T+60 and migrate inward as supplier rating stabilises through the Vaatika quarterly scorecard. The contract baseline matters because HMI’s Korean-parent influence tends to hold longer payment cycles than the Indian-promoter OEMs (Tata, Mahindra) where the T+45 number is more common.

Settlement cadence is monthly for most programmes, with fortnightly settlement on the highest-volume Creta and Venue lines where the rupee throughput per supplier per fortnight is large enough to justify the operational overhead. The settlement statement is published on Vaatika on the settlement date with a 30-day dispute window from publication.

HMI Vaatika — the supplier portal touchpoint

Vaatika is HMI’s supplier-side delivery, quality and settlement portal. Tier-1 suppliers use it as the primary daily interaction point. The supplier login lets the finance and operations teams pull:

• Daily kanban call-off 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
• Rolling PPM dashboard per part per supplier
• RMPV settlement statements per period (where the supplier is on RMPV)
• Quarterly supplier-rating scorecard
• Payment advice download per settlement run

The reconciliation engine’s input is the settlement-statement export. The structured export from Vaatika 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 / RMPV settlement, and routes the variance lines to the reason-taxonomy classifier.

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

The kanban / JIT discipline at Sriperumbudur

Hyundai Motor India runs Sriperumbudur on a tight kanban / JIT discipline inherited from the Korean parent’s operating model. The practical reality for a Tier-1 supplier:

• Daily kanban release per part — the supplier sees a 7-14 day rolling forecast on Vaatika that converts to firm orders at the daily release boundary
• Multiple daily delivery windows at the Sriperumbudur receiving dock — a typical Tier-1 supplying high-volume parts (door panels, bumpers, seats, instrument-panel sub-assemblies) runs three to six dispatch windows per day
• No traditional MRP push — the supplier’s planning is consumption-driven from the HMI line-side stores, not from a long-horizon MRP run
• JIT shortage penalties are sharper than at OEMs with longer planning horizons — a Sriperumbudur line stop attributable to Tier-1 short-supply carries a per-hour rate plus a quality-rating downgrade trigger

The reconciliation overhead of the JIT model: more invoice lines per period (because each daily dispatch generates a separate invoice or invoice line), more debit memos per period for short-supply / late-delivery events, and a tighter requirement for ASN-GRN reconciliation because the volume of individual dispatches makes ASN-GRN errors more frequent.

Mobis-routed module supply vs direct Tier-1 supply

Hyundai Motor Group operates Mobis (Hyundai Mobis) as the in-house Tier-1 for module supply. At Sriperumbudur, Mobis India runs a near-plant facility that consolidates Indian Tier-2 supply into modules — front-end module (FEM), cockpit module (CPM), chassis module (CCM), brake module — and ships those modules to HMI on a separate commercial framework from direct Tier-1 supply.

From the perspective of an Indian Tier-2 supplier supplying into Mobis India: the customer is Mobis, not HMI. The commercial terms, debit-note format, settlement portal, payment cycle and quality regime are Mobis-specific (broadly Korean-parent-influenced) rather than HMI-direct. The supplier’s customer master must carry HMI and Mobis India as separate parent records because settlement, payment and debit-note flows run separately.

Practical reconciliation implications:

• A part supplied by the same Tier-1 to both HMI direct (a service-part SKU) and Mobis India (a module-content SKU) carries two separate scheduling agreements, two separate FOMP running accounts, and two separate settlement streams
• Mobis India’s payment cycle can differ from HMI direct — typically aligned but with the Mobis commercial entity as the obligor
• Debit-note reason coding and warranty back-charge flow runs through Mobis, with the HMI-end warranty event traced back through the Mobis-to-Tier-2 chain
• Supplier-rating quarterly scorecards run separately for HMI direct and Mobis India

For a Tier-1 with substantial Mobis India billing alongside HMI direct, treating the two as a single customer is the most common reconciliation failure mode. Programme margin gets blended, FOMP exposure gets mis-attributed, and the supplier’s negotiation posture at programme refresh becomes data-poor.

RMPV pass-through on aluminium die-cast and copper-content parts

HMI operates RMPV (raw-material price variance) pass-through on commodity-linked Tier-1 parts where the rupee-content of aluminium, copper, steel or polymer is high enough that LME or domestic benchmark variance materially affects per-part cost. The mechanism:

• The contracted scheduling-agreement rate decomposes into a fixed conversion component and a variable RMPV component
• The RMPV component is indexed to a benchmark — LME aluminium cash settlement plus a contracted premium for aluminium content, LME copper for copper content, Indian domestic HRC benchmark for steel, polymer index for ABS / PP / PA
• Monthly RMPV settlement on Vaatika picks up the variance between the contracted benchmark window and the actual benchmark, with a 30-day lag from the LME settlement date to the RMPV settlement on the portal
• The supplier’s RMPV claim is computed against the contracted formula and submitted via Vaatika; HMI’s settlement computes the RMPV from its end and the variance is the operational reconciliation focus

Worked illustration: a Tier-1 supplying aluminium die-cast brackets for the Creta front-end module at ₹120 per piece (₹85 conversion + ₹35 aluminium content at base LME of $2,400/MT). LME settles at $2,600/MT for the reference month. The contracted formula gives RMPV of ₹2.91 per piece (₹35 × (2,600-2,400)/2,400). At 80,000 pieces per month the RMPV claim is ₹2.33 lakh. The HMI Vaatika RMPV settlement comes in at ₹2.18 lakh. The ₹15,000 variance is the reconciliation item — typically a 2-3 day lag in the LME averaging window or a premium-component computation difference.

The reconciliation engine must cap RMPV claims against the contracted formula (suppliers occasionally claim against spot LME rather than the contracted window) and surface variance where the HMI RMPV settlement differs from the supplier’s computed claim.

The HMI debit-note format and reason coding

HMI’s debit notes follow a structured format broadly aligned to the seven-category reason taxonomy that ACMA has codified across Indian OEMs, with HMI-specific sub-codes:

1. FOMP / warranty back-charge — field warranty claim with 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
6. Technical service deduction — visit log reference, plant, engineer-days, hourly rate
7. Transport / premium freight debit — freight event reference, dispatch lane, premium differential

The supplier’s reconciliation engine validates each component: is the rate the contracted rate, is the claim ID valid in Vaatika, is the calculation arithmetically correct, does the warranty event fall within the contractual warranty period for that part. Industry observation: 12-18% of OEM debits across Indian OEMs fail this validation at first pass; HMI tends to run at the cleaner end given Vaatika’s relatively mature debit-note structure, with first-pass rejection rates closer to the 10-12% band.

Worked example — Tier-1 with ₹120 crore annual HMI billing

A Tier-1 supplying door panels and interior trim to HMI Sriperumbudur across i20, Creta and Venue:

Across the ₹8.76 crore annual short-pay:

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

Tier-2 passthrough on the accepted ₹5.7 crore: roughly ₹4.0 crore (70%) traces to specific Tier-2 vendors. At full recovery, ₹4.0 crore of Tier-2 back-charge revenue. Excel-driven shops leak at least 30% (₹1.2 crore annually) because the Tier-2 traceback is not systematically maintained at debit-line level.

Programme-level margin visibility — without the per-programme decomposition, the controller cannot see that Verna + Alcazar (9% short-pay) is dragging the book down while i20 (6%) is profitable. Re-negotiation conversations at programme refresh need the per-programme number, not the blended ₹8.76 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.
• 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 HMI suppliers

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

What automated reconciliation changes for an HMI Tier-1

Manual reconciliation of a four-programme, Sriperumbudur-anchored, ₹120 crore HMI book typically runs 6-10 days of controller time per month-end with material recovery leakage on Tier-2 passthrough, RMPV variance, and lapsed Section 34 windows. Purpose-built auto-component 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 HMI’s plant-coded settlement, programme-level FOMP running accounts, rolling 12-month PPM tracking, RMPV reconciliation against the LME / benchmark formula, 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:

• Maruti Suzuki supplier settlement process
• Tata Motors Tier-1 supplier reconciliation
• Mahindra supplier payment reconciliation

Up the chain:

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