# A File Naming System for Bills, Receipts and Bank Statements

A good bookkeeping filename identifies the document date or reporting period, document type, counterparty or account and a stable reference. Use one documented pattern and keep it short enough to read. The filename should help locate evidence; it should not carry every accounting decision or change whenever a payment is made.

Choose a pattern the team can apply without interpretation. Consistency across hundreds of ordinary files is more useful than an elaborate name used correctly only by its designer. Keep detailed fields and workflow status in a document register linked to the file.

## Choose a small set of naming fields

For bills and receipts, a practical pattern is `Date_Type_Counterparty_Reference`. For example, `2026-10-08_BILL_RaoTools_INV1847.pdf`. The date uses year, month and day so ordinary alphabetical sorting follows date order when the convention is applied consistently.

The supplier’s invoice number and your internal document reference are different identifiers. Include one in the filename and retain both in the register, or include both if names remain manageable. Do not replace the original invoice number in the evidence.

Avoid characters and excessive length that your actual storage or software handles poorly. Test the pattern in the systems the team uses, including exports, email attachments and shared folders, rather than assuming every device behaves identically.

## Use different patterns for period documents

A bank statement covers a period rather than one purchase. A suitable example is `2026-10_BANK_Account1234_Statement.pdf`, using a masked account identifier. Keep the full account details in a controlled register where needed.

Payroll summaries, monthly settlement statements and recurring reports can follow similar period-based patterns. Define whether the date indicates the statement month, document issue date or transaction date so users do not make different choices.

| Document | Illustrative filename |
|---|---|
| Supplier bill | `2026-10-08_BILL_RaoTools_INV1847.pdf` |
| Expense receipt | `2026-10-09_RECEIPT_Taxi_EXP0261.jpg` |
| Bank statement | `2026-10_BANK_Account1234_Statement.pdf` |
| Supplier credit note | `2026-10-12_CREDIT_RaoTools_CN0052.pdf` |
| Monthly closing report | `2026-10_REPORT_Close_v02_Draft.pdf` |

These are internal conventions, not prescribed accounting or tax document numbers. The original document remains the source evidence.

## Standardise names without changing facts

Create short approved counterparty names linked to the customer or supplier master. A single vendor appearing as Rao Tools, RaoTool and RT Co can scatter files and defeat ordinary search. Preserve the legal name and original text in the register or document.

Keep invoice numbers recognisable. If an original number contains a slash or other character your system cannot conveniently use, define a replacement convention and retain the exact original in a separate field. Do not silently remove distinctions that could make two numbers appear identical.

For documents without an external number, assign an internal reference. A small cash receipt can be named using EXP0261 while the register explains that no supplier number was present. Do not invent an external invoice number.

## Keep workflow status out of stable evidence names

A bill can move from received to queried, entered and paid. Renaming the evidence at every stage can break links and produce multiple copies. Track those states in the register or approved system instead.

Version labels are useful for working reports and genuinely revised documents. Use a defined sequence such as v01 and v02, with a change log. A supplier’s corrected invoice should remain linked to the original and its explanation rather than simply overwriting it.

Distinguish a duplicate copy from a revised document. Receiving the same invoice by email after scanning it does not create a new commercial transaction. Mark the clearer copy under the same internal reference.

## Work through a retrieval example

An illustrative Ahmedabad distributor has 300 monthly supplier files. A reviewer asks for a ₹23,600 October bill from Rao Tools and the related ₹10,000 advance. The invoice file’s name identifies the date, supplier and invoice number; the register links the advance payment and remaining ₹13,600 balance.

Trying to include every payment in the invoice filename would make it longer and unstable. The link through the register preserves one evidence file while explaining several settlement events.

Similarly, one bank transfer settling four invoices should have a payment reference connected to all four document records. File naming supports the relationship, while the bookkeeping register establishes its detail.

## Protect sensitive information

Do not put full bank numbers, personal identity numbers, salary amounts or employee medical details in filenames visible to broad audiences. Use a suitable internal identifier and limit access to the relevant records.

A readable filename is not a security control by itself. Shared-folder permissions, approved access and appropriate handling of exports still matter. An employee should not gain access to every document merely because they need to upload one receipt.

Document how unknown dates or counterparties are handled. Use a clearly flagged temporary name and register the missing fact rather than inventing a date to satisfy the pattern. Once verified, update the name through the controlled process and preserve the reference. The convention should expose incomplete information, not make uncertain evidence appear complete for the sake of tidy sorting.

## Introduce the convention without disrupting history

Apply the pattern to new documents first and identify any older files that need renaming. Before a bulk change, preserve the original-to-new mapping and check links used by the books or register.

Test a sample covering multi-page invoices, credit notes, statements and mobile photographs. Ask another person to name and retrieve them using the written rule. Revise ambiguous parts before applying it widely.

A useful naming system makes ordinary retrieval predictable while preserving document identity. Keep the pattern simple, the register complete and the links stable so bookkeeping evidence remains understandable as the archive grows.

## Sources and references

- [ICAI Foundation Accounting: Basic Accounting Procedures — Journal Entries](https://resource.cdn.icai.org/74606bos60479-fnd-cp2-u1.pdf)
- [ICAI Foundation Accounting: Subsidiary Books](https://resource.cdn.icai.org/74609bos60479-fnd-cp2-u4.pdf)
- [ICAI Foundation Accounting: Rectification of Errors](https://resource.cdn.icai.org/74611bos60479-fnd-cp2-u6.pdf)