STPI / SOFTEX Export Filing
STPI / SOFTEX Export Filing is the declaration a software or IT-services exporter files, certified by STPI, to report the value of software exported electronically so the RBI can track realisation of the foreign proceeds. It appears in the books alongside export invoices and bank realisation. It matters because it is the regulatory bridge between an export invoice and inward remittance under FEMA.
What Is STPI / SOFTEX Export Filing?
When goods leave India through a port, customs records the export; but software and IT services delivered over data links have no physical shipment for customs to capture. The SOFTEX form fills that gap: it declares the value of software and IT/ITeS exported electronically, and the Software Technology Parks of India (STPI) certifies it, so the Reserve Bank can monitor that the export proceeds are realised and repatriated.
An Indian IT or SaaS exporter meets SOFTEX filing every billing cycle. Against each software export invoice, the exporter files SOFTEX with STPI, which certifies the declared value; the certified form then supports the bank in tracking inward remittance against the export. A significant change is coming: under FEMA 23(R)/2026-RB, which supersedes the 2015 Export of Goods and Services regulations, SOFTEX moves to a monthly Export Declaration Form (EDF) regime from 1 October 2026 — with SOFTEX remaining operative up to 30 September 2026.
Key terms
- Software Export Revenue (Section 10AA SEZ) — The income-tax deduction on SEZ software export profit.
- Foreign Currency Receivables — The export receivables SOFTEX tracks to realisation.
- Transfer Pricing for IT Services — Arm's-length pricing on exports to group companies.
How STPI / SOFTEX Export Filing Works
A software export moves from invoice to realisation through a set path:
- 1Raise the export invoice
The exporter invoices the overseas client for software or IT services — the source document for the declaration.
- 2File the SOFTEX declaration
Against the invoice (or a consolidated monthly set), the exporter files SOFTEX with STPI declaring the export value.
- 3STPI certifies the form
STPI verifies the declaration against the invoice and contract and certifies the value — the artefact banks rely on.
- 4Submit the certified form to the bank
The certified SOFTEX goes to the authorised-dealer bank, which tracks the export in its records.
- 5Realise and reconcile proceeds
Inward remittance is matched to the export within the FEMA realisation window, closing the loop.
Where STPI / SOFTEX Export Filing Applies — IT and Software Companies
SOFTEX filing applies wherever software or IT/ITeS is exported electronically:
- Software services exporters — Companies delivering development or support to overseas clients over data links file SOFTEX per export.
- SaaS and product firms — Subscription and product exporters declare electronically delivered software value.
- STPI-registered units — Units registered under the STP scheme file SOFTEX as a condition of the scheme.
- ITeS and BPO providers — IT-enabled services billed to foreign clients fall within the SOFTEX net.
- Firms preparing for EDF — Exporters must adapt processes for the monthly EDF regime from 1 October 2026.
See also: IT & Software Company Accounting Services SaaS Accounting Services (IT & SaaS) Financial Statement Preparation
Statutory Position on STPI / SOFTEX Export Filing
SOFTEX filing arises under the Foreign Exchange Management Act (FEMA) framework governing the export of software. An exporter of software must declare the export value in the SOFTEX form, which STPI (or the SEZ Development Commissioner for SEZ units) certifies, supporting the authorised-dealer bank in monitoring realisation of proceeds. Under the current framework export proceeds must generally be realised within nine months of the date of export. From 1 October 2026, FEMA 23(R)/2026-RB supersedes the 2015 Export of Goods and Services regulations and moves software-export reporting to a monthly Export Declaration Form (EDF); SOFTEX remains operative until 30 September 2026, with AD banks certifying on par with STPI thereafter.
- What is declared — Value of software / IT-services exported electronically, certified by STPI. Law stated as at 22 July 2026.
- Legal basis — FEMA export-of-software framework; realisation generally within 9 months of export.
- Coming change — FEMA 23(R)/2026-RB moves to monthly EDF from 1 October 2026; SOFTEX operative to 30 September 2026.
- Filing — Per-invoice or consolidated monthly SOFTEX to STPI; certified form supports bank realisation tracking.
STPI / SOFTEX Export Filing: A Practical Example
| Particulars | Amount (INR) | Treatment |
|---|---|---|
| Software export invoice (USD 60,000) | 50,00,000 | Booked at invoice-date rate |
| SOFTEX declared value | 50,00,000 | Filed with and certified by STPI |
| Certified form to AD bank | — | Supports realisation tracking |
| Inward remittance received | 50,20,000 | Within 9-month FEMA window |
| Exchange gain on realisation | 20,000 | Booked to P&L |
A Hyderabad software services firm invoices a US client USD 60,000, booked at ₹50,00,000. It files SOFTEX against the invoice; STPI certifies the value and the certified form goes to its bank. When the USD 60,000 is remitted within the nine-month FEMA window, at a slightly better rate, the firm books a ₹20,000 exchange gain. From October 2026 the same firm will report these exports through the monthly EDF regime instead, so it is already updating its process ahead of the switch.
Not filing SOFTEX at all: Skipping the declaration leaves exports unreported under FEMA → file SOFTEX for every software export within the prescribed timeline.
Common Mistakes With STPI / SOFTEX Export Filing
SOFTEX defaults usually surface as unrealised or unreported exports:
- Not filing SOFTEX at all — Skipping the declaration leaves exports unreported under FEMA → file SOFTEX for every software export within the prescribed timeline.
- Value mismatch with invoice — Declaring a SOFTEX value that differs from the invoice invites STPI queries → reconcile SOFTEX to the export invoice and contract.
- Ignoring the realisation window — Letting proceeds run past the nine-month window breaches FEMA → track realisation against each export.
- Not preparing for EDF — Assuming SOFTEX continues past 30 September 2026 misses the change → adopt the monthly EDF process from 1 October 2026.
- Weak export-to-remittance trail — Failing to link invoice, SOFTEX and remittance fails bank and audit checks → maintain a clear linked trail.
STPI / SOFTEX Export Filing is the declaration a software or IT-services exporter files, certified by STPI, to report the value of software exported electronically so the RBI can track realisation of the foreign proceeds. It appears in the books alongside export invoices and bank realisation. It matters because it is the regulatory bridge between an export invoice and inward remittance under FEMA.
Need help with STPI / SOFTEX Export Filing?
STPI / SOFTEX Export Filing sits inside your day-to-day books. Patron's CA-led team keeps them accurate, compliant and audit-ready.
Applicable framework: FEMA export-of-software framework; FEMA 23(R)/2026-RB (SOFTEX to monthly EDF from 1 Oct 2026). For general information only, not professional advice. Verify the current position for your entity before acting.