errorbusinessEN 16931

BR-O-07:When using this VAT category, the VAT rate must be 0 (zero). This category...

Fix: Invoice Navigator automatically fixes this issue by correcting the `cac:AllowanceCharge` element in your Invoice (BR-O-07). Upload your invoice to fix this automatically.

When using this VAT category, the VAT rate must be 0 (zero). This category does not have a positive tax rate (applies to `cac:AllowanceCharge`, rule BR-O-07).

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
95%
Category
tax

Engine Classification

Remove VAT rate from document-level charges with Not subject to VAT category per EN16931 BR-O-07

Confidence: 95% · Applied automatically in pipeline

What is BR-O-07?

BR-O-07 is a fatal validation rule defined in the EN 16931 specification. It validates the Percent element under TaxCategory in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:AllowanceCharge[cbc:ChargeIndicator='true']/cac:TaxCategory[cbc:ID='O']/cbc:Percent

Why This Error Matters

Invoice will be rejected. "Not subject to VAT" (category O) has strict rules: no VAT identifiers allowed, no other categories permitted, and exemption reason required. Non-compliance prevents validation.

BR-O-07 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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-O-07
  • ·Specification: EN 16931

How to Fix It

1.

Locate the disallowed element

Open your invoice XML and find cbc:Percent at //cac:AllowanceCharge[cbc:ChargeIndicator='true']/cac:TaxCategory[cbc:ID='O']/cbc:Percent. This element is not permitted in the target e-invoice profile and triggers BR-O-07.

2.

Remove cbc:Percent

Delete the entire cbc:Percent block and its child elements. Invoice Navigator automatically fixes this issue by correcting the `cac:AllowanceCharge` element in your Invoice (BR-O-07).

3.

Re-validate your invoice

Upload the corrected invoice to confirm BR-O-07 is resolved. If your software consistently adds this element, contact your vendor about their e-invoice export settings.

Before / After

Failing XML
<Invoice>
  <cac:AllowanceCharge>-100.00</cac:AllowanceCharge>
</Invoice>
Corrected XML
<Invoice>
  <cac:AllowanceCharge>100.00</cac:AllowanceCharge>
</Invoice>

Technical Reference

XPath//cac:AllowanceCharge[cbc:ChargeIndicator='true']/cac:TaxCategory[cbc:ID='O']/cbc:Percent
SpecEN 16931
Operationremove
StrategyRemove VAT rate from document-level charges with Not subject to VAT category per EN16931 BR-O-07

Common Causes

  • ·Document charge with category O contains VAT rate
  • ·BT-103 charge VAT rate present for O category
  • ·"Not subject to VAT" charges must not specify rate
  • ·cbc:Percent element on charge when should be omitted
  • ·Template includes rate field for out-of-scope charge

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

Frequently Asked Questions

When using this VAT category, the VAT rate must be 0 (zero). This category does not have a positive tax rate (applies to `cac:AllowanceCharge`, rule BR-O-07).

Invoice Navigator automatically fixes this issue by correcting the `cac:AllowanceCharge` element in your Invoice (BR-O-07). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, BR-O-07 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of BR-O-07 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Related Errors

Related Content

Last updated: 14 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-O-07

Auto-fix BR-O-07 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.