Skip to content

Coverage and accuracy

Henri Lepic edited this page Nov 22, 2026 · 9 revisions

What ZeRechnung supports, how it compares with the reference validators, and what it does not do yet. A longer analysis in French, criterion by criterion, is on Grille de la norme and Ce que valide ZeRechnung.

Contents

Profiles

Profile Read Write Schema Profile rules
MINIMUM yes yes yes yes
BASIC WL yes yes yes yes
BASIC yes yes yes yes
EN 16931 yes yes yes yes
EXTENDED yes yes yes yes
XRECHNUNG (CII) yes yes full CII D16B schema, like the KoSIT validator yes; BR-DE applied automatically
EXTENDED-CTC-FR yes yes EXTENDED schema, included in the CII D22B schema of the FNFE-MPE package yes; in CII, syntax rules of the FNFE-MPE EXTENDED-CTC-FR schematron; BR-FR on request (France or Auto)
PEPPOL (CII) yes yes EN 16931 schema yes; Peppol rules applied automatically
NLCIUS (CII) yes yes EN 16931 schema yes; BR-NL applied automatically
CIUS-IT (CII) yes yes EN 16931 schema yes; CIUS-IT rules (BR-IT) applied automatically
FatturaPA 1.2 (FPA12, FPR12) yes (as CIUS-IT) yes FatturaPA 1.2.4 schema, except the content of the XML signature, with the same verdicts as xmllint; the 40 SDI controls on the content that need none of the SDI data (00300 to 00476) through UBL or CII: CIUS-IT rules once written with ubl.Marshal or cii.Marshal, and those of the Italian extensions (BR-IT-DE) in UBL
Facturae 3.2, 3.2.1, 3.2.2 yes yes (3.2.2) schema of its version, except the content of the XML signature and of the extensions; values readable (FE-01) through UBL or CII: EN 16931 rules once written with ubl.Marshal or cii.Marshal (warning FE-02)
ZUGFeRD 1.0 (BASIC, COMFORT, EXTENDED) yes (as BASIC, EN 16931, EXTENDED) no: written back as Factur-X minimal structural check (ZF1-01 to ZF1-03) n/a: predates EN 16931 (warning ZF1-04)
UBL 2.1 (EN 16931, XRECHNUNG, PEPPOL, NLCIUS, CIUS-IT) yes yes UBL 2.1 schema (Invoice, CreditNote), except the content of extensions n/a; BR-DE (UBL schematron) applied automatically for XRECHNUNG, Peppol (UBL schematron) for PEPPOL, BR-NL (SI-UBL 2.0 schematron) for NLCIUS, BR-IT with the rules of the Italian extensions (BR-IT-DE) for CIUS-IT, BR-FR (UBL schematron) on request

XRECHNUNG in CII

A CII XRECHNUNG invoice is checked, as in the KoSIT validator, against the full UN/CEFACT CII D16B schema of its configuration (XRechnung 3.0.2). D16B elements outside the EN 16931 set are accepted there, and the CII-SR rules report them. Only one reference to a preceding invoice (BG-3) is allowed, so cii.Marshal writes only one for XRECHNUNG.

EXTENDED-CTC-FR in CII

A CII EXTENDED-CTC-FR invoice gets, instead of the CEN syntax rules, those of the FNFE-MPE schematron EXTENDED-CTC-FR-CII.sch (France_RFE 1.4.0.04), with its severities and messages: 434 CII-SR (38 blocking), 92 CII-DT and 9 rules of its own (CII-FREXT-SR, CII-EXT-DT-018, CII-FREXT-DT-024, CII-FREXTDT-027). Data that EXTENDED-CTC-FR allows is not reported: line notes with a subject, type and measure of an item characteristic, order reference and Incoterm at line level, exemption reason on an allowance or charge, credit transfer without an account, several payment cards or mandates, an attachment without MIME type or file name, contract reference type...

It is still checked against the EXTENDED schema, which is included in the CII D22B schema the FNFE-MPE package uses to validate CII invoices (the tests verify this), and not against D22B. The FNFE completes D22B with its whole schematron, including a business pattern (BR-FREXT...) that ZeRechnung does not implement, so D22B plus the syntax rules would not give its full verdict.

