Skip to main content
Auto Components · Excel Template · India

OEM Debit Note Register Template (FOMP, Sorting, Line-Stop, Warranty)

Tier-1 and tier-2 auto component suppliers absorb 3-8% of dispatched value in OEM debit notes each year. This free 17-column register tracks every debit note by reason code, dispute status, and GST credit-note action — the input data for month-end review, QBR with the OEM, and Section 34 credit-note compliance.

Download CSV template ↓ See the column guide →

Quick reference

Columns 17
Sample rows 5 (Maruti, Tata, Mahindra, Bosch)
Reason codes FOMP, sorting, line-stop, warranty, quantity, quality
GST anchor Section 34 CGST Act (credit note time limit)
Format CSV (UTF-8) — opens in Excel, Google Sheets, ERP extract pipelines

When to use this template

Month-end OEM deduction review

Pull all debit notes raised in the month, group by reason code, and identify the OEM plant or part-number drivers of the largest deductions before close.

GST credit-note compliance ageing

Filter for rows where gst_treatment_required = CN and gst_cn_date is blank. The original_invoice_date column tells you which rows are approaching the Section 34 30-November deadline.

Quarterly business review with OEM

Slice by oem_name and reason_code to produce the standard QBR Pareto — most tier-1 suppliers carry this exact view into Maruti, Tata, and Mahindra commercial reviews.

Contested debit-note write-off decision

Filter contested rows where days_open > 365 — these are the candidates for the credit-committee write-off decision under the supplier's policy.

Column-by-column guide

Column What to put in it
debit_note_no OEM-issued debit note number. Always store verbatim — leading zeros and prefixes matter for OEM portal reconciliation.
debit_note_date Date on the debit note (yyyy-mm-dd). Drives the days_open ageing and GST credit-note time limit (Section 34, 30 Nov following FY-end).
oem_name OEM customer name — Maruti Suzuki, Tata Motors, Mahindra, Bosch, Hyundai, Ashok Leyland, etc. One row per debit note per OEM.
oem_plant Specific OEM plant raising the debit note — Manesar, Bawal, Pune, Chakan, Jamshedpur, Bidadi. Plant concentration matters for root-cause analysis.
original_invoice_no Supplier's tax invoice number against which the OEM raised the debit note. Ties the debit note to the GST original supply for credit-note purposes.
original_invoice_date Original invoice date — anchors the Section 34 30-November deadline for GST credit note issuance.
original_invoice_amount Taxable value of the original invoice (numeric, no commas). Used to compute the debit-note percentage and the recoverable cap.
debit_note_amount Gross debit-note amount (numeric, no commas). The deduction the OEM is applying.
reason_code Single-token reason — FOMP, sorting, line-stop, warranty, quantity, quality. Drives Pareto analysis and GST treatment selection.
reason_description Free-text expansion of the reason for the QBR pack and internal root-cause logs.
gst_treatment_required CN (credit note required — value reduction of original supply) or no-CN (compensation charge booked as expense without affecting original supply).
gst_cn_no GST credit note number once issued. Blank until the supplier issues the CN under Section 34.
gst_cn_date Date of GST credit note issuance. Must be before 30 November following the original invoice FY-end.
dispute_status accepted (supplier agrees), contested (supplier disputes), or under-review (open with quality/commercial team).
accepted_amount Portion of the debit note the supplier has accepted. Becomes the basis for the GST credit note value.
contested_amount Portion the supplier is contesting. Working capital lock until resolution.
days_open Days from debit_note_date to today (or to resolution date if closed). Ageing buckets drive escalation.

How it ties to TransactIG

This template is the manual version of what tier-1 auto component finance teams run inside TransactIG's auto component reconciliation — every OEM payment advice is parsed, debit-note lines are matched against the invoice they reduce, reason codes are normalised across OEMs, and GST credit-note action items are surfaced before the Section 34 deadline. The template is enough for a single-OEM supplier or a manual close. For multi-plant tier-1 suppliers running thousands of debit notes a month, the workflow becomes the bottleneck — that is where the platform takes over.

Frequently Asked Questions

What is an OEM debit note in auto component supply? +

An OEM debit note is a charge raised by the OEM (Maruti, Tata, Mahindra, Bosch, etc.) against a supplier's invoice for deductions such as field-failure-of-material parts (FOMP), sorting and rework at the OEM line, line-stop penalty, warranty claims, quantity short-receipt, or quality rejection. The OEM either deducts the amount from the next payment cycle or expects the supplier to issue a GST credit note. The debit note is a commercial document — the GST treatment depends on whether the original supply value is being reduced (credit note required) or whether it is a separate compensation charge.

What reason codes should an OEM debit note register track? +

Standard reason codes across Indian OEMs include FOMP (field-failure-of-material parts under warranty policy), sorting (rework charges at the OEM line for mixed-grade or defective shipments), line-stop (penalty for halting OEM assembly line), warranty (field warranty claims passed back to the supplier), quantity (short-receipt against invoiced quantity), and quality (rejected parts at incoming inspection). Tracking these codes separately is essential for root-cause analysis, quarterly business reviews with the OEM, and feeding the supplier's own quality and operations dashboards.

When is a GST credit note required for an OEM debit note? +

Under Section 34 of the CGST Act, a GST credit note is required when the value of the original taxable supply is being reduced — for example, on quantity short-receipt, quality rejection at incoming inspection, or warranty replacement where the supplier accepts the deduction against the original invoice. Time limit: the credit note must be issued by 30 November following the end of the financial year in which the original supply was made, or before filing the relevant annual return, whichever is earlier. Pure compensation charges (line-stop penalty, sorting fees with no quantity change) may not require a credit note — book as a separate expense or compensation.

How do contested debit notes affect supplier financials? +

When a supplier contests a debit note, the OEM typically still withholds the payment, creating a working capital lock equal to the contested amount. The supplier should book the disputed amount as a contingent liability with a corresponding receivable, age the dispute, and track resolution. CARO 2020 requires disclosure of disputed amounts under statutory dues and trade receivables. A contested debit note that ages beyond 12 months without resolution should trigger a write-off decision under the supplier's credit policy. The register's days_open column is the input to that ageing analysis.

Can this register feed quarterly business reviews with the OEM? +

Yes. The register, sliced by reason code and OEM plant, produces the input data for the standard QBR slides — Pareto of debit-note value by reason, ageing of open disputes, plant-wise concentration, and trend of total deductions as a percentage of dispatched value. The accepted vs contested split shows commercial acceptance rate. The GST credit-note column shows compliance hygiene. Most tier-1 suppliers maintain this register at the part-number and plant level, then aggregate up for the OEM relationship review.

Reconcile every OEM debit note against the invoice it reduces

TransactIG matches OEM payment advices to invoices, decomposes short-pays into reason codes, and triggers GST credit-note workflows before the Section 34 deadline.

Request a Demo Auto Component Reconciliation →