Line-Stop Charges and Liquidated Damages in Indian Auto Supply: Accounting Treatment

An axle-shaft Tier-1 supplier in Chakan opens an email from Mahindra & Mahindra’s supply-chain team on a Monday morning: a 47-minute line halt on the Bolero programme on Saturday afternoon, attributed to a delayed delivery of axle shafts from the supplier’s Sangamner plant, charged at ₹38,000 per minute under the master supply agreement — ₹18 lakh on the next settlement. The supplier’s logistics team had logged a monsoon-related highway closure that diverted the dispatch truck through a longer route. Force-majeure notice was due within 7 days of the event. The 8-day mark passed on Sunday. This is the operational reality of line stop charge liquidated damages auto component India for any Tier-1 running just-in-time delivery into Indian OEM plants.

Quick reference

The line-stop charge mechanism

OEM production lines run on take-rate calculations where every minute of downtime translates to a measurable production shortfall. When a supplier’s just-in-time delivery slips — late dispatch, short kanban, or quality rejection at incoming inspection — the OEM line halts, the OEM line log captures the start and stop timestamps, and the OEM raises a line-stop charge against the supplier on the next settlement.

The charge mechanism is straightforward: contractual per-minute or per-hour rate × downtime duration × programme-specific multiplier. Premium passenger-car programmes at the Maruti Manesar plant or the Hyundai Sriperumbudur plant run line-stop rates at the upper end of the ₹1-5 lakh per hour band. High-volume two-wheeler programmes run at the lower end. Commercial-vehicle programmes vary by plant and shift.

The contractual basis is the liquidated damages clause in the master supply agreement, supported by the quality manual and the supplier code of conduct. The line-stop rate is typically encoded as a specific schedule referenced from the LD clause, with the rate locked at MSA signing and rarely renegotiated mid-cycle.

CBIC Circular 178/10/2022 and the GST position on liquidated damages

For several years before 2022, the GST treatment of liquidated damages — line-stop charges, breach-of-contract penalties, late-delivery charges, cancellation charges — was genuinely contested. One reading held that the recipient of the LD was “tolerating an act” by the counterparty and therefore supplying a service under Schedule II of the CGST Act, attracting GST at 18%. The other reading held that LDs are compensation for damage and not consideration for any supply.

CBIC Circular 178/10/2022-GST dated 3 August 2022 settled the question. The circular clarifies that:

• Amounts received as liquidated damages, compensation for breach, or penal charges are not consideration for a taxable supply.
• These payments compensate for loss, damage, or breach rather than represent consideration for any tolerated act, refraining, or other supply.
• Where there is no underlying supply being made by the recipient of the LD, no GST applies.

For the line-stop charge, the OEM is not supplying anything to the supplier in exchange for the LD — the LD compensates the OEM for production loss caused by the supplier’s contractual breach. The line-stop charge therefore falls outside the GST net. No output GST on the LD component, no Section 34 credit-note action required from the supplier on the LD component, and no ITC consequences for the OEM.

This is materially different from a quality back-charge with physical return where the supplier issues a Section 34 GST credit note to reverse output GST on the returned goods. The two often appear on the same settlement statement but get accounted differently.

Force-majeure carve-outs and the notice window

The MSA’s liquidated damages clause includes a force-majeure carve-out exempting the supplier from line-stop charges where the underlying delay or quality issue is caused by events beyond the supplier’s reasonable control. The standard carve-out covers natural disasters, strikes, governmental action, war and terrorism, and large-scale infrastructure failure. Contemporary post-2020 contracts often explicitly cover pandemic-related disruption.

The carve-out is contractually conditional on the supplier giving written force-majeure notice within a tight window — typically 7-14 days from the event. The notice must identify the qualifying event, the impact on the supplier’s ability to perform, and the expected duration. A monsoon-related highway closure that diverts a dispatch truck and causes a Saturday line halt at the Mahindra Chakan plant qualifies — but only if the supplier gives written notice by the contractual day-7 or day-14 mark.

In practice the notice window is the most-missed contractual provision in line-stop disputes. Plant logistics teams know the event happened but do not always know to file the force-majeure notice with the OEM contracts team within the window. Reconciliation teams often discover the missed notice only when the line-stop charge posts to the running account 30-45 days later.

Aggregate-liability cap and how it binds

The MSA caps aggregate liquidated damages in a contract period — typically a financial year — at 5-10% of annual contract value. Some OEMs break the cap into sub-caps: line-stop separately, quality penalties separately, total combined. Once the supplier hits the cap, no further LD can be debited for the period.

For most well-performing suppliers the cap is rarely binding. Aggregate line-stop runs 0.2-0.7% of trailing monthly billing, or roughly 0.5-2% of annual contract value. But for a supplier in distress — say a Tier-1 with a programme-launch quality issue causing repeated line halts in the first quarter of a financial year — the cap can become binding by Q2 or Q3. At that point the supplier’s contest position shifts from incident-by-incident defence to cap-enforcement against the OEM’s accumulated billing.

The reconciliation system must track cap consumption per OEM per FY in real time. A supplier with ₹240 crore Maruti Suzuki annual contract value and a 7.5% cap has ₹18 crore of LD headroom. If trailing-9-month LD billing is already at ₹14 crore, the cap binds within roughly two more incidents at average per-incident size.

