Skip to content

EN16931 Validation artefacts v.1.3.3

Compare
Choose a tag to compare
@oriol oriol released this 02 Oct 13:58
· 221 commits to master since this release

This is version 1.3.3 of the EN16931 validation artefacts.

It supports the validation of UBL 2.1 and Cross Industry Invoice D16B.

Each ZIP file contains the validation artefacts as source Schematron as well as a single preprocessed Schematron (.sch) and as pre-compiled XSLT versions (.xslt).

For both syntaxes, example documents are contained in the folder "examples".

This release of the EN16931 validation artefacts is licensed using European Union Public Licence (EUPL) version 1.2.

Release notes

  • UBL-CR-295 should probably reference SellerSupplierParty #237
  • Update codes in schematron validations to support latest CEF distribution CodeList Format CII Format UBL #235
  • PartyTaxScheme not validated (correctly) #230
  • Wrong context for TaxTotal (for creditnote) #225
  • Belarusian Ruble wrong in ISO 4217 code list #224
  • BR-IG-09 i BR-IP-09 absolute values #223
  • Don't use xs:decimal when checking for existence BR-CO-16 #222
  • Weird characters at the end of rule "BR-E-05" #220
  • Rule BR-CO-19 not working correctly #219
  • Code list validation for cac:DeliveryLocation/ID #217
  • cac:PaymentMeans/cac:PayerFinancialAccount should not be valid Format #215
  • Change severity code “warning” to “fatal” for all rules in the UBL-SR-xx series #214
  • Spelling error in rule #213
  • Rules triggering at line-level should only trigger at header-level. #212
  • Extra code in ICD list CodeList #210
  • Use of due dates in CreditNotes #206

Important Note

When resolving issue #222, an error was introduced in the validation artefacts. When an instance contains a PayableRoundingAmount with a value of 0, the BR-CO-16 rule raises a false positive.
To avoid this error, a suitable work around is not providing PayableRounding Amount if its value is 0.
The bug is resolved in issue #242 and will be released in the upcoming spring release.