EN 16931 rules › BR-CO-20
BR-CO-20 — If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date…
| Rule id | BR-CO-20 |
|---|---|
| Rule set | EN 16931 itself, not a national or network addition |
| Severity | fatal in CII and UBL — a validator enforcing this rule set rejects the invoice |
| Applies to | the CII and UBL syntaxes |
| Checked by | the validator on this site and invoicekit.go v0.2.11, the library behind it |
The rule as published
If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both.
fatal in CII and UBL — a validator enforcing this rule set rejects the invoice.
What runs for it
Straight from the artefacts the engine embeds: the node the assertion selects and the test it applies there. A failing invoice is reported with the message above.
| Syntax | Severity | Artefact phase | Applied to | Fails when |
|---|---|---|---|---|
| CII | fatal | EN16931-model-phase | //ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod | (ram:StartDateTime) or (ram:EndDateTime) |
| UBL | fatal | EN16931model_phase | cac:InvoiceLine/cac:InvoicePeriod | cac:CreditNoteLine/cac:InvoicePeriod | exists(cbc:StartDate) or exists(cbc:EndDate) |
Data elements it names
- BG-26 Invoice line period (cited by 1 rule)
- BT-134 Invoice line period start date (cited by 2 rules)
- BT-135 Invoice line period end date (cited by 2 rules)
See also
- Every EN 16931 rule id — the same list as a filterable table, with the assertions as CSV and JSON.
- What XRechnung and Peppol BIS add — rule sets that run these ids plus their own.
- The data elements — every BT and BG with the rules that name it.