SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BG-26

BR-CO-20 — E-Invoice Validation Rule & Fix

Fixture ID: emptyLinePeriod · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:InvoicePeriod

1. Why This Rule Triggers (Diagnostic Message)

Line 1 carries an invoice line period (BG-26) with neither a start date (BT-134) nor an end date (BT-135). Unlike the document level period (BG-14), a line period has no legal empty form: BT-8, the tax point date code that lets BG-14 exist without dates, is a document term and has no line equivalent, so a line period with no dates conveys nothing whatsoever. A line period exists to say that this line covers a different timeframe from the rest of the invoice — omit the group and the line simply inherits BG-14, which is usually what you want.

2. How to Fix BR-CO-20

Set line.period.startDate, line.period.endDate, or both, or remove line.period so the line falls back to the document level invoicing period. Note that line.period.descriptionCode is ignored at line level.

3. Valid Code / Payload Example

"period": { "startDate": "2026-07-01", "endDate": "2026-07-15" }
Test & Validate XML / JSON in Live SchemaGuard Validator →