BT-125Attached document
Official rule text
[BR-DEX-01] The element … "Attached Document" (BT-125) uses a MIME code that is not permitted: … . In the case of an Extension, the MIME code application/xml may be used in addition to the list of mime codes (defined in section 8.2, "Binary Object").
Official text (German): Das Element … "Attached Document" (BT-125) benutzt einen nicht zulässigen MIME-Code: … . Im Falle einer Extension darf zusätzlich zu der Liste der mime codes (definiert in Abschnitt 8.2, "Binary Object") der MIME-Code application/xml genutzt werden.
Why this error occurs
The element or combination is not allowed in this context. The file contains something the standard forbids: an element that must not be repeated, a value that contradicts another field, or data that belongs to a different profile.
How to fix it
Remove the offending element or make the two fields consistent as described in the rule text. If your software adds the element automatically, check for a profile setting (e.g. "EN 16931" vs "EXTENDED") or an export option that suppresses it.
What the validator checks
Checked element (context):
UBL
cbc:EmbeddedDocumentBinaryObject[$isExtension]Test (XPath):
.[@mimeCode = 'application/pdf' or @mimeCode = 'image/png' or @mimeCode = 'image/jpeg' or @mimeCode = 'text/csv' or @mimeCode = 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' or @mimeCode = 'application/vnd.oasis.opendocument.spreadsheet' or @mimeCode = 'application/xml']CII
ram:AttachmentBinaryObject[$isExtension]Test (XPath):
.[@mimeCode = 'application/pdf' or @mimeCode = 'image/png' or @mimeCode = 'image/jpeg' or @mimeCode = 'text/csv' or @mimeCode = 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' or @mimeCode = 'application/vnd.oasis.opendocument.spreadsheet' or @mimeCode = 'application/xml']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.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
BR-TMP-5BT-125 "Attached document" (ram:AttachmentBinaryObject) may occur at most once within…BR-DEX-02The value of "Invoice line net amount" of an "INVOICE LINE" or a "SUB INVOICE LINE"…BR-DEX-03A Sub Invoice Line must contain exactly one "SUB INVOICE LINE VAT INFORMATION"BR-DEX-04Any scheme identifier in … MUST be coded using one of the ISO 6523 ICD listBR-DEX-05Any scheme identifier in … MUST be coded using one of the ISO 6523 ICD listBR-DEX-06Any scheme identifier in … MUST be coded using one of the ISO 6523 ICD listBR-DEX-07Any scheme identifier for an Endpoint Identifier in … MUST belong to the CEF EAS code…BR-DEX-08Any scheme identifier for a Delivery location identifier in … MUST be coded using one…
Frequently asked questions
What does BR-DEX-01 mean?
BR-DEX-01 is a xrechnung rule: The element … "Attached Document" (BT-125) uses a MIME code that is not permitted: … . In the case of an Extension, the MIME code application/xml may be used in addition to the list of mime codes (defined in section 8.2, "Binary Object").
Will my invoice be rejected because of BR-DEX-01?
Yes. BR-DEX-01 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-DEX-01 apply to?
XRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it. Syntax: UBL and CII.
Source: XRechnung 3.0.2, schematron 2.6.0 (KoSIT, September 2026). Catalogue generated from the official schematron on 2026-10-14.