コンテンツへスキップ
ブログに戻る
Explainer公開日 2026年7月5日7 分で読めます

Why e-invoices get rejected over a fraction of a cent

An e-invoice can look perfect and still fail validation. The usual culprit is rounding: how floating-point money maths and EN 16931 rules like BR-CO-15 reject invoices — and how to prevent it.

You send an invoice. It looks perfect — the numbers on screen all add up. Hours later the network or the tax authority bounces it with a cryptic rule code and no explanation. Nine times out of ten, the cause is not a big mistake. It is a fraction of a cent.

Computers cannot add money exactly

Open any programming language and type 0.1 + 0.2. You do not get 0.3 — you get 0.30000000000000004. It is called floating-point arithmetic, and for most software it is harmless. On an invoice it is not: that microscopic error compounds across lines and VAT, and it lands in a decimal you never see on the printout.

The rule that catches it: BR-CO-15 (and friends)

EN 16931 — the European standard behind Peppol BIS, XRechnung, Factur-X and the national formats — enforces a set of arithmetic rules that must reconcile to the cent. The ones that reject real invoices most often:

  • BR-CO-15 — the invoice total with VAT must equal the total without VAT plus the total VAT amount. Off by one cent and the document fails.
  • BR-S-08 (and the other category rules) — for each VAT category, the taxable base must equal the sum of the relevant line net amounts.
  • Per-category VAT — the VAT amount for a category must equal its taxable base × the rate, rounded to two decimals. Compute VAT per line and sum it, and you can land a cent away from the rule’s expectation.

Every visible number can look right and the invoice still fails, because the failure is in the reconciliation, not the presentation.

Why “looks fine” is not “valid”

There are two layers of checking. XSD confirms the file is well-formed XML — elements in the right place, dates that are dates. Schematron checks the business rules — the arithmetic above, mandatory fields, code lists. A file can pass the first and fail the second. That is exactly the invoice that “looks fine” and still gets rejected.

How to prevent it

  • Never do money maths with ordinary floating-point numbers — use an exact decimal type.
  • Round consistently: half-up, to two decimals, at defined points — not wherever the language happens to.
  • Recompute the totals from the line items. Do not trust the totals in the incoming file; a supplier’s rounding quirk becomes your rejection.
  • Group VAT per category and rate, then round once per group — not per line.

Validate before you send

Catch the cent in your own pipeline, not in a rejection notice. Run the document through the official XSD and Schematron rules the moment it is generated — before it reaches an Access Point or a tax authority. Our free, open-source peppol-validator npm package runs those checks in Node, no Java required, so a failed rule is a code fix, not a lost day.

How MyInvoice handles it

MyInvoice runs every amount through exact decimal arithmetic, groups VAT per category and rate, and always recomputes the totals from the lines — never trusting the input. Then it validates the result against the destination’s own rules before you get it back. It is a boring set of decisions, made early. It is also why 53,000 automated checks stay green and invoices pass on the first try.

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=peppol-bis-3"
Convert one of your invoices in the browserRead the API docs