errorbusinessPeppol BIS 3.0

PEPPOL-EN16931-R002:No more than one note is allowed on document level, unless both parties are...

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

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

Target path: /Invoice/cbc:Note

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

Peppol access points reject invoices with more than one document-level note (unless both parties are German). Your invoice cannot be delivered until the notes are consolidated.

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 →

Frequently Asked Questions

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.

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.

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

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.

Related Content

Last updated: 27 February 2026

Share this guide:

Validate your invoice

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

Auto-fix PEPPOL-EN16931-R002 in seconds

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