Release 26.5.49 on 07.08.2026

This release adds support for tax category O (not subject to VAT) in the XRechnung CII and UBL output, fills the seller's electronic address (BT-34) with the own GLN when the company has opted in, and lets the delivery date (BT-72) fall back to the posting date when a document carries no shipment date.

Feature

• The delivery date (BT-72) now follows the German convention in CII and UBL, for invoices and credit memos alike: the Shipment Date is used, and the Posting Date when the document has none. Previously a document without a shipment date lost the whole delivery block, and credit memos were inconsistent between the two formats — CII read the posting date, UBL the shipment date. The value comes from the new buffer field Delivery or Posting Date, so an extension can override it. Existing tenants keep their current mapping until Update Schema from Standard is run on XRECHNUNG-OUT and XRECHNUNG-UBL-OUT; locked lines keep their customer mapping (SR-1582)

Bugfix

• Documents with tax category O (not subject to VAT) no longer violate EN 16931 and XRechnung rules in the CII and UBL output. The line VAT rate (BT-152, BR-O-05), the allowance/charge VAT rate (BT-96, BR-O-06) and the Seller and Buyer VAT identifiers (BT-31 and BT-48, BR-O-02) are left out of the document instead of being written with a zero rate or an identifier. As the seller identifier then has to be present in another form (BR-CO-26), the legal registration identifier (BT-30) is now written from Company Information → Registration No. in both formats, and generation stops with a clear message when a category-O VAT breakdown has no VAT clause code (BR-O-10). The VAT breakdown rate (BT-119) stays in the document for category O, as BR-DE-14 requires it. Category Z keeps writing its real 0 % rate (SR-1581)
• The own GLN is now used as the seller's electronic address in Peppol/UBL documents when Company Information → Use GLN in Electronic Document is set. The seller endpoint (BT-34) previously always carried the VAT registration number with scheme 9930, even though the same setting was already honoured on the buyer side; it now carries the GLN with scheme 0088, and generation reports a clear error when the option is set but no GLN is entered. The same correction applies to the CII output, where the seller URIID is filled from the same source (INC-1590)

Enhancements

• Schema lines have two new columns, Visibility Control Table No. and Visibility Control Field No., which point at a flag field in any of the buffered records. When that field holds its type's default value (No, empty, 0, 0D, empty GUID), the writer leaves the element and its whole subtree out of the XML; any other value writes it. Unlike Check to Process or Ignore, the flag is independent of the element's own value, so an element can be suppressed while keeping its original source and data type. Both columns are editable on the schema-line pages, are translated, and survive Update Schema from Standard on locked lines; extensions can set them through the new AddLine and AddProgrammaticLock overloads (SR-1581)