How do I fix PEPPOL-EN16931-R101?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R101). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is PEPPOL-EN16931-R101 a critical error?

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

Can PEPPOL-EN16931-R101 be automatically fixed?

Many instances of PEPPOL-EN16931-R101 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorPeppol BIS 3.0

`PEPPOL-EN16931-R101`:Invoice line document reference has wrong type code

A document reference on one of your invoice lines uses the wrong type code. Line-level document references in Peppol invoices must use code "130", which means "invoice line object identifier".

Severity

Fatal

Rule set

Peppol BIS 3.0

Country

All EU

Fix type

AUTO-FIX

Confidence

95%

Engine Classification

Set DocumentTypeCode to "130" (invoice line object identifier) on all line-level DocumentReferences

Confidence: 95% · Applied automatically in pipeline

What is PEPPOL-EN16931-R101?

PEPPOL-EN16931-R101 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the DocumentTypeCode element under DocumentReference 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:DocumentReference/cbc:DocumentTypeCode

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Document references must be in correct structural location.

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

How to Fix It

Before / After

Failing XML

<Invoice>
  <!-- Issue: Element Document reference can only be used for Invoice line -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per Peppol BIS 3.0 -->
</Invoice>

Technical Reference

XPath//cac:InvoiceLine/cac:DocumentReference/cbc:DocumentTypeCode

SpecPeppol BIS 3.0

Operationset_value

StrategySet DocumentTypeCode to "130" (invoice line object identifier) on all line-level DocumentReferences

Common Causes

·Wrong type of document reference used at line level
·Contract or order reference placed in wrong location
·ERP maps document references to incorrect element
·Confusion between line and document level references
·Template structure error

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

Handle PEPPOL-EN16931-R101 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-R101:Invoice line document reference has wrong type code