Skip to navigation

Upcoming enforcement

This week’s releases change the answer to some requests. Where a rule gets stricter, you first get a warning SPEC_RULE_PENDING with enforceFrom; from that date the request is rejected. Send enforcePending: true to get the rejection today and test your integration.

FromWhat is rejectedCode
2026-11-11AT ebInterface: phone and email of seller and buyer move from eb:Contact into the address block (document change, warning until then)—
2026-11-14Card payment without a card accountCARD_ACCOUNT_REQUIRED
2026-11-14BE Factur-X: credit transfer without payment accountPAYMENT_ACCOUNT_REQUIRED
2026-11-14FR and BE: credit transfer without payment accountCREDIT_TRANSFER_ACCOUNT_REQUIRED
2026-11-14Sellers outside the EU: invoice above the small-invoice limit without the buyer’s countryBUYER_COUNTRY_REQUIRED
2026-11-15ES Facturae: empty invoice number (ES-FAE322-056) and rule ES-FAE322-055rule id
2026-11-17Document-level allowance or charge without a tax category, in every formatALLOWANCE_TAX_CATEGORY_REQUIRED
2026-11-17Creating an invoice (/generate, /embed, /convert, PDF) without the buyer’s name where the seller’s country requires it (23 countries)422 RECIPIENT_REQUIRED
2026-11-17Small invoice without the buyer’s name, sellers in 22 EU countries and Switzerland, also with reverse charge or intra-EU supply (K): /validate and the PDF route warn until then, then the invoice is invalidRECIPIENT_REQUIRED
2026-11-17A quantity that becomes 0 after the format’s rounding (AT ebInterface, PT CIUS-PT, IT FatturaPA, HU NAV)QUANTITY_ROUNDS_TO_ZERO

Small-invoice limits for the buyer’s name are those of the seller’s country (for example FR up to 150 EUR, PL up to 450 PLN, PT up to 100 EUR). Sellers in AE, AU, CA, GB, IS, JP, LI, NO, NZ, OM and US: no change for small invoices without the buyer’s name. E-invoice formats that already answered 422 with BR-07 keep doing so. With enforcePending: true the error is RECIPIENT_REQUIRED on buyer.name in errors.

Stricter now (no warning phase)

  • Impossible invoice date (for example 2026-02-30): /DE/validate answers valid: false with INVOICE_DATE_NOT_XS_DATE at issueDate; /convert answers 422 PARSE_FAILED with DE_INVALID_INVOICE_DATE.
  • Empty issueDate: /validate reports BR-03 instead of VAL-SYS-005; /generate answers 422 BR-03 instead of 400 INVALID_DATE.
  • /parse without an invoice date: success: false with DE_MISSING_INVOICE_DATE instead of a filled-in date.
  • PDF route: an unreadable invoice date gives 400 INVALID_DATE (before: a PDF printing the raw value); an empty one gives 422 BR-03.
  • /validate and totals (CII): a VAT breakdown category that no line has is invalid with AMT_004, as at /generate. Wrong totals also report AMT_00x next to the format rules.
  • buyer.taxableRecipient must be true or false; other values give 400 (null = not sent). In Portugal, with true, a small invoice without the buyer’s vatId or taxId gets 422 RECIPIENT_REQUIRED.
  • Hungary (NAV): countrySpecific.customerVatStatus now takes effect. PRIVATE_PERSON omits buyer name, address and tax number from the NAV report; a status contradicting the buyer’s tax number gives 422 NAV_CUSTOMER_STATUS_CONFLICT.
  • Portugal (/PT/ubl/generate): orderNumber with 21–100 characters gives 422 DT-CIUS-PT-012; quoteNumber over 20 characters together with an order number gives 422 DT-CIUS-PT-013. Before, the values silently went missing.

Accepted now (was rejected)

  • /validate adds a missing VAT ID country prefix (BR-CO-09) with VAT_ID_COUNTRY_PREFIX_ADDED.
  • CII (ZUGFeRD, Factur-X): a missing exemption reason gets the standard text with TAX_EXEMPTION_REASON_SUBSTITUTED.
  • ES Facturae: /validate now runs the rules (passed instead of not_run).
  • AT ebInterface: prices with many decimals are kept exactly.
  • /parse (UBL): a missing trading name is taken from the legal name.
  • Peppol UBL: a price base quantity ≤ 0 is ignored with PRICE_BASE_QUANTITY_IGNORED (before: 422 PEPPOL-EN16931-R121).
  • /convert: DE CII sources with direct-debit mandate details in the schema position; IT FatturaPA with spaces in the IBAN; zugferd (DE, CH) with direct debit (code 59) and no seller bank account.

