# What Is an Invoice Number? Formats, Examples, and Numbering Rules

> An invoice number is the unique ID that tracks each invoice for accounting and tax. Learn invoice number formats, examples, sequential numbering rules, and fixes.
- **Author**: Deepak Jangir
- **Published**: 2026-09-30
- **Category**: Billing, Finance
- **URL**: https://dodopayments.com/blogs/en/invoice-number

---

An invoice number is a unique identifier assigned to each invoice a business issues, used to track that invoice through accounting, payment collection, and tax audits. No two invoices from the same seller should ever share an invoice number, and in most tax systems the numbers must follow a sequence.

The invoice number ties together your ledger, your bank deposits, your customer's payables system, and your tax filings. When numbering is sloppy, reconciliation breaks and audits get harder.

This guide covers what an invoice number is, the most common invoice number formats with examples, the rules for sequential numbering, what to do when you make a mistake, and how numbering works when a SaaS business issues thousands of invoices a month through automated renewals.

## What Is an Invoice Number and Why It Matters

Think of the invoice number as the primary key of your billing records. Every other field can repeat across documents. The invoice number cannot.

That uniqueness does real work in five places.

- **Audit trail.** Tax authorities and auditors check that invoice sequences are complete. A clean sequence shows that every sale was recorded and none were quietly removed.
- **Tax compliance.** Many VAT and GST regimes make a unique, sequential number a mandatory invoice field. An invoice without one may not count as a valid tax invoice, which can block your customer from reclaiming input tax.
- **Reconciliation.** When a payment lands in your bank account, the invoice number in the remittance reference is how you match cash to the open receivable. Our guide to [payment reconciliation for SaaS](https://dodopayments.com/blogs/payment-reconciliation-saas) covers this matching process in depth.
- **Dispute handling.** When a customer questions a charge, "invoice 2026-0412" resolves the conversation in one line. "The invoice from sometime in March" does not.
- **Accounts receivable.** Aging reports, collection emails, and payment reminders all reference invoice numbers. A well-structured [accounts receivable process](https://dodopayments.com/blogs/accounts-receivable-saas-guide) depends on every open item having a clear identifier.

Buyers use invoice numbers to catch duplicates before paying, so a repeated number can get a legitimate invoice rejected or paid twice.

## Invoice Number Format: Common Numbering Schemes

There is no single mandatory invoice number format. Most jurisdictions care that the number is unique and sequential, not what it looks like. That leaves room to encode useful information such as the year, the customer, or the business entity.

Here are the six schemes you will see most often, with an invoice number example for each.

| Scheme | Invoice number example | Pros | Cons |
| --- | --- | --- | --- |
| Simple sequential | 0001, 0002, 0003 | Easiest to implement, gaps are obvious | Reveals total invoice volume, no context in the number |
| Year-prefixed | 2026-0001, 2026-0002 | Easy to sort by year, common in the EU | Need a rule for whether the counter resets each year |
| Customer-coded | ACME-0001, ACME-0002 | Instantly shows who the invoice belongs to | Requires a global sequence too, or numbers can collide across customers |
| Project-coded | PRJ104-001, PRJ104-002 | Good for agencies and services billing per project | Harder to prove a single complete sequence |
| Date-based | 20260930-01, 20260930-02 | Date is embedded, easy to read | Long, and the daily suffix still needs a counter |
| Multi-series by entity or brand | US-2026-0001, EU-2026-0001 | Separates legal entities, brands, or document types | More series to track and keep gapless |

A few practical notes on choosing between them.

**Pad your numbers.** Use a fixed width such as 0001 or 000001 so invoices sort correctly in spreadsheets and file systems. Without padding, invoice 10 sorts before invoice 2.

**Year prefixes and resets.** If you use a year-prefixed invoice number format like 2026-0001, decide up front whether the counter restarts at 0001 each January. Both approaches are common. The year prefix keeps the full number unique even when the counter resets, which is why this format is popular with European businesses.

**Keep the sequence the source of truth.** Customer and project codes are useful labels, but they should sit alongside a sequential counter, not replace it. ACME-2026-0147 works because 0147 is still part of a single running sequence.

## Sequential Invoice Numbering Rules

Whatever format you choose, a few rules apply almost everywhere.

### Every number must be unique

Two invoices must never share a number within the same series. This is the one rule with no exceptions. If you run multiple series (say one per legal entity), the prefix is what keeps numbers unique across series.

### Numbers should be sequential

Most tax regimes expect invoice numbers to follow a consecutive sequence. In the European Union, the VAT Directive (Article 226) requires a sequential number, based on one or more series, which uniquely identifies the invoice. That "one or more series" wording is important: it means EU businesses can run separate sequences, for example by branch or by document type, as long as each series is itself sequential and every number is unique.

The UK follows a similar principle. A VAT invoice needs a unique invoice number that follows on from the previous one. Individual countries layer their own details on top, so if you invoice in several markets, check each country's specific requirements or use a provider that handles them for you.

### Can invoice numbers be skipped?

In short, you should avoid it. A gap in the sequence is exactly what auditors look for, because a missing number can indicate an invoice that was issued and then deleted to hide revenue. In jurisdictions with strict sequential rules, unexplained gaps can trigger questions during a tax audit.

Gaps do sometimes happen for innocent reasons, such as a system crash mid-issue or a draft that consumed a number. If one occurs, document it: record which number was skipped, when, and why. A documented gap is an administrative note. An unexplained one is a red flag.

### Never reuse a number

Once an invoice number has been issued, it belongs to that invoice permanently, even if the invoice is later cancelled. Reusing a voided number breaks the audit trail and can confuse your customer's payables team, who may already have the original recorded.

### Credit notes get their own series

When you reduce or reverse an invoice, you issue a credit note (also called a credit memo) rather than editing the original. Credit notes should carry their own sequence, such as CN-2026-0001, and reference the invoice number they correct. Our guide to the [credit memo](https://dodopayments.com/blogs/credit-memo) explains when to issue one and how it differs from a refund.

## Where the Invoice Number Goes and What Else Belongs on an Invoice

Place the invoice number near the top of the document, next to the issue date, since it is what your customer will quote when they pay.

The invoice number is only one of the required fields. A compliant invoice typically includes:

- Invoice number (unique and sequential)
- Issue date, and the supply date if different
- Seller's legal name, address, and tax registration number
- Buyer's name and address, plus their tax ID for B2B sales where required
- Description and quantity of goods or services
- Unit price, net amount, tax rate, and tax amount
- Total amount due and the currency
- Payment terms and due date
- Any required legal notes, such as a reverse charge statement

Tax IDs deserve special attention in cross-border B2B sales. Our explainer on [what a VAT number is](https://dodopayments.com/blogs/what-is-a-vat-number) covers formats and validation, and the guide to [reverse charge VAT](https://dodopayments.com/blogs/reverse-charge-vat) explains when the buyer rather than the seller accounts for the tax.

Not every document with a number on it is an invoice. A proforma invoice is a preview sent before the sale is final and should be clearly marked as such, usually without consuming a number from your official sequence. See [proforma invoice vs invoice](https://dodopayments.com/blogs/proforma-invoice-vs-invoice) for the full comparison. Similarly, a receipt confirms payment after the fact, which we break down in [invoice vs receipt](https://dodopayments.com/blogs/invoice-vs-receipt).

## Invoice Number vs Purchase Order Number and Other References

Invoices often carry several reference numbers, and mixing them up is a common source of payment delays. Here is how the invoice number compares to the others.

| Reference | Who creates it | What it identifies | When it appears |
| --- | --- | --- | --- |
| Invoice number | Seller | A specific demand for payment | On the invoice, at the point of sale or billing |
| Purchase order (PO) number | Buyer | The buyer's internal approval to purchase | Sent before the sale, then quoted on the invoice |
| Receipt number | Seller | Confirmation that a payment was received | After payment |
| Order ID | Seller's store or system | A customer order, which may produce one or more invoices | At checkout |
| Payment or transaction ID | Payment processor | A single movement of money | When the charge is processed |

The key distinction in invoice number vs purchase order number: the PO comes from the buyer and represents their permission to spend, while the invoice number comes from you and represents your request to be paid. Many enterprise customers will not pay an invoice that does not quote their PO number, so include it as a separate field whenever one is supplied. Never replace your invoice number with their PO number, since one PO can cover many invoices.

## How to Handle Invoice Mistakes Without Breaking the Sequence

Mistakes happen: a wrong amount, a missing tax ID, the wrong address. Once an invoice has been issued, do not edit or delete it. Leave it in place and issue a correcting document.

```mermaid
flowchart LR
    A["Invoice 2026-0147 issued"] --> B["Error found"]
    B --> C["Issue credit note CN-2026-0012 referencing 2026-0147"]
    C --> D["Issue corrected invoice 2026-0148"]
    D --> E["Books and tax records stay complete"]
```

The standard process looks like this:

1. **Keep the original invoice.** Mark it as cancelled or voided in your system, but do not delete it. Its number stays used.
2. **Issue a credit note** that references the original invoice number and reverses the full amount (or the incorrect portion).
3. **Issue a new invoice** with the next number in the sequence and the correct details.
4. **Tell the customer** which invoice to pay, quoting both numbers so their payables team can match everything.

Worked example: you issue invoice 2026-0147 for $1,200 but should have billed $1,000. You issue credit note CN-2026-0012 for $1,200 against 2026-0147, then new invoice 2026-0148 for $1,000. Alternatively, a partial credit note for $200 against 2026-0147 achieves the same net result with one fewer document. Either approach keeps the sequence intact and leaves a clear record of what happened.

The only exception is a draft that was never sent or recorded, which is why many systems assign the final number only at finalization.

## How to Number Invoices Automatically in SaaS Billing

Manual invoice numbering works for a freelancer sending ten invoices a month. It falls apart for a SaaS company where every subscription renewal produces a new invoice. A product with 5,000 monthly subscribers generates roughly 5,000 renewal invoices every month before counting upgrades, one-time purchases, and add-ons.

At that scale, how to number invoices stops being a spreadsheet question and becomes a systems question:

- **Numbers must be assigned atomically.** If two renewals process at the same instant, the system must never hand both the same number. Spreadsheets and naive database counters fail here.
- **Every successful payment needs its own invoice.** Monthly renewals, prorated upgrades, and usage charges each produce a separate document with its own number.
- **Refunds need linked documents.** Each refund should generate its own credit document that points back to the original invoice.
- **Numbers must map to payment IDs.** Your finance team needs to go from a bank deposit to a payment to an invoice without manual lookup.

This is why most SaaS teams move to [automated invoicing](https://dodopayments.com/blogs/automated-invoices-saas) early, letting the billing system assign numbers and keep the sequence complete. If you sell internationally, [e-invoicing mandates](https://dodopayments.com/blogs/e-invoicing-compliance-global-saas) in a growing number of countries add structured data requirements on top of the numbering rules.

## How Dodo Payments Generates Invoices Automatically

Dodo Payments acts as a [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record), which means Dodo is the legal seller on each transaction and handles the tax obligations that come with invoicing. Per the [invoice generation documentation](https://docs.dodopayments.com/features/invoice-generation), an invoice is generated automatically for every successful transaction, covering both one-time purchases and every subscription renewal. You never assign numbers or build invoice templates yourself.

Each invoice includes the tax breakdown, customer details, and product details, and can be branded with your company logo and brand name through your Business Profile. For B2B buyers, checkout supports purchasing as a business with a Business Tax ID. Dodo validates the tax ID, and with a valid ID the invoice shows the customer's tax ID and marks reverse charge where the law applies. The [B2B payments guide](https://docs.dodopayments.com/features/b2b-payments) covers the details.

You can download any invoice PDF from Transactions, then Payments in the dashboard, and refunds have their own "Download Refund Invoice" option under Transactions, then Refunds. Customers can access their billing history and download invoices from the Customer Portal. The [refunds documentation](https://docs.dodopayments.com/features/transactions/refunds) explains how refund documents are produced.

If your finance system needs a copy of every invoice, you can fetch the PDF by payment ID with the [Get Invoice API](https://docs.dodopayments.com/api-reference/payments/get-invoice). A common pattern is to trigger this from a `payment.succeeded` [webhook](https://docs.dodopayments.com/developer-resources/webhooks) and archive the file keyed by payment ID:

```typescript
import DodoPayments from 'dodopayments';

const client = new DodoPayments({
  bearerToken: process.env.DODO_PAYMENTS_API_KEY,
  environment: 'test_mode',
});

// Called from your payment.succeeded webhook handler
async function archiveInvoice(paymentId: string) {
  const invoice = await client.invoices.payments.retrieve(paymentId);
  const pdf = await invoice.blob(); // application/pdf

  // Store under the payment ID so finance can go from payment to invoice directly
  await financeStorage.put(`invoices/${paymentId}.pdf`, pdf);
}
```

Because the invoice is keyed to the payment, reconciliation becomes a lookup rather than a search.

## FAQ

### Is an invoice number the same as an invoice ID?

In everyday use, yes. Both refer to the unique reference that identifies a specific invoice. Some software shows an internal database ID separately from the customer-facing invoice number, in which case the invoice number is the one that must follow your sequential numbering rules.

### Can I use letters in an invoice number?

Yes. Most jurisdictions allow letters, numbers, and separators such as hyphens, so formats like INV-2026-0001 or EU-0042 are common. What matters is that each invoice number is unique and the numeric sequence within each series is consecutive.

### Should invoice numbers restart every year?

It is your choice in most countries. Restarting at 0001 each year works well with a year prefix like 2026-0001, because the prefix keeps every full number unique. A continuous counter that never resets is equally valid and slightly simpler to audit.

### Do I need separate invoice number series for different businesses?

If you operate multiple legal entities, each one should have its own invoice series, because each entity is a separate seller with its own books and tax registrations. Within one entity, separate series by brand or document type are also allowed in many jurisdictions, including under EU VAT rules, as long as each series is sequential.

### What invoice number should my very first invoice use?

Any starting point works, as long as numbers only move forward from there. Many businesses start at 1001 so a new customer does not see "invoice #1", or use a year-prefixed format like 2026-0001.

## Conclusion

An invoice number is a small field with a large job. It makes every invoice uniquely identifiable, keeps your audit trail complete, lets your customers pay the right document, and connects cash in the bank to revenue in the ledger. Pick a clear invoice number format, keep it unique and sequential, never reuse or delete numbers, and correct mistakes with credit notes rather than edits.

For SaaS businesses, the practical answer is to stop numbering invoices by hand. With [Dodo Payments](https://dodopayments.com), an invoice is generated automatically for every successful payment and renewal, with tax handled under a Merchant of Record model. Invoicing is included at no extra cost, so see the [pricing page](https://dodopayments.com/pricing) for the full fee breakdown.
---
- [More Billing articles](https://dodopayments.com/blogs/category/billing)
- [All articles](https://dodopayments.com/blogs)