errorbusinessEN 16931

BR-O-11:Mixed VAT categories with "Not subject to VAT". When using VAT category O...

Fix: Remove or correct the `cac:TaxSubtotal` element in your Invoice XML to comply with the rule.

Mixed VAT categories with "Not subject to VAT". When using VAT category O (Not subject to VAT), no other VAT categories are allowed on the invoice.

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

Engine Classification

Financial or legal field · Modification blocked by policy

What is BR-O-11?

BR-O-11 is a fatal validation rule defined in the EN 16931 specification.

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

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

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

How to Fix It

1.

Identify the issue in your invoice

Mixed VAT categories with "Not subject to VAT". When using VAT category O (Not subject to VAT), no other VAT categories are allowed on the invoice.

2.

Correct this in your invoicing software

Remove or correct the `cac:TaxSubtotal` element in your Invoice XML to comply with the rule.

3.

Re-export and validate

Generate a new invoice export from your accounting system and re-validate to confirm BR-O-11 is resolved.

Before / After

Failing XML
<cac:TaxTotal>
  <cac:TaxSubtotal>-100.00</cac:TaxSubtotal>
</cac:TaxTotal>
Corrected XML
<cac:TaxTotal>
  <cac:TaxSubtotal>100.00</cac:TaxSubtotal>
</cac:TaxTotal>

Technical Reference

SpecEN 16931
Strategy1. Check VAT category consistency. 2. Ensure rates match categories. 3. Add missing identifiers.

Common Causes

  • ·Invoice with O category contains other VAT categories
  • ·"Not subject to VAT" must be the only category on invoice
  • ·O breakdown found alongside S, E, or other categories
  • ·Mixed VAT treatment incompatible with O category
  • ·All items must be O when using out-of-scope category

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

Frequently Asked Questions

Mixed VAT categories with "Not subject to VAT". When using VAT category O (Not subject to VAT), no other VAT categories are allowed on the invoice.

Remove or correct the `cac:TaxSubtotal` element in your Invoice XML to comply with the rule. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

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

Related Errors

BR-45Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).BR-48Document allowance tax category requiredBR-AE-09Reverse charge VAT breakdown tax amount must be zero

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: 14 April 2026

Share this guide:

Validate your invoice

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

Detect BR-O-11 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