Start date of line period MUST be within invoice period.
The start of the invoice line period is before the start of the invoice period in the header. The test compares the line’s udt:DateTimeString with the header date and requires the line period to start no earlier.
An invoice line’s period must begin within the billing period stated in the invoice header. This keeps the line’s time coverage consistent with the invoice period.
An invoice line period starts before the invoice period stated in the header. You can resolve this by aligning the two start dates.
- Compare the invoice line’s
ram:StartDateTimewithram:StartDateTimein the invoice header. - Make sure the invoice line period does not start before the invoice period.
- Generate the invoice again and validate it.
<ram:BillingSpecifiedPeriod> <ram:StartDateTime> <udt:DateTimeString>2026-02-01</udt:DateTimeString> </ram:StartDateTime> </ram:BillingSpecifiedPeriod> <ram:BillingSpecifiedPeriod> <ram:StartDateTime> <udt:DateTimeString>2026-01-31</udt:DateTimeString> </ram:StartDateTime> </ram:BillingSpecifiedPeriod>
<ram:BillingSpecifiedPeriod> <ram:StartDateTime> <udt:DateTimeString>2026-02-01</udt:DateTimeString> </ram:StartDateTime> </ram:BillingSpecifiedPeriod> <ram:BillingSpecifiedPeriod> <ram:StartDateTime> <udt:DateTimeString>2026-02-01</udt:DateTimeString> </ram:StartDateTime> </ram:BillingSpecifiedPeriod>
Technical details
The rule is evaluated for invoice lines when the invoice header contains a ram:StartDateTime. Under the XPath comparison, the line start value must be greater than or equal to the header start value.
The rule applies to ram:StartDateTime in the ram:BillingSpecifiedPeriod of an invoice line when the invoice header also has a ram:BillingSpecifiedPeriod with a start date.
rule/@context)assert/@test)