REGIME_KEY_NOT_SUPPORTED
Regime key ‹value› is not available. Keys 06 and 14 require data the invoice does not carry (06, the cost-based taxable base; 14, an operation date after the issue date and a public-administration recipient). Key 03 requires the invoice not to show the tax separately (RD 1619/2012, art. 16.2.c), and the invoice always does. Use the key that fits the operation
Category: Invoices
| HTTP status | 422 Unprocessable Content |
| Retry | After fixing the cause |
When it happens
A line, or the default of the tax configuration, carries regime_key 03, 06 or 14. Under 03 the invoice must not show the tax separately, and a BeeL. invoice always does; with 06 and 14 AEAT requires data the invoice does not carry.
How to fix it
Use another regime key. A corrective invoice of an original that already carried one of these keys keeps it.
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}/invoicesPATCH /v1/companies/{company_id}/invoices/{invoice_id}POST /v1/companies/{company_id}/invoices/{invoice_id}/issuePUT /v1/companies/{company_id}/tax-configuration
Rules that cite this code
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/REGIME_KEY_NOT_SUPPORTED",
"title": "REGIME_KEY_NOT_SUPPORTED",
"detail": "Regime key ‹value› is not available. Keys 06 and 14 require data the invoice does not carry (06, the cost-based taxable base; 14, an operation date after the issue date and a public-administration recipient). Key 03 requires the invoice not to show the tax separately (RD 1619/2012, art. 16.2.c), and the invoice always does. Use the key that fits the operation",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "REGIME_KEY_NOT_SUPPORTED",
"message": "Regime key ‹value› is not available. Keys 06 and 14 require data the invoice does not carry (06, the cost-based taxable base; 14, an operation date after the issue date and a public-administration recipient). Key 03 requires the invoice not to show the tax separately (RD 1619/2012, art. 16.2.c), and the invoice always does. Use the key that fits the operation",
"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
ATTACH_SOURCE_INVOICE_UNAVAILABLE
A source invoice is not available (it does not exist or you no longer have access); uncheck the source invoices attachment to send without the folder
ATTACH_SOURCE_INVOICES_NO_SOURCES
The invoice has no consolidation disbursements: there are no source invoices to attach
ATTACH_SOURCE_INVOICES_REQUIRES_PDF
Attaching the source invoices also requires attaching the invoice PDF
ATTACH_SOURCE_PDF_MISSING
These source invoices have no generated PDF: ‹value›
ATTACH_SOURCE_ZIP_TOO_LARGE
The source invoices ZIP (‹value› MB) exceeds the maximum sendable size (‹value› MB)
Keep exploring
REGIME_KEY_CLASSIFICATION_NOT_ACCEPTED
Regime key ‹value› does not accept a line with exemption_reason ‹value›: with that key AEAT only accepts exemption_reason ‹value›
REGIME_KEY_REQUIRES_RECIPIENT_NIF
With regime key ‹value› the recipient must be identified by NIF: AEAT does not accept an alternative identifier