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

Fixture ID: emptyPeriod · XPath: /ubl:Invoice/cac:InvoicePeriod

1. Why This Rule Triggers (Diagnostic Message)

The invoice carries an invoicing period (BG-14) with neither a start date (BT-73), an end date (BT-74) nor a tax point date code (BT-8). An empty period asserts that the supply relates to a timeframe and then declines to say which — and the timeframe is what a periodic invoice is *for*: it is how the buyer accrues the cost to the right month and how both sides detect a gap or an overlap between consecutive invoices. Note that a period carrying only the description code is legal in the UBL binding, because BT-8 has nowhere else to live; a period carrying nothing at all is not.

2. How to Fix BR-CO-19

Set invoicingPeriod.startDate, invoicingPeriod.endDate, or both, as ISO dates. Remove the invoicingPeriod object entirely if the supply is a one-off with a delivery date (BT-72) rather than a period.

3. Valid Code / Payload Example

"invoicingPeriod": { "startDate": "2026-07-01", "endDate": "2026-07-31" }