GST on Export of Software and SaaS Services: Getting the Export Classification Right

If you run a SaaS or software company in India billing a customer abroad, it's tempting to treat the GST question as already settled: the customer isn't in India, so the invoice goes out at zero GST, end of story. That instinct is usually right, but it isn't automatic, and it isn't decided by where your customer happens to sit. Export of services is a specific, defined status under GST law, one that makes the transaction zero-rated rather than simply GST-free, and it only applies when a full set of conditions holds together at once. Miss one of them, and a sale invoiced at zero GST can turn out to have never qualified as an export, with the tax you didn't charge still technically owed. For a SaaS business with a foreign parent, subsidiary, or referral partner in the mix, or one earning through a platform or commission model, this is exactly where the real complexity sits, and it's worth working through deliberately rather than assuming.

Export of Services Is a Defined Test, Not Just 'Customer Outside India'

Under Section 16 of the IGST Act, export of services is one of three categories treated as zero-rated supply, alongside export of goods and supply to a Special Economic Zone unit or developer. Zero-rated is a specific status, not a casual synonym for 'no GST charged.' An exempt supply also carries no output tax, but the input tax credit behind it gets blocked or reversed, so the GST paid on whatever went into delivering the service, things like cloud hosting, third-party software licences, payment gateway fees, and contractor invoices, ends up stuck as a real cost. A zero-rated supply carries no output tax either, but the credit stays claimable, and can eventually be claimed back in cash. That difference is the entire economic point of getting the export classification right: it decides whether the GST paid on your inputs comes back to you or quietly sits in your cost base.

Whether a specific sale actually counts as export of services comes down to five conditions, and all five have to hold at once, not just the one that happens to be easiest to check. The supplier has to be located in India. The recipient has to be located outside India. The place of supply has to work out to a location outside India, a separate legal determination, not an assumption based on where the recipient is registered or billed from. Payment has to be received in convertible foreign exchange, or in Indian rupees specifically where the RBI permits it. And the supplier and recipient can't merely be establishments of the same distinct legal person. A SaaS company can satisfy four of these without any effort at all and still fail the fifth, and the sale stops being an export the moment any single condition doesn't hold, regardless of how obviously foreign the counterparty looks on the invoice.

Once a sale clears all five conditions, invoicing it at zero GST works the same way it does for any other export of services: furnish a Letter of Undertaking (Form GST RFD-11) on the GST portal, free and valid for one financial year, and invoice without charging IGST upfront. It has to be filed fresh before your first export invoice of each financial year, so a SaaS company billing customers abroad every month can't treat this as a one-time setup step. Paying IGST and claiming it back afterward is available as an alternative, though most SaaS exporters find LUT simpler to run month over month.

The Condition That Catches SaaS Companies Off Guard: Same Legal Person, Different Countries

Of the five conditions, the one that causes the most confusion for SaaS founders is the last one: the supplier and recipient can't merely be establishments of the same distinct legal person. It's easy to read that condition, nod, and move on, since your customer obviously isn't you. But GST doesn't stop at the invoice; it looks at whether the two sides of the transaction are genuinely separate parties in the first place. The clearest case where this condition fails is billing your own branch, liaison office, or project office abroad. That's still legally the same company, just operating in two places, so a service billed from the Indian entity to its own overseas office doesn't qualify as an export just because the invoice shows a foreign address and the payment arrives in dollars. Money crossing a border isn't the test. Two genuinely separate parties transacting is.

Where this gets genuinely harder for a SaaS business is the foreign subsidiary or group company case, and it's worth being honest that this isn't a single clean rule. A wholly-owned subsidiary incorporated abroad is, on the face of it, a separate legal person from its Indian parent: different company, different registration, different jurisdiction, so billing that subsidiary for software, platform access, or shared services looks nothing like billing your own branch office at first glance. But the closer the two entities are in practice, in ownership, in how the service is actually used, in whether the 'customer' entity is a genuine independent recipient or effectively a pass-through for the Indian company's own group operations, the more this specific condition deserves a deliberate look rather than an assumption that a related entity counts the same way an unrelated foreign customer would. This is not a case where a general rule of thumb safely substitutes for checking the structure of the actual transaction.

The takeaway isn't that billing a foreign subsidiary or group entity automatically fails this condition; plenty of genuine intra-group service arrangements do qualify as exports. It's that this is the condition a SaaS founder is least likely to think to double-check, since the invoice itself gives no hint that anything differs from selling an ordinary foreign customer. Any recurring billing arrangement with a foreign parent, subsidiary, or affiliate is worth confirming against this condition specifically, before it becomes a pattern across dozens of monthly invoices rather than after.

The Intermediary Trap: Are You Supplying the Service, or Arranging Someone Else's?

A separate risk sits alongside the five conditions, and it applies even when the recipient is unquestionably foreign and completely unrelated to your company: being classified as an intermediary. An intermediary, in this context, is a business that arranges or facilitates a supply between two other parties rather than supplying the service on its own account, similar to a broker or an agent rather than a principal seller. Where a transaction is found to be an intermediary arrangement, it can lose export and zero-rated treatment even though the counterparty paying you is genuinely, verifiably outside India.

