What is a SOFTEX Form? Filing Process for Software Service Exports in India

If you export software or IT services from India and get paid in foreign currency, the money is only half the job. The Reserve Bank of India (RBI) also wants a record that the export happened and that the payment came home.

That record is the SOFTEX form. Miss it or file it late and you invite bank follow-ups, EDPMS mismatches, and questions on your GST refund.

One thing has changed, and most guides have not caught up: from 1 October 2026, a new unified Export Declaration Form (EDF) replaces the SOFTEX form.

This guide covers how SOFTEX works today, how to file it in time, and what the switch to EDF means for software exporters.

Xflow builds receiving accounts for exactly this segment, so the paperwork angle matters to us as much as the payout.

A SOFTEX form (short for Software Export Declaration) is a mandatory RBI declaration that Indian software and IT/ITeS exporters file to report foreign-currency earnings from software and service exports.

It exists under the Foreign Exchange Management Act (FEMA) so the RBI can match each export invoice against the payment that lands in your bank, closing the loop on realisation of export proceeds.

In plain terms: the shipping bill records physical goods leaving a port. Software has no port, so SOFTEX is the digital equivalent.

It certifies that the foreign money you received is genuine export revenue, not an unexplained inflow. That certification is what later supports your bank realisation certificate and your zero-rated export status for GST.

SOFTEX is filed with the Software Technology Parks of India (STPI), certified there, and passed to your Authorised Dealer (AD) bank, which feeds it into the RBI’s Export Data Processing and Monitoring System (EDPMS). A certified SOFTEX does three jobs:

• Confirms your foreign receipt is genuine export revenue, not an unexplained inflow
• Closes the export against its incoming payment in EDPMS
• Backs your bank realisation record and your zero-rated GST refund

SOFTEX applies to businesses exporting software or IT-enabled services, whether they sit inside an STPI or Special Economic Zone (SEZ) or operate as a Domestic Tariff Area (DTA) unit. The three common cases:

• STPI units: registered inside a Software Technology Park, with SOFTEX built into the standard STPI compliance workflow.
• SEZ units: software exporters in a Special Economic Zone, certified by the SEZ Development Commissioner.
• Non-STPI (DTA) units: companies, LLPs, and IT-enabled services firms outside an STPI who still export software. They must take a one-time Non-STPI registration before they can file.

This is the most common source of confusion, and the honest answer is: it depends on what you export and how your bank treats the inflow.

SOFTEX is meant for software and IT/ITeS exports, so a solo developer shipping software work abroad can fall within its scope.

In practice, many small independent contractors receiving service fees under a purpose code such as P0802 are not asked to file, and enforcement varies by bank and by size.

Because the line is genuinely grey, confirm your position with a chartered accountant rather than assuming. This is guidance, not tax advice.

Before you file, you generate a SOFTEX number: a unique reference the RBI system issues that identifies each declaration. You request it through the RBI’s SOFTEX facility (accessed via the EDF/SOFTEX portal), quoting your exporter details and the relevant period.

Bulk filers pull a block of numbers for a month’s invoices in one go. The number ties your invoice, your declaration, and your bank realisation together, so it has to be generated before the form is submitted, not after.

A single declaration ties together five things:

• The SOFTEX number issued by the portal
• The export invoice number and date (export invoice details must match exactly)
• The overseas client name and country
• The purpose code for the receipt
• The export value in foreign currency and its INR equivalent

Here is how those fields line up on a sample filing (illustrative values, not a live number):

Missing paperwork is the second-most-common reason a filing stalls, so keep these ready before you start:

• The export invoice raised on the overseas client
• The master service agreement or purchase order behind the invoice
• Your Non-STPI or STPI registration details (for DTA units, the one-time registration must already be in place)
• The agreement/contract registration number from your STPI centre
• Your digital signature certificate on a working USB token
• The foreign inward remittance advice or bank credit reference for the payment received

The filing runs in a set sequence. Skipping a step is the usual reason a submission stalls.

Step 1: Register once

Register once. STPI and SEZ units are registered by default. DTA exporters complete a one-time Non-STPI registration, which takes around 10 working days (STPI software exports registration is a prerequisite, not a formality).

Step 2: Register each export contract

Register each export contract. Log your master service agreement or purchase order with your STPI centre before you file against it.

Step 3: Generate the SOFTEX number

Generate the SOFTEX number for the invoice or the month’s batch.

Step 4: Prepare the declaration

