errorbusinessEN 16931

`PEPPOL-EN16931-R004`:The specification identifier must be exactly...

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

The specification identifier must be exactly "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0". This identifies the invoice as PEPPOL BIS Billing 3.0 compliant.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Derive schemeID from country code or endpoint pattern

Confidence: 90% · Applied automatically in pipeline

What is PEPPOL-EN16931-R004?

PEPPOL-EN16931-R004 is a fatal validation rule defined in the EN 16931 specification. It validates the @schemeID element under Party > EndpointID 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:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID

Fix this error

Why This Error Matters

Invoice will be rejected by PEPPOL network. Incorrect specification identifier prevents proper validation and processing.

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

Seller endpoint required for Peppol network routing.

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-R004
·Specification: EN 16931

How to Fix It

Find the missing derived value

Check @schemeID at //cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID. This value should be computed from other fields in the invoice.

Derive the correct value

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

Re-validate your invoice

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

Before / After

Failing XML

<Invoice>
  <!-- Issue: Specification identifier MUST have the correct value. -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID

SpecEN 16931

Operationderive

StrategyDerive schemeID from country code or endpoint pattern

Common Causes

·Wrong or outdated specification identifier used
·Old PEPPOL BIS 2.0 identifier still in template
·Customization ID manually modified
·ERP configured for different e-invoice standard
·Typo in specification identifier string

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

Frequently Asked Questions

The specification identifier must be exactly "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0". This identifies the invoice as PEPPOL BIS Billing 3.0 compliant.

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

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

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

Upload XML

Auto-fix PEPPOL-EN16931-R004 in seconds

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

Fix it now Automate via API

PEPPOL-EN16931-R004:The specification identifier must be exactly...