Tata Motors Tier-1 Supplier Reconciliation: JLR vs Domestic OEM Settlement Differences

A Tier-1 brake-and-suspension supplier in Pune with ₹240 crore annual Tata Motors billing closes the December quarter. The Tata book spans two plants: Sanand (passenger vehicles — Nexon, Punch, Tiago, Tigor, the new Curvv) and Pune (passenger vehicles — Harrier, Safari) with a small JLR India leg for an export programme that ships sub-assemblies into the Pune JLR build. TML SRM export shows 2,140 invoices for the quarter, 412 debit-memo lines, two settlement statements per plant, a quality dashboard tracking rolling PPM across 42 part numbers, and a foreign-currency invoice register for the JLR leg of roughly ₹14 crore-equivalent in GBP-denominated billing. The controller is closing month-end. The question is not “is the data complete” — TML SRM gives clean structured exports. The question is whether the plant-by-plant, programme-by-programme, business-by-business decomposition has actually been done, whether Form 168 TDS deductions reconcile against the books, and whether the JLR foreign-currency leg has been revalued correctly at quarter close.

This is the operational reality of being a Tata Motors Tier-1. Tata Motors is structurally different from the Maruti book because it spans three distinct commercial models inside a single corporate customer master — commercial vehicles, passenger vehicles, and JLR India — each with its own commercial terms. This guide is the Tata Motors Tier-1 supplier reconciliation India operating playbook.

Quick reference

How does Tata Motors organise its supplier book across commercial vehicles, passenger vehicles and JLR India?

The first reconciliation question is structural: Tata Motors is not a single commercial entity from the supplier’s point of view. Inside a Tier-1’s customer master, Tata Motors typically sits as a parent record with three child sub-organisations:

• Commercial vehicles — Jamshedpur (heavy commercial vehicle heritage plant), Lucknow (medium and heavy commercial vehicles), Pantnagar (small commercial vehicles — Ace family). Programmes include Prima, Signa, Ultra, LPK / LPT heavy ranges, Ace, Ace Gold, Intra, Magic, Yodha.
• Passenger vehicles — Sanand (Nexon, Punch, Tiago, Tigor, Altroz, Nexon EV, Curvy, Avinya) and Pune (Harrier, Safari, and historically the Hexa / Bolt programmes). Each programme has its own scheduling agreement, FOMP running account and tooling cap.
• JLR India — Pune-housed JLR assembly with India-localised sub-assembly sourcing. Some Tier-1s supply directly to JLR India for India-market vehicles; others supply sub-assemblies that get exported to JLR’s UK / Slovakia plants on inter-company commercial terms.

Each sub-organisation runs its own GRN, settlement statement, debit-memo register and supplier-rating cycle. The supplier’s reconciliation engine must key every transaction to the correct sub-organisation, because a Sanand-built Nexon FOMP claim cannot be netted against a Pune-built Harrier FOMP claim — they belong to different programme running accounts even though both sit under “Tata Motors Passenger Vehicles”.

TML SRM — Tata’s supplier portal touchpoint

TML SRM is Tata Motors’ supplier relationship management portal. 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 Tata, deposited against supplier PAN)
• For JLR-linked suppliers — foreign-currency invoice register with INR equivalent at booking-date FX

The reconciliation engine’s primary inputs are the structured settlement-statement and debit-memo exports per period per sub-organisation. The portal screens themselves are operational machinery — reconciliation runs against the structured exports, not against scraped page state.

The JLR vs domestic OEM commercial difference

The JLR India leg is the structural difference that makes Tata Motors materially harder to reconcile than a pure-domestic OEM like Maruti or Mahindra. Three differences matter:

Currency. Export-bound parts on the JLR leg are typically invoiced in GBP (for UK-bound parts) or USD (for select programmes). The supplier raises an INR-equivalent invoice in books at booking-date FX, then revalues outstanding receivables at month-end and at settlement. Each settlement carries an FX-gain or FX-loss adjustment that does not exist on the commercial-vehicle or passenger-vehicle legs.

Commercial framework. JLR’s global premium-tier supplier framework brings tighter quality KPIs, longer warranty windows, more granular launch-cost recovery clauses, and a different escalation taxonomy. The debit-memo format on the JLR leg follows JLR’s global template, not Tata’s domestic template.

Tax overlay. Pure-export sub-assembly billing carries GST at zero-rate (with LUT or IGST refund) and brings IGST refund-claim mechanics that the domestic legs do not. Any associated technical-service fees paid to JLR-side non-resident engineers (for programme launch, fixture commissioning, quality investigation) attract Section 413 / payment code 1062 TDS on the supplier’s pay-leg — a code that has no equivalent on a pure-domestic OEM book.

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

The Tata payment clock starts at GRN — the moment the receiving plant confirms goods receipt in TML SRM. Not invoice date. Not dispatch date. A dispatch on 28 November that GRN-confirms on 5 December starts the cycle on 5 December — at T+60 the cash lands on 3 February.

The T+45 to T+60 band varies by programme, supplier rating and business. Higher-rated suppliers on critical passenger-vehicle programmes (Nexon, Harrier, Safari) typically sit at T+45. Commercial-vehicle suppliers on legacy programmes (Ace, Magic) typically sit at T+60. JLR-leg suppliers operate on the JLR global commercial framework — typically T+45 from goods-acceptance with strict adherence.

