← All guides · How-to & workflow
Invoice numbers and dates on an e-invoice: the rules that keep your sequence clean
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
An e-invoice must carry an invoice number (BR-01) and an issue date that is a real ISO date (BR-02) — validation checks both before anything else. Beyond validity, craft matters: numbers should be unique and sequential in a series you can explain, credit notes take their own numbers in the same sequence, and dates on the document drive everything from payment terms to which mandate phase applies to it.
What do the rules require?
BR-01 requires the invoice number (BT-1): 'Invoice number is required.' BR-02 requires the issue date (BT-2) to be present and parseable as an ISO date: 'Issue date must be an ISO date.' In the converter these live in §1 of the form, with the due date and the type code (380/381/384/389). The acceptance computation also keys off the issue date — it is the date input that selects the mandate phase for the invoice.
The number: unique, sequential, explainable
Validation demands only presence, but your ledger demands more: each number used once, in order, with gaps you can explain. Auditors read sequences the way editors read drafts — a duplicate number suggests two invoices sharing an identity; a silent gap suggests a deleted document. Structured invoicing strengthens the point: numbers are now data that clients' systems match payments and credit notes against, so a reused number creates collisions in their system as well as yours.
Choose a scheme and keep it boring: a year-prefixed running series (2026-001, 2026-002…) or a continuous counter, one series per entity. Credit notes belong in the same sequence as invoices — they are documents of the same family, distinguished by their type code (381), not by a parallel numbering universe. If your tooling offers a separate credit-note series, ensure the two series can never collide on the same identifier.
The issue date: the invoice's legal birthday
The issue date is the date the invoice comes into existence, and validation insists it be a real ISO date — 2026-11-14, not 'Nov 14th' or a spreadsheet's serial number. That date starts payment terms running, places the invoice in a VAT period, and — uniquely in the mandate era — selects the law the invoice is judged under: the acceptance checker computes its verdict from the invoice date, so an invoice dated either side of a phase boundary (Poland, 1 April 2026) is literally a different legal object.
Backdating and postdating both corrupt that function. Issue invoices when you issue them; if work spans a boundary and timing matters commercially, that is a conversation with the client about when to invoice, conducted openly — not a quiet edit to BT-2. The date's integrity is what makes the checker's verdict, the payment clock and the tax period agree with each other.
Due dates and the payment chain
The due date rides alongside the issue date in §1: it is the date payment falls due under your terms. It is not validated as elaborately as the issue date, but it is read by the client's payables process as data — a structured invoice with a due date gets scheduled; one without gets queried. State it explicitly on every invoice rather than relying on '30 days' folklore in a covering email, because the system booking your invoice does not read your email.
Keep terms consistent between the document and the relationship: if the contract says 14 days, the due date should be issue date plus 14, computed, not approximated. Discrepancies between the invoice's due date and the agreed terms are a standard source of 'we paid on our terms' delays. The structured era rewards stating the whole agreement inside the document — the document is now the part everyone, and every system, actually processes.
Corrections, credits and the audit trail
When an invoice must change, the numbering discipline decides whether the trail stays clean. A credit note takes the next number in sequence and references the original invoice; a corrected invoice (384) supersedes its original as the operative record. What never happens in a clean system: editing a sent invoice's file in place, reusing its number for the replacement, or deleting the original from the archive. The sequence tells the story — original, credit, reissue — and every document in it validates on its own data.
This is where structured practice quietly outperforms the PDF era. A folder of PDFs can be silently rearranged; a sequence of numbered, validated, archived structured documents — each conversion's files kept with its acceptance stamp — resists rearrangement, because every artefact carries its number, its date and its computed totals as data. Keep both outputs (UBL and Factur-X) per number, and the archive is the audit trail.
Series design for growing firms
Small decisions compound: one series per legal entity (never share a sequence across entities); a series per year or one continuous series — both defensible, switching mid-stream is not; prefixes that mean something stable (INV- for the series, the type code carrying document kind rather than CN- prefixes inventing a second taxonomy). Agencies on Team workspaces should hold the series centrally, so two account managers cannot mint the same number on the same morning.
Finally, reconcile the sequence monthly: every number in the period accounted for as issued, credited or corrected, with the archive matching the list. Ten minutes a month buys the answer to the auditor's first question and the client's 'we seem to be missing invoice…' email. In the structured era your numbers are identifiers in other people's systems; their cleanliness is a form of customer service.
Numbering and dates in 5 steps
- Use one explainable series: unique numbers, issued in order, gaps accounted for — credit notes included in the same sequence.
- Set the issue date to the real day of issue, in ISO format; remember it selects the mandate phase for the invoice.
- State the due date explicitly on the document, computed from your agreed terms.
- Never edit or renumber a sent invoice: credit it (381) or correct it (384) with a new number and a reference.
- Reconcile the sequence monthly against the archive — every number present as a validated document pair.
Worked example: a sequence that tells the story
An agency's March sequence runs 2026-031 to 2026-047. Invoice 2026-038, EUR 4,560.00 to a German client, is found to carry the wrong buyer address after sending. The agency does not touch the file. It issues credit note 2026-048 (type 381) mirroring 2026-038's lines, then invoice 2026-049 with the corrected address and the same EUR 4,560.00 — each document validated, each with its own date.
An auditor reading the sequence sees the whole event without asking a question: original, reversal, corrected reissue, amounts tying to the cent. The same event in a PDF folder — original quietly replaced — would read as a discrepancy. Numbering discipline is narrative discipline: the sequence is the story of your billing, written so strangers can follow it.
Frequently asked questions
Can I reuse an invoice number if the first invoice was never sent?
Validation only requires a number to be present, but ledger hygiene says a number once attached to a document stays attached. If it truly never left your system, document the void in your sequence reconciliation; never reuse a number that reached a client.
Does a credit note get its own number?
Yes — its own number in the same sequence, its own issue date, and a reference to the original invoice. Its type code (381) is what marks it as a credit.
Why does the issue date matter for mandates?
The acceptance checker computes the verdict from the invoice date: an invoice dated before a phase boundary and one dated after it carry different obligations for the same client.
What date format is required?
A real ISO date (YYYY-MM-DD). BR-02 rejects missing or unparseable issue dates.
Can I backdate an invoice to fall in an earlier period?
The issue date should be the true date of issue — it drives payment terms, tax periods and mandate phases. Timing of invoicing is a commercial conversation with the client, not an edit to BT-2.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- How to issue a credit note as an e-invoice (type code 381)
- Invoice type codes 380, 381, 384 and 389: what each one means
- EN 16931 business rules explained: what BR codes mean when validation fails
- The acceptance checker explained: how a verdict is computed from date, country and size
- Convert your first invoice free: a walkthrough of the one-invoice job