Organise EDF documents: a folder and naming system that works

Keep invoices, payment evidence, versions and acknowledgements connected with a simple export-document index.

Good document organisation is less about collecting more PDFs and more about making a transaction understandable. Someone reviewing the folder should be able to answer who exported what, which invoice was raised, what was received and what action remains open. This is a practical filing suggestion, not a prescribed retention schedule.

Use stable identifiers instead of personal data

A useful filename starts with the invoice number, then the document type and date. For example, EX-104_receipt_2026-10-18.pdf is easier to connect than document-final-new.pdf. Avoid placing PAN or full bank account numbers in filenames that may appear in shared links. Keep originals separate from annotated working copies so comments cannot be mistaken for issuer content.

Keep one index of status and versions

List the invoice, customer, currency, related payment references, submission reference and latest action. Add version numbers to corrected drafts and preserve the earlier acknowledged version. A separate status column can distinguish prepared, sent, acknowledged and closed. Back up the folder using storage appropriate for the sensitivity of your documents and limit access to the people who need it.

Create a small index that survives staff changes

The index is the map to the folder, not a duplicate accounting system. Include the invoice reference, customer, currency, original-document location, receipt references and latest official response. Add the person responsible for the next action. Use consistent status terms and explain them in a short note so a new team member does not interpret sent as accepted.

Where files are stored in different systems, use a stable reference or controlled link rather than copying sensitive documents into every folder. Check that the people who need the index can actually open the underlying records. Avoid public sharing links for convenience. A well-named file is still unhelpful if its location or access depends entirely on the person who created it.

Name corrections without hiding the original

Use a predictable pattern such as invoice-reference, document-type, date and version. Put working annotations in a separate file or clearly marked copy. When a document is revised, keep a note explaining which value changed and whether an earlier version was submitted. Do not call every file final; it stops being a useful status label after the first correction.

Keep acknowledgement and correction references next to both versions in the index. If the bank requests a signed replacement, preserve the exact version that was signed and sent. A later editing copy should not silently take its place. This makes it possible to answer a question about a previous submission without reconstructing filenames from an email attachment history.

Plan access and backup around the actual sensitivity

Exporter information can include personal identifiers, customer details and payment references. Give access according to the work being performed. A colleague checking invoice counts may not need identity-document scans. Keep public source research separate from private transaction folders so sharing a regulation link does not accidentally share the complete business file.

Decide how your archive is backed up and how access is removed when a role changes. Test that an essential file can be retrieved from the backup rather than assuming synchronisation guarantees recovery. Apply the retention requirements appropriate to your business with professional advice where needed. This organisational guide does not supply a universal deletion date for legal, tax or banking records.

A fictional example

An exporter corrects the client spelling in EX-104. The folder retains v1, the correction request, v2 and the bank’s response. The index explains the change instead of leaving two unexplained PDFs called final.

Preparation checklist

Give each transaction a stable reference.
Separate originals, working drafts and accepted records.
Review shared access when a team member changes roles.

How long must I retain these files?

Check the legal, tax and bank requirements applicable to your circumstances. This naming guide does not prescribe a universal retention period.

FICTIONAL WALKTHROUGH

Two corrected invoices with similar filenames

A fictional team discovers EX-41-final.pdf and EX-41-final-new.pdf in separate folders. It compares them with the sent message and records which version was actually submitted. Neither file is deleted while the discrepancy is being resolved.
The team adopts a versioned naming pattern and adds the correction reason, submission reference and latest response to the index. Working comments move into a separate review note so the invoice remains distinguishable from internal annotations.
A second reviewer uses the index to retrieve the original, corrected copy and acknowledgement without asking the preparer where they are. The team then checks that the same records are included in its controlled backup and that access matches current responsibilities.

Your next step

Build a document checklist

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.