BR-56:Each Seller tax representative party (BG-11) shall have a Seller tax...
Invoice line allowance must have either reason code or text explanation.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: Allowance/charge reasons affect accounting treatment and tax reporting. The reason must accurately reflect the business purpose.
What is BR-56?
BR-56 is a fatal validation rule defined in the EN 16931 specification. It validates the AllowanceCharge element under InvoiceLine 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: XPath: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator=false]
Why This Error Matters
Invoice rejected. Tax representatives must be properly identified with their VAT number for tax authority compliance.
BR-56 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.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-56
- ·Specification: EN 16931
How to Fix It
Find line allowance
Locate AllowanceCharge with ChargeIndicator=false
Add reason code
Use UNCL5189 code like 95 (discount)
Or add text
Add AllowanceChargeReason with explanation
Before / After
<Invoice> <!-- cac:TaxRepresentativeParty is missing --> </Invoice>
<Invoice> <cac:TaxRepresentativeParty>valid-value</cac:TaxRepresentativeParty> </Invoice>
Technical Reference
XPath: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator=false]Common Causes
- ·Tax representative party without VAT identifier
- ·TaxRepresentativeParty missing PartyTaxScheme/CompanyID
- ·Fiscal rep configured without VAT number
- ·Template missing rep VAT identifier field
- ·VAT ID stored separately from representative record
Seeing this in production? The API handles BR-56 automatically. See the fix response →
Frequently Asked Questions
Invoice line allowance must have either reason code or text explanation.
Add the required `cac:TaxRepresentativeParty` element to your Invoice. Ensure it contains a valid value per EN 16931. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, BR-56 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.
BR-56 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
Related Content
Last updated: 3 March 2026
Detect BR-56 Before Submission
This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.