How do I fix PEPPOL-EN16931-R003?

This requires user input to resolve. Review the relevant cbc: and cac: elements in your Invoice XML and provide the correct value. (PEPPOL-EN16931-R003). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is PEPPOL-EN16931-R003 a critical error?

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

Can PEPPOL-EN16931-R003 be automatically fixed?

Many instances of PEPPOL-EN16931-R003 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorEN 16931

`PEPPOL-EN16931-R003`:Buyer reference or order reference required

A buyer reference (BT-10) or purchase order reference (BT-13) MUST be provided in Peppol invoices.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

INPUT REQUIRED

Confidence

85%

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Buyer Reference / PO Number

What is PEPPOL-EN16931-R003?

PEPPOL-EN16931-R003 is a fatal validation rule defined in the EN 16931 specification. It validates the BuyerReference 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:BuyerReference

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Buyer needs reference information to process and approve the invoice.

PEPPOL-EN16931-R003 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.

Validator Behavior

·Causes invoice rejection
·Error returned: PEPPOL-EN16931-R003
·Specification: EN 16931

How to Fix It

Before / After

Failing XML

<Invoice>
  <!-- Issue: A buyer reference or purchase order reference MUST be provid -->
</Invoice>

Corrected XML

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

Technical Reference

XPath/Invoice/cbc:BuyerReference

SpecEN 16931

Operationset_default

StrategyDerive from OrderReference if available, otherwise prompt user for buyer reference or PO number

Common Causes

·Neither buyer reference nor PO number provided
·Buyer did not supply reference when ordering
·ERP does not capture buyer references
·Free-form sale without PO
·Reference fields not mapped in export

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

Handle PEPPOL-EN16931-R003 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-R003:Buyer reference or order reference required