Unlike a physical shipment, there is no shipping bill showing that the software crossed India's border. For certain software exports, SOFTEX provides the export declaration and value-certification trail used under India's foreign-exchange framework.
Understanding when SOFTEX applies, when to file it, and how it connects with payment realisation can help software exporters avoid gaps between their invoices and export records.
- SOFTEX is a declaration used for eligible exports of software otherwise than in physical form, including relevant off-site software exports.
- RBI requires applicable SOFTEX declarations to be submitted for certification within 30 days from the invoice date or the date of the last invoice raised in a month.
- Both single and bulk SOFTEX filings are permitted, and non-STP units can register with STPI for SOFTEX certification.
- SOFTEX records the export; FIRA/FIRC records receipt of funds, while eBRC is generated separately from inward-remittance data.
What is a SOFTEX form?
SOFTEX is the prescribed export declaration used for applicable exports of computer software and certain audio, video, and television software otherwise than in physical form.
The form records exporter, client, invoice, contract, currency, export-value, software, and AD-bank details. It is an export declaration and valuation record, not a payment receipt.
Who needs to file SOFTEX?
SOFTEX applies to exporters whose software export falls within the relevant RBI declaration requirements.
DGFT's current eBRC guidance covers software and software-related services under the SOFTEX process. The exact treatment still depends on the service and purpose code; not every service performed by an IT company is automatically a SOFTEX transaction.
For services to which no prescribed export declaration form applies, RBI permits export without a declaration, subject to the applicable foreign-exchange realisation and repatriation rules.
Do non-STP companies need SOFTEX?
Non-STP units can register with STPI specifically for SOFTEX certification. STPI currently provides a separate registration process for companies seeking SOFTEX certification without operating as an STP unit.
When should SOFTEX be filed?
For applicable software exports, RBI requires the SOFTEX declaration to be submitted to the designated authority not later than 30 days from:
- the invoice date, or
- the date of the last invoice raised in a month, where invoices are being combined.
For long-duration contracts, RBI expects periodic invoicing—at least monthly or at milestones—with the final invoice no later than 15 days after completion. For a one-shot transmission, the invoice should generally be raised within 15 days.
Can multiple invoices be filed in one SOFTEX?
Yes.
RBI permits single and bulk SOFTEX declarations, and its bulk-filing facility applies to all software exporters. Multiple invoices for the same overseas client can also be combined where the conditions are met.
How do you file SOFTEX?
The exact process can vary by STPI centre or scheme, but the broad workflow is:
Register with the relevant authority → obtain/generate SOFTEX number → add contract and bank details → upload invoice-level export data → upload supporting documents → submit for certification
STPI's current workflow requires invoice and contract information. Non-STP exporters generally register with the relevant STPI centre first.
What documents are required for SOFTEX filing?
Commonly requested documents include:
- export invoice
- agreement, purchase order, work order, or statement of work
- SOFTEX form or bulk statement
- contract/project reference
- supporting export details
- IEC details where applicable
- datacom/service-provider information where requested
- other documents required by the designated STPI/SEZ authority
A FIRC/FIRA is not necessarily required before filing. STPI's checklist says to attach FIRC copies if the export amount has already been realised.
SOFTEX vs FIRA/FIRC vs eBRC
These documents record different parts of the export lifecycle.
| Document | What it records |
|---|---|
| SOFTEX | Declaration/certification of applicable software export value |
| FIRA/FIRC | Evidence/advice relating to inward foreign remittance |
| IRM | Bank-reported inward remittance information used in DGFT workflows |
| eBRC | Electronic Bank Realisation Certificate evidencing export proceeds |
Under DGFT's current self-certification system, exporters generate service eBRCs using IRM data reported by banks. For SOFTEX-related IT exports, DGFT uses purpose code P0807 – Off-site Software Exports.
How long do software exporters have to realise payment?
SOFTEX filing and payment realisation have separate timelines.
RBI's current Master Direction requires export proceeds for goods, software, and services to generally be realised and repatriated to India within nine months from the date of export, unless an applicable extension or exception applies.
If payment is delayed, exporters should work with their Authorised Dealer bank on the applicable extension or regularisation process.
Common SOFTEX filing mistakes
Avoid:
- filing after the 30-day timeline without addressing the delay
- assuming every IT service is automatically a SOFTEX export
- using invoice details that do not match the contract
- omitting the relevant SOFTEX number from follow-up records
- treating FIRA/FIRC as the same document as SOFTEX
- assuming SOFTEX certification itself proves export proceeds were realised
The cleanest process is to keep the contract → invoice → SOFTEX → inward remittance → eBRC trail connected.
How PayGlocal supports software exporters
PayGlocal does not replace the SOFTEX filing or certification process.
Its Multi-Currency Accounts help Indian SaaS, IT, and service exporters collect international payments in 130+ global currencies from 180+ countries, settle in INR, track payments, and receive automated FIRA.




