Category: Uncategorized

Saturday, October 8th, we published the new functionality announced for October in a new endpoint, “PDF”, to create PDF/A-1 files from any input PDF provided. These can be plain PDFs, or even PDF/A-1 or PDF/A-3 files.

This re-renders the vector graphics in the PDF so it should actually work from any input PDF. Rumours have it that there can only be issues with class-1 fonts: Feel free to send me samples. A good validator to check the output is e.g. VeraPDF.

Of course all pages will be converted but embedded files will be stripped, so if you want to update the XML structure of an existing Factur-X PDF you can pass that in and afterwards perform another combine operation.

First subscription

Please note that despite we’re still in beta this is not a reason not to subscribe for the commercial support (500 Eur/year), actually we were able to welcome our first customer last week. We’ll shortly go live with details and a dedicated page to subscribe for commercial support. Please note that at the end of the beta, only users with commercial support will be provided access to the live system.

Version 1.2.0 of the free e-invoice-viewer Quba, published today, September 26th, 2022, continues to work offline, but can now also connect to Mustang Server, to validate invoices, confirming their syntactical and mathematical correctness.

The September release “Version 0.5” of Mustang Server was already published on Saturday, September 24th. Additionally to it’s own validator, it adds support for the Open-Source PHIVE validation engine, useful e.g. for UBL and Peppol invoices. As regards future planning, a PDF to PDF/A conversion feature is expected in October and a native integration of OAuth2 (currently available via it’s API Management) is expected for November.

Mustangproject version 2.5.6, released today, September 22nd 2022, adds some Javadoc documentation and removes a unneccessary dependency.

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, published on 2022-09-01 allows to simultaneously specify IDs and global IDs and improves the Invoiceimporter.

Mustang 2.5.3, released 2022-08-15, allows to specify global IDs like GTIN or GLN for both products and tradeparties.

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.

Today, on 2022-06-23, we published another corrected version of our open source cross platform e-invoice viewer, capable of displaying Factur-X/ZUGFeRD, XRechnung and PEPPOL invoices, Quba

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.