BG-4SellerBG-11Seller tax representative partyBG-12Seller tax representative postal address
Official rule text
[BR-19] The Seller tax representative postal address (BG-12) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11).
Why this error occurs
This rule only applies when another field has a certain value (for example a payment means code or an invoice type). Your file triggers the condition but does not provide the data that then becomes mandatory, or provides data that is then forbidden.
How to fix it
Either change the triggering value so the condition no longer applies, or add/remove the dependent elements as the rule text describes. Check the condition in the XPath test above to see exactly which value triggers it.
What the validator checks
Checked element (context):
UBL
cac:TaxRepresentativePartyTest (XPath):
exists(cac:PostalAddress)CII
//ram:SellerTaxRepresentativeTradePartyTest (XPath):
(ram:PostalTradeAddress)
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-20The Seller tax representative postal address shall contain a Tax representative…BR-18The Seller tax representative name shall be provided in the Invoice, if the Seller has…BR-17The Payee name shall be provided in the Invoice, if the Payee is different from the SellerBR-56Each Seller tax representative party shall have a Seller tax representative VAT…BR-01Specification identifier (BT-24) is missingBR-02Invoice number (BT-1) is missingBR-03Invoice issue date (BT-2) is missingBR-04Invoice type code (BT-3) is missing
Frequently asked questions
What does BR-19 mean?
BR-19 is a en 16931 core rule: The Seller tax representative postal address (BG-12) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11).
Will my invoice be rejected because of BR-19?
Yes. BR-19 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-19 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.