1.Introduction
This is the manual for the integration between Woocommerce and e-Boekhouden.
- This integration is a financial integration. It is not a logistics integration. It is not suitable for updating customers in e-Boekhouden, printing packing slips, or synchronizing products/inventory.
- This integration does not replace the work of an accountant. It saves time because you no longer have to retype documents. The accountant is still needed for advice, expertise, and control.
- We do our utmost to keep the manuals up to date. No rights can be derived from the content of this manual. We appreciate customer feedback to further improve the manuals.
- Tip: Other customers using this integration found the tips in the FAQ for Woocommerce and in the FAQ for e-Boekhouden.
Installing the integration starts with signing up for a trial period, via our integrations page. After registering, you'll receive an email containing an installation URL and login details. Use this installation URL to start the integration setup. Installation is complete when both dots for the connection are green and the settings in the Configuration tab have been entered and saved.
There is a 30-day trial period. If you want to install another integration, you can do so in the same way. Make sure you are logged out of the integration dashboard and preferably start the new installation in an incognito browser.
At the end of the trial or subscription period, the integration will not be automatically renewed. You will receive an offer for a one-year subscription or renewal by email at the end of this period. You can confirm the renewal by using the payment link in that email. Do you want to terminate the integration in the meantime? This can be done via the dashboard, tab Profile>>Cancel integration.
Are you switching to another web shop/accounting system and do you want to re-establish a connection? In this faq we explain how to do this.
When uninstalling the integration, we recommend revoking the consumerkey and consumersecret in WooCommerce.
2.How the integration works
New orders from your online store are retrieved at least once per hour. If webhooks are enabled in the Woocommerce webshop, orders are retrieved in real time. In addition, any previously retrieved orders that have not yet been sent to your accounting system are checked every night. For more details see the FAQ.
Read more How the integration works .... Read less How the integration works ....
At the start of processing a order we perform a number of checks on the Woocommerce order:
- It is checked whether the total of the Woocommerce order is equal to the sum of the amounts in the order lines plus the shipping amount.
- If the order is an ICP order, the VAT number is checked.
- It is checked whether a corresponding VAT code exists in e-Boekhouden for the VAT in each line.
- It is checked whether the order has not already been processed.
A payment is processed for every order that has been processed to e-Boekhouden and that has been paid in Woocommerce. It is possible to always process the payment, regardless of the status in Woocommerce. This can be requested via webcare@webwinkelfacturen.nl.
Processing a Woocommerce order to e-Boekhouden takes place in three steps:
- The integration first checks if the debtor is already present in the accounting system. If not, the integration creates the debtor in e-Boekhouden. For a new debtor, we must provide a Code field. This becomes the debtor number in e-Boekhouden. We use the same logic here as e-Boekhouden. Matching of debtors between Woocommerce and e-Boekhouden is based on email address.
- Products With the invoices option, the integration uses the SKU in the invoice lines. If this product is not present in e-Boekhouden, e-Boekhouden will reject the invoice or post it to a random product. Unfortunately, the integration cannot create new products in e-Boekhouden.
- The e-Boekhouden transaction (mutation, invoice) is created and processed.
When processing payments, the integration retrieves the mutation from e-Boekhouden that was created based on the related sale. The integration checks if this mutation is still outstanding. If so, the integration creates the payment mutation.
After the order has been forwarded and a success message from e-Boekhouden has been received, the order is marked as completed. The Woocommerce order appears in the Report tab on the dashboard. If e-Boekhouden returns an error while processing the order, the order appears in the Errors tab on the dashboard. Via the yellow button More info more information about the problem can be found. Via the red button Report problem can the order with all necessary information easily be submitted to us after you have tried to resolve the problem yourself. If the problem is solved, in some cases the orders can be processed again with the blue Process button.
When forwarding the payment, the payment is also registered so that it cannot be processed again. Payments can also be reviewed via the dashboard.
Data
Information about the data that is processed can be found in the section Day-to-day: To e-Boekhouden later in the manual.
3.Required: e-Boekhouden codes
Registrations from March 14, 2025
To establish the integration with e-Boekhouden, you need an API token. You can find this API token via Administration > Connections > API > e-Boekhouden API > Next. We recommend entering a clear name and an end date one year in the future. Please note that after this end date, you will need to re-establish the connection with the integration.
Registrations before March 14, 2025
To establish the integration with e-Boekhouden.nl, special codes are required. These are:
- username
- Security code 1
- Security code 2
4.Required: WooCommerce keys
The last paragraph of this chapter "WooCommerce Keys" is only necessary if you want to push real-time orders in addition to the regular batch. If you skip this subsection, your orders from WooCommerce will still be transferred regularly and automatically at the batch level after installing the connection in the next chapter.
To create the webhook, click on the "Webhooks" tab within the "Advanced" main tab and then on the "Add webhook" button.
In the screen that has now opened, fill in the requested information. Provide a clear description for the name of the webhook. The Status must be "active". In the third field, enter when the webhook is activated. We recommend choosing "Order updated" (Dutch "Order gewijzigd") here.
At “Delivery URL" enter: https://interface.cloudinvoice.company/api/v1/servlet/woocommerce/webhook.php?licensekey=UWLICENTIESLEUTEL
where "UWLICENTIESLEUTEL" is of course your own specific webwinkelfacturen.nl license key that you received in your email confirmation of the connection (a 32-character letter/number combination). For the secret, enter the WooCommerce consumer secret as generated at the beginning of this paragraph. Finally, you must save the configuration (save webhook).
Indien je later ooit de Webhooks zou willen de-activeren, ga je binnen "Advanced” tab naar subtab "Webhooks" en kiest voor die specifieke webhook "delete permanently”.
5.Installation
Installing the integration starts with signing up for a trial period, via our integrations page. After registering, you'll receive an email with an installation URL and login details. Use this installation URL to start the integration installation.
Activating the integration consists of three steps:
1. Establishing the connection with the WooCommerce webshop. In this step you authorize the integration to read data from your webshop.
2. Establishing the connection with e-Boekhouden. This authorizes the integration to write transactions to your e-Boekhouden administration and read information.
3. The configuration itself.
The connection with the Woocommerce webshop is established using the Clientkey and Clientsecret that you created in a previous section. Click the red Connect button next to Woocommerce and enter the Clientkey and Clientsecret in the popup window. If the connection is established correctly the indicator will turn green. If the connection is not established then this is the FAQ for troubleshooting.
e-Boekhouden Authentication
The red dot and the red Connect button for e-Boekhouden on the Configuration screen indicate that the connection with e-Boekhouden is not yet valid. To activate the connection, click the red Connect button. You will then see a screen containing fields for a username and two security codes. Here, you enter the username and the two security codes you determined in the previous section.
You can specify which statuses orders should be processed to e-Boekhouden. You can select multiple statuses. The integration will never forward orders twice. The integration is protected against this.
For e-Boekhouden invoices, an invoice template must be provided. Unfortunately, the integration cannot retrieve the invoice templates in the e-Boekhouden administration. Therefore, the integration uses the name 'Invoice template' as default. If you want to use a different invoice template, you can enter the name of the template when clicking Edit.
When configuring the VAT rates and general ledger accounts, a link is created between the VAT rates in webshop and the VAT codes and revenue accounts in e-Boekhouden. You can always make changes by clicking the blue 'Edit' button and selecting an option from the drop-down menus.
Intra-Community (ICP) and international deliveries
The Intra-Community supplies / ICP option is intended for business-to-business deliveries within the EU. These sales are invoiced with 0% VAT. A VAT number from the customer is required. The International option applies to deliveries outside the EU. For these sales, the integration expects 0% VAT; otherwise, the sales cannot be processed. Separate VAT codes and general ledger accounts can be configured for both ICP and international deliveries.
OSS settings
If you are dealing with OSS - new regulations as of July 1, 2021 - it can be configured as follows.
If you use the NL VAT rates, the following remains applicable:
- in the column VAT Code the VAT code with the relevant percentage
- in the column revenue account a revenue account for the net revenue, the payment and shipping costs
- the VAT account column has no function in this case
If you calculate with VAT percentages of the country of delivery in the webshop, please fill in the following:
Per EU country, except NL
- in the column VAT code the VAT code VAT_OSS
- in the VAT account column, a Balance Sheet account for the VAT to be paid in the respective country
- in the column revenue account a revenue account for the net revenue, the payment and shipping costs
Only when using VAT code VAT_OSS, the entry will take place based on the configured VAT account in the Configuration. For other codes, the VAT account is determined in e-boekhouden based on the code.
Once the VAT settings have been configured and saved, you will always see the selected VAT rates. If you want to start over, you can use the grey 'Remove VAT settings' button. Your current settings will then be deleted and you can begin again.
You can create a link here between the payment methods in the webshop and a fixed debtor in your e-Boekhouden administration. Orders with a payment method from the list will then always be posted to this debtor. In that case, no new debtors will be created.
Note: It is not possible to set fixed debtors for ICP orders. For an ICP order, a valid VAT number must be transmitted. Therefore, a debtor will always be created in e-Boekhouden for an ICP order.
This option is only available when processing to Invoices.
When processing payments, a suspense account of type Payment Methods is configured in e-Boekhouden. When setting up the suspense accounts, there is no option to post to fixed debtors per payment method.
It is possible to process revenue based on product categories. You can configure the general ledger accounts here. We recommend a maximum of 40 categories, and there is a technical maximum of 99 categories. When accounts are configured at the category level, they take precedence. The revenue accounts set under the VAT rates will no longer apply.
6.Day-to-day: From WooCommerce
In this section, we show how we retrieve the orders from Woocommerce
Once an order has been processed, it cannot be processed again. Any order changed in the webshop after it has been processed will not be updated in e-Boekhouden.
Payments (if activated):
When processing payments, the integration checks every day the Woocommerce orders that have been successfully forwarded to e-Boekhouden. If the order has been forwarded and the status of the order in Woocommerce is paid, then a payment will be created in e-Boekhouden for this order. If desired, payments can always be created — regardless of the status of the order in Woocommerce. Send an email to webcare@webwinkelfacturen.nl to request this.
Orders that are picked up and have a status other than one of the selected options will automatically be transferred the following night if they have one of the selected options in WooCommerce.
* Technical: This concerns the fields [total], [total_tax], [subtotal], [subtotal_tax] and [taxes] per order line in [line_items].
- The fields [total] and [total_tax] contain the line amount excluding VAT and the VAT amount after discount, in two decimals
- The fields [subtotal] and [subtotal_tax] contain the line amount excluding VAT and the VAT amount before discount, in two decimals.
- The [taxes] field contains the same amounts but with four decimals. The integration uses the values in [taxes] for the VAT calculation.
Please note: The integration looks back 30 days to retrieve refunds. Refunds that come in later cannot be processed by the integration. The integration only processes a refund if it has previously processed the order to which the refund relates. Finally, the integration only processes full refunds . Partial refunds are not processed. For more information see the FAQ
Pay special attention to fields that come from plugins. There is a good chance that the integration does not process these fields. For example, with discount plugins the amounts may not be correctly included in the order, preventing the order from being processed.
Field-level specification orders
| Name field | Values from Woocommerce order |
| Order-identifier | [id] |
| Order number | A fixed prefix followed by field [number]. The prefix configuration can be requested via webcare@webwinkelfacturen.nl |
| Invoice number | Determined from the [meta_data]. The following fields are examined in turn. The first one present is returned.
|
| Booking date | [date_created] |
| Order date | [date_created] |
| Status order | [status] |
| Payment status | If the status of the order is completed or processed or if [date_paid] has been entered then paid |
| Payment reference | [id] |
| Note | [customer_note] |
| Is it a Bol.com order? | The answer is yes if there is a field [customer_user_agent] with the value effectconnect and the field [billing][email] is a bol.com email address |
| Is it a Fonq order? | The answer is yes if it is not a Bol.com order and there is a field [customer_user_agent] with the value effectconnect |
| Is it another order coming through an external party? | The answer is yes if the key is part of a fixed set of keys. This list can be expanded upon request. |
| Affiliate number |
The affiliate number is determined as follows:
|
| Valuta | If the currency option is set for the customer then [currency] |
| Payment method | field [gateway] in [transactions] |
| Order total incl. VAT and discounts | [total_price] |
| Total VAT order incl. discounts | Value in [total_tax], or, if that value is 0, the value from [current_total_tax]. When using [current_total_tax], there's an additional check. The VAT lines in the order must add up to the value in [current_total_tax]. |
| Order total excl. VAT and discounts | Difference between the two lines above |
| Delivery country | The delivery country will be the [shipping][country] field if it is filled in. Otherwise, the [billing][country] field will be used. |
| ICP indication | The integration determines as follows whether it concerns an ICP order:
|
| International indication | The integration determines as follows whether it concerns an international order:
|
| Do the order lines have VAT? | To determine whether VAT is applied to order lines, the [subtotal_tax] and [total_tax] fields are examined per line, and the [shipping_tax] fields are examined in the order itself. If any of these fields have a value other than 0, VAT is applied to the order lines. If all fields have a value of 0, there is no VAT on the order lines. |
| To read the order lines, the integration retrieves the [line_items] field. Multiple order lines can be included in the order, and the integration reads these lines one by one. | ||
| Name field | Values from Woocommerce order line | |
| Productid | [product_id] | |
| Category | In the case of processing categories, the category ID and name | |
| Amount | [quantity]. Note: if the quantity is 0, parsing stops. | |
| SKU | If the SKU is filled, then [sku]. Otherwise [product_id]. | |
| Description | [name] plus the values ​​in field [meta] in the order line with key / key label or key | |
| VAT percentage |
The VAT percentage is determined as follows:
|
|
| Amounts excl. VAT | Amount in field [total] | |
| Amounts incl. VAT | Amount in field [total] plus the amount in field [total_tax] | |
| Discount in order line | An order line has two totals: [total] and [subtotal]. The [total] amount is the line amount including the discount, and the [subtotal] amount is the amount excluding the discount. Discounts are therefore processed directly in the order line and not added as separate lines. | |
| VAT code and accounts e-Boekhouden | These are determined based on the settings, the VAT percentage and the delivery country. It also takes into account whether the order is an ICP or international order. If processing is done based on categories, the revenue account is determined using the revenue account configured for the respective category in the dashboard | |
| To read the shipping costs, the integration uses the field [shipping_lines]. There can be multiple shipping lines. For the name and VAT percentage only the first line is used, while the amounts from all shipping lines are summed. In most cases there will be only one shipping cost line. | ||
| Name field | Values from Woocommerce order line | |
| Description | [method_title] from the last shipping cost line | |
| VAT amount shipping costs | Each line in the [shipping_lines] field can contain multiple VAT lines in the [taxes] field. These are summed and the total is the VAT amount for shipping costs. | |
| Shipping costs excl VAT | [shipping_total] in the order | |
| Shipping costs incl VAT | Shipping costs excl. VAT plus the VAT amount for the shipping costs. | |
| VAT percentage | VAT amount for shipping costs divided by the shipping cost amount excl. VAT | |
| VAT code and accounts e-Boekhouden | These are determined based on the settings, the VAT percentage and the delivery country. It also takes into account whether it is an ICP or international order. | |
| The surcharges are stored in the [fee_lines] field. Each surcharge becomes a separate line in the order. | ||
| Name field | Values from Woocommerce order line | |
| Description | [name] | |
| VAT amount | If it is an international or ICP order then 0, otherwise the amount in the [total_tax] field. | |
| Amount excl VAT | [total] in the order | |
| Amount incl VAT | Amount excl. VAT plus VAT amount | |
| VAT percentage | VAT amount of the surcharge divided by the amount excl. VAT | |
| VAT code and accounts e-Boekhouden | These are determined based on the settings, the VAT percentage and the delivery country. It also takes into account whether it is an ICP or international order. | |
| Name field | Values from Woocommerce customer |
| The billing address is in field[billing] and the shipping address in field [shipping]. The content of these fields is always the same, so we do not describe them separately. | |
| Address |
If present based on [billing_address] in the Woocommerce order
|
| VAT number | The VAT number may be present in the [meta_data] of the order. There is a fixed list of keys that are searched. If the VAT number is not found, the integration continues searching in the [vat_number] and VIES data fields in the order. A VAT number is always validated. |
| The option to forward payments to e-Boekhouden in addition to orders can be requested via webcare@webwinkelfacturen.nl. This option has additional costs. The payment is created if the field [date_paid] is filled. | |
| Name field | Values from Woocommerce order |
| Order id | The field [id] from the order |
| Payment id | The field [payment_method]]#[transaction_id] from the order |
| The paid amount | The field [total] from the order |
| Payment method | [payment_method_title] |
| Status | [status] |
| Transaction-id | Retrieved from the [meta_date] key, [_mollie_payment_id] key. If this field is not found, the [transaction_id] field from the order is used.|
| Payment date | [date_paid] |
7.Day-to-day: To e-Boekhouden
Creating invoices / sales transactions
The orders from Woocommerce are imported into e-Boekhouden as mutations or invoices. For each order, the VAT and ledger account are provided as configured during the installation of the integration.
When creating an OSS invoice or mutation in e-Boekhouden, for each line in the Woocommerce order two lines appear in the e-Boekhouden mutation / invoice. The first line in the e-Boekhouden mutation / invoice contains the amount excl VAT and the second line the VAT amount. The first line is posted to a revenue account, the second line to a VAT account. The revenue and VAT accounts can be configured via the Configuration tab of the dashboard.
When creating invoices or mutations, descriptions and invoice numbers can be adjusted. Below are the options for creating invoices and mutations in e-Boekhouden. When creating invoices, new debtors may be added to e-Boekhouden.
Please note: When creating mutations, the integration provides a sales number. If a mutation with that number already exists, the existing mutation will be overwritten. Therefore, always ensure that sales numbers are unique, especially if you have multiple integrations feeding into a single e-Boekhouden account.
If your integration was installed after March 14, 2025, and the integration processes to Invoices, these are invoices without a corresponding mutation. We can change this to Invoices with a corresponding mutation. In that case, the invoice can no longer be modified in e-Boekhouden.
Creating new debtors
When creating a mutation or invoice in e-Boekhouden, the code of the relation in e-Boekhouden is used. The integration first checks if the debtor is already present in e-Boekhouden. If so, the integration will use the relation code of this existing e-Boekhouden debtor. If not, the integration creates the debtor in e-Boekhouden.
The integration creates a RelationCode for the new e-Boekhouden debtor. The procedure is the same as if you were to create the mutation or invoice in e-Boekhouden yourself. The method performed by the integration is:
1. Determine the company name and the name of the debtor. For the debtor's name, the first name is appended to the last name.
2. Determine whether the company name or personal name of the debtor is used as the base name. If the company name is present, this becomes the base name. Otherwise, the first plus last name.
3. Take at most the first 10 characters of the base name
4. Determine if the base name occurs more than once in e-Boekhouden. If so, it will have one or more sequence numbers. Determine the first available sequence number and append this to the base name.
Example: If the company name is empty and the name is Klaartje Pietersen, the base name becomes KlaartjePietersen. We take the first 10 characters of this. This results in KlaartjePi. If this already occurs 5 times and the highest is KlaartjePi4, the debtor code becomes KlaartjePi5.
Matching between and e-Boekhouden for debtors is based on the email address.
Please note: The integration will never modify debtors in e-Boekhouden. The email address field is used for matching debtors. For integrations started before October 28, 2023, that process to e-Boekhouden mutations, we provide the debtor data within the mutation, and e-Boekhouden determines the debtor code itself.
Create products
Unfortunately, the integration cannot create new products in e-Boekhouden through the e-Boekhouden connection possibilities.
Creating payment transactions
Payments from Woocommerce are imported into e-Boekhouden as mutations. For each payment, the financial account is provided as configured in the integration settings. If you want to change this account, you can easily do so via the Configuration tab of the dashboard.
To process a payment, the integration attempts to find the corresponding item in e-Boekhouden.
Since the sale has also been processed under the same key, the integration will attempt to find the mutation for the processed sale.
Processing without outstanding item
It is possible to process payments for which there is no outstanding item to e-Boekhouden. To do this, we need to adjust a contract setting. It is certainly not the best method, so we advise using this sparingly or not at all. Please note: There are two things to keep in mind when processing payments to e-Boekhouden:
- There is a technical limit to the number of outstanding items the integration can retrieve. We cannot say exactly where that limit lies, but a few hundred outstanding items is very many.
- e-Boekhouden has its own reconciliation option. This means that if payments come in through the bank book, for example, and the debtor and order number match, e-Boekhouden automatically matches that payment to the sales mutation. e-Boekhouden does not take the outstanding amount into account because there may also be partial payments. Always ensure that the order numbers of the mutations are unique.
Specification field level creating e-Boekhouden
| Name | Example | Note |
| Invoice number | 3908 | This is optional; we recommend letting e-Boekhouden determine the invoice numbers itself. Then they are guaranteed to be unique and sequential. If you still want to provide the invoice number, the Woocommerce order number, on request invoice number can be used for this. |
| Relation code | 2023031416200123 | The RelationCode of the debtor in e-Boekhouden. It is possible that the debtor was added to e-Boekhouden by the integration in a previous step. |
| Date | 2023-01-11 | Order date |
| Payment term | 14 | |
| Accounting mutation description | ORD145 - mollie | Order number - payment method (if present) |
| DirectDebit | false | Cannot be adjusted |
| Invoice template | Invoice template | The name of the invoice profile, default Invoice template. If you cannot set the invoice profile in the Configuration tab, you can provide the name to us, and we will set it. |
| Products | The article codes of the products in e-Boekhouden. It is possible that the integration created products in e-Boekhouden for this in a previous step. | |
| PostInAccounting | true | Cannot be adjusted |
| Lines | ||
| Amount | 1 | |
| Code | 6940478067395 | Product code in e-Boekhouden |
| Description | 2-week extension | The description in the line |
| PricePerUnit | 8.22 | Unit price excl. VAT |
| VATCode | HIGH_SALES_21 | As configured via the dashboard |
| OffsetAccountCode | 8000 | As configured via the dashboard |
| CostCenterID | 0 | This is never provided |
| Name | Example | Note |
| TYPE | 2 | Invoice payment received, this cannot be adjusted. |
| ACCOUNT | 1300 |
Usually 1300, but can be adjusted on request. Account configured for the payment method - this is a financial account in e-Boekhouden. |
| DESCRIPTION | ORD235 | Payment payment method - sales number in payment. |
| INVOICE | ORD235 | sales number in payment |
| PAYMENT REFERENCE | ORD235 | order number, on request invoice number |
| DATE | 01-01-2023 | |
| INEX | EX | |
| RelationCode | Debtor from the Open Items list at the sales mutation | |
| Lines | ||
| AMOUNTEXCL | 99.09 | Amount ex VAT |
| AMOUNTINCL | 119.90 | Amount incl. VAT |
| VATAMOUNT | 20.81 | VAT amount |
| VATPERC | HIGH_SALES_21 | As set on the dashboard |
| OFFSET ACCOUNT | 8000 | As set on the dashboard |
| Name | Example | Note |
| MutationNo | Empty | e-Boekhouden determines this number automatically. This cannot be adjusted. |
| Type | InvoicePaymentReceived | This cannot be adjusted. |
| Relation code | Relation debtor in e-Boekhouden | |
| Date | 2023-10-02 | Sales date |
| Description | iDEAL - 123 - trx_qwer | Payment method - mutation number - transaction_id |
| Invoice number | 90282 | Invoice number |
| Entry document | tr_qwer | transaction ID payment |
| Payment term | 14 | Not editable |
| InExVAT | IN | Not editable |
| Line |
|
8.Support
Read more Support .... Read less Support ....
Explanation tabs dashboard
On the Dashboard >> Report you can see which orders from your Woocommerce webshop, and when, have been transferred to e-Boekhouden.What if orders are missing in e-Boekhouden
If orders are missing in e-Boekhouden we recommend following the steps below:- Log in to the dashboard: https://uwkoppeling.webwinkelfacturen.nl. The username and password are included in the registration email.
- Go to the Errors tab and check if order is there. You may need to adjust the search period if the
order is from a previous month. If you find order in this overview:
- Check the error code and verify whether you can resolve it yourself.
- If yes resolve the issue and click the blue Process button to resubmit the order.
- If not use the red Report problem button to create a ticket with us.
- Note if there are multiple errors, please create only 1 or 2 tickets. We will automatically see the other issues.
- Go to the Report tab and see if order is listed there. If so, you'll often see an identifier for e-Boekhouden (in the purple section of the overview) that you can use to search for order.
- Go to the Open tab and check if order is there.
- If you cannot resolve the issue, you can always create a ticket via the green Ask us button.