How do I fix PEPPOL-EN16931-R100?

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

Is PEPPOL-EN16931-R100 a critical error?

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

Can PEPPOL-EN16931-R100 be automatically fixed?

Many instances of PEPPOL-EN16931-R100 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-R100`:Only one invoiced object is allowed pr line

Only one invoiced object identifier is allowed per invoice line. Each line can reference at most one object (contract, order, etc.).

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

85%

Engine Classification

Remove duplicate document references per invoice line, keeping first

Confidence: 85% · Applied automatically in pipeline

What is PEPPOL-EN16931-R100?

PEPPOL-EN16931-R100 is a fatal validation rule defined in the EN 16931 specification. It validates the DocumentReference element 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

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Lines must have single object reference for clear traceability.

PEPPOL-EN16931-R100 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-R100
·Specification: EN 16931

Before / After

Failing XML

<Invoice>
  <!-- Issue: Only one invoiced object is allowed per line. -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cac:InvoiceLine/cac:DocumentReference

SpecEN 16931

Operationremove_duplicates

StrategyRemove duplicate document references per invoice line, keeping first

Common Causes

·Multiple object references on single line
·ERP exports multiple document references per line
·Line consolidation merged objects incorrectly
·Template allows multiple object fields
·Manual addition of extra references

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

Handle PEPPOL-EN16931-R100 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-R100:Only one invoiced object is allowed pr line