Release 26.5.61 on 19.11.2026
· 2 min read
This release keeps the document that Cegedim actually delivered to the customer — the PDF with Cegedim's qualified electronic signature — as the eDoc's main document. It also lets an extension that supplies the SEPA direct debit mandate also supply the creditor ID (BT-90).
Feature
- Documents sent via Cegedim/XimantiX: once Cegedim reports the job as finished, mseDoc365 fetches the document that Cegedim delivered to the end customer (the PDF with Cegedim's qualified electronic signature) and saves it on the eDoc with type Document, so it becomes the main document. The PDF that mseDoc365 had sent to Cegedim is kept with the new type Unsigned Document. The information log records the delivery type (for example Email). This happens on the synchronous poll, on a repeated send, and when the status is refreshed on the asynchronous route. The document is saved only once per Cegedim job. If Cegedim returns no file or a file that is not a PDF, only a warning is logged, the step stays successful and the sent PDF remains the main document (CHN-587)
Bugfix
- For payment means
59(SEPA direct debit), an extension that handledOnBeforeResolveDirectDebitMandatecould supply the mandate ID (BT-89) and the debtor IBAN (BT-91), but not the creditor ID (BT-90). BT-90 was always taken from the Creditor No. of the company bank account, so a payment add-on that keeps the creditor ID with its own mandates ran into the missing-creditor-ID error. The buffer table mseBC mseDoc365 S. Inv.Buffer now also raises the new integration eventOnBeforeResolveDirectDebitMandateWithCreditorID, which carries an additionalBankAssignedCreditorIDparameter. A creditor ID returned there is written to BT-90; if it stays empty, the creditor ID is resolved from the company bank account as before. The existing eventOnBeforeResolveDirectDebitMandateis still raised unchanged. See Creditor ID from Extensions