> 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.

## Upcoming enforcement

| From       | What is rejected                                                                                                                                                                                                   | Code                         |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------- |
| 2026-11-11 | Empty `buyer.countryCode`, sellers in EU member states — also where it is accepted today (for example `/DE/pdf/generate`); sellers elsewhere: see the 2026-10-11 entry (2026-11-14, above the small-invoice limit) | 422 `BUYER_COUNTRY_REQUIRED` |
| 2026-11-16 | A date that is readable but not `YYYY-MM-DD`                                                                                                                                                                       | 400 `INVALID_DATE`           |

Until then the answer carries the warnings `BUYER_COUNTRY_REQUIRED` and `SPEC_RULE_PENDING`, or `DATE_NOT_ISO`. With
`enforcePending: true` you get the rejection today.

**Do I need to act?** Always send the buyer's country, and send dates as `YYYY-MM-DD`.

## Dates that are not `YYYY-MM-DD`

On `/generate` and `/embed`, `dueDate`, `deliveryDate`, `delivery.date`, `servicePeriod.start` / `end` and
`taxPointDate` should be `YYYY-MM-DD`. Another readable form (`01.05.2026` is read day first, `05/01/2026`) is written
as the date shown in `warnings[].params.written`, with the warning `DATE_NOT_ISO` (`field`, `params.received`,
`params.rejectFrom`). From 2026-11-16 it is rejected with 400 `INVALID_DATE`. A timestamp such as
`2027-03-15T23:30:00-05:00` writes its date part as sent.

## Changes for callers

* **Factur-X embed with an unreadable delivery note date:** `POST /FR/facturx/embed` with a `deliveryNote.date` that is
  not a real date (for example `31.02.2026`) answers **400** `INVALID_DATE`. Before, it answered 200 and silently left
  the delivery note out.
* **PDF without embedded XML:** `POST /parse` answers **400** `NO_EMBEDDED_XML` (before: 200 with `DE_UNKNOWN_FORMAT`);
  `POST /convert` answers 400 `NO_EMBEDDED_XML` instead of 422 `PARSE_FAILED`.
* **`/parse` payment term:** `invoice.paymentTerms.dueDays` is filled only from the document. Without a term in the
  document the field is absent instead of a fixed default.

**Do I need to act?** Handle `400 NO_EMBEDDED_XML` and a missing `dueDays` if you rely on them.

## PDF template: the reference describes what the renderer does

The PDF output does not change. The API reference for `formatOptions.template` now documents:

* 13 more `table` fields that already worked: `carryOver`, `carryOverByTaxRate`, `carryOverColumn`,
  `carryOverColumns`, `carryOverTaxRateField`, `carryOverLabels`, `prepaidReceiptLabels`, `rowFill`,
  `alternateRowFill`, `bodyTextColor`, `fontFamily`, `numberFormat`, `dateFormat`. A wrong type for one of them is now
  rejected with **400**.
* `{{page.current}}` and `{{page.total}}` in header and footer blocks.
* `repeatOnAllPages`: header on every page by default, footer on the last page only by default.
* Block lengths are read in the template's `lengthUnit` (not always points).
* `dataSource` takes any array in your invoice data.
* Accepted block types: text, table, summary, keyvalue, columns, image, spacer, line, qrcode.

**Do I need to act?** If you set `lengthUnit` to `mm` or `inch`, give block lengths in that unit.