Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Auto-component Tier 1 suppliers run parallel revenue streams — long-running scheduling agreements with daily kanban call-offs, discrete POs for aftermarket and spares, OEM-paid tooling bundled with part contracts, RMPV escalation claims as variable consideration, and FOMP / warranty back-charges as variable consideration reductions. Ind AS 115's five-step model has to be applied consistently across all four streams, with variable-consideration constraint at every period-end and tooling capitalisation tested against the bundled-vs-distinct criteria. A typical ₹240 crore Tier 1 booking a single quarter-end has to apply the model across 8 to 12 OEM customers, 30 to 50 active SAs, 8 to 20 tooling-amortisation lines, and a rolling FOMP provision — none of which a generic ERP revenue module handles together.
Apply Ind AS 115 step-by-step. Identify each scheduling agreement plus discrete PO as a contract. Identify performance obligations — part deliveries at GRN as point-in-time, tooling as bundled-or-distinct based on programme-life commitment, engineering services where contractually separable. Determine transaction price including RMPV escalation estimate (constrained per paragraph 56) and net of FOMP back-charge provision (paragraph 51). Allocate price across performance obligations on standalone-selling-price basis where multiple POs exist. Recognise revenue at point-in-time GRN for parts, over the production schedule for bundled tooling, at ownership transfer for distinct tooling.
Customer master with OEM contract type flag (SA / discrete PO), performance-obligation register per contract with timing rule (point-in-time GRN / over-time / programme-end), tooling lineage table tagged bundled-or-distinct with amortisation schedule, variable-consideration estimator with method flag (expected-value or most-likely-amount), constraint rule library mapped to OEM and claim type, FOMP provision rate per OEM customer historical baseline, GRN-event capture from OEM portals and dispatch system.
A daily revenue recognition register per contract showing GRN-driven point-in-time bookings for parts, monthly amortisation lines for bundled tooling, period-end variable-consideration adjustment journals for RMPV (additive) and FOMP (deductive), an audit-defensible trail per contract linking the five-step application to the booked revenue, and a quarterly disclosure pack for the Ind AS 115 contract-balance reconciliation note.
A finance controller at a ₹240 crore body-pressing Tier 1 supplying Tata Motors closes the June quarter and pulls the revenue working: ₹62 crore of parts dispatched against 14 active scheduling agreements, ₹4.8 crore of OEM-paid tooling sitting partially amortised against four vehicle programmes, ₹1.9 crore of pending RMPV claims linked to JPC-steel index movement, and a ₹1.4 crore historical FOMP run-rate to provide against the quarter’s delivered units. None of this is one revenue number. Ind AS 115 forces every stream into the same five-step framework — and the operational challenge for any revenue recognition auto component Ind AS 115 India team is applying the framework consistently across 30 to 50 simultaneous contracts without losing the audit-defensible trail.
This guide walks the five-step model as applied to an Indian auto-component Tier 1. The legacy Ind AS 11 / Ind AS 18 split between construction-type contracts and goods sale dissolved on 1 April 2018 when Ind AS 115 became mandatory for all listed and large unlisted entities. The standard now governs every rupee of revenue, with no exception for serial-production manufacturing.
Quick reference
| Item | Standard | Regulator | Code / Threshold |
|---|---|---|---|
| Revenue standard | Ind AS 115 (Revenue from Contracts with Customers) | MCA / ICAI | Effective 1 April 2018 |
| Underlying global standard | IFRS 15 | IASB | Aligned text |
| Performance obligation timing | Para 35 (over-time) or Para 38 (point-in-time) | ICAI | Default point-in-time for parts |
| Variable consideration | Para 50 to 58 | ICAI | Estimate plus constraint |
| Constraint test | Highly probable no significant reversal | ICAI | Para 56 |
| Modification accounting | Para 18 to 21 | ICAI | Prospective or catch-up |
| Tax overlay TDS | Section 393(1)(a) code 1002 on job-work paid out | CBDT | 1% individual, 2% firm |
| Tax overlay TCS | Section 394 code 1071 on scrap sales | CBDT | 1% from 1 April 2026 |
The Ind AS 115 five-step model applied to auto-component contracts
Step 1 — Identify the contract
A scheduling agreement (SA) issued by an OEM is the contract for serial-production parts. A typical SA runs for the vehicle programme life — 5 to 7 years — and binds the supplier to deliver per a rolling call-off schedule with daily or weekly windows. The SA itself is the master document; individual call-offs are not separate contracts but execution releases under the SA.
A discrete PO for aftermarket parts, spares, or prototype runs is a separate contract. Tooling agreements are sometimes contained within the SA (with a tooling annexure) and sometimes issued as standalone POs. The classification matters for step 2 — bundled tooling sits inside the SA as a performance obligation; standalone tooling is its own contract.
Step 2 — Identify performance obligations
Under paragraph 22, a promised good or service is a performance obligation only if it is distinct — capable of being distinct on its own (22a) and distinct in the context of the contract (22b). For an SA with bundled tooling, the tooling fails 22b: the tooling exists only to produce the parts under the SA, has no alternative use, and the supplier cannot transfer it to other customers without OEM consent. The tooling and the parts are therefore a single bundled performance obligation, recognised over the production schedule.
For a standalone tooling PO where the OEM contractually transfers ownership and the tool can be used for other OEM programmes (rare but possible for generic press dies), the tooling is a distinct performance obligation recognised at the point of ownership transfer.
Engineering services — design, validation, PPAP — are sometimes contractually separable. If priced separately with stand-alone selling prices and capable of being satisfied independently, they are distinct performance obligations.
Step 3 — Determine the transaction price
The transaction price has three layers for an auto-component Tier 1:
Fixed consideration: the SA-base price per part, the tooling cost, the engineering service fee.
Variable consideration (additive): RMPV escalation claims indexed to JPC steel, LME aluminium, LME copper, or a contract-specific basket. Under paragraph 50 the supplier must estimate the expected RMPV recovery at every period-end. Under paragraph 56 the estimate is constrained — included only to the extent highly probable that no significant reversal will occur.
Variable consideration (deductive): FOMP back-charges, quality debit notes, line-stop charges. Under paragraph 51 these are estimated forward and revenue is reduced accordingly. A historical 2% FOMP run-rate translates to a 2% revenue haircut at recognition with quarter-end true-ups.
For a JPC-steel-indexed RMPV with monthly settlement and OEM-acknowledged formula, the estimate is typically included at full value because the index movement is objective. For an OEM-discretionary productivity claim subject to a committee review, the estimate is constrained to zero or a low percentage until acknowledgement.
Step 4 — Allocate the transaction price
If the contract has one performance obligation (bundled SA plus tooling), allocation is irrelevant — the entire price sits against the one obligation and is recognised over the production schedule. If the contract has multiple obligations (parts plus distinct tooling plus distinct engineering services), allocation is on stand-alone-selling-price basis, using observable prices where available and estimated prices (cost-plus or residual approach) where not.
Step 5 — Recognise revenue
For an SA serial-production part, control transfers when the OEM accepts the part at GRN. Each GRN is a discrete recognition event keyed to the delivery slip, the GRN reference, the part number, and the SA call-off line. The supplier’s revenue recognition system has to ingest the daily GRN feed from the OEM portal and the daily kanban dispatch log to book revenue at the right moment for the right quantity.
For bundled tooling, the tooling cost is amortised across the SA production schedule. A ₹40 lakh tooling for an expected programme volume of 80,000 parts amortises at ₹50 per part, booked alongside the part revenue on every GRN.
For period-end variable consideration, an estimate journal is passed at the quarter close — RMPV estimate added to revenue (constrained), FOMP provision deducted from revenue. True-ups at the next quarter close adjust against actuals received.
How is RMPV variable consideration constrained in practice?
Paragraph 56 requires the variable consideration estimate to be included only to the extent highly probable that no significant reversal will occur when the uncertainty resolves. In auto-component practice this translates to a tiered policy:
| RMPV claim type | Constraint logic | Typical inclusion % |
|---|---|---|
| Index-formula RMPV with OEM-acknowledged monthly settlement | High confidence — objective index, formulaic | 100% |
| Index-formula RMPV with quarterly OEM committee approval | Medium confidence — settlement risk | 60% to 80% |
| Productivity claim with OEM-discretionary committee | Low confidence — no objective formula | 0% to 30% |
| Retrospective RMPV claim filed but not acknowledged | Very low confidence | 0% |
The constraint is documented per claim in the variable-consideration tracker so the statutory auditor can re-perform the judgement.
How is FOMP back-charge variable consideration recorded?
Under paragraph 51 the FOMP exposure is forward-estimated at recognition. The standard practice is a percentage-of-revenue provision tuned to historical FOMP rates. A Tier 1 with a three-year average FOMP run-rate of 2.1% would book a 2.1% revenue reduction at the time of GRN-based recognition.
At quarter-end the controller reconciles: actual FOMP debit notes received during the quarter, FOMP debit notes acknowledged but not yet received, pending warranty claim ageing from the OEM portal, and any specific high-value claim notices. The true-up journal adjusts the provision up or down. The audit trail per OEM customer shows opening provision, additions, releases, and closing provision with reconciliation to actual debit notes.
Three-Way Match Exception Cost Calculator
Quantify the revenue leakage from unresolved three-way-match exceptions across SA call-offs, GRN events, and OEM payments — the data feed for the Ind AS 115 variable consideration true-up.
Open the Three-Way Match Exception Cost Calculator →Worked example: a Tata Motors body-pressing Tier 1
A ₹240 crore Tier 1 supplies body-pressing parts to Tata Motors under four scheduling agreements (one per vehicle programme). The June quarter shows the following:
| Metric | Quarter |
|---|---|
| GRN-booked dispatch quantity (parts) | 1,68,000 |
| SA-base part revenue | ₹62.4 crore |
| OEM-paid tooling outstanding (4 programmes) | ₹4.8 crore at quarter-open |
| Tooling amortisation booked in quarter | ₹78 lakh (across the four programmes) |
| RMPV claim filed against JPC-steel May index movement | ₹1.9 crore |
| RMPV claim filed against productivity committee review | ₹0.6 crore |
| Historical FOMP run-rate (three-year average) | 2.1% of recognised revenue |
| FOMP debit notes actually received in quarter | ₹1.32 crore |
| FOMP provision at quarter-open | ₹4.92 crore |
The Ind AS 115 journal at quarter-end works as follows:
Part revenue (Step 5, point-in-time): ₹62.4 crore booked across 1,68,000 GRN events at SA-base price. This includes the ₹78 lakh tooling amortisation as a bundled performance obligation revenue line.
RMPV variable consideration (Step 3, additive): the ₹1.9 crore index-formula RMPV is included at 100% per the constraint policy (acknowledged monthly settlement, objective index). The ₹0.6 crore discretionary productivity claim is included at 25% — ₹15 lakh — pending committee acknowledgement. Total RMPV addition to revenue: ₹2.05 crore.
FOMP variable consideration (Step 3, deductive): the 2.1% historical run-rate applied to ₹62.4 crore yields a ₹1.31 crore current-quarter provision addition. The opening provision of ₹4.92 crore plus ₹1.31 crore addition minus ₹1.32 crore actuals received yields a closing FOMP provision of ₹4.91 crore.
Net recognised revenue for the quarter: ₹62.4 + ₹2.05 − ₹1.31 = ₹63.14 crore.
The audit trail per OEM customer shows the GRN feed by part number and call-off line, the tooling amortisation schedule per programme, the RMPV tracker with constraint reasoning per claim, and the FOMP provision movement with reconciliation to actual debit notes received from the Tata Motors portal.
Tax overlay
Revenue recognition under Ind AS 115 governs the financial statements. The tax overlay runs on the same revenue stream but with discrete provisions.
Section 393(1)(a) code 1002: the Tier 1 paying job-work charges to a heat-treatment, plating, or sub-assembly vendor deducts TDS at 1% for individual/HUF vendors and 2% for company/firm vendors. The deduction is at invoice or payment, whichever is earlier, with monthly deposit by the 7th of the following month and quarterly Form 26Q filing.
Section 394 code 1071: scrap sale TCS at 1% on the gross value before GST applies from 1 April 2026 — relevant because every press operation generates skeleton scrap as a separate revenue stream that must be split out from part revenue.
Section 413 code 1062: payments to non-resident parties — relevant for any OEM with overseas tooling vendors or engineering service providers.
The CBDT publishes the official codes and the cross-era reconciliation rules on the income tax portal. The ICAI Ind AS 115 educational material covers the financial reporting layer.