# BR-IC-11: Intra-Community supply without a delivery date

Source: https://veriport.io/einvoice-rules/br-ic-11 (published 2026-11-17)

An invoice with an intra-Community supply (a K breakdown) must state when the goods were delivered: the actual delivery date (BT-72) or an invoicing period (BG-14). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-72, BT-118, BG-14, BG-23
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-IC-11 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```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.
```

## What it checks

An invoice with an intra-Community supply (a K breakdown) must state when the goods were delivered: the actual delivery date (BT-72) or an invoicing period (BG-14). The date fixes the period in which the supply is reported in the recapitulative statement.

## Why invoices fail it

Goods invoices are written without a delivery date because it equals the invoice date.

## How to fix it

Write the delivery date in BT-72 (`cac:Delivery/cbc:ActualDeliveryDate`, `ram:ActualDeliverySupplyChainEvent`) or the period in BG-14.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-IC-11.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-IC-11** | error | `/ubl:Invoice` | 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. |

```diff
  …
    </cac:AccountingCustomerParty>
    <cac:Delivery>
+     <cbc:ActualDeliveryDate>2026-10-15</cbc:ActualDeliveryDate>
      <cac:DeliveryLocation>
        <cac:Address>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    (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']))
```

```xpath
context: //rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode[.= 'K'][upper-case(../ram:TypeCode) = 'VAT']
test:    (/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ActualDeliverySupplyChainEvent/ram:OccurrenceDateTime/udt:DateTimeString) or (../../ram:BillingSpecifiedPeriod/ram:StartDateTime) or (../../ram:BillingSpecifiedPeriod/ram:EndDateTime)
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-IC-09: K VAT amount not zero](https://veriport.io/einvoice-rules/br-ic-09)
- [BR-IC-10: No exemption reason for category K](https://veriport.io/einvoice-rules/br-ic-10)
- [BR-IC-12: Intra-Community supply without deliver-to country](https://veriport.io/einvoice-rules/br-ic-12)
- [BR-47: VAT breakdown category code (BT-118) missing](https://veriport.io/einvoice-rules/br-47)
- [BR-CO-18: At least one VAT breakdown (BG-23)](https://veriport.io/einvoice-rules/br-co-18)
- [BR-O-11: Category O mixed with other breakdowns](https://veriport.io/einvoice-rules/br-o-11)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