The mechanism behind this is the same place-of-supply logic that decides ordinary transactions, just pointed in a different direction. A straightforward cross-border service generally takes its place of supply from the recipient's location, which is what lets an ordinary SaaS sale qualify as an export in the first place. An intermediary's services don't follow that path. Where a business is treated as an intermediary for a given transaction, GST's place-of-supply rules for that category generally tie the place of supply to the intermediary's own location instead, which for an Indian business is India. That breaks the export test not because the counterparty stops being foreign, but because place of supply stops being outside India, one of the five conditions covered earlier.

This is a genuine, recurring point of dispute for tech-enabled services businesses. Certain SaaS models sit closer to the line than a straightforward subscription does: platforms connecting Indian service providers with foreign customers, referral or commission-based arrangements, and businesses supporting a foreign principal's own end customers on its behalf all invite the question. Whether a specific business actually is an intermediary depends on the real substance of what it's doing, principally whether it supplies its own service to the counterparty on its own account, or arranges a supply that's really happening between two other parties, a fact-specific determination general guidance can't safely settle for any one company. If your SaaS business earns through referral fees, commissions, or a marketplace-style model rather than a straightforward subscription, treat the intermediary question as one to actively work through, not assume away.

Proving It Happened: Payment Realisation and the FIRC

Meeting all the conditions on paper isn't the same as being able to prove it later, and for export of services specifically, the invoice by itself proves very little. What actually substantiates the claim that payment was received in convertible foreign exchange is bank documentation: a Foreign Inward Remittance Certificate (FIRC), or the equivalent bank realisation certificate your bank issues for that specific transaction. This isn't paperwork to gather only if you're ever asked. It's the evidence the export claim rests on, and it needs to be collected and matched against the specific invoice it relates to, not just held in a general folder of proof that you get paid internationally.

Timing matters as much as the document itself. Payment has to actually arrive in convertible foreign exchange within the window FEMA regulations allow, and an LUT doesn't cover a specific invoice retroactively if that window is missed. If a customer sits on an invoice for months, or pays through a route that doesn't generate proper bank documentation, that invoice's export status is at risk regardless of how clean the rest of your export sales look. For a SaaS business raising recurring invoices to the same foreign customers, this is worth tracking as its own line item, rather than something to notice only when a refund claim or an assessment forces the reconciliation.

Confirm Before You Invoice, Not After

The conditions, the intermediary question, and the documentation all point toward the same practical rule: confirm whether a sale genuinely qualifies as an export, and confirm your LUT or bond is actually in place, before you issue the invoice at zero GST, not after. This matters because of how the correction works if the classification turns out to be wrong. If a transaction invoiced at zero GST later turns out not to have qualified, whether because a condition wasn't actually met or because the arrangement gets treated as intermediary, the GST that should have been charged becomes payable, along with interest for the period it went unpaid. That liability doesn't disappear because the mistake was made in good faith, and because SaaS billing repeats the same customer relationship and contract terms every month or renewal cycle, getting the classification wrong once usually means getting it wrong on every invoice raised under that arrangement until someone catches it. Treating export classification as a decision to revisit whenever a new customer, entity structure, or revenue arrangement shows up, rather than a box ticked once, is what actually keeps this manageable.

Before raising an invoice at zero GST for a customer outside India, it's worth running through the same checklist every time, especially for a new customer, a new contract structure, or any related-party arrangement:

• Confirm the recipient is genuinely located outside India, not an Indian entity routing payment through a foreign account
• Work out the place of supply for this specific service on its own terms, rather than assuming it simply follows the recipient's address
• Check whether the recipient is a foreign branch, liaison office, or other establishment of your own company; if so, this condition fails regardless of the other four
• For a foreign subsidiary, parent, or group entity as customer, confirm the structure and substance of the relationship specifically, rather than treating it like an unrelated foreign customer by default
• Assess whether this transaction could be seen as arranging or facilitating a supply between two other parties, rather than supplying your own service on your own account
• Confirm a valid LUT is on file for the current financial year, or that a bond is in place if you're not eligible for LUT, before the first invoice goes out
• Set payment terms specifying convertible foreign exchange, or Indian rupees only where RBI rules actually permit it, and put a process in place to collect the FIRC or bank realisation certificate for every invoice once payment lands
• When a transaction involves a related entity, a commission or referral structure, or a delayed remittance, get the classification specifically reviewed rather than defaulting to how you've treated other, unrelated customers

None of this makes exporting software or SaaS services out of India harder than it needs to be. The conditions are specific, but they're knowable in advance, and each one can be confirmed before an invoice goes out rather than reconstructed after a notice arrives. Businesses that treat this as a five-minute check built into onboarding a new foreign customer, rather than a topic to revisit only when something goes wrong, are the ones that get the cash-flow benefit of zero-rating without ever finding out what the alternative costs.