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

## Taxable amount per VAT category is checked — and your tax breakdown is written as sent

This can reject a request that passed before.

Each `taxSummary` entry has a `netAmount` (BT-116, the taxable amount). It must match the line net amounts of that
category and rate, plus charges, minus allowances. When you ask for an e-invoice format, we now check this. If it does
not match, you get **422** with error code `AMT_004`, field `taxSummary[n].netAmount`, and the rule (for example
`BR-S-08`) in the message. The message names the expected sum.

The tolerance is the one in the official rule set of the format you ask for, not our own number:

* Peppol BIS, XRechnung, CIUS-PT, CIUS-RO: the EN 16931 limit (± 1.00) — less strict than our former 0.01
* PINT AE: 0.02 · PINT A-NZ: 1.00 · PINT OM and SI-UBL (Netherlands): the limit of their rule sets
* ZUGFeRD and Factur-X: the limits of the rule sets we check these profiles with
* Formats whose official rules have no such check (PINT JP, KSeF, ebInterface, ISDOC, Facturae, FatturaPA, NAV,
  myDATA, QR-bill): no check any more
* **Stricter in one case:** for categories `Z`, `E`, `AE`, `K`, `G` and `O` the official rule requires an exact match.
  A difference below 0.01 that we accepted before is now rejected.

Without an e-invoice format (no format, or only `pdf` / `html`) this check does not run, and `POST /validate`
without a format no longer returns `AMT_004` for the taxable amount.

**We write the tax breakdown you send.** If you send `taxSummary`, every e-invoice format now writes exactly these
values into the VAT breakdown (BG-23): taxable amount, tax amount, category and exemption reason. Before, most UBL
formats recalculated the breakdown from the lines. A `taxSummary` row without a category takes it from the lines with
the same rate.

**Do I need to act?** If you get the new 422, check that each `netAmount` is the sum of its lines (plus charges, minus
allowances).

## Australia and New Zealand: PINT A-NZ Billing 1.1.3

The Peppol network removed the old A-NZ version on 2026-03-31. Every AU and NZ invoice now carries the identifiers of
the current version:

| Element               | Before                                                                                           | Now                                |
| --------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------- |
| `cbc:CustomizationID` | `urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:international:aunz:3.0` | `urn:peppol:pint:billing-1@aunz-1` |
| `cbc:ProfileID`       | `urn:fdc:peppol.eu:2017:poacc:billing:01:1.0`                                                    | `urn:peppol:bis:billing`           |

* The created invoice is checked against PINT A-NZ 1.1.3. The rule set name in responses changes from
  `pint-au-nz-1.0` to `pint-au-nz-1.1`.
* Error messages name PINT rule ids, for example `ibr-006` (seller name missing) instead of `BR-06`, and `ibr-120`
  for a malformed ABN.
* Australia: the seller's GST registration (`PartyTaxScheme`) is written only when at least one line has a GST
  category other than `O`.

**Do I need to act?** If you send your own `businessProcess` (BT-23), use `urn:peppol:bis:billing`. If your system or
access point checks the old identifiers, or matches on rule ids, update it.

## Swiss and Liechtenstein QR bill: the payee is the creditor

On a QR bill, creditor and account must match (SIX Implementation Guidelines, 4.3.1). Before, the QR bill always used
`seller.bankAccount`, even when a `payee` was shown as creditor. For `POST /api/v1/invoice/{CH|LI}/qr-bill/generate`:

* A `payee` is the creditor. It needs a postal code, city and country, otherwise **422** `CH_ADDR_004`
  (`payee.postalCode`), `CH_ADDR_005` (`payee.city`) or `CH_ADDR_006` (`payee.countryCode`).
* The payee needs its own account: without `payee.bankAccount.iban` you get **422** `CH_IBAN_003`.
* Without a `payee`, nothing changes.

`payee.bankAccount` is now documented. When set, it is the payment account (BT-84) in every format and the account in
the QR code. Payee address fields now have limits — `street` and `additionalStreet` 200, `city` 100, `postalCode` 20,
`countryCode` exactly 2 characters; longer values get **400**.

**Do I need to act?** If you send a `payee` on a QR bill, send its postal code, city, country and its own
`bankAccount`.

## Register and party identifiers need an ISO 6523 (ICD) scheme

