How to file an EDF with your bank in India in 2026

Use the RBI regulations as amended through 22 September 2026, rather than the original January version alone. They took effect on 1 October 2026. Software exporters outside SEZs can use an AD bank or STPI; SEZ service exporters use the Development Commissioner.

Ask the receiving authority which format, upload channel and signatory it accepts. Do not send a generic spreadsheet to an unrelated branch and treat the task as complete. Existing SOFTEX or older-period records should be resolved through the route that applies to those records, rather than deleted when starting the new workflow.

Scope: service-export invoice preparation. Goods exports, SEZ cases, historic declarations and bank-specific submission formats need their own checks.

Start with invoices raised in the reporting month, not only payments received in it. An unpaid invoice can otherwise disappear from your preparation process. Keep the original invoice and its client record beside the register so every value can be traced back to a document.

Create an exception list before making the document. “Invoice BB-EX-002: client country missing” is actionable; “some export details incomplete” is not. Assign the missing field to the person who can supply it and record whether the correction changes an already issued invoice.

1. 1Contact the branch or trade/forex team that handles your export receipts. State whether the export is software or another service and whether the entity is in an SEZ.
2. 2Ask for its current EDF template, supporting-document checklist, accepted signature method and secure submission channel.
3. 3Confirm how it wants amendments, credit notes, multiple GSTINs and a month with no exports handled.
4. 4Ask what acknowledgement or reference it issues, how to track pending cases and where to escalate a rejected pack.

A useful message is: “We need to submit the monthly service-export EDF for [month] for [entity]. Please confirm the applicable authority, current template, documents, signing method, submission channel and acknowledgement process.” Use your actual details only in the private message, not a public support thread.

1. 1Resolve the exception list. A missing country or SAC should remain visibly unresolved, not be filled with a plausible guess.
2. 2Compare the included invoice numbers against the month’s export register. Check that no invoice is absent or included twice.
3. 3Review totals separately by currency. Do not add USD and EUR into one unlabeled total or substitute a guessed exchange rate.
4. 4Check the generated PDF and spreadsheet against the bank’s accepted template. Obtain the required signature and submit through its confirmed channel.
5. 5Save the exact submitted version, acknowledgement, submission date and any follow-up requests beside the period’s records.

Treat “draft ready”, “sent” and “acknowledged” as different states. A downloaded PDF proves preparation; it does not prove that the bank accepted the declaration. If the bank asks for a correction, retain both versions and the reason for the change.

• Prior-month credit note: link it to the original invoice and ask whether the bank needs an amendment or a current-period adjustment. Do not silently net it against an unrelated export.
• Invoice amended next month: preserve the original, revised document and change reason. Check whether an already submitted pack needs correction.
• No exports: record that the month was checked and confirm the authority’s nil process. We have not verified a universal requirement to file a nil EDF.
• Late or incomplete pack: contact the authority promptly with the missing items and a reasoned request; do not mark it filed just to clear a dashboard warning.

Keep declaration timing separate from payment realisation. Under the amended RBI text, the general service realisation period is nine months from invoice; exports invoiced or settled in INR have twelve months. The bank can consider reasoned extension requests. Its small-value EDPMS closure provisions are not a blanket exemption from preparing an EDF.

In the EDF workspace, use the reporting period, review the export invoices and resolve the named completeness issues before generating the draft artefacts. Check the resulting files against your bank’s requirements. This keeps the invoice register, missing-field review and preparation in one workflow; the human still reviews and submits.

The example at the end lets you correct a missing field and regenerate a sample review pack. It deliberately does not calculate a regulatory deadline, invent bank acceptance or submit a declaration. To improve the next month’s pack, capture country and SAC when creating the invoice, rather than reconstructing them at filing time.

Can I file the EDF directly with my bank?

For non-software service exports outside an SEZ, the amended regulations identify the AD bank as the specified authority. Confirm the exact submission channel with the bank. Software and SEZ routes differ.

Is a Blackbird EDF download proof that I have filed?

No. It is a preparation artefact. Keep the receiving authority’s acknowledgement and any subsequent acceptance or correction messages.

Should I include only paid invoices?

Build the reporting register from invoices raised in the month, then attach the payment trail separately. Filtering only to received payments can omit outstanding invoices.

Prepared by Blackbird Finance editorial. Sources reviewed on 19 October 2026; access limitations are noted below. No independent CA review is claimed. Provider prices and portal screens can change.

• RBI: 2026 Export and Import Regulations, amended through 22 September 2026

Found an outdated detail? Tell us which passage and source need checking.

• Issue an export invoice under LUT, step by step
• Skydo vs Wise: compare the net INR received