Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian SaaS exporters invoicing overseas customers must satisfy all five conditions of Section 2(6) of the IGST Act, file a LUT, e-invoice export supplies, and reconcile FIRCs against invoices within the RBI nine-month window — failure on any limb converts zero-rated supplies into IGST-bearing supplies and locks refund claims for months.
Verify the five Section 2(6) conditions per invoice, file Form GST RFD-11 at the start of each financial year, generate IRN for each export invoice, and reconcile FIRC realisation against invoice value within the nine-month FEMA window.
Section 2(6) IGST Act five-limb test, Form GST RFD-11 LUT, Section 13 place of supply rules, Rule 48(4) e-invoicing threshold ₹5 crore, FEMA nine-month realisation rule, GSTR-1 Table 6A reporting.
LUT-validated export invoice register, FIRC-to-invoice reconciliation matrix, GSTR-1 Table 6A reconciliation against books, and a nine-month realisation aging report flagging FEMA breaches.
Indian SaaS companies that invoice overseas customers operate in a narrow zero-rating window defined by Section 2(6) of the IGST Act, 2017. The export classification rests on five strict conditions, the LUT under Form GST RFD-11 must be live, the proceeds must arrive in convertible foreign exchange within nine months under FEMA, and every invoice over the e-invoicing threshold must carry an IRN. Miss any limb and the supply becomes a normal taxable supply attracting IGST at 18%, with a refund claim that takes 60-90 days to resolve.
How does the Section 2(6) five-limb test work?
Section 2(6) of the IGST Act lays down a cumulative test. The supplier must be located in India. The recipient must be located outside India, determined by reference to the place where the recipient is registered for tax or maintains a permanent address. The place of supply must be outside India under Section 13, which for SaaS supplies typically defaults to the location of the recipient. The payment must be received in convertible foreign exchange — USD, EUR, GBP, SGD, AED, and other RBI-recognised currencies — or in Indian rupees where the RBI specifically permits, such as for Bhutan and Nepal. Finally, the supplier and the recipient must not be mere establishments of a distinct person under Explanation 1 of Section 8.
The fifth limb is the trap most Indian SaaS exporters underestimate. If an Indian SaaS company invoices its own US subsidiary or its UK branch for software access, the supply is not an export — it is an intra-entity transfer between establishments of a distinct person, taxable as an inter-state supply under the cross-border establishment rule.
Quick reference: Section 2(6) and LUT compliance facts
| Compliance lever | Legal anchor | Threshold or rule | Documentation |
|---|---|---|---|
| Export of services definition | Section 2(6) IGST Act, 2017 | All five conditions cumulative | Invoice + agreement showing five limbs |
| Place of supply for SaaS | Section 13(2) IGST Act | Default: location of recipient | Customer master with overseas address |
| Zero-rating without IGST payment | Section 16(3)(a) IGST Act + Rule 96A | LUT in Form GST RFD-11 | LUT acknowledgement (ARN) |
| Convertible forex realisation | FEMA Master Direction on Export | Nine months from invoice date | FIRC / BRC from AD Category-I bank |
| E-invoicing for exports | Rule 48(4) CGST Rules | Aggregate turnover above ₹5 crore | IRN + signed QR + GSTR-1 Table 6A |
| GST refund of unutilised ITC | Section 54 + Rule 89 CGST | Within two years of relevant date | Form GST RFD-01 + Annexure-A statements |
| LUT eligibility bar | Notification 37/2017 CT | Below ₹2.5 crore tax evasion prosecution in last two years | Self-declaration in LUT |
What changes when the LUT route is chosen over the IGST-and-refund route?
A SaaS exporter has two paths under Section 16 of the IGST Act. The first is to pay IGST at 18% on every export invoice and claim refund under Section 54 of the CGST Act within two years of the relevant date. The second is to furnish a LUT under Notification 37/2017-CT and supply without payment of IGST, claiming refund only on the unutilised input tax credit accumulated on domestic procurements.
The LUT route dominates in practice because the cash impact of the IGST-and-refund route is brutal. Consider an exporter invoicing ₹15 crore quarterly. The first route locks ₹2.7 crore as IGST paid, sitting in the GSTN ledger until the refund order is processed. Even with the standard 60-day acknowledgement and 90-day disposal window, the working capital cost compounds across quarters. The LUT route avoids this entirely — IGST is never paid on the export invoice; only the input tax credit refund is claimed, typically on cloud infrastructure, software tools, and professional services consumed in the export delivery.
The LUT is filed once each financial year on the GST portal under Form GST RFD-11. It is auto-acknowledged with an ARN and is valid until 31 March of the year of filing. Renewal in April is non-negotiable — an exporter who issues an invoice on 5 April without a fresh LUT must pay IGST on that invoice, and the LUT cannot be retrospectively backdated.
How do you reconcile the FIRC against the export invoice?
The FIRC, increasingly issued in electronic form by AD Category-I banks, is the proof of inward remittance in convertible foreign exchange. The reconciliation matches three values per export transaction: the invoice value in foreign currency, the gross remittance received per the SWIFT MT103 confirmation, and the INR credit posted to the EEFC or domestic current account. Bank charges deducted by the correspondent bank, intermediary bank deductions, and the exchange margin applied by the AD bank produce predictable gaps that must be documented.
For SaaS exporters, the matching key is rarely a clean one-to-one mapping. Annual subscription invoices often realise across multiple wire transfers when customers pay quarterly. Conversely, a single wire transfer may cover several short-cycle invoices for the same customer. The FIRC-to-invoice reconciliation matrix must show the split clearly because the GST refund application under Annexure-A requires the realised foreign exchange against each invoice claimed.
The nine-month realisation rule under FEMA runs from the date of issue of the export invoice. A SaaS exporter invoicing on 15 April must realise the full proceeds by 14 January of the following year. If the customer is on a quarterly billing cycle with a 60-day payment term, the realisation typically lands well inside the nine-month window — but customers with NET-90 or NET-120 terms, or any payment dispute, can push realisation outside the window and trigger an automatic FEMA flag in EDPMS reporting.
Worked example: ₹62 crore SaaS exporter to US — quarterly LUT cycle
Consider an Indian SaaS company with ₹62 crore of annual export revenue billed entirely in USD to US enterprise customers on annual subscription contracts averaging USD 75,000 per customer. The company has 100 active overseas customers and the FY runs April to March.
The compliance cycle begins on 1 April. The finance team files Form GST RFD-11 on the GST portal and receives the ARN within 24 hours. The LUT is now valid until 31 March of the next year. On 5 April, the first annual invoice is issued in USD at the prevailing RBI reference rate of 83.40 per USD. The invoice value is USD 75,000, equivalent to ₹62.55 lakh at the invoice-date rate. The invoice is e-invoiced — the IRN is generated, the signed QR is printed on the PDF sent to the customer, and the invoice flows into GSTR-1 Table 6A as a zero-rated supply.
The customer remits USD 75,000 on 18 May via a SWIFT wire. The AD bank credits the EEFC account in USD on 20 May after deducting USD 35 of correspondent bank charges. The FIRC shows USD 74,965 realised at a conversion rate of 83.18, crediting ₹62.36 lakh to the INR current account. The FIRC-to-invoice reconciliation now logs a USD 35 short-realisation, attributable to standard wire charges, and a forex gain or loss against the invoice-date booking.
Across the quarter, the company issues 25 such invoices. The aggregate value is ₹15.64 crore. Cumulatively, the LUT route avoids ₹2.81 crore of IGST that would otherwise have been paid and refunded. The accumulated ITC on AWS Mumbai infrastructure costs, software licences, and India-resident professional services for the quarter totals ₹38 lakh — this is the actual refund the exporter files under Section 54 in Form GST RFD-01, attaching the Annexure-A statement linking each export invoice to its FIRC.
The nine-month aging report at the end of the quarter flags two invoices that have crossed 200 days without realisation — both attributable to customer payment disputes. These are escalated to the customer success team, with the finance team modelling the IGST exposure should the dispute extend beyond the FEMA window.
How does the new TDS payment-code era interact with SaaS export compliance?
The TDS framework reset under Sections 393 and 394 of the Income Tax Act, 1961 — and the payment-code architecture spanning 1001 to 1092 — operates in parallel to the GST export regime but rarely overlaps for outbound supplies. A SaaS exporter receiving foreign remittance does not deduct TDS on its own receipt. The TDS code era becomes relevant on the procurement side: payments to overseas software licensors are captured under Section 413 with payment code 1062, and the equalisation levy framework continues to apply to specified digital services where the recipient is non-resident without a permanent establishment.
For the SaaS exporter’s outbound revenue stream, the substantive overlap is in the books-to-GSTR-1 reconciliation. Zero-rated export invoices reported in Table 6A of GSTR-1 must match the export revenue line in the books, which in turn must match the FIRC realisations. When the exporter procures cloud infrastructure on AWS Mumbai, the GST on the input invoice is fully eligible for ITC, and the ITC refund claim under Section 54 closes the loop.
Plug in your quarterly export turnover, AWS spend, software licence spend, and domestic professional services to estimate the refund-able ITC pool and the working capital trapped in pending Section 54 claims.
Open the ITC Leakage Calculator →What recurring controls keep the Section 2(6) classification intact?
Finance teams that run SaaS export compliance cleanly build four recurring controls into the month-end close. The first is a Section 2(6) checklist applied to every new overseas customer — the five conditions are evidenced in the customer master before the first invoice is raised, including documentary proof that the customer is not an establishment of a distinct person. The second is a LUT calendar — the LUT renewal date is non-negotiable, with renewals filed in the final week of March every year. The third is a nine-month realisation aging — every open export invoice is aged against the FEMA window, with escalation triggers at 180 days and 240 days. The fourth is a GSTR-1 Table 6A reconciliation against the books export revenue line and against the FIRC realisation log.
A GST reconciliation software workflow can automate the Table 6A matching, while a broader reconciliation software India workflow handles the FIRC-to-invoice and books-to-bank matching. The CBIC publishes the operative notifications and circulars on the CBIC GST portal, which finance teams should monitor for any change to Notification 37/2017-CT or the LUT eligibility rules.
Continue reading
Indian SaaS exporters reading this article typically also read:
- SaaS subscription reconciliation India — how to match deferred revenue, cash receipts, and MRR schedules across multiple billing cycles.
- Multi-currency reconciliation for IT services — the FIRC, EEFC, and forex revaluation chain in detail.
- Ind AS 115 revenue reconciliation — the five-step model applied to SaaS performance obligations.