BG-14Invoicing periodBG-23VAT breakdownBT-72Actual delivery dateBT-118VAT category code
Official rule text
[BR-IC-11] In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Actual delivery date (BT-72) or the Invoicing period (BG-14) shall not be blank.
Why this error occurs
VAT rules tie the VAT category of the lines, allowances and charges to the VAT breakdown of the document. The validator checks that for every category used there is exactly one matching breakdown entry, that the rate and the exemption reason fit the category, and that taxable and tax amounts add up per category.
How to fix it
Use one VAT category code (UNTDID 5305: S standard, Z zero rated, E exempt, AE reverse charge, K intra-community, G export, O not subject, L/M Canary Islands/Ceuta) consistently on the lines and in the breakdown. For E, AE, K, G and O the rate must be 0 and an exemption reason (text or VATEX code) is required; for S the rate must be greater than 0 and no exemption reason is allowed. Recompute the taxable amount per category from the lines.
What the validator checks
Checked element (context):
UBL
/ubl:Invoice | /cn:CreditNoteTest (XPath):
(exists(cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/cbc:ID[normalize-space(.) = 'K']) and (string-length(cac:Delivery/cbc:ActualDeliveryDate) > 1 or (cac:InvoicePeriod/*))) or (not(cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/cbc:ID[normalize-space(.) = 'K']))CII
//rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode[.= 'K'][upper-case(../ram:TypeCode) = 'VAT']Test (XPath):
(/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString) or (../../ram:BillingSpecifiedPeriod/ram:StartDateTime) or (../../ram:BillingSpecifiedPeriod/ram:EndDateTime)
Check your invoice
Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
BR-IC-01An Invoice that contains an Invoice line, a Document level allowance or a Document…BR-IC-08In a VAT breakdown where the VAT category code is "Intra-community supply" the VAT…BR-IC-09The VAT category tax amount in a VAT breakdown where the VAT category code is…BR-IC-10A VAT breakdown with the VAT Category code "Intra-community supply" shall have a VAT…BR-IC-12In an Invoice with a VAT breakdown where the VAT category code is "Intra-community…BR-47Each VAT breakdown shall be defined through a VAT category codeBR-AE-01An Invoice that contains an Invoice line, a Document level allowance or a Document…BR-AE-08In a VAT breakdown where the VAT category code is "Reverse charge" the VAT category…
Frequently asked questions
What does BR-IC-11 mean?
BR-IC-11 is a en 16931 core rule: In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Actual delivery date (BT-72) or the Invoicing period (BG-14) shall not be blank.
Will my invoice be rejected because of BR-IC-11?
Yes. BR-IC-11 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.
Which formats does BR-IC-11 apply to?
Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.
Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.