BR-O-09:Out of scope must be only category
Fix: Invoice Navigator automatically fixes this issue by correcting the `cbc:TaxAmount` element in your Invoice (BR-O-09). Upload your invoice to fix this automatically.
If O is used, only O category allowed on invoice.
Engine Classification
Set tax amount to 0 for Not subject to VAT breakdown per EN16931 BR-O-09
Confidence: 95% · Applied automatically in pipeline
What is BR-O-09?
BR-O-09 is a fatal validation rule defined in the EN 16931 specification. It validates the TaxAmount element under TaxSubtotal[cac:TaxCategory > ID='O'] 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:TaxTotal/cac:TaxSubtotal[cac:TaxCategory/cbc:ID='O']/cbc:TaxAmount
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-09 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-09
- ·Specification: EN 16931
How to Fix It
Check all categories
Look for mix of O with S, Z, E, etc.
Separate invoices
O cannot mix with other VAT categories
Before / After
<cac:TaxSubtotal> <cbc:TaxAmount>INVALID_CODE</cbc:TaxAmount> </cac:TaxSubtotal>
<cac:TaxSubtotal> <cbc:TaxAmount>VALID_CODE</cbc:TaxAmount> </cac:TaxSubtotal>
Technical Reference
//cac:TaxTotal/cac:TaxSubtotal[cac:TaxCategory/cbc:ID='O']/cbc:TaxAmountCommon Causes
- ·Category O breakdown shows non-zero tax amount
- ·BT-117 in O breakdown must be 0.00
- ·"Not subject to VAT" cannot have tax amount
- ·cbc:TaxAmount contains value instead of zero for O
- ·Tax calculation applied to out-of-scope category in error
Seeing this in production? The API handles BR-O-09 automatically. See the fix response →
Frequently Asked Questions
If O is used, only O category allowed on invoice.
Use separate invoices for different VAT treatments. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-O-09 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.
Many instances of BR-O-09 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including out of scope must be only category.
Related Errors
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for BR-O-09
Auto-fix BR-O-09 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.