<details class="details"><summary>BOE-001: Error opening the company file </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-002: Invalid login credentials </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0003: The ID is found but the relation is not a supplier </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0008: The general ledger account has been deleted and is inactive in the company file </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0009: The purchase journal has been deleted and is inactive in the company file </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0010: The purchase journal was not found </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0019: The cost center was not found </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0021: The invoice number already exists in SnelStart </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0022: A cost center is required for the specified general ledger account </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0025: This payment has already been processed </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0026: The cost center has been deleted and is inactive </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0027: The amount paid and amount received are both non-zero </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0028: A line amount is zero </summary><div data-type="detailsContent">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).</div></details><details class="details"><summary>BOE-0029: The format of the UBL is not valid </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0031: The UBL content cannot be empty </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0032: UBL does not comply with the schema </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0033: The booking date cannot be more than 5 years before the current fiscal year </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0035: A problem occurred while processing the UBL </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-018: Error creating a new stock transaction </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-019: Error processing a stock adjustment </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-020: Error creating a new project </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-021: Error processing a project budget </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0061 - An unauthorized general ledger account was used </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0069 - The specified VAT is not valid </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0080: For this customer, posting to an EU revenue account is not allowed </summary><div data-type="detailsContent">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.</div></details><details class="details"><summary>BOE-0082 - A VAT type is missing </summary><div data-type="detailsContent">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).</div></details>

Most error codes that come up in the SnelStart integration will start with "BOE". If the error that you are looking for is not in this list, contact either BEX or SnelStart support.

SnelStart error messages

Search for any helpful articles to find an answer to your question

www.bookingexperts.com

Updates

Developer Portal

Trust Center

Onboarding

What you need to know before starting the onboarding process

Before you start

Welcome to Booking Experts! Here you can find an overview of what happens next and how to start with your BEX PMS.

Starting with Booking Experts

Log in to your Booking Experts account in one of the following ways: with an email address and password with MFA, or via SSO through a Google or Microsoft account.

Log in to BEX PMS or CMS

The user role connected to your account determines how you interact with BEX PMS. You can be an employee working for a single or multi-park organization, an owner who rents out their accommodation, an executor or contractor who performs maintenance or provides services, or even a travel agency booking holidays for your clients. For BEX CMS, there is only one user role.

User roles within BEX PMS and CMS

The light green upper part of the menubar focuses on options regarding the account details, updates of Booking Experts, or reception messages.

Menubar in the BEX PMS

Every employee who uses the Booking Experts system has their own profile within the software. This is setup during onboarding or when a new colleague needs to be introduced to the system.

Adjusting your profile

Tools to help you in the onboarding process

Checklist and Academy

About the safety of your and your guests' data

Privacy and security

Modules

About data transferable from other systems

Importing data

Organization and administration settings

All organizations with multiple administrations have an Organization overview. In this overview, as an organization manager, you have insight into the bundled data of all administrations.

Overview for organizations with multiple administrations

What you need to know about setting up accounts for your employees

Employee settings

Brand and appearance

Central management of terms and conditions

Terms & Conditions

Domains

Setting up objects

Amenities

Individual objects and the types they belong to

Types and objects

Media content

Set up your pricing and business finances

Prices and finances

Important financial settings

Rental prices for various types and periods of time

Price lists

Costs

Setting up CMS

Switching between BEX PMS and BEX CMS

As a park manager, you can create CMS accounts for employees and manage their rights.

Access rights for CMS users

Tools

Site settings

Website pages

How reservations are made through your website

Search & Book

Brand appearance

Email campaigns

Offering holiday homes for sale on your website 

Sales module

If you are using both ParcVu and BEX CMS with the sales module, you can connect the two to easily generate prospects out of interested website visitors and advertise ParcVu Vans for sale on your website.

Connect to ParcVu

All day-to-day actions necessary at your reception

Daily use of PMS

Dashboard

Getting started with the reservations module and reception messages

Reservations and messages

BEX PMS

Planboard

The Planboard is the main tool for receptionists. From here, current and future reservations can easily be managed.

Managing reservations from the Planboard

You can scroll left and right to move through the dates in your planboard, but with these tips you might find what you are looking for easier and faster.

Calendar navigation in the planboard

Using the PMS planboard, you can easily move a reservation to a different object, or make two reservations switch places.

Move or swap a reservation in the Planboard

Select an available date range directly at the correct object by clicking and dragging, or first create a shortlist of objects using the filters at the top of your planboard.

Making a new reservation via Planboard

A cluster is a combination of multiple objects, which are treated as a single object in the Planboard.

Cluster reservation in the Planboard

The planboard legend explains the significance of colors, and through planboard settings you can determine what the planboard looks like for your account.

Planboard legend and settings

The planboard filters can be used to find certain reservations, or to narrow down the availability for a new reservation.

Available filters for the Planboard

Convenient keyboard shortcuts that may make your work easier.

Hotkeys for Planboard

Settings that apply to your entire organization

Organization settings

During onboarding, you connect or register your domain(s) to ensure that your BEX PMS works correctly. You might also add a new domain when opening a new park, for example.

Domains: settings for technical website management

It is possible to make predefined holidays and bank holidays visible on your website, so guests can click on them or more easily search for availability, for example, during the Christmas period. 

