Mustang 2.0.0

The move

ZUV has been completely integrated into Mustangproject and the development will continue there, so have a look on https://www.mustangproject.org/ if there is anything new: No more releases will be added here. This way you can also use it as a library, or if you prefer the command line application, use java -jar Mustang-CLI-2.0.0.jar --action=validate --source=factur-x.pdf .

New

ZUV/Mustang now also supports validating XRechnung 2.0, and throws notices if an EN16931-file does not comply to the XRechnung, unless of course started with --no-notices.

ZUV 0.9.0: ZUGFeRD 2.1.0

New Features

• Support for ZUGFeRD 2.1/Factur-X 1.0.05
• check against URI allowing for different fragments, e.g. XRechnung
• validate against updated CEN 1.3 schematron

Fixes

• #27 wrong exit code
• introduced fatal errors. new errors: filename empty (10), xml not extractable (17), En16931 CEN Schematron error (24)
• prevent accidental application of CEN EN16931 schematrons on extended profile
• solved issues when XML structures start with comments instead of root node
• fail better if -f missing
• corrected invalidation of complete output status for broken pdfs
• escape xml in report elements, e.g. < in criterion to become <

Changes

• mention filename in report
• validation element has been removed from pdf info and added as attribute in root, duration is now direct child of info
• file not found and file too small now without filename
• First XMLUnit tests
• Better Check of XML Validity also against documents which start with comments or not with xml header <?xml...
• added signature of Symtrax generated invoices
• XML output now pretty-printed (XML report may now contain header <?xml...)

ZUV 0.8.3: ZUGFeRD 2.0.1

• check for 1.0 or 2p0 in RDF, not 1.0 and 2.0 like before
• added #22 incorrect rounding error to automatic tests
• updated Schematron files to zf 2.0.1 with #22 fix

ZUV 0.8.2: corrected schematron

The corrected schematron/XSLT fixes #22 rounding errors when applying schematron

ZUV 0.8.1: single filename input

New features

• command line parameters -x (XML input file) and -z (PDF input file) were merged to -f, this will not automatically detect whether it's a PDF or a XML file
• added check for additional data correctness

Corrections

• #23 ZF2 basic was incorrectly checked against Minimum/Basic Without lines Schema/Schematron
• added Signature pdfMachine

Refactorings

• Created ZUGFeRDValidatorClass and MiscValidatorTests for e.g. tests without existing files

ZUV 0.8.0: Schema support

New features

• validate not only against schematron but also against schema files

Bugfixes

• updated Mustang to tackle #20 zf1 validation does not always return a section

ZUV 0.7.0: ZUGFeRD 2.0 support

This version of the open source ZUGFeRD/Factur-X e-invoice validator should

• Validate ZUGFeRD 1.0, Factur-X and ZUGFeRD 2.0 files (using VeraPDF and the according ZUGFeRD schematron files)
• display the number of applied and failed rules on XML as well (previously it was only PDF)
• fail on "too simple" documents, i.e. if no rule could be applied at all
• have a tighter check for profile names

ZUV 0.6.0: Factur-X compatible, validates XMP/PDF-A Schema Extensions, Location attribute

This version of the open source ZUGFeRD/Factur-X e-invoice validator is

• Factur-X compatible
• Mention xpath location where the errors occurred
• Has first automated (JUnit) tests
• refactors the way to collect&handle errors and
• validates XMP/PDF-A-Schema extension

Several additions/fixes

• Non-16931 profiles are no longer automatically (but still can be manually) checked,
• now writing a log file,
• attempt to find out which toolkit created that particular file (issue #2),
• fixing that XML could not be extracted from certain valid PDF/A-3 files (issue #9),
• added --action parameter (has to be validate), -f option changes to "-o -z",
• added APL license text,
• added possibility to check XML files only,
• fixing issues with files that contained a UTF8 BOM in the XML content ("Content not allowed in prolog"),
• Upgraded VeraPDF-validation from 1.10.5 to 1.12.1

XML Output Correction

• XML Output now closes <error> element
• all <error> elements are now in an <errors> list
• XML is now also validated if not grand total can be found