The 30-Day IRN Clock on Reinstatement Invoices: Where a Property Claim Quietly Loses Money

Property and machinery claims do not settle against estimates for long. They settle against work actually done and billed. A repairer rebuilds a damaged press line, a fabricator supplies replacement structural steel, an electrical contractor rewires a burnt panel room, and each of them raises a tax invoice on the insured. That invoice does two jobs at the same time. It evidences quantum for the surveyor and the loss adjuster, and it carries GST that the insured expects to recover as input tax credit.

Indian property practice generally settles reinstatement value claims net of recoverable GST, on the reasoning that the tax is not a cost to a registered insured because the credit is available downstream. That reasoning is sound, and it holds right up to the point where the credit is not actually available.

If the vendor's invoice never receives an Invoice Reference Number, the GST on it stops being a recoverable tax and becomes a real cost sitting inside the claim. The insured has paid the repairer in full, the insurer has settled net of tax, and the tax has nowhere to go. Nobody at the claims desk sees it happen, because the failure occurs in the vendor's compliance calendar weeks after the survey report is signed off and the file is closed.

The rule is narrow, dated, and unforgiving. Taxpayers with aggregate annual turnover of Rs 10 crore or more must report invoices, credit notes and debit notes to the Invoice Registration Portal within 30 days of the document date. The restriction took effect from 1 April 2025. Beyond the window the portal blocks IRN generation outright, and an invoice reported late is invalid for input tax credit.

Three features of that rule matter for claims work.

1. The clock runs from the invoice date, not from the date the insurer approved the scope, not from the date the surveyor assessed the item, and not from the date the insured paid.
2. There is no late-reporting route and no condonation counter. The portal simply refuses the document. The vendor cannot fix it by filing later.
3. The restriction covers credit notes and debit notes, not only invoices, which is where reinstatement billing gets caught most often.

Until recently a mid-market insured could assume most of its small repair panel sat outside e-invoicing entirely. That assumption expired. E-invoicing became mandatory from 1 April 2026 for any GSTIN whose aggregate annual turnover exceeded Rs 5 crore in FY 2025-26. The Rs 5 crore aggregate turnover threshold for GST e-invoicing was set by CBIC Notification No. 10/2023 Central Tax, dated 10 May 2023.

The two numbers do different jobs, and confusing them produces the wrong risk register:

• Rs 5 crore decides whether a vendor must issue e-invoices at all. Below it, the vendor raises an ordinary tax invoice and no IRN question arises.
• Rs 10 crore decides whether that vendor is also bound by the 30-day reporting deadline.

For a manufacturing or warehousing insured, the vendors who show up on a reinstatement file are exactly the businesses now crossing these lines: fabricators, machine rebuilders, HVAC and refrigeration contractors, panel builders, civil contractors and specialist restoration firms. Many of them are first-year e-invoicing filers with thin finance teams and no habit of watching a 30-day portal deadline. The insured's claim recovery now depends partly on the compliance maturity of a vendor it selected for engineering competence.

The size of the leak is easy to underestimate because it is never the base cost. It is only the tax, which is precisely why nobody budgets for it.

Take a machinery loss on a production line. The rebuild is scoped and awarded to a specialist repairer at Rs 1.2 crore, with GST at the rate applicable to the work, taken here at 18 percent, or Rs 21.6 lakh. The policy is on a reinstatement basis, the surveyor assesses the full rebuild as payable, and the insurer settles net of GST on the standard reasoning that the insured recovers the tax.

If the repairer generates the IRN inside the window, the arithmetic is clean. The insured funds Rs 1.42 crore to the vendor, recovers Rs 21.6 lakh as credit, and is indemnified.

If the repairer misses the window, the invoice can never carry an IRN. The insured has funded the same Rs 1.42 crore, holds no valid credit, and has been settled on the assumption that it does. Rs 21.6 lakh has moved from the tax ledger to the loss ledger, on a claim everyone treated as fully settled. Against a typical mid-market deductible on a machinery loss, that single failure can exceed the excess the insured deliberately retained.

The same shape repeats at smaller scale across a fire reinstatement with fifteen or twenty vendors. No single miss is dramatic. The aggregate on a large material damage rebuild is not small, and it is invisible in the claim file because the claim file closed months earlier.

