errorbusinessPeppol BIS 3.0

PEPPOL-EN16931-P0100:Wrong invoice type code for Peppol

Fix: We set the invoice type code to 380 (Commercial Invoice), which is required for Peppol Invoice documents. Upload your invoice to fix this automatically.

Peppol Invoice documents must use type code 380 (Commercial Invoice). A different or missing type code was found.

Severity
Fatal
Rule set
Peppol BIS 3.0
Country
All EU
Fix type
AUTO-FIX
Confidence
95%

Engine Classification

Set invoice type code to 380 (Commercial Invoice) for Peppol documents

Confidence: 95% · Applied automatically in pipeline

What is PEPPOL-EN16931-P0100?

PEPPOL-EN16931-P0100 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the InvoiceTypeCode 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: /Invoice/cbc:InvoiceTypeCode

Why This Error Matters

Invoice will be rejected by PEPPOL validators. PEPPOL BIS Billing enforces specific format, type code, and VAT exemption code consistency requirements.

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

Peppol access points reject invoices with an incorrect type code. Your invoice will not reach the buyer until this is corrected.

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
  • ·Rejected by PEPPOL Access Points
  • ·Error returned: PEPPOL-EN16931-P0100
  • ·Specification: Peppol BIS 3.0

How to Fix It

.

.

.

Before / After

Failing XML
<Invoice>
  <!-- Issue: Invoice type code MUST be set according to the profile. -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per Peppol BIS 3.0 -->
</Invoice>

Technical Reference

XPath/Invoice/cbc:InvoiceTypeCode
SpecPeppol BIS 3.0
Operationset_value
StrategySet invoice type code to 380 (Commercial Invoice) for Peppol documents

Common Causes

  • ·Invoice type code not valid for PEPPOL profile
  • ·BT-3 InvoiceTypeCode not in allowed PEPPOL list
  • ·cbc:InvoiceTypeCode value invalid for BIS Billing
  • ·Document type not permitted in PEPPOL network
  • ·UNTDID 1001 code not matching profile requirements

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

Frequently Asked Questions

Peppol Invoice documents must use type code 380 (Commercial Invoice). A different or missing type code was found.

We set the invoice type code to 380 (Commercial Invoice), which is required for Peppol Invoice documents. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

Many instances of PEPPOL-EN16931-P0100 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

Share this guide:

Validate your invoice

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

Auto-fix PEPPOL-EN16931-P0100 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.