The EXTENDED schema is stricter than the FNFE, whose package knows EXTENDED-CTC-FR only in CII and UBL, not in Factur-X. Out of 2,931 variants of the 5 EXTENDED-CTC-FR examples of France_RFE (each element removed or duplicated, targeted mutations on the syntax rules), 125 are accepted by the FNFE (valid against D22B, no blocking rule) but rejected by the EXTENDED schema. They have two contents in a note, two item descriptions or payment terms descriptions, a second BusinessProcessSpecifiedDocumentContextParameter, a description in the delivery terms, and even no document totals (BG-22), which the FNFE schematron does not block.

Rule sets

Set Rules Reference
Schema 11 checks (elements, order, cardinalities, attributes, namespaces, types, closed lists, fixed values) Factur-X 1.09.2 XSD (ZUGFeRD 2.5.2), UN/CEFACT CII D16B XSD from the KoSIT XRechnung 3.0.2 configuration (XRECHNUNG) and OASIS UBL 2.1 XSD (Invoice, CreditNote), compiled into Go tables
EN 16931 793 assertions (328 errors, 465 warnings): BR, BR-CO, BR-CL, BR-DEC, rules per VAT category (BR-S, BR-Z, BR-E, BR-AE, BR-IC, BR-IG, BR-IP, BR-G, BR-O, BR-AF, BR-AG, BR-B), CII-SR, CII-DT. For EXTENDED-CTC-FR in CII, 535 syntax rules (108 errors, 427 warnings) replace the CEN's: CII-SR (434), CII-DT (92), CII-FREXT and CII-EXT (9) CEN TC 434 artefacts v1.3.17 (CII); syntax pattern of the FNFE-MPE EXTENDED-CTC-FR-CII schematron v1.4.0.04
EN 16931 (UBL) Same business rules, with the contexts and tests of the UBL artefacts (categories L and M, tolerances, BR-DEC on text, UBL-specific code lists); 759 syntax rules (62 errors, 697 warnings): UBL-CR (678), UBL-SR (57), UBL-DT (24) CEN TC 434 artefacts v1.3.17 (UBL)
Factur-X 544 rules (523 errors, 21 warnings): profile identification (BT-24), assertions of the MINIMUM and BASIC WL schematrons, unused elements per profile; code lists of the BASIC (48), EN 16931 (58) and EXTENDED (209) schematrons; BR-FXEXT rules of EXTENDED and EXTENDED-CTC-FR (line sub-types and groupings, totals with tolerance, logistics charges and third-party charges, VAT breakdown per category, rate and exemption reason) Factur-X 1.09 schematrons (MINIMUM, BASIC WL); Factur-X 1.09.2 schematrons and code lists (BASIC, EN 16931, EXTENDED); Factur-X 1.09.2 EXTENDED XSLT (ZUGFeRD 2.5.2)
France (BR-FR) 59 rules, 170 assertions in CII, 173 in UBL: SIREN/SIRET, electronic addresses, mandatory mentions, billing frames, multi-seller; 3 checks of admitted profiles (FR-PROFILE) FNFE-MPE schematrons v1.4.0.04 (CII and UBL)
Germany (BR-DE) 52 assertions in CII, 57 in UBL (BR-DE, BR-DE-CVD, BR-DEX, BR-TMP; PEPPOL-EN16931-R043 in UBL); BMF profile check (DE-PROFILE-01); Leitweg-ID and GEBA format and check digits (DE-LEITWEG-01, DE-LEITWEG-02, DE-GEBA-01, DE-GEBA-02) KoSIT XRechnung 3.0.2 schematrons (CII and UBL); BMF; Leitweg-ID Formatspezifikation 2.0.2; GEBA Formatspezifikation 1.0.1
Peppol BIS Billing 3.0 CII: 90 assertions (73 errors, 17 warnings); UBL: 165 assertions (139 errors, 26 warnings), 76 of them UBL-only. PEPPOL-EN16931-R, PEPPOL-COMMON-R (identifiers by ICD scheme), restricted code lists, national rules NO, DK, IT, SE and NL, and in UBL GR, IS and DE Peppol BIS Billing 3.0.21 schematrons (PEPPOL-EN16931-CII.sch and PEPPOL-EN16931-UBL.sch, unchanged in 3.0.22)
Netherlands (BR-NL) CII: 32 assertions (10 errors, 22 warnings); UBL: 43 assertions (22 errors, 21 warnings), including the SI-UBL 2.0 version check (BII2-T10-R001, SI-V20-INV-R000) and the 8 G-account rules (BR-GA-0 to BR-GA-7). KVK and OIN identifiers, buyer and order references, addresses, document types, payment means, G-account, discouraged data, empty elements NPa artefacts of 2026-05-21: NLCIUS-CII 1.0.3.13 (NLCIUS-CII-validation.sch), SI-UBL 2.0.3.13 (si-ubl-2.0.sch, si-ubl-2.0-nlcius.sch), G-account extension 1.0.2.13 (si-ubl-2.0-ext-gaccount.sch)
Italy (BR-IT, SDI) 149 rules (141 errors, 8 warnings): 59 of the 61 CIUS-IT rules of appendix 2 (lengths and character sets, addresses and provinces, identifiers, payment means, VAT categories, split payment); the 45 rules of the Italian extensions of appendix 3 (BR-IT-DE), on the UBL extensions and elements of the domestic invoice of a seller in Italy (BR-IT-DE-052 in CII too); the specification identifier check (IT-PROFILE-01); Partita IVA and Codice Fiscale formats and check characters (IT-PIVA-01/02, IT-CF-01/02); the 40 SDI controls on the content of a FatturaPA document that need none of the SDI data, under their codes (00300 to 00476) Italian technical rules 2.7 (Regole tecniche, art. 3 d.lgs. 148/2018), appendices 2 and 3, written from their tables (no official schematron); code lists of the FatturaPA 1.2.4 schema; extension URIs of the AgID documentation; FatturaPA technical specifications 1.9.1 and 1.10, appendix 1
ZUGFeRD 1.0 4 checks (ZF1-01 to ZF1-04): ZUGFeRD 1.0 profile identifier, readable values, data that identifies an invoice; a warning that no EN 16931, Factur-X or national rule applies ZUGFeRD 1.0 specification (FeRD, 2014)
Chorus Pro (B2G) 8 checks (CPRO-01 to CPRO-08): SIRET of the public body, service code, engagement number, document type, invoice number Chorus Pro external specifications (EDI annex V4.23)
PDF container 72 checks (PDF-01 to PDF-72), listed below Factur-X 1.08 and 1.09 specification (§ 6.2.2), ISO 19005-2, 19005-3 and 19005-4, numbered like the veraPDF validation profiles for PDF/A-2b and PDF/A-3b; rules 6.1.3-4 and 6.1.3-5 of the veraPDF PDF/A-4 profile

