Tata Motors Supplier Portal (TML SRM): Delivery Data Extraction for Finance Teams

A Tier-1 forging supplier in Jamshedpur with a ₹220-crore annual Tata Motors book runs the September quarter close. Three Tata plants served: Jamshedpur (medium and heavy commercial vehicle programmes), Pune Chinchwad (Harrier, Safari and Curvv), and Sanand (Nexon, Punch, Tiago, Tigor). One commercial team, one scheduling agreement umbrella, but three separate TML SRM logins per plant, three separate settlement statements, three separate debit-note registers. The September close throws up a ₹38-lakh discrepancy between the consolidated Tata-customer ledger and the bank receipts. The cleanup takes nine days because the finance team rolls up to “Tata customer” first and tries to decompose afterwards — the right order is the opposite. This is the Tata Motors supplier portal TML SRM delivery reconciliation discipline a Tier-1 finance team needs to internalise: reconcile per plant first, aggregate at customer level only after each plant is closed.

Quick reference

TML SRM in the Tata supplier ecosystem

Tata Motors operates TML SRM as the digital supplier touchpoint that supplements the underlying EDI/IDoc transport. The portal is the visible surface; the IDoc archive (DELFOR for forecasts, DELJIT for firm call-offs, DESADV outbound for ASNs, MBGMCR inbound for GRN confirms) is the canonical record for SAP-integrated supplier estates. For Tier-2 and Tier-3 supplier estates without SAP-to-SAP integration, the portal is the only transport — those suppliers download CSV/PDF/XLS extracts on a scheduled cadence and feed them into their reconciliation engine.

The portal’s finance-relevant surfaces:

• Scheduling agreement view. Per part per Tata plant. Carries pricing, delivery tolerance, reset marker (typically 1 April), tooling cap and recovery rate, PPM thresholds. The contract anchor.
• Call-off schedules. Daily firm window plus weekly forecast horizon. The firm quantity drives authorised dispatch; the forecast feeds capacity planning.
• ASN upload and acknowledgement. Supplier-side dispatch notification, with pack structure (SNP, bin count, vehicle number). Tata’s plant inbound logistics matches the ASN to physical receipt.
• GRN confirmation per plant. Goods receipt at the receiving Tata plant. The Ind AS 115 control-transfer event.
• Debit note register. Quality-reject debits, line-stop FOMP, PPM penalty, tooling clawback, freight and premium freight. Each debit carries a reason code from Tata’s Supplier Quality Manual taxonomy.
• Payment advice. Periodic remittance statement showing gross invoice value, debits applied, Section 393(1)(k) TDS deducted, and net bank remittance.
• Quality dashboard. Rolling 12-month PPM per part against contractual threshold. Breach triggers contractual penalty plus 8D corrective-action requirement.

For the Tata commercial-term mechanics, see the Tata Motors Tier-1 supplier reconciliation deep dive.

The extraction workflow — PDF, CSV and IDoc transport-neutral

Most Tier-1 finance teams run a hybrid extraction discipline:

• IDoc transport (where SAP-to-SAP integration exists) — DELJIT, DESADV, MBGMCR flow automatically. The supplier’s SAP receives DELJIT (firm call-off) and posts it to the scheduling agreement. The supplier’s SAP transmits DESADV outbound on dispatch. Tata’s SAP transmits MBGMCR back on GRN posting. The IDoc archive is the canonical audit record.
• Portal export (for debit notes, payment advices, and quality dashboard — which are portal-only data) — finance team logs into TML SRM per plant, downloads weekly or fortnightly CSV/PDF extracts.

The reconciliation engine should treat both transports as transport-neutral inputs landing in the same data model. Per-part, per-plant, per-scheduling-agreement keyed records. A common error is to keep the IDoc-fed data in SAP and the portal-export data in a finance team spreadsheet — the two never reconcile because they sit in different systems.

There is no public finance API for TML SRM at the time of writing; PDF/CSV/XLS extracts via the portal UI are the only finance-facing transport for portal-only data (debit notes, payment advices). Where Tata has tested supplier-portal API exposure, it has been operational-side (ASN upload, GRN polling) rather than finance-side.

The four-plant complication — why per-plant reconciliation comes first

Tata Motors operates a four-plant manufacturing footprint where each plant carries distinct commercial behaviour:

A Tier-1 supplying brake systems across three of these plants runs three separate ASN streams, three separate GRN flows, three separate debit-note cycles and three separate payment advices. Aggregating to “Tata customer” before plant-level closure is operationally wrong:

• Debit-note reason taxonomy differs per plant (quality-related debit at Pune PV is a different category from a line-stop FOMP at Jamshedpur CV).
• Settlement cadence differs per plant.
• Programme-attributable FOMP register sits at the plant level.
• PPM threshold bands and breach triggers are plant-and-part specific.

The discipline: reconcile per plant first. Roll up only after each plant is closed. The roll-up view is for management reporting; the operational reconciliation lives at the plant level.

The canonical reconciliation chain — TML SRM extract to bank receipt

For each Tata plant per month, the reconciliation chain runs:

