How do I fix PEPPOL-EN16931-R043?

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

Is PEPPOL-EN16931-R043 a critical error?

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

Can PEPPOL-EN16931-R043 be automatically fixed?

Many instances of PEPPOL-EN16931-R043 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-R043`:Allowance/charge ChargeIndicator value MUST equal "true" or "false"

The ChargeIndicator on one of your discounts or surcharges is not in the correct format. It must be exactly "true" (for a surcharge) or "false" (for a discount), in lowercase.

Severity

Fatal

Rule set

Peppol BIS 3.0

Country

All EU

Fix type

AUTO-FIX

Confidence

95%

Engine Classification

Normalise ChargeIndicator boolean values to lowercase "true" or "false"

Confidence: 95% · Applied automatically in pipeline

What is PEPPOL-EN16931-R043?

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

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Invalid ChargeIndicator prevents proper interpretation of allowances and charges.

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

How to Fix It

Before / After

Failing XML

<Invoice>
  <!-- Issue: Allowance/charge ChargeIndicator value MUST equal "true" or  -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cbc:ChargeIndicator

SpecPeppol BIS 3.0

Operationnormalize

StrategyNormalise ChargeIndicator boolean values to lowercase "true" or "false"

Common Causes

·ChargeIndicator has invalid value (not true/false)
·Numeric value used instead of boolean string
·Case sensitivity issue (TRUE vs true)
·Empty or null ChargeIndicator
·ERP exports 1/0 instead of true/false

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

Handle PEPPOL-EN16931-R043 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-R043:Allowance/charge ChargeIndicator value MUST equal "true" or "false"