Author: admin

Mustang version 2.5.1, released Thu, 2022-05-12, fixes minor validation issues and switches to XRechnung version 2.2, mandatory as of August 2022. (Please note that while XR 2.2 can already be written, the validation is currently only possible available up to including version 2.1.)

Additionally, Despatch Advices are first supported, in terms of a hybrid Cross Industry Despatch advice in a pilot stage and in terms of the UBL based 1Lieferschein as a proof of concept for write support only.

Please note that since version 2.5.0 it is no longer possible to use “=” in the command line version between parameters and their options, i.e. e.g. instead of “–action=validate” one has to use the previously already available “–action validate”.

Today, April 7th, 2022, version 2.5.0 of the open source e-invoicing tool Mustangproject has been released. It adds support for Factur-X 1.0.6.0/ZUGFeRD 2.2 fixing various issues e.g. in the validation of electronic invoices. Additionally, it adds support for two industry recommendation, namely for the german railway industry (issue #253) and french B2G invoices vis á vis Chorus Pro, allowing to specify legalorganisation ID and scheme ID, which is one of the few Chorus Pro mandatory requirements. Additional fixes and changes are also mentioned in the project’s history file.

With version 2.4.0, Mustang now also supports Order-X.

So far, Mustangproject could read, write and validate XRechnung(CII) and Factur-X/ZUGFeRD invoices as well as
validate Order-X files. Now it can also read and write those orders.

If ERP vendors use the Mustang library to create electronic orders, they can now also use it to
compare invoices to their respective referenced orders: if the order has already been pre-processed and the
fulfillment of the services has been registered, the arrival of a matching invoice referring to the order
can now automatically trigger automatic payment and booking.

Additionally some minor issues have been fixed and the XRechnung has been updated to version
2.1.1 required for german B2G invoices as of February 1st, 2022.

Mustang 2.3.3 was released on Tuesday, December 21st 2021 and updated it’s logback library from version 1.2.3 to 1.2.9.
Version 2021-12-13 and 2021-12-20 of https://github.com/mergebase/log4j-detector did not issue any warning so far but Github’s Dependabot recommended a version > 1.2.7 in conjunction with Log4j.

Mustang 2.3.2 was released on Thursday, December 16th 2021. Apart from the fact that the invoice class can now be persisted e.g. using Jackson, whitespace removal has been reconfigured to leave newlines in place, which may be required for XRechnung’s cash discount and other small fixed detailled in the projects history.md.

Please note that Mustang was not affected by log4j CVE-2021-44228 or CVE-2021-45046.

Frankfurt am Main, 2021-12-06

In their coalition agreement the new german government apparently agreed on a
federal reporting system on VAT which will be used for the creation, validation and forwarding of invoices
“ein elektronisches Meldesystem bundesweit einheitlich einführen, das für die Erstellung, Prüfung und Weiterleitung von Rechnungen verwendet wird”.

After Italy introducing mandatory business-to-business e-invoices in 2019 and France set to do so in 2026 (source when this was still planned for 2025) this agreement, together with other documents like a (realtively independent) (german) study, a (german) complaint by the Federal Audit Office, a (german) investigation by the research service of the Bundestag as well as a (german) request by the political liberal party, make it look as if these were preparations to introduce an obligation for e-invoices in Germany as well.

Jochen Stärk
jstaerk@usegroup.de

Mustang 2.3.1 was released on Monday, October 25th 2021, and features an improved and features the document type PARTIAL_BILLING, invoiceReferencedIssueDate, as well as specifiedProcuringProject. It’s now also possible to add multiple referenced documents per line item and the importer has been improved and can now e.g. also act on XML input, not only PDF.

XRechnung 2.1.1 validation is now possible and a PDF issue has been fixed.

Despite it’s only a minor feature this version is also called 2.3.0 to indicate that the changed (internal) PDF upgrade is also a good opportunity to confirm the output PDF/A validity of at least some random samples 🙂

Mustang 2.2.1 adds support for references to orders on line level which was the last required attribute to send XRechnungen to the Deutsche Bahn AG.

Mustang 2.2.0 adds support to validate orders in the Order-X standard and fixes some other issues.