Expense naming standard
Standardize expense receipts with employee name, vendor, date, and amount.
Keep reimbursements audit-ready and reconciliation fast.
For operations, finance admins, and expense management teams
4.2k expense receipts processed last month with this pattern at 95.6% confidence across 38 teams.
Expense naming standard
Name expense receipts as YYYY-MM-DD_Employee_Vendor_Amount.pdf for instant reimbursement matching and policy enforcement.
- Lead with date (YYYY-MM-DD) so expense reports sort chronologically by transaction date.
- Include employee name and vendor to surface who spent what without opening files.
- Append amount to catch policy violations and duplicate submissions visually.
4.2k expense receipts processed last month with this pattern at 95.6% confidence across 38 teams.
Recommended patterns
Standard expense receipt pattern
Lead with transaction date for chronological sorting. Include employee and vendor for visual search and policy enforcement.
YYYY-MM-DD_Employee_Vendor_Amount.pdf2025-10-15_JohnSmith_Uber_42.50.pdfCompact expense receipt pattern
Compact YYYYMMDD format saves filename length while maintaining chronological sorting. Ideal for systems with character limits.
YYYYMMDD_Employee_Vendor_Amount.pdf20251015_JohnSmith_Uber_42.50.pdfExpense with category tag
Append expense category in brackets for GL coding and policy enforcement before exporting to ERP.
YYYY-MM-DD_Employee_Vendor_Amount_[Category].pdf2025-10-15_JohnSmith_Uber_42.50_[Travel].pdfMulti-department expense pattern
Add department code after date for multi-department expense management and budget tracking.
YYYY-MM-DD_Dept_Employee_Vendor_Amount.pdf2025-10-15_MKTG_JohnSmith_Uber_42.50.pdfCore principles
Start with transaction date
YYYY-MM-DD ensures receipts sort by expense date, not submission date. Critical for monthly close and accrual accounting.
Include employee or cardholder name
Employee name surfaces who submitted the expense without opening files. Essential for reimbursement workflows and policy violations.
Always include vendor name
Vendor identification enables policy enforcement (meals, travel, subscriptions) and duplicate detection visually.
Add amount for policy enforcement
Amount in filename catches over-limit expenses and duplicate submissions before they reach finance approval.
Use department codes for cost allocation
Department or project codes enable budget tracking and GL mapping without opening every receipt.
Never embed personal information
Avoid SSN, credit card numbers, or sensitive data in filenames. These appear in logs and metadata.
Common mistakes
Using submission date instead of transaction date
Employees submit receipts weeks after transactions. Submission dates break chronological sorting and monthly reconciliation.
Fix: Always use transaction date from the receipt: 2025-10-15_JohnSmith_Uber_42.50.pdf
Omitting employee or cardholder name
Impossible to identify who submitted an expense without opening files. Reimbursement workflows grind to a halt.
Fix: Include employee name after date: 2025-10-15_JohnSmith_Uber_42.50.pdf
Using "Receipt.pdf" or "IMG_1234.pdf"
Generic filenames provide zero context. Every receipt overwrites the previous one in email downloads.
Fix: Include date, employee, vendor, and amount: 2025-10-15_JohnSmith_Uber_42.50.pdf
Adding version numbers or approval status
receipt_v2_approved.pdf signals poor workflow control. Use expense management systems for approval status.
Fix: Single filename with transaction metadata. Track approval in Expensify, Navan, or ERP, not filenames.
Leaving spaces in filenames
Spaces break email attachments, scripts, and ERP imports. Files appear as receipt%20scan.pdf in URLs.
Fix: Replace spaces with underscores: 2025-10-15_JohnSmith_Uber_42.50.pdf
Frequently asked questions
Should I include currency in the amount?
Optional. If all expenses are in the same currency, omit it. For multi-currency workflows, append currency code: 42.50-USD.pdf.
Can I use decimals in the amount field?
Yes, periods are safe in filenames and won't cause errors on Windows, macOS, or cloud storage. Use standard decimal format: 123.45.pdf. Avoid commas in amounts as they can cause issues in some systems.
What if employees submit multiple receipts from the same vendor on the same day?
Append a sequence number or transaction time: 2025-10-15_JohnSmith_Uber_42.50_01.pdf and 2025-10-15_JohnSmith_Uber_38.25_02.pdf.
Can I use this pattern for corporate card statements?
Yes. Use YYYY-MM-DD_Employee_CorporateCard_Statement.pdf for monthly statements. Individual receipts follow the standard pattern.
How do I handle image-based receipts vs PDF receipts?
Same pattern works for .jpg, .png, and .pdf files. Just change the extension: 2025-10-15_JohnSmith_Uber_42.50.jpg.
Should I rename receipts before or after approval?
Rename immediately after receipt capture. Consistent filenames enable faster approval and policy enforcement before submission.