UBL-CR-301: cac:TaxRepresentativeParty/cbc:IndustryClassificationCode not used by EN 16931
The UBL schema allows cac:TaxRepresentativeParty/cbc:IndustryClassificationCode at this place, but EN 16931 does not map it to any business term, so the CEN rules flag it. Below: the message, the cause and the fix.
- Specification: UBL syntax rules (UBL-CR, UBL-SR, UBL-DT), CEN EN 16931 validation artefacts 1.3.16
- Severity: warning
- Reported by
POST /einvoice/validateand our free validators, with a link to this page
The message validators print
UBL-CR-301 is a rule of the UBL syntax rules (UBL-CR, UBL-SR, UBL-DT) (CEN validation artefacts 1.3.16) for UBL. It is a warning: the invoice stays valid, but should be corrected.
[UBL-CR-301]-A UBL invoice should not include the TaxRepresentativeParty IndustryClassificationCodeWhat it checks
The UBL schema allows cac:TaxRepresentativeParty/cbc:IndustryClassificationCode at this place, but EN 16931 does not map it to any business term, so the CEN rules flag it. The rule is a warning: the invoice stays valid, but a receiver may ignore whatever the element holds.
Why invoices fail it
The generator writes the full syntax (a library that serialises every field it knows), or information that EN 16931 does not model is put into a free element of the syntax.
How to fix it
Remove cac:TaxRepresentativeParty/cbc:IndustryClassificationCode; if its content matters to the buyer, put it in the business term that carries that information (a note, BT-22, or an item attribute, BG-32).
This explanation covers the whole UBL-CR family (678 rules, overview), so this page is not indexed.
The rule as published
Where the rule applies (context) and what must hold (test), unmodified from CEN EN 16931 validation artefacts 1.3.16. An assert fails when its test is false.
Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.
context: /ubl:Invoice | /cn:CreditNote
test: not(cac:TaxRepresentativeParty/cbc:IndustryClassificationCode)Check your own invoice
Drop your XRechnung, ZUGFeRD or Peppol file into a free validator (Peppol BIS, XRechnung, Factur-X): each runs the same rule files and links every finding to its rule page. From your own code, POST /einvoice/validate (reference) returns the same check as JSON, each finding with an explanation field pointing here (5 calls a check, anonymous within the daily allowance).
Sources
- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — CEN/TC 434, published with the European Commission (Connecting Europe), consulted 2026-10-28
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — European Commission (Connecting Europe), for CEN/TC 434, consulted 2026-11-17. The EUPL permits reproduction and communication to the public, with the licence, the copyright notices and the disclaimer kept; a modified copy must say so. The rule library quotes the rule ids and messages of the BR-*, UBL-* and CII-* rules unmodified, credits the artefacts and links the licence.