NAS Mail — Practical email, follow-up and inbox workflow guidance for small organisations.

A Practical File-Naming Standard for Small Bookkeeping Practices

Bookkeeping folders become difficult to navigate when files arrive as “scan”, “invoice”, “statement final” or a string generated by somebody's phone. Renaming everything perfectly is rarely realistic, but a simple standard for controlled working copies can make records much easier to identify and review.

The best naming convention is one the team can apply consistently without spending more time naming a document than using it.

Choose the information that matters most

For each document group, decide which elements help a bookkeeper distinguish one record from another. Period, source, document type and a useful reference may matter more than long descriptive wording.

Put dates into a consistent order

Where dates belong in filenames, use one agreed format so records sort predictably. Make clear whether the date represents the document date, statement period or another relevant point.

Do not mix several meanings of date without a convention.

Use stable document-type labels

Agree a short vocabulary for recurring record types. Small variations such as “bank stmt”, “statement” and “bank statement” can make searching and sorting less reliable over time.

Preserve useful source references

Where an invoice number, account reference or other non-sensitive identifier helps distinguish records, include it consistently if appropriate. Avoid adding unnecessary confidential information merely to make a filename descriptive.

Handle corrected or replacement files explicitly

If a document is replaced, make the controlled current version clear while preserving the evidence needed to understand the change. Avoid accumulating filenames such as “final2-new-corrected” with no reliable status.

Do not destroy the original evidence trail

A working naming convention should not erase the provenance of received records. Where the practice retains an original upload or received file, keep the relationship between that source and any renamed working copy understandable.

Apply the standard where it creates value

Not every temporary file requires manual renaming. Focus on records that staff need to retrieve, review or hand over repeatedly.

A practical naming standard reduces the small delays that accumulate when bookkeepers cannot tell what a file contains until they open it. Consistency matters more than an elaborate naming formula.