Messages are those of the official artefacts. Code lists (countries, currencies, units, identifier schemes, exemption reasons...) are embedded.

What the PDF checks cover

  • PDF/A-3 or PDF/A-4f declared, consistent with the PDF version.
  • XMP fx metadata consistent with the XML; the attachment, /AF, /AFRelationship by profile and country, MIME type, encryption.
  • PDF/A prerequisites that can be checked without rendering: embedded fonts, forbidden JavaScript and actions (/OpenAction, links, bookmarks, /AA), consistency between /Info and the XMP (warning), /Info of a PDF/A-4 document (absent, or reduced to ModDate with PieceInfo in the catalog), supporting attachments (/AFRelationship, MIME type, presence in an /AF), filters (LZWDecode, Crypt, non-standard filters).
  • PDF/A-2 and PDF/A-3 requirements, checked without rendering (PDF-41 to PDF-69, PDF-71 and PDF-72, clause by clause, not applied to a PDF/A-4 document): file syntax (header, end of file, xref tables, hex strings, streams, objects, implementation limits), output intents and ICC profiles, colour spaces, graphics states, images, XObjects, font dictionaries and encodings, annotations, forms, XMP (packets, properties of predefined schemas and their value types, extension schemas), optional content, presentations.
  • Page content, with the form XObjects, patterns, soft masks, Type 3 glyphs and annotation appearances it uses: operators and the resources they take (PDF-71), syntax and nesting of q, inline images, colour spaces set by the operators, overprinting, ri, transparency. Also the JP2 header of JPEG 2000 images, the CIDs of embedded CMaps and the /ID of the newest trailer of a linearized file.
  • Font programs (TrueType, CFF and OpenType) and Type 3 glyphs, read the way veraPDF reads them: every glyph the text shows exists in the program, with the width of the font dictionary to one unit, and none is .notdef; the CharSet of a subset Type 1 font and the CIDSet of a subset CIDFont list exactly the glyphs of the program (PDF-72); the glyph names of the Differences of a non-symbolic TrueType font are in the Adobe Glyph List, and its program has a (3,1) cmap (PDF-60).

