errorpeppol-bis-3
BR-29:Invoice period end date before start date
The Invoicing Period End Date (BT-74) is before the Start Date (BT-73). The end date must be on or after the start date.
We can fix this automatically
AUTO-FIXAuto-fix: Swap the start and end dates if they are reversed. This is a common data entry error where the dates are correct but in wrong fields.
No manual changes needed
Upload and Fix NowWhy This Error Matters
Invoice rejected. An invalid billing period cannot be processed.
How to Fix It
1
Identify the dates
Find StartDate and EndDate in the InvoicePeriod element
2
Compare values
Check if EndDate is before StartDate
3
Swap if reversed
Exchange the date values so StartDate <= EndDate
Code Example
<cac:PartyTaxScheme>
<cbc:CompanyID>NL123456789B01</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>Technical Details
XPath: /Invoice/cac:InvoicePeriod/cbc:StartDate and /Invoice/cac:InvoicePeriod/cbc:EndDate. Dates use YYYY-MM-DD format (ISO 8601).Common Causes
- Invoice period dates entered in wrong order
- End date before start date due to data entry error
- Date picker UI allowed illogical date range
- Copy-paste from previous invoice with wrong dates
- System timezone issue causing date comparison failure
Commonly Seen In
All invoicing software
Frequently Asked Questions
The seller must have a VAT identifier or tax registration number.
Add seller VAT number in PartyTaxScheme. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-29 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-29 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including seller vat identifier or tax number required.
BR-29 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
Last updated: 16 January 2026
Share this guide: