Skip to main content

Release 26.5.62 on 20.11.2026

· 2 min read

This release fixes the import of incoming CII invoices (ZUGFeRD / XRechnung CII) that carry more than one VAT breakdown (BG-23) or more than one document-level allowance or charge. It also adds a single direct debit mandate event that passes the source table of the posted document, so an extension can tell a sales invoice from a sales credit memo with the same number.

Bugfix​
  • Incoming CII invoices with two or more VAT breakdowns (BG-23, e.g. one group with category S 19 % and one with E 0 %) stopped during import with the error that the record already exists in table mseDoc365 xInvoice VAT Line with No. 1. The same happened with two or more document-level allowances or charges (BG-20/BG-21). While reading the XML, mseDoc365 first buffers these records and writes them only after parsing. The VAT lines were numbered from the database, which is still empty at that point, and the allowance number was fixed to 1, so every record got No. 1. The XML reader now numbers VAT breakdowns and document-level allowances/charges consecutively per document. No schema update is needed (CHN-595)
Enhancements​
  • New integration event OnBeforeResolveDirectDebitMandateForDocument in the buffer table mseBC mseDoc365 S. Inv.Buffer for payment means 59 (SEPA direct debit). It combines the two existing events and additionally passes SourceTableNo (Database::"Sales Invoice Header" or Database::"Sales Cr.Memo Header"). A posted sales invoice and a posted sales credit memo can share a number series, so the document number alone did not identify the document. A subscriber can return the mandate ID (BT-89), the debtor IBAN (BT-91) and the creditor ID (BT-90). The events OnBeforeResolveDirectDebitMandate and OnBeforeResolveDirectDebitMandateWithCreditorID are now marked obsolete but are still raised before the new event, so existing subscribers keep working. See Direct Debit Mandate per Document