Measured accuracy

The Conformance workflow runs on every pull request. It runs the reference validators on 282 invoices from the ZUGFeRD corpus and the KoSIT test suite, and compares the rules raised as errors, invoice by invoice. For NLCIUS, it runs the NPa schematron XSLTs on 290 files and compares the rules raised as errors and warnings. Method and details: conformance/README.md (in French).

Reference Invoices compared Same rules Justified differences
KoSIT validator 1.6.3, XRechnung 3.0.2 configuration of 2026-08-31 128 128 0
Mustang 2.26.0 282 241 41
NPa XSLTs (Saxon-HE 12.10): NLCIUS-CII 1.0.3.13, SI-UBL 2.0.3.13, G-account 1.0.2.13 290 283 7

KoSIT and Mustang

With KoSIT, every invoice compared has the same errors. With Mustang, each difference is justified in conformance/parity/known.txt, and any new difference fails the job. The differences come from the references themselves: Mustang applies neither Peppol BIS 3.0 nor the KoSIT configuration to XRechnung invoices (rule severities, CII D16B XSD), and embeds the XRechnung 2.4.0 schematron (2.6.0 for KoSIT and ZeRechnung).

The 26 deliberately invalid invoices of the corpus (ZUGFeRDv2/fail, not_validating examples) are checked one by one by TestOfficialNegativeCases against the errors of the references.

Corpus coverage

  • All 104 hybrid PDFs of the corpus (ZUGFeRDv2/correct, XML-Rechnung/FX) are extracted, and all 26 of their XML files are read.
  • The 73 UBL invoices of the corpus (XML-Rechnung/UBL, 28) and of the KoSIT test suite (45) are read, written back, read again into the same model, and validated with no errors other than the 3 expected ones: BR-CL-25 on the two examples using scheme 9958 (as in CII) and the not_validating... example, invalid on purpose. All respect the UBL 2.1 schema. On 11,000 randomly modified variants of these invoices (order, cardinalities, types, attributes, namespaces, extensions), the schema check gives the same verdict as xmllint (libxml2) with the OASIS XSDs.
  • The 41 CII invoices of the KoSIT test suite respect the CII D16B schema, as in the KoSIT validator. The 28 CII and Factur-X invoices of the FNFE-MPE examples (France_RFE 1.4.0.04, Z.example/TEST) respect the schema of their profile and the CII D22B schema. On 9,000 randomly modified variants (3,000 KoSIT invoices against D16B, 3,000 EXTENDED invoices against D22B, and the same against the EXTENDED XSD), the schema check gives the same verdict as xmllint with the original XSDs. The tests also verify, on the compiled tables, that each Factur-X schema is included in the reference schema of its profile: EN 16931 in D16B (apart from the number of BG-3), and EXTENDED in D22B.

EXTENDED-CTC-FR syntax rules

They give the same CII findings (same count per rule and severity) as the EXTENDED-CTC-FR-CII.xslt of France_RFE 1.4.0.04 run by Saxon. This holds on the 28 CII and Factur-X XML examples, which have none, and on 10,000 variants of the 5 EXTENDED-CTC-FR examples, each modified to break a syntax rule: identical findings on the 8,716 the XSLT processes, while it stops on a type error for the other 1,284 (repeated amounts in particular). 525 of the 535 rules are triggered; unit tests cover CII-SR-038 and CII-SR-339, and the total-counting rules (CII-SR-477 to 487) on which the XSLT stops.

