Unique, readable, consistent
Invoice Numbering Guide
An invoice number should let you and the recipient refer to one exact document. A simple sequence is usually easier to maintain than a code that tries to encode every detail.
Only an approved preset and interface language cross to the editor. No invoice fields are passed.
Choose a stable pattern
Examples include 2026-001, INV-2026-001, or a continuous sequence such as INV-1042. Pick one pattern, document how it advances, and avoid reusing a number for a different invoice.
Keep identifiers private enough
A client code can help internal filing, but avoid names, tax identifiers, health information, or confidential project labels in a number that may appear in email subjects and payment systems.
Corrections and replacements
Retain a record of what was sent. If an invoice must be corrected, follow the process required by your agreement and applicable rules rather than silently reusing the same PDF without a record.
What the editor supplies
A new local draft receives an initial readable number that you can replace. The editor does not maintain an account-wide sequence, detect duplicates across deleted drafts, or serve as an accounting ledger.