SOFTEX Filing for Software explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
SOFTEX is the declaration filed for software and specified service exports transmitted through data communication links, where no physical shipment and therefore no shipping bill exists. It is certified by STPI or the SEZ authority and is what allows the inward remittance to be matched and an e-BRC issued.
The Gap SOFTEX Fills
When goods are exported, the shipping bill is the declaration to the authorities that an export has occurred. It carries the value, feeds EDPMS, and is what the bank matches the inward remittance against.
Software delivered over a network produces no shipping bill. Without a substitute, there would be nothing in the system recording that an export happened, no way to match the dollars arriving in the exporter's account to an underlying export, and no basis for an e-BRC.
SOFTEX is that substitute. It is the declaration for software exports and for services transmitted through data communication links, and it performs precisely the function a shipping bill performs for goods.
Who Files, and Who Certifies
| Exporter type | Certifying authority |
|---|---|
| STP unit | Software Technology Parks of India, the jurisdictional STPI office |
| Non-STP software exporter | STPI, after registering as a non-STP unit |
| SEZ unit | The specified officer of the SEZ |
| EOU | The jurisdictional authority for that unit |
A non-STP exporter — an independent software company with no STP registration — generally needs to register with STPI as a non-STP unit before its SOFTEX forms can be certified. The registration itself is light, but it must exist before the first filing, and this catches new exporters who discover it only when the bank asks for a certified form.
The Filing Flow
- Raise the invoice on the overseas client for the software or services delivered.
- Prepare the SOFTEX declaration with the export details — client, contract, invoice, value, currency and period.
- Submit to the designated authority for certification, with the supporting invoices and contract or purchase order.
- Certification is granted and the form is transmitted to the banking system.
- The AD bank records the declaration in EDPMS as an outstanding export.
- The remittance arrives and the bank matches it to the declaration.
- The entry closes and an e-BRC is issued.
Bulk Filing
A software exporter may raise dozens of invoices a month across several clients. Filing a separate SOFTEX for each would be unworkable, so a single bulk SOFTEX covering all invoices for a month is permitted, which is how most regular exporters operate.
Because the format, periodicity and submission mode have been modernised over time — including movement to electronic submission — confirm the current requirement with your jurisdictional authority rather than continuing a legacy process. The substance has not changed; the mechanics have.
Why It Matters Beyond Compliance
Exporters sometimes treat SOFTEX as a formality until something downstream breaks. The consequences of not filing, or filing late, are concrete:
- EDPMS entries stay open. The remittance arrives with no declaration to match it against, and eventually appears as an unreconciled item.
- No clean e-BRC. Which blocks Foreign Trade Policy scheme claims and complicates GST refund substantiation.
- Realisation timelines. The obligation to realise proceeds within the prescribed period runs on the export, and without a declaration the position cannot be demonstrated.
- Audit and diligence. A software exporter with a history of unfiled SOFTEX forms carries a live regulatory exposure that surfaces in due diligence.
How It Interacts with GST
SOFTEX and GST are separate regimes but they describe the same transactions, and they should agree.
- Export of services under GST requires the five conditions in Section 2(6) of the IGST Act to be met, including receipt of payment in convertible foreign exchange.
- The FIRC or e-BRC is the primary evidence of that receipt for a refund claim.
- The e-BRC depends on the SOFTEX declaration being filed and matched.
So an unfiled SOFTEX eventually shows up as a GST refund problem, which is how many exporters first discover the issue.
Documentation to Maintain
- Master service agreement or contract with each overseas client
- Purchase orders or statements of work
- Invoices, numbered consistently with what is declared
- SOFTEX forms with certification evidence, filed by month
- FIRCs and e-BRCs, mapped to invoices
- EDPMS statement from the AD bank with your reconciliation
- Registration certificate with STPI or the relevant authority
Practical Tips
- Register with the designated authority before the first export, not when the bank asks.
- Move to bulk monthly filing as soon as volumes justify it, and set a fixed date in the month for it.
- Use one invoice numbering convention across the invoice, the SOFTEX and your GST return; mismatches here cause the same reconciliation pain as SB005 does for goods.
- Reconcile SOFTEX filed, remittances received and e-BRCs issued every month, not annually.
- Where a client pays a net amount after withholding foreign tax, document the withholding so the shortfall does not sit as an unexplained gap in EDPMS.
- If historic filings were missed, regularise them deliberately with the authority and the bank rather than hoping the entries age out.