Settlement cadence is fortnightly for high-volume programmes (Nexon, Punch, Ace, Prima) and monthly for low-volume programmes (Avinya, Curvy at ramp, premium commercial-vehicle programmes). The settlement statement publishes on TML SRM on settlement date with a defined dispute window from publication — disputes raised after the window are deferred to the next settlement.

Tata’s debit-note reason taxonomy

Tata’s debit notes follow a structured format that broadly aligns to the ACMA-codified Indian OEM taxonomy but with Tata-specific reason codes:

1. FOMP — field warranty back-charge with claim ID, vehicle registration range, dealer reference, programme reference
2. Quality penalty — line rejection (rejection slip ID + plant), PPM excess (rolling 12-month PPM and threshold breach), audit non-conformance from supplier-site audit
3. JIT shortage — shortage event ID, called-off quantity, dispatched quantity, expediting premium where applicable
4. Line-stop charge — line-stop event ID, plant, programme, hours stopped, hourly rate applied
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

Each debit memo cites the contractual per-unit rate, the calculation and the underlying claim ID. The supplier’s reconciliation engine validates each component against the scheduling-agreement rate, the claim ID in TML SRM, the arithmetic and the contractual warranty period for that part.

Form 168 TDS reconciliation under Section 393(1)(a) code 1002

Tata Motors deducts contractor TDS on the supplier’s job-work component under Section 393(1)(a) of the Income Tax Act 2025 effective from 1 April 2026, using payment code 1002. The rate is 1% for individual / HUF suppliers and 2% for other entities. The deduction applies on the job-work / conversion component of the invoice, not on the pure-material passthrough where the contract structurally separates the two.

Form 168 is the periodic TDS certificate / statement the supplier downloads from TML SRM (and reconciles against the income-tax department’s reflected position against PAN). The reconciliation engine reads each Form 168 line, ties it to the underlying Tata invoice or scheduling-agreement reference, validates the deducted amount against the contracted job-work component, and flags variances. Common variance patterns: deduction applied on full invoice (including material passthrough) instead of job-work component only; rate applied at 2% on individual / HUF supplier where 1% applies; deduction missing on a covered invoice; deduction reflected against wrong PAN.

Variances must be escalated to the Tata Vendor Finance team before the quarterly TDS return cut-off, because a once-filed return is much harder to correct than a pre-filing adjustment.

Cross-era reconciliation continues for dispositions started before 1 April 2026 under legacy Section 194C — see Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India for the full code map.

Worked example — Tier-1 with ₹240 crore annual Tata Motors billing

A brake-and-suspension Tier-1 supplying two Tata plants (Sanand passenger vehicles, Pune passenger vehicles plus a small JLR India sub-assembly leg):

Across the ₹17.12 crore annual short-pay:

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

Form 168 TDS reconciliation on the ₹240 crore book: applying Section 393(1)(a) code 1002 at 2% on roughly 30% job-work component (₹72 crore of conversion across the book) yields expected annual TDS of about ₹1.44 crore. A ±5% variance band between books-TDS-receivable and Form-168-TDS-deducted is normal; anything outside flags a reconciliation issue worth investigating.

FX revaluation on the ₹14 crore JLR leg at quarter-end: outstanding GBP-denominated receivables of roughly ₹3.5 crore at quarter-close, with a 2% adverse FX move yielding a ₹7 lakh FX loss recognised in books — small in absolute terms but structurally distinct from the domestic legs and requiring its own ledger discipline.

Tax overlay — Section 393, 394 and 413 across the Tata book

The Tata 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 Tata 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.
• Section 413 code 1062 — Non-resident pay-leg TDS on associated technical-service fees paid to JLR-side non-resident engineers for programme launch or quality investigation, where applicable.

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

ACMA reference for Tata suppliers

The Automotive Component Manufacturers Association of India (ACMA) is the canonical industry reference for Tata Tier-1 commercial frameworks. ACMA’s Supplier Excellence Programme materials, OTIF score methodologies and back-charge taxonomies map closely to Tata Motors Supplier Quality Excellence outputs across commercial-vehicle, passenger-vehicle and JLR India programmes. Most Tata Tier-1 ERP configurations use ACMA’s standardised reason codes as the master vendor-master debit-reason taxonomy, then overlay Tata-specific extensions.

What automated reconciliation changes for a Tata Tier-1

Manual reconciliation of a two-plant, three-business, ₹240 crore Tata book typically runs 10-14 days of controller time per month-end with material recovery leakage on the contested debit lines and Form 168 TDS mismatches, plus an unmanaged FX exposure on the JLR leg. Purpose-built auto-component reconciliation software India treats each debit reason code as a structured variance stream, decomposes settlement at the plant-and-programme level, runs Form 168 TDS reconciliation against books, and revalues the JLR foreign-currency sub-ledger at close. TransactIG carries 24+ industry presets including an auto-component configuration that handles plant-coded settlement, programme-level FOMP running accounts, Section 34 GST credit-note timing, Rule 37 ageing, Section 393(1)(a) code 1002 deductions and Section 413 code 1062 considerations. 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