> ## 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 | Please check the credentials used in the connector configuration | | 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 | | | 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 | | | 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 | | | 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 | | | 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 | | | 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 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 setup 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 | | | 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 | | ### Sync errors Syncs raise error codes prefixed with `ERROR_SYNC_`. These errors appear in the execution logs of a sync. See [Monitor executions](/developer-guide/syncs/monitor-executions) to find the execution logs and the affected records. Errors specific to the invoices sync (`ERROR_SYNC_INVOICE_*`) are listed in the [Invoices sync troubleshooting](/developer-guide/syncs/ready-to-use-syncs/invoices#troubleshooting) section.