File naming conventions
File naming conventions that stay readable at scale
Instead of ad-hoc filenames, use simple, repeatable patterns for invoices, receipts, legal docs, research, and project files. Start from proven examples, then adapt them to your own folders.
Short answer
A good file naming convention leads with date, includes who or what the file is about, and ends with a stable identifier—using only safe characters.
- Start with a sortable date, usually YYYY-MM-DD or YYYY-MM for statements and reporting periods.
- Add the key entity: client, vendor, matter code, project code, or country/jurisdiction.
- Finish with document type and an identifier like invoice number, statement period, or version-neutral label.
- Use underscores or hyphens, avoid spaces and characters that break on Windows.
For example: 2025-03-31_AcmeCorp_Invoice_INV-1042.pdf or 2025-Q1_EU-Digital-Services_OSS-VAT-Return.pdf.
Naming convention examples by team
Browse opinionated patterns for accounting, legal, research, and operations. Each guide includes battle-tested filename formats, token definitions, and common mistakes to avoid.
Accounting & finance
Patterns tuned for how this team actually searches and reconciles documents.
For operations, finance admins, and expense management teams
Expense Receipt Naming Convention
Standardize expense receipts with employee name, vendor, date, and amount. Keep reimbursements audit-ready and reconciliation fast.
Example pattern
2025-10-15_JohnSmith_Uber_42.50.pdfFor bookkeepers, accountants, and finance teams
Invoice File Naming Convention
Establish consistent invoice filenames with vendor, date, amount, and invoice number. Keep your accounting workflow audit-ready and reconciliation fast.
Example pattern
2025-10-15_AcmeSupply_INV-10234_1250.00.pdfFor bookkeepers, accountants, and finance teams
Chase Bank Statement Naming Convention
Standardize Chase Bank statement filenames with account number, statement period, and account holder. Keep your banking records organized and audit-ready.
Example pattern
2025-10_Chase_4567_Sep15-Oct14.pdfFor bookkeepers, accountants, and finance teams
QuickBooks Invoice Naming Convention
Standardize QuickBooks invoice filenames with invoice number, customer name, date, and amount. Keep your AR records organized and ready for import.
Example pattern
2025-10-15_AcmeCorp_1042_2500.00.pdfFor bookkeepers, accountants, and business expense tracking
Amazon Receipt Naming Convention
Standardize Amazon receipt filenames with order number, date, vendor, and amount. Keep your expense records organized and ready for reimbursement or tax filing.
Example pattern
2025-10-15_Amazon_123-4567890_89.99.pdfFor bookkeepers, accountants, and finance teams
Amex Statement Naming Convention
Standardize American Express statement filenames with account number, statement period, and cardholder. Keep your credit card records organized and audit-ready.
Example pattern
2025-10_Amex_1005_Sep15-Oct14.pdfFor bookkeepers, personal finance, and accounting teams
Bank Statement Naming Convention
Organize bank statements by period, institution, and account for fast reconciliation. Keep statements audit-ready without exposing account numbers.
Example pattern
2025-10_Chase_7842.pdfFor accountants, tax preparers, and individuals
Tax Return Naming Convention
Name tax returns and supporting documents by tax year, form type, and entity. Never include full SSNs. Keep filings findable for 7+ years.
Example pattern
2024_1040_SmithFamily.pdfFor procurement teams, AP departments, and operations
Purchase Order Naming Convention
Name purchase orders by PO number, vendor, and date to match ERP records. Streamline AP workflows and three-way matching.
Example pattern
2025-10-15_PO-10234_AcmeSupply.pdfFor bookkeepers, CFOs, and finance teams
Accounting Document Naming Convention
Name accounting documents by fiscal period, document type, and entity. A unified system for GL exports, trial balances, financial statements, and journal entries.
Example pattern
2025-10_TB_AcmeCorp.pdfLegal & compliance
Patterns tuned for how this team actually searches and reconciles documents.
Operations & ops teams
Patterns tuned for how this team actually searches and reconciles documents.
For procurement, vendor management, and business operations teams
Contract File Naming Convention
Standardize contracts with counterparty, agreement type, execution date, and version. Keep procurement, vendor management, and legal review audit-ready.
Example pattern
2025-10-15_MSA_AcmeCorp.pdfFor project managers, product teams, and knowledge workers
Project Documentation Naming Convention
Organize project files with project code, document type, version, and date. Keep team documentation searchable and version control clear.
Example pattern
PROJ-42_Spec_2025-10-15.pdfFor consultants, agencies, and professional services firms
Client File Naming Convention
Name client files by client code, project, document type, and date. Keep deliverables professional and prevent the "final_v3_FINAL" problem.
Example pattern
ACME_BrandRefresh_Report_2025-10-15.pdfResearch & knowledge
Patterns tuned for how this team actually searches and reconciles documents.
Healthcare & medical
Patterns tuned for how this team actually searches and reconciles documents.
Construction & engineering
Patterns tuned for how this team actually searches and reconciles documents.
HR & people ops
Patterns tuned for how this team actually searches and reconciles documents.
Insurance & risk
Patterns tuned for how this team actually searches and reconciles documents.
General & personal
Patterns tuned for how this team actually searches and reconciles documents.
Turn conventions into fully automated workflows
Once you agree on filenames, let AI read PDFs and apply those patterns automatically in Google Drive, Dropbox, or OneDrive. No more manual renaming at month-end.
1. Design your convention
Use the naming convention generator to capture rules once for your team.
2. Connect storage
Point watched folders in Google Drive, Dropbox or OneDrive at the documents you already collect.
3. Let AI apply names
The PDF renamer reads content, extracts dates, entities, and IDs, then writes filenames that match your convention with 95%+ accuracy.