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 (BT-135) shall be filled, or both.
What does this rule mean?
An invoice line has a period (BG-26) with neither a start date (BT-134) nor an end date (BT-135).
An empty period says nothing — at least one of the two dates must be filled.
- BG-26
- Invoice line period (group)
- BT-134
- Invoice line period start date
- BT-135
- Invoice line period end date
Official rule message (standard)
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.
Where the rule applies
Syntax: CII · UBL
The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.
UBL
cac:InvoiceLine/cac:InvoicePeriod | cac:CreditNoteLine/cac:InvoicePeriod
CII
//ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod
Technical test
The rule passes when this Schematron expression holds true:
(ram:StartDateTime) or (ram:EndDateTime)How to fix it
Touches amounts, VAT or IBAN. We never change these automatically — correct them in your source data.
Add the start and/or end date — or remove the empty period from the line.
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.