Back to the error catalogue
PEPPOL-EN16931-R121BT-149
input

The item price base quantity is not strictly positive

`Item price base quantity` (BT-149) must be a number strictly greater than zero.

Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.

The message your validator prints

Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.

Base quantity MUST be a positive number above zero.

Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.

Common searches around this code

These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.

PEPPOL-EN16931-R121 The item price base quantity is not strictly positivePEPPOL-EN16931-R121 XRechnung Schematron package (KoSIT)PEPPOL-EN16931-R121 BT-149Base quantity MUST be a positive number above zero.PEPPOL-EN16931-R121 correction

Test your file with this error in mind

Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.

To automate this check in an ERP flow, call the validation API and link every returned code to its public page.

Why this error happens

The base quantity is the divisor in the line calculation: at zero the net amount is not merely wrong, it does not exist. The value usually comes from a field left at its default rather than from data entry.

How to fix it

Fill in the real base quantity — most often 1. Factlint does not replace it: it governs the unit price, and giving it a value would change the line amount.

XML correction example

BEFORE (invalid)
<ram:BasisQuantity unitCode="C62">0</ram:BasisQuantity>
AFTER (compliant)
<ram:BasisQuantity unitCode="C62">1</ram:BasisQuantity>