How do I fix PEPPOL-EN16931-R130?

Invoice Navigator automatically fixes this issue by correcting the `cbc:InvoicedQuantity` element in your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is PEPPOL-EN16931-R130 a critical error?

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

Can PEPPOL-EN16931-R130 be automatically fixed?

Many instances of PEPPOL-EN16931-R130 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-R130`:Unit code of price base quantity MUST be same as invoiced quantity.

The unit code of the price base quantity must match the unit code of the invoiced quantity. You cannot have different units between quantity and base quantity.

Severity

Fatal

Rule set

Peppol BIS 3.0

Country

All EU

Fix type

AUTO-FIX

Confidence

85%

Engine Classification

Ensure payable amount is non-negative

Confidence: 85% · Applied automatically in pipeline

What is PEPPOL-EN16931-R130?

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

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Mismatched units prevent proper price calculation.

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

Before / After

Failing XML

<cac:InvoiceLine>
  <cbc:InvoicedQuantity>-100.00</cbc:InvoicedQuantity>
</cac:InvoiceLine>

Corrected XML

<cac:InvoiceLine>
  <cbc:InvoicedQuantity>100.00</cbc:InvoicedQuantity>
</cac:InvoiceLine>

Technical Reference

XPath//cac:LegalMonetaryTotal/cbc:PayableAmount

SpecPeppol BIS 3.0

Operationnormalize

StrategyEnsure payable amount is non-negative

Common Causes

·Different unit codes used for quantity and base quantity
·Base quantity unit not updated when quantity unit changed
·Template has mismatched default units
·ERP exports different units for these fields
·Manual entry inconsistency

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

Handle PEPPOL-EN16931-R130 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-R130:Unit code of price base quantity MUST be same as invoiced quantity.