How do I fix PEPPOL-EN16931-R005?

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

Is PEPPOL-EN16931-R005 a critical error?

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

Can PEPPOL-EN16931-R005 be automatically fixed?

Many instances of PEPPOL-EN16931-R005 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-R005`:VAT accounting currency code MUST be different from invoice currency code...

When a VAT accounting currency is provided, it must be different from the invoice currency. If they are the same, the VAT accounting currency field should not be used at all.

Severity

Fatal

Rule set

Peppol BIS 3.0

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-R005?

PEPPOL-EN16931-R005 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the @schemeID element under Party > EndpointID 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:AccountingCustomerParty/cac:Party/cbc:EndpointID/@schemeID

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Redundant same-currency declaration violates the specification.

PEPPOL-EN16931-R005 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-R005
·Specification: Peppol BIS 3.0

Before / After

Failing XML

<Invoice>
  <!-- Issue: VAT accounting currency code MUST be different from invoice  -->
</Invoice>

Corrected XML

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

Technical Reference

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

SpecPeppol BIS 3.0

Operationderive

StrategyDerive schemeID from country code or endpoint pattern

Common Causes

·VAT accounting currency set to same value as invoice currency
·Field populated by default with same currency
·Copy from multi-currency invoice without updating
·ERP always exports both currencies even when same
·Misunderstanding of when VAT accounting currency is needed

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

Handle PEPPOL-EN16931-R005 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-R005:VAT accounting currency code MUST be different from invoice currency code...