Purchase order naming standard
Name purchase orders as YYYY-MM-DD_PO-Number_Vendor.pdf so every PO is traceable, sortable by date, and matchable to your ERP.
- Lead with PO date (YYYY-MM-DD) for chronological sorting and period filtering.
- Include the PO number as the primary identifier — this is how AP and procurement search for documents.
- Add the vendor legal name (not a nickname) to enable visual filtering when scrolling through folders.
- Optionally append department or cost center for routing and budget tracking.
3.1k purchase orders processed with this naming convention across 28 procurement teams.
Recommended patterns
Standard purchase order pattern
The standard pattern for most procurement workflows. PO number is the primary key; date and vendor provide human-readable context for folder browsing.
YYYY-MM-DD_PO-Number_Vendor.pdf2025-10-15_PO-10234_AcmeSupply.pdfPO with department routing
Adds department or cost center for organizations where POs route through different budget holders. Enables filtering by department.
YYYY-MM-DD_PO-Number_Vendor_Department.pdf2025-10-15_PO-10234_AcmeSupply_MKTG.pdfPO with amount for approval tiers
Leads with PO number for systems where the PO number is the primary lookup key. Amount helps identify POs that need higher approval tiers.
PO-Number_Vendor_Date_Amount.pdfPO-10234_AcmeSupply_2025-10-15_15000.pdfCore principles
PO number is the primary identifier
Every PO has a unique number from your procurement or ERP system. This is how AP matches invoices to POs (three-way matching). It must always be in the filename.
Use the vendor legal name, not nicknames
Name files with the vendor's legal name as it appears on invoices and in your ERP. "AcmeSupplyCo" not "Acme" or "those supply guys." Consistency enables automated matching.
Include department for routing
In organizations with multiple cost centers, the department or cost center code in the filename enables AP to route the PO for approval without opening the document.
Match your ERP naming where possible
If your ERP exports POs as "PO-10234," use that exact format in filenames. This eliminates a translation step during reconciliation and three-way matching.
Date by PO issuance, not receipt or approval
A PO issued October 15 but approved October 20 and received October 25 should be dated 2025-10-15. The issuance date is the canonical date for a purchase order.
Common mistakes
Omitting the PO number entirely
Without the PO number, there is no way to match the document to your ERP record. AP must open every file to find the right PO during invoice matching.
Fix: Always include the PO number: 2025-10-15_PO-10234_AcmeSupply.pdf
Using vendor nickname instead of legal name
"Bob's Supplies" in the filename but "Robert Supply Co LLC" in the ERP means automated matching fails and manual lookup is required.
Fix: Use the exact legal name from your vendor master: 2025-10-15_PO-10234_RobertSupplyCo.pdf
Not including a date at all
POs without dates in the filename make period-end cutoff analysis impossible. You cannot see which POs belong to which fiscal period without opening them.
Fix: Lead with date: 2025-10-15_PO-10234_AcmeSupply.pdf
Using spaces and special characters
Filenames with spaces break ERP import scripts, email attachment handling, and URL encoding. "PO 10234 Acme Supply.pdf" becomes "PO%2010234%20Acme%20Supply.pdf" in URLs.
Fix: Use underscores and hyphens only: 2025-10-15_PO-10234_AcmeSupply.pdf
Automate purchase order naming from PDFs
Renamed.to reads purchase order PDFs, extracts the PO number, vendor name, date, and amount, and applies your procurement team's naming convention automatically. Integrates with Google Drive and Dropbox watched folders.
50 free renames to start. No credit card required.
Frequently asked questions
Should the PO number or date come first in the filename?
If you primarily search by date range (month-end close), lead with date. If you primarily search by PO number (matching to invoices), lead with PO number. Most teams prefer date first for chronological sorting.
How do I handle PO revisions or change orders?
Append the revision: 2025-10-15_PO-10234_AcmeSupply_Rev2.pdf. Alternatively, create a separate file for the change order: 2025-10-20_CO-001_PO-10234_AcmeSupply.pdf.
Should I include the PO amount in the filename?
Optional but useful for approval workflows. If your organization has spending thresholds (e.g., POs over $10k need VP approval), amount in the filename enables quick visual scanning.
What about blanket POs that span multiple months?
Use the original PO date and number for the master PO. For individual releases against a blanket PO, add a release number: 2025-10-15_BPO-5001_Release03_AcmeSupply.pdf.
Can I match PO filenames to my ERP system?
Yes. Use the exact PO number format your ERP generates. If SAP creates PO numbers like "4500010234," use that: 2025-10-15_4500010234_AcmeSupply.pdf. Consistency enables automated reconciliation.
How do I handle POs from multiple subsidiaries?
Add an entity code: 2025-10-15_USLLC_PO-10234_AcmeSupply.pdf. This is critical for multi-entity organizations where the same vendor may supply different legal entities.