XRechnung test suite version release-2026-01-31: UBL document reference interpreted as date

[stefan6419846]

When running Mustang-CLI (mustang --action validate --source 03.07a-INVOICE_ubl.xml), way to less rules seem to be applied and there are exceptions not represented in the validation report.

[main] INFO com.helger.schematron.api.xslt.AbstractSchematronXSLTBasedResource - Applying Schematron XSLT on XML instance
[main] WARN org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter - Failed to parse date ANG987654321 with pattern yyyy-MM-dd
java.text.ParseException: Unparseable date: "ANG987654321"
	at java.base/java.text.DateFormat.parse(DateFormat.java:399)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.parseDate(ZUGFeRDInvoiceImporter.java:1342)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.extractInto(ZUGFeRDInvoiceImporter.java:629)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.setDocument(ZUGFeRDInvoiceImporter.java:340)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.setRawXML(ZUGFeRDInvoiceImporter.java:297)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.setRawXML(ZUGFeRDInvoiceImporter.java:311)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.fromXML(ZUGFeRDInvoiceImporter.java:1462)
	at org.mustangproject.validator.XMLValidator.checkArithmetics(XMLValidator.java:456)
	at org.mustangproject.validator.XMLValidator.validate(XMLValidator.java:409)
	at org.mustangproject.validator.ZUGFeRDValidator.internalValidate(ZUGFeRDValidator.java:199)
	at org.mustangproject.validator.ZUGFeRDValidator.validate(ZUGFeRDValidator.java:254)
	at org.mustangproject.commandline.Main.performValidate(Main.java:482)
	at org.mustangproject.commandline.Main.main(Main.java:442)
[main] WARN org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter - Failed to parse date ANG987654321 with pattern yyyy-MM-dd
java.text.ParseException: Unparseable date: "ANG987654321"
	at java.base/java.text.DateFormat.parse(DateFormat.java:399)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.parseDate(ZUGFeRDInvoiceImporter.java:1342)
	at org.mustangproject.ZUGFeRD.ZUGFeRDInvoiceImporter.extractInto(ZUGFeRDInvoiceImporter.java:629)
	at org.mustangproject.validator.XMLValidator.checkArithmetics(XMLValidator.java:458)
	at org.mustangproject.validator.XMLValidator.validate(XMLValidator.java:409)
	at org.mustangproject.validator.ZUGFeRDValidator.internalValidate(ZUGFeRDValidator.java:199)
	at org.mustangproject.validator.ZUGFeRDValidator.validate(ZUGFeRDValidator.java:254)
	at org.mustangproject.commandline.Main.performValidate(Main.java:482)
	at org.mustangproject.commandline.Main.main(Main.java:442)
[main] INFO org.mustangproject.validator.ZUGFeRDValidator - Parsed PDF:absent XML:valid Signature:null Checksum:3BCFED594297D6CDE5D3937CF1C50E93C000B4F2 Profile:urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 Version:2 Took:2755ms Errors:[] ErrorIDs: []
<?xml version="1.0" encoding="UTF-8"?>

<validation filename="03.07a-INVOICE_ubl.xml" datetime="2026-02-23 13:54:53">
  <xml>
    <info>
      <version>2</version>
      <profile>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</profile>
      <validator version="2.22.0"/>
      <rules>
        <fired>30</fired>
        <failed>0</failed>
      </rules>
      <duration unit="ms">2648</duration>
    </info>
    <summary status="valid"/>
  </xml>
  <summary status="valid"/>
</validation>

The specific file is available in https://github.com/itplr-kosit/xrechnung-testsuite/releases/download/v2026-01-31/xrechnung-3.0.2-testsuite-2026-01-31.zip as instances/standard/03.07a-INVOICE_ubl.xml.

Running the validation against a custom implementation inspired by Mustang-CLI leads to 228 rules being fired, which looks much more correct.

[langfr]

According to
https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-OriginatorDocumentReference/
this element only has an ID, no date.

Current logic uses the ID element from the xml as document id and tries to parse it as document date.

Creating a PR to remove the date parsing.

[langfr]

Output after PR:

$ "$JAVA_HOME"/bin/java -jar Mustang-CLI-2.22.1-SNAPSHOT.jar --action validate --source 03.07a-INVOICE_ubl.xml
[main] INFO com.helger.schematron.xslt.SchematronResourceXSLTCache - Compiling XSLT instance [cpPath=/xslt/en16931schematron/EN16931-UBL-validation.xslt; urlResolved=true; URL=jar:file:/C:/GitHub/mustangproject/Mustang-CLI/target/Mustang-CLI-2.22.1-SNAPSHOT.jar!/xslt/en16931schematron/EN16931-UBL-validation.xslt]
[main] INFO com.helger.schematron.api.xslt.AbstractSchematronXSLTBasedResource - Applying Schematron XSLT on XML instance
[main] INFO com.helger.schematron.xslt.SchematronResourceXSLTCache - Compiling XSLT instance [cpPath=/xslt/XR_30/XRechnung-UBL-validation.xslt; urlResolved=true; URL=jar:file:/C:/GitHub/mustangproject/Mustang-CLI/target/Mustang-CLI-2.22.1-SNAPSHOT.jar!/xslt/XR_30/XRechnung-UBL-validation.xslt]
[main] WARN com.helger.xml.transform.LoggingTransformErrorListener - [warn] Transformation warning (net.sf.saxon.trans.XPathException: A function that computes atomic values should use xsl:sequence rather than xsl:value-of)
[main] WARN com.helger.xml.transform.LoggingTransformErrorListener - [warn] Transformation warning (net.sf.saxon.trans.XPathException: A function that computes atomic values should use xsl:sequence rather than xsl:value-of)
[main] INFO com.helger.schematron.api.xslt.AbstractSchematronXSLTBasedResource - Applying Schematron XSLT on XML instance
[main] INFO org.mustangproject.validator.ZUGFeRDValidator - Parsed PDF:absent XML:valid Signature:null Checksum:3BCFED594297D6CDE5D3937CF1C50E93C000B4F2 Profile:urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 Version:2 Took:2704ms Errors:[] ErrorIDs: []
<?xml version="1.0" encoding="UTF-8"?>

<validation filename="03.07a-INVOICE_ubl.xml" datetime="2026-03-01 13:49:07">
  <xml>
    <info>
      <version>2</version>
      <profile>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</profile>
      <validator version="2.22.1-SNAPSHOT"/>
      <rules>
        <fired>30</fired>
        <failed>0</failed>
      </rules>
      <duration unit="ms">2581</duration>
    </info>
    <summary status="valid"/>
  </xml>
  <summary status="valid"/>
</validation>

Exceptions are gone, but still only 30 rules applied.
Don't know, if this is really a problem / fault.

[stefan6419846]

For CII/UNCEFACT, only 38 rules are fired as well, which sounds rather low given that EN16931-CII-validation.xslt and XRechnung-CII-validation.xslt is used.

https://github.com/ZUGFeRD/mustangproject/tree/master/validator/src/main/resources/xslt/XR_30 indicates that it does not yet use the 2.5.0 release (https://github.com/itplr-kosit/xrechnung-schematron/releases/tag/v2.5.0), while https://github.com/ZUGFeRD/mustangproject/tree/master/validator/src/main/resources/xslt/en16931schematron uses version 1.3.12 instead of the 1.3.15 release (https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.15). Thus it either is related to outdated artifacts or implementation issues from either Mustang or my side.