Ind AS 37 provisioning treatment

Ind AS 37 (Provisions, Contingent Liabilities and Contingent Assets) governs how the supplier accounts for line-stop exposure. Three recognition conditions: present obligation, probable outflow, reliable estimation.

For line-stop charges:

• Present obligation — legal under the MSA. The line-stop event creates the obligation; the OEM’s debit note is the confirmation of the amount.
• Probable outflow — yes once the OEM has communicated the line-stop event and provisional charge estimate. Even before formal debit-note posting (which can lag 30-60 days), the supplier provisions on the OEM’s communication.
• Reliable estimation — straightforward where the OEM line log and contractual rate are both known. Where the supplier intends to contest on force-majeure or attribution grounds, the provision is held at the supplier’s best estimate of probable settlement after contest — typically the supplier-attributable portion of the downtime rather than the full OEM-claimed amount.

The provision is released on accepted force-majeure notice or contest win, and utilised on accepted debit-note posting.

Worked example — ₹18 lakh line-stop charge at Mahindra Chakan

The axle-shaft Tier-1 in Chakan, Saturday-afternoon incident on the Bolero programme:

• Event: 47-minute line halt attributable to delayed axle-shaft delivery from the supplier’s Sangamner plant
• Contractual rate: ₹38,000 per minute (₹22.8 lakh per hour equivalent) under the MSA line-stop schedule for the Bolero programme
• OEM line log: 14:23 stop, 15:10 restart, total 47 minutes
• Supplier-side root cause: dispatch truck rerouted through extended detour after Pune-Nashik highway closure due to monsoon flooding from 06:00 Saturday morning
• Initial OEM debit: ₹18 lakh (₹38,000 × 47 minutes, with rounding)

Decision sequence:

1. Day 1 (Monday) — OEM email received. Logistics team confirms monsoon highway closure event with dated state highway authority circular and dispatch tracking log.
2. Day 2 (Tuesday) — Force-majeure notice drafted and sent to OEM contracts team with documentation. Notice given on day 3 of event (within the 7-day window).
3. Day 3-30 — OEM contracts team reviews force-majeure notice and verifies independent monsoon event records.
4. Day 30-45 — OEM contracts team accepts force-majeure attribution but disputes the full 47 minutes — argues 18 minutes of the downtime is from supplier-side dispatch slippage independent of the highway closure, and 29 minutes is force-majeure-protected.
5. Settlement — partial accept. ₹6.84 lakh (18 minutes × ₹38,000) posted as confirmed line-stop charge against supplier. ₹11.16 lakh (29 minutes × ₹38,000) waived under force-majeure.

Accounting treatment:

• Initial provision raised at ₹18 lakh on Day 1 under Ind AS 37, charged to quality cost centre
• Provision revised to ₹6.84 lakh on Day 45 after force-majeure partial acceptance
• ₹11.16 lakh provision released to P&L
• No GST on either accepted or waived portion per CBIC Circular 178/10/2022
• Aggregate-liability cap consumption updated: ₹6.84 lakh added to FY count against the ₹18 crore Mahindra cap (assuming ₹240 crore Mahindra annual contract value and 7.5% cap)

Without the force-majeure notice on Day 2, the full ₹18 lakh would have been accepted as binding — the supplier’s logistics team had the event documentation but the contractual process required formal notice to the OEM contracts team within the 7-day window.

CBIC Circular reference

The Goods and Services Tax Network (GSTN) — CBIC Circulars portal hosts the full text of Circular 178/10/2022-GST dated 3 August 2022. The circular is binding guidance for both supplier and OEM accounting and is the authoritative reference for the no-GST-on-LDs position. Suppliers should retain the circular reference in their MSA reconciliation file for audit defence.

What automated reconciliation changes

Manual line-stop handling at a multi-OEM Tier-1 is a process that breaks at the force-majeure notice window — operations teams know about events but contractual notice often slips because there is no automated trigger. Aggregate-liability cap tracking is rarely real-time. Ind AS 37 provisioning lags actual events by 30-60 days. Purpose-built reconciliation software India treats each line-stop event as a structured exception keyed by OEM and vehicle programme, applies the MSA rate schedule, opens the force-majeure notice timer on event capture, runs the cap-consumption counter in real time, and routes to Ind AS 37 provision automatically. TransactIG carries 24+ industry presets including a configuration that handles the line-stop accounting cycle end-to-end with embedded CBIC Circular 178/10/2022 GST treatment, force-majeure notice calendars, and aggregate-cap dashboards. Customer outcomes include match-rate improvement from 51% to 88% on OEM settlement decomposition. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement equivalent see three-way matching software India. For the broader pillar see automotive component manufacturing reconciliation in India and manufacturing reconciliation in India. For the quality cluster sibling see auto line rejection PPM quality debit reconciliation.

Continue reading the automotive-components cluster

• OEM debit note disputes: when to accept, when to contest — decision matrix for the seven OEM debit categories
• How Indian auto component suppliers handle OEM short-pays — the finance-controller end-to-end playbook
• OEM-Tier 1 settlement and debit-note reconciliation — the seven-category OEM debit taxonomy