How Should You Number Receipts? 4 Systems That Scale

Number receipts with any format you can sustain — the rules matter more than the scheme: every receipt gets a number, numbers never repeat, sequences never skip silently, and voided numbers are kept and marked rather than reused. Four formats cover almost every small business: plain sequence, year-prefixed, date-based, and client-coded. Pick by volume and whether humans need to read meaning into the number.

Why numbering exists at all

A receipt number makes each transaction uniquely referenceable — for customer lookups, refunds tied to originals, and above all bookkeeping: an unbroken sequence proves your ledger is complete. Auditors read gaps as missing income and duplicates as sloppiness or worse; a clean series is quiet evidence of clean books, which is the whole game in recording receipts in bookkeeping. (What the numbers mean on big-retail receipts — store, register, sequence — is covered in what is a receipt number.)

System 1: plain sequence (0001, 0002, …)

The default. Works at any volume, sorts naturally, and gaps are instantly visible. Its one weakness: the number carries no information — fine for software, mildly annoying for humans flipping paper. Zero-pad to at least four digits so filenames sort.

System 2: year prefix (2026-0041)

Resets each January; numbers stay short and every receipt self-dates to a year. The sweet spot for service businesses issuing tens to hundreds annually — "2026-0041" reads as "41st receipt of 2026" with no lookup. Handles the year-boundary audit question ("how many receipts in 2026?") by construction.

System 3: date-based (260721-03)

YYMMDD plus a daily counter. Encodes the full date, sorts chronologically as text, and suits businesses with several-per-day volume — market vendors, food stalls, service calls. Slightly longer to write by hand; trivially generated by software.

System 4: client or job codes (ACME-2026-07)

For freelancers and contractors with repeat clients: prefix by client or job, then year, then sequence. The number becomes a filing system — every Acme receipt findable by its prefix — and pairs naturally with the deposit-progress-final chains described in partial payment receipts. Keep a master log so prefixes don't collide.

The rules that make any system audit-proof

1. No reuse, ever — including voids: mark "VOID," keep the copy, move on. A missing number with no void record is the classic audit question.
2. One series per system of record — if you run a receipt book alongside software, prefix book receipts ("B-") into the same logical sequence, per the hybrid setup in receipt book vs. digital.
3. Assign at issuance, not later — numbering retroactively is how duplicates happen.
4. Log everything — number, date, payer, amount, status. The log is what turns the numbers into proof.

Common mistakes

Starting at 0001 publicly (start at 1001 if optics bother you — gap-free from there is what matters), restarting sequences mid-year after a software change without documenting the cutover, and letting refunds share the original's number (refunds get their own number, referencing the original).

The bottom line

Pick the simplest format your volume allows — sequence or year-prefix for most — and enforce the four rules without exception. The receipt generator assigns and remembers numbers automatically; the sales receipt template shows the number placement customers expect.