# A unit price with more than 4 decimals is rejected, not rounded

A `unit_price` with more than 4 significant decimals now answers `422 LINE_UNIT_PRICE_TOO_MANY_DECIMALS` instead of being rounded silently. Round to 4 decimals, or send the line total.

Oct 2, 2026 · Breaking

The contract has always said `unit_price` supports up to 4 decimal places, but a price with more was rounded silently to 4: `1000 × 0.12345` was invoiced at `0.1235` with a base of `123.50`, and `0.00001` was stored as `0`. The invoice then said something different from what you sent.

Now that line answers `422 LINE_UNIT_PRICE_TOO_MANY_DECIMALS` and the invoice is not created or changed. Trailing zeros do not count: `10.500000` is still `10.5`.

## What else changed

- **Applies wherever you send a `unit_price`:** creating and editing invoices, corrective invoices, and recurring invoice templates.
- **Who is affected:** integrations that send prices with 5 or more significant decimals, typically computed by division (`total / quantity`) without rounding.
- **What to do:** round the price to 4 decimals before sending it. If what you know is the line total, send it in `total_excluding_tax` or `total_including_tax` and the unit price is derived from it.

## Where to go next

- [LINE_UNIT_PRICE_TOO_MANY_DECIMALS](/errors/LINE_UNIT_PRICE_TOO_MANY_DECIMALS)
- [Create an invoice](/invoices/createCompanyInvoice)

---

Full OpenAPI spec: https://docs.beel.es/api/openapi