Invoice numbers

The habit of giving every piece of paper a number belongs to double-entry bookkeeping, and the oldest surviving records of that practice are Italian. A ledger kept for Giovannino Farolfi & Company, a firm of Florentine merchants headquartered in Nîmes whose most important customer was the Archbishop of Arles, covers 1299–1300 and is the earliest surviving set of records in full double entry; the name of the merchant who kept it, Amatino Manucci, survives with it.

Luca Pacioli, a Franciscan friar and collaborator of Leonardo da Vinci, put the method into print. His Summa de arithmetica, geometria, proportioni et proportionalità (Venice, 1494) devotes a treatise — Particularis de computis et scripturis — to what he called the Venetian method: a memorandum, a journal and a ledger, with every entry cross-referenced between them. He is often called the father of accounting, and the careful version of the claim is that he was the first to publish a detailed description, not the first to write one: Benedetto Cotrugli, a Ragusan merchant and ambassador to Naples, had described double entry in a treatise composed in 1458 that went unprinted until 1573, by which time its printer had cut and garbled the relevant passages. What Pacioli insisted on was that entries be dated, ordered and traceable, because an account nobody can trace is an account nobody can audit. Werner Sombart's later claim that double-entry bookkeeping made modern capitalism possible has been argued over by economic historians ever since and is not a settled result.

Numbering became law much later. Article 226 of Council Directive 2006/112/EC, the EU VAT Directive, lists the details a VAT invoice must carry, and point (2) asks for "a sequential number, based on one or more series, which uniquely identifies the invoice". Member states wrote the rule into their own codes; Germany's Umsatzsteuergesetz, in §14(4), calls it a fortlaufende Nummer — a running number assigned once and only once. The purpose is completeness rather than tidiness. If a series has no gaps, a missing invoice is visible to anyone who counts, and a business cannot quietly drop a sale from its records. Whether a gap by itself invalidates a series is a question of national case law, not of the Directive, and several tax authorities now certify billing software instead of reconstructing sequences after the fact.

Key properties

• Article 226(2) of Council Directive 2006/112/EC requires a VAT invoice to carry "a sequential number, based on one or more series, which uniquely identifies the invoice".
• The phrase "based on one or more series" is what makes per-year or per-branch prefixes lawful: INV-2026-00001 and CN-2026-00001 are two series, each sequential within itself.
• Nothing in the Directive fixes a format — the prefix, the separators, the field widths and the starting value are all the issuer’s choice.
• Ledgers kept in full double entry survive from 1299–1300, nearly two centuries before Luca Pacioli published the first detailed printed description of the method in 1494.
• The pattern fields are {SEQ:n} for the padded counter, {YYYY} and {YY} for the year, {MM}, {DD} and {Q} for month, day and quarter, {N:n} for random digits, {A:n} for random letters and {X:n} for random letters and digits.
• The counter is held as an arbitrary-precision integer, so a series continued from 90071992547409910001 increments exactly; the same value in a double-precision number would round to the nearest representable integer.
• Year, month and day are inputs rather than clock readings, so the same link renders the same references indefinitely.
• A gapless series is an audit control, not a privacy measure: two invoices from the same series disclose how many were issued between them.

Where they turn up

• VAT invoices across the European Union, and in the United Kingdom under rules inherited from the same Directive, must carry a uniquely identifying sequential number.
• Digital tax audits routinely run a gap analysis over invoice series — a run of numbers with holes in it is the cheapest possible red flag, which is the whole reason the sequence is required.
• Accounting packages auto-increment the next number on a new invoice and keep credit notes in a separate series, so that a refund never consumes a sales number.
• European e-invoicing formats such as Peppol BIS Billing 3.0 and Italy’s Sistema di Interscambio treat the invoice number as a mandatory field in the document schema.
• Forensic accountants apply Benford’s law to invoice amounts, not to invoice numbers: a sequential series is uniform by construction and would fail the test trivially without anything being wrong.
• QA and demo environments need references that look plausible in a PDF or a list view without pointing at a real transaction, which is what this page produces.