BR-04: Invoice type code (BT-3) is missing – e-invoice error explained

StandardEN 16931-1 (European e-invoicing semantic model)SeverityError: the invoice is rejectedSyntaxUBL, CIIBusiness terms

BT-3 Invoice type code

Applies toEvery EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles.

Official rule text

[BR-04] An Invoice shall have an Invoice type code (BT-3).

Why this error occurs

The rule checks that the document type is coded: cbc:InvoiceTypeCode (UBL Invoice) or cbc:CreditNoteTypeCode (UBL CreditNote), or rsm:ExchangedDocument/ram:TypeCode in CII. Receivers use this code to route the document into the right booking process (invoice, credit note, corrective invoice). It is normally missing when the export template has no type mapping or hard-codes an empty element.

How to fix it

In UBL add cbc:InvoiceTypeCode after cbc:IssueDate (for a CreditNote document use cbc:CreditNoteTypeCode). In CII add rsm:ExchangedDocument/ram:TypeCode. Use a code from UNTDID 1001, typically 380 (commercial invoice), 381 (credit note), 384 (corrected invoice), 389 (self-billed invoice); see BR-CL-01 for the full allowed list. Note that 381 is not allowed in a UBL Invoice document, use a UBL CreditNote instead.

Example (valid)

<cbc:IssueDate>2026-10-14</cbc:IssueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>

What the validator checks

Checked element (context):

UBL

/ubl:Invoice | /cn:CreditNote

Test (XPath):

normalize-space(cbc:InvoiceTypeCode) != '' or normalize-space(cbc:CreditNoteTypeCode) !=''

CII

/rsm:CrossIndustryInvoice

Test (XPath):

normalize-space(rsm:ExchangedDocument/ram:TypeCode) != ''

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

BR-01 Specification identifier (BT-24) is missing
BR-02 Invoice number (BT-1) is missing
BR-03 Invoice issue date (BT-2) is missing
BR-05 Invoice currency code (BT-5) is missing
BR-06 Seller name (BT-27) is missing
BR-07 Buyer name (BT-44) is missing
BR-08 Seller postal address is missing
BR-09 Seller country code (BT-40) is missing

Frequently asked questions

What does BR-04 mean?

BR-04 is a en 16931 core rule: An Invoice shall have an Invoice type code (BT-3).

Will my invoice be rejected because of BR-04?

Yes. BR-04 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.

Which formats does BR-04 apply to?

Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.

Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.