errorformatPEPPOL_BIS

PEPPOL-EN16931-CL006:Invoice period description code must be according to UNCL 2005 D.16B.

Fix: The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).

The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).

Severity
Fatal
Rule set
PEPPOL_BIS
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

What is PEPPOL-EN16931-CL006?

PEPPOL-EN16931-CL006 is a fatal validation rule defined in the PEPPOL_BIS specification.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Period descriptions must use standard codes for clarity.

PEPPOL-EN16931-CL006 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Rejected by PEPPOL Access Points
  • ·Error returned: PEPPOL-EN16931-CL006
  • ·Specification: PEPPOL_BIS

How to Fix It

1.

Identify the issue in your invoice

The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).

2.

Correct this in your invoicing software

The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).

3.

Re-export and validate

Generate a new invoice export from your accounting system and re-validate to confirm PEPPOL-EN16931-CL006 is resolved.

Technical Reference

SpecPEPPOL_BIS
StrategyAuto-fix: Map period description code to valid UNCL 2005 value. Common mappings for service/delivery periods. Safe code normalization.

Common Causes

  • ·Invalid period description code
  • ·Using wrong code list for period type
  • ·Custom description code used
  • ·Typo in period code
  • ·Old version of code used

Seeing this in production? The API handles PEPPOL-EN16931-CL006 automatically. See the fix response →

Frequently Asked Questions

The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.).

The invoice period description code must be from the UNCL 2005 D.16B list. This code describes what the invoicing period represents (delivery period, service period, etc.). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

Many instances of PEPPOL-EN16931-CL006 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: 14 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for PEPPOL-EN16931-CL006

Detect PEPPOL-EN16931-CL006 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.