Reinstatement billing is rarely a single clean invoice. Scope changes after the surveyor's assessment. Salvage is credited back once the damaged parts are recovered and valued. Retention is released on completion. A vendor over-bills against the original estimate and corrects it. Every one of those corrections is a credit note or a debit note, each with its own document date and its own 30-day reporting deadline for a vendor above the Rs 10 crore mark.

The salvage adjustment is the most common trap on property files. The repairer invoices the full replacement, the recovered scrap or serviceable parts are then valued and credited, and the credit note gets raised whenever the salvage realisation is finally agreed, which on a contested item can be well past the 30-day mark from any sensible document date.

There is a second consequence that runs the other way. When a supplier files a credit note, the corresponding input tax credit is auto-reversed in the recipient's GSTR-3B. So a scope-reduction credit note does not merely reduce the invoice value. It pulls back credit the insured has already taken, in a return period that may sit well after the claim was settled and reconciled.

A claims desk that agrees the salvage figure without agreeing the credit note mechanics has settled the commercial point and left the tax point open.

The Invoice Management System added a step that punishes an entirely reasonable accounts-payable reflex. When a recipient rejects an invoice in the Invoice Management System, or when the supplier files a credit note, the corresponding input tax credit is auto-reversed in the recipient's GSTR-3B.

On a claim file, rejection is exactly what a careful AP team does. The repairer's invoice arrives before the insurer has approved the scope. The billed figure differs from the assessed figure. The surveyor has queried two line items. The instinctive action is to reject the invoice in IMS and wait for the claim position to firm up.

The practical fix is a rule that AP applies to claim-related vendor invoices specifically: never reject on grounds of pending claim approval or pending quantum agreement. Those are commercial questions to settle with the vendor and the loss adjuster directly. Rejection is reserved for invoices that are genuinely not the insured's liability.

The controls are cheap. They are just not anybody's current job, because they sit between the claims function, the tax function and procurement.

1. Screen the vendor at award, not at billing. Capture each reinstatement vendor's GSTIN and confirm whether it is above Rs 5 crore (e-invoicing applies) and whether it is above Rs 10 crore (the 30-day deadline applies). Two questions on the work order.
2. Fix the invoice date to the billing decision, not the completion date. Ask vendors not to date an invoice until the scope is agreed and they are ready to report it. A document dated early and held for approval is the single most common way the window is lost.
3. Verify the IRN before releasing payment. Make IRN presence a payment-release condition on every claim-related invoice above a set value. This is the one control that catches the failure while it is still fixable by re-issuing.
4. Log every credit and debit note separately. Salvage credits, scope reductions and retention adjustments each get their own date and their own 30-day check.
5. Ring-fence claim invoices in IMS. No rejection on grounds of pending insurer approval or unagreed quantum.
6. Reconcile before the claim file closes, not at year end. Match every vendor invoice on the reinstatement to a valid IRN and a claimed credit while the vendor still wants the next job.

On a property insurance or fire insurance rebuild, steps one to three catch most of the exposure for a few minutes of work per vendor.

The last gap is documentary. Claim correspondence routinely records that settlement is net of recoverable GST and then says nothing about what happens if the tax turns out not to be recoverable. That silence puts the entire risk of a vendor's compliance failure on the insured, by default rather than by negotiation.

Three places to close it.

In the vendor work order, make e-invoice compliance an obligation, not an assumption. State that the vendor will generate a valid IRN within the statutory reporting window where applicable, that payment release is conditional on IRN evidence, and that the vendor bears the tax consequence of its own failure to report in time. This is standard supplier-terms drafting and vendors accept it without argument.

In claim correspondence with the insurer, say what the net-of-GST settlement assumes. A line recording that the settlement is computed net of GST on the basis that credit is available, and reserving the position where credit is denied for reasons outside the insured's control, keeps the point alive instead of conceding it silently.

In the claim file itself, keep the IRN evidence alongside the invoice. Where a claim is later reopened, audited, or taken into a quantum dispute, the credit position is part of the indemnity arithmetic and needs the same documentary discipline as the surveyor's assessment.

How far a given policy wording supports a gross-of-tax position, and how the settlement basis clause interacts with recoverable taxes, differs materially between insurers. Sarvada's searchable insurer policy-wordings intelligence lets a broker read settlement-basis and reinstatement clauses across the market side by side, so the tax assumption is examined before the slip is bound rather than after the vendor has missed a portal deadline. Request Access to search the clauses directly.