Invoice numbers: format and examples

Choose a format you can maintain

A simple sequence is often easier to manage than a long reference packed with information. For example, INV-0001, INV-0002 and INV-0003 are readable references. A year can help organize files, as in INV-2026-001.

The examples show organizational choices, not a statement of legal requirements. Check local rules where sequential or other specific numbering requirements apply.

Three numbering examples

Keep numbers separate from other references

A purchase-order number comes from the customer’s buying process. An invoice number identifies your invoice. Include both when required, but avoid replacing one with the other without checking what the customer expects.

A bank payment reference can repeat your invoice number so the incoming transfer is easier to match. Ask the customer to include it in the payment note.

Prevent duplicates and confusing revisions

Check your register before issuing a new document. If you have several people or devices creating invoices, agree who allocates references and where they are recorded. A browser history on one device cannot coordinate numbering across a team.

If a document needs correction, keep a record of the original and the correction. The right process for a cancellation, replacement or credit document depends on the transaction and local requirements. Avoid silently reusing an old reference for unrelated work.

Using the invoice-number field

Go Invoice Maker starts a new invoice with a generated reference, and you can edit the Invoice # field. The generated value is not a centralized sequence or a guarantee of uniqueness across devices. Replace it with your chosen issued reference and check your records.

Keep the same reference in the PDF filename, your email subject and the payment instructions. Retain a separate issued-invoice register because browser history is device-specific and can be cleared.