What is the rounding tolerance for R048?

The Schematron uses ±0.01 against a value rounded to two decimal places. Differences greater than one cent fail; differences within one cent pass.

Why does my calculation come out a cent off?

Almost always because rounding happens at the wrong step. EN 16931 expects round-after-multiply. Computing the unit price by dividing line subtotal by quantity at high precision and then rounding does not produce the same result.

How does the price base quantity (BT-149) affect this rule?

When BT-149 is present and not 1, the line net is BT-129 * BT-146 / BT-149 (plus charges, minus allowances). A typical case is a price quoted per 100kg with a quantity of 1.5 — the base must be honoured or the calculation diverges by orders of magnitude.

Is this rule auto-fixable?

Yes — the recomputed value is deterministic from the line components. Invoice Navigator applies the recomputation and records both before and after values in the evidence pack so the original seller intent is auditable.

Does R048 apply to credit notes?

Yes — the equivalent rule on Peppol BIS credit notes (PEPPOL-EN16931-R048 with the credit note context) applies the same calculation to cac:CreditNoteLine.

Error codes · EN 16931

PEPPOL-EN16931-R048Fixable here

Invoice line net amount must equal price * quantity ± allowances/charges

This is the rejection, word for word: „[PEPPOL-EN16931-R048] PEPPOL-EN16931-R048 is a Schematron calculation rule on the Peppol BIS Billing 3.0 invoice. For each cac:InvoiceLine the rule requires: BT-131 (Invoice line net amount) = (BT-129 Invoiced quantity * BT-146 Item net price / BT-149 Item price base quantity) + sum of BT-141 line-level charges − sum of BT-136 line-level allowances. When the calculated value differs from the value the seller emitted by more than the rounding tolerance, the line is rejected.“

What to have readyThe missing value from your purchase order, contract or bookkeeping.

What we doRecompute BT-131 in the canonical order: gross = round_half_up(qty * price / coalesce(base, 1), 2); net = gross + charges − allowances. Auto-fixed when components are deterministic; downgraded to input when the price base is missing or ambiguous.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="H87">3</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="EUR">29.99</cbc:LineExtensionAmount>
  <cac:Price>
    <cbc:PriceAmount currencyID="EUR">10.00</cbc:PriceAmount>
  </cac:Price>
</cac:InvoiceLine>

After

<cac:InvoiceLine>
  <cbc:ID>1</cbc:ID>
  <cbc:InvoicedQuantity unitCode="H87">3</cbc:InvoicedQuantity>
  <cbc:LineExtensionAmount currencyID="EUR">30.00</cbc:LineExtensionAmount>
  <cac:Price>
    <cbc:PriceAmount currencyID="EUR">10.00</cbc:PriceAmount>
  </cac:Price>
</cac:InvoiceLine>

What the finding looks likeExample

FindingValue missing · PEPPOL-EN16931-R048

From youThe missing value

ThenPassed

ProofSHA-256 and /verify link after the check