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.
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/validateanswersvalid: falsewithINVOICE_DATE_NOT_XS_DATEatissueDate;/convertanswers 422PARSE_FAILEDwithDE_INVALID_INVOICE_DATE. - Empty
issueDate:/validatereportsBR-03instead ofVAL-SYS-005;/generateanswers 422BR-03instead of 400INVALID_DATE. /parsewithout an invoice date:success: falsewithDE_MISSING_INVOICE_DATEinstead 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 422BR-03. /validateand totals (CII): a VAT breakdown category that no line has is invalid withAMT_004, as at/generate. Wrong totals also reportAMT_00xnext to the format rules.buyer.taxableRecipientmust betrueorfalse; other values give 400 (null= not sent). In Portugal, withtrue, a small invoice without the buyer’svatIdortaxIdgets 422RECIPIENT_REQUIRED.- Hungary (NAV):
countrySpecific.customerVatStatusnow takes effect.PRIVATE_PERSONomits buyer name, address and tax number from the NAV report; a status contradicting the buyer’s tax number gives 422NAV_CUSTOMER_STATUS_CONFLICT. - Portugal (
/PT/ubl/generate):orderNumberwith 21–100 characters gives 422DT-CIUS-PT-012;quoteNumberover 20 characters together with an order number gives 422DT-CIUS-PT-013. Before, the values silently went missing.
Accepted now (was rejected)
/validateadds a missing VAT ID country prefix (BR-CO-09) withVAT_ID_COUNTRY_PREFIX_ADDED.- CII (ZUGFeRD, Factur-X): a missing exemption reason gets the standard text with
TAX_EXEMPTION_REASON_SUBSTITUTED. - ES Facturae:
/validatenow runs the rules (passedinstead ofnot_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: 422PEPPOL-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.
cashwith a seller IBAN is code 10.direct_debitwith 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
Ewith the note text, no BT-121 code. - ES Facturae:
BatchIdentifieris 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/validateanswers with the same codes as/DE/validateand/generate(for exampleDE_SELLER_CONTACT_001with ruleBR-DE-2).- AT ebInterface: wrong decimals give
AT-EBI61-004instead ofXSD-ERROR. - An attachment with only a description: 422
BR-52instead of 400. POST /api/v1/lroe/submitwithout Bizkaia credentials: 409LROE_CREDENTIAL_MISSING/LROE_NRS_MISSINGor 503ESCROW_UNAVAILABLEinstead of 500./convertwith a non-JSON body: 400Malformed JSON in request bodyinstead of 500.DE_REF_002now 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) inorderNumber. - IBANs arrive without spaces and in capitals, in every input format.
paymentMethods[].typefollows one table: 10cash; 30/42/58bank_transfer; 48/54/55credit_card; 49/59direct_debit; otherother.- 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) returnsseller.legalName/buyer.legalName; CII from DE, CH, NL returnsdirectDebitMandate; NAV returnsseller.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) whilesuccessstaystrue. If you treat anyerrorsentry as failure, check this case. - Missing party country: new warning
PARTY_COUNTRY_ASSUMEDwith field and place. /converthas a new fieldsourceErrorswith the findings from reading the source.
New
/{country}/{format}/validatechecks a document you received. Send{ "data": "<base64 XML or PDF>", "filename": "…" }instead ofinvoice. The file itself is checked against XSD and rulebook; a PDF also getsextractedFromPdf: true. Billed 1 unit on the format’sparseentitlement. New answers: 400NO_EMBEDDED_XML, 400FORMAT_MISMATCH; with bothinvoiceanddata,invoiceis checked and you getDATA_IGNORED./fr/ublvalidation follows the file: Peppol BIS, EXTENDED-CTC-FR (EN 16931 + CTC-FR rules) or EN 16931;results[].formatnames the rulebook./validateexplains a non-Unified body: the 400 gains ahint(ValidationHint) withcode(BODY_NOT_JSON,INVOICE_MISSING,INVOICE_LOOKS_LIKE_XML,INVOICE_NOT_UNIFIED),messageand, where useful,next. Status,errorandsuccessare unchanged.- Warning
TAX_SUMMARY_CATEGORY_WITHOUT_LINESwhen a breakdown row has a category and rate no line uses. - Portugal: optional
buyer.taxableRecipient;falselets you omit buyer name and address (TAXABLE_RECIPIENT_CONFLICTwith reverse charge). - Some formats warn
FIELD_NOT_WRITTENwhen a field has no place in the format. POST /api/v1/lroe/submitis listed under the tagLROE.
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 inrule(for exampleFX-SCH-A-000155). If you match oncodevalues starting withFX-SCH-A-, match onrule. - Portugal (CIUS-PT): BT-31 and BT-48 carry the
vatIdyou send, unchanged. Without it,PTplus the checkedtaxId. New warningsBUYER_VAT_ID_PLACEHOLDER,BUYER_VAT_ID_MISSING,SELLER_VAT_ID_MISSING. SendvatIdfor 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.
