Tata Motors SRM Portal Integration
Tata Motors publishes supplier-facing data through its SRM portal in a mix of PDF and CSV formats — scheduling agreements, ASN acknowledgements, GRN postings, debit notes, payment advices, and warranty back-charges. TransactIG orchestrates the extract, normalises across the four major plants (Jamshedpur, Pune, Pantnagar, Sanand), and runs cross-plant reconciliation into supplier SAP, Oracle, or Tally.
Cross-plant reconciliation
Most Tier-1 suppliers sell into more than one Tata plant. The same part, the same scheduling agreement type, and the same supplier code can carry materially different call-off rhythms, payment terms, and debit-note patterns plant by plant. Reconciling per plant is the first layer; rolling up consistently across plants is the second.
What we extract from TML SRM
| Artifact | Reconciliation purpose |
|---|---|
| Scheduling agreement / firm call-off | Anchor for the four-way CUM match per part per Tata plant. Cross-plant reconciliation across Jamshedpur, Pune, Pantnagar, and Sanand. |
| ASN dispatch confirmation | Supplier-side CUM-shipped persisted across uploads. Cross-plant duplicate dispatches surface as a single exception register. |
| GRN acknowledgement | Tata-side CUM-received reconciled to supplier-side CUM-shipped. Drift surfaces within the cycle, not at quarter end. |
| Debit-note PDF or CSV | Reason code parsed, claim ID extracted, linked to originating invoice. Routed into accept or dispute queue with Section 34 credit-note action and Rule 37 ITC-reversal ageing. |
| Payment advice | Decomposed into base invoice plus reason-coded debits. Rolling 12-month PPM per part per Tata plant computed for the quality-debit ledger. |
| Warranty back-charge | Linked from Tata claim to supplier invoice to Tier-2 sub-vendor where passthrough applies. Recovery ageing tracked end-to-end. |
PDF artifacts (debit notes, payment advices, warranty back-charge memos) are parsed by the connector. Schema and login-flow changes on the SRM side are absorbed without customer effort.
Warranty back-charge passthrough
A Tata warranty back-charge to a Tier-1 frequently originates from a Tier-2 sub-vendor component. Tracing the chain — Tata claim → Tier-1 invoice → Tier-2 sub-vendor — is the only way to recover. TransactIG links the three documents at part and batch level, ages the recovery, and surfaces the Tier-2 ageing on a separate ledger so the recovery cycle is not lost.
Pilot on one Tata plant
Share the SRM credentials and one quarter of debit notes and payment advices for one Tata plant. We will return a reason-coded decomposition and a cross-plant rollup template.
Request pilot