How do I fix PEPPOL-EN16931-R111?

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.

Is PEPPOL-EN16931-R111 a critical error?

Yes, PEPPOL-EN16931-R111 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can PEPPOL-EN16931-R111 be automatically fixed?

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.

errorEN 16931

`PEPPOL-EN16931-R111`:Invoice line billing period extends beyond invoice dates

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.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

75%

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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: //cac:InvoiceLine/cac:InvoicePeriod/cbc:EndDate

Get API Access Test This Error ↓

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. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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

Failing XML

<Invoice>
  <!-- Issue: End date of line period MUST be within invoice period. -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath//cac:InvoiceLine/cac:InvoicePeriod/cbc:EndDate

SpecEN 16931

Operationset_value

StrategySuggest setting the line period end date to the invoice period end date. User must confirm the date is correct for their billing.

Common 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 →

Handle PEPPOL-EN16931-R111 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

PEPPOL-EN16931-R111:Invoice line billing period extends beyond invoice dates