Releases: ZUGFeRD/mustangproject
Mustang 2.5.6
Mustangproject version 2.5.6, released today, September 22nd 2022, adds some Javadoc documentation and removes a unneccessary dependency.
Mustang 2.5.5
Mustangproject 2.5.5, published on 2022-09-19, updates a library necessary for the validation of electronic invoices (ph-schematron).
Mustang 2.5.4: Invoiceimporter improvement
Mustang 2.5.4, published on 2022-09-01 allows to simultaneously specify IDs and global IDs and improves the Invoiceimporter.
Mustang 2.5.3: Global IDs
Mustang 2.5.3, released 2022-08-15, allows to specify global IDs like GTIN or GLN for both products and tradeparties.
Mustang 2.5.2: XRechnung 2.2 validation
Mustangproject 2.5.2, released 2022-07-09, adds support to also validate XRechnung 2.2 (CII) files, a new build profile and improved Order-X and Factur-X(thanks to Weclapp-Dev) XML.
The german B2G invoice CIUS, XRechnung, is set to mandatorily switch to version 2.2 as of August 2022.
Mustang 2.5.1: XR 2.2, Despatch Advices
Fixing 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
.
Mustang 2.5.0: ZUGFeRD 2.2
Mustang 2.5.0 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 the german railway industry (issue #253) and improves french B2G invoices vis á vis Chorus Pro, allowing to specify legalorganisation ID and scheme ID.
Mustang 2.4.0: 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 had been updated to version
2.1.1 required for german B2G invoices as of February 1st, 2022.
Mustang 2.3.3
2021-12-21
- updated logback from 1.2.3 to 1.2.9 https://github.com/ZUGFeRD/mustangproject/security/dependabot/validator/pom.xml/ch.qos.logback:logback-core/open
- neither 2021-12-13 nor 2021-12-20 of https://github.com/mergebase/log4j-detector have complained so far
Mustang 2.3.2
2021-12-16
- Jacksonability: Invoice and dependent objects can now be Stringified to / restored from a JSON (persistence? XML?) using e.g. Jackson
- Please note Mustang was not affected by log4j CVE-2021-44228 or CVE-2021-45046: this is not a security update
- unknown root elements will now throw separate errors (type 3)
- added some automated tests
- Remove faulty '/' from getNodeListByPath call. PR #256, Thanks again to Weclapp-dev
- Issue 238 Validierungsproblem mit Skonto/do not remove linebreaks in XML
- Do not trim trailing whitespace in XML submitted by the user, e.g. for XRechnung Skonto in PaymenttermsDescription