It supports export without payment of integrated tax where conditions are met.

Should LUT be tracked annually?

Yes. Keep financial-year wise acknowledgement and export linkage.

Does bank realisation matter?

Yes. It supports export and refund evidence.

GST & Indirect Tax

GST LUT Renewal and Export Invoice Controls

Finin2min GST Desk·June 2026·7 min readLUT

Reviewed by CA Nikhil Gupta · Last reviewed 20 June 2026

LUT protects exporter cash flow only when renewal, invoice wording, export realisation, bond conditions and refund/zero-rated records are monitored.

Quick View

Decision

Renew LUT before exports under LUT and keep invoice-level export completion evidence.

First action

Create a financial-year LUT tracker with ARN, validity, invoice series and export realisation status.

Core evidence

Official source, working paper, approval, acknowledgement and correspondence.

Main warning

Using an old LUT or missing realisation evidence can create tax, interest and refund risk.

Workflow Map

Check exporter eligibility, GST registration and prior compliance before LUT filing.
File LUT for the financial year and save ARN/acknowledgement.
Map each export invoice to shipping/service proof, payment realisation and GST return reporting.
Monitor time limits, non-realisation, amendments, credit notes and refund claims.
Close with bank evidence, reconciliation, return data and management exception report.

Law and Source Map

Area	What to check	Working control
LUT	Eligibility, filing and financial-year validity	Retain ARN and signatory proof.
Invoice	Zero-rated wording, GSTIN, place and supply details	Match invoice to return.
Realisation	Bank/FIRC/e-BRC or service export evidence	Track due dates and exceptions.
Refund/returns	GSTR data, credit notes and refund file	Reconcile before claim.

Section-wise Decode

LUT layer

LUT is a condition-based facility, not a permanent exemption.

Invoice layer

Export invoices should support zero-rated treatment and audit trail.

Realisation layer

Foreign exchange realisation evidence protects LUT/refund position.

Exception layer

Non-realisation or wrong invoicing should be escalated before refund or audit.

Working File and Reconciliation

For this gst lut renewal and export invoice controls workflow, the working paper should not be a loose note. It should connect the official source, the user facts, the computation or decision, the filing or complaint route and the final evidence of closure. This is the control that prevents a guide from becoming generic advice.

Record	Documents to keep	Reconciliation test
LUT	Source copy, fact note, approval trail, working sheet and closure evidence for eligibility, filing and financial-year validity.	Retain ARN and signatory proof. Record who checked it, when it was checked and what exception was considered.
Invoice	Source copy, fact note, approval trail, working sheet and closure evidence for zero-rated wording, gstin, place and supply details.	Match invoice to return. Record who checked it, when it was checked and what exception was considered.
Realisation	Source copy, fact note, approval trail, working sheet and closure evidence for bank/firc/e-brc or service export evidence.	Track due dates and exceptions. Record who checked it, when it was checked and what exception was considered.
Refund/returns	Source copy, fact note, approval trail, working sheet and closure evidence for gstr data, credit notes and refund file.	Reconcile before claim. Record who checked it, when it was checked and what exception was considered.

Use the GST LUT renewal and export invoice controls page with related internal routes only after the source row and workflow step have been matched to the facts.
Keep a concise chronology if the matter involves a deadline, complaint, remittance, filing, notice, cyber event or board decision.
Save the source material in the same folder as the working papers so that a later reviewer can reproduce the conclusion without relying on memory.
Where the issue touches more than one law family, keep separate tabs for legal source, computation, portal filing, accounting entry and management approval.

Red Flags and Escalation Controls

Use this gst lut renewal and export invoice controls page as a controlled workflow, not as a shortcut. Stop and escalate when the facts are incomplete, the official source has changed, or the evidence file cannot prove the conclusion independently.

The source, facts or party status do not match the GST LUT renewal and export invoice controls workflow.
There is a statutory deadline, regulator notice, bank/portal query, complaint number, penalty exposure or money already at risk.
The file has source material but no working paper explaining why that source applies to the present facts.
Internal records disagree: books, portal acknowledgement, bank statement, tax return, statutory register or board paper show different facts.

When escalation is needed, preserve the current source copy, transaction chronology, working sheet, approvals, portal acknowledgements, correspondence and rejected alternatives. That record lets an adviser, auditor, banker or regulator see what was known on the decision date and why the action was taken.

Forms, Portals and Acknowledgements

For this gst lut renewal and export invoice controls workflow, do not invent offline forms. Use the official portal, statutory form, regulator acknowledgement, challan, ARN, SRN, PRAN, bank reference or filing receipt that actually applies to the facts.

Identify the official form, portal, acknowledgement number or bank/regulator reference before closing the task.
Keep the source copy and portal screenshot or downloaded acknowledgement in the same evidence folder.
Where no public PDF form is prescribed, retain the portal instruction, submitted data, challan or system-generated acknowledgement instead of creating an artificial substitute.
If the route depends on bank, MCA, GST, RBI, PFRDA, labour or tax portal processing, record the user, filing date, status and follow-up owner.

When a prescribed form is online-only or dynamically generated, the working file should keep the submitted copy, system receipt and source instruction rather than a manually created substitute file.

Practical Example

A SaaS exporter files LUT in April. The monthly file should map invoices, contract, realisation, GSTR-1/3B and exceptions.

Highlighted Points

Keep the official source open while making the decision.
Record the date, facts, conclusion and evidence owner.
Escalate when money, penalty, licence, foreign exchange, personal data or limitation risk is present.
Preserve portal acknowledgements and regulator correspondence with the working file.

Exam and Advisory Case Study

Exam case: An exporter has LUT but invoices domestic supplies as export. The LUT exists, but facts do not support zero rating.

Advisory note: if the source, date, party status or evidence trail changes, redo the conclusion rather than copying a prior file note.

Finin2min Summary

LUT pages should combine eligibility, renewal, invoice controls, realisation and refund/return reconciliation.

Q&A

When should LUT be filed?

Before making zero-rated supplies under LUT for the relevant financial year.

Is LUT enough for refund?

No. Invoice, export and realisation evidence also matter.

What should be tracked monthly?

Invoice, return, payment realisation, credit note and exception status.

When should tax be paid?

If conditions fail, evaluate tax/interest exposure under current law and facts.

Primary Official Sources

Use the source as it stands on the decision date. Applicability can change with facts, dates, thresholds, entity type, residency and regulator instructions.

Disclaimer: This article is for education and workflow planning only. It is not legal, tax, investment, financial, insurance, cyber-forensic or regulatory advice. Verify the current official source and obtain qualified advice for material decisions.