SnelStart: Error messages

This error message indicates that a problem occurred while opening the company file (administration) in SnelStart.
Cause:
A corrupted company file or an incorrect configuration of the SnelStart software.
Examples:
The company file is corrupted as a result of a power outage.
The SnelStart software is not installed correctly on the computer.
The company file has been moved to a different location without the necessary adjustments in the software.
Solution:
Try to repair the company file using the built-in recovery options in SnelStart. If this does not work, please contact SnelStart support for further assistance.

This error message indicates that the entered login credentials for SnelStart are not valid.
Cause:
This problem can be caused by a typo in the username or password, or by an expired or blocked account.
Examples:
The username was accidentally mistyped.
The password has expired and needs to be renewed.
The account is temporarily blocked due to multiple failed login attempts.
Solution:
Check the entered login credentials and correct any typos. If the password has expired, request a new password or contact the administrator of the SnelStart account. If the account is blocked, contact SnelStart support for further assistance.

This error message indicates that the specified relation ID exists in SnelStart, but is not configured or marked as a supplier.
Cause:
The integration is attempting to perform a purchase entry or action on a relation registered in the company file as a customer or general relation.
Examples:
An incorrect ID belonging to a customer was sent from the external software.
The relation is newly created, but the 'Supplier' checkbox was forgotten in SnelStart.
A supplier ID was subsequently changed manually in the company file.
Solution:
Check the status of the relevant relation in SnelStart. Ensure that the relation is correctly marked as a supplier or adjust the ID mapping in the source system to the correct supplier.

This error message indicates that the linked general ledger account can no longer be actively used for entries.
Cause:
The general ledger account was manually deleted or set to inactive within the SnelStart company file, while the integration is still trying to post to it.
Examples:
An accountant cleaned up the company file and archived old general ledger accounts.
An attempt is made to synchronize an entry to an account that no longer exists in the current fiscal year.
Solution:
Reactivate the relevant general ledger account in SnelStart, or change the configuration settings in BEX PMS to reference an active, valid general ledger account.

This error message indicates that the purchase journal where the integration wants to log the entry has been deactivated.
Cause:
The journal is marked as inactive or has been removed from the settings in SnelStart.
Examples:
A new purchase journal was created and the old one was set to inactive.
Due to an administrative change, the default purchase journal is no longer available.
Solution:
Check the journal settings in SnelStart to see if the purchase journal is active. Change the status back to active or adjust the integration settings in BEX PMS to the current purchase journal.

This error message indicates that SnelStart cannot find the specified purchase journal at all.
Cause:
The identification or name of the purchase journal in the integration does not match what is present in SnelStart.
Examples:
The purchase journal was given a different code in SnelStart.
The integration is configured for a journal that does not (yet) exist in this specific company file.
Solution:
Check if a purchase journal is present in SnelStart and verify that the name or code exactly matches the configuration within the BEX PMS integration.

This error message indicates that the provided cost center code is not recognized in SnelStart.
Cause:
The synchronization contains a cost center that has not been created or was created under a different name in SnelStart.
Examples:
A new cost center was created in the source system that does not yet exist in SnelStart.
A typo was made when entering the cost center in the source software.
Solution:
Create the cost center in SnelStart or correct the cost center name/code in the source software so that it exactly matches SnelStart.

This error message indicates that an attempt is being made to post an invoice with a number that is already present in the company file.
Cause:
SnelStart does not allow duplicate invoice numbers within the same journal (usually sales or purchase) to prevent errors.
Examples:
An invoice is submitted a second time due to a synchronization error.
An invoice with this number has already been entered manually in SnelStart.
Solution:
Check in SnelStart whether the invoice has already been processed correctly. If it concerns a new, unique invoice, adjust the invoice number in the source system.

This error message indicates that the chosen general ledger account has strict settings regarding cost centers.
Cause:
In SnelStart, the 'Cost center required' option is enabled for this specific general ledger account, but the integration is not sending a cost center.
Examples:
A posting is made to a car expenses account where a license plate (cost center) is mandatory.
The integration is not configured to pass along cost centers.
Solution:
Add a cost center to the entry in the source software, or turn off the cost center requirement in the settings of the general ledger account in SnelStart.

This error message indicates that the payment status of the relevant invoice has already been updated.
Cause:
The integration is trying to register a payment for an invoice that is already marked as 'paid' in SnelStart.
Examples:
The payment has already been processed manually via a bank statement in SnelStart.
The same payment transaction is offered twice by the integration.
Solution:
In principle, no action is required because the payment is already settled. You can ignore the error message.

This error message indicates that a cost center is being provided that is no longer allowed to be used.
Cause:
The cost center has been archived or set to inactive in SnelStart.
Example:
A project or department (cost center) has been completed and closed in SnelStart.
Solution:
Temporarily set the cost center back to active in SnelStart to process the entry, or adjust the entry in the source system to an active cost center.

This error message indicates that the VAT structure of the entry is logically incorrect for SnelStart.
Cause:
In a single entry line, both VAT to be received and VAT to be paid are specified, which is bookkeeping-wise not allowed on a single line.
Examples:
A complex VAT structure (such as reverse-charged VAT) is incorrectly formatted and passed from the software.
Solution:
Check the VAT settings in the integration. Ensure that debit and credit lines for VAT are strictly separated using the correct VAT codes.

