INVOICE_TAX_RATE_TOO_MANY_DECIMALS

When it happens

On an invoice recorded with VeriFactu, a tax or surcharge rate has more than two decimals, and AEAT only accepts two. The invoice was not issued and no number was used.

How to fix it

Use a rate with two decimals at most and issue it again.

Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.

Returned by

The operations where this code is most likely. The list is not exhaustive.

• POST /v1/companies/{company_id}/invoices
• PATCH /v1/companies/{company_id}/invoices/{invoice_id}
• POST /v1/companies/{company_id}/invoices/{invoice_id}/issue

Rules that cite this code

• REC-013 An invoice AEAT would reject is not numbered

Example response

When this error occurs, the API answers 422 Unprocessable Content with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/INVOICE_TAX_RATE_TOO_MANY_DECIMALS",
  "title": "INVOICE_TAX_RATE_TOO_MANY_DECIMALS",
  "detail": "The rate ‹value› % has more than two decimals and the AEAT accepts only two. The invoice was not issued and the number was not used: use a rate with at most two decimals.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "INVOICE_TAX_RATE_TOO_MANY_DECIMALS",
    "message": "The rate ‹value› % has more than two decimals and the AEAT accepts only two. The invoice was not issued and the number was not used: use a rate with at most two decimals.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Placeholders like ‹value› are filled in at runtime with the actual values of your request.

Other errors in this category

Keep exploring