10 Invoices, 1 or 10 EDF? EDF for Multiple Invoices Explained

The short answer

For most service exporters, ten invoices raised in the same month can go on one EDF, with each invoice as its own row. The rules allow one consolidated EDF per month covering all your clients and invoices. What decides which EDF an invoice belongs on is the month it was raised, not the month you get paid. Ten invoices spread across three months means three EDFs.

Key takeaways

• One EDF per month can cover every invoice raised that month, across all your clients. Each invoice is one row.
• Deadline: within 30 days from the end of the month the invoice was raised. October invoices, for example, are due by 30 November.
• Instalments don’t add rows. One invoice is one row, however many payments arrive against it.
• Invoice month drives it. Under the standard route, a October invoice paid in December still belongs on October’s EDF.
• Check with your bank on the edge cases: payments split across banks, months with no invoices, and the “file by payment date” option.

First, what is an EDF? (in plain terms)

Under RBI’s Foreign Exchange Management (Export and Import of Goods and Services) Regulations, service exporters declare their exports on an Export Declaration Form (EDF). You submit it to your AD bank (Authorised Dealer bank, the bank that handles your foreign exchange receipts).

The bank then records it on EDPMS (Export Data Processing and Monitoring System), which is RBI’s database that tracks each export entry until the money arrives and the entry is closed.

For software exporters, the EDF replaced the old SOFTEX form. For other service exporters (design, consulting, marketing, development agencies and the like), it brought in a declaration they didn’t previously have to file.

EDF for multiple invoices: five scenarios

Find the row that looks like your month. The explanations follow the table.

Scenario 1: ten invoices, one month

Say your agency raises ten invoices in October: four to a US SaaS client, three to a UK retailer and three to an Australian startup. All ten can go on one October EDF, as ten rows, due by 30 November. The rules allow a single EDF to cover all services exported to one or more recipients in a month.

Note that consolidating is an option the rules give you, not a requirement. How you actually submit (portal, email, bank template) is set by each AD bank’s own procedure, so check your bank’s process before your first filing.

Scenario 2: ten invoices, three months

If those ten invoices were raised across October, November and December, you file three EDFs: one per invoice month. Each has its own deadline:

•       October invoices: due 30 November
•       November invoices: due 30 December
•       December invoices: due 30 January

These dates follow the “30 days from the end of the invoice month” rule. The count of invoices doesn’t change the count of forms; the number of months does.

Scenario 3: one invoice, three instalments

A $9,000 project billed on one invoice, paid as $3,000 three times, is still one row. The EDF captures details invoice by invoice (invoice number, date, currency, amount), so payments against the same invoice don’t create new rows.

What the instalments do affect is tracking. A first payment doesn’t close the invoice; the rest is still outstanding until it arrives. Ask your bank how it wants part payments noted. Service export proceeds are generally expected within 9 months of the invoice date (12 months for rupee-invoiced exports).

Scenario 4: invoiced in October, paid in December

Under the standard route, this invoice goes on your October EDF, due 30 November, even though the money only arrives in December. That feels backwards, but it is how the rule is written: the deadline runs from the invoice month, not the payment date. The EDPMS entry simply stays open until the payment comes in.

There is one wrinkle. The rules also allow filing on or before the date you receive payment as an alternative. The common reading is that this applies to services other than software, so if you plan to rely on it, confirm with your AD bank first.

Scenario 5: money lands in two banks

The basic rule: file with the AD bank through which the proceeds are realised, meaning the bank that receives the money. If you collect through a payment platform, banks may handle that differently, so ask yours how it wants the EDF filed.

The split case is less clear-cut: some invoices paid into Bank A, others into Bank B. Does each bank get its own EDF for its share? Ask both banks directly and get their answer in writing.

Edge cases to confirm with your bank

A few situations depend on how your bank applies the rules. Worth a quick email before you file:

• The payment-date option: whether your bank lets you use it, and for which services.
• Months with no invoices: the obligation follows the invoice, so a month with no invoices has nothing to declare. Check whether your bank still wants a nil filing.
• Format and channel: each AD bank sets its own procedure for how the EDF is submitted, so the practical format can differ from bank to bank.
• RBI updates: RBI issues FAQs and circulars from time to time. If your bank points you to newer guidance, that takes priority over any general explainer, this one included.

A habit that helps: keep a simple monthly invoice register with invoice number, date, client, country, amount, currency, expected payment date and receiving bank. Whatever format your bank uses, those are the details each EDF row will draw from.

A note on the ₹10 lakh figure

You may have heard that bills under ₹10 lakh are “exempt”. They aren’t. The ₹10 lakh figure is a per-bill limit for bank self-declaration and closing the entry on EDPMS; it does not remove the EDF filing itself.

And if you’re a freelancer?

RBI has clarified that individuals with contracts of a personal nature are not covered by these reporting requirements. If you invoice as a business (a firm, a GSTIN, a proprietorship), confirm your position with your CA or AD bank.