Keeping an EDF Register: Records Every Service Exporter Should Maintain

An EDF register is a single running record that links every export invoice to the EDF it was declared on, the payment that settled it and the certificate that proves it. If you keep only one compliance spreadsheet as a service exporter, make it this one, because it answers almost every question your bank, CA or GST officer will ask. A spreadsheet with a dozen columns, updated once a month, is enough.

Key takeaways

• Track two levels: one line per monthly EDF and one line per invoice inside it.
• Record the submission date and any bank acknowledgement number the day you file.
• Log realisation date, amount received, FIRA/FIRC reference and charges for each invoice.
• Watch the 9-month realisation deadline for every invoice, not just the EDF due date.
• Close the loop with the eBRC reference once it is generated.

Why a register matters more under the 2026 rules

Since 1 October 2026, service exporters file one EDF per month covering all invoices of that month. That is convenient, but it means a single form can carry ten or forty invoices, each with its own currency, client and payment timeline. Your bank enters the EDF into EDPMS and tracks each invoice until it is realised. If your records are thinner than the bank's, you will struggle to explain gaps.

A good register also protects you when people change. The accountant who filed the October EDF may not be the one answering a bank query in June. The register is the institutional memory. We explain the related term in the glossary entry for EDF register.

The two-level structure

Keep the register as two linked tabs, or one sheet with clear grouping.

Level 1: the monthly EDF log

Level 2: the invoice tracker

For each invoice, add a row with: EDF month, invoice number, invoice date, client, country, currency, invoice amount, net realisable value, SAC code, realisation deadline (9 months from invoice date, or 12 for rupee invoices), date received, amount received, charges deducted, FIRA/FIRC reference, purpose code on the remittance, closure method (documents or ₹10 lakh declaration), EDPMS status and eBRC reference.

That looks like a lot, but most columns are copied straight from your invoice and your bank advice. Only three need thought each month: amount received, closure method and status.

A worked example

Kestrel Analytics Pvt Ltd, a Kochi data-services company, invoiced three foreign clients in October 2026.

Kestrel filed its October EDF on 18 November. Reading the register in December, the finance lead sees three actions at a glance. KA/26/041 needs a note to the bank explaining the GBP 15 charge deducted abroad. KA/26/042 needs a polite reminder to the Singapore client. KA/26/043 needs a check in January to confirm the eBRC has appeared.

Without the register, the GBP 15 shortfall would probably sit unnoticed until it caused a query months later.

The acknowledgement number: record it on day one

Whatever proof your bank gives you on submission, whether a reference number, a stamped copy or an email reply, record it immediately. If the bank later says it never received the October EDF, the acknowledgement settles it in one line. Banks use different channels, so the form of proof varies. If yours gives nothing, keep the sent email and ask for a written confirmation. Our piece on why the EDF acknowledgement number matters covers this in more depth.

Monthly routine: fifteen minutes

1. First week of the month: list last month's invoices in the tracker and calculate each realisation deadline.
2. Before the EDF due date: fill and submit the EDF, then log the submission date, channel and acknowledgement.
3. Whenever money arrives: record date, amount, charges and FIRA/FIRC reference against the right invoice.
4. Month end: filter for open invoices older than six months. These need chasing or an extension request.
5. Quarter end: list realised invoices of ₹10 lakh or less that can go on a periodic realisation declaration.

You can work out due dates quickly with our EDF due date calculator.

What to keep alongside the register

The register points to documents; it does not replace them. Keep, for each month: the signed EDF, every invoice, contracts or statements of work, FIRAs or FIRCs, payment advices, any matching letters you sent the bank, ₹10 lakh declarations and eBRCs. How long to retain these is a question for your CA, since FEMA, GST and income-tax rules each have their own expectations.

This is general information, not legal or tax advice.

Frequently asked questions

Is an EDF register a legal requirement?

The 2026 Regulations require the EDF and timely realisation; they do not prescribe a register format. A register is a practical control that makes compliance easier to prove. Ask your CA whether your accounting system already captures the same data.

Can I keep the EDF register inside Tally or Zoho Books?

Yes, if you can add custom fields for EDF month, acknowledgement number, realisation deadline and eBRC reference. Many exporters still keep a separate spreadsheet because it is easier to share with the bank and CA.

What should I do if an invoice appears on the wrong month's EDF?

Note the error in the register's remarks column and speak to your AD bank about correcting it. Do not quietly re-list the invoice on another EDF without the bank knowing, as that can create a duplicate EDPMS entry.

How do I track partial payments in the register?

Add a separate row for each receipt under the same invoice, or keep running totals of amount received and balance due. The invoice stays open until the full value is realised or the bank accepts an explanation for the shortfall.

Bottom line

A simple two-level register turns the monthly EDF from a scramble into a checklist and gives you instant answers when the bank asks. Set it up this month and fill it as you go. Then generate each month's form with our free EDF form generator and log it the same day.