SOFTEX Filing: How to File the SOFTEX Form, Step by Step

SOFTEX filing is the process of declaring a software or IT-services export to the Reserve Bank of India (RBI), so your foreign earnings are recorded and can be realised against the payment that reaches your bank.

You file the software export declaration within 30 days of the invoice, and because the declaration is what lets your bank close the export record, missing it usually stalls everything downstream.

One change to note up front: as of July 2026, the RBI is folding SOFTEX into a single Export Declaration Form, with full transition by 1 October 2026.

This guide covers who files, the deadline, the step-by-step process, the documents, the penalties, and what the 2026 transition means for a software or ITeS exporter.

• SOFTEX filing declares your software or IT-services export to the RBI, historically through Software Technology Parks of India (STPI), so the export is recorded and can be realised.
• File within 30 days of the invoice date, or within 30 days of the month's last invoice if you consolidate monthly.
• Both registered STP-scheme units and non-STP exporters file. Freelancers and small SaaS firms are not exempt if they receive foreign remittance.
• There is no value threshold: an old USD 25,000 floor was removed in 2013, so software and ITeS exports are reportable regardless of ticket size (as of July 2026).
• The RBI's Export and Import of Goods and Services Regulations, 2026 replace SOFTEX with a unified Export Declaration Form (EDF) and let AD-1 banks certify exports alongside STPI, with full transition by 1 October 2026.
• Missing the filing can attract a penalty of up to three times the sum involved under Section 13(1) of FEMA, plus a continuing daily penalty.

The RBI's Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 are consolidating the older reporting forms into a single export declaration form that covers goods, services and software together.

The transition period runs to 1 October 2026, after which the unified process applies (as of July 2026).

Two things matter for a software exporter. First, an Authorised Dealer Category-1 (AD-1) bank is now recognised as a "Specified Authority" on par with STPI, so STPI certification is no longer the only route.

Second, the shift confirms the move to monthly consolidated filing rather than per-transaction declarations.

The practical steps below still describe the SOFTEX system as most exporters have filed it, and they remain the closest reference for the transition period.

If you are setting up compliance today, confirm with your bank or your STPI software exports centre which route to file under, and treat this as educational material, not tax or legal advice.

SOFTEX filing means submitting the software export declaration form for every export of software or IT-enabled services, so the value you exported is recorded against the payment that later lands in your bank. In practice it works like any other export declartion form, recording what left the country so it can be reconciled against payment.

It exists because software and services leave no shipping bill, unlike physical goods. The declaration is how the RBI tracks that an export happened and that the money came back.

For the form itself, its fields and history, see the SOFTEX form explainer. This page focuses on the procedure and the current transition.

If you are based in India, export software or IT-enabled services, and receive payment from a client outside India, you file SOFTEX. That covers a wide range of exporters handling international payments for IT ITeS.

The common misconception is that SOFTEX is "only for large IT companies" or "only for units inside an STP or SEZ". It is not.

A freelancer working solo from home files through the same route as a 500-person firm, just as a non-STP unit.

If foreign currency reaches your account for software or ITeS work, the declaration applies.

No. An earlier RBI notification set a USD 25,000 floor, but a September 2013 circular removed it, so software and ITeS exports are reportable regardless of invoice size (as of July 2026).

A small SaaS firm invoicing a US client USD 8,000 files just as a firm invoicing USD 800,000 does.

Worked example: you raise a USD 8,000 invoice to an overseas client. At an illustrative rate of ₹95 to the dollar, that is roughly ₹7.6 lakh of export value to declare and then realise.

Even though it sits well below the old USD 25,000 mark, the declaration still applies, and the payment must still be realised within the period the RBI allows.

File the SOFTEX form within 30 days of the invoice date. When you raise several export invoices in a month, you can consolidate them into a single filing submitted within 30 days from the date of the month's last invoice.

Do not treat the deadline as soft. The declaration is what lets your AD-1 bank match the invoice to the inward payment and close the export record.

File late and the record stays open, which is where downstream problems start.

