errorbusinessEN 16931

BR-IC-01:Intra-community must be in breakdown

Fix: Add TaxSubtotal with TaxCategory/ID = "K".

If any line uses VAT category K, breakdown must include K.

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-IC-01?

BR-IC-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="K"]

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

Why This Error Matters

Invoice will be rejected. Intra-community supply (category IC) requires both seller and buyer VAT numbers for reverse charge mechanism. Missing elements prevent cross-border VAT compliance verification.

BR-IC-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-IC-01
  • ·Specification: EN 16931

How to Fix It

1.

Check for K lines

Any line with category K?

2.

Add breakdown

Include TaxSubtotal for K

Before / After

Failing XML
<Invoice>
  <cac:InvoiceLine>999.99</cac:InvoiceLine>
  <!-- Does not match expected calculation -->
</Invoice>
Corrected XML
<Invoice>
  <cac:InvoiceLine>100.00</cac:InvoiceLine>
  <!-- Matches expected calculation -->
</Invoice>

Technical Reference

XPathXPath: /Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cbc:ID="K"]
SpecEN 16931
Strategy1. Find all lines/allowances/charges with this VAT category. 2. Ensure exactly one TaxSubtotal with matching category exists. 3. Create if missing.

Common Causes

  • ·Intra-community category IC used but no BG-23 breakdown exists
  • ·Invoice lines tagged IC but tax breakdown section missing entry
  • ·cac:TaxSubtotal for intra-community supply not generated
  • ·IC transactions require explicit zero-rate VAT breakdown
  • ·Tax breakdown missing despite intra-community category on lines

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

Frequently Asked Questions

If any line uses VAT category K, breakdown must include K.

Add TaxSubtotal with TaxCategory/ID = "K". This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Yes, BR-IC-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-IC-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

BR-IC-02Intra-community requires both VAT IDsBR-IC-06Intra-community VAT 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: 25 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-IC-01

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

Fix it nowAutomate via API