BR-S-01:Standard rate must be in VAT breakdown
Fix: Add TaxSubtotal with TaxCategory/ID = "S".
If any line uses VAT category S, VAT breakdown must include S category.
Engine Classification
Financial or legal field · Modification blocked by policy
What is BR-S-01?
BR-S-01 is a fatal validation rule defined in the EN 16931 specification. It validates the TaxCategory element under TaxTotal > TaxSubtotal 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: /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cbc:ID="S"]
Why This Error Matters
Invoice will be rejected. Standard rated VAT (category S) requires seller VAT registration, positive VAT rate, and correct tax calculations. Missing elements prevent tax compliance verification.
BR-S-01 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-S-01
- ·Specification: EN 16931
How to Fix It
Check line categories
Any line with TaxCategory S?
Add breakdown
Include TaxSubtotal for S with rate and amounts
Before / After
<Invoice> <cac:InvoiceLine>999.99</cac:InvoiceLine> <!-- Does not match expected calculation --> </Invoice>
<Invoice> <cac:InvoiceLine>100.00</cac:InvoiceLine> <!-- Matches expected calculation --> </Invoice>
Technical Reference
XPath: /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cbc:ID="S"]Common Causes
- ·Standard rated (S) category used but no S breakdown exists
- ·Invoice lines use BT-151=S but BG-23 missing S entry
- ·cac:TaxSubtotal for standard rate not generated
- ·Tax breakdown section lacks mandatory S category
- ·Standard rated items require matching breakdown entry
Seeing this in production? The API handles BR-S-01 automatically. See the fix response →
Frequently Asked Questions
If any line uses VAT category S, VAT breakdown must include S category.
Add TaxSubtotal with TaxCategory/ID = "S". This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, BR-S-01 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-S-01 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
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for BR-S-01
Detect BR-S-01 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.