Same request, different document

  • Discounts are written in Factur-X, ISDOC, FatturaPA and NAV. A percentage discount with a price base quantity is quantity × price / base quantity.
  • Payment means: Factur-X writes the seller’s IBAN/BIC for credit transfer, and the code follows the payment method (for example 30 instead of 1), also in UBL. cash with a seller IBAN is code 10. direct_debit with a mandate now writes the seller’s IBAN.
  • HU NAV: unit price keeps all decimals; exchange rate up to 6 decimals (more are rounded with EXCHANGE_RATE_DECIMALS_ROUNDED).
  • DE small business (§ 19 UStG): category E with the note text, no BT-121 code.
  • ES Facturae: BatchIdentifier is the seller’s tax number followed by the invoice number (ES-FAE322-039).
  • CH QR bill: header version 0200.
  • Portugal CIUS-PT: order number (BT-13) and quote number (BT-14) are now in the document.
  • /DE/xrechnung/validate answers with the same codes as /DE/validate and /generate (for example DE_SELLER_CONTACT_001 with rule BR-DE-2).
  • AT ebInterface: wrong decimals give AT-EBI61-004 instead of XSD-ERROR.
  • An attachment with only a description: 422 BR-52 instead of 400.
  • POST /api/v1/lroe/submit without Bizkaia credentials: 409 LROE_CREDENTIAL_MISSING / LROE_NRS_MISSING or 503 ESCROW_UNAVAILABLE instead of 500.
  • /convert with a non-JSON body: 400 Malformed JSON in request body instead of 500.
  • DE_REF_002 now names its rule: BR-DE-15.

Parsing and converting

  • UBL from CH, CZ, ES, FR, HU, PT: buyer reference (BT-10) is in countrySpecific.buyerReference, order number (BT-13) in orderNumber.
  • IBANs arrive without spaces and in capitals, in every input format.
  • paymentMethods[].type follows one table: 10 cash; 30/42/58 bank_transfer; 48/54/55 credit_card; 49/59 direct_debit; other other.
  • The payment term comes from the source’s due date (BT-9) instead of a fixed 30 days (UBL from FR, CZ, ES, HU, PT; KSeF; FatturaPA, ISDOC and Facturae with a due date on the invoice date give 0 days).
  • UBL from FR, CZ, ES, HU, PT keeps payment account and means code; French CII keeps payment instructions for every means code.
  • /parse (UBL) returns seller.legalName / buyer.legalName; CII from DE, CH, NL returns directDebitMandate; NAV returns seller.bankAccount.iban.
  • Mandate details outside the CII schema position are read as before but listed in errors (DE_DIRECT_DEBIT_MANDATE_OUTSIDE_SCHEMA, CH_…, NL_…; NAV: HU_BANK_ACCOUNT_OUTSIDE_SCHEMA) while success stays true. If you treat any errors entry as failure, check this case.
  • Missing party country: new warning PARTY_COUNTRY_ASSUMED with field and place.
  • /convert has a new field sourceErrors with the findings from reading the source.

New

  • /{country}/{format}/validate checks a document you received. Send { "data": "<base64 XML or PDF>", "filename": "…" } instead of invoice. The file itself is checked against XSD and rulebook; a PDF also gets extractedFromPdf: true. Billed 1 unit on the format’s parse entitlement. New answers: 400 NO_EMBEDDED_XML, 400 FORMAT_MISMATCH; with both invoice and data, invoice is checked and you get DATA_IGNORED.
  • /fr/ubl validation follows the file: Peppol BIS, EXTENDED-CTC-FR (EN 16931 + CTC-FR rules) or EN 16931; results[].format names the rulebook.
  • /validate explains a non-Unified body: the 400 gains a hint (ValidationHint) with code (BODY_NOT_JSON, INVOICE_MISSING, INVOICE_LOOKS_LIKE_XML, INVOICE_NOT_UNIFIED), message and, where useful, next. Status, error and success are unchanged.
  • Warning TAX_SUMMARY_CATEGORY_WITHOUT_LINES when a breakdown row has a category and rate no line uses.
  • Portugal: optional buyer.taxableRecipient; false lets you omit buyer name and address (TAXABLE_RECIPIENT_CONFLICT with reverse charge).
  • Some formats warn FIELD_NOT_WRITTEN when a field has no place in the format.
  • POST /api/v1/lroe/submit is listed under the tag LROE.

Rule ids, Portuguese VAT numbers, certificates, Hungarian tax numbers

  • ZUGFeRD 2.4 / CII against EN 16931: a rulebook finding has code: "SPEC_RULE_FAILED" and the identifier in rule (for example FX-SCH-A-000155). If you match on code values starting with FX-SCH-A-, match on rule.
  • Portugal (CIUS-PT): BT-31 and BT-48 carry the vatId you send, unchanged. Without it, PT plus the checked taxId. New warnings BUYER_VAT_ID_PLACEHOLDER, BUYER_VAT_ID_MISSING, SELLER_VAT_ID_MISSING. Send vatId for business customers outside Portugal.
  • PKCS#12 certificates with an iteration count above 100,000 are refused with PKCS12_PARSE_FAILED (TicketBAI, Batuz/LROE, connection test). Files exported with default settings are not affected.
  • Hungary: the tax number check digit follows the official seven-weight rule; valid numbers refused before (HU_TAX_001, HU_TAX_002, HU_TAX_006) are now accepted.