EN 16931 has two scheme lists: **ICD** for party identifiers and legal registrations (BT-29, BT-30, BT-46, BT-47;
rules `BR-CL-10`, `BR-CL-11`) and **EAS** for electronic addresses (BT-34, BT-49; rule `BR-CL-25`). Codes like `9934`
or `9936` are EAS codes. Before, our check accepted an EAS code in an ICD position; the receiver's check does not.

* An EAS code (`99xx`) in `seller.registrationScheme`, `buyer.registrationScheme` or `identifiers[].schemeId` is
  rejected with **422** naming `BR-CL-10` or `BR-CL-11`.
* Croatia and Liechtenstein: these positions no longer carry a `schemeID`. In Croatia the seller identifier (BT-29) is
  written as `9934:<OIB>`.

**Do I need to act?** Use an ICD code for registers (for example `0088` for a GLN) or leave the scheme out. Put
electronic addresses in `seller.electronicAddress` / `buyer.electronicAddress`.

## Austria: ebInterface 6.1 is checked

There is no official Schematron for ebInterface 6.1, so we wrote 27 rules from the official documentation (AUSTRIAPRO,
14 June 2023), ids `AT-EBI61-001` … `AT-EBI61-027`.

* `POST /api/v1/invoice/at/ebinterface/validate` and `/at/validate` now give a verdict (`passed` / `failed`) instead
  of `not_run`.
* `/at/ebinterface/generate` can reject with **422** and an `AT-EBI61-…` rule id, for example when line amounts or
  totals do not add up.
* Invoices not in EUR need `taxCurrencyCode: "EUR"` and `taxSummary[].taxCurrencyTaxAmount` for every rate, otherwise
  **422** `AT_EBI_TAX_EUR_AMOUNT_REQUIRED` (`AT-EBI61-011`). We do not apply an exchange rate.
* `cardAccount.pan` may have at most 10 digits, otherwise **422** `AT_EBI_PAN_TOO_MANY_DIGITS` (`AT-EBI61-013`).
* The other 14 rules are warnings and do not change `valid`.

Three of the four official ebInterface 6.1 sample files do not pass these rules — their totals do not calculate as the
documentation says. If you copied one, check your totals.

## Security retention reaches every format with payment terms

`retention` was written only in German XRechnung and ZUGFeRD. It is now written as one sentence into the payment terms
(BT-20 or the national field) of every format that has them.

* The sentence is in the seller's language (German original; English, French, Dutch, Italian, Spanish and Polish are
  machine translations; other languages get English). A `reason` you send is written as sent.
* Amounts keep their full value; the retention only reduces the amount to pay. Do not model it as an allowance.
* France (Peppol) now writes `cac:PaymentTerms`. Netherlands, Portugal, Romania: an empty `cac:PaymentTerms` is gone.
* Italy (FatturaPA): non-Latin-1 characters are replaced, with warning `TEXT_CHARACTERS_REPLACED` on `retention.reason`.
* Hungary (NAV): a payment description over 512 characters is no longer cut but split into `X99999_PAYMENT_DESC`,
  `X99999_PAYMENT_DESC_2`, … (also without a retention).
* Spain (Facturae): written to `InvoiceTotals/AmountsWithheld`, and `TotalExecutableAmount` is lowered.
* **422** `RETENTION_NOT_CARRIED` (field `retention`) only where a format has no place for it: ZUGFeRD / Factur-X
  MINIMUM, and Greek myDATA without `paymentMethods`. A plain PDF is never rejected for this.

**Do I need to act?** If you compare XML with stored copies, expect the new sentence. For Greek invoices with a
retention, send a payment method.

## Buyer identifier is BT-46

BT-46 may occur once. Before, it held `customerNumber`, and some UBL formats wrote both values (rule UBL-SR-16).

* The first `buyer.identifiers` entry is now BT-46, with its `schemeId`.
* If you send a buyer identifier, `customerNumber` is not written — warning `FIELD_NOT_WRITTEN`, `field: customerNumber`.
  Further identifiers give `FIELD_NOT_WRITTEN` with `field: buyer.identifiers.<n>`.
* Without a buyer identifier, `customerNumber` stays BT-46.

**Do I need to act?** Only if you send both. If your receivers expect the customer number in BT-46, do not send
`buyer.identifiers`.

## `/validate` says when a rulebook was not run

