BR-04: Invoice type code is required
Invoice type code is required; restore the invoice type code for the transaction.
What the rule says
[BR-04]-An Invoice shall have an Invoice type code (BT-3).
Official en16931 source, version 1.3.16. EUPL 1.2; sources, licences and notices. Syntax and business checks are separate; this is not certification.
Invoice type code is required
Invoice type code is required. The controlled example changes the specific field or group named by this rule. Remove only /*/cbc:InvoiceTypeCode.
Business terms: BT-3.
Restore the invoice type code for the transaction.
Reproduced failure and correction
Tested on 2 November 2026 with the production SaxonC-HE 13.1 / saxonche 13.1.1 engine, en16931 mode, UBL. The XSD passes; the report then contains BR-04. Restoring this fragment makes the complete original invoice pass the selected checks.
[BR-04]-An Invoice shall have an Invoice type code (BT-3).Additional triggered rules: 0. None. Counts include distinct error and warning codes; the target code is excluded.
Precise mutated XPath: /*/cbc:InvoiceTypeCode.
Before: triggers this rule
<!-- cbc:InvoiceTypeCode is absent at this position -->After: passes
<ns0:InvoiceTypeCode xmlns:ns0="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">380</ns0:InvoiceTypeCode>
The context shown is part of a complete invoice; it is not a standalone invoice. Mutation: remove at /*/cbc:InvoiceTypeCode. The passing baseline is validated with the selected pinned package. UBL examples use a controlled single-line adaptation of the official XRechnung example; the CII example uses the official EN 16931 baseline.
Download complete failing invoice · Download complete passing invoice
Check the rest of the invoice
Repair the source data and exporter, then validate the complete invoice again with the same package. Review every remaining error and warning; a passing rule is not a guarantee of recipient acceptance.
EN 16931 syntax and business checks · XRechnung profile requirements · Pro/Team batch checks.