Skip to content

Free template

File naming convention template

One page that settles how every file is named: the pattern, dates, separators, versions, patterns by document type, and the private numbers that never belong in a name. Copy it, adjust the examples and share it with the team.

For office managers, records managers and IT admins · Free, no sign-up · Copy it or print it · Updated October 2026

See the template

How to use this template

  1. 01

    Look at how people search

    Ask the team how they look for files today: by vendor, by date, by employee, by job. The folders should follow that; the names should sort within it.

  2. 02

    Keep only your document types

    Delete the rows you do not need in the patterns table and add the ones you do. Five well-chosen rows beat twenty.

  3. 03

    Try it on last month's files

    Rename twenty real files by the convention. If two clash or one will not fit, fix the rule now, not after a year of files.

  4. 04

    Automate it where you scan

    People forget conventions. Scanning software that names files from the values it reads never does.

The template

File naming convention

Text in [brackets] is yours to fill in. Copy pastes with headings and tables into Word or Google Docs, and as Markdown into plain-text tools.

File naming convention

Organization: [Organization name] · Applies to: [shared drives, SharePoint, scanned documents]
Owner: [Office manager or IT admin] · Effective: [YYYY-MM-DD] · Version: [1.0]

Every file we keep is named the same way, so anyone can find it, sort it and tell what it is without opening it. Names are built from values on the document, never from a scanner counter or a word like "final".

1. The pattern

Date_Identifier_Description_Version.ext, with folders carrying the document type and who the document is from or about.

  • Date first, so files sort in date order.
  • Identifier: one value that makes the name unique, such as an invoice, PO, contract or claim number.
  • Description: two to four words, only when the folder and identifier do not already say it.
  • Version: only for documents that change (drafts, contracts, policies).

2. Dates

  • Full dates are YYYY-MM-DD: 2026-09-14. They sort correctly and cannot be misread as day-month or month-day.
  • Monthly documents use YYYY-MM: 2026-09. Yearly documents use YYYY.
  • Use the date on the document (invoice date, signed date), not the date it was scanned. If there is none, use the received date and say so in [the description or a field].
  • Never 9-14-26, 14.09.2026 or Sept 14.

3. Separators and characters

  • An underscore separates the parts of a name. A hyphen joins words or numbers inside one part: 2026-09-14_INV-20931.pdf.
  • Spaces: [allowed inside a part, as in Northwind Supply / replaced with hyphens]. Pick one and keep to it.
  • Use letters, numbers, spaces, hyphens and underscores only. Windows does not allow \ / : * ? " < > | in names, and some systems reject # % & and commas too.
  • Write vendor and people names the same way every time: [Northwind Supply], [Lee Jordan] (last name first). Keep a list of approved short names for long ones.
  • Keep names under [60] characters. Long folder paths break in some systems and backup tools.

4. Patterns by document type

Swipe the table sideways to see every column.

Document typeFoldersFile nameExample
Vendor invoiceInvoices / VendorInvoice date_Invoice numberInvoices/Northwind Supply/2026‑09‑14_INV-20931.pdf
Purchase orderPurchase orders / VendorPO date_PO numberPurchase orders/Northbridge Office Supply/2026‑09‑02_PO-1031.pdf
Vendor statementStatements / VendorStatement dateStatements/Northwind Supply/2026‑09‑30.pdf
ContractContracts / Other partyEffective date_Contract type_VersionContracts/Harbor Logistics/2026‑07‑01_MSA_v03.pdf
Signed contractContracts / Other partyEffective date_Contract type_signedContracts/Harbor Logistics/2026‑07‑01_MSA_signed.pdf
HR documentEmployees / Last First / Document typeDocument date_Document typeEmployees/Lee Jordan/Offer letter/2026‑08‑01_Offer letter.pdf
Scanned mailScans / YYYY-MMReceived date_Sender_SubjectScans/2026‑09/2026‑09‑18_County Tax Office_Assessment notice.pdf
Meeting notesMeetings / TeamMeeting date_Meeting nameMeetings/Finance/2026‑09‑21_Month-end close.docx
Policy or procedurePoliciesPolicy name_VersionPolicies/Accounts payable policy_v02.docx

