Yes, invoice numbers can have letters. Federal law places no restriction on the format of an invoice number, so letters, digits, or any mix of the two are acceptable. What matters is that each number is unique and that you can tie every invoice back to the underlying transaction if the IRS asks.
What Federal Law Says About Invoice Format
The tax code does not tell you how to format an invoice number. Under 26 U.S.C. ยง 6001, taxpayers must keep whatever records the Secretary of the Treasury considers sufficient to show tax liability.1Office of the Law Revision Counsel. 26 U.S. Code 6001 – Notice or Regulations Requiring Records, Statements, and Special Returns The statute is silent on character type, length, or sequencing. Your obligation is to maintain records that clearly connect each invoice to income received, so you can substantiate what appears on your return.
In practice, two things matter. Every invoice number should be unique, and you should be able to trace it to its payment. Duplicate numbers create ambiguity about whether a transaction happened once or twice. Gaps in a sequence can raise questions about unreported income. Letters, on their own, cause neither problem.
Building an Alphanumeric Invoice Number
The value of adding letters is that they can carry information. A well-designed identifier tells anyone glancing at it who the client is, which team issued the invoice, or when the work was billed. Common building blocks include:
- A client prefix of two or three letters. An invoice for Acme Corp might start with “ACM,” which makes filtering by customer easy in accounting software.
- A department prefix such as “MKT” for marketing, “ENG” for engineering, or “SAL” for sales, so revenue can be tracked by team without a separate report.
- A date segment like “2601” for January 2026, placed before or after the sequence, tying each invoice to a billing period.
- A sequential number that increments with each new invoice. Assembled together, “ACM-2601-0042” is the 42nd invoice issued to Acme Corp in January 2026.
- A project suffix for businesses managing multi-year engagements where a single client receives dozens of invoices tied to different contracts.
Pick a structure and hold to it. Switching formats mid-year or across departments makes reconciliation harder and weakens the audit trail you have to maintain under federal recordkeeping rules.
Character Limits in Accounting and Payment Systems
Your format has to fit inside the technical limits of the tools you use. Exceeding them can cause silent truncation, where the receiving system stores a shortened version that no longer matches your books.
- QuickBooks caps the invoice number field at 11 characters. “ACM-2601-42” fits; adding a project suffix would not.2Intuit QuickBooks. Character Limitations for Fields in QuickBooks
- Stripe requires custom invoice prefixes to be between 3 and 12 characters, and each prefix must be unique across your entire account, including ones you previously used and later retired.3Stripe Documentation. Customize Invoices
- ACH and bank transfer remittance fields have fixed lengths. Long invoice numbers can be cut off in transit through banking networks, causing reconciliation failures on the receiving end.
Hyphens and underscores work as separators in most platforms. Avoid asterisks, percentage signs, ampersands, and similar special characters, because database-driven systems can read them as code and trigger validation errors. Uppercase letters, digits, and hyphens are the safe combination.
Why Letters Improve Security
Purely sequential numbers leak information. A customer who receives invoice 1001 in March and invoice 1087 in April can estimate that you issued around 86 invoices that month. Anyone with visibility into a handful of invoices over time can piece together transaction volume.
Alphanumeric systems disrupt that pattern. Letter-based prefixes, embedded project codes, or non-sequential numbering within lettered categories break the arithmetic that makes volume estimation possible. The same disruption also helps you spot fraudulent invoices: when every legitimate document follows a recognizable pattern, a fake using random formatting stands out on review.
Cross-Border and Government Invoices
Letters are also accepted outside U.S. domestic billing. Article 226(2) of the EU VAT Directive (2006/112/EC) requires a sequential number that uniquely identifies each invoice, and that number may contain alphanumeric characters.4Peppol BIS Billing. ubl:Invoice – Peppol BIS Billing 3.0 The Peppol network for electronic invoicing treats the invoice number as a string, accepting letters, digits, and separators like hyphens and colons. A domestic alphanumeric system usually carries over to cross-border e-invoicing without changes.
For invoices to the U.S. federal government, FAR 52.232-25 requires an invoice date and invoice number but sets no format rules for the number itself. Alphanumeric numbers are accepted. The practical risk is content, not character type: an invoice missing required information will be returned by the billing office within seven days, delaying payment under the Prompt Payment Act.5Acquisition.GOV. FAR 52.232-25 Prompt Payment