One EDF Per Month: How to Club All Your Client Invoices in a Single Form

You do not need a separate Export Declaration Form for every invoice. Under Regulation 3(2)(a) of the 2026 export regulations, one EDF per month can cover all your service exports of that month, to one or more recipients, with each invoice entered as its own row in Part 2B. File that single form within 30 days from the end of the month and you have handled the whole month in one go.

Key takeaways

• One EDF can carry every service invoice dated in a calendar month, even if they went to ten different clients in six countries.
• Each invoice is one row in Part 2B. The client, currency and amount can differ row to row.
• The monthly deadline is 30 days from the end of the invoice month, so October 2026 invoices are due by 30 November 2026.
• Part 1 is filled once for the whole form; only Part 2B grows with your invoice count.
• If you discover a missed invoice after filing, talk to your AD bank before you do anything else.

What the regulation actually allows

The Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 came into force on 1 October 2026. Regulation 3(2) sets the filing window for services, and clause (a) adds the practical relief: a single EDF can be used for all service exports made during a month, whether you billed one client or many.

A studio that sends 18 invoices a month would otherwise be signing and tracking 18 forms. The monthly route turns the EDF into a routine month-end job.

For services other than software, there is also an alternative: you can submit the EDF on or before the date payment is received. Most businesses with several clients still find the monthly bundle simpler, because it lines up with their accounting close.

How a monthly EDF is structured

Think of the form as a header and a ledger.

Part 1 (fields 1.1 to 1.22) is the header. It holds facts that do not change invoice to invoice: type of export (Services or Software), mode of delivery (usually Internet for remote work), your AD code, IEC if you have one, GSTIN, PAN, AD bank details and your own name and address. Field 1.22 is the total value in rupees for everything on the form, in figures and words.

Part 2B is the ledger. Each row records one invoice: recipient name and address, country, invoice number, invoice date, currency, amount, net realisable value, description of services, SAC code, contract number and date, and remarks.

Part 4 is your declaration, signed once for the whole form.

Where fields in Part 1 only fit one client (for example 1.13 consignee/recipient or 1.17 country of final destination), ask your bank how it wants a multi-client form handled. Many exporters write "Various, as per Part 2B" — but confirm that wording with your branch, since each bank publishes its own acceptance policy.

Worked example: a five-invoice month

Nimbus Labs Pvt Ltd, a Pune software firm, raised these invoices in October 2026:

All five go on one EDF. Pinegrove appears twice, and that is fine: two invoices, two rows. Nimbus converts each amount to rupees for field 1.22 using one documented exchange-rate method, totals them (say ₹38,46,000), and writes the total in words as well. The form is due by 30 November 2026.

Nimbus should still note the realisation deadline per row. Each invoice has its own nine-month clock from its own invoice date, so row 1 must be paid by early July 2027 and row 5 by the end of July 2027.

Building the form without errors

The most common problems in a monthly EDF are not legal; they are clerical. A practical sequence:

1. Pull an invoice register for the month from your accounting software, filtered to foreign clients.
2. Check numbering is continuous and that cancelled invoices are marked as such, not silently dropped.
3. Confirm each invoice's SAC code against your GST invoice. You can check codes with the SAC code finder.
4. Enter rows in invoice-date order so the bank can match them quickly.
5. Total the rupee values, write the total in words (our amount in words tool handles lakh and crore), and cross-check with your GST return figures for the month.
6. Sign Part 4 once, attach whatever the bank asks for, and record the acknowledgement.

The free EDF form generator lets you add as many Part 2B rows as you need and calculates the rupee total for you, which removes most of the arithmetic risk.

What if you miss an invoice

It happens: an invoice dated 31 October gets raised after your EDF was filed on 5 November.

There is no published self-service "amendment" route that applies to every bank, so the honest answer is: write to your AD bank, explain what was missed and why, and ask how it wants the invoice declared. Options a bank might suggest include a supplementary EDF for that month or a revised form. Do not quietly add the missed invoice to next month's EDF, because the invoice date would then sit outside that form's month and the records will not match in EDPMS.

The regulations also let the AD bank accept a delayed EDF for reasonable cause, so a genuine slip explained promptly is usually manageable. Keep a short note in your records of what happened.

This is general information, not legal or tax advice; your bank's written policy and your CA's view should guide edge cases.

When one form per month may not be the best fit

The monthly bundle is permitted, not compulsory. A few situations where exporters choose differently:

• One large invoice, paid fast. If you raise a single big invoice and the client pays within days, filing on or before receipt (the alternative for non-software services) can close things out early.
• Different AD banks. If some clients pay into HDFC and others into SBI, each bank handles the exports it receives. You may end up with one monthly EDF per bank. See our note on using multiple banks for exports.
• SEZ and non-SEZ units. An SEZ unit files with the Development Commissioner, not the bank, so it would not share a form with a DTA unit of the same group.

Frequently asked questions

Can one EDF include invoices to clients in different countries?

Yes. Regulation 3(2)(a) allows one EDF to cover service exports to one or more recipients in a month, and Part 2B has a country column on every row. Clients in the UK, US and Australia can sit on the same form as long as all the invoices are dated in that month.

Can I mix currencies on a single monthly EDF?

Yes. Each Part 2B row records its own currency and amount, so USD, EUR and GBP invoices can appear together. Field 1.22 then shows the combined total in rupees, so use one consistent, documented exchange-rate method for the conversion.

Does the one-per-month rule apply to software exports too?

The monthly bundling in Regulation 3(2)(a) covers service exports, and software is now declared on the same single EDF since SOFTEX was withdrawn. The "file on or before payment" alternative applies to services other than software, so software exporters should work to the 30-day monthly deadline.

What if my month has only one foreign invoice?

Then your monthly EDF simply has one row in Part 2B. You still file it within 30 days from the end of that month, or, for non-software services, on or before the date payment arrives if that suits you better.

Do I need a separate EDF for each AD bank?

Usually yes in practice, because each AD bank reports the exports it handles into EDPMS. If your clients pay into two different banks, ask each bank how it wants the month's invoices split.

Bottom line

One EDF per month is the simplest way to stay compliant: a single Part 1, one row per invoice, one signature, filed within 30 days from the month end. Build your next monthly form in the free EDF form generator and check your exact date with the EDF due date calculator.