errorbusinessEN 16931

`PEPPOL-EN16931-R100`:Only one invoiced object is allowed pr line

Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R100). Upload your invoice to fix this automatically.

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 rejected by Peppol access points and never reaches the buyer.

Target path: //cac:InvoiceLine/cac:DocumentReference

Fix 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 — the invoice must be corrected and re-sent before it can reach the recipient.

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

How to Fix It

Locate the duplicate entries

Search for multiple cac:DocumentReference elements at //cac:InvoiceLine/cac:DocumentReference. Only one instance is allowed per the specification.

Remove the duplicates

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R100).

Re-validate your invoice

Upload the corrected invoice to confirm PEPPOL-EN16931-R100 is resolved.

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 →

Frequently Asked Questions

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

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.

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

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.

Validate your invoice

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

Upload XML

Auto-fix PEPPOL-EN16931-R100 in seconds

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

Fix it now Automate via API

PEPPOL-EN16931-R100:Only one invoiced object is allowed pr line