Set holidays as selectable on your website

For each administration separately, financial records can be locked and closed for accounting purposes. In your organization settings, you can prevent them from being reopened across your administrations.

Preventing closed financial records from being reopened

Special periods are used in statistics, price lists, and the Search & Book. Examples of special periods are the often-booked getaways around public holidays, local events or school holidays.

How are special periods used?

Special periods are arrival/departure date ranges that are important to your organization, and that can be applied throughout your administrations.

Creating special periods

A label alerts the user to important matters concerning the various modules and data within the PMS. For example, you could give the label 'loyal guest' to guests who have stayed for the fourth time, or the label 'renovated' to objects that have been refurbished. You can create these labels yourself and give them a desired colour and emoji.

Purpose of labels

Employees

Manage the amenities of your types, objects and administrations

Brands

Manage your booking portal and customer portal

Portal settings

Settings that apply within an administration

Administration settings

Description of the park and its surroundings

Exclude postcodes

Period groups are applied to costs, packages, auto emails and discounts, to determine when these items are valid, active, and/or applicable.

Period groups

Reservation settings

Manage channels through which reservations are made

Channel management

General invoicing and accounting settings

Financial settings

Everything about communicating with guests and owners

Communication

Translations

About types, objects, availability and meter readings

Setup

Whether or not a late checkout is allowed, is determined in the settings of the booked type. 

How to set up and recognize a late check-out

How do you indicate whether or not pets are allowed? This is done per object, in the object setup. In the type settings, you can set how many pets guests are allowed to bring, but this only applies if the booked object allows pets.

Pets allowed/not allowed

In the BEX PMS, you can add media to your types and objects so that guests can get a good impression of the kind of accommodation they are booking.

Add media to types and objects

How to make exports of your types, objects, or object setups.

Export of objects/types

In auto emails and templates, you can add useful information about an object or type that is predefined in the object or type settings.

Attachment text for emails objects/types

If you have a map of your park as a high-quality image, you can mark your objects on it and use it on your website to let guests select where they want to stay. This map will be shown during the booking process. If desired, you can attach a preference cost to this selection of an object.

Booking on the map

Types

Objects

Marking types and/or objects as not-available

Blocked periods

About tracking and charging for meter readings

Meter readings module

All about cost items, price lists, deposits and discounts

Pricing

Influencing revenue by controlling availability

Availability

Charge, claim, and refund security deposits

Security deposits

Cost items for anything that is not included in the rent price

Discounts

Packages

Bundle extras that are available independent of stay

Bundles

Finance

If you are a park working with owners, you need to file a DAC7 report. The BEX PMS can provide the necessary data. Read this article to find out which data is required and some of the common error messages concerning the data.

DAC7: What is it and which data is required?

Creating and checking a DAC7 report

To submit a DAC7 report to the Dutch Tax Administration, you likely use Digipoort. Our DAC7 Digipoort Connector app allows you to upload a DAC7 report directly from your PMS to Digipoort, the Tax Administration’s electronic post office.

Submitting a DAC7 report via Digipoort

Invoice management

Payment policies, bulk payments, payment methods, and more

Payments

About VAT, profit and loss, and ledger accounts

Accounting

Reservation management

View channel reservations

Overview nights stayed and tourist tax declaration

Within the reservations index page you can create a list for export using any of the tabs and filter options. Creating exports of reservations may help you anticipate your guest's needs.

Exporting reservations

Create an export file that lists which reservations have cancellation insurance.

Export for cancellation insurance

Open a booker contact page by clicking the name of a booker from the Contacts module. Here, collected personal, reservation, and invoice data for this contact is shown.

Booker contact management

The BEX PMS Booking portal overview provides a centralized list of all reservation attempts made through your Booking portal over the last 30 days.

Booking portal

There are multiple ways to enter a new reservation, and thus support your guests in booking a stay.

Making a new reservation

There are two ways to create group bookings in the BEX PMS back office, and which approach you should take depends on the requirements of your guests. In CMS, you can allow guests to make group bookings themselves via your website.

Creating a group booking

Reservation

Reviews

Vouchers represent a credit toward a reservation

Vouchers

Manage and assign the to-do lists for your administration

Todos module

Creating and editing various types of todos

Creating todos

Todo management

Invoicing todos

Executors

Contractors

A cash register for the direct sale of products

POS module

The POS module is used to be able to sell and receive payments for products. It is possible to receive payments via different payment methods. You can create multiple cash registers, which is useful if you have other points of sale besides the reception desk. Every day that you use the register, you have to open and close it. You use counts to log the amount of cash and identify any discrepancies.

Getting started with the POS module

You can create one or more registers. It is useful to create a separate register for each point of sale and to reflect this in the name. Once created, the registers must be opened for use.

Create and open a register

Add the products you want to sell to the POS module. These can be organised into product groups.

Add POS products and product groups

Because the price of a POS product is adjustable, it is possible to create a POS product for variable items. However, the linked VAT rate of a POS product cannot be adjusted.

POS product with variable price

Enabling the use of a barcode scanner can make selling items via the POS module much faster.

Using a POS barcode scanner

Register sales can be paid in different ways. Cash is a default method, and you probably have a PIN terminal, or maybe you also want to be able to accept vouchers as a payment method.