BR-30: If both Invoice line period start date and Invoice line…

StandardEN 16931-1 (European e-invoicing semantic model)SeverityError: the invoice is rejectedSyntaxUBL, CIIBusiness terms

BT-134 Invoice line period start date
BT-135 Invoice line period end date

Applies toEvery EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles.

Official rule text

[BR-30] If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134).

Why this error occurs

This rule only applies when another field has a certain value (for example a payment means code or an invoice type). Your file triggers the condition but does not provide the data that then becomes mandatory, or provides data that is then forbidden.

How to fix it

Either change the triggering value so the condition no longer applies, or add/remove the dependent elements as the rule text describes. Check the condition in the XPath test above to see exactly which value triggers it.

What the validator checks

Checked element (context):

UBL

cac:InvoiceLine/cac:InvoicePeriod | cac:CreditNoteLine/cac:InvoicePeriod

Test (XPath):

(exists(cbc:EndDate) and exists(cbc:StartDate) and xs:date(cbc:EndDate) >= xs:date(cbc:StartDate)) or not(exists(cbc:StartDate)) or not(exists(cbc:EndDate))

CII

//ram:SpecifiedLineTradeSettlement/ram:BillingSpecifiedPeriod

Test (XPath):

(ram:EndDateTime/udt:DateTimeString[@format = '102']) >= (ram:StartDateTime/udt:DateTimeString[@format = '102']) or not (ram:EndDateTime) or not (ram:StartDateTime)

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

BR-CO-20 If Invoice line period is used, the Invoice line period start date or the Invoice line…
BR-01 Specification identifier (BT-24) is missing
BR-02 Invoice number (BT-1) is missing
BR-03 Invoice issue date (BT-2) is missing
BR-04 Invoice type code (BT-3) is missing
BR-05 Invoice currency code (BT-5) is missing
BR-06 Seller name (BT-27) is missing
BR-07 Buyer name (BT-44) is missing

Frequently asked questions

What does BR-30 mean?

BR-30 is a en 16931 core rule: If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134).

Will my invoice be rejected because of BR-30?

Yes. BR-30 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.

Which formats does BR-30 apply to?

Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.

Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.

BR-30: If both Invoice line period start date and Invoice line period end date are given then…