A SOFTEX form (short for Software Export Declaration) is the mandatory declaration Indian software exporters file with the Reserve Bank of India (RBI), through STPI or the SEZ authority, to report the value of software exported in non-physical form. It is how the RBI confirms that money is due from a foreign client and later matches the payment when it lands in your bank. If you write code, build SaaS, or ship software to clients abroad and get paid in foreign currency, SOFTEX filing usually applies to you.
One timing point matters more than any other right now. As of September 2026, SOFTEX is still live, but it is in its final weeks. Under the RBI's FEMA (Export and Import of Goods and Services) Regulations, 2026 (notified as FEMA 23(R)/2026-RB on 13 January 2026), a single unified Export Declaration Form (EDF) replaces the SOFTEX form for exports made on or after 1 October 2026. So the short answer is: keep filing SOFTEX for your September invoices, and switch to the EDF for October onward. This guide covers both, so you file correctly through the changeover.
What is a SOFTEX form in export compliance?
A SOFTEX form is a post-facto export declaration. You raise an invoice on your foreign client, deliver the software or the service, and then declare that export to the RBI so the transaction enters the country's export-monitoring system. Because software crosses the border as data rather than as a physical shipment, it never passes through a customs port and never generates a shipping bill. SOFTEX is the substitute record that tells the RBI an export has happened and foreign exchange is expected against it.
The declaration does three things at once. It records the export value the RBI expects you to realise. It gives your bank the reference it needs to match the incoming remittance to a specific invoice. And it creates the paper trail that supports a zero-rated GST refund on your export of services. Get it right and the money reconciles quietly. Skip it and the mismatch tends to surface months later, usually when you least want it to.
Is SOFTEX filing mandatory, and who must file?
Yes. For software exports invoiced up to 30 September 2026, SOFTEX filing is mandatory, and there is no minimum-value exemption. Every export invoice is reportable, however small. The old USD 25,000 threshold that once let small exporters skip filing was withdrawn years ago, so a ₹40,000 invoice carries the same obligation as a ₹40 lakh one.
Here is the distinction most guides, and most AI answers, blur. RBI's own SOFTEX facility states that SOFTEX is filed "only in case of export of Software not exported as goods, and it does not include export of services using IT as a tool, i.e. ITeS." In plain terms:
- You file SOFTEX if you export software in non-physical form: custom software development, SaaS products, licensed software, application development, and software consultancy billed as a software export.
- You may not file SOFTEX if your work is pure IT-enabled services (BPO, back-office, transcription, support desks) where technology is only the tool. Those receipts are declared through your AD bank against the invoice and FIRC, not through a SOFTEX form.
The line is genuinely grey for mixed work, for example a firm that both builds a product and runs a managed-support team. If your billing straddles both, confirm the treatment with your bank or a chartered accountant rather than assuming. From 1 October 2026 the question softens anyway, because the EDF brings goods, services, and software under one declaration, so the software-versus-ITeS boundary stops deciding which form you use.
Do freelancers need to file a SOFTEX form?
Often, yes. The obligation follows the nature of the export, not the size of the exporter. An independent developer on Upwork, Fiverr, or a direct contract who ships code to an overseas client and receives foreign currency is exporting software in non-physical form, which puts them in SOFTEX scope, the same as a registered company.
Two practical points make it lighter for solo exporters. First, you file on a monthly bulk basis, so a month of small invoices becomes one consolidated declaration rather than dozens. Second, if you are not inside an STP or SEZ, you complete a one-time STPI registration as a Non-STP unit before you can file. Many freelancers below the GST threshold assume compliance does not apply to them; the RBI's export-monitoring obligation is separate from GST, and it does.
SOFTEX form vs EDF: what changes on 1 October 2026
This is the part to read carefully if you are invoicing across the changeover. The RBI is retiring SOFTEX and folding software exports into a single Export Declaration Form that covers goods, services, and software together. The trigger is the export date, not the filing date, so the rule is simple: exports up to 30 September 2026 stay on SOFTEX, exports from 1 October 2026 move to the EDF.
| Invoice month | Which form applies | Filing route |
|---|---|---|
| September 2026 | SOFTEX (old regime) | STPI or SEZ certification, then AD bank |
| October 2026 | EDF (new regime) | AD bank, STPI, or SEZ |
| November 2026 onward | EDF (new regime) | AD bank, STPI, or SEZ |
Three shifts are worth knowing before the switch. Filing moves from per-invoice or per-transaction declarations to one consolidated monthly EDF, due within 30 days of the end of the invoicing month. Certification opens up: the RBI now recognises AD banks as a "specified authority" for DTA units at par with STPI, so bank certification becomes an option rather than STPI being the only route, though each bank is still finalising how it will process this. And the window to realise export proceeds is extended to 15 months from the invoice date, up from the earlier nine, with a provision to declare "nil" for exports made without payment. For the full mechanics of the new form, see our guide to the export declaration form.
None of this removes the underlying duty. You still declare every export and still reconcile every payment. Only the form, the frequency, and the certifying authority change.
What is a SOFTEX number, and how is it generated?
A SOFTEX number is the unique reference the RBI assigns to your declaration before you submit it. You cannot file a SOFTEX form without one. You request the number through the RBI's SOFTEX facility, quoting your exporter details and the period you are filing for. Bulk filers usually pull a block of numbers for a whole month's invoices at once, so a single request covers the month rather than one number per invoice.
The number is what ties everything together downstream. It appears on the certified declaration STPI or the SEZ authority signs off, it travels to your AD bank, and it becomes the key the bank uses to match your incoming remittance inside the RBI's export system. Treat it as the invoice's compliance ID for the rest of its life.
The reference is structured rather than random, so reading it back is the quickest way to confirm a filing is mapped to the right year and filing office:
SOFTEX number : 2026 KA 00 123456
| | | |
| | | +-- running serial within the block
| | +----- STPI filing-office / batch segment
| +-------- jurisdiction code (KA = Karnataka)
+------------- year the declaration is filedWhat documents do you need to file a SOFTEX form?
Keep these ready before you start; most rejections come from a detail that does not match across documents.
- The commercial export invoice raised on the foreign client, with value and currency.
- The client contract, statement of work, or purchase order describing the software or service.
- Your Importer Exporter Code (IEC), PAN, and GST registration details.
- Your Non-STP or STP/SEZ registration reference.
- The applicable RBI purpose code, commonly P0802 purpose code for software implementation and consultancy receipts.
- Bank and AD-code details for the account that will receive the payment.
Consistency is the quiet requirement here. The value, currency, and description on the SOFTEX form should match the invoice, and the invoice should match what eventually lands in your account, because your bank reconciles all three.
How to file the SOFTEX form for software exporters
The process runs in six steps, whether you file one invoice or a month's worth in bulk. For a field-by-field walkthrough of each step, see the dedicated softex filing guide.
Step 1: Register once
If you are not physically inside an STP or SEZ, complete a one-time Non-STP unit registration with your jurisdictional STPI office. It takes roughly 10 working days and carries a small one-time fee. This is a prerequisite, not a monthly task.
Step 2: Register each export contract
Record the client contract, master service agreement, or purchase order with STPI so your declarations map to an approved export arrangement.
Step 3: Generate the SOFTEX number
Pull the SOFTEX number (or a block of numbers for the month) from the RBI's SOFTEX facility, quoting your details and the filing period.
Step 4: Prepare the declaration
Enter the exporter details, the description of the software or service, the invoice value and currency, the client and country, and the purpose code. Attach the invoice and supporting contract.
Step 5: Submit within the deadline
File through the STPI portal (or the SEZ authority for SEZ units) within the deadline, on a per-invoice or monthly-bulk basis.
Step 6: Get it certified
STPI or the SEZ authority certifies the declaration and forwards it to your AD bank, which uses it to reconcile the remittance and complete the export record.
A filed SOFTEX record reads roughly like this:
SOFTEX No. : 2026KA00123456 Exporter : ExampleSoft Pvt Ltd Invoice : ESPL/2026/0812 dated 08-Aug-2026 Client : Acme Inc, USA Purpose code : P0802 Export value : USD 10,000 = INR 8,50,000 @ 85.00 Period : August 2026
When is the SOFTEX form due?
The deadline is 30 days, and how you count it depends on whether you file per invoice or in a monthly batch. For a single invoice, the clock runs from the invoice date. For monthly bulk filing, it runs from the date of the last invoice in that month.
| Invoice pattern | Filing basis | Due date |
|---|---|---|
| Single invoice raised 8 August | Per invoice | 7 September |
| Several invoices in August, last one on 28 August | Monthly bulk | 27 September |
Most software exporters file monthly. It cuts the admin, keeps a whole month's exports on one declaration, and lines up neatly with how the EDF will work from October, when monthly filing becomes the norm.
What happens if you miss the SOFTEX deadline?
A missed or late SOFTEX filing rarely bites on the day. It surfaces later, as a mismatch in the RBI's Export Data Processing and Monitoring System (EDPMS), the database where every export declaration is meant to meet its matching inward payment. When a remittance arrives with no certified declaration behind it, the entry sits open and unmatched, and three things tend to follow.
Your bank starts chasing you for the paperwork to close the entry, because an open EDPMS item is the bank's problem as well as yours. Your electronic Bank Realisation Certificate (eBRC), the proof that export proceeds were realised, cannot be generated cleanly until the declaration and the payment reconcile. And a missing eBRC or an open EDPMS entry is exactly the kind of gap that stalls a GST refund and can invite RBI follow-ups on unrealised exports. Filing on time is far cheaper than unwinding a backlog of open entries later.
If an entry is already open, the fix is to file the pending SOFTEX declaration, get it certified, and ask your AD bank to match it against the specific remittance so the foreign inward remittance closes in EDPMS. The longer the gap between the payment and the declaration, the more back-and-forth the bank needs, which is the practical reason monthly filing beats a year-end scramble.
SOFTEX and GST refunds for export of services
Software export is a zero-rated supply under GST, which means you can either export under a Letter of Undertaking without paying IGST, or pay it and claim a refund. Either way, you have to prove the export actually happened and the money came in. That proof chain is the SOFTEX declaration, the reconciled EDPMS entry, and the resulting bank realisation certificate.
This is why compliance that looks like pure RBI paperwork also protects your cash flow. A clean SOFTEX trail is what lets your export of services under GST qualify for a refund without the officer questioning whether the receipt is a genuine export. Break the chain, and the refund is where the break shows up.
SOFTEX form vs shipping bill
Both are export declarations, but they cover different kinds of exports and are certified by different authorities.
| Aspect | SOFTEX form | Shipping bill |
|---|---|---|
| Covers | Software exported in non-physical form | Physical goods |
| Trigger | Invoice raised for a software export | Goods cleared at a port |
| Certified by | STPI or SEZ authority | Customs |
| Feeds into | EDPMS via your AD bank | EDPMS via Customs |
If you have ever wondered which applies to a mixed shipment, or how the two reconcile against one payment, our deeper explainer on SOFTEX vs shipping bill walks through the edge cases. From 1 October 2026, both feed into the same unified EDF.
How Xflow helps software exporters stay compliant
The compliance itself, the SOFTEX or EDF filing, is done through STPI, the SEZ authority, and your bank. What tends to break the process is not the form; it is the paperwork around the payment, the FIRA and the purpose code and the reconciliation, arriving late or not matching. That is the part Xflow is built to handle.
Xflow gives Indian software exporters receiving accounts to collect from clients in over 25 currencies, with settlement to your Indian bank on the next business day (T+1). Every inward payment comes with an auto-issued electronic FIRA and the correct purpose code applied, so the documentation your SOFTEX or EDF declaration needs is generated as the money arrives rather than requested weeks later. Xflow holds final Payment Aggregator, Cross Border (PA-CB) authorisation from the RBI for both exports and imports (as of February 2026), and is ISO 27001 and SOC 2 certified, so the flow itself sits inside the regulatory perimeter. On FX, exporters convert at the live mid-market rate and can save up to 50% on FX costs versus a typical bank wire. For the ITeS-specific view, see how Xflow supports IT-enabled services exporters.
Get paid by global clients with compliance handled
The bottom line
For software invoiced up to 30 September 2026, file your SOFTEX form on time, monthly if you can, and keep the value, currency, and description consistent from invoice to declaration to bank credit. From 1 October 2026, switch to the unified EDF: one monthly filing, a 30-day deadline from month-end, bank certification as an option, and a 15-month window to realise proceeds. The obligation to declare every export and reconcile every payment does not change; the form and the routing do. Ask your AD bank now, in September, exactly how it plans to handle your October filings, because the bank-level process is still settling.
For a broader view of how compliance works when you move away from a plain bank wire, read our Xflow compliance guide.
Open a receiving account built for Indian exporters
20
000+ businesses
140+ countries
auto eFIRA
up to 50% FX savings
Frequently asked questions
Yes. For software exported in non-physical form and invoiced up to 30 September 2026, SOFTEX filing is mandatory with no minimum-value exemption. From 1 October 2026, the unified EDF applies instead.
Usually yes. If you export software to overseas clients and receive foreign currency, you are in scope regardless of size. Non-STP freelancers register once with STPI, then file monthly in bulk.
Within 30 days. For a single invoice, count from the invoice date. For monthly bulk filing, count from the last invoice date in that month. Most exporters file monthly.
Often, yes. P0802 covers software implementation and consultancy receipts and is the common code on software-export remittances, though your bank may apply a different code based on the exact service.
If you are not inside an STP or SEZ, yes. You complete a one-time Non-STP unit registration with your jurisdictional STPI office, which takes around 10 working days, before you can file.
A unified Export Declaration Form (EDF) under the RBI's FEMA (Export and Import of Goods and Services) Regulations, 2026, effective 1 October 2026. It covers goods, services, and software in one monthly filing.
Yes, indirectly. A late or missing SOFTEX filing leaves an open EDPMS entry and delays your eBRC, which is the proof of realised export used to support a zero-rated GST refund on export of services.
No. Xflow is your receiving and FX layer, not a filing agent. It issues the eFIRA and applies the correct purpose code as payment arrives, so your STPI, SEZ, or bank filing reconciles cleanly.
SOFTEX stands for Software Export Declaration. It is the RBI declaration Indian exporters file to report software or services sold to overseas clients in non-physical form.
You request it from the RBI's SOFTEX facility with your exporter details and filing period, per invoice or as a monthly block. It must exist before you submit the declaration.