Peppol

The Peppol rules give the expected result on the 351 CII unit tests of the Peppol BIS Billing 3.0 repository (87 test sets, folders rules/unit-CII-*, versions 3.0.21 and 3.0.22). The three assertions they do not cover (PEPPOL-COMMON-R040, R041, R056-2) are covered by ZeRechnung's own tests.

The UBL schematron rules give the expected result on the 678 UBL unit tests (153 test sets, 687 assertions, folders rules/unit-UBL-*, versions 3.0.21 and 3.0.22). The 13 assertions they never make fail (PEPPOL-EN16931-R008, PEPPOL-COMMON-R041, R056-2, IS-R-001 to IS-R-010) are covered by ZeRechnung's tests. The 26 official examples (rules/examples, rules/snippets) pass the default validation (UBL schema, EN 16931 and Peppol) with no errors.

NLCIUS

The BR-NL catalogue repeats, identifier by identifier, the severity and message of each assertion of the NPa schematrons, which a test checks.

On the 107 SimplerInvoicing test files for SI-UBL 2.0.3.2, NLCIUS-CII 1.0.3 and the G-account extension 1.0 (taken from phive-rules), whose names give the broken rule and its severity, ZeRechnung raises that rule with that severity, and nothing else. Only 4 names do not tell the whole rule raised: code 381 on an Invoice, which BR-NL-8 reports since SI-UBL 2.0.3; code 532 on a credit note, which also breaks BR-NL-7; and the two files with the message of BR-NL-34, whose assertions carry the identifier BR-NL-32-1. The 9 error files of the extension name the tested case rather than the rule, and each raises the BR-GA rule of that case. The 38 files that break no rule pass the full validation (schema, EN 16931, BR-NL) with no errors, and the valid extension example with no warnings.

The parity job also compares these rules with the NPa XSLTs run by Saxon, file by file, errors and warnings included, along with the EN 16931 rules these XSLTs include. On these 107 files, the 3 NLCIUS invoices of the repository and the 180 variants the mutation tests derive from them, ZeRechnung raises the same NLCIUS rules as the XSLTs (BR-NL, BR-GA, version and empty-element checks), at the same severity, and gives the same verdict. The 7 differences, each justified, concern EN 16931 rules: UBL-SR-57, added by CEN 1.3.17 while the XSLTs include 1.3.16, and 5 XSLT stops on an XPath type error (an element repeated where the schema allows it once), which ZeRechnung reports with the syntax rule or the schema. The 8 NLCIUS assertions no file triggers are those excluded by rule order. Any new difference, or any assertion that stops firing, fails the job.

FatturaPA signatures

The FatturaPA signature interoperability job of the Conformance workflow crosses the fatturapa package with three reference implementations, both ways, on a test PKI generated at run time. OpenSSL 3.5 (cms -verify -cades), xmlsec1 1.3 and EU DSS 6.5.1 verify the files SignCAdES and SignXAdES write with RSA, RSA-PSS and ECDSA keys: DSS classes them CAdES-BASELINE-B and XAdES-BASELINE-B, with the format, integrity and signing certificate checks of ETSI EN 319 102-1 passed. The package verifies the 13 files those tools sign: OpenSSL with and without -cades, in BER or PEM, RSA-PSS with the longest salt; xmlsec1 with exclusive C14N, C14N 1.1 and the XPath transform; DSS in XAdES (XPath Filter 2.0) and in CAdES.

Round trips

Of the 147 CII XML files read from the ZUGFeRD corpus and the XML extracted from its PDFs, 145 are written back as EXTENDED with their whole tree. The other 2 carry data no Factur-X profile allows (the German bank code of ZUGFeRD 2.0, since removed from the schema, and a reference type on a supporting document other than 130), and Marshal reports it. A document that contains every element of the EXTENDED XSD with all its attributes is read and written back identically, except for that same element forbidden by the rules.

