Datev

This section contains no articles.

Exact Online / Exact Globe

• Integrations call error: Grootboekrekening - kostenplaats/kostendrager koppeling bestaat niet

  The cost center / cost unit selected in the booking line is not allowed on the selected general ledger account. Solution: In Exact online, go to Financial Entries & G/L Accounts G/L Accounts Overview Select the the relevant general ledger account Cost analysis. Click on: Add link located behind cost center / cost unit. Add the cost centers / cost unitsFew readers

• Integrations call error: Error encountered in converting the value from request payload for property 'GLAccount' to type 'Guid

  Solution: This error message indicates that you are trying to book an invoice/expense without a general ledger. Verify that a general ledger account has been entered in the booking line.Few readers

• Integrations call error: Not allowed: Currency

  Solution: The currency on the invoice/expense is not allowed in Exact. Please check the following settings in Exact: Master data Financial Journal Purchase journal Is the checkbox variable currency turned on? If not, please turn this checkmark On. Is the checkbox exchange rate turned on? If so, please turn this checkmark Off.Few readers

• Integrations call error: Verplicht: vervaldatum / Verplicht: betalingsconditie

  Solution: No payment condition has been set for the creditor. In Exact Online, go to Accounts Suppliers Overview Click on the employee’s creditor Then you can select Edit at the top left corner of the screen Scroll down and choose a payment term under the header Creditor by pressing the magnifying glass and choosing a payment termFew readers

• Integrations call error: [GLtransactions] Leverancier (type)

  Solution: Most likely the creditor has not been created / designated as a supplier in Exact Online. In Exact online, go to Accounts Suppliers Overview. There you will find a list of all the creditors. Select the corresponding employee and click on Edit Check if the Supplier box has been checked.Few readers

• Integrations call error: Forbidden - user division is not within division scope

  Solution: The following steps should be performed to give Klippa access to the relevant administrations: In Exact Online, go to import/export. Click on the App permissions button, located under the other header. Click on Klippa for the user who authorised the connection with Klippa. At the bottom of the page at permitted companies you can see to which administrations Klippa has access to. If you click on manage administrations you can add administrationsFew readers

• Integrations call error: 403 Forbidden

  Solution: This error occurs when te linked user does nog have sufficient rights to exchange data, or does not have access to the specific division of Exact Online. Check the user’s rights and settings in Exact Online.Few readers

• Integrations call error: Document Type is not allowed

  Solution This means that the Exact Online account, with which the connection was made, does not have sufficient rights to make bookings. The connection needs to be re-established. More information about making the connection can be found in the following article: https://help.klippa.com/en/article/how-to-connect-with-exact-online-18sgqoa/Few readers

General

• Integrations call error

  Solution: If there is no explanation on the integration call error, check if the accounting relation, general ledger account and VAT code fields are filled in. These are required fields for booking invoices and expenses.Few readers

Minox

• Integrations call error - No account with the id 'X' exists in this administration

  Solution: The supplier is not active in the booking period of the invoice/expense. Check the posting date of the invoice/expense Check the supplier in Minox. If the supplier has been recently added, the booking date must be after the supplier's addition date.Few readers

• Integrations call error: The booking contains a booking line without a VAT code

  Solution: The error message indicates that you are trying to book an invoice without a VAT code. However, in Minox a VAT code has been assigned to the general ledger account to which you are trying to book. This leads to an incorrect Minox booking. Check whether the VAT code is set correctly on the general ledger account in Minox.Few readers

• Integrations call error: Accounts of type 'ledger_account' only allow VAT when using unlocked VAT or with preset VAT

  Accounts of type ledgeraccount only allow VAT when using unlocked VAT or with preset VAT in journals of type purchase. Solution This means that a VAT code can only be used for the general ledger account if unlocked VAT is enabled.Few readers

NetSuite

• Integrations call error: There is already an employee with external access to this account using that entity name.

  Solution When the match relation based on email address setting is enabled, it is important that the user has the same email address in Klippa as in Netsuite. This is because it is not allowed to create the same user twice.Few readers

Informer

• Integrations call error: Invalid vat_id in line 1...

  Solution This error message indicates that no VAT code was entered when booking the expense/invoice. Enter a VAT code in the booking line.Few readers

• Integrations call error: Accounting relation is required

  Solution* This error message indicates that no accounting relation was entered when booking the expense/invoice. Enter an accounting relation when booking the expense/invoice.Few readers

• Integrations call error: Invalid ledger_id in line 1...

  Solution This error message indicates that no general ledger account was entered when booking the expense/invoice. Enter a general ledger in the booking line.Few readers

SAP BusinessByDesign

• Integrations call error: sap_bydesign connect failed: could not get profile

  The connection with SAP BusinessByDesign could not be made. This can have several causes: Check if the user who created the integration has an active account in SAP BusinessByDesign Check is the correct email address and password are entered. Check if the correct ULR has been entered.Few readers