errorEN 16931

`BR-48`:Document allowance tax category required

Document-level allowances/charges must specify the VAT category.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Tax category assignment affects tax liability calculation. Must be determined based on the specific goods/services and applicable tax rules.

What is BR-48?

BR-48 is a fatal validation rule defined in the EN 16931 specification. It validates the TaxCategory element under Invoice > AllowanceCharge 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: /Invoice/cac:AllowanceCharge/cac:TaxCategory

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

Why This Error Matters

Invoice rejected. VAT rate is required for tax calculation verification and reporting.

BR-48 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-48
·Specification: EN 16931

How to Fix It

Add TaxCategory

Same structure as line item categories

Match category

Should match applicable line item categories

Include rate

Percent for standard rate

Before / After

Failing XML

<cac:TaxSubtotal>
  <!-- cbc:TaxAmount is missing -->
</cac:TaxSubtotal>

Corrected XML

<cac:TaxSubtotal>
  <cbc:TaxAmount>valid-value</cbc:TaxAmount>
</cac:TaxSubtotal>

Technical Reference

XPathXPath: /Invoice/cac:AllowanceCharge/cac:TaxCategory

SpecEN 16931

StrategyBLOCKED: VAT rates have legal implications. We cannot guess tax rates - using wrong rate causes tax compliance issues. Must come from source system tax configuration.

Code Example

<cac:AllowanceCharge>
  <cbc:ChargeIndicator>false</cbc:ChargeIndicator>
  <cbc:Amount currencyID="EUR">50.00</cbc:Amount>
  <cac:TaxCategory>
    <cbc:ID>S</cbc:ID>
    <cbc:Percent>21</cbc:Percent>
    <cac:TaxScheme>
      <cbc:ID>VAT</cbc:ID>
    </cac:TaxScheme>
  </cac:TaxCategory>
</cac:AllowanceCharge>

Common Causes

·VAT breakdown missing rate (Percent)
·TaxCategory/Percent not mapped in export
·Tax rate stored separately from tax category
·Zero-rate category missing explicit 0 percent
·Rate field empty for standard VAT category

Seeing this in production? The API handles BR-48 automatically. See the fix response →

Commonly Seen In

All invoicing software

Frequently Asked Questions

Document-level allowances/charges must specify the VAT category.

Add the required `cbc:TaxAmount` 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-48 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-48 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.

BR-48 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Detect BR-48 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.

Get API Access View API Documentation

BR-48:Document allowance tax category required