Skip to navigation

Upcoming enforcement — all dates at a glance

Each of these cases gets a warning today and is rejected from the date shown. Details are in the entry of the week the warning was introduced. Every pending rule also answers with SPEC_RULE_PENDING and enforceFrom; send enforcePending: true to get the rejection today and test your integration.

FromWhat is rejectedCodeDetails
2026-11-11Empty buyer.countryCode, sellers in EU member states422 BUYER_COUNTRY_REQUIRED2026-10-18
2026-11-11AT ebInterface: seller and buyer phone and email move into the address block (document change)—2026-10-11
2026-11-14Card payment without a card accountCARD_ACCOUNT_REQUIRED2026-10-11
2026-11-14BE Factur-X: credit transfer without payment accountPAYMENT_ACCOUNT_REQUIRED2026-10-11
2026-11-14FR and BE: credit transfer without payment accountCREDIT_TRANSFER_ACCOUNT_REQUIRED2026-10-11
2026-11-14Sellers outside the EU: above the small-invoice limit without the buyer’s countryBUYER_COUNTRY_REQUIRED2026-10-11
2026-11-15ES Facturae: rules ES-FAE322-055 and ES-FAE322-056 (empty invoice number)rule id2026-10-11
2026-11-16A date that is readable but not YYYY-MM-DD400 INVALID_DATE2026-10-18
2026-11-17Allowance or charge on document level without a tax categoryALLOWANCE_TAX_CATEGORY_REQUIRED2026-10-11
2026-11-17Invoice without the buyer’s name where the seller’s country requires itRECIPIENT_REQUIRED2026-10-11
2026-11-17Quantity that rounds to 0 (AT, PT, IT, HU formats)QUANTITY_ROUNDS_TO_ZERO2026-10-11
2027-01-01Invalid block inside a columns block of an inline PDF template400, warning TEMPLATE_BLOCK_INVALID2026-10-25

Announced without a date yet (a later release, announced in advance): the FIELD_TOO_LONG limits and INVOICE_LINES_ABOVE_MODE_LIMIT (see 2026-10-04), and the removal of countrySpecific.peppolEndpointId (see 2026-09-27).

PDF templates over the REST API

You can now store, update and read PDF templates with your API key:

  • POST /api/v1/pdf/templates stores a BlockTemplate for your organization and returns it with its id (201). Use the id as templateId in POST /api/v1/pdf/generate or in formatOptions.templateId of the invoice routes. The template also appears in the Console under PDF templates.
  • PUT /api/v1/pdf/templates/{id} changes only the fields you send. isActive is not accepted (400 UNSUPPORTED_FIELD); system templates are read-only (403 SYSTEM_TEMPLATE_READ_ONLY).
  • GET /api/v1/pdf/templates/{id} returns a template of your organization or a system template.

Body fields: name and template (required), documentType (default invoice), description, sampleData, pageSettings, isDefault. isDefault: true makes the template the default of the whole organization.

Entitlements: pdf:template:create, pdf:template:update, pdf:template:read — on plans that include the PDF template editor, not on the Free plan. Only API keys you created in the Console may use these routes; session keys get 403 SESSION_KEY_FORBIDDEN. The body is limited to 2 MiB (413 PAYLOAD_TOO_LARGE). Not metered.

Send the generated invoice by e-mail

POST /api/v1/invoice/{countryCode}/{format}/generate takes a new optional field emailRecipients (paid plans only): up to 10 recipients, each an address or { email, subject?, body? } (subject 1–300, body 1–10,000 characters, sent as plain text).

  • After a successful generation, the document is sent as attachment — the hybrid PDF for ZUGFeRD / Factur-X, otherwise the XML (the data of the response with its mimeType).
  • A bare address gets a default subject (Rechnung <number> von <seller> for /DE and /AT, otherwise Invoice <number> from <seller>) and a default text. Duplicate addresses (case-insensitive) are sent once.
  • The sender is our invoice mail address with your organization’s name; replies go to the contact e-mail of your seller profile.
  • The response is the same as without the field; the result per recipient is in your generation log.
  • Without an active paid subscription the call is rejected with 403 before anything is generated. A generation that answers 422 sends nothing. Sending does not count as extra usage.

TRAFFIQX delivery: planned endpoint

POST /api/v1/traffiqx/send (tag TRAFFIQX) is listed in the reference. Delivery via the TRAFFIQX network is planned for Q1/2027 and not implemented yet: the endpoint answers 501 NOT_IMPLEMENTED_PLANNED with the planned quarter and the roadmap URL. The request body is ignored; nothing is billed.