Release 26.5.57 on 12.10.2026

This release fixes incoming credit memos: an XRechnung or ZUGFeRD credit memo received by folder or e-mail job now becomes a Purchase Credit Memo instead of a Purchase Invoice, decided from the type code BT-3 in the XML. AutoFlow flows can now run as steps of an mseDoc365 process, and the external document number and invoice date of a received xInvoice can be corrected by hand.

Feature

• Every active AutoFlow flow with the trigger When manually started on the eDocument table is now available as a process step of its own. The step's Parameter Name is the flow's Code, its description is AutoFlow: followed by the flow's description; add it to a process template like any other step. The step passes the eDocument to the flow and runs the flow to its end in the same session as the process, independent of the Job Queue and of the AutoFlow setup Manually start flows. If the flow fails, for example in an Error step, the step fails with the flow's error; the step's responses show the flow's execution number in AutoFlow. The list of steps is refreshed every time a process template is opened, so new flows appear and deleted or deactivated ones disappear. A flow is offered only if its Code has at most 20 characters and is not already used by another step. mseDoc365 does not depend on AutoFlow: without AutoFlow installed no flow steps are offered, and an existing flow step fails with a clear message. See Process Template (CHN-534)
• On the mseDoc365 xInvoice card, the fields Exchanged Document ID (external document no., BT-1) and Issued Date Time (invoice date, BT-2) are now editable, so a value that was read or recognised incorrectly can be corrected before the purchase document is created. The corrected values flow into Vendor Invoice No. and Document Date of the purchase document. Note that running the OCR step again overwrites manual corrections with the recognised values (CHN-537)

Bugfix

• Incoming credit memos (BT-3 type code 381 and the other credit-memo codes) received through a FunctionServer folder job or an e-mail job created a Purchase Invoice. The XML was read correctly, but the step Create invoice mapped the credit memo to an invoice. It now creates a Purchase Credit Memo and writes the vendor's credit memo number (BT-1) to Vendor Cr. Memo No.. Check for duplicate purchase invoice checks credit memos against open and posted purchase credit memos — an invoice with the same number no longer blocks a credit memo, and vice versa. Find order, Assign invoice lines and Assign order lines are skipped for credit memos, so a credit memo is never booked against a purchase order. Open Created Invoice on the eDoc card and on the xInvoice opens the credit memo, and posting it marks the xInvoice as posted with the posted credit memo number, just as for invoices. Inbound jobs must keep the document type RECEIVED; the job card now rejects PURCHASE-INVOICE and PURCHASE-CR.MEMO for direction In, because the type is decided from the XML. The credit memo is not applied to the original invoice automatically (BT-25). See Incoming Credit Memos (CHN-538)