How do I fix BR-IC-11?

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

Is BR-IC-11 a critical error?

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

Can BR-IC-11 be automatically fixed?

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

errorEN 16931

`BR-IC-11`:Missing delivery date for intra-community supply. Invoices with VAT category...

Missing delivery date for intra-community supply. Invoices with VAT category "Intra-community supply" (K) must have either a delivery date (BT-72) or invoicing period (BG-14).

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

85%

Engine Classification

1. Check VAT category consistency. 2. Ensure rates match categories. 3. Add missing identifiers.

Confidence: 85% · Applied automatically in pipeline

What is BR-IC-11?

BR-IC-11 is a fatal validation rule defined in the EN 16931 specification. It validates the ram:CountryID element under ram:PostalTradeAddress in the UBL invoice XML.

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: ram:ShipToTradeParty/ram:PostalTradeAddress/ram:CountryID

Get API Access Test This Error ↓

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-11 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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

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

XPathram:ShipToTradeParty/ram:PostalTradeAddress/ram:CountryID

SpecEN 16931

Operationderive

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

Common Causes

·Intra-community category on document charge without breakdown
·Document-level charge with IC category needs matching breakdown
·Charge with IC category not reflected in tax subtotal section
·cac:AllowanceCharge (charge) IC missing from tax breakdown
·IC charge handling incomplete in invoice structure

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

Related Errors

BR-45

Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).

BR-48

Document allowance tax category required

BR-AE-09

Reverse charge VAT breakdown tax amount must be zero

Last updated: 27 February 2026

Share this guide:

Handle BR-IC-11 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

BR-IC-11:Missing delivery date for intra-community supply. Invoices with VAT category...