This error message indicates that one of the invoice lines contains no financial value.
Cause:
SnelStart does not accept entry lines with an amount of exactly 0.00 euros via the API.
Examples:
There is an informative text line or a free product (0 euros) on the invoice.
Solution:
Ensure that zero-lines are filtered or not sent in the integration, or assign a value to the line (such as a discount processed in the main line).

This error message indicates that the XML/UBL file is corrupt or does not comply with the basic structure.
Cause:
The structure of the digital invoice file (UBL) contains syntax errors.
Example:
The file was cut off during generation or contains illegal characters.
Solution:
Regenerate the UBL invoice in the source system or contact the vendor of that software to check the UBL export.

This error message indicates that an empty file or empty data stream was sent.
Cause:
The integration is trying to provide a UBL invoice, but the actual content of the file is missing.
Example:
A glitch during upload caused a 0-byte file to be sent.
Solution:
Try to manually re-synchronize the relevant entry.

This error message indicates that the UBL invoice does contain data, but violates official UBL standard rules.
Cause:
Mandatory fields within the UBL standard (such as Chamber of Commerce number, VAT number, or specific country codes) are missing or in the wrong place.
Examples:
The country code is written in full ('Netherlands') instead of the mandatory two letters ('NL').
Solution:
Check whether all company and customer details (such as VAT and Chamber of Commerce/KVK) are fully filled out in the source system.

This error message indicates that the date of the invoice is too far in the past.
Cause:
SnelStart blocks transactions that are too old due to security and administrative guidelines.
Example:
A typo was accidentally made in the year of an invoice (e.g., 2012 instead of 2026).
Solution:
Correct the invoice date in the source system to the correct current date.

This error message is a general SnelStart processing error for UBL files.
Cause:
An unknown or unspecified error occurred in SnelStart's calculation module during importing.
Examples:
Temporary downtime or a timeout of the SnelStart API servers.
Solution:
Wait a brief moment and try to process the entry again.

This error message indicates that updating the stock level failed.
Cause:
The item is not correctly configured for inventory management or the inventory link is sending invalid quantities.
Example:
In SnelStart, 'Track inventory' is unchecked for the item, but the integration is attempting to change the stock level.
Solution:
Check the item settings in SnelStart and ensure that inventory management is enabled for this item.

This error message occurs when a manual or automatic stock adjustment cannot be processed.
Cause:
The company file does not allow negative stock, or the period in which the adjustment is being made is closed.
Example:
The integration indicates that 5 items are being deducted, while according to SnelStart only 2 are available and negative stock is blocked.
Solution:
Adjust the stock level manually in SnelStart or enable the option to allow negative stock.

This error message indicates that a project cannot be created from external project management software.
Cause:
The project code already exists, or mandatory project master data (such as a linked customer) is missing.
Example:
An attempt is made to create a project without a valid relation/customer linked to it.
Solution:
Check whether the customer of the project already exists in SnelStart and has been correctly synchronized.

This error message relates to the budgeting module within SnelStart projects.
Cause:
The budget format is incorrect or the project module is not active within your SnelStart license tier.
Example:
Your SnelStart package does not support comprehensive project budgets.
Solution:
Check your SnelStart license or check the budget rules in the source software.

This error message indicates that the chosen general ledger account does not match the type of entry.
Cause:
An attempt is being made to use a revenue account in the purchase journal, or a balance sheet account where this is not allowed. You cannot post a payment from a journal directly to the accounts receivable or accounts payable general ledger. An invoice must always be linked to it.
Example:
An attempt is being made to post (pre-invoiced) revenue directly to accounts receivable via a payment. Similarly, for accounts payable, you cannot post an outgoing payment directly to the purchase journal.
Solution:
Check the mapping of the general ledger accounts in the integration settings.
Check if entries are occurring directly on accounts receivable or accounts payable without a linked invoice.
Verify which general ledger accounts are being used in the entry and what their functions are. Compare the functions of the ledgers, for example, types like cash, bank, or suspense account.

This error message indicates that the calculated VAT amount does not match the chosen VAT code in SnelStart.
Cause:
The external software sends a VAT rate that does not match the percentage linked to that VAT code in SnelStart (e.g., sending 21% on a 9% code).
Example:
Rounding differences cause the VAT amount to deviate by a few cents from the SnelStart calculation.
Solution:
Check the VAT settings in both BEX PMS and SnelStart and ensure that percentages and codes run synchronously.

This error message relates to ICP (Intra-Community Supply) or foreign VAT rules.
Cause:
The customer is configured as a Dutch customer in SnelStart, but the integration is attempting to post revenue to a general ledger account reserved for countries within the EU (outside the Netherlands).
Example:
The customer's address is in Germany, but the country in the relation settings is still set to the Netherlands.
Solution:
Adjust the country setting of the customer in SnelStart or check the VAT rate determination in the integration.

This error message indicates that a VAT-free entry is being attempted where SnelStart requires a specification.
Cause:
No VAT code or type was provided in the entry request.
Example:
An export from a POS system only sends the total amount including VAT, without specifying the VAT type.
Solution:
Ensure that the linked software always explicitly passes a VAT code (such as high, low, or exempt).