Late EDF preparation: write a clear chronology for your request

Prepare an honest explanation of a filing delay and the steps taken to resolve it.

When a date has passed, the most useful starting point is an accurate chronology. Avoid backdating a document or selecting a false invoice date. Explain what happened, which records are affected and what practical step you are requesting from the appropriate bank or authority.

List events and supporting evidence

Record invoice dates, the date you identified the issue, earlier contact with the bank and the reason the information was unavailable or incomplete. Link each material event to evidence where possible. Separate a known fact from an estimate. If several invoices are affected, provide a schedule so the reviewer can see the scope of the request.

Make the requested action concrete

State what you are now ready to provide and the date you propose, where relevant. Describe any correction to your internal process that addresses the cause of the delay. Ask for a written decision and any conditions. A generated request is only preparation; keep its actual submission reference and the authority’s response before treating the matter as resolved.

Reconstruct the timeline without improving the facts

Start from source documents: invoice issue dates, earlier bank contact, records requests, discovery of the omission and the date the preparation became ready. Put events in order and identify their evidence. Where you do not know a date, state that limitation instead of inserting a plausible one. A chronology should be accurate enough for another person to verify.

Separate the cause of delay from the action taken after discovery. For example, missing source information and a later corrective review are different events. Avoid a long narrative that makes the key dates difficult to find. Use a short summary and an attachment index, while preserving the underlying messages and documents needed to support the account.

Specify the affected population and requested action

List each affected invoice or period, its original reference and current preparation status. Identify whether the request concerns an initial delayed submission, additional time, a missing attachment or a correction to something already sent. Those questions should not be merged into one vague request for regularisation. Use the relevant bank workflow and ask what further information it needs.

State any proposed date honestly and mark it as requested, not approved. Explain what is ready and what remains outstanding. Keep your corrective steps proportionate to the cause, such as reconciling invoice counts or assigning a review owner. Do not promise a complete process redesign that you have not implemented merely to make the letter sound stronger.

Track the decision rather than the generated letter

A prepared extension letter is not an approval. After sending through the confirmed channel, retain the date, recipient, attachments and reference. Record the actual response, including conditions or requests for evidence. If no decision has arrived, keep the status pending and follow up using the same chronology. Do not replace it with an approved label because a draft contains the date you requested.

When further facts emerge, update the request transparently and preserve the earlier version. If some invoices are resolved and others are not, track them separately. At the next monthly review, confirm that the underlying cause has been addressed. The aim is an honest record and a workable next step, not a cosmetic explanation hiding an ongoing gap.

A fictional example

A records migration leaves two invoices out of a monthly working list. The exporter identifies them, reconstructs the timeline, attaches the missing invoice schedule and asks the bank to assess the delayed submission. The draft does not invent an earlier sending date.

Preparation checklist

Use actual event dates.
Identify every affected invoice.
Retain the written decision and any conditions.

Will a good explanation guarantee an extension?

No. The relevant authority decides the request. The purpose of the chronology is to make the facts clear.

FICTIONAL WALKTHROUGH

An omission is discovered during a later review

A fictional exporter discovers two omitted invoices while comparing its register with a previous schedule. The preparer records when the invoices were issued, when the omission was found and what earlier submissions exist. They preserve the original schedule rather than changing its archived date.
The request identifies the two invoice references, explains the documented cause and states what is now ready. A proposed sending date is labelled as a request. The exporter asks the bank for the accepted delayed-submission process and any further requirements.
The response is logged against both invoices. If one needs extra evidence, that item stays pending. The team adds a count comparison to its next close and retains the complete chronology so the same omission cannot disappear behind a new monthly file.

Your next step

Prepare a delayed-filing request

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.