Skip to main content

Release 26.5.37 on 01.06.2026

· 2 min read

This release sharpens xRechnung / CII compliance and inbound document handling: the CII export now emits the document-level allowance group (BG-20) and orders schema children correctly, vendor recognition can match third-country suppliers by their tax number, e-mails with oddly-typed PDF attachments are no longer silently lost, and large OCR requests no longer abort at the 100-second default.

Feature​
  • Vendor recognition now matches third-country suppliers by their seller tax number (Steuernummer). When neither the IBAN nor the VAT registration number resolves a vendor – common for Outside-of-Community suppliers – the parsed seller tax number is matched against the vendor's registration number, with the bare VAT scheme token skipped (CHN-267)
Bugfix​
  • CII xRechnung now emits the document-level allowance group (BG-20) when a sales document carries an invoice discount. The block was previously omitted, breaking KoSIT validation with BR-CO-11 and BR-Z-08; it is now written per VAT category that actually carries a discount, for both invoices and credit memos (CHN-257)
  • CII xRechnung schema children are now emitted in Sorting No. (document) order instead of Entry No. order, and a programmatically locked line without an explicit predecessor is placed as the first child – fixing element-ordering validation failures such as InvoiceIssuerReference. Run Update from Standard on the CII schema setup to apply (CHN-268)
  • Incoming e-mails whose PDF attachment carries a generic MIME type (for example application/octet-stream) now produce an eDocument through a MIME-normalisation and file-extension fallback. E-mails that yield no document are no longer silently archived – they stay in the source folder and a warning is written to the mseDoc365 Response Log (CHN-269)
  • Large OCR requests no longer abort at the .NET 100-second default; the timeout is now governed by a configurable HTTP Request Timeout (Sec.) setup field that defaults to 5 minutes (CHN-265)
  • The default schema now fills the buyer contact phone number with the telephone number instead of the address