Invoice File Naming Convention: Template & Examples BLANK WORKSHEET INVOICE FILE NAMING STANDARD Standard ID / version / effective date / owner: [details] Scope: [outgoing invoice PDFs / destination / exclusions] 1. FIELD RULES Pattern: [client_invoiceID_issueDate_vNN.pdf, adapted if needed] Client label or code / controlled mapping location: [rule / reference] Actual invoice ID source / original-to-filename mapping: [details] Date basis: [issue date printed on the invoice, YYYY-MM-DD] Version range / padding / version-register reference: [rule / reference] Separators / allowed characters / agreed length: [rule] Non-Latin labels / stable code mapping: [rule / reference] Destination path and platform checks: [actual checks] Information excluded from names: [bank details / contact details / tokens] 2. COLLISION CHECK AND DECISION Original client identity | original invoice ID | candidate filename [rows] Existing file / case-insensitive match / identity comparison: [details] Decision: [same unchanged file / distinct clients / document revision / unresolved] Stable code or approved version decision / authority: [details] Resolved filename / retained existing file reference: [details] Unresolved exception / owner / next action: [details] 3. RELEASE AND ARCHIVE RECORD PDF opened: client / invoice ID / issue date match: [check] Content approval or correction reference / current version: [details] Original export filename / source file reference: [details] User-managed archive alias, if any: [details] Exact sent attachment name / actual delivery reference: [details] Prior versions retained / reviewer / date: [details] FILLED EXAMPLE (fictional) Fictional NAMING-1 v1, effective 2026-10-26; owner Morgan. Scope: user-managed archive of outgoing invoice PDFs. Pattern: client_invoiceID_issueDate_vNN.pdf. Underscores separate fields. Example label handling: ASCII letters/numbers retained; separator runs become hyphens; edge hyphens removed. Non-Latin client names use a stable approved ASCII code, with original identity retained in the controlled register and PDF. The archive owner confirms field lengths and destination path compatibility before adoption. Bank/contact details and access tokens stay outside filenames. COLLISION EXAMPLE Original client A: Northstar / Ops; invoice INV-441; issued 2026-10-02; v1. Original client B: Northstar: Ops; invoice INV-441; issued 2026-10-02; v1. Both initially suggest Northstar-Ops_INV-441_2026-10-02_v01.pdf. Decision: distinct fictional clients. Stop filing; do not overwrite. Controlled register CLIENT-1 assigns NS01 to A, NS02 to B. Resolved A: NS01_INV-441_2026-10-02_v01.pdf. Resolved B: NS02_INV-441_2026-10-02_v01.pdf. Both remain v01. Reviewer checks the PDF identities against CLIENT-1. VERSION EXAMPLE — SAME CLIENT AND INVOICE Later authorized change for A is recorded under CHANGE-1 / APP-1. New file: NS01_INV-441_2026-10-02_v02.pdf; v01 retained. If this version is actually sent, retain its exact attachment name and actual delivery evidence in the version register. Do not fill a planned send as completed. An unchanged file renamed for the archive is recorded as an alias, without inventing a content revision. CURRENT PRODUCT NAMING — SEPARATE ILLUSTRATION For InvoiceAgent invoice number 441 and recipient Northstar Ops: Browser PDF suggested filename: invoice-441.pdf. Google Drive sync filename: Invoice 441 - Northstar Ops.pdf. This standard does not configure either format or rename existing files. Keep any user-managed archive alias beside the original export name. BEFORE USE Replace every bracketed field. Examples are illustrative. Confirm your agreement, local invoice requirements, and applicable tax treatment separately. This download does not send an invoice or update a billing record. Source page: https://www.getinvoiceagent.com/templates/invoice-file-naming-standard Reviewed: 2026-10-26