All 21 ZUGFeRD 1.0 XML files extracted from the PDFs of ZUGFeRDv1/correct are read, one with an unreadable date (20139102, an error in the document). Written back as Factur-X, 8 keep their whole tree in EXTENDED. The other 12 readable ones lose only data no Factur-X profile allows (bank name, German bank code, insurance tax, empty tax registration...), and Marshal reports it. The 3 PDFs of ZUGFeRDv1/fail each have at least one ZF1-01 to ZF1-03 error.

PDF/A checks

The container's PDF/A checks are run against the 998 PDF/A-2b and PDF/A-3b test files of the veraPDF corpus, whose names give the ISO 19005 clause tested and the expected verdict. None of the 384 valid files raises a PDF/A error; the one whose /Info differs from the XMP (clause 6.1.5) raises PDF-35 as a warning. 609 of the 614 invalid files raise a rule of their clause. The other 5 are listed in the test with their reason: a value type of an XMP extension schema without pdfaType:field, and 4 files of the PDF/A-2 identification, which PDF-04 already reports since it expects PDF/A-3 or PDF/A-4 for an invoice. A file that changes verdict fails the test.

The files ConvertPDFA writes are checked with veraPDF 1.30.3: of the same 998 files, 836 are converted and 835 of them pass; the last one is the XMP value type above. The 162 others are refused, all invalid files but one signed document. The non-conforming PDFs the tests generate pass too once converted.

PDF and XML readers

The PDF reader is written for this package: classic xref tables and xref streams, object streams, incremental updates, reconstruction when the xref table is damaged, Flate (with predictors), ASCIIHex and ASCII85 filters. Decompression is capped (256 MiB per stream) and nesting depth is limited, so a hostile file can neither exhaust memory nor overflow the stack. The decompressor is tested by differential fuzzing against compress/flate.

The XML reader is written for this package too: a single pass over the bytes, resolved namespaces, nesting limited to 256 levels, DOCTYPE declarations ignored and no entity expanded apart from the five predefined ones. It is tested by differential fuzzing against encoding/xml: same documents accepted, same tree. The fast BT-24 lookup (the profile of the attachment, read by Embed and CheckContainer without building a tree) is in turn compared with this reader by fuzzing: same root element, same identifier.

Limitations

Partial PDF/A conversion

Embed declares PDF/A-3 (or PDF/A-4f for a PDF 2.0) in the XMP, but touches neither fonts, colour spaces nor output intents. With EmbedOptions.ConvertPDFA, a host that does not declare PDF/A is first rewritten as PDF/A-3 by ConvertPDFA, in pure Go and without rendering: output intent, XMP, removal of JavaScript and forbidden entries, LZW re-encoded, graphics states, images and annotations cleaned. What would need a PDF engine is refused with its reasons (ConversionError, wrapping ErrNotConvertible): a font that shows visible text without being embedded, a glyph its program lacks or whose width differs, DeviceCMYK without a CMYK profile, JPEG 2000 data PDF/A does not allow, a hidden annotation or one without an appearance, a signed document, PDF 2.0 (PDF/A-4 is not written). EmbedOptions.RequirePDFA instead refuses a host that does not declare PDF/A-2, PDF/A-3 or PDF/A-4 in its XMP.

PDF/A validation

Check reports what is missing among the PDF/A-2 and PDF/A-3 requirements, page content and font programs included, but it does not replace a PDF/A validator such as veraPDF. It does not check:

  • Type 1 font programs (FontFile), and the glyphs of Type 0 fonts whose CMap is predefined but not Identity;
  • the glyphs and widths of invisible text (rendering mode 3), as veraPDF does not either;
  • the value types of XMP extension schemas;
  • the requirements of levels A and U (logical structure, Unicode mapping): Factur-X and ZUGFeRD only need level B, which ConvertPDFA declares unless the PDF already declares A or U, and a PDF that declares level A or U is checked as level B.

