What does BR-DE-3 mean?
The element "Seller city" (BT-37) must be provided. This is a national KoSIT rule (XRechnung) that goes beyond EN 16931 and is mandatory for German e-invoices.
Common causes of BR-DE-3
- The element required by the German KoSIT rule is missing from the XML.
- The value appears only in the PDF, not in the structured data set.
- The entry was left empty.
How to fix BR-DE-3
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-37 along this XPath:
//ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityName - Apply the fix. Add the seller city (BT-37) in 'ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityName'.
- Validate again. Save the file and validate it again to check that BR-DE-3 is no longer reported.
Add the seller city (BT-37) in 'ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityName'.
//ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityNameBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
<ram:PostalTradeAddress>
<ram:PostcodeCode>80331</ram:PostcodeCode>
<!-- ram:CityName fehlt -->
<ram:CountryID>DE</ram:CountryID>
</ram:PostalTradeAddress>
<ram:PostalTradeAddress>
<ram:PostcodeCode>80331</ram:PostcodeCode>
<ram:CityName>München</ram:CityName>
<ram:CountryID>DE</ram:CountryID>
</ram:PostalTradeAddress>
Frequent questions about BR-DE-3
How do I fix BR-DE-3?
Related error codes
Check BR-DE-3 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.