Example names and values are fictional. Replace the rows with your own document types.

5. Versions

  • Drafts carry a two-digit version: _v01, _v02, _v03. Two digits keep v10 sorting after v09.
  • The approved or signed copy replaces the version with a status: _approved or _signed. There is only one.
  • Never use final, final2, new, latest or a person's initials as a version.
  • Where the system keeps version history (SharePoint, a document management system), keep one file and let the system track versions instead.

6. What never goes in a file name

File names show up in folder lists, search results, sync logs, email notifications and sharing links, often to people who cannot open the file. Keep these out:

  • Social Security numbers and other tax IDs, including vendor tax IDs from W-9s
  • Bank account, card, routing and loan numbers
  • Dates of birth
  • Patient, member or policy numbers, and health details, when they identify a person
  • Passwords or anything marked confidential

Use an internal reference instead: a vendor name, an employee ID that means nothing outside [Organization name], a claim number. If you need the private value to find the file, keep it inside the document or in a restricted field.

7. Missing values and duplicates

  • When a value is missing, write a word, not nothing: [No PO], [Undated], [Unknown vendor].
  • Never overwrite a file with the same name. Add -2, -3 to the second and third, then find out why they clash.

8. Abbreviations we use

AbbreviationMeans
INVInvoice
POPurchase order
MSAMaster services agreement
NDANon-disclosure agreement
[Add yours][Meaning]

How to adapt it

Folders for browsing, names for sorting

Put who or what a document is about in the folders (the vendor, the employee, the matter) and let the name sort inside it. Two folder levels are usually enough, three at most. Deeper trees hide files and make paths long.

One unique value in every name

A date and a vendor name alone will clash the first time a vendor sends two invoices on the same day. An invoice, PO, contract or claim number makes each name unique.

Let the system carry the rest

If you store files in SharePoint, Google Drive or a document management system, the values can live beside the file as columns or fields. Then names can stay short, and search does the heavy lifting.

For folder layouts, duplicates and missing values in more depth, read how to name and file scanned documents automatically.

Common mistakes

  • Scan_0042.pdf. The scanner's counter tells nobody anything. Every scanned file needs a real name.
  • Dates written three ways. 09-14-26, 14.09.2026 and Sept 14 will never sort together.
  • contract_final_FINAL_v2.docx. Use two-digit versions and one approved or signed copy.
  • Private numbers in names. A tax ID in a file name is visible to anyone who can see the folder.

How CapturePoint 6 builds names automatically

CapturePoint 6 reads each scanned or imported document on your Windows PC, recognizes its type and pulls out the fields. It then names and files it by your convention, with no typing. The Export card in Job setup shows the destination and a live preview of where a real document will land.

The preview path AP Scans › Invoice › Northwind Supply › 2026-09-14_INV-20931.pdf: folders by type and vendor, then the invoice date and number.
  • Change how files are named opens the naming window. Each document type has its own folder levels and file name, built from the document type, any captured field, or your own words.
  • Separators and dates: pick an underscore, hyphen, space or nothing between parts. For a date, Show as offers year, year-month, full date, month or day, so a folder can be 2026-09 while the file name carries the full date.
  • Missing values: each field in a name has an If it's missing, use setting, such as No PO.
  • Duplicates: nothing is overwritten. A second file with the same name gets -2, a third -3, and the naming window warns you before you save when two current documents would share a name.
  • Private values: fields such as tax IDs and bank account numbers are marked as private. Choosing one shows a plain warning, and the Export card says Private value in names until you change it.
  • Reuse: Copy Invoice naming to… gives other types the same layout.

The same naming carries to SharePoint or OneDrive, Google Drive, Dropbox and Nucleus One. If a job exports to Content Central instead, Content Central's catalog builds the folders and file names. The CapturePoint help library covers setup step by step.

Next step

Let every scan name itself.

Download CapturePoint 6, open a sample job and set your naming convention in the preview before you scan a page.

Windows 10 or 11, 64-bit. The free trial starts the first time you open it, with no form to fill in.