E-Invoicing for Export Services & Goods in India (2026)
Export invoices look tax-free on paper — zero-rated under LUT, no IGST on the face — but if your turnover puts you in GST e-invoicing scope, those invoices still need an IRN before they leave your system. Export of goods, export of services, and domestic B2B use different supply types, different buyer fields, and different validation rules on the same IRP infrastructure. This is operational guidance on how those three streams differ and which software handles each — not tax advice.
⚡ Key Takeaways
- Businesses above the ₹5 crore e-invoicing threshold must register export tax invoices on the IRP and carry an IRN — zero-rating under LUT does not exempt you from e-invoicing.
- Export of goods uses supply types EXPWP/EXPWOP; export of services and SEZ supplies use their own schema fields — domestic B2B templates will fail IRP validation if reused unchanged.
- LUT (Letter of Undertaking) or bond is how you export without charging IGST; file the LUT before the financial year. That is a tax position — separate from the operational step of generating the IRN.
- ERP and compliance-first e-invoicing tools (Clear, IRIS, Cygnet.One, TallyPrime, Zoho Books) are the right layer for export invoices; workflow tools built for domestic channel POs are not.
- FilFlo generates IRNs for domestic B2B and quick-commerce channel invoices — not export invoicing. Brands that do both typically run export through ERP/compliance software and domestic channels through FilFlo.
Disclaimer: This is operational guidance, not tax advice. LUT eligibility, bond requirements, shipping bill linkage, and place-of-supply rules depend on your facts and your CA's reading of the law. Confirm positions with a qualified tax professional before changing how you invoice.
Short Answer
If e-invoicing applies to you, every export tax invoice — goods or services — goes through the IRP and gets an IRN, just like a domestic B2B invoice. The difference is the payload: export supply types, zero tax under LUT, foreign buyer or SEZ details, and currency/FOB fields where the schema requires them. Domestic B2B e-invoicing software that only knows CGST/SGST/IGST on an Indian GSTIN buyer will not pass validation on an export JSON without export-specific configuration.
Most Indian FMCG and D2C brands we work with invoice domestically into quick-commerce DCs, modern trade, and distributors — that is where operational e-invoicing pain shows up daily. Export is a parallel stream, usually owned by finance and the ERP. The two streams share an IRP but not the same invoice birth point.
When Export Invoices Need an IRN
GST e-invoicing in India is turnover-gated: if aggregate turnover exceeded ₹5 crore in any financial year from FY 2017–18 onwards, e-invoicing applies — and once triggered, it stays on even if turnover later drops. Since 1 April 2025, businesses at ₹10 crore or more must report invoices to the IRP within 30 days of the invoice date.
The registrable documents list includes export tax invoices and export credit/debit notes alongside domestic B2B invoices. An export invoice is zero-rated — no IGST on the face when you have a valid LUT — but "zero-rated" and "exempt from e-invoicing" are not the same thing. If you are in scope, the export invoice still needs IRP registration before it is a valid tax document in the GST system.
The practical failure mode we see: finance raises an export invoice in a tool configured only for domestic B2B, skips the IRN because "there is no tax," and discovers the mismatch during GSTR-1 reconciliation or a customs/GST audit trail check. The fix is export-aware configuration in whatever system creates the invoice — not a separate manual portal upload after the fact.
Export of Goods vs Export of Services: What Changes on the Invoice
Both are exports under GST when place of supply is outside India (for services) or goods leave the country (for goods). On the e-invoice JSON, the differences matter because the IRP validates field-by-field.
| Dimension | Export of goods | Export of services | Domestic B2B (contrast) |
|---|---|---|---|
| Supply type on IRP | EXPWP (with tax) or EXPWOP (without tax) | Export service types per schema; SEZ uses SEZWP/SEZWOP | B2B — intra-state or inter-state |
| Tax on invoice | Zero-rated under LUT/bond, or IGST if not | Zero-rated under LUT where applicable | CGST+SGST or IGST as applicable |
| Buyer details | Foreign buyer; no Indian GSTIN | Foreign client or SEZ unit with required IDs | Indian buyer GSTIN mandatory |
| Linked documents | Shipping bill / bill of export where applicable | Service agreement / contract reference | PO, delivery challan, e-way bill for goods movement |
| Typical invoice owner | ERP / export billing module | ERP / service billing in accounting | ERP, or channel ops tool for PO-driven B2B |
Export of services covers IT services, consulting, royalties, and other Section 13 place-of-supply cases where the recipient is outside India. The e-invoice still registers on the IRP when you are in scope; the JSON carries the export service supply type and zero tax lines, not a domestic B2B buyer GSTIN. SEZ supplies to a SEZ developer/unit follow their own supply types — treat SEZ as a separate configuration in your software, not as generic export.
LUT and Bond: High-Level Context (Not a Tax Opinion)
To export goods or services without collecting IGST on the invoice, you typically file a Letter of Undertaking (LUT) on the GST common portal before the financial year begins — stating you will pay IGST if the export proceeds are not realised within the allowed period. The alternative is furnishing a bond with bank guarantee, more common when LUT is not available or not preferred.
LUT/bond governs whether IGST appears on the invoice. E-invoicing governs whether the invoice is registered on the IRP. A brand with a valid LUT still generates an export e-invoice with zero tax lines and the correct export supply type — then registers it for an IRN. Confusing the two leads to either charging IGST unnecessarily or skipping IRP registration because "the invoice has no tax."
Your CA files and renews the LUT; your software must reflect the zero-rated position on the JSON it sends to the IRP. If those two systems disagree, reconciliation breaks at GSTR-1 and the export document trail.
Software That Supports Export E-Invoices
Export e-invoicing belongs in the system that already owns export billing — usually the ERP or a compliance layer connected to it. The tools that handle export supply types reliably fall into three buckets:
Compliance-first e-invoicing platforms
Clear, IRIS Onyx, Cygnet.One, Masters India autoTax, and Whitebooks APIs connect to SAP, Oracle, Tally, or custom ERPs and push export payloads to the IRP with the correct supply types. They are built for finance teams registering invoices another system creates — including export lines, shipping bill references, and multi-GSTIN groups.
Accounting and distribution ERPs
TallyPrime, Zoho Books, Busy, and Marg ERP generate export invoices inside the accounting workflow — with export voucher types, zero-rated tax rows, and connected e-invoicing. If your export invoice is born in Tally, Tally's connected e-invoicing is the lowest-friction IRN path. For a deeper map of these tools, see our top 10 e-invoicing solutions in India guide.
Workflow-embedded tools (domestic B2B scope)
Tools that generate IRNs inside an order-to-cash flow — FilFlo included — are optimised for domestic B2B: Indian buyer GSTIN, channel PO quantities, per-warehouse GSTIN series, e-way bills on domestic dispatch. That is the daily invoicing loop for brands selling into Blinkit, Zepto, modern trade, and distributors. Export invoicing is a different document shape and a different buyer model; do not assume a domestic channel tool covers it without explicit export modules.
Before selecting software, demo three scenarios with real export JSON: zero-rated goods under LUT, export services to a foreign client, and a credit note against an export invoice. Ask whether shipping bill numbers flow through, whether multi-currency FOB values validate, and what happens when the IRP rejects a field — export payloads fail more often than domestic B2B because fewer teams test them.
Domestic Channel Invoicing Is the Other Half
If your export stream runs in ERP but domestic B2B invoices still go through spreadsheets and portal uploads, see how FilFlo generates IRNs inside the quick-commerce and modern-trade PO workflow.
Where FilFlo Fits — and Where It Does Not
FilFlo is an order-to-cash operations platform for FMCG and D2C brands selling into domestic B2B channels — quick commerce, modern trade, general trade distributors, and institutional buyers. IRN e-invoicing, e-way bills, credit notes, and GRN reconciliation are built into that domestic PO workflow: the invoice is born from an approved channel order, registered on the IRP from the dispatching warehouse's GSTIN, and stored against the order with the signed QR code.
FilFlo does not target export of goods or export of services. Brands that ship containers overseas or bill foreign clients for services run those invoices through their ERP or a compliance-first e-invoicing layer — the right home for export supply types, LUT zero-rating, and shipping bill linkage.
The overlap case is common: a brand exports to distributors in the Gulf and also supplies Blinkit dark stores in India. Two invoice streams, two birth points, one GST registration. Run export through ERP/compliance software; run domestic channel invoicing through FilFlo (or an equivalent operational tool). Trying to force both through one generic e-invoicing utility usually means one stream works and the other becomes manual again.
Domestic B2B vs Export: One Checklist
- Confirm e-invoicing scope — turnover threshold crossed? 30-day reporting rule applies?
- Separate export from domestic templates — supply type, buyer ID, tax lines, and linked documents differ.
- Align LUT/bond with invoice JSON — CA owns the tax position; software must mirror zero-rating on the IRP payload.
- Test credit notes on exports — export credit notes get their own IRN and reference the original export invoice.
- Route each stream to the right tool — ERP/compliance for export; operational O2C for domestic channel POs.
Frequently Asked Questions
Is e-invoicing mandatory for export invoices in India?
If your business crosses the GST e-invoicing turnover threshold — aggregate turnover above ₹5 crore in any financial year from FY 2017–18 onwards — export tax invoices and credit/debit notes must be registered on an Invoice Registration Portal and carry an IRN, the same as domestic B2B invoices. The invoice is zero-rated under LUT or bond, but the IRP registration step still applies when you are in scope.
What is the difference between export of goods and export of services for e-invoicing?
Both require an IRN when e-invoicing applies. Export of goods uses supply types EXPWP (export with payment of tax) or EXPWOP (export without payment of tax) on the invoice payload, with shipping bill or bill of export details where applicable. Export of services uses SEZWP or SEZWOP for SEZ supplies, or the export service supply types in the schema for overseas clients — with place-of-supply outside India and typically no IGST when covered by LUT. The JSON schema fields differ; generic domestic B2B templates will reject an export payload if supply type, tax values, and buyer details are wrong.
Do I need an LUT or bond for zero-rated export e-invoices?
To export without charging IGST on the invoice, you file a Letter of Undertaking (LUT) on the GST portal before the financial year starts, or furnish a bond with bank guarantee as the alternative. The LUT/Bond decision is a tax position your CA sets — it does not remove the IRN step. Your e-invoicing software must still generate a compliant zero-rated export invoice JSON and register it on the IRP.
Which e-invoicing software supports export invoices in India?
Compliance-first platforms — Clear, IRIS Onyx, Cygnet.One, Masters India autoTax, Whitebooks APIs — handle export supply types through ERP connectors or bulk utilities. Accounting suites — TallyPrime, Zoho Books, Busy, Marg ERP — support export e-invoices where the invoice is created inside the accounting system. Workflow tools like FilFlo generate IRNs for domestic B2B channel invoices; export invoicing is not their primary scope. Verify export supply types, shipping bill linkage, and LUT zero-rating in a demo before buying.
Can the same IRN process be used for domestic B2B and export invoices?
The IRP registration flow is the same — validate JSON, return IRN and signed QR code — but the invoice payload is not. Domestic B2B invoices carry B2B supply types with CGST/SGST or IGST. Export invoices carry export supply types, zero tax lines under LUT, foreign buyer or SEZ details, and currency/FOB fields where required. Software that only models domestic B2B will fail validation on export fields. Most brands running both streams use their ERP or a compliance layer for exports and a separate operational tool for domestic channel invoicing.
Domestic B2B E-Invoicing Inside the PO Workflow
Export stays in ERP. For quick-commerce and modern-trade POs, see how FilFlo runs IRN invoicing, e-way bills, and GRN reconciliation in one operational loop.
This is operational guidance, not tax advice. Confirm LUT, bond, and export compliance positions with your chartered accountant.