errorbusinessEN 16931

BR-56:Each Seller tax representative party (BG-11) shall have a Seller tax...

Fix: Add the required `cac:TaxRepresentativeParty` element to your Invoice. Ensure it contains a valid value per EN 16931.

Invoice line allowance must have either reason code or text explanation.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
BLOCKED

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 rejected by Peppol access points and never reaches the buyer.

Target path: XPath: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator=false]

This error requires manual correction — financial fields are protected by policy.

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 — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-56
  • ·Specification: EN 16931

How to Fix It

1.

Find line allowance

Locate AllowanceCharge with ChargeIndicator=false

2.

Add reason code

Use UNCL5189 code like 95 (discount)

3.

Or add text

Add AllowanceChargeReason with explanation

Before / After

Failing XML
<Invoice>
  <!-- cac:TaxRepresentativeParty is missing -->
</Invoice>
Corrected XML
<Invoice>
  <cac:TaxRepresentativeParty>valid-value</cac:TaxRepresentativeParty>
</Invoice>

Technical Reference

XPathXPath: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator=false]
SpecEN 16931
StrategyBLOCKED: This is a legal VAT identifier. We cannot generate or guess VAT numbers - they are registered with tax authorities. Must come from the tax representative's official registration.

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 Errors

BR-55Prepayment should reference prepayment invoiceBR-57Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80)

Related Content

Learn
Free EN 16931 ValidatorValidate EN 16931 Invoices for germany
Glossary
Evidence Packe-Reporting
Errors
Invoice must have an issue dateMissing invoice type code
Answers
What is the difference between B2G and B2B e-invoicing?
Regulations
EN 16931

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-56

Detect BR-56 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API