Official rule text
[PEPPOL-EN16931-R130] Unit code of price base quantity MUST be same as invoiced quantity.
Why this error occurs
The element is mandatory in this standard but is missing or empty in your file. Typical causes: the field is not filled in the invoicing software, the ERP export does not map it, or the element is present but contains only whitespace.
How to fix it
Add the element with a non-empty value at the position given by the context above. Check the master data (seller, buyer, payment) in your invoicing software; most tools expose the field under the business term name shown here. Re-validate after the change.
What the validator checks
Checked element (context):
UBL
cac:Price/cbc:BaseQuantity[@unitCode]Test (XPath):
not($hasQuantity) or @unitCode = $quantity/@unitCodeCII
ram:NetPriceProductTradePrice/ram:BasisQuantity[@unitCode] | ram:GrossPriceProductTradePrice/ram:BasisQuantity[@unitCode]Test (XPath):
@unitCode = ../../../ram:SpecifiedLineTradeDelivery/ram:BilledQuantity/@unitCodeCheck your invoice
Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
PEPPOL-EN16931-R001Business process identifier (BT-23) is missingPEPPOL-EN16931-R002No more than one note is allowed on document level, unless both the buyer and seller…PEPPOL-EN16931-R003Neither buyer reference nor purchase order reference givenPEPPOL-EN16931-R004Specification identifier is not the Peppol BIS Billing 3.0 identifierPEPPOL-EN16931-R005VAT accounting currency equals the invoice currencyPEPPOL-EN16931-R006Only one invoiced object is allowed on document levelPEPPOL-EN16931-R007Business process identifier has the wrong formatPEPPOL-EN16931-R008Document contains empty elements
Frequently asked questions
What does PEPPOL-EN16931-R130 mean?
PEPPOL-EN16931-R130 is a peppol bis billing 3.0 rule: Unit code of price base quantity MUST be same as invoiced quantity.
Will my invoice be rejected because of PEPPOL-EN16931-R130?
Yes. PEPPOL-EN16931-R130 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.
Which formats does PEPPOL-EN16931-R130 apply to?
Invoices and credit notes sent over the Peppol network (UBL) and, because XRechnung embeds the Peppol rule set, every XRechnung as well. Syntax: UBL and CII.
Source: Peppol BIS Billing 3.0.20 (November 2025). Catalogue generated from the official schematron on 2026-10-14.