How do I fix PEPPOL-EN16931-R002?

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

Is PEPPOL-EN16931-R002 a critical error?

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

Can PEPPOL-EN16931-R002 be automatically fixed?

Many instances of PEPPOL-EN16931-R002 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-R002`:No more than one note is allowed on document level, unless both parties are...

Your invoice has multiple document-level notes, but Peppol only allows one. The exception is when both the seller and buyer are German organisations — in that case, multiple notes are permitted.

Severity

Fatal

Rule set

Peppol BIS 3.0

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Merge multiple document-level notes into a single note, separated by line breaks. German-to-German invoices are exempt.

Confidence: 90% · Applied automatically in pipeline

What is PEPPOL-EN16931-R002?

PEPPOL-EN16931-R002 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the Note 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: /Invoice/cbc:Note

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation unless both parties are German. Non-German invoices must consolidate to single note.

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

How to Fix It

Before / After

Failing XML

<Invoice>
  <!-- Issue: No more than one note is allowed on document level, unless b -->
</Invoice>

Corrected XML

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

Technical Reference

XPath/Invoice/cbc:Note

SpecPeppol BIS 3.0

Operationnormalize

StrategyMerge multiple document-level notes into a single note, separated by line breaks. German-to-German invoices are exempt.

Common Causes

·Multiple notes added to invoice header
·ERP system exports multiple note fields
·Terms and conditions split into multiple notes
·Copy from template with multiple default notes
·Manual addition of extra notes

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

Handle PEPPOL-EN16931-R002 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-R002:No more than one note is allowed on document level, unless both parties are...