PEPPOL-EN16931-R111:Invoice line billing period extends beyond invoice dates
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R111). Upload your invoice to fix this automatically.
One of your invoice lines has a billing period end date that falls outside the overall invoice period. For example, the invoice covers January but a line item says it ends in February.
Engine Classification
Suggest setting the line period end date to the invoice period end date. User must confirm the date is correct for their billing.
Confidence: 75% · Applied automatically in pipeline
What is PEPPOL-EN16931-R111?
PEPPOL-EN16931-R111 is a fatal validation rule defined in the EN 16931 specification. It validates the EndDate element under InvoicePeriod 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/cbc:EndDate
Why This Error Matters
Invoice will be rejected by PEPPOL validation. Line periods must be contained within the invoice billing period.
PEPPOL-EN16931-R111 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Peppol access points reject invoices where line billing periods extend beyond the invoice period. This inconsistency suggests a data entry error that could affect revenue recognition.
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: PEPPOL-EN16931-R111
- ·Specification: EN 16931
How to Fix It
Before / After
<Invoice> <!-- Issue: End date of line period MUST be within invoice period. --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
//cac:InvoiceLine/cac:InvoicePeriod/cbc:EndDateCommon Causes
- ·Line period ends after invoice period
- ·Invoice period updated without checking line periods
- ·Line added from different billing cycle
- ·Date entry error on line period end
- ·Service period extends beyond invoice coverage
Seeing this in production? The API handles PEPPOL-EN16931-R111 automatically. See the fix response →
Frequently Asked Questions
One of your invoice lines has a billing period end date that falls outside the overall invoice period. For example, the invoice covers January but a line item says it ends in February.
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R111). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, PEPPOL-EN16931-R111 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of PEPPOL-EN16931-R111 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for PEPPOL-EN16931-R111
Auto-fix PEPPOL-EN16931-R111 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.