BR-DE-17: Invoice type code outside the XRechnung list
An XRechnung should use only the invoice type codes 326 (partial invoice), 380 (commercial invoice), 384 (corrected invoice), 389 (self-billed invoice), 381 (credit note), 875, 876 and 877 (construction invoices). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.
- Specification: XRechnung 3.0 rules, XRechnung 3.0.2 schematron 2.6.0
- Severity: warning
- Business terms: BT-3
- Reported by
POST /einvoice/validateand our free validators, with a link to this page
The message validators print
BR-DE-17 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is a warning: the invoice stays valid, but should be corrected.
[BR-DE-17] Mit dem Element "Invoice type code" (BT-3) sollen ausschließlich folgende Codes aus der Codeliste UNTDID 1001 übermittelt werden: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice) und 381 (Credit note),875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).What it checks
An XRechnung should use only the invoice type codes 326 (partial invoice), 380 (commercial invoice), 384 (corrected invoice), 389 (self-billed invoice), 381 (credit note), 875, 876 and 877 (construction invoices). The rule is a warning: other UNTDID 1001 codes pass EN 16931 but are not expected by German public buyers.
Why invoices fail it
A prepayment invoice (386) or another code valid under EN 16931 is sent to a German public buyer.
How to fix it
Use one of the listed codes; a prepayment invoice is usually issued as a partial invoice (326) or a commercial invoice (380) with the advance noted.
A failing invoice and its fix, checked
We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as XRechnung 3.0 in UBL. The change below (- the failing version, + the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as POST /einvoice/validate runs them): the fixed one is valid, the failing one reports BR-DE-17.
| Rule | Severity | Where | Message |
|---|---|---|---|
| BR-DE-17 | warning | /ubl:Invoice | Mit dem Element "Invoice type code" (BT-3) sollen ausschließlich folgende Codes aus der Codeliste UNTDID 1001 übermittelt werden: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice) und 381 (Credit note),875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice). |
…
<cbc:IssueDate>2026-10-20</cbc:IssueDate>
<cbc:DueDate>2026-11-03</cbc:DueDate>
- <cbc:InvoiceTypeCode>386</cbc:InvoiceTypeCode>
+ <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
…The rule as published
Where the rule applies (context) and what must hold (test), unmodified from XRechnung 3.0.2 schematron 2.6.0. An assert fails when its test is false.
Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.
context: /ubl:Invoice | /cn:CreditNote
test: normalize-space(cbc:InvoiceTypeCode) = $supportedInvAndCNTypeCodes or normalize-space(cbc:CreditNoteTypeCode) = $supportedInvAndCNTypeCodescontext: /rsm:CrossIndustryInvoice
test: normalize-space(rsm:ExchangedDocument/ram:TypeCode) = ('326', '380', '384', '389', '381', '875', '876', '877')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).
The whole failing invoice (UBL)
<?xml version="1.0" encoding="UTF-8"?>
<ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
<cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
<cbc:ID>2026-017</cbc:ID>
<cbc:IssueDate>2026-10-20</cbc:IssueDate>
<cbc:DueDate>2026-11-03</cbc:DueDate>
<cbc:InvoiceTypeCode>386</cbc:InvoiceTypeCode>
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="EM">rechnung@hartmann-webdesign.example</cbc:EndpointID>
<cac:PostalAddress>
<cbc:StreetName>Lindenstraße 14</cbc:StreetName>
<cbc:CityName>Berlin</cbc:CityName>
<cbc:PostalZone>10969</cbc:PostalZone>
<cac:Country>
<cbc:IdentificationCode>DE</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:CompanyID>DE136695976</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Lena Hartmann — Webdesign</cbc:RegistrationName>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Lena Hartmann</cbc:Name>
<cbc:Telephone>+49 30 1234567</cbc:Telephone>
<cbc:ElectronicMail>rechnung@hartmann-webdesign.example</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingSupplierParty>
<cac:AccountingCustomerParty>
<cac:Party>
<cbc:EndpointID schemeID="EM">buchhaltung@mustermann.example</cbc:EndpointID>
<cac:PostalAddress>
<cbc:StreetName>Industrieweg 7</cbc:StreetName>
<cbc:CityName>Stuttgart</cbc:CityName>
<cbc:PostalZone>70565</cbc:PostalZone>
<cac:Country>
<cbc:IdentificationCode>DE</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyLegalEntity>
<cbc:RegistrationName>Mustermann Maschinenbau GmbH</cbc:RegistrationName>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:ElectronicMail>buchhaltung@mustermann.example</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingCustomerParty>
<cac:Delivery>
<cbc:ActualDeliveryDate>2026-10-15</cbc:ActualDeliveryDate>
</cac:Delivery>
<cac:PaymentMeans>
<cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
<cac:PayeeFinancialAccount>
<cbc:ID>DE02120300000000202051</cbc:ID>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>
<cac:TaxTotal>
<cbc:TaxAmount currencyID="EUR">457.60</cbc:TaxAmount>
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="EUR">2408.40</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="EUR">457.60</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>19.00</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>
</cac:TaxTotal>
<cac:LegalMonetaryTotal>
<cbc:LineExtensionAmount currencyID="EUR">2408.40</cbc:LineExtensionAmount>
<cbc:TaxExclusiveAmount currencyID="EUR">2408.40</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">2866.00</cbc:TaxInclusiveAmount>
<cbc:PayableAmount currencyID="EUR">2866.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:InvoicedQuantity unitCode="HUR">24.00</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">2280.00</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Name>Relaunch Website, Konzeption und Umsetzung</cbc:Name>
<cac:ClassifiedTaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>19.00</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="EUR">95.00</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>2</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">1.00</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">128.40</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Name>Lizenz Bildmaterial</cbc:Name>
<cac:ClassifiedTaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>19.00</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:ClassifiedTaxCategory>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="EUR">128.40</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
</ubl:Invoice>
Sources
- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — KoSIT (Koordinierungsstelle für IT-Standards), Bremen, consulted 2026-10-28
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — KoSIT, consulted 2026-10-28
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — KoSIT (Koordinierungsstelle für IT-Standards), Bremen, consulted 2026-11-17. Apache 2.0 permits redistribution with the licence and the notices kept. KoSIT’s LICENSE adds that the copyright in the EN 16931 standard lies with CEN. The rule library quotes the BR-DE-*, BR-DEX-* and BR-TMP-* messages unmodified, in KoSIT’s German.