Filing is also only step one; the payment still has to complete its realisation of export proceeds within the permitted period (generally nine months from the date of export, as of July 2026; confirm the current limit with your bank).

The core sequence is the same whether you are an STP-scheme unit or a non-STP exporter. The difference is the one-time registration step at the start.

Under the 2026 regulations, step 4 can run through an AD-1 bank as an alternative to STPI, since the bank now qualifies as a Specified Authority.

Keep these ready before you start, so the details you enter match your records.

An accurate export invoice matters most here, because the value and client on the form must match it exactly, or certification stalls.

If you also bill domestic clients, keep your export of services under GST records aligned with what you declare, since the zero-rated treatment leans on the same paper trail.

Non-STP exporters, which is most freelancers, agencies and SaaS firms outside an STP or SEZ, take one extra step first.

You register as a non-STP unit with your jurisdictional STPI centre, submitting the application, documents and the applicable fee. Registration usually takes around 10 working days.

Once registered, you file exactly like an STP unit: prepare the form per invoice, submit on the portal, get it certified, and route it to your AD-1 bank.

Freelancers should also confirm the right purpose code for freelancers before filing, since the purpose code on the declaration must line up with the one your bank uses on the inward payment.

Not filing contravenes the Foreign Exchange Management (Export of Goods and Services) Regulations under FEMA, 1999.

Under Section 13(1), the penalty can run up to three times the sum involved where that amount is quantifiable, and a continuing contravention can attract a further daily penalty.

Where the delay is for genuine reasons, the certifying authority can condone it, subject to conditions.

Beyond the fine, the practical cost bites first: an open export record, a bank that cannot close the transaction, and a held-up FIRC for GST refund until the filing is regularised.

For a services exporter on thin working capital, that is real money stuck.

SOFTEX rarely sits on its own. It feeds a chain that keeps your export inflows clean, and each link depends on the one before it.

• EDPMS: your certified declaration and the realised payment close the entry in the RBI's monitoring system, which is the point of good EDPMS compliance.
• FIRA / FIRC: when the payment lands, your bank issues a remittance advice; read how the FIRA documents your inward remittance.
• eBRC: for many incentives and refunds, an electronic bank realisation certificate is your proof of realisation, and it helps to know the BRC vs FIRC distinction before you claim.

File on time and the rest of the chain flows. Skip it and every downstream step stalls.

• Assuming you are exempt: freelancers and non-STP units file too. When in doubt, register and file.
• Missing the 30-day window: set a monthly reminder tied to your invoice cycle rather than filing ad hoc.
• Mismatched details: the invoice value, client name and description on the form must match your records and your bank's.
• Confusing it with a goods declaration: software and services use SOFTEX, not a shipping bill; see SOFTEX vs shipping bill if you handle both.
• Filing but not tracking realisation: the form is step one; the payment still has to be realised and reconciled within the permitted period.
• Ignoring the 2026 transition: confirm whether you should file under the retired SOFTEX system or the new EDF process before your next cycle.

The filing is only half the job. The other half is getting paid, at a fair rate, with the paperwork that keeps your compliance chain moving.

Xflow is built for receiving money from abroad into India, so it fits the export-proceeds side of this workflow rather than the declaration itself.

You receive cross-border payments into a Receiving Account, a routing account issued by the banking partner, converted to INR at the live mid-market rate with settlement on the next business day (T+1).

Xflow auto-issues the eFIRA for each inflow, so the remittance advice your bank and chartered accountant need is generated for you, and your downstream receive international payments workflow stays intact.

Your SOFTEX, EDPMS and reconciliation steps run as before, with the documentation handled in the background.

Xflow holds final RBI Payment Aggregator - Cross Border (PA-CB) authorisation for both exports and imports (as of February 2026) and is ISO 27001 and SOC 2 certified.

The aim is relief, not extra work: get paid faster and at a fairer rate, and let the routine paperwork take care of itself so you can file on time without the scramble.

This article is educational and is not tax, legal or financial advice. Regulations change, and the 2026 transition is still rolling out, so confirm current rules with your AD-1 bank, your STPI centre, a chartered accountant, or the RBI before you file.