COMPLIANCE_SYSTEM_NOT_AVAILABLE
The system ‹value› cannot be activated in this environment.
Category: VeriFactu and SII
Example response
When this error occurs, the API returns a JSON response with the following shape:
{
"type": "https://docs.beel.es/errors/COMPLIANCE_SYSTEM_NOT_AVAILABLE",
"title": "COMPLIANCE_SYSTEM_NOT_AVAILABLE",
"detail": "The system ‹value› cannot be activated in this environment.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "COMPLIANCE_SYSTEM_NOT_AVAILABLE",
"message": "The system ‹value› cannot be activated in this environment.",
"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
COMPLIANCE_EFFECTIVE_DATE_IN_PAST
The date cannot be earlier than today. Use today or a later date.
COMPLIANCE_REQUIRED_IN_SANDBOX
In Sandbox the company always reports through VeriFactu or the SII. Activate the other system instead of deactivating this one.
COMPLIANCE_SYSTEMS_INCOMPATIBLE
The other system (VeriFactu or the SII) cannot be ended on that date. Deactivate it first and try again.
SII_ACKNOWLEDGEMENT_REQUIRED
To report through the SII, confirm that you are responsible for it.
SII_CHANGE_ONLY_FROM_TOMORROW
Entering or leaving the SII can only take effect from tomorrow. Use tomorrow or a later date.