Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Auto OEMs withhold a fixed percentage — typically 5%, sometimes up to 10% — of every supplier invoice as retention money against warranty failures. When a naive reconciliation system sees the shortfall against the invoice amount, it flags the entry as a short-payment or dispute, generating false dunning, incorrect ageing reports, and downstream errors in Section 43B(h) interest calculations.
For each OEM remittance, parse the debit advice reason code. Where the reason maps to retention, security deposit, or warranty hold, classify the shortfall as a retention receivable — not a short-payment, rejection, or price adjustment. Post an entry to the retention register with the invoice reference, retention percentage, retention amount, and contractual release date derived from the master contract.
Retention percentage per OEM (5% default, 10% for certain safety-critical parts), warranty period in days (90/120/180 depending on part class), remittance advice reason code mapping (retention/security/warranty hold), release-date calculation rule (invoice date or delivery date plus warranty period), MSME status flag per supplier to distinguish 43B(h) clock start.
Retention register with open retention receivables by OEM, expected release dates, and 43B(h) status. Reconciliation report shows retention debits classified separately from short-payments, rejection debits, and rebate debits. Ageing report treats retention as a distinct bucket with its own contractual due date rather than an overdue payable.
For every ₹100 of goods a Tier-1 auto supplier invoices to an Indian OEM, roughly ₹95 lands in the bank on due date. The remaining ₹5 is retention — held back as security against warranty failure and released only after the parts have run for a contractual defect-free period. This is not a payment dispute, not a rejection, and not a rebate. It is a working-capital deferral that must be booked as a receivable, tracked in a dedicated register, and released against a schedule tied to the OEM’s warranty terms.
The problem is that reconciliation systems designed for the general trade-payable world treat any invoice-vs-remittance gap as a short-payment. When Mahindra pays a Motherson Sumi invoice of ₹28.5 lakh with a bank credit of ₹27.075 lakh, a naive system will flag ₹1.425 lakh as unmatched, generate a dispute ticket, and start ageing the shortfall. The finance controller now has to unwind that misclassification manually, and if the volume runs into thousands of invoices a month, this becomes the single biggest source of noise in the AR ledger.
This article is for finance controllers, AR managers, and treasury teams at auto component manufacturers dealing with OEM retention deductions. It explains how to model retention correctly, why the Section 43B(h) MSME clock does not run on retention until release, and how to build a reconciliation flow that keeps retention separate from short-payments and rejections.
The reconciliation in one paragraph
An OEM’s remittance against a supplier invoice includes a retention debit line — typically 5% of the pre-tax invoice value — that must be classified as a retention receivable, not a short-payment, rejection, or rebate. The retention register tracks each open retention amount with its contractual release date (invoice date or delivery date plus the warranty period), and the 43B(h) 45-day clock does not start until that release date passes. Ind AS 115 treats retention as revenue recognised at supply time; Ind AS 109 requires a modest expected credit loss allowance on the retention receivable. When the OEM later releases the retention as a separate remittance, the platform closes the retention register entry against the original invoice — not against a new invoice — and the accounting cycle completes without ever having overstated overdue receivables or overpaid MSME interest.
What retention debit looks like in India
Retention money is universal in Indian auto manufacturing. The OEM buys braking assemblies from Endurance Technologies, wiring harnesses from Motherson Sumi, forgings from Bharat Forge, fasteners from Sundram Fasteners, or lighting modules from Uno Minda — and in every one of these relationships, the master purchase agreement includes a warranty retention clause.
The commercial reasoning is straightforward. The OEM will not know if a batch is defective until it has been fitted, shipped, and driven for weeks or months. A brake caliper that fails after 50,000 km costs the OEM warranty-claim liability, dealer service time, and brand damage. By holding back a small percentage of every payment, the OEM has a security pool it can debit if a defect emerges without having to raise a fresh claim on the supplier’s ledger.
Typical retention terms in India:
- Standard components (fasteners, harnesses, plastic trim) — 5% retention, released after 90 days from delivery
- Powertrain and safety-critical parts (brakes, steering, airbags) — 5% to 10% retention, released after 120 to 180 days
- New Part Development (NPD) parts in initial production run — up to 10% retention, extended warranty window
- Long-warranty commercial vehicle parts — some OEMs like Ashok Leyland and Tata Motors extend retention up to 12 months for engine and chassis components
The dominant OEMs — Maruti Suzuki, Hyundai India, Tata Motors, Mahindra & Mahindra, Ashok Leyland — each have their own retention percentage tables baked into supplier agreements. Some issue a structured remittance advice with explicit retention reason codes; others send a consolidated debit note. Either way, the supplier’s AR ledger must know the difference between a retention deduction and a genuine short-pay.
The regulatory and accounting overlay
Retention money touches four distinct regulatory frameworks. Getting the classification wrong in reconciliation propagates errors through all four.
Section 43B(h) of the Income Tax Act
Section 43B(h) disallows a deduction in the year of accrual for any sum payable to a Micro or Small enterprise where payment is not made within the timelines under Section 15 of the MSMED Act 2006 — 15 days without a written agreement, 45 days with a written agreement, hard-capped at 45 days.
The critical point for retention: the 45-day clock runs from the date the amount becomes due. For retention money, the amount is not contractually due until the warranty period expires. If Mahindra retains ₹1.425 lakh on 10 April 2026 and the contract says the retention is released 120 days later on 8 August 2026, the 45-day clock starts on 8 August 2026 — not 10 April 2026. Only if Mahindra fails to pay the retention within 45 days of 8 August 2026 does Section 43B(h) potentially disallow the deduction.
This distinction matters because auto component suppliers to OEMs are frequently classified as Micro or Small enterprises under the revised MSMED Act thresholds (investment below ₹10 crore, turnover below ₹50 crore for Small enterprises).
CGST Section 16(2) — ITC Clawback
The Second Proviso to Section 16(2) requires the buyer to pay the supplier the full invoice value (including GST) within 180 days of the invoice date, failing which the input tax credit reverses proportionally. Retention deductions push part of the invoice value past the 180-day boundary in some contracts.
CBIC Circular 170/2021-GST and the Suncraft Energy case have clarified that the ITC reversal on unpaid consideration is proportional, not full. If ₹1.425 lakh out of ₹28.5 lakh (5%) remains unpaid at day 180, the ITC reversal is on 5% of the GST — not the full GST on the invoice. Some OEM contracts specifically extend the retention release beyond 180 days for long-warranty parts; in those cases the OEM must either restructure the payment to fall within 180 days or bear the proportional ITC reversal.
Ind AS 115 — Revenue Recognition
Under Ind AS 115, the entity recognises revenue when control transfers to the customer. Retention money is a payment timing mechanism, not a variable consideration — the price is not reduced, only deferred against a warranty condition. Consequently, the full invoice value (including the retained 5%) is recognised as revenue at the time of supply.
Where a specific contract structures retention as a warranty-service reduction (rare in Indian auto), the entity would need to identify a performance obligation for the warranty and allocate consideration. Standard OEM retention terms are payment timing and do not create a separate performance obligation.
Ind AS 109 — Expected Credit Loss
Retention receivables are financial assets and subject to the expected credit loss (ECL) framework. Because retention release is contingent on defect-free performance during the warranty window, entities that experience release-holdback events (partial release due to warranty claims) should provide a modest loss allowance against retention receivables. In practice, this is a small percentage — historical hold-back rates observed across Tier-1 suppliers are usually well under 1% of total retention pool — but it is required disclosure.
A worked example
All numbers below are illustrative and drawn from a hypothetical Tier-1 supplier scenario for teaching purposes.
Scenario. Motherson Sumi supplies a wiring harness lot to Mahindra & Mahindra under a master supply agreement that includes a 5% retention against 120-day warranty performance.
| Line item | Value |
|---|---|
| Invoice number | MS/2026/04/0872 |
| Invoice date | 10 April 2026 |
| Base value | ₹24,15,254 |
| GST (18%) | ₹4,34,746 |
| Invoice total | ₹28,50,000 |
| Retention (5% of pre-tax value) | ₹1,20,763 |
| Contractual payment terms | 45 days from invoice |
| Warranty period | 120 days from delivery |
| Delivery date | 10 April 2026 |
| Contractual retention release date | 8 August 2026 |
Payment run on 25 May 2026 (day 45).
| Entry | Amount |
|---|---|
| Invoice payable | ₹28,50,000 |
| Less: Retention debit (5%) | (₹1,20,763) |
| Net bank credit received | ₹27,29,237 |
Naive reconciliation. Sees ₹28,50,000 invoice against ₹27,29,237 credit, flags ₹1,20,763 as short-payment. Ages the shortfall starting 10 April 2026. If Motherson is classified as a Small enterprise (which it is not — but many Tier-2 suppliers are), the naive system reports the ₹1,20,763 as breaching Section 43B(h) by day 46.
Correct reconciliation.
Journal on receipt of ₹27,29,237:
| Account | Debit | Credit |
|---|---|---|
| Bank | ₹27,29,237 | |
| Retention Receivable — Mahindra | ₹1,20,763 | |
| Accounts Receivable — Mahindra (invoice MS/2026/04/0872) | ₹28,50,000 |
The Accounts Receivable is now fully closed on this invoice. The retention receivable is a separate line, tracked in the retention register with a due-for-release date of 8 August 2026.
Retention release on 12 August 2026. Mahindra runs its retention release cycle and remits ₹1,20,763 with a remittance advice referencing invoice MS/2026/04/0872.
Journal on release:
| Account | Debit | Credit |
|---|---|---|
| Bank | ₹1,20,763 | |
| Retention Receivable — Mahindra | ₹1,20,763 |
Full cycle closes cleanly. The 43B(h) test is applied only if this release payment is delayed beyond 45 days from 8 August 2026 — which did not happen here.
Common reconciliation breakages
Retention classified as short-payment. The single most common failure. Reconciliation systems that match on invoice-vs-remittance-amount without parsing the debit advice reason code will flag every retention as an exception. Symptom: exception queue grows by 5% of every invoice value; false dunning notices sent to OEM buyers who take offence at being chased for money they are contractually entitled to withhold.
Wrong Section 43B(h) clock start. If the buyer’s tax team applies 43B(h) from the invoice date to the retention portion, they will book unnecessary disallowance in their own AY (as a buyer) or their supplier will book unnecessary interest income (as a Small enterprise). Correct rule: the 45-day clock starts from the retention release date, not the invoice date, because that is when the amount becomes contractually due.
Retention receivable not aged separately. Some ledgers park retention money inside general trade receivables. When the retention release is delayed by the OEM beyond the contractual release date, it does not show up in the standard ageing report because the ageing bucket has been reset to the release date. Retention receivables must be aged from their contractual release date so that delayed releases are visible.
No warranty period per supplier / per part class. Master data gap. If the retention register does not know that Endurance’s brake assemblies have a 120-day warranty while Uno Minda’s lighting parts have a 90-day warranty, it cannot compute a release date. Some auto component companies solve this by holding a single default warranty period (90 or 120 days) and manually overriding for exceptions — this works only if the exception rate is low.
Retention release matched to a new invoice. When the OEM releases retention as a separate remittance, some suppliers book it as a fresh invoice payment against the next-oldest open invoice. This double-counts revenue (retention is already booked as revenue on the original invoice) and understates the true retention receivable balance. Correct treatment: the release must close the retention receivable, not any open trade receivable.
GST retention confusion. GST on the full invoice value is paid at supply time — retention does not defer the GST liability. Suppliers who provision GST only on the net-of-retention amount face short-payment of output GST liability and reversal notices under Section 74.
How a reconciliation platform handles this
A production-grade auto-component reconciliation platform models retention as a first-class transaction type, not a residual exception.
Supplier and part master. Each OEM contract is captured with the retention percentage, warranty period in days, and applicable part categories. Motherson Sumi’s contract with Mahindra sits alongside Endurance’s contract with Tata Motors — each with its own retention rules. Where an OEM issues structured remittance advice with reason codes, the platform maps those codes to the retention transaction type.
Remittance parsing. Every OEM remittance file (bank statement narration, IDoc, EDI 820, MT940, or portal download) is parsed for debit advice reason codes. When a reason maps to retention (English variants: retention, security, warranty hold, hold-back), the platform decomposes the remittance into a payment against the invoice plus a retention receivable entry.
Retention register. Each retention receivable is a row with: source invoice number, source invoice date, retention percentage, retention amount, contractual release date, actual release date (once known), status (open / released / partial-release / claimed against defect). The register drives a release-tracking view for AR teams.
Section 43B(h) clock. For suppliers flagged as Micro or Small enterprises in the master, the platform holds the 43B(h) clock until the retention release date, then starts the 45-day countdown from that date. Only if the OEM misses the 45-day window from the release date does the retention appear in the 43B(h) disallowance report. This aligns with the treatment described in Section 43B(h) MSME payment reconciliation for genuine trade payables.
Warranty claim tie-back. If the OEM later raises a warranty claim and debits the retention pool against a defect, the platform closes the retention receivable against a rejection or debit-note entry — not against a cash release. This ensures the retention register does not carry a stale open balance when the money will never be released.
Ageing correction. The standard AR ageing report is corrected to age retention receivables from the contractual release date, not the invoice date. Delayed releases beyond release date show up in the standard 30/60/90 buckets from that date onward.
For companies dealing with retention across multiple OEMs and thousands of invoices per month, a purpose-built reconciliation software India instance ties the retention register to the vendor master, the OEM remittance file, and the GST return workflow. The same infrastructure that powers GST reconciliation software for GSTR-2B and IMS matching also handles the retention lifecycle, because both are variations on the same core problem: matching a partial or split remittance to its correct source obligation.
Cross-reference articles in this cluster: retroactive price increase — credit note aggregation, rejection debit after invoice paid, and the MSME 45-day payment compliance tracker for the taxable-interest angle on delayed MSME payments.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Ministry of Corporate Affairs — Ind AS 115 Revenue — Paragraphs on variable consideration and constraining estimates of variable consideration in customer contracts
- ▸ Ministry of Corporate Affairs — Ind AS 109 Financial Instruments — Expected credit loss model applicable to retention receivables
- ▸ MSMED Act 2006 — Section 15 — Timeline for payment of amount due; interest liability on delayed payments
- ▸ Income Tax Act — Section 43B(h) — Deduction allowed only on actual payment for sums payable to Micro and Small enterprises
- ▸ CGST Act — Section 34 — Credit and debit notes — timing and conditions for GST adjustment