A document that declares PDF/A-4 gets only part of these rules, which were written for PDF/A-2 and PDF/A-3. A font present in a page's resources without being embedded is a warning (PDF-31): whether the content draws visible text with it is not analysed. An /Info entry that differs from its XMP equivalent is a warning too (PDF-35): PDF/A-1 required equivalence (6.7.3), PDF/A-2 and PDF/A-3 no longer do (6.1.5), but a reader may show either value. The /Info of a PDF/A-4 document is not compared with the XMP: PDF-70 checks that it is absent, or contains only ModDate when the catalog has a PieceInfo entry (19005-4, 6.1.3).

Content streams and font programs are always read: on a 149 KB invoice, this adds about 0.2 ms to Check.

UBL: extensions not checked, BR-FR not compared with the official schematrons

The UBL 2.1 schema declares the content of extensions (ext:ExtensionContent) as lax xsd:any, and the signature schemas it imports for them (xmldsig, XAdES) are not compiled. Only the namespace and the number of elements of an extension are checked, not their content. The exception is the Italian domestic invoice: for a seller in Italy, the Italy set checks the content of its extensions (EXT-IT) with the rules of appendix 3 of the technical rules (BR-IT-DE).

The BR-FR rules follow the UBL schematron of their set, but have not been compared with a run of the official schematron; mutation tests check them. The BR-DE rules are compared with KoSIT by the parity job, on the UBL XRechnung invoices of the corpus and the KoSIT suite.

The Germany set does not write the Peppol rules that the XRechnung schematrons include, except PEPPOL-EN16931-R043 in UBL: they belong to the Peppol set, and a UBL invoice checked with both sets sees R043 reported by each. The Chorus Pro rules run on a CII view of the document; their findings are located in the UBL.

EXTENDED-CTC-FR: CII syntax only

The business pattern of the FNFE EXTENDED-CTC-FR schematron (BR-FREXT, code lists, blocking BR-CO-25...) is not applied. An EXTENDED-CTC-FR invoice gets the business rules of the Factur-X EXTENDED XSLT (BR-FXEXT and the subset of CEN rules it includes). In UBL, an EXTENDED-CTC-FR invoice gets the CEN UBL rules, not those of the UBL EXTENDED-CTC-FR schematron.

Other limits

  • Encrypted PDFs are reported (PDF-01), not decrypted.
  • FatturaPA is checked against its XSD 1.2.4, which also accepts the tax regime RF21 that the XSD 1.2.3, in force until 10/01/2027, lacks. Of the SDI controls on the content, those that need the SDI data are not applied: duplicates (00002, 00404), recipient codes (00311, 00312), consistency with the Anagrafe tributaria (00320 to 00327) and declarations of intent (00477); tax codes are checked by format and check character only (see Validating invoices). Signatures are Baseline B only, without timestamps, and VerifySignature downloads nothing: the caller gives the trusted roots, CRLs and OCSP responses (see Reading invoices).
  • Facturae has no official mapping to EN 16931: the facturae package follows its own. The XAdES signature is neither created nor verified. There is no Spanish rule set: the business rules of the Spanish tax agency (AEAT) are a draft with no error codes nor schematron, written for UBL 2.5 on EN 16931-1:2026, and the NIF check is not published. ubl.Marshal does not write the UBL of the AEAT public solution (2026 identifier, Spanish BT-ES elements).
  • The CIUS-IT rules and those of its extensions are written from the tables of the Italian technical rules, which publish no schematron: no parity can be measured. The extensions of the domestic invoice are checked, and read into and written from the Italian blocks of the model (invoice.Italy...) by ubl.Parse and ubl.Marshal; the FatturaPA data that they cannot carry (bank details, CIG and CUP codes beyond BT-17 and BT-11, delivery time...) is reported as lost by Strict.
  • ZUGFeRD 1.0 is read only, with a minimal check. The XML is read and can be written back as Factur-X, but not as ZUGFeRD 1.0. It is checked neither against the ZUGFeRD 1.0 XSD nor against business rules (see Reading invoices).
  • The schematron rules are rewritten in Go, not interpreted. A new version of the official artefacts requires a code update. The EN 16931 catalogues for CII and UBL and the EXTENDED-CTC-FR catalogue are regenerated by go generate, and the tests check they stay aligned.

Clone this wiki locally