NEEDО · INDIA SERVICE EXPORTS & FEMA REPORTING
India RBI Service Export EDF Rules 2026: ₹10 Lakh Threshold and EDPMS Checklist
India's service exporters have a new FEMA reporting framework from 1 October 2026. The Reserve Bank of India (RBI) Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, Notification FEMA 23(R)/2026-RB, were amended again on 2 November 2026. The changes matter to resident individuals, software professionals, agencies, consultancies and other service exporters receiving overseas payments. The key distinction is not simply whether an invoice is below ₹10 lakh. The regulation treats resident individuals differently from other exporters, uses an inward-remittance threshold for one deemed-EDF route, and separately allows certain small export entries to be closed in EDPMS on the basis of a declaration. This guide turns those provisions into an invoice, remittance and bank-evidence workflow. It is a document-preparation guide, not a legal or tax opinion.

1. Start with the 2026 FEMA regulations, not an old EDF checklist
The principal regulation is the Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, Notification No. FEMA 23(R)/2026-RB dated 13 January 2026. It came into force on 1 October 2026 and superseded the 2015 export-and-import regulations, subject to the provisions dealing with matters done or omitted before supersession. RBI's consolidated version is marked amended up to 2 November 2026. The Second Amendment, Notification FEMA 23(R)/(2)/2026-RB, was dated and published on 2 November and states that its relevant changes take effect from 1 October 2026.
RBI also issued A.P. (DIR Series) Circular No. 20 on 16 January 2026. It says the new regulations and associated directions become effective on 1 October 2026 and that the earlier Master Directions on export and import of goods and services stand superseded from that date. If an old bank checklist refers to the 2015 regulation or an earlier master direction, do not assume it reflects the current filing route. Ask the Authorised Dealer (AD) bank which current procedure and supporting information it requires for the actual service and exporter.
Record the controlling references
- Principal regulation: FEMA 23(R)/2026-RB, dated 13 January 2026.
- Effective date of the 2026 regulations: 1 October 2026.
- Second Amendment: FEMA 23(R)/(2)/2026-RB, dated 2 November 2026, with the relevant changes effective from 1 October.
- Consolidated RBI text: amended up to 2 November 2026.
- Transaction date, invoice month and payment date should be preserved separately.
2. Understand the general service-export EDF deadline
Regulation 3(2) says an exporter of services must furnish an Export Declaration Form (EDF) to the specified authority, declaring the amount representing the full export value of the services, within 30 days from the end of the month in which the service invoice was raised. This is a month-end calculation, not simply 30 days from the invoice date. An invoice issued on the first day and one issued on the last day of the same month fall within the same month-end filing window, subject to the specific deemed-submission and timing provisions described below.
For services in the Domestic Tariff Area, the regulation identifies an Authorised Dealer as the specified authority for services other than software. For software, the specified authority is an Authorised Dealer or Software Technology Parks of India (STPI). In a Special Economic Zone, the Development Commissioner is identified for services. The regulation defines services to include software, so do not assume that the word services excludes a software exporter from the EDF framework.
The general 30-day rule is the starting point. It must then be read with the deemed-submission routes for resident individuals and qualifying small inward remittances, the monthly consolidated filing option, and the special timing option for non-software services. Keep a record of which provision you rely on for each invoice instead of applying one blanket rule to every customer and payment.
A simple month-end control
- Record the invoice issue date and invoice month.
- Calculate the 30-day period from the end of that invoice month.
- Identify whether a deemed-EDF provision applies to the exporter and remittance.
- Record any consolidated monthly EDF or non-software timing option used.
- Retain the bank or specified-authority acknowledgement and any follow-up.
3. Resident individuals have a specific deemed-EDF route
The Second Amendment inserted a definition of resident individual as a person resident in India who is a natural person. It also added a provision to Regulation 3(2): an exporter of services who is a resident individual is deemed to have submitted the EDF when that person provides the information required in relation to receipt of payment for the services to the Authorised Dealer for crediting the individual's account.
The provision is not written with the ₹10 lakh ceiling that appears in the separate clause for a person other than a resident individual. Do not import that threshold into the resident-individual clause. At the same time, deemed submission is not a statement that the individual can ignore the bank's payment information requirements, the underlying service transaction, applicable realisation period, tax obligations or other FEMA provisions. Preserve the information supplied to the bank and evidence that the inward remittance was credited to the correct account.
The practical question is the person's legal status for this regulation. A sole proprietor, partnership, LLP, company, trust or other organization should not automatically be treated as a resident individual merely because one person owns or manages it. Where the legal form is uncertain, obtain the AD bank's written view rather than choosing the more convenient route.
Resident-individual evidence file
- Identity and evidence that the exporter is a resident individual for the relevant transaction.
- Overseas customer, contract or statement of work and service description.
- Invoice number, date, currency, full export value and invoice month.
- Information submitted to the AD bank for crediting the inward remittance.
- Bank credit advice, payment reference and date credited.
- Any bank acknowledgement or EDPMS reference supplied for the transaction.
4. Non-individual service exporters have a separate ₹10 lakh test
For an exporter who is a person other than a resident individual, Regulation 3(2)(b) deems the EDF submitted when the exporter gives the AD bank the required information relating to receipt of payment for the service for crediting the exporter's account, if the value of the inward remittance for that service is not more than ₹10 lakh or its equivalent in foreign currency.
Read the wording carefully. It refers to the value of the inward remittance for the service. It is not expressed as the exporter's annual turnover, total monthly sales, company size or a general exemption for every invoice issued by a small business. If several invoices are paid together, one invoice is paid in instalments, a customer pays through a platform, or one remittance covers more than one service, retain the allocation and ask the AD bank how it applies the threshold to that transaction. Do not split or relabel a payment to manufacture eligibility.
For a non-individual exporter whose inward remittance for a service is above ₹10 lakh, the small-remittance deemed-submission clause does not apply. The general EDF rule and the other available timing provisions must be considered. The bank may still require a formal EDF and supporting information even where a deemed route appears available; the exporter should keep the bank's written processing confirmation.
Threshold decision fields
- Exporter legal form: resident individual or other person.
- Service invoice, recipient and contract or statement-of-work reference.
- Inward remittance amount and currency for that service.
- INR equivalent and the bank's conversion or valuation basis.
- Whether the payment is one invoice, several invoices or an instalment.
- The clause relied on and the bank's acknowledgement.
5. When a formal EDF is still required
If the exporter is not a resident individual and the inward remittance for the service exceeds ₹10 lakh, do not mark the EDF as deemed submitted under Regulation 3(2)(b). Start from the general requirement to submit an EDF within 30 days from the end of the month in which the invoice was raised. Then check whether the service exporter can use another express timing or consolidation provision.
The regulation permits an exporter of services that has exported to one or more recipients in a month to submit a single EDF for all such exports. This can help a service business that invoices multiple overseas customers in the same month, but the underlying invoices and customer-level evidence should remain available. A consolidated form should not make it impossible to identify which customer, service, invoice value or remittance belongs to each line.
The regulation also says an exporter of services other than software may submit an EDF on or before the date of receipt of payment. The text expressly limits this option to services other than software. A software exporter should not assume that the same payment-date option applies. If the service is mixed, includes software deliverables or is difficult to classify, obtain the AD bank's written view before relying on the option.
Keep the filing route explicit
- Formal EDF under the general month-end rule.
- Single consolidated EDF for one or more recipients in a month, where used.
- Non-software service EDF submitted on or before payment receipt, where applicable.
- AD-bank extension requested with reasons if the filing period is delayed.
- A clear note when a deemed-submission clause is relied on instead of a separate form.
6. Do not confuse EDF submission with EDPMS closure
EDF submission and closure of an entry in the Export Data Processing and Monitoring System (EDPMS) are separate steps. Regulation 4(2) requires an AD bank to satisfy itself about the genuineness of an export or import transaction before crediting or debiting the account and to close or update the corresponding EDPMS or IDPMS entry. For an export where the service invoice is up to ₹10 lakh or its equivalent, the regulation allows the EDPMS entry to be closed on the basis of a declaration from the exporter that payment against the invoice has been realised either in full or otherwise.
The exporter may alternatively give that declaration to the AD bank on a quarterly basis for bulk closure of eligible entries. This is a mechanism for the bank's EDPMS reconciliation. It is not a blanket waiver of the obligation to realise and repatriate export proceeds, not proof that the customer paid in full, and not an instruction to erase an unpaid balance. If the invoice was only partly realised or remains unpaid, the declaration and the bank's treatment should accurately reflect the facts and any permitted reduction or extension.
The bank remains responsible for satisfying itself about transaction genuineness and for updating the system. Keep the invoice, remittance, bank advice, exporter declaration and any explanation for under-realisation together. A quarterly spreadsheet without invoice-level traceability is difficult to reconcile when the bank asks which entry is being closed.
EDPMS closure register
- Invoice number, date, customer and service description.
- Invoice value, currency and INR equivalent.
- EDPMS reference or bank's outstanding-entry identifier.
- Amount realised, date credited and any balance or shortfall.
- Exporter declaration date and whether it is part of a quarterly batch.
- AD-bank acknowledgement, closure status or follow-up question.
7. The ₹10 lakh import-service rule is a separate counterpart check
The 2 November amendment also changed the bank's IDPMS entry requirement for import of services. The AD bank enters details in IDPMS as furnished by an importer who is a person other than a resident individual where the service invoice or contract value is more than ₹10 lakh, within five working days of receiving the details. This is an importer-side rule. It should not be used to decide an exporter's EDF route.
Regulation 4(2) separately allows an IDPMS entry for an import service invoice up to ₹10 lakh to be closed on the basis of an importer declaration that the import payment has been made either in full or otherwise. The importer may provide the declaration quarterly for bulk closure. Again, this is a system-reconciliation provision, not a substitute for checking the underlying contract, payment and bank requirements.
If an Indian agency both exports services to overseas customers and buys cloud, software, design, research or consulting services from overseas suppliers, maintain export and import registers separately. The direction of the transaction, the resident status of the party, the invoice or contract value and the relevant system all matter.
Separate the two ledgers
- Export services: exporter, inward remittance, EDF and EDPMS.
- Import services: importer, outward payment, supporting details and IDPMS.
- Do not reuse an export declaration to close an import entry.
- Retain the bank's written status for each system reference.
8. Keep export-proceeds realisation separate from EDF timing
Regulation 5 sets a separate period for realisation and repatriation of the full export value. For services, the general period is nine months from the date of invoice. Where the export of goods or services is invoiced and/or settled in Indian rupees, the regulation specifies twelve months from the invoice date for services. The AD bank may allow an extension on an exporter request that explains the delay, if the bank is satisfied with the reasons.
These periods answer a different question from the EDF filing deadline. The EDF rule deals with when the export declaration is furnished or deemed submitted. The realisation rule deals with when the export proceeds must be realised and repatriated. An exporter should not use the nine-month period as permission to delay an EDF that is due earlier, and should not treat an EDF acknowledgement as proof that payment has been received.
Where the invoice is partially paid, discounted, disputed, written off or otherwise under-realised, record the amount received and the reason for the difference. Regulation 6 contains a process for reduction in export realisation and a declaration-based provision for exports up to ₹10 lakh. Ask the AD bank to confirm the evidence and route applicable to the particular case.
Two separate dates to track
- EDF: the general 30-day-from-month-end period or the specific deemed/timing route.
- Realisation and repatriation: nine months from invoice for services, or twelve months where invoiced and/or settled in INR.
- Any bank-approved extension, reduction or non-realisation treatment.
- Actual bank credit date and amount, not only the payment advice sent by the customer.
9. Build an invoice-to-remittance evidence register
The most useful control is a monthly register that connects the service delivered, the invoice, the customer, the inward remittance and the bank's system status. Give every invoice a stable internal reference. If a payment platform, payment aggregator or overseas intermediary appears in the bank statement, record the relationship between that sender and the contractual customer. Do not assume the sender name alone proves who purchased the service.
For each invoice, retain the contract or statement of work, customer legal name and country, service description, period of performance, invoice value and currency, invoice issue date, payment terms, bank receiving account, remittance reference, value date, INR equivalent and any fee or deduction. If the payment covers multiple invoices, record the allocation. If the customer pays in instalments, retain each remittance against the same invoice and update the outstanding balance.
Keep a separate field for the EDF route: formal filing, consolidated filing, non-software payment-date filing, resident-individual deemed submission, non-individual small-remittance deemed submission, or pending bank clarification. This prevents a later reviewer from having to reconstruct why a form is absent. Store the bank acknowledgement or email with the record rather than writing only 'submitted' in a spreadsheet.
Suggested register columns
- Invoice ID, invoice month, customer, country and service category.
- Exporter legal form and whether the service is software.
- Invoice amount, currency, date and contract reference.
- Remittance amount, currency, date, bank reference and allocation.
- Applicable EDF clause, due date, filing or deemed-submission evidence.
- EDPMS reference, closure declaration date and bank status.
- Realisation deadline, unpaid balance, extension or reduction request.
- Evidence owner, next action and last verified date.
10. Worked examples: individual, small firm and larger invoice
Example A: an Indian resident individual consultant invoices an overseas customer for ₹4 lakh of services. When the consultant gives the AD bank the information required in relation to receipt of payment for crediting the account, the individual is deemed to have submitted the EDF under Regulation 3(2)(a), as inserted by the Second Amendment. Keep the invoice, contract, bank information and credit advice. The resident-individual clause is not expressed with the non-individual ₹10 lakh ceiling.
Example B: an Indian private limited company receives an inward remittance of ₹8.5 lakh for a service invoice. If it is a person other than a resident individual and the inward remittance for that service is not more than ₹10 lakh, the deemed-submission route in Regulation 3(2)(b) may apply when the required payment information is given to the AD bank. Preserve the invoice-to-remittance mapping and the bank acknowledgement.
Example C: an Indian LLP receives ₹18 lakh for a service invoice. The non-individual small-remittance clause does not apply to that remittance. The company should assess the general 30-day month-end EDF rule, whether a single monthly EDF is appropriate, and whether the service is non-software and can use the payment-date option. It should not simply mark the form exempt because the business is an MSME. These examples are illustrative; the AD bank must confirm the transaction's treatment.
What the examples do not decide
- Whether a service is software for Regulation 3(2)(d).
- How a combined or platform-mediated remittance should be allocated.
- The bank's current supporting-document checklist.
- GST, income-tax, export-of-services or other statutory treatment.
11. Common mistakes that create avoidable bank follow-up
The first mistake is treating ₹10 lakh as an annual turnover exemption. The regulation uses different transaction-level wording for deemed EDF submission and EDPMS closure. The second is treating a company owned by one person as a resident individual. The definition is a natural person resident in India; a company remains a separate legal person. The third is using the non-software payment-date option for a software export without checking the exact wording.
Other common errors include counting the 30-day EDF period from the invoice date rather than the end of the invoice month, combining multiple invoices without a traceable allocation, recording a payment screenshot as a bank credit, and treating EDPMS closure as proof that the full export value was realised. A payment processor's settlement statement may be useful, but reconcile it to the AD bank's credit advice and the actual remittance.
A final error is relying on a 2015 regulation or an old Master Direction without checking the 2026 replacement. If a bank portal or internal checklist still shows the older procedure, ask the bank to identify the current clause and process. Keep the answer with the transaction file so the next monthly close uses the same verified interpretation.
Red flags in your own process
- No legal-form field for the exporter.
- No distinction between software and non-software services.
- No invoice-month or month-end EDF calendar.
- Remittance amount cannot be mapped to one or more invoices.
- No bank acknowledgement for a deemed EDF route.
- EDPMS closure declaration is treated as payment confirmation.
- Old 2015 guidance is used without checking the 2026 regulation.
12. A practical bank clarification request
When the legal form, remittance allocation or service classification is not obvious, ask the AD bank a precise question and attach the supporting documents. Avoid a broad request such as 'Please confirm FEMA compliance.' State the exporter type, service type, invoice date and month, amount, remittance value, currency and the exact provision you believe may apply. Ask the bank to confirm the EDF route, supporting information, system reference and any required declaration.
A useful request also distinguishes the EDF question from EDPMS closure and export-proceeds realisation. If the invoice has been paid in instalments or the remittance covers several invoices, include an allocation schedule. If the service is software or contains software deliverables, describe the work accurately rather than choosing a category only to obtain a more convenient filing date.
Copy-ready questions for the bank
- Please confirm whether our exporter legal form is treated as a resident individual or a person other than a resident individual for Regulation 3(2).
- Please confirm how the inward remittance for invoice [number] is valued against the ₹10 lakh threshold and what evidence is required.
- Please confirm whether the service is treated as software or a non-software service for the timing provision.
- Please confirm whether a formal EDF, monthly consolidated EDF or deemed-submission route applies and how we receive acknowledgement.
- Please confirm the EDPMS reference and the form of declaration required for any eligible invoice-level or quarterly closure.
13. Use Needo to prepare the monthly service-export control pack
Needo can organize a set of service invoices, contracts, bank advices and remittance records into a monthly evidence register. It can separate resident individuals from other legal forms based on information supplied, identify whether the service has been described as software or non-software, calculate invoice-month filing dates, flag non-individual remittances near or above the ₹10 lakh threshold, and list which transactions still need an AD-bank answer.
It can also prepare a separate EDPMS closure register, identify invoices up to ₹10 lakh, reconcile declared realisation with the bank evidence, track quarterly declaration batches and maintain a separate nine-month or INR-settled twelve-month realisation calendar. If a payment is allocated across multiple invoices or only partly realised, Needo can show the missing allocation instead of assuming a match.
The output is a preparation pack: source-linked rule notes, invoice-to-remittance matrix, due-date calendar, bank questions, missing-evidence list and owner handoff. The AD bank remains responsible for its banking and system processes, and the exporter remains responsible for accurate declarations and applicable tax and legal obligations.
Ask Needo for these deliverables
- A monthly EDF route and deadline matrix.
- A resident-individual versus non-individual threshold review.
- A software versus non-software question register.
- An invoice-to-remittance reconciliation and EDPMS closure tracker.
- A bank clarification email or document checklist for your review.
- A separate export-proceeds realisation and repatriation calendar.
14. Final checklist before closing the month
Before the monthly close, confirm that every overseas service invoice is in the register, the exporter legal form is recorded, the service category is described accurately and every inward remittance is allocated. For each invoice, identify whether a formal EDF is due, a consolidated filing is used, the non-software payment-date option applies, or a deemed-submission clause is supported by information given to the AD bank. Retain the bank evidence.
Then review EDPMS separately. Identify eligible service invoices up to ₹10 lakh, reconcile the actual amount realised, prepare any quarterly bulk declaration with invoice-level references and obtain the bank's status. Finally, review the realisation and repatriation period and escalate unpaid, short-paid or disputed invoices before the due date. A tidy register is useful only if it records the actual evidence and the unresolved decisions.
Month-end sign-off
- Every service invoice has a customer, service description and invoice month.
- Exporter legal form and software/non-software status are recorded.
- The correct EDF clause and filing date are documented.
- Bank inward remittances are reconciled to invoices and credit advice.
- EDPMS closure declarations are separate from EDF submission.
- Unpaid or under-realised invoices have an owner and next action.
- Tax, GST and other non-FEMA obligations are reviewed separately.
Sources and further reading
- RBI — Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, amended up to 2 November 2026
Primary consolidated text for Regulations 3, 4, 5 and 6, including EDF, EDPMS/IDPMS and export-proceeds realisation.
- RBI — Second Amendment Regulations, 2026, Notification FEMA 23(R)/(2)/2026-RB
Primary 2 November 2026 amendment adding the resident-individual and non-individual ₹10 lakh deemed-EDF provisions and changing import-service IDPMS reporting.
- RBI — A.P. (DIR Series) Circular No. 20, Export and Import of Goods and Services
Explains the 1 October 2026 commencement of the new framework and supersession of earlier export and import Master Directions.
- RBI — Foreign Exchange Management (Manner of Receipt and Payment) Regulations, 2023
The 2026 regulations refer to this framework, as amended, for the manner of export and import receipts and payments.
Sources support the specific points noted above. Confirm current requirements for your product, destination and contract before committing.
Need the actual problem solved?
This guide explains the method. Needo can work from your specific requirement, compare relevant options, verify important details and help move the next step forward.
Start with your exact problem →Selling or exporting? See live buyer requirements by product · see a sample verified shortlist