> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.invoice-api.xhub.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.invoice-api.xhub.io/_mcp/server.

## Blocks inside a column of an inline PDF template — rejected from 2027-01-01

`/generate` checks the `header`, `body` and `footer` blocks of `formatOptions.template`, but blocks inside a column of a
`columns` block went to the renderer unchecked. They are now checked with the same rules, including columns in header
and footer and columns inside columns.

* **Until 2026-12-31:** the block is rendered as sent, with the warning `TEMPLATE_BLOCK_INVALID`. `field` is the path
  (for example `formatOptions.template.body.blocks.1.data.columns.0.blocks.0`), `params.rejectFrom` is `2027-01-01`.
* **From 2027-01-01:** such a block is rejected with **400**, with the same finding as a top-level block.
* `enforcePending: true` gives you the 400 now.

Templates selected with `templateId`, and country templates, are not checked here.

**Do I need to act?** If you see `TEMPLATE_BLOCK_INVALID`, change the block at `field` before 2027-01-01.

## Currency code checked against ISO 4217

`invoice.currency` must be an ISO 4217 code — three upper-case letters such as `EUR`. Before, whether a wrong code was
rejected depended on the format. On `/generate`, `/validate`, `/embed` and `/embed/upload`, a code that is not in
ISO 4217 now adds the warning `CURRENCY_CODE_UNKNOWN` with `field: "currency"`. The answer is otherwise unchanged. The
check is case-sensitive (`eur` is not `EUR`); we do not change your code. A code that is in ISO 4217 but not allowed by
a format (for example `BGN` in EN 16931) is still checked by that format's rules.

**Do I need to act?** If you see `CURRENCY_CODE_UNKNOWN`, fix the code.

## PDF template: page break, watermark and barcode

`formatOptions.template` now accepts three more block types in `header`, `body` and `footer` (rejected with 400
before):

* **`pageBreak`** — starts a new page; optional `data.label` (max. 100 characters).
* **`watermark`** — text across every page, behind the content; `data.text` required (max. 100). Optional `fontSize`,
  `color`, `opacity` (0–1), `rotation` (−90 to 90), `bold`, `font`.
* **`barcode`** — 1D barcode or Data Matrix; `data.content` required (max. 200, placeholders such as
  `{{invoiceNumber}}` allowed). Optional `format` (`code128` default; `code39`, `code93`, `ean13`, `ean8`, `upca`,
  `upce`, `itf14`, `codabar`, `datamatrix`), `width`, `height` (in `lengthUnit`), `alignment`, `includeText`.

Limits count the characters in the template, before placeholders are filled. `bordered`, `chart`, `formField`,
`repeater` and `toc` are still rejected with 400.

## Dates: preceding invoice date and empty strings

* The `YYYY-MM-DD` rule with the `DATE_NOT_ISO` warning (rejected from 2026-11-16) now also covers the preceding
  invoice date (BT-26): `referencedInvoiceDate`, `precedingInvoiceReferences[].issueDate` and
  `items[].creditedFrom.invoiceIssueDate`.
* An empty string (`""`) in `dueDate`, `deliveryDate`, `delivery.date`, `servicePeriod.start` / `end` or
  `items[].servicePeriod.start` / `end` is left out of the document with the warning `DATE_EMPTY_IGNORED` (`field`).
  Omit the field or send `YYYY-MM-DD`.