Free tier

← All guides · How-to & workflow

Due dates and payment terms on an e-invoice: stating them where systems read them

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

Put the due date on the invoice itself — the converter's §1 takes it beside the issue date — because your client's payables system schedules payment from the document's data, not from your covering email. State terms that match your agreement exactly (issue date plus the agreed days), keep them consistent invoice to invoice, and remember the issue date also selects the mandate phase: dates on a structured invoice do legal, tax and operational work simultaneously.

What is the due date on an e-invoice?

The due date is the date by which payment falls due, entered in §1 of the converter form alongside the invoice number (BT-1), issue date (BT-2), type code (BT-3) and currency (BT-5). While the issue date is hard-validated (BR-02 requires a real ISO date — it drives the acceptance checker's mandate computation), the due date's force is operational: it is the date the receiving payables process works to, read from the structured document itself.

Why the document must carry its own terms

In the PDF era, payment terms lived in three places at once — the contract, the invoice's small print and the covering email — and payables departments reconciled them by reading. Structured intake reads one place: the document's data. An invoice whose due date exists only in your email arrives in the client's system as an invoice with no schedule, queued behind every invoice that states one. Worse, an invoice whose stated due date disagrees with the contract invites the client to pay by whichever is later, with the document — your document — cited as the authority.

The discipline follows: the due date on the invoice is computed from the agreement (issue date plus terms), stated explicitly, and never left to be inferred. If your terms are '14 days', the due date is the fourteenth day, written as a date. Inference is the enemy — every system and every human in the chain should read the same deadline off the same field.

Issue date, due date and the mandate clock

The issue date does double duty in the structured era: it starts the payment clock and it selects the law. The acceptance checker computes its verdict from the invoice date — an invoice dated the day before a client's phase boundary and one dated the day after are different legal objects. That makes date honesty more than bookkeeping virtue: the date is a factual claim other systems act on, and the verifiable one (the conversion's own record, the sending confirmation) should agree with it.

Practically: issue invoices on the day you issue them, set due dates from real terms, and when timing around a known boundary matters commercially — a client asking to be invoiced before or after their phase date — have that conversation explicitly. Dates chosen openly are planning; dates edited quietly are the kind of thing auditors and tax inspectors are paid to notice.

Terms consistency across the relationship

Payables systems learn suppliers. A supplier whose terms wander — 30 days on one invoice, 14 on the next, 'due on receipt' in an email contradicting both — gets handled by exception, because no rule can be set for them. A supplier whose terms are invariant gets a standing rule in the client's process: book on arrival, pay on the stated date. Consistency is a feature of your invoices' data, as real as their validity.

Fix terms at the relationship level: agreed once, recorded in the client record, applied by template. When terms genuinely change — a renegotiation, a move to shorter terms for a prompt payer — change them as an event, communicated and then consistent thereafter. The template should make the current terms the path of least resistance, so that deviating requires a deliberate act rather than a tired afternoon's improvisation.

Due dates, credits and corrections

Date logic extends to the document family. A credit note (381) carries its own issue date and does not alter the original invoice's due date — it reduces the amount the due date applies to. A corrected invoice (384) replaces the document; its dates should be handled as your accountant directs, since the correction's purpose is a true record, not a more convenient one. What never happens in clean practice: quietly reissuing an invoice with a later due date to restart a payment clock, a manoeuvre the structured record — numbered, dated, archived — is specifically good at exposing.

Chasing overdue payment also reads from the document: the due date is the reference every reminder cites. DueLadder-style discipline — human-approved chasing against real due dates — works because the dates are data: the overdue list computes itself from the same fields the clients' systems scheduled by. State dates well and both sides' machinery agrees on what 'late' means, which is most of what payment diplomacy consists of.

A note on early-payment and prompt terms

If you offer prompt-payment arrangements, express them as cleanly as the due date itself — in the agreement, and consistently. What the structured invoice must never do is hide a discount inside its arithmetic: allowances are for agreed reductions stated in the open (the allowance fields), and the payable amount is the amount the document demands. A payables system books the payable amount; a prompt-payment nuance that exists only in your head will be booked as an error and queried as a shortfall.

The general principle closes the guide: on a structured invoice, everything that matters must be in the document, in its fields, in its dates. Terms, dates, amounts, treatments — if it is not in the data, it is not in the invoice, and the systems now running your clients' payables will behave exactly as if it did not exist. Write invoices that contain their whole truth, and dates will do their quiet work for you.

Date and terms discipline in 5 steps

  1. State the due date on every invoice, computed from the agreed terms (issue date plus days) — never left to an email.
  2. Issue on the true issue date: it starts the payment clock and selects the mandate phase — both functions need the real date.
  3. Fix terms per relationship in the client record and apply them by template; change them only as communicated events.
  4. Cite the document's due date in every reminder — it is the reference both systems share.
  5. Keep prompt-payment or discount arrangements in the open: agreements and allowance fields, never hidden arithmetic.

Worked example: the invoice that paid itself on time

A supplier's terms with a German client are 14 days. Invoice 2026-091 is issued 3 November 2026 with due date 17 November 2026 stated in §1 — net EUR 4,800.00 (EUR 4,000.00 plus 20% S-category tax, per the client's domestic arrangement). The client's system books it on arrival, schedules by the document's due date, and pays on 17 November without a single email.

The counterfactual is the same supplier's older habit: due date omitted, 'payment within 14 days' in the covering message. That invoice entered the system unscheduled, surfaced in a manual review queue, and paid at day 26 after one query. Nothing about the client changed — only whether the invoice carried its own instructions. Dates are instructions; write them where the machines read.

Frequently asked questions

Is the due date validated like the issue date?

The hard validation targets the issue date (BR-02: present, real ISO date) because it drives tax periods and the mandate computation. The due date's importance is operational: payables systems schedule from it, so its absence or inconsistency costs time and money.

What if my terms are 'due on receipt'?

Then the due date is the issue date — state it as such on the document. The system should not have to interpret the phrase; give it the date.

Can I extend a due date by reissuing the invoice?

Not quietly. Changes to issued documents travel as credit notes (381) or corrections (384) under advice — the structured record exists to prevent silent re-dating. If terms are renegotiated, record the event and invoice forward under the new terms.

Do credit notes change the original due date?

No — a credit note reduces the amount owed under the original document; the original's dates stand. The net position is original minus credit, payable per the original terms.

Why does the issue date affect mandates?

The acceptance checker computes the verdict from the invoice date against the mandate phases. An invoice dated across a boundary (e.g., Poland, 1 April 2026) changes obligation — one more reason dates must be true rather than convenient.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back