Choose details you actually search by
In a manually managed folder, combining date, supplier and document number is often practical. For example, “2026-08-31_HostingAlfa_FA-1042.pdf”. This is a sample, not a mandatory format. Names should help distinguish files while their parts retain a consistent meaning.
Choose which date to include and use it consistently. Switching between issue and download dates changes how files sort. Use the document’s actual date; the filename is for finding files, not determining the accounting period.
You can include the company in the filename or express it through a clearly identified folder. Company labels are useful for files often sent individually. In a properly separated archive, repeating a long company name can be unnecessary.
The same number does not mean the same invoice
Two suppliers can each issue invoice “2026-001”. Naming files only by number makes them look like copies. Adding the supplier helps without putting every item and amount in the name.
Likewise, two companies may receive different documents from one supplier. Distinguish the buyer at handover. An example shared folder could contain “Alfa_2026-08-31_Hosting_FA-1042.pdf” and “Beta_2026-08-31_Hosting_FA-1043.pdf”. It is immediately clear these are not randomly renamed identical files.
For recurring subscriptions, do not rely only on the service name. Different periods may have equal amounts and similar names. A number or another verified distinguishing detail prevents confusion.
Do not invent missing details
If you do not know an invoice number, do not replace it with your own that might look supplier-issued. Use a clear name and leave the uncertainty in a note. Likewise, do not substitute an order number for a different document number.
For a corrected version, “correction” or “new-version” can help, but the name alone does not explain the change. Retain its relationship to the original and give the accountant specific information. “Final” in several successive filenames usually helps nobody.
If a document has several parts or pages in separate files, mark their relationship and order. The recipient should not guess whether a second image belongs to the same receipt or another purchase.
Renaming should not break the path to the original
You can make the filename clearer without changing its contents. Knowing its source message, portal or order helps later verification. If a name suggests a different company, it does not correct the original details inside.
Renaming files after handover can be confusing: your accountant has a copy and may refer to its original name. Leave completed packages as they are. If a change is necessary, tell them which file it concerns.
Sometimes keeping the original name is better
If an application finds documents by supplier, company and handover, you need not repeat these details in every PDF name. Useful records can largely replace manual renaming. The correct original and package context usually matter more to the accountant than perfectly consistent filename punctuation.
Try the naming pattern on a few invoices. If it helps you find them faster, it is useful. If renaming only slows you down and your app already finds everything, keep the original names.