Type of electronic address unknown
For the electronic address of the seller or buyer (BT-34, BT-49), a type is given that is not in the EAS code list.
What to do now
Who has to fix this?
The issuer of the invoice has to fix this: the detail is missing in the generated XML file. For invoices to public authorities, a violation usually leads to automatic rejection by the portal.
Where this rule comes from
This rule does not come from EN 16931 itself but from XRechnung, the German national specification (CIUS). It is mandatory for invoices to public-sector buyers in Germany and is checked by the invoice portals of the federal government and the federal states. It does not apply to pure B2B invoices in a ZUGFeRD profile.
- Rule ID
- BR-DEX-07
- Rule set
- XRechnung (German CIUS)
- Checked for
- XRechnung (UBL and CII)
- Consequence of a violation
- The invoice is considered non-compliant with the standard and is automatically rejected by many recipients.
Does BR-DEX-07 occur in your invoice?
Upload the XRechnung or the ZUGFeRD/Factur-X PDF – the validator shows every violation with the same explanation as here. Free, no login, nothing stored.
Validate your invoice nowGeneral information, not tax or legal advice. As of October 2026. Validation rules: CEN/TC 434 (EN 16931, EUPL 1.2), KoSIT (XRechnung, Apache 2.0), FNFE-MPE/FeRD (Factur-X/ZUGFeRD, Apache 2.0), OpenPeppol AISBL (Peppol BIS), ANAF (CIUS-RO). Explanations: Billvox. Licence notices