Exact Online error messages in Reflex Harmony integrations
When exchanging data from Reflex Harmony to Exact Online, errors may occur that prevent the data from being accepted.
When errors occur during data exchange, you will receive a notification via email. In the Reflex Cloud Portal, you can view notifications for each failed record in the failed integration run, indicating why the data exchange failed. These notifications often contain information from Exact Online.
Known error messages and solutions
The table below provides an overview of known messages from Exact Online, possible causes, and suggestions on how to resolve the issue.
The solutions below often indicate that you can adjust things in Exact Online to solve a certain problem.
Although the solution can solve the possible problem, you always remain responsible for checking whether this adjustment is actually a correct adjustment for your Exact Online administration.
Please contact your Exact Online representative to determine whether the proposed solution works well in your Exact Online administration.
| Exact Online message | Description and solution |
|---|---|
| In use: Document number | This means that the invoice number already exists in Exact Online. The invoice may have already been processed. Check your administration in Exact Online. |
| Not allowed: VAT code | This means that the journal where Exact Online wants to place the invoice does not allow VAT codes. This can be resolved by enabling this in the journal settings in Exact Online. |
| Invalid: Cost center link | This error message appears when a cost center in Exact Online does not have a general ledger number linked. This can be resolved by linking a general ledger number to the specified cost center in Exact Online. |
| Required: Journal | In Exact Online, the journals are not set. Fill in the journals in Exact Online under Settings -> Financial tab. |
| Invalid: Customer (Type) | The debtor is invalid. This error message can occur if a new debtor is sent to Exact Online, but the debtor number already exists for another relation in Exact Online. This error message can also occur if the relation in Exact Online is set to Prospect. In that case, change it to Customer. |
| Blocked: General ledger account: XXX | In Exact Online, this general ledger account is blocked. Look it up and unblock the general ledger account. |
| Invalid: General ledger account type | Check whether the journal number of the sales journal and general ledger account number are suitable for sales invoices. Also check that the VAT code specified for the transaction is filled in and matches the general ledger account number. |
| Required: Payment condition | No payment condition is sent with the export, but this is not set by default in Exact Online. Fill in a standard payment condition in Exact Online under Settings -> Financial tab. |
| Invalid reference: Payment condition | A payment condition must be created for the missing number in Exact Online. |