Some formats have no official rulebook (Schematron) we can run. Before, `/validate` answered them with `valid: true`.
Now:

* `POST /api/v1/invoice/{country}/{format}/validate` answers **200** with `status: not_run`, `valid: null` and
  `reason: missing`. The XSD check still runs; a real finding still gives `failed`. A rulebook that failed to load
  still answers 503 (retryable); `missing` is not.
* `POST /api/v1/invoice/{country}/validate` has a new field `validation` with the same shape. The top-level `valid` is
  unchanged.

Affected at the time of this release: parts of AT ebInterface, HU NAV, IT FatturaPA, ES Facturae, CH QR-bill and
ZUGFeRD 2.3 EXTENDED, CZ ISDOC 6.0 / 5.3, DE XRechnung 2.3 (German rules) and PT CIUS-PT 2.0. ebInterface 6.1 got its
rules in this same week; Facturae followed later.

**Do I need to act?** If you use `valid === true` as a gate, also handle `status: not_run`.

## Fewer silent omissions in the XML

* **VAT ID without country prefix:** a VAT ID that starts with a digit no longer fails with `BR-CO-09`. Where the
  format's rules require the prefix, we add the party's `countryCode` (`EL` for Greece) and warn with
  `VAT_ID_COUNTRY_PREFIX_ADDED`. VAT IDs starting with letters are not changed.
* **Seller identifier in XRechnung (BT-29):** the seller VAT ID is repeated as identifier only when nothing else
  satisfies BR-CO-26; then you get `SELLER_IDENTIFIER_DERIVED`.
* **Payee identifier (BT-60):** the first non-empty `payee.identifiers` entry is written, with its `schemeId`.
* **Payee and tax representative:** `payee.registrationNumber` (BT-61) is now written in XRechnung UBL, SI-UBL,
  CIUS-PT, CIUS-RO and all CII formats. The tax representative's `additionalStreet`, `addressLine3` and `state`
  (BT-65, BT-164, BT-68) are now written in CII, and in UBL also without street or city.
* **ZUGFeRD / Factur-X exemption reason:** a line exemption reason (BT-120/121) is written on the line only in
  EXTENDED and XRECHNUNG; in BASIC and EN 16931 it goes into the VAT breakdown. If it cannot reach the document you get
  `FIELD_NOT_WRITTEN` with `lossy: true`.
* **Rule ids instead of `UNKNOWN`:** rulebook findings without an id are now `SCHEMATRON_ASSERT_WITHOUT_ID`,
  `SCHEMATRON_REPORT_WITHOUT_ID` or `RULE_ID_MISSING`.
* **Netherlands:** checked with SI-UBL 2.0.3.13 and NLCIUS-CII 1.0.3.13 (release of 2026-05-21). UBL: new
  `UBL-SR-56`, `BR-CO-25` removed. CII: 28 new `CII-SR` rules, `BR-CO-25` and `BR-CO-27` removed.

## `countrySpecific.peppolEndpointId` is deprecated

The field (AE, AU, BE, NZ) was accepted but never written. Sending it now adds the warning `FIELD_NOT_WRITTEN` with
`field: "countrySpecific.peppolEndpointId"`. Use `buyer.electronicAddress` (BT-49) and `seller.electronicAddress`
(BT-34) instead. In Belgium, warning `BE_PEPPOL_001` now looks at `buyer.electronicAddress`. The field will be removed
in a later release, announced separately.

Three new warnings (with `substituted: true`) say when we fill in a value you did not send:
`SELLER_CONTACT_NAME_DERIVED` (`seller.contact.name`, XRechnung UBL), `BUSINESS_PROCESS_DEFAULTED` (`businessProcess`,
XRechnung UBL and ZUGFeRD XRECHNUNG) and `AE_TRANSACTION_TYPE_DEFAULTED` (`countrySpecific.transactionTypeCode`). ZUGFeRD
XRECHNUNG now writes BT-23, which fixes `PEPPOL-EN16931-R001`.

**Do I need to act?** If your code treats every warning as an error, send these values yourself.

## PDF output

* An amount and its currency symbol stay on one line.
* The tax rate in the totals uses the template language's percent format, as in the item column. Your own copies of
  system templates keep their label; change `{{taxRate}}%` to `{{taxRate:percent}}` to get it.
* The German default template shows `1.190,00 €` instead of `1,190.00 €`. The embedded XML does not change.