RBI EDF for Export of Services 2026 | FEMA Guide
RBI EDF for Export of Services from 1 October 2026: FEMA Compliance Guide for Indian Service Exporters
From 1 October 2026, India's FEMA framework introduces a significant reporting change for businesses and professionals exporting services from India. Exporters of services must furnish an Export Declaration Form (EDF) declaring the full export value of their services.
The change is important for Indian freelancers, consultants, IT and software companies, agencies, professional firms, startups and other businesses billing customers outside India.
The new requirement arises under the Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, notified by the Reserve Bank of India (RBI) on 13 January 2026 and effective from 1 October 2026. The framework was subsequently amended on 22 September 2026, including a reduction in the export-realisation period before commencement.
Key Takeaways
EDF reporting for export of services applies from 1 October 2026.
The requirement covers services, including software, under the 2026 FEMA framework.
The normal EDF deadline is within 30 days from the end of the month in which the service invoice is raised.
A single EDF may cover all service exports to one or more recipients during a month.
For services other than software, the exporter may alternatively furnish the EDF on or before receipt of payment.
For a Domestic Tariff Area exporter, the EDF is generally furnished to the Authorised Dealer (AD) bank. Software exporters may also use STPI in the circumstances specified by the Regulations.
The AD bank enters service-export EDF details into EDPMS, generally within five working days of receiving the EDF.
Export proceeds for services must ordinarily be realised and repatriated within 9 months from the invoice date. The period becomes 12 months where the export is invoiced and/or settled in Indian Rupees, subject to the precise application of Regulation 5.
The EDF is a FEMA/foreign-exchange declaration, not a GST return.
A foreign remittance is not automatically an export of services. The underlying transaction must first be examined under the applicable FEMA and, separately, GST framework.
1. What changed from 1 October 2026?
The 2026 Regulations replace the earlier FEMA export framework with a consolidated regime covering exports and imports of goods and services.
One of the most important changes is the expansion of the EDF framework to service exports.
Under the previous regime, the EDF was principally associated with goods exports, while software exports were subject to the SOFTEX mechanism and services for which no prescribed declaration form applied could generally be exported without furnishing an export declaration.
The 2026 framework removes that gap. Regulation 3(2) requires an exporter of services to furnish an EDF declaring the full export value of services. The Regulations also expressly provide that, for this purpose, services include software.
The practical effect is a move towards a common FEMA reporting trail for goods, software and other service exports.
2. What is an Export Declaration Form (EDF)?
An Export Declaration Form is a FEMA declaration containing details of an export transaction and the amount representing its full export value.
It is not:
a GST return;
an income-tax return;
an invoice;
a foreign-remittance form by itself; or
a substitute for GST export reporting.
The EDF connects the underlying export transaction with the foreign-exchange realisation that is subsequently monitored through the banking system.
The statutory framework is rooted in Section 7 of FEMA, 1999, which deals with export of goods and services, together with Section 8 concerning realisation and repatriation of foreign exchange.
3. Why has EDF become relevant for service exporters?
The policy shift is essentially one of declaration, monitoring and reconciliation.
Once a service export is declared, the transaction can be recorded and monitored through the RBI's Export Data Processing and Monitoring System (EDPMS). The AD bank is responsible for entering service-export EDF information into EDPMS and following up outstanding entries.
This means a service exporter should no longer view an overseas receipt simply as a bank-credit event.
The exporter should be able to connect:
Contract → Invoice → EDF → EDPMS entry → Inward remittance → Realisation/closure
That reconciliation becomes particularly important where an exporter has many invoices, multiple overseas customers, payment intermediaries, deductions, credit notes or delayed collections.
4. What constitutes export of services under FEMA?
Before filing an EDF, the underlying transaction must first qualify as an export of services.
Under FEMA, the concept broadly concerns the provision of services from India to a person outside India. Therefore, receiving money from a foreign source is not by itself sufficient to establish that an export of services has occurred.
The commercial substance matters.
Examples that can ordinarily present a conventional service-export relationship include:
an Indian consultant providing consulting services to a US company;
an Indian designer providing design services to a UK client;
an Indian software developer undertaking development work for an overseas customer;
an Indian professional firm providing accounting, legal or advisory services to an eligible overseas recipient; or
an Indian agency providing contracted marketing services to a foreign business.
More complex receipts—such as platform income, advertising revenue, royalties, commissions, marketplace settlements or creator income—should not automatically be classified as service exports merely because the payer is located outside India.
The contract, recipient, nature of supply, invoicing arrangement, payment flow and applicable law should be reviewed before making that classification.
5. FEMA export of services vs GST export of services
This distinction is critical.
FEMA and GST are separate legal frameworks.
For GST purposes, Section 2(6) of the IGST Act contains its own conditions for an "export of services", including requirements concerning the location of the supplier, location of the recipient, place of supply, receipt of consideration and the relationship between the parties.
Accordingly:
A transaction can require separate analysis under FEMA and GST; satisfying one framework does not automatically establish compliance with the other.
The EDF is therefore not a GST return.
GST compliance may separately involve invoices, GSTR reporting, LUT/bond or payment of IGST and refund procedures, depending on the circumstances. The FEMA EDF should be treated as a separate foreign-exchange compliance requirement.
6. Who needs to comply?
Regulation 3(2) applies to an exporter of services without prescribing a turnover threshold or an exemption merely because the exporter is an individual or small business.
The framework can therefore cover:
Freelancers and individual professionals
A freelancer providing software development, design, writing, consulting, engineering or other professional services to an overseas customer should review the EDF requirement.
The fact that the exporter is a sole proprietor or individual does not, by itself, remove the FEMA reporting obligation.
IT and software companies
Software is expressly included within "services" for the 2026 Regulations. The new framework therefore brings software exports into the EDF system.
Consultants and professional firms
Management consultants, accountants, lawyers, engineers, architects and other professional-service businesses providing eligible services to overseas recipients should examine their monthly invoicing process and AD-bank reporting arrangements.
Marketing, design and digital agencies
Agencies providing contracted services to overseas business customers should similarly incorporate EDF preparation into their monthly export-compliance process.
7. When must the EDF be submitted?
The principal rule is:
Within 30 days from the end of the month in which the invoice for services is raised.
For example:
Invoice month | Normal EDF deadline |
October 2026 | 30 November 2026 |
November 2026 | 30 December 2026 |
December 2026 | 30 January 2027 |
The deadline is linked to the month of invoice, rather than simply the date on which payment is received.
Can one EDF cover multiple invoices?
Yes.
An exporter that exports services to one or more recipients during a month may submit a single EDF covering all those exports.
This is an important practical simplification for freelancers and businesses issuing numerous monthly invoices.
Alternative timing for non-software services
For services other than software, Regulation 3(2)(b) provides an additional option: the exporter may furnish the EDF on or before the date of receipt of payment.
Because this provision operates alongside the general 30-day rule, exporters should establish a consistent procedure with their AD bank rather than assuming that payment-date filing is always the preferred approach. The bank's documented SOP should be checked for implementation details.
Extension for delay
An AD may extend the EDF submission period when the exporter requests an extension, cites the reasons for delay and the AD is satisfied that the reasons are reasonable.
An extension should therefore be treated as an exception requiring justification—not as an automatic grace period.
8. Where and how is the EDF submitted?
The 2026 Regulations define the relevant "specified authority".
Export category | Domestic Tariff Area | SEZ |
Services other than software | Authorised Dealer | Development Commissioner of the SEZ |
Software | Authorised Dealer or STPI | Development Commissioner of the SEZ |
Where the specified authority is not the AD, the authenticated EDF is required to be forwarded to the relevant AD.
For a typical Indian freelancer or service company operating in the Domestic Tariff Area, the practical starting point is therefore the AD bank through which the export proceeds are handled.
The Regulations do not make the exporter personally responsible for entering the transaction into EDPMS.
9. Role of the Authorised Dealer bank
The AD bank is central to the new compliance cycle.
Among other responsibilities, the AD:
receives or obtains the EDF;
satisfies itself regarding the genuineness of the transaction;
enters service-export EDF details into EDPMS;
monitors outstanding export entries;
follows up with exporters where documents are required;
credits or updates the export entry when proceeds are received; and
handles permitted extensions, reductions, third-party receipts and other matters within its delegated powers and internal SOP.
The 2026 Directions require an AD to enter service EDF details into EDPMS within five working days of receipt.
Banks are also required to maintain documented internal policies and SOPs covering matters such as documents, timelines, charges, extensions and export-value adjustments.
10. EDPMS monitoring
EDPMS stands for Export Data Processing and Monitoring System.
Under the new framework, service exports become part of the EDPMS monitoring trail.
The AD is required to enter service-export EDF information into EDPMS within five working days and to monitor transactions for closure of outstanding entries.
For export invoices/shipping bills up to ₹10 lakh or equivalent foreign currency, the Regulations provide a simplified closure mechanism based on an exporter declaration that payment has been realised, either fully or otherwise. Such declarations may also be submitted quarterly for bulk closure.
This does not mean that invoices below ₹10 lakh are exempt from EDF filing. The ₹10 lakh provision concerns EDPMS closure, not a blanket exemption from the service-export declaration requirement.
11. Export proceeds realisation and repatriation: the latest 2026 position
This is the area where older January 2026 articles can now be misleading.
The January 2026 Regulations originally prescribed a 15-month period for ordinary exports and an 18-month period for exports invoiced and/or settled in Indian Rupees.
However, RBI amended Regulation 5 on 22 September 2026, before the Regulations came into force.
The amendment substituted:
15 months → 9 months, and
18 months → 12 months.
The amendment takes effect from 1 October 2026.
For service exporters, the practical position is therefore:
Transaction | Applicable period from 1 Oct 2026 |
Services – ordinary case | 9 months from invoice date |
Services invoiced and/or settled in INR, where the INR proviso applies | 12 months from invoice date |
Goods – ordinary exports | 9 months from shipment |
Goods exported to overseas warehouse | 9 months from sale from warehouse |
Project exports | According to applicable contractual terms |
The distinction between goods and services is important because the starting point differs: shipment for ordinary goods versus invoice date for services.
An AD may extend the realisation period on a reasoned request where it is satisfied with the reasons for delay.
12. Software exports and the transition from SOFTEX
Software exporters should pay particular attention to the transition.
Under the earlier framework, software exports were associated with SOFTEX reporting. The 2026 Regulations instead treat software as services for the purpose of the new framework and include software exports within the EDF regime.
For a Domestic Tariff Area software exporter, the specified authority may be the AD or STPI.
The change therefore should not be interpreted as merely renaming SOFTEX. It is part of a wider move towards a common export-declaration framework.
Businesses that previously maintained separate SOFTEX processes should update their ERP, invoicing, banking and compliance workflows accordingly.
13. Goods vs services: a brief distinction
The EDF is now relevant to both goods and services, but the mechanics differ.
For goods exported through an EDI port, the EDF is deemed to be submitted as part of the shipping bill.
For services, there is no Customs shipping bill equivalent. The service exporter therefore submits the EDF to the specified authority within the prescribed period.
This is why an ordinary service exporter should not assume that Customs/ICEGATE will automatically create the required FEMA declaration for its service invoices.
14. Special cases and transaction-specific issues
The 2026 framework also contains provisions dealing with matters such as:
third-party receipts;
advance receipts;
reduction in export value;
set-off of export receivables against eligible import payables;
delayed realisation;
project exports; and
exporters on the caution list.
Third-party payment, for example, should not be treated as an informal arrangement. The AD must be satisfied about the transaction and its bona fides before permitting the relevant receipt/payment.
Similarly, exporters who were already on the RBI Caution List as of 30 September 2026 remain governed by the relevant existing RBI order until they are removed from that list.
These provisions are fact-specific and should be reviewed with the AD bank where applicable.
15. Documents and information exporters should maintain
A service exporter should maintain a clear documentary trail, including, as applicable:
executed contract, engagement letter or purchase order;
customer details and country;
invoices;
description and nature of services;
invoice currency and value;
contract references;
EDF copies/acknowledgements;
bank inward-remittance records;
EDPMS references and closure evidence;
credit notes or revised invoices;
evidence supporting deductions or short realisation;
third-party payment documentation, where applicable;
correspondence concerning delayed payment;
relevant GST export documentation; and
supporting records for the accounting entry.
The EDF itself contains information concerning the exporter, AD details, recipient information, invoice details, currency/value and service particulars.
16. Practical monthly compliance checklist
For a typical service exporter, the following workflow is practical:
Every month
Identify invoices raised on overseas customers.
Confirm that each transaction is genuinely a service export under the applicable framework.
Identify the overseas recipient and payment arrangement.
Prepare the monthly EDF.
Submit it within the prescribed timeline to the appropriate authority.
Obtain and retain evidence of submission.
Ensure the AD has recorded the transaction in EDPMS.
Track each receivable against its FEMA realisation deadline.
Reconcile inward remittances with invoices and EDF entries.
Follow up on overdue receivables well before the 9-month deadline.
Resolve EDPMS outstanding entries with the AD.
Separately reconcile FEMA reporting with GST and accounting records.
17. Common mistakes and risks
Mistake 1: Treating every foreign receipt as an export
The payer's foreign location is not enough. The underlying transaction must be analysed.
Mistake 2: Treating EDF as a GST form
EDF is a FEMA foreign-exchange declaration. GST returns and export-of-services conditions remain separate.
Mistake 3: Using the old 15-month realisation period
This is particularly important. The January 2026 Regulations originally contained 15/18-month periods, but the September amendment reduced them to 9/12 months from 1 October 2026.
Mistake 4: Assuming ₹10 lakh means no EDF
The ₹10 lakh rule concerns simplified EDPMS closure, not a general exemption from filing the EDF.
Mistake 5: Continuing the old SOFTEX workflow
Software exporters should transition to the EDF framework applicable from 1 October 2026.
Mistake 6: Ignoring the invoice date
For services, the realisation clock under Regulation 5 runs from the invoice date, not the date on which the service is completed.
Mistake 7: Assuming the exporter must personally access EDPMS
The regulatory reporting responsibility for the service EDF entry is placed on the AD. The exporter should nevertheless monitor the status through the bank and retain evidence.
18. What should an exporter do now?
If you receive payments from overseas customers, do not wait until a remittance is rejected or an EDPMS entry becomes overdue.
Instead:
speak to your AD bank and obtain its current EDF process/SOP;
identify all service-export invoices raised from 1 October 2026;
create a monthly EDF calendar;
standardise customer and invoice data;
map each invoice to its expected inward remittance;
configure accounting/ERP reports for the 9-month FEMA deadline;
review software/SOFTEX processes if applicable;
reconcile FEMA and GST records without treating them as the same compliance;
establish a procedure for third-party receipts, refunds, deductions and delayed collections; and
obtain professional or AD-bank advice for unusual payment models.
For October 2026 invoices, the normal monthly EDF deadline is 30 November 2026.
FAQs
Is EDF mandatory for freelancers?
If the freelancer is an exporter of services covered by Regulation 3(2), yes. The regulation does not create a general exemption merely because the exporter is an individual or small business.
Can one EDF cover several invoices?
Yes. One EDF may cover service exports to one or more recipients during the month.
Can one EDF cover different overseas customers?
Yes. Regulation 3(2)(a) expressly permits a single EDF for service exports to one or more recipients in a month.
Is EDF a GST return?
No. EDF is a FEMA export declaration. GST reporting and export-of-services conditions are separate.
Is software covered?
Yes. The 2026 Regulations expressly state that services include software for these purposes.
Is SOFTEX still required from 1 October 2026?
The new framework replaces the earlier software declaration mechanism with the EDF framework. Software exporters should follow the applicable AD/STPI process under the 2026 Regulations.
Does every foreign remittance require an EDF?
Not automatically. First determine whether the underlying transaction constitutes an export of services or another type of receipt. Payment platforms, advertising revenue, royalties, marketplace settlements and creator income require transaction-specific analysis.
What is the FEMA realisation deadline for service exports?
Ordinarily 9 months from the invoice date from 1 October 2026. The period is 12 months where the applicable INR provision under Regulation 5 applies.
Can the AD extend the deadline?
Yes. The Regulations permit an AD to extend the realisation period on a request explaining the delay, if the AD is satisfied with the reasons.
Does the ₹10 lakh EDPMS rule exempt small exporters?
No. It provides a simplified EDPMS closure mechanism for qualifying small-value export entries. It is not a general exemption from EDF filing.
Conclusion
The 2026 FEMA framework changes service-export compliance in a meaningful way.
From 1 October 2026, Indian service exporters move into a formal EDF-based declaration and EDPMS monitoring framework. The change affects not only large IT companies but also freelancers, consultants, agencies and professional businesses dealing with overseas customers.
The practical compliance model is straightforward:
Identify the export → raise the invoice → furnish the EDF → ensure EDPMS reporting → receive and reconcile the proceeds → close the outstanding entry.
The most important date-sensitive point is the realisation period. Although the January 2026 Regulations originally provided 15 months, RBI's 22 September 2026 amendment reduced the applicable period to 9 months, or 12 months for the specified INR transactions, effective 1 October 2026.
Because the classification of certain cross-border receipts can depend heavily
on the contractual and commercial facts, exporters should obtain confirmation from their Authorised Dealer bank or qualified FEMA professional wherever the transaction does not clearly fit the conventional service-export model.
This article is intended for general regulatory information and should not be treated as a legal opinion. FEMA, GST and banking treatment can depend on the facts of the transaction and subsequent RBI clarifications or bank-level implementation procedures.
Comments