1. Scheduling agreement view extract. Pull current SA configuration: parts, pricing, tolerance, reset, programme attribution.
2. Firm call-off extract. DELJIT IDoc archive or portal call-off CSV. Reconcile to scheduling-agreement-line-level CUM-required.
3. ASN log. Outbound DESADV or portal ASN upload log. Reconcile CUM-shipped to CUM-required with delivery-tolerance applied. See the CUM quantity drift article for the rolling CUM mechanic.
4. GRN confirmation. Inbound MBGMCR or portal GRN view. Reconcile CUM-received to CUM-shipped. Open the delivery-tolerance band exceptions queue.
5. Periodic GST e-invoice generation. Bill confirmed-received quantity for the billing window. IRN obtained from IRP. E-way bills linked to ASNs.
6. Debit-note decomposition. Portal debit-note register extract. Decompose by reason: quality reject (Section 34 credit-note candidate), line-stop FOMP, PPM penalty, tooling clawback, freight, premium freight. Queue Section 34 credit notes against accepted quality-reject debits.
7. Payment advice reconciliation. Portal payment-advice extract. Match gross invoice to debits applied to Section 393(1)(k) TDS deducted to net bank remittance.
8. Bank receipt match. Net remittance from payment advice reconciled to actual bank credit.
9. Section 393(1)(k) TDS receivable update. TDS deducted per payment advice posted to TDS receivable; reconcile to Form 26AS at quarter-end.

For SAP-to-SAP integrated supplier estates, steps 2–4 are IDoc-driven. For portal-only estates, steps 2–4 are CSV/PDF-extract driven. Steps 6–7 are portal-only across both estate types.

Worked example — Tier-1 supplying to three Tata plants

A Tier-1 brake-system supplier in Jamshedpur services three Tata plants. Annual programme value ₹220 crore: Jamshedpur (CV) ₹95 crore, Pune Chinchwad (PV) ₹70 crore, Sanand (PV) ₹55 crore. Single scheduling-agreement umbrella but three separate plant call-off streams.

September monthly reconciliation workflow:

Jamshedpur (₹7.9 crore monthly billing):

• DELJIT IDocs landed for 240 daily firm releases across 18 part numbers.
• Outbound DESADV ASNs: 612 dispatches, total CUM-shipped 184,000 units across the SA reset window.
• MBGMCR GRN confirms: CUM-received 183,400 (600-unit short due to in-transit rejection). Inside tolerance band.
• Periodic GST e-invoices (4 weekly): ₹7.92 crore billed against confirmed-received.
• Debit notes from TML SRM Jamshedpur: 42 lines totalling ₹68 lakh. Decomposition: quality reject ₹22 lakh (Section 34 candidate), line-stop FOMP ₹18 lakh, PPM penalty ₹4 lakh, tooling clawback ₹14 lakh, freight ₹10 lakh.
• Payment advice: ₹7.92 crore gross − ₹68 lakh debits − ₹17.5 lakh Section 393(1)(k) TDS at 2% on conversion portion (₹8.75 crore conversion estimate) − ₹5 lakh other deductions = ₹7.01 crore net. Bank receipt matched.
• Form 26AS Q2 reconciliation: TDS deducted ₹17.5 lakh tied to TDS receivable register.

Pune Chinchwad (₹5.8 crore monthly billing):

• Fortnightly settlement cadence: two payment advices in September.
• Tighter PPM band; September breach on one part (Curvv programme) triggered ₹3 lakh contractual penalty plus 8D corrective action.
• Section 34 GST credit notes raised against ₹8 lakh accepted quality-reject debits — calendar tracked against 30 November of next FY cutoff.

Sanand (₹4.6 crore monthly billing):

• Fortnightly settlement cadence.
• Nexon EV programme attributable FOMP separated from Nexon ICE in FOMP register.
• Higher dispatch volume due to high-volume Punch and Tiago programmes; CUM drift exception cleared via joint reconciliation with Sanand inbound team.

Cross-plant roll-up (only after each plant closes):

• Tata customer-level monthly billing: ₹18.3 crore.
• Tata customer-level TDS receivable accrual: ₹40.2 lakh.
• Tata customer-level Section 34 credit-note open queue: ₹38 lakh, all calendared.
• Tata customer-level FOMP open exposure: ₹62 lakh across three plants.

For the OEM-wide context, see the Tata Motors Tier-1 supplier reconciliation guide, the automotive component manufacturing reconciliation sub-pillar and the manufacturing reconciliation pillar. For SRM and OEM-portal standardisation across the Indian Tier-1 base, see the Automotive Component Manufacturers Association of India (ACMA).

Tax overlay — Section 393(1)(k), debit decomposition and Form 26AS

Under the Income Tax Act 2025, Tata Motors deducts TDS at Section 393(1)(k) — 2%, payment code 1012 on the conversion-charge portion of the periodic invoice. Where the supply is structured as job-work, Section 393(1)(a) — payment code 1002 applies on the labour portion. The legacy Section 194C reference survives only for transitional Form 168, Form 131 and Form 141 reconciliations. For broader cross-references see the TDS payment codes 1001–1092 reference and the Section 393 master guide.

The TDS deduction base is on conversion portion net of accepted Section 34 credit notes — meaning quality-reject debits that have been credit-noted reduce the TDS base, while line-stop FOMP and PPM penalty debits do not (those are commercial deductions, not supply-quantity reductions). Form 26AS reconciliation depends on getting the decomposition right at the time of payment advice processing — back-fixing at quarter-end is expensive.

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 credit notes against accepted quality-reject debits must be raised within the 30 November of next FY cutoff.

What automated reconciliation changes

A Tata-aware reconciliation engine ingests both IDoc transport (DELJIT, DESADV, MBGMCR) and TML SRM CSV/PDF extracts (debit notes, payment advices) into one transport-neutral data model, keyed per plant per scheduling agreement. Plant-level reconciliation runs first; cross-plant roll-up runs after. TransactIG ships 24+ industry presets including the auto-component OEM-portal-aware preset. 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)
• Tata Motors Tier-1 supplier reconciliation
• EDI 830, 862 and 856 finance primer
• Manufacturing reconciliation in India (pillar)