BR-32:Each Document level allowance (BG-20) shall have a Document level allowance...
Each Document level allowance (BG-20) shall have a Document level allowance VAT category code (BT-95). Check the `cac:AllowanceCharge` element in your invoice XML.
Engine Classification
Ensure tax representative VAT identifier is present per EN16931 BR-32
Confidence: 80% · Applied automatically in pipeline
What is BR-32?
BR-32 is a fatal validation rule defined in the EN 16931 specification. It validates the CompanyID element under PartyTaxScheme in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: //cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID
Why This Error Matters
Invoice rejected. VAT cannot be correctly calculated without knowing the tax category.
BR-32 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-32
- ·Specification: EN 16931
How to Fix It
Check payment means
If code is 30, 31, 42 - bank account needed
Add IBAN
In PayeeFinancialAccount/ID
Add BIC
Optional but recommended in FinancialInstitutionBranch
Before / After
<Invoice> <!-- cac:AllowanceCharge is missing --> </Invoice>
<Invoice> <cac:AllowanceCharge>valid-value</cac:AllowanceCharge> </Invoice>
Technical Reference
//cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyIDCode Example
<cac:PaymentMeans>
<cbc:PaymentMeansCode>30</cbc:PaymentMeansCode>
<cac:PayeeFinancialAccount>
<cbc:ID>NL91ABNA0417164300</cbc:ID>
<cac:FinancialInstitutionBranch>
<cbc:ID>ABNANL2A</cbc:ID>
</cac:FinancialInstitutionBranch>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>Common Causes
- ·Document allowance missing VAT category assignment
- ·TaxCategory/ID not mapped for allowances
- ·Allowance created before tax category configured
- ·Export template missing allowance tax category
- ·VAT code lookup failed for allowance
Seeing this in production? The API handles BR-32 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
When payment means is credit transfer (30), payee bank account must be specified.
Add PayeeFinancialAccount with IBAN or account number. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-32 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
Many instances of BR-32 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including payment account required for credit transfer.
BR-32 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-32 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.