> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

## Introduction

This document describes the shape of Chift errors and lists the errors you can expect from our different APIs.

### Chift error

A Chift error is always composed of the following elements:

* status: "error"
* message: "message explaining the error"
* error\_code: "unique error code to describe the error"
* detail: "additional details explaining the error" (optional)

Chift always returns errors with an HTTP error code (4XX, 5XX). Note that the combination of the message and the error\_code is not always unique.

Example of an error message:

```json theme={null}
{
    "message": "The resource GET - /order is not supported by Cashpad",
    "status": "error",
    "error_code": "ERROR_RESOURCE_NOT_SUPPORTED"
}
```

### Specific errors

Chift uses generic errors whenever possible. Some errors are nevertheless specific to a connector. The related connector documentation describes those errors.

### List of errors

| Error code | HTTP status | Error description | Used by APIs | Resolution |
| - | - | - | - | - |
| ERROR\_CHIFT\_AUTHENTICATION\_ERROR | 401 | Error with the provided Chift token or combination of clientId, clientSecret and accountId | All | |
| ERROR\_CONNECTOR\_AUTHENTICATION | 401 | Error related to the authentication to the connector (wrong credentials, ...) | All | Check the credentials used in the connector configuration. If they are wrong or have expired, [update the existing connection](/developer-guides/core-concepts/monitor-connections#update-an-existing-connection) so the end user can enter them again, instead of deleting and recreating it. |
| ERROR\_CONNECTOR\_CONFIGURATION | 400 | Error related to the configuration of the connector not related to Chift (e.g. no license, connector not active, needs to be restarted, ...) | All | |
| ERROR\_CONFIGURATION\_SYNC | 400 | Error in the configuration of the sync | All | The sync is not correctly configured for that consumer. Make sure that it was correctly configured and activated. |
| ERROR\_NO\_ACTIVE\_CONNECTION | 400 | No active connection/integration for this API are configured | All | |
| ERROR\_CONFIGURATION\_CONNECTION | 400 | Error related to the configuration of the connection (e.g. more than one connection is active, ...) | All | |
| ERROR\_DATA\_VALIDATION | 400 | Impossible to retrieve data due to a data validation issue. Contact support for more details | All | |
| ERROR\_API\_RESOURCE\_NOT\_FOUND | 400 | The route that was called does not exist. Make sure that you use the routes as specified in the documentation. | All | |
| ERROR\_WEBHOOK\_NOT\_SUPPORTED | 405 | This webhook type is not supported for this integration | All | |
| ERROR\_UNKNOWN | 400 | An unknown error occurred during the call. Please contact Chift team. | All | |
| ERROR\_INVALID\_BODY | 422 | One of the input fields of the body is invalid | All | |
| ERROR\_INVALID\_QUERY\_PARAMETER | 422 | One of the query parameters is invalid | All | |
| ERROR\_INVALID\_PATH\_PARAMETER | 422 | One of the path parameters is invalid | All | |
| ERROR\_INVALID\_RESPONSE | 422 | The response could not be built. Our support should be contacted. | All | |
| ERROR\_RESOURCE\_NOT\_SUPPORTED | 405 | The requested resource is not supported by this connector. | All | |
| ERROR\_TECHNICAL\_MAPPING | 400 | There is a technical error while processing the request. We are already alerted and working on this. Please contact support if needed. | All | There is a technical error. Please contact support if needed. |
| ERROR\_INTEGRATION\_INVALID | 400 | The specified integration is invalid or could not be found | Connections | |
| ERROR\_CONNECTION\_INFO\_EMPTY | 400 | A field in the connection is not filled in. | All | |
| ERROR\_ORDER\_NOT\_FOUND | 404 | The given order could not be retrieved | POS | |
| ERROR\_CUSTOMER\_NOT\_FOUND | 404 | The given customer could not be retrieved | POS | |
| ERROR\_LOCATION\_NOT\_FOUND | 404 | The given location could not be found | POS | |
| ERROR\_CONFIGURATION\_LOCALAGENT | 502 | Impossible to connect to the specified local agent (e.g. not configured, ...) | All | Check the [local agent status](/platform/advanced/local-agent#monitoring-a-local-agent) on the consumer's page. If it is red, install the local agent on the server. If it is orange, start the Windows service on the server. Then retry. See the connector's documentation for connector-specific installation steps. |
| ERROR\_CONNECTOR\_MAINTENANCE | 503 | Impossible to connect to the target application | All | The target application is temporarily unable to handle a request. Please retry later. |
| ERROR\_GATEWAY\_TIMEOUT | 504 | Impossible to connect to a remote application (for local agent) | All | Check that the [local agent](/platform/advanced/local-agent#monitoring-a-local-agent) is online (green) on the consumer's page and that the server running it is switched on. Then retry. |
| ERROR\_BACKEND\_FORBIDDEN | 403 | Impossible to retrieve data due to a permission issue | All | Please authorize the access to the connector again |
| REQUEST\_ALREADY\_PROCESSED | 409 | Request with same client request id was already successfully processed | All | |
| REQUEST\_IN\_PROCESS | 409 | Request with same client request id is currently processed | All | |
| ERROR\_RATE\_LIMIT | 429 | The rate limit has been reached for this connector. Please try again later. | All | |
| ERROR\_BACKEND\_NOT\_FOUND | 504 | Impossible to connect to the specified backend (url, host, unique identifier,... might be incorrect or the backend is down) | All | Check the values entered in the connection (URL, host, unique identifier). If one is wrong, [update the existing connection](/developer-guides/core-concepts/monitor-connections#update-an-existing-connection). If the values are correct, the target application may be unavailable. Retry later. |
| ERROR\_BACKEND\_FORBIDDEN | 403 | Impossible to retrieve data due to a permission issue | All | |
| ERROR\_UNEXPECTED | 400 | Unexpected error while trying to perform the request. This is often linked to some data being incorrectly managed. We are notified and are working proactively on those errors. | All | Check the detail of the error and the data sent or synchronized for the affected record, then retry. If the error persists, [contact Chift's support](/platform/support/contact-support) with the consumer ID. |
| ERROR\_INTERNAL\_ERROR | 400 | Internal server error. This is often linked to a technical error. We are notified and are working proactively on those errors. | All | |
| ERROR\_CONNECTOR\_MISSING\_EXTENSION | 400 | The connector requires an extension. | All | The connector is missing a required extension (please install or update) |
| ERROR\_INVALID\_PERIOD | 400 | The given period is not valid (based on date\_from & date\_to parameters) | POS | |
| ERROR\_INVALID\_HOST | 400 | The given host is not valid and the backend cannot be reached | POS | |
| ERROR\_FOLDER\_NOT\_FOUND | 404 | Folder not found | Accounting | The requested folder was not selected during the connection process or does not exist in the accounting system |
| ERROR\_INVALID\_VAT\_FORMAT | 422 | The VAT number doesn't seem to be correct. Please remove dots and whitespaces. The expected format is the following: BE0784930037 | Accounting | |
| ERROR\_INVALID\_LANGUAGE\_FORMAT | 422 | The language format is not correct. Please use the ISO 639-1 codes. | Accounting | |
| ERROR\_INVALID\_CURRENCY\_FORMAT | 422 | The currency format is not correct. Please use the ISO 4217 codes. | Accounting | |
| ERROR\_INVALID\_COUNTRY\_FORMAT | 422 | The country format is not correct. Please use the ISO 3166-1 codes. | Accounting | |
| ERROR\_INVALID\_FINANCIAL\_PERIOD\_FORMAT | 422 | The forced financial period must be 6 numbers (e.g. 02 for February and 2022 => 022022). | Accounting | |
| ERROR\_BOOKS\_FROZEN | 422 | The books are frozen in the accounting tool. | Accounting | Unfreeze the books in the accounting tool, or use an entry date after the freeze date. |
| ERROR\_NO\_INVOICE\_LINE | 400 | The invoice must contain at least one invoice line. | Accounting | |
| ERROR\_ZERO\_INVOICE | 400 | You cannot create an invoice with an untaxed amount of 0. | Accounting | |
| ERROR\_ZERO\_LINE | 400 | You cannot create entries/invoices with a line equal to zero. | Accounting | |
| ERROR\_NO\_OPERATION\_LINE | 400 | The miscellaneous operation must contain at least one line. | Accounting | |
| ERROR\_INVALID\_OPERATION\_LINE\_TYPE | 400 | A line of type 'customer\_account' or 'supplier\_account' must have a 'partner\_id' filled in. | Accounting | |
| ERROR\_OPERATION\_NOT\_BALANCED | 400 | The operation is not balanced. The sum of the lines must be zero. | Accounting | |
| ERROR\_NOT\_ENOUGH\_MATCHING\_ENTRIES | 400 | Matching is only possible with at least 2 entries. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNTING\_NOT\_ACTIVE | 405 | Analytic accounting is not active on this connection. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNTING\_PLAN\_NOT\_CONFIGURED | 405 | A default analytic plan must be configured to use this endpoint. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_ALREADY\_EXISTS | 400 | An analytic account already exists with the same code in the accounting system. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_NOT\_FOUND | 404 | The analytic account doesn't exist in the accounting system. | Accounting | |
| ERROR\_ANALYTIC\_PLAN\_NOT\_FOUND | 404 | The analytic plan doesn't exist in the accounting system. | Accounting | |
| ERROR\_INVALID\_ANALYTIC\_DISTRIBUTION | 400 | There is an error with the analytic distribution. This error can come from an analytic plan or account being more than once in the analytic distribution; from a percentage not being between 1 and 100 or from an analytic plan not having a 100% coverage. | Accounting | |
| ERROR\_INVALID\_ANALYTIC\_DISTRIBUTION\_ACCOUNTS | 400 | Each analytic plan in the analytic distribution of an invoice line must contain at least one analytic account. | Accounting | |
| ERROR\_INVALID\_ANALYTIC\_DISTRIBUTION\_ACCOUNTS\_PERCENTAGE | 400 | Analytic accounts of each analytic plan in the analytic distribution of an invoice line must cover 100% of the amount of the invoice line. | Accounting | |
| ERROR\_INVOICE\_AMOUNTS\_DO\_NOT\_MATCH | 400 | The amounts of the invoice are not correct. | Accounting | |
| ERROR\_LINE\_AMOUNTS\_DO\_NOT\_MATCH | 400 | The amounts in one invoice line are not correct. | Accounting | Please make sure that tax amount and tax rate are correct. If no issue is detected, please contact Chift. |
| ERROR\_TAX\_RATE\_NOT\_CORRESPONDING | 400 | The tax rate doesn't match the tax rate linked to the tax code in the accounting system. | Accounting | Please modify the mapping of that tax rate with a vat code of the same rate |
| ERROR\_MULTIPLE\_GL\_ACCOUNTS | 400 | The entries have different receivable/payable accounts. | Accounting | |
| ERROR\_MULTIPLE\_PARTNER\_ACCOUNTS | 400 | A sale/purchase entry cannot be linked to multiple partner accounts. | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_NOT\_CONFIGURED | 400 | The account number is not configured to be used in entries. It cannot be imputed. | Accounting | |
| ERROR\_ENTRY\_HAS\_INVALID\_STATUS | 400 | The entry doesn't have the correct status to be matched. | Accounting | |
| ERROR\_ENTRY\_HAS\_NO\_ACCOUNT\_RECEIVABLE\_PAYABLE | 400 | The entry doesn't have a receivable/payable account. | Accounting | |
| ERROR\_ENTRY\_NOT\_LINKED\_TO\_PARTNER | 400 | The entry is not linked to the partner mentioned in the matching body. | Accounting | |
| ERROR\_ENTRY\_ALREADY\_RECONCILED | 400 | The entry is already reconciled in the accounting system. | Accounting | |
| ERROR\_ENTRY\_ALREADY\_PARTIALLY\_MATCHED | 400 | An entry is already partially matched with another entry in the accounting system. | Accounting | |
| ERROR\_JOURNAL\_NOT\_GOOD\_SCOPE | 400 | The journal cannot be used for this scope. | Accounting | The provided journal is not valid for the scope of the invoice. Please adapt it in your input or in your mapping (if using a sync) |
| ERROR\_JOURNAL\_NOT\_CONFIGURED | 400 | The journal is not configured for a used functionality. | Accounting | |
| ERROR\_TAX\_CODE\_NOT\_GOOD\_SCOPE | 400 | The tax code cannot be used for this type of invoices. | Accounting | Please adapt the tax code or update the mapping (if using a sync) |
| ERROR\_MULTIPLE\_JOURNALS | 404 | Multiple journals were found. Please indicate the wanted journal in the request. | Accounting | |
| ERROR\_JOURNAL\_NOT\_FOUND\_FOR\_SCOPE | 404 | Please indicate the wanted journal in the request. No journal has been found for this scope. | Accounting | |
| ERROR\_INVOICE\_NUMBER\_ALREADY\_USED | 409 | The invoice number is already used in the accounting system. | Accounting | |
| ERROR\_INVOICE\_ALREADY\_EXISTS | 409 | The invoice already exists in the accounting system. | Accounting | |
| ERROR\_ENTRY\_NUMBER\_ALREADY\_USED | 409 | The entry number is already used in the accounting system. | Accounting | |
| ERROR\_PDF\_NOT\_APPLICABLE\_TO\_DRAFT\_INVOICE | 400 | You cannot upload a PDF when creating a draft invoice. | Accounting | |
| ERROR\_TAX\_CODE\_NOT\_FOUND | 404 | The tax code doesn't exist in the accounting system. | Accounting | Please set up the tax code in the accounting system or adapt the tax code in the mapping (if using a sync) |
| ERROR\_TAX\_CODE\_NOT\_CONFIGURED | 400 | The tax code is not configured to be used with this type of invoice. | Accounting | Please set up a payable account on the tax code in the accounting system |
| ERROR\_ACCOUNT\_NUMBER\_NOT\_FOUND | 404 | The account number doesn't exist in the accounting system. | Accounting | Please create the ledger account in the accounting system |
| ERROR\_OPERATION\_NOT\_FOUND | 404 | The operation doesn't exist in the accounting system. | Accounting | |
| ERROR\_OPERATION\_NUMBER\_ALREADY\_USED | 409 | The operation number is already used in the accounting system. | Accounting | |
| ERROR\_WRONG\_ACCOUNT\_TYPE | 400 | The account cannot be used for this type of line of a miscellaneous operation. | Accounting | |
| ERROR\_BOOKYEAR\_NOT\_FOUND | 400 | The accounting system is not set up for this date. | Accounting | Create a fiscal year in the accounting system including the date of the invoice or verify why the fiscal year is not set up |
| ERROR\_PERIOD\_CLOSED | 400 | The accounting period is closed in the accounting system. | Accounting | Reopen the accounting period in the accounting system, or use a date that falls within an open period. |
| ERROR\_JOURNAL\_LOCKED | 400 | The journal is locked in the accounting system. | Accounting | Please unlock the journal in the accounting system |
| ERROR\_INVALID\_FIELD\_FORMAT\_BANK\_ACCOUNT | 422 | The bank account/iban is not valid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ANALYTIC\_ACCOUNT | 422 | The code of the analytic account doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ANALYTIC\_PLAN | 422 | The format of the field 'analytic\_plan' doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_JOURNAL\_ID | 422 | The format of the field 'journal\_id' doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_TAX\_CODE | 422 | The format of the field 'tax\_code' doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ENTRIES | 422 | The format of the IDs entries doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_JOURNAL\_ALREADY\_OPEN | 400 | The entry couldn't be created in the accounting system. The journal is already open. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ID | 422 | The format of the ID doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_PARTNER\_ID | 422 | The format of the field 'partner\_id' doesn't seem to be correct for the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_COMPANY\_ID | 422 | The format of the field 'company\_id' doesn't seem to be correct for the corresponding accounting system. | Accounting | |
| ERROR\_MISSING\_FIRST\_NAME | 400 | The field 'first\_name' must be filled in when the client/supplier is an individual. | Accounting | |
| ERROR\_MISSING\_LAST\_NAME | 400 | The field 'last\_name' must be filled in when the client/supplier is an individual. | Accounting | |
| ERROR\_MISSING\_INVOICE\_NUMBER | 400 | The target connector is expecting an invoice number. | Accounting | The field invoice number cannot be empty |
| ERROR\_PARTNER\_ALREADY\_EXISTS | 400 | A client/supplier already exists with the same code/id in the accounting system. | Accounting | |
| ERROR\_JOURNAL\_NOT\_FOUND | 404 | The journal doesn't exist in the accounting system. | Accounting | |
| ERROR\_PARTNER\_NOT\_FOUND | 404 | The client/supplier doesn't exist in the accounting system. | Accounting | Make sure that the client/supplier is correctly created in the accounting system |
| ERROR\_ENTRY\_NOT\_FOUND | 404 | The entry doesn't exist in the accounting system. | Accounting | |
| ERROR\_DUPLICATE\_ENTRIES | 400 | Entries cannot contain duplicates. | Accounting | |
| ERROR\_INVOICE\_NOT\_FOUND | 404 | The invoice doesn't exist in the accounting system. | Accounting | |
| ERROR\_MISCELLANEOUS\_OPERATION\_NOT\_FOUND | 404 | The miscellaneous operation doesn't exist in the accounting system. | Accounting | |
| ERROR\_LANGUAGE\_NOT\_FOUND | 404 | The specified language doesn't exist or is not active in the accounting system. | Accounting | |
| ERROR\_CURRENCY\_NOT\_FOUND | 404 | The currency doesn't exist or is not active in the accounting system. | Accounting | |
| ERROR\_NEGATIVE\_INVOICE | 400 | An invoice must be positive. The invoice type determines the sign of the invoice. | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_NOT\_ACTIVE | 400 | An account number used in an invoice line is not active. | Accounting | Activate the ledger account in the accounting system |
| ERROR\_PARTNER\_NOT\_ACTIVE | 400 | The used client/supplier is not active. | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_NOT\_GOOD\_SCOPE | 400 | The account number cannot be used in this scope. | Accounting | |
| ERROR\_INVALID\_INVOICE\_DATE | 400 | The period containing the invoice date is already locked. | Accounting | |
| ERROR\_WRONG\_ENTRY\_TYPE | 400 | You can only create entries in a sale or purchase journal. | Accounting | |
| ERROR\_MAX\_DIFFERENCE\_MONTHS | 400 | You can retrieve maximum 3 months of data at once. The difference between 'date\_from' and 'date\_to' is at maximum 3 months. | Accounting | |
| ERROR\_ATTACHMENT\_ALREADY\_EXISTS | 400 | An attachment already exists for this invoice. | Accounting | |
| ERROR\_INVALID\_BASE64\_STRING | 400 | The document is not a valid base64 string representing a PDF. | Accounting | |
| ERROR\_INVALID\_DUE\_DATE | 422 | The due date must be after the invoice date. | Accounting | |
| ERROR\_CHARGE\_PRODUCT\_ACCOUNT\_MISSING | 422 | Please provide at least one charge/product account. | Accounting | |
| ERROR\_COLLECTIVE\_ACCOUNT\_MISSING | 422 | Please provide a client/supplier collective account. | Accounting | |
| ERROR\_PARTNER\_ACCOUNT\_MISSING | 422 | Please provide a client/supplier account in the partner\_id field. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_ARCHIVED | 400 | The analytic account is archived. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_INVOICE\_NUMBER | 422 | The format of the invoice number doesn't follow the format of the corresponding accounting system (e.g. too long) | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_OPERATION\_NUMBER | 422 | The format of the operation number doesn't follow the format of the corresponding accounting system (e.g. too long) | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_NUMBER | 422 | The format of the number doesn't follow the format of the corresponding accounting system (e.g. too long) | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_NUMBER\_PLAN\_NOT\_ACTIVE | 400 | The account number cannot be used (is not configured) with an analytic account of the specified analytic plan | Accounting | |
| ERROR\_LEDGER\_ACCOUNT\_ALREADY\_EXISTS | 400 | A ledger account already exists with the same number in the accounting system. | Accounting | |
| ERROR\_NUMBER\_ALREADY\_USED | 400 | The number of the invoice is already used in the accounting system. | Accounting | |
| ERROR\_COUNTERPART\_ACCOUNT\_NUMBER\_NOT\_GOOD\_SCOPE | 400 | The counterpart account number cannot be used in this scope. | Accounting | |
| ERROR\_COUNTERPART\_ACCOUNT\_NOT\_FOUND | 400 | The counterpart account doesn't exist in the accounting system. | Accounting | |
| ERROR\_COLLECTIVE\_ACCOUNT\_NOT\_CONFIGURED | 400 | The collective account is not set up for customer/supplier. | Accounting | |
| ERROR\_JOURNAL\_ALREADY\_EXISTS | 400 | A journal already exists with the same code in the accounting system. | Accounting | |
| ERROR\_COUNTERPART\_ACCOUNT\_ALREADY\_USED | 400 | The counterpart account is already linked to another journal. | Accounting | |
| ERROR\_LEDGER\_ACCOUNT\_ALREADY\_EXISTS | 400 | A ledger account already exists with the same number in the accounting system. | Accounting | |
| ERROR\_COUNTERPART\_ACCOUNT\_NOT\_ALLOWED | 400 | You can only specify a counterpart account on Bank and Cash journals. | Accounting | |
| ERROR\_MISSING\_COUNTERPART\_ACCOUNT | 400 | You must specify a counterpart account on Bank and Cash journals. | Accounting | |
| ERROR\_PERIOD\_BLOCKED | 400 | The accounting period is currently blocked due to a revision. | Accounting | |
| ERROR\_PDF\_MUST\_BE\_UNIQUE | 400 | The pdf already exists in the accounting system. | Accounting | The invoice that you are trying to create already exists in the target tool. It must be unique. |
| ERROR\_ENTRY\_ITEMS | 400 | You need to push at least 2 entry items. | Accounting | |
| ERROR\_BANK\_ACCOUNT\_NUMBER\_ALREADY\_EXISTS | 400 | The bank account number already exists in the accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_STATEMENT\_NUMBER | 422 | The statement id/number format is not accepted by the accounting software. | Accounting | |
| ERROR\_CUSTOMER\_NOT\_FOUND | 404 | The customer doesn't exist. | eCommerce | |
| ERROR\_PRODUCT\_NOT\_FOUND | 404 | The product doesn't exist. | eCommerce | |
| ERROR\_VARIANT\_NOT\_FOUND | 404 | The variant doesn't exist. | eCommerce | |
| ERROR\_LOCATION\_NOT\_FOUND | 404 | The location doesn't exist. | eCommerce | |
| ERROR\_ORDER\_NOT\_FOUND | 404 | The order doesn't exist. | eCommerce | |
| ERROR\_SHOPIFY\_CUSTOMER\_DATA\_ACCESS | 403 | The Shopify app is not configured to have access to customer data. See Shopify documentation. | eCommerce | |
| ERROR\_PHONE\_INVALID | 422 | The phone number doesn't seem to be valid. The number must begin with the country code. | eCommerce | |
| ERROR\_PHONE\_ALREADY\_USED | 422 | The phone number is already used by another client. | eCommerce | |
| ERROR\_INVALID\_FIELD\_FORMAT | 422 | The date format of the query parameter 'Date From' or 'Date To' is not valid. The expected format is the following: YYYY-MM-DD. | eCommerce | |
| ERROR\_NO\_ORDER\_LINE | 400 | New orders must have at least one line. | eCommerce | |
| ERROR\_INVALID\_CURRENCY\_FORMAT | 422 | The currency format is not correct. Please use the ISO 4217 codes. | eCommerce | Please use the ISO 4217 codes. |
| ERROR\_INVALID\_COUNTRY\_FORMAT | 422 | The country format is not correct. Please use the ISO 3166-1 codes. | eCommerce | |
| ERROR\_OPPORTUNITY\_NOT\_FOUND | 404 | The opportunity doesn't exist. | Invoicing | |
| ERROR\_PRODUCT\_NOT\_FOUND | 404 | The product doesn't exist. | Invoicing | |
| ERROR\_TAX\_NOT\_FOUND | 404 | The tax doesn't exist. | Invoicing | |
| ERROR\_INVOICE\_NOT\_FOUND | 404 | The invoice doesn't exist. | Invoicing | |
| ERROR\_OPPORTUNITY\_NOT\_CREATED | 400 | The opportunity was not created. | Invoicing | |
| ERROR\_PRODUCT\_NOT\_CREATED | 400 | The product was not created. | Invoicing | |
| ERROR\_TAX\_NOT\_CREATED | 400 | The tax was not created. | Invoicing | |
| ERROR\_INVOICE\_NOT\_CREATED | 400 | The invoice was not created. | Invoicing | |
| ERROR\_DUPLICATE\_PAYOUT | 409 | The payout already exists. | Payment | |
| ERROR\_ACTION\_NOT\_SUPPORTED | 400 | The requested action is not supported by this connector. | All | |
| ERROR\_BAD\_REQUEST | 400 | The request was rejected by the target application. | All | |
| ERROR\_CONNECTION\_CREDENTIALS\_NOT\_CORRECT | 401 | The connection could not be created or updated as the credentials are not correct. | All | Please check the credentials provided for the connection. |
| ERROR\_CONNECTION\_CREDENTIALS\_NOT\_SUPPORTED | 400 | At least one credential is missing for this integration. | All | |
| ERROR\_CONNECTION\_NOT\_FOUND | 404 | The connection could not be found in the target application. | All | |
| ERROR\_CONNECTION\_POSTCONNECTION\_MISSING | 400 | At least one mandatory post connection value is missing for this integration. | All | |
| ERROR\_CONNECTOR\_INTERNAL | 502 | The target connector API returned a temporary internal server error. | All | Please retry later. |
| ERROR\_CONNECTOR\_NOT\_FOUND | 404 | No connector/local agent was found with this identifier. | All | |
| ERROR\_CONNECTOR\_SCOPE | 403 | The connection is missing an OAuth scope required for this operation. Please reconnect to grant it. | All | Reconnect the connection to grant the missing scope. |
| ERROR\_DAILY\_RATE\_LIMIT | 429 | The daily rate limit of the connector is reached. | All | Please retry tomorrow. |
| ERROR\_DATALAYER\_CONNECTION\_NOT\_ENABLED | 400 | The datalayer is not enabled for this connection. | All | |
| ERROR\_DATALAYER\_ENTITY\_NOT\_AVAILABLE | 400 | The datalayer is configured to sync entities that are not available on the connection. | All | |
| ERROR\_DATALAYER\_FILTER\_NOT\_AVAILABLE\_LIVE | 409 | The request uses a filter that only the datalayer supports and the datalayer cannot serve this read. Drop the filter to be served live, or retry once the scope is synced. | All | Drop the filter to be served live, or retry once the scope is synced. |
| ERROR\_DATALAYER\_INVALID\_MAX\_STALENESS | 400 | The provided max\_staleness value is invalid. | All | |
| ERROR\_DATALAYER\_INVALID\_START\_DATE | 400 | The provided start date is invalid. | All | |
| ERROR\_DATALAYER\_NOT\_CONFIGURED | 400 | The datalayer is not configured for this account. | All | |
| ERROR\_DATALAYER\_NOT\_ENABLED | 400 | The datalayer is not enabled for this consumer. | All | |
| ERROR\_DATALAYER\_OUT\_OF\_SYNC\_WINDOW | 409 | The request starts before the period covered by the datalayer. | All | Use a date\_from within the period covered by the datalayer, or extend the datalayer start date. |
| ERROR\_DATALAYER\_SCOPE\_INACTIVE | 409 | The requested scope is turned off on this connection, so the datalayer mirrors none of it. | All | |
| ERROR\_DATALAYER\_STALE | 409 | The datalayer data is older than the staleness allowed by the request. | All | Increase the allowed staleness or retry once the datalayer has synced. |
| ERROR\_DATALAYER\_SYNC\_PENDING | 409 | The datalayer is still performing its first sync for this connection. Retry once it completes. | All | Retry once the first sync of the datalayer completes. |
| ERROR\_DATASTORE\_FORMAT | 422 | The input does not match the definition of the datastore. | All | |
| ERROR\_ENTITY\_NOT\_FOUND | 404 | The entity doesn't exist in the target application. | All | |
| ERROR\_FORBIDDEN | 403 | Access denied to the resource. | All | |
| ERROR\_INVALID\_CHAIN | 500 | No module is defined for the step of the chain. | All | |
| ERROR\_INVALID\_CREDENTIALS | 422 | The user and/or password don't seem to be correct. | All | |
| ERROR\_INVALID\_CURSOR | 400 | The cursor is either invalid or has expired. | All | |
| ERROR\_INVALID\_HEADER | 422 | One of the provided headers is invalid. | All | |
| ERROR\_INVALID\_INPUT | 422 | One of the inputs is invalid. | All | |
| ERROR\_INVALID\_MODULE\_NAME | 404 | The module cannot be found. | All | |
| ERROR\_INVALID\_PARAMETER | 400 | One of the parameters is invalid. | All | |
| ERROR\_MISSING\_QUERY\_PARAMETER | 400 | A mandatory query parameter is missing. | All | |
| ERROR\_RESOURCE\_NOT\_FOUND | 404 | The requested resource could not be found. Please check the URL or the request parameters. | All | |
| ERROR\_RESOURCE\_NOT\_IMPLEMENTED | 400 | The requested resource is not implemented for this connector. | All | |
| ERROR\_RESOURCE\_UNAVAILABLE | 503 | The flow/route has been disabled. | All | |
| ERROR\_RESOURCE\_UNDER\_ANALYSIS | 400 | The requested resource is not yet implemented but is currently under analysis. | All | Contact Chift to know when the resource will be available. |
| ERROR\_RESUME\_LATER | 409 | The rate limit of the target application was reached. The execution will resume later. | All | No action needed: the execution resumes automatically. |
| ERROR\_SETTING\_NOT\_APPLICABLE | 422 | The requested setting cannot be honoured by this flow. | All | |
| ERROR\_UNSUPPORTED\_QUERY\_PARAMETER | 400 | One of the query parameters is not supported by this connector. | All | |
| ERROR\_ACCOUNTING\_INFO\_NOT\_SETUP | 404 | The fiscal years are not set up in the accounting system. | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_ALREADY\_EXISTS | 400 | An account already exists with the same number in the accounting system. | Accounting | Use another account number or update the existing account. |
| ERROR\_ACCOUNT\_NUMBER\_CONFIGURATION | 400 | The account number is not configured to be used this way in the accounting system (e.g. with that tax code, in invoices or with analytic accounting). | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_LENGTH | 400 | The account number is too long or too short for the configured length in the target accounting system. | Accounting | Adapt the account number to the length configured in the accounting system. |
| ERROR\_ACCOUNT\_NUMBER\_NOT\_ALLOWED | 400 | The account number cannot be used for this type of journal. | Accounting | |
| ERROR\_ACCOUNT\_NUMBER\_SCOPE | 400 | The account number cannot be used in this scope. | Accounting | Ensure the account number used in the invoice line or entry is a valid ledger account for that scope. Update the account number or adjust your mapping. |
| ERROR\_ACCOUNT\_NUMBER\_WRONG\_TYPE | 400 | The account number is already used in the accounting system for another type of accounts. | Accounting | |
| ERROR\_ACCOUNT\_TYPE\_NOT\_ALLOWED | 400 | You can only create journal entries with general accounts in this accounting system. Provide 'force\_general\_account' for customer, supplier or employee lines. | Accounting | |
| ERROR\_ACCOUNT\_TYPE\_NOT\_SUPPORTED | 400 | The account type is not supported by the accounting system for this operation. | Accounting | |
| ERROR\_ACD\_GED\_ACCESS | 400 | The user doesn't have access to a specific GED folder in ACD. | Accounting | Grant the user access to the GED folder in ACD. |
| ERROR\_ACD\_INVALID\_CHARACTERS | 422 | Accounts with special characters (e.g. dots) cannot be used in the ACD entries creation endpoint. | Accounting | Remove the special characters in the account setup through the ACD interface. |
| ERROR\_AMOUNTS\_NOT\_BALANCED | 400 | The amounts of the entries are not balanced. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_LINE\_NOT\_FOUND | 404 | The analytic account line doesn't exist in the accounting system. | Accounting | |
| ERROR\_ANALYTIC\_ACCOUNT\_NOT\_ACTIVE | 400 | The analytic account is not active in the accounting system. | Accounting | Activate the analytic account in the accounting system. |
| ERROR\_ANALYTIC\_ACCOUNT\_NOT\_CONFIGURED | 400 | The analytic account is not configured to be used with this account number. | Accounting | |
| ERROR\_ANALYTIC\_PLAN\_ARCHIVED | 400 | The analytic plan is closed or not activated in the accounting system. | Accounting | Reopen the analytic plan in the accounting system. |
| ERROR\_ANALYTIC\_PLAN\_NOT\_ACTIVE | 400 | The analytic plan is not active in the accounting system. | Accounting | Activate the analytic plan in the accounting system. |
| ERROR\_ANALYTIC\_PLAN\_NOT\_GOOD\_SCOPE | 400 | The analytic plan cannot be used with this type of account. | Accounting | |
| ERROR\_ATTACHMENT\_NOT\_FOUND | 404 | No attachment was found for this document. | Accounting | |
| ERROR\_ATTACHMENT\_UPLOAD | 400 | The attachment could not be uploaded or linked to the created document. | Accounting | |
| ERROR\_ATTACHMENT\_UPLOAD\_FAILED | 400 | The entry was created in the accounting system but its attachment could not be uploaded or linked to it. | Accounting | |
| ERROR\_AUTHENTICATION\_FAILED | 401 | Authentication to the target application failed. Please verify your credentials. | Accounting | Please check the credentials used in the connection. |
| ERROR\_AUTHENTICATION\_MISSING | 401 | A credential required to authenticate to the target application is missing. | Accounting | |
| ERROR\_BANKFEED\_CONNECTION\_PENDING | 409 | The bank feed connection is still being provisioned by the accounting system. Please retry in a few minutes. | Accounting | Retry in a few minutes. |
| ERROR\_BANK\_ACCOUNT\_ALREADY\_EXISTS | 400 | A bank account with the same number/IBAN already exists in the accounting system. | Accounting | |
| ERROR\_BANK\_ACCOUNT\_NOT\_FOUND | 404 | The bank account doesn't exist in the accounting system. | Accounting | |
| ERROR\_BANK\_CODE\_ALREADY\_USED | 400 | A bank account with the same code already exists in the accounting system. | Accounting | |
| ERROR\_BANK\_STATEMENT\_ALREADY\_EXISTS | 400 | The bank statement already exists in the accounting system. | Accounting | |
| ERROR\_BANK\_TRANSACTION\_ALREADY\_EXISTS | 422 | The bank transaction already exists in the bank account of the accounting system. | Accounting | |
| ERROR\_BATCH\_ENTRIES\_MIXED\_MONTHS | 422 | All entries in a batch must belong to the same month. Please split entries by month and send separate batch requests. | Accounting | |
| ERROR\_BATCH\_INVOICES\_MIXED\_TYPES | 400 | All invoices in a batch must be of the same type. Please split invoices by type and send separate batch requests. | Accounting | |
| ERROR\_BOOKYEARS\_NOT\_FOUND | 404 | The accounting system is not set up for this date. | Accounting | Create a fiscal year in the accounting system including the date of the document. |
| ERROR\_BUSINESSCENTRAL\_NOSERIES\_CONSUMED | 400 | The numbering series has been fully consumed in Business Central. The record cannot be created. | Accounting | |
| ERROR\_CLIENT\_NOT\_CREATED | 400 | The client was not created in the accounting system. | Accounting | |
| ERROR\_COMMENT\_TOO\_LONG | 400 | The comment is too long for the accounting system. | Accounting | |
| ERROR\_COMPANY\_NAME\_ALREADY\_USED | 400 | A client/supplier with the same name already exists in the accounting system. | Accounting | |
| ERROR\_COMPANY\_NOT\_FOUND | 404 | The provided company\_id doesn't exist in the accounting system. | Accounting | |
| ERROR\_CONFIGURATION\_BANK\_ACCOUNTS | 400 | A bank account in the required currency must be created in the accounting system before creating partners linked to that currency. | Accounting | |
| ERROR\_CONFIGURATION\_DEFAULT\_ACCOUNT\_MISSING | 400 | No default account is configured in the accounting system for this operation. | Accounting | |
| ERROR\_CONFIGURATION\_MISSING\_CONNECTORS | 400 | Required connectors are missing in the configuration of the target application. | Accounting | |
| ERROR\_CONNECTOR\_EXTENSION\_PERMISSION | 401 | The extension version could not be read with the current account. Please add the required permission set to your user. | Accounting | |
| ERROR\_CONNECTOR\_OUTDATED\_EXTENSION | 400 | The installed extension version is not supported for this operation. Please update the extension. | Accounting | Update the extension in the target application. |
| ERROR\_COUNTERPART\_ACCOUNT\_NUMBER\_MISSING | 422 | Please provide a counterpart ledger account as it cannot be retrieved from the settings of the accounting system. | Accounting | |
| ERROR\_COUNTRY\_NOT\_FOUND | 404 | The country doesn't exist in the accounting system. | Accounting | |
| ERROR\_CREATE\_INVOICE\_A3ERP | 400 | The invoice could not be created in a3ERP. | Accounting | |
| ERROR\_CREATE\_JOURNAL\_ENTRY\_A3ERP | 400 | The journal entry could not be created in a3ERP. | Accounting | |
| ERROR\_CREATE\_NOT\_ALLOWED | 405 | The accounting system doesn't allow to create this type of resource. | Accounting | |
| ERROR\_CURRENCY\_EXCHANGE\_RATE | 400 | An exchange rate is required (or is not configured) to create documents in a different currency than the journal currency. | Accounting | |
| ERROR\_CURRENCY\_NOT\_ALLOWED | 400 | You cannot create an entry in the specified currency. | Accounting | Use a currency that is active in the accounting system. |
| ERROR\_CUSTOMER\_INVOICE\_PDF\_REQUIRED | 400 | An invoice number must be specified when creating a customer invoice/refund with an attachment. | Accounting | |
| ERROR\_CUSTOMER\_INVOICE\_TYPE\_NOT\_SUPPORTED | 400 | Customer invoice types are not supported for this connection. Please use a supplier invoice type. | Accounting | |
| ERROR\_DEBIT\_CREDIT\_VALUE | 422 | Debit and credit cannot be negative, nor both positive on the same line. | Accounting | |
| ERROR\_DOCUMENT\_NOT\_GOOD\_TYPE | 400 | The document is not of the expected type. | Accounting | |
| ERROR\_DRAFT\_SUPPLIER\_INVOICE | 400 | You cannot create a draft supplier invoice in this accounting system. | Accounting | |
| ERROR\_EMPLOYEE\_NOT\_CONFIGURED | 400 | The employee is not linked to a partner in the accounting system. | Accounting | |
| ERROR\_EMPLOYEE\_NOT\_FOUND | 404 | The employee doesn't exist in the accounting system. | Accounting | Make sure that the employee exists in the accounting system. |
| ERROR\_EMPTY\_FILE | 400 | The uploaded file is empty. Please upload a file containing data. | Accounting | |
| ERROR\_ENTRIES\_NOT\_CREATED | 400 | The entries could not be created in the accounting system. | Accounting | |
| ERROR\_ENTRY\_CREATION | 400 | An error occurred while creating the entry (e.g. while linking the analytic accounts). | Accounting | |
| ERROR\_ENTRY\_NAME\_ALREADY\_USED | 400 | The entry name is already used in the accounting system. | Accounting | |
| ERROR\_ENTRY\_NOT\_BALANCED | 422 | The entry is not balanced. The sum of debit is not equal to the sum of credit. | Accounting | |
| ERROR\_ENTRY\_NOT\_CREATED | 400 | The entry could not be created in the accounting system. | Accounting | |
| ERROR\_ENTRY\_NOT\_MATCHABLE | 400 | The provided entry is not matchable. | Accounting | |
| ERROR\_ENTRY\_NOT\_POSTED | 400 | The entry is not posted. You can only match posted entries. | Accounting | |
| ERROR\_EXCHANGE\_RATE\_NOT\_FOUND | 422 | No exchange rate was found for the currency on or before the given date. Please define one in the accounting system. | Accounting | |
| ERROR\_EXTF\_IMPORT\_FAILED | 403 | The EXTF file import failed in DATEV. | Accounting | |
| ERROR\_EXTF\_PERMISSION\_DENIED | 403 | The EXTF file import was refused by DATEV due to missing permissions. | Accounting | |
| ERROR\_FEC\_CREATION | 400 | The FEC export could not be created. | Accounting | |
| ERROR\_FEC\_PERIOD\_NOT\_FOUND | 422 | Could not find a bookyear covering the provided dates. The bookyear doesn't exist in the accounting system. | Accounting | |
| ERROR\_FEC\_UNSUPPORTED\_PERIOD | 422 | The requested period is not supported for exporting FEC entries. The provided dates must be within the same bookyear. | Accounting | |
| ERROR\_FILE\_ATTACHMENTS\_SCOPE\_MISSING | 403 | You cannot upload a PDF file without the file attachments scope. Please reconnect to grant it. | Accounting | Reconnect the connection to grant the file attachments scope. |
| ERROR\_FINANCIAL\_ENTRIES\_NOT\_CREATED | 400 | The financial entries were not created in the accounting system. | Accounting | |
| ERROR\_FORBIDDEN\_ACCESS | 403 | You are not allowed to access this folder's information. | Accounting | |
| ERROR\_FORCE\_GENERAL\_ACCOUNT\_NOT\_SUPPORTED | 400 | The 'force\_general\_account' field is not supported in the accounting system. | Accounting | |
| ERROR\_FREEAGENT\_ANALYTIC\_DISTRIBUTION | 400 | Using multiple analytic accounts in a single invoice is not allowed in FreeAgent. | Accounting | |
| ERROR\_FREEAGENT\_ANALYTIC\_PARTNER\_MISSMATCH | 400 | The analytic account is not linked to the partner in FreeAgent. | Accounting | |
| ERROR\_FREEAGENT\_BANK\_TRANSACTION\_ALREADY\_EXPLAINED | 400 | The bank transaction has already been explained in FreeAgent. | Accounting | |
| ERROR\_FREEAGENT\_FUTURE\_FOREIGN\_CURRENCY\_INVOICE\_NOT\_SUPPORTED | 400 | FreeAgent does not support invoices dated in the future that use a foreign currency. | Accounting | |
| ERROR\_FREEAGENT\_INVALID\_CHIFT\_ID\_FORMAT | 400 | The ID format is invalid. Expected format: 'ENTITY-ID' (e.g. 'CLI-12345'). | Accounting | |
| ERROR\_FREEAGENT\_INVALID\_EXCHANGE\_RATE | 400 | For a foreign currency, the exchange rate must be specified and not equal to 0 or 1. | Accounting | |
| ERROR\_FREEAGENT\_MATCHING\_MIXED\_ENTITY\_TYPES | 400 | Cannot mix different document types in entries. Use either invoices or bills with transactions, not both. | Accounting | |
| ERROR\_FREEAGENT\_MATCHING\_MULTIPLE | 400 | You cannot match multiple entries of the same type with multiple entries of another type at the same time. | Accounting | |
| ERROR\_FREEAGENT\_MATCHING\_NO\_TRANSACTIONS | 400 | At least one bank transaction must be provided in entries for matching. | Accounting | |
| ERROR\_FREEAGENT\_MATCHING\_UNSUPPORTED\_ENTITY | 400 | The entity type is not supported for matching. Only transactions, invoices and bills are supported. | Accounting | |
| ERROR\_GENERAL\_ACCOUNT\_USED | 400 | A general account used in the entries is not allowed in the accounting system. | Accounting | |
| ERROR\_INQOM\_ENTRY\_FORMAT | 422 | Inqom expects at least one line with a debit or credit amount. | Accounting | |
| ERROR\_INVALID\_ACCOUNT\_LENGTH | 400 | The account length defined in the file must match the information filled in the connection. | Accounting | |
| ERROR\_INVALID\_ACCOUNT\_LENGTH\_UNTERNHEMEN\_ONLINE | 400 | The account length defined in DATEV Unternehmen Online must match the information filled in the connection. | Accounting | |
| ERROR\_INVALID\_ACCOUNT\_TYPE | 400 | The account cannot be used for this type of line. | Accounting | |
| ERROR\_INVALID\_BALANCE\_RANGE | 400 | Only the year-to-date balance range is supported by the accounting system. | Accounting | |
| ERROR\_INVALID\_BANK\_ACCOUNT\_FORMAT | 422 | The bank account number doesn't seem to be correct. | Accounting | |
| ERROR\_INVALID\_BANK\_ACCOUNT\_NUMBER | 400 | The bank account could not be created because its number is invalid. | Accounting | |
| ERROR\_INVALID\_BODY\_PARAMETER | 400 | One of the parameters of the body is invalid. | Accounting | |
| ERROR\_INVALID\_CHART\_OF\_ACCOUNT\_TYPE\_UNTERNHEMEN\_ONLINE | 400 | The chart of account type (SKR 03 vs. SKR 04) defined in DATEV Unternehmen Online must match the information filled in the connection. | Accounting | |
| ERROR\_INVALID\_CONSULTANT\_CLIENT\_COMBINATION | 404 | The consultant and/or client number don't seem to be correct. | Accounting | |
| ERROR\_INVALID\_CURRENCY | 400 | The currency cannot be used in the accounting system for this operation. | Accounting | |
| ERROR\_INVALID\_ENTRY\_ITEM\_TYPE | 400 | A line of type 'customer\_account', 'supplier\_account' or 'employee\_account' must have a 'partner\_id' filled in. | Accounting | |
| ERROR\_INVALID\_FIELD | 422 | One of the fields of the body is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ACCOUNT\_ID | 422 | The format of the field 'account\_id' doesn't seem to be correct. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ACCOUNT\_NAME | 400 | The account name doesn't follow the format of the corresponding accounting system (e.g. too long). | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ACCOUNT\_NUMBER | 422 | The account number doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ANALYTIC\_ACCOUNT\_ID | 422 | The format of the field 'analytic\_account\_id' is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_DOCUMENT\_ID | 422 | The format of the field 'document\_id' is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_ENTRY\_NUMBER | 422 | The entry number doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_FOLDER\_ID | 422 | The format of the field 'folder\_id' is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_INVOICE\_ID | 422 | The format of the field 'invoice\_id' is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_JOURNAL\_CODE | 422 | The journal code doesn't follow the format of the corresponding accounting system (e.g. too long). | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_JOURNAL\_NAME | 400 | The journal name doesn't follow the format of the corresponding accounting system (e.g. too long). | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_NAME | 422 | The name doesn't follow the format of the corresponding accounting system (e.g. too long). | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_OPERATION\_ID | 422 | The format of the field 'operation\_id' is invalid. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_PARTNER | 422 | The identifier of the client/supplier doesn't follow the format of the corresponding accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_FORMAT\_POSTAL\_CODE | 422 | The postal code doesn't follow the format of the corresponding accounting system (e.g. too long). | Accounting | |
| ERROR\_INVALID\_FIELD\_NUMBER | 422 | An entry number is mandatory for this accounting system. | Accounting | |
| ERROR\_INVALID\_FIELD\_VALUE | 400 | One of the field values is invalid for the accounting system. | Accounting | |
| ERROR\_INVALID\_FILE | 400 | The uploaded file format is invalid. | Accounting | |
| ERROR\_INVALID\_FISCAL\_YEAR\_START\_UNTERNHEMEN\_ONLINE | 400 | The fiscal year start defined in DATEV Unternehmen Online must match the information filled in the connection. | Accounting | |
| ERROR\_INVALID\_G\_ACCOUNT | 422 | The G-account IBAN is invalid. It must start with NL and contain 099 at the right position. | Accounting | |
| ERROR\_INVALID\_IBAN\_FORMAT | 422 | The IBAN doesn't seem to be correct. | Accounting | |
| ERROR\_INVALID\_INVOICE\_BODY | 400 | The invoice body is not valid for the accounting system. | Accounting | |
| ERROR\_INVALID\_JOURNAL\_CODE | 400 | This journal code is already being used in the accounting system. | Accounting | |
| ERROR\_INVALID\_LEDGER\_ACCOUNT\_NUMBER | 422 | The provided ledger account number is not valid for this partner. | Accounting | |
| ERROR\_INVALID\_PAYMENT\_TERM\_SPLIT | 422 | The payment terms split is invalid (e.g. the amounts don't add up to the invoice total or the IBANs are not valid). | Accounting | |
| ERROR\_INVALID\_POSTCONNECTION\_VALUE | 400 | One of the post connection values is invalid. | Accounting | |
| ERROR\_INVALID\_REQUEST | 422 | The request is invalid for the accounting system (e.g. a PDF can only be attached when using client and/or supplier accounts). | Accounting | |
| ERROR\_INVALID\_SKR\_TYPE | 400 | The chart of account type (SKR 03 vs. SKR 04) defined in the file must match the information filled in the connection. | Accounting | |
| ERROR\_INVALID\_START\_DAY\_OF\_YEAR\_DAY\_UNTERNHEMEN\_ONLINE | 400 | The start day of the fiscal year cannot be greater than 31. The expected format is 'ddMM'. | Accounting | |
| ERROR\_INVALID\_START\_DAY\_OF\_YEAR\_FORMAT\_UNTERNHEMEN\_ONLINE | 400 | The start day of the fiscal year must be 4 digits in the format 'ddMM'. | Accounting | |
| ERROR\_INVALID\_START\_DAY\_OF\_YEAR\_MONTH\_UNTERNHEMEN\_ONLINE | 400 | The start month of the fiscal year cannot be greater than 12. The expected format is 'ddMM'. | Accounting | |
| ERROR\_INVALID\_TAX\_AMOUNT | 400 | The tax amount is not valid for the used tax code (e.g. it must be zero for a reverse-charge VAT code). | Accounting | |
| ERROR\_INVALID\_TRANSACTION\_DATE | 400 | The bank statement start date is outside the range accepted by the accounting system. | Accounting | |
| ERROR\_INVOICE\_CURRENCY\_MISMATCH | 412 | All invoices must be in the same currency and match the provided currency when creating a payment. | Accounting | |
| ERROR\_INVOICE\_DATE\_IN\_FUTURE | 400 | You cannot create an invoice with an invoice date in the future without a PDF. | Accounting | |
| ERROR\_INVOICE\_DATE\_IN\_PAST | 400 | You cannot create draft invoices before existing validated invoices on Pennylane. | Accounting | Adapt the setting of the synchronisation to create validated invoices instead of draft invoices. |
| ERROR\_INVOICE\_NUMBER\_EMPTY | 400 | The invoice number must be filled in for this accounting system. | Accounting | |
| ERROR\_INVOICE\_NUMBER\_NOT\_ACCEPTED | 400 | The invoice number is not accepted by the accounting system (e.g. it doesn't follow the expected sequence). | Accounting | |
| ERROR\_INVOICE\_NUMBER\_NOT\_VALID | 422 | The invoice number is not valid for the accounting system. | Accounting | |
| ERROR\_INVOICE\_PARTNER\_MISMATCH | 412 | All invoices must belong to the same partner when creating a payment. | Accounting | |
| ERROR\_INVOICE\_PAYMENT\_NOT\_CREATED | 400 | The invoice payment was not created in the accounting system. | Accounting | |
| ERROR\_INVOICE\_TYPE\_MISMATCH | 412 | You cannot create a payment for both customers and suppliers at the same time. | Accounting | |
| ERROR\_ISUITEEXPERT\_VERSION | 400 | The iSuite Expert version is too old. 23 is the minimum required version. | Accounting | |
| ERROR\_JOURNAL\_BLOCKED | 400 | The journal is blocked in the accounting system. | Accounting | Unblock the journal in the accounting system. |
| ERROR\_JOURNAL\_CODE\_ALREADY\_USED | 400 | The journal code is already used in the accounting system. | Accounting | |
| ERROR\_JOURNAL\_ENTRY\_CREATION\_FAILED | 400 | The journal entry couldn't be created in the accounting system. | Accounting | |
| ERROR\_JOURNAL\_NOT\_ACCEPTED | 400 | This type of document cannot be created in the given journal. | Accounting | |
| ERROR\_JOURNAL\_TYPE\_NOT\_ALLOWED | 400 | The journal type is not allowed by the accounting system for this operation. | Accounting | |
| ERROR\_LIMIT\_REACHED | 400 | A limit of the accounting system has been reached (e.g. the maximum number of customers). | Accounting | |
| ERROR\_MATCHING\_DRAFT\_ENTRY | 400 | A draft entry cannot be matched. | Accounting | |
| ERROR\_MATCH\_ENTRIES\_NOT\_CREATED | 400 | The entries were not matched in the accounting system. | Accounting | |
| ERROR\_MISSING\_SHIPPING\_COUNTRY | 400 | You must provide a shipping country when using European taxes. | Accounting | |
| ERROR\_MULTIPLE\_CURRENCIES | 422 | Only one currency can be used. | Accounting | |
| ERROR\_MULTIPLE\_EXCHANGE\_RATES | 422 | Exchange rates must be equal. | Accounting | |
| ERROR\_MULTIPLE\_PARTNERS | 400 | The entries have different clients/suppliers. | Accounting | |
| ERROR\_MULTIPLE\_VAT\_REGIMES\_USED | 400 | Tax codes from different VAT regimes are used in the invoice. | Accounting | |
| ERROR\_NEGATIVE\_JOURNAL\_BALANCE | 422 | The journal balance is negative. Please correct the balance in the accounting system to be able to create new entries. | Accounting | Correct the journal balance in the accounting system. |
| ERROR\_NO\_DOCUMENT\_MANAGEMENT | 401 | The client doesn't have the document management feature. | Accounting | |
| ERROR\_NO\_EXTF\_FILES | 401 | The client doesn't have the EXTF files feature. | Accounting | |
| ERROR\_NO\_GL\_ACCOUNT\_CODE\_FOUND | 400 | The GL account code couldn't be determined. | Accounting | |
| ERROR\_ODOO\_ACCESS\_RIGHTS | 422 | The user doesn't have admin rights on the Odoo instance. Please verify that the user has admin rights. | Accounting | |
| ERROR\_ODOO\_INVALID\_CREDENTIALS | 422 | The Odoo user and/or password don't seem to be correct. | Accounting | |
| ERROR\_ODOO\_PROTOCOL\_ERROR | 422 | Connection error with Odoo. The server may be inactive, the URL invalid or the database missing or inactive. | Accounting | Verify that the provided credentials still refer to an active Odoo instance and database. |
| ERROR\_ODOO\_UNSUPPORTED | 422 | This version of Odoo is not supported. | Accounting | |
| ERROR\_ODOO\_VERSION | 400 | This operation cannot be used with this version of Odoo. | Accounting | |
| ERROR\_OPERATION\_NUMBER\_EMPTY | 400 | The operation number must be filled in for this accounting system. | Accounting | |
| ERROR\_PARENT\_ACCOUNT\_NOT\_DIVIDABLE | 400 | The client/supplier cannot be created. The parent account (411 for customers and 401 for suppliers) is not dividable. | Accounting | Change the setup of these accounts in the accounting system. |
| ERROR\_PARTNER\_BANK\_ACCOUNT\_MISSING | 400 | A bank account is mandatory for this client/supplier in the accounting system. | Accounting | Add a bank account to the client/supplier in the accounting system. |
| ERROR\_PARTNER\_NOT\_CONFIGURED | 400 | The client/supplier is not correctly configured in the accounting system (e.g. missing receivable/payable account or VAT number). | Accounting | Complete the configuration of the client/supplier in the accounting system. |
| ERROR\_PAYMENT\_AMOUNT\_MISMATCH | 400 | The amount of the payment exceeds the open amount of the linked invoice. | Accounting | |
| ERROR\_PAYMENT\_INVOICE\_DRAFT | 400 | A payment cannot be registered on a draft invoice. | Accounting | |
| ERROR\_PAYMENT\_METHOD\_NOT\_ACTIVE | 400 | The payment method is not active in the accounting system. | Accounting | Activate the payment method in the accounting system. |
| ERROR\_PAYMENT\_TERM\_NOT\_FOUND | 404 | The payment term doesn't exist in the accounting system. | Accounting | |
| ERROR\_PERIOD\_NOT\_FOUND | 404 | The accounting period doesn't exist in the accounting system. | Accounting | |
| ERROR\_SUPPLIER\_INVOICE\_PDF\_REQUIRED | 400 | An attachment is required to create a supplier invoice. | Accounting | Provide a PDF with the supplier invoice. |
| ERROR\_SUPPLIER\_INVOICE\_TYPE\_NOT\_SUPPORTED | 400 | Supplier invoices are not supported for this connector. | Accounting | |
| ERROR\_SUPPLIER\_NOT\_CREATED | 400 | The supplier was not created in the accounting system. | Accounting | |
| ERROR\_TAX\_CODE\_MISSING | 400 | A tax code must be provided with the used ledger account. | Accounting | |
| ERROR\_TAX\_CODE\_NOT\_ACTIVE | 400 | The tax code is not active in the accounting system. | Accounting | Activate the tax code in the accounting system or adapt the tax code in the mapping (if using a sync). |
| ERROR\_TAX\_MULTIPLE\_VAT\_ACCOUNTS | 400 | Multiple VAT accounts are used with the same tax code. The VAT account must be the same for a single tax code. | Accounting | |
| ERROR\_UNBALANCED\_ENTRY\_REQUIRES\_DRAFT | 400 | The balance validation of the accounting system failed. Send the invoice with status 'draft' to bypass it. | Accounting | |
| ERROR\_UNEXPECTED\_ACD | 400 | This is an unexpected ACD error. | Accounting | Check the detail of the error. Contact support if needed. |
| ERROR\_UNEXPECTED\_ODOO | 400 | Odoo returned an invalid response. | Accounting | |
| ERROR\_UNKNOWN\_FILE | 400 | The uploaded file is not recognised. | Accounting | |
| ERROR\_UNMATCHABLE\_ENTRIES | 400 | The entries cannot be matched together in the accounting system. | Accounting | |
| ERROR\_UNSUPPORTED\_ATTACHMENT\_TYPE | 415 | Unsupported attachment type. Allowed: PDF, JPEG, PNG. | Accounting | Provide a PDF, JPEG or PNG attachment. |
| ERROR\_UNSUPPORTED\_ATTRIBUTE | 400 | One of the attributes of the body is not supported on this connector. | Accounting | |
| ERROR\_UNSUPPORTED\_BODY | 422 | The body is not supported by this connector (a required field is missing or a value is not accepted). | Accounting | |
| ERROR\_UNSUPPORTED\_QB\_ENTITY | 422 | The QuickBooks entity is not supported. | Accounting | |
| ERROR\_WRONG\_TAX\_CODE\_COMBINATION | 400 | The tax codes used in the invoice cannot be combined together. | Accounting | |
| ERROR\_YUKI\_ANALYTIC\_DISTRIBUTION | 400 | Using multiple analytic accounts or plans in a single invoice is not allowed in Yuki. | Accounting | |
| ERROR\_ZERO\_ENTRY | 422 | You cannot create an entry where all lines have debit and credit equal to 0. | Accounting | |
| ERROR\_FOLDER\_ID\_MISSING | 405 | The folder must be provided in the query params. | Accounting, Invoicing | |
| ERROR\_PARTNER\_NOT\_GOOD\_SCOPE | 400 | The client/supplier cannot be used in this type of journal. | Accounting, Invoicing | |
| ERROR\_PAYMENT\_METHOD\_NOT\_FOUND | 404 | The payment method doesn't exist in the target application. | Accounting, Invoicing | |
| ERROR\_CLIENT\_CONTACT\_NOT\_CREATED | 400 | The client contact was not created in the invoicing system. | Invoicing | |
| ERROR\_CONTACT\_ID\_FORMAT | 400 | The ID of the contact doesn't have the correct format. | Invoicing | |
| ERROR\_CONTACT\_NOT\_CREATED | 400 | The contact was not created in the invoicing system. | Invoicing | |
| ERROR\_CONTACT\_NOT\_FOUND | 404 | The requested contact does not exist. | Invoicing | |
| ERROR\_DOCUMENT\_TYPE\_NOT\_SUPPORTED | 400 | The document type is not supported by the invoicing system. | Invoicing | |
| ERROR\_EINVOICING\_REQUIRED | 400 | E-invoicing must be activated in the invoicing system in order to create invoices. | Invoicing | |
| ERROR\_ENTRY\_ALREADY\_CREATED | 400 | The entry already exists in the target application. | Invoicing | |
| ERROR\_INVOICE\_ID\_FORMAT | 400 | The ID of the invoice doesn't have the correct format. | Invoicing | |
| ERROR\_INVOICE\_NOT\_POSTED | 400 | The invoice was not posted in the invoicing system. | Invoicing | |
| ERROR\_PAYDATE\_ID\_NOT\_FOUND | 404 | The paydate id doesn't exist in the invoicing system. | Invoicing | |
| ERROR\_PAYMENT\_NOT\_CREATED | 400 | The payment was not created (e.g. no journal is configured with an inbound payment method). | Invoicing | |
| ERROR\_PAYMENT\_NOT\_DELETED | 400 | The payment could not be deleted (e.g. it is linked to one or more documents). | Invoicing | |
| ERROR\_PAYMENT\_NOT\_UPDATED | 400 | The payment could not be updated. | Invoicing | |
| ERROR\_PRODUCT\_ID\_FORMAT | 400 | The ID of the product doesn't have the correct format. | Invoicing | |
| ERROR\_STATUS\_ALREADY\_SET | 400 | The document is already in the expected status. | Invoicing | |
| ERROR\_TAX\_ID\_FORMAT | 400 | The ID of the tax doesn't have the correct format. | Invoicing | |
| ERROR\_PAYMENT\_NOT\_FOUND | 404 | The payment doesn't exist. | Invoicing, Payment | |
| ERROR\_RESUMABLE\_FETCH\_DATA\_LOSS | 500 | Checkpoint data is missing, the fetch cannot safely resume. | eCommerce | |
| ERROR\_BALANCE\_NOT\_FOUND | 404 | The requested balance doesn't exist. | Payment | |
| ERROR\_CONNECTOR\_BAD\_REQUEST | 400 | The request was rejected by the connector. | Payment | |
| ERROR\_INVALID\_PAYMENT\_ID | 400 | The payment id is invalid. | Payment | |
| ERROR\_PAYOUT\_NOT\_FOUND | 404 | The payout doesn't exist. | Payment | |
| ERROR\_PAYPLUG\_REFUND\_WITHOUT\_PAYMENT\_ID | 400 | Payplug does not support retrieving refunds without a payment\_id. | Payment | |
| ERROR\_REFUND\_NOT\_FOUND | 404 | The refund doesn't exist. | Payment | |
| ERROR\_TRANSACTIONS\_NOT\_FOUND | 400 | Unable to retrieve the transactions. Try using a narrower date range. | Payment | |
| ERROR\_CLYO\_VERSION | 406 | Accounting categories can only be retrieved on Clyo versions starting from 1.303.0.0. | POS | |
| ERROR\_COMPANY\_ID\_NOT\_FOUND | 400 | No company could be found for the given location. | POS | |
| ERROR\_INVALID\_LOCATION\_ID | 404 | The location id is invalid. | POS | |
| ERROR\_INVALID\_SITE\_ID | 400 | The site ID is invalid. | POS | |
| ERROR\_LIGHTSPEED\_VERSION | 406 | Orders and payments can only be retrieved from the date of the change to Lightspeed version 3. | POS, Payment | |
| ERROR\_CONNECTOR\_INVALID\_URL | 400 | The provided instance URL is invalid. | PMS | |
| ERROR\_TRANSACTION\_NOT\_FOUND | 404 | The bank transaction doesn't exist. | Banking | |
| UNEXPECTED\_\{CONNECTOR}\_ERROR | 400 | The connector returned an error that Chift could not map to a known error code (e.g. UNEXPECTED\_ODOO\_ERROR). The detail contains the response of the connector. | All | Check the detail of the error and retry. Contact support if it persists. |
| ERROR\_CONSUMER\_NOT\_FOUND | 404 | The consumer does not exist. | All | |
| ERROR\_FLOW\_NOT\_FOUND | 404 | The flow does not exist. | All | |
| ERROR\_EXECUTION\_NOT\_FOUND | 404 | The execution does not exist. | All | |
| ERROR\_DATASTORE\_NOT\_FOUND | 404 | The datastore does not exist. | All | |
| ERROR\_DATASTOREDATA\_NOT\_FOUND | 404 | The datastore data does not exist. | All | |
| ERROR\_ISSUE\_NOT\_FOUND | 404 | The issue does not exist. | All | |
| ERROR\_MARKETPLACE\_NOT\_FOUND | 404 | The marketplace does not exist. | All | |
| ERROR\_TRIGGER\_NOT\_FOUND | 404 | The trigger does not exist. | All | |
| ERROR\_ICON\_NOT\_FOUND | 404 | The icon of the integration does not exist. | All | |
| ERROR\_LOGO\_NOT\_FOUND | 404 | The logo of the integration does not exist. | All | |
| ERROR\_SYNC\_NOT\_CREATED | 422 | The sync was not created. | All | |
| ERROR\_ACCOUNT\_NOT\_FOUND | 404 | The account doesn't exist in the accounting system. | Accounting | |
| ERROR\_LEDGER\_ACCOUNT\_NOT\_FOUND | 404 | The ledger account doesn't exist in the accounting system. | Accounting | |
| SAGE\_INTACCT\_ATTACHMENT\_ALREADY\_EXISTS | 400 | An attachment already exists for this document in Sage Intacct. | Accounting | |

### Sync errors

Syncs raise error codes prefixed with `ERROR_SYNC_` (or `WARNING_SYNC_` when the record was still synchronized with a fallback). These errors appear in the execution logs of a sync. See [Monitor executions](/syncs/monitor-executions) to find the execution logs and the affected records.

The following errors can occur in any sync:

| Error code | Error description | Resolution |
| - | - | - |
| ERROR\_SYNC\_UNBALANCED\_ENTRY | The synchronization could not be completed because the entry is unbalanced. | An accounting entry must always balance: the total debits must equal the total credits (see [journal entries](/unified-apis/accounting/concepts/journal-entry)). Open the execution logs to find the affected record and verify its amounts in the source tool (for example, discounts, tips or payments that are not recorded correctly). If the amounts are correct in the source tool, contact Chift's support with the consumer ID. |
| ERROR\_SYNC\_MISSING\_CONNECTION | The connection required by the synchronization is missing or no longer active. | Reconfigure the connection (source or target) for this consumer and retry. |
| ERROR\_SYNC\_PARALLEL\_EXECUTION | Another execution of this synchronization is already running. | No action needed: this execution has been skipped and will be retried later. |
| ERROR\_EXECUTION\_ALREADY\_RUNNING | An execution of this flow is already running for this consumer. Parallel executions are not allowed. | Wait for the running execution to finish before triggering a new one. |
| ERROR\_RETRY\_LATER | The data is not ready to be synchronized yet (e.g. a closure is still open in the source tool). | No action needed: the synchronization will be retried automatically. |
| ERROR\_SYNC\_MISSING\_MAPPING\_VALUE | A value required by the synchronization is missing from a mapping. | Complete the mapping configuration of the sync and retry. |
| ERROR\_SYNC\_TAX\_CODE\_NOT\_CONFIGURED | The tax code is not configured to be used with this type of document in the accounting system. | Set up the tax code in the accounting system (e.g. link the deductible/collected VAT account) or adapt the tax rate mapping of the sync. |
| ERROR\_SYNC\_TAX\_CODE\_NOT\_GOOD\_SCOPE | The tax code cannot be used with this type of document (e.g. a sales tax code used in a purchase invoice). | Adapt the tax rate mapping of the sync so that it points to a tax code of the right scope. |
| ERROR\_SYNC\_INVALID\_ACCOUNT\_TYPE | The account type is invalid for the operation being performed. | Check the accounts used in the mapping: a customer/supplier account cannot be used where a general account is expected, and vice versa. |
| ERROR\_SYNC\_BATCH\_UPLOAD | A batch of entries could not be uploaded to the accounting system. | Open the execution logs to find the underlying error returned by the accounting system, correct the affected entries and retry. |
| ERROR\_MISSING\_CONTACT\_INFO | The contact information is incomplete and the contact could not be created in the accounting system. | Complete the contact (name, company name or VAT number) in the source tool and retry. |
| ERROR\_SYNC\_UNEXPECTED\_ERROR | An unexpected error occurred during the synchronization. | Retry later. If the issue persists, contact support with the execution id. |
| ERROR\_SYNC\_INTERNAL\_ERROR | An internal error occurred during the synchronization. | Retry later. If the issue persists, contact support with the execution id. |
| ERROR\_SYNC\_NOT\_FOUND | The requested sync or flow does not exist. | Check the sync id and the flow id used in the request. |
| ERROR\_SYNC\_AMBIGUOUS | Multiple syncs match this consumer and sync combination. | Contact support. |

Errors specific to a ready-to-use sync are listed in the troubleshooting section of that sync:

* [Invoices sync](/syncs/ready-to-use-syncs/invoices#troubleshooting) (`ERROR_SYNC_INVOICE_*`)
* [eCommerce sync](/syncs/ready-to-use-syncs/ecommerce#troubleshooting) (`ERROR_SYNC_ECOMMERCE_*`)
* [POS sync](/syncs/ready-to-use-syncs/pos#troubleshooting)
* [PMS sync](/syncs/ready-to-use-syncs/pms#troubleshooting)
* [Payment sync](/syncs/ready-to-use-syncs/payment#troubleshooting)

#### Accounting to accounting sync

| Error code | Error description | Resolution |
| - | - | - |
| ERROR\_SYNC\_ACCOUNTING\_MISSING\_JOURNAL | The journal is missing in the source or target accounting system. | Check the journal mapping of the sync and make sure the journal exists in both accounting systems. |
| ERROR\_SYNC\_ACCOUNTING\_MISSING\_MATCHING\_INFO | The matching entry is missing information required to book it (target partner, entries, ...). | Open the execution logs to find the affected entry and verify that its partner and matched entries were synchronized. |
| ERROR\_SYNC\_ACCOUNTING\_MISSING\_ANALYTIC\_PLAN | The analytic plan is missing in the mapping configuration or in the target accounting system. | Complete the analytic plan mapping of the sync or create the analytic plan in the target accounting system. |
| ERROR\_SYNC\_ACCOUNTING\_PARTNER\_NOT\_FOUND | The partner could not be found in the source accounting system. | Verify that the client/supplier still exists in the source accounting system. |
| ERROR\_SYNC\_ACCOUNTING\_ACCOUNT\_NOT\_FOUND | The account number could not be found in the source accounting system. | Verify that the ledger account still exists in the source accounting system. |
| ERROR\_SYNC\_ACCOUNTING\_ANALYTIC\_ACCOUNT\_NOT\_FOUND | The analytic account could not be found in the source or target accounting system. | Verify that the analytic account exists in both accounting systems or adapt the analytic mapping of the sync. |

#### Banking sync

| Error code | Error description | Resolution |
| - | - | - |
| ERROR\_SYNC\_BANKING\_MISSING\_COUNTERPART\_MAPPING | No counterpart account mapping was found for the bank account. | Complete the counterpart account mapping of the bank account in the sync configuration and retry. |
| ERROR\_SYNC\_BANKING\_ACCOUNT\_PROCESSING | The bank account could not be processed during the synchronization. | Open the execution logs to find the underlying error for the affected bank account. |
| ERROR\_SYNC\_BANKING\_GROUPED\_TRANSACTION | The grouped bank transactions could not be booked in the accounting system. | Open the execution logs to find the error returned by the accounting system for the affected group of transactions. |
| ERROR\_SYNC\_BANKING\_TRANSACTION | The bank transaction could not be booked in the accounting system. | Open the execution logs to find the error returned by the accounting system for the affected transaction. |
| ERROR\_SYNC\_BANKING\_BANK\_ACCOUNT\_CREATION | The bank account could not be created in the accounting system. | Open the execution logs to find the error returned by the accounting system, or create the bank account manually in the accounting system and map it. |
| WARNING\_SYNC\_BANKING\_UNMAPPED\_TRANSACTION\_TYPE | The transaction type is not mapped. The default suspense account was used instead. | Map the transaction type in the sync configuration if it must be booked on a specific account. |
| WARNING\_SYNC\_BANKING\_MISSING\_LEDGER\_ACCOUNT | No ledger account was found in the mapping. The waiting account was used instead. | Complete the ledger account mapping if the transaction must be booked on a specific account. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.