BR-30:Invoice line period end date before start date
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-30). Upload your invoice to fix this automatically.
If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the end date shall be later or equal to the start date.
Engine Classification
Auto-fix: Swap the start and end dates on the line item if they are reversed. Same logic as document-level period fix.
What is BR-30?
BR-30 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoicePeriod element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: cac:InvoiceLine/cac:InvoicePeriod
Why This Error Matters
Invoice rejected. Invalid service period on line item.
BR-30 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-30
- ·Specification: EN 16931
How to Fix It
Identify the line
Find the InvoiceLine with the InvoicePeriod containing the date error
Check the dates
Compare StartDate and EndDate within the line's InvoicePeriod
Swap if reversed
Exchange the date values so StartDate <= EndDate
Before / After
<Invoice> <!-- Issue: If both Invoice line period start date and end date are give --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
cac:InvoiceLine/cac:InvoicePeriodCode Example
<cac:PaymentMeans>
<cbc:PaymentMeansCode>30</cbc:PaymentMeansCode>
<cac:PayeeFinancialAccount>
<cbc:ID>NL91ABNA0417164300</cbc:ID>
</cac:PayeeFinancialAccount>
</cac:PaymentMeans>Common Causes
- ·Line period dates entered in wrong order
- ·End date before start date on invoice line
- ·Service period copied incorrectly from contract
- ·Date validation not enforced at line level
- ·Partial period billing with incorrect date range
Seeing this in production? The API handles BR-30 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The invoice must specify how payment should be made using UNCL4461 code.
Add PaymentMeansCode with valid UNCL4461 code. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-30 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
Many instances of BR-30 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including payment means code required.
BR-30 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for BR-30
Auto-fix BR-30 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.