Prepare the declaration with invoice details, client name, purpose code, and the software or service description.

Step 5: Submit within the deadline

Submit within the deadline (covered below), signed with your digital signature certificate.

Step 6: Get it certified

Get it certified by STPI or SEZ, after which it moves to your AD bank and into EDPMS.

Filing is fully online through the STPI e-filing portal. The frequent snag is technical, not procedural: submission needs a valid digital signature certificate on a USB token, and an expired or wrongly configured certificate is the most common reason the final "Submit" step fails.

The SOFTEX form is due within 30 days of raising the export invoice.

If you use the bulk (monthly) facility, the deadline is 30 days from the date of the last invoice raised in that month, which is why most exporters treat it as a month-end task.

A worked example makes the timing concrete:

Late filing is the single biggest trigger for EDPMS entries staying open, which then holds up your realisation record and can stall your FIRC for GST refund.

There is no fixed penalty schedule for a single late SOFTEX, but the knock-on effects are real and they compound:

• The matching EDPMS entry stays open, so the RBI system shows an export without a closed realisation.
• Your bank raises follow-up queries and may withhold the bank realisation certificate explained, which you need downstream.
• Your GST refund on zero-rated exports can be held until the export is evidenced as realised.
• Repeated defaults can invite scrutiny from the RBI or your AD bank under FEMA.

A worked example shows how quickly it bites: an invoice of USD 10,000 (about ₹8,50,000) raised on 8 August is due by 7 September.

File it on 20 September and that EDPMS entry sits unmatched for the gap, which is exactly the mismatch a bank flags during year-end reconciliation in March, the busiest compliance window for software exporters.

Software exporters often ask why they file SOFTEX when goods exporters file a shipping bill. They serve the same purpose for different exports:

For the fuller breakdown, see softex vs shipping bill.

SOFTEX and your GST filing are separate obligations that lean on each other. SOFTEX is the FEMA record of the export; your GST return reports the same export for tax.

When you claim a refund on zero-rated export of services under GST, the department cross-checks that the foreign payment was realised, and a certified SOFTEX plus your foreign inward remittance certificate is what evidences it.

File SOFTEX cleanly and the GST refund step gets easier; skip it and the refund is where the gap shows up.

This is the part most exporters have not registered yet.

Under RBI’s Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 (Notification FEMA 23(R)/2026-RB dated 13 January 2026, with A.P. (DIR Series) Circular No. 20 dated 16 January 2026), the SOFTEX form is being retired.

From 1 October 2026, a single export declartion form (EDF) covers goods, services, and software together. The practical shifts, as of July 2026:

• Software becomes a "service" for reporting, folded into one declaration type instead of its own form.
• One EDF per month: for services and software you file a single consolidated EDF within 30 days of the month-end, rather than transaction-level SOFTEX declarations.
• Banks can certify. AD banks are recognised as a "Specified Authority" at par with STPI for DTA units, so STPI certification becomes optional rather than mandatory for those exporters.
• Realisation timelines stay at 15 months from the invoice date for services, extended to 18 months for exports invoiced in INR.

Until 1 October 2026 you continue with SOFTEX as usual, and the sensible move now is to keep filing on time, watch for your bank’s EDF process, and confirm the effective date on rbi.org.in, since regulatory dates can shift.

Xflow does not file your SOFTEX or EDF for you, and any guide that implies otherwise is overselling. What Xflow does is remove the documentation friction around it.

When your international clients pay into an Xflow receiving account, you get an auto-issued electronic Foreign Inward Remittance Advice (eFIRA), correct purpose-code tagging, and clean transaction statements.

That is the exact evidence trail STPI, your AD bank, and your GST filing need, so reconciliation and xflow compliance stop being a month-end scramble.

Xflow settles collections at live mid-market rates on a next-business-day (T+1) basis. Its invoicing tool captures invoice data and syncs with Zoho Books and Tally, so nothing is re-keyed at reconciliation.

As an RBI-authorised Payment Aggregator - Cross Border (PA-CB) for both exports and imports (final authorisation, February 2026), the compliance posture is built in rather than bolted on.

It handles the payment and the paper trail; you (or your CA) still lodge the declaration.

SOFTEX is the RBI’s proof that your software export earnings are real and realised. File within 30 days, generate the number first, and keep your invoice, purpose code, and bank record aligned.

Then plan for the 1 October 2026 switch to a unified EDF, which simplifies filing to one monthly declaration and lets your bank certify it. Get the documentation right at the point of payment and the compliance follows.