How do I fix PEPPOL-EN16931-R044?

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

Is PEPPOL-EN16931-R044 a critical error?

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

Can PEPPOL-EN16931-R044 be automatically fixed?

Many instances of PEPPOL-EN16931-R044 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-R044`:Charge on price level is NOT allowed. Only value 'false' allowed.

Price level allowances/charges must be allowances only (ChargeIndicator = false). Surcharges at the item price level are not allowed in PEPPOL - they must be at line or document level.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Remove charges from price level (only allowances permitted)

Confidence: 90% · Applied automatically in pipeline

What is PEPPOL-EN16931-R044?

PEPPOL-EN16931-R044 is a fatal validation rule defined in the EN 16931 specification. It validates the AllowanceCharge element under Price 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:InvoiceLine/cac:Price/cac:AllowanceCharge[cbc:ChargeIndicator='true']

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. PEPPOL only allows discounts (not surcharges) at the price level.

PEPPOL-EN16931-R044 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
·Error returned: PEPPOL-EN16931-R044
·Specification: EN 16931

Before / After

Failing XML

<Invoice>
  <!-- Issue: Charge on price level is NOT allowed. Only ChargeIndicator f -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cac:InvoiceLine/cac:Price/cac:AllowanceCharge[cbc:ChargeIndicator='true']

SpecEN 16931

Operationremove

StrategyRemove charges from price level (only allowances permitted)

Common Causes

·Charge applied at price level instead of line level
·ERP models surcharges as price adjustments
·ChargeIndicator incorrectly set to true for price allowance
·Confusion between price, line, and document level charges
·Template or mapping error

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

Handle PEPPOL-EN16931-R044 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-R044:Charge on price level is NOT allowed. Only value 'false' allowed.