The invoicing period has neither a start nor an end date
As soon as the invoicing period (BG-14) is present, it must carry its start date (BT-73), its end date (BT-74), or both.
Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.
The message your validator prints
Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.
[BR-CO-19]-If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both.
Quoted from schematron-cen 1.3.16, licensed under EUPL-1.2.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
The empty group is produced by serialisers that write the structure before knowing whether they will have the data — a subscription whose period is computed downstream, an adjustment invoice without bounds. An absent group would be valid; it is the present-but-empty group that fails.
How to fix it
Fill at least one of the two bounds, or drop the group if the invoice covers no period. Both options are valid — the choice depends on what the invoice actually covers.
XML correction example
<ram:BillingSpecifiedPeriod/>
<ram:BillingSpecifiedPeriod>
<ram:StartDateTime>
<udt:DateTimeString format="102">20260801</udt:DateTimeString>
</ram:StartDateTime>
</ram:BillingSpecifiedPeriod>