Your first month with EDF: from invoice folder to bank response

A manageable first-month workflow for collecting export information, preparing a draft and following up with the forex desk.

The first month feels difficult when invoices, receipts and instructions are scattered across different apps. You can make progress before knowing every field: establish one organised record of the facts. The following is an editorial preparation routine, which you should adapt to your authority’s accepted process.

Create an invoice-first working folder

Use a month label and a short index of invoice numbers, customers, currencies and issue dates. Put the original invoice in the folder, then link any receipt or deduction evidence to it. Do not organise solely by the date a payout reached your account; that makes unpaid invoices hard to see. Separate older outstanding items so they cannot disappear inside the new month.

Move from questions to a reviewed draft

Resolve the exporter identity and submission route first. Prepare the worksheet, compare each row with its original invoice and review the totals by currency. Send questions through the bank’s verified channel. Record whether the response is a request for more information, an acknowledgement of receipt or a confirmation of the final status. These stages should remain visibly different.

Run a small trial with fictional information

Before entering real business details, use a sample that resembles your work and follow it from the first field to the review screen. Notice which values belong to the exporter, invoice, customer and receipt. Check what the downloaded worksheet contains. This helps you identify missing facts before you have a deadline or sensitive documents open on a shared computer.

Then create your real working list from original invoices. Keep the fictional trial separate so a sample customer or amount cannot accidentally enter the final bundle. If a field is unfamiliar, write down the question and use the field guide. Avoid filling every optional field merely because it is visible; concentrate on accurate information and the authority’s requirements.

Set up a review that catches actual errors

Review the schedule in two directions. First, choose an original invoice and confirm it appears correctly in the draft. Second, choose a draft row and trace it back to the original. This catches both omissions and invented or duplicated entries. Compare counts, currencies, customer names and gross values, not only the final total.

Give exceptions a clear label and owner. Examples include a missing customer country, an unexplained fee, a payment without an invoice reference or an uncertain authority route. An exception list is more useful than silently guessing a value. If you work alone, make the second review at a different time and check against source documents rather than relying on memory.

Close the preparation loop after sending

The job is not finished when a draft is downloaded. After using the official submission channel, record the date, recipient or portal, attachments and reference. Save any request for additional evidence with the same bundle. Distinguish an automated delivery message from the authority’s acknowledgement and any later acceptance or closure response.

At the end of the cycle, list what remains open and what slowed preparation. Choose one improvement for next month, such as collecting customer addresses at contract stage or downloading settlement statements routinely. Keep the current form version and channel in a process note. This turns the first month into a repeatable routine rather than a collection of one-off emails.

A fictional example

An agency has four invoices and two payments. It prepares all four invoice rows, links the two receipts and lists the remaining balances. Its first enquiry asks which accepted form and channel to use; it does not call the draft a filed EDF.

Preparation checklist

Choose a consistent folder and filename pattern.
Review customer names and gross invoice amounts before sending.
Keep a follow-up date beside every unanswered request.

Should I wait for every customer to pay before organising the month?

No. You can organise invoice and receipt facts separately while confirming the applicable declaration route.

FICTIONAL WALKTHROUGH

A first-month bundle with one unresolved receipt

A fictional agency lists four invoices and discovers only three original PDFs in its folder. It retrieves the fourth before preparing the worksheet. The schedule separates USD and EUR and identifies which invoices have no receipt yet. It checks the exporter name against the contract.
One payment statement lacks a clear invoice reference. The agency leaves the allocation unresolved and asks the customer or provider for supporting information. It does not attach the payment to the closest-looking invoice merely to make all the status labels read received.
The reviewer signs off the accurate information and sends the bank a focused process enquiry. The agency records the reply and next action, then adds payment-reference collection to the next month’s routine. The unresolved receipt remains visible until evidence supports the match.

Your next step

Prepare an information draft

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.