clate®

Navigation

Good things need room to grow.

WooCommerce and e-Boekhouden.nl

WooCommerce orders into e-Boekhouden.nl: what moves and what to check

This guide is for e-commerce managers and bookkeepers who want paid WooCommerce orders booked in e-Boekhouden.nl. After reading, you will know which parts of an order reach the books, which orders stop for a person to check, what to prepare in e-Boekhouden.nl, and how to test before anything is written. Integrator by CLATE, which is in beta, is the example throughout.

Book entries, not a second invoice

e-Boekhouden.nl can do two different things with an order. It can create an invoice in its invoicing module, with its own number series and layout, and it can email that invoice to the customer. It can also book an entry in the ledger. Your webshop has already invoiced the customer, so an invoice from the invoicing module would be a second one.

Integrator books each paid WooCommerce order as a sales entry of the type invoice sent, on your debtors ledger. It makes no invoices in the invoicing module and emails nothing to your customers. If you connect the two systems another way, settle this choice first, because it shapes everything else.

The connection is in beta. Review the mapping and a dry run on your own orders before turning it on, then check the first entries with the person responsible for your books.

What moves for each order

Integrator looks for orders every 15 minutes, and when you press Run now. One record is one order. From WooCommerce it reads the order number, customer, email, billing country, line items, VAT per line, shipping, discounts, refunds, totals and payment status. Changes made in the last minute are read on the next run.

Sending an order again does not create a duplicate. There is one sales entry per order, one credit entry per refund and one payment per entry, also when you replay. Integrator does not delete or change entries that already exist in e-Boekhouden.nl.

  • The order: one sales entry with the relation, invoice number, date and one row per order line on your revenue ledger, each row with its own VAT code. The invoice number is the order reference from the mapping, by default in the form Webshop order #1043.
  • VAT: lines at 21% and 9% get the matching Dutch sales VAT codes. For lines at 0% you choose the code in the settings: no VAT by default, or an EU or export code. e-Boekhouden.nl calculates VAT per row, so its total can differ a cent or two from the webshop. The check before booking allows a few cents and does not try to correct e-Boekhouden's rounding.
  • Discounts: a discount on a line is taken off that row's amount, so it stays at the VAT rate of that product.
  • Shipping: each shipping line becomes its own row at its own VAT rate.
  • Payment: when booking payments is on, a paid order also gets a payment (invoice payment received) on the payment ledger you choose, with the same invoice number.
  • Refunds: a refund becomes a credit entry with negative rows, and the order reference plus the word refund and an id as its invoice number. A negative payment is booked on the payment ledger. A refund made after the order was booked is credited on the next run, once.
  • The customer: the order goes to an existing relation with exactly the customer's email address. If there is none, one new relation is created: a business relation when the order has a company name, otherwise a private person. You can also book every order to one fixed relation.

What does not move, or stops for review

Some details do not reach e-Boekhouden.nl by design. e-Boekhouden keeps one description per entry, the order reference, and replaces the text of each row with it. The rows keep their ledger, VAT code and amount, while product names and line details stay in WooCommerce. Lines are booked as free rows, not against products in e-Boekhouden.

Changes to an order after it was booked are not followed, except refunds. If you edit an order by hand later, correct the booking yourself.

Other orders stop so a person can decide what to do. A stopped order does not hold up the others. These are the cases that stop:

  • A line at a VAT rate other than 21%, 9% or 0%, for example the VAT rate of another EU country.
  • An order with fees, compound taxes, or more than one tax rate on one line.
  • A refund that returns an amount that cannot be tied to one VAT rate. This one is for you to book by hand.
  • An order whose lines, shipping and discounts do not add up to what the customer paid, often because of a gift card or a change made by hand in the webshop.
  • An order where the VAT codes would give a different VAT amount than the order shows.
  • A customer email that belongs to more than one relation in e-Boekhouden.nl.
  • An order or refund dated in a period that has been closed, for example by your accountant.
  • An order that changed while it was being read.
  • A sales entry that was removed in e-Boekhouden.nl after it was booked, or an invoice number that already exists under another relation.

Prepare e-Boekhouden.nl and WooCommerce

Integrator supports Dutch administrations. Belgian administrations use different VAT codes and are out of scope. One connection opens one administration.

Look up the ledger codes you need in your chart of accounts under Beheer, Grootboekrekeningen before you start. Ledgers are checked for the right category before anything is written, so a wrong code stops orders rather than booking them in the wrong place.

  • API token: in e-Boekhouden.nl open Beheer, Inrichting, Koppelingen, then e-Boekhouden API (not API/SOAP), and add a token. Give it a name you will recognise and a validity of at least a year. Copy it right away: e-Boekhouden shows it once. The token opens the administration it was made in.
  • Revenue ledger: required. Use the code of a revenue account, a profit and loss account.
  • Debtors ledger: fill in the code of the debtors account (category Debiteuren) when your administration has more than one.
  • Payment ledger: if you want payments booked, choose a bank, cash or payment provider account (category Liquide middelen). Or turn off booking payments.
  • VAT code for 0% lines: no VAT, or an EU or export code, depending on what those lines are.
  • Relations: merge relations that share one email address. If you book everything to one fixed relation, give it a code of its own.
  • Periods: make sure the periods you will book in are open.
  • Subscription: if the administration is on a free trial of the accounting module, orders stop once its entry limit is reached.
  • Invoice number: e-Boekhouden.nl limits its length, and refunds add text to it. Keep the rule short, for example the order number alone.
  • WooCommerce: version 8 or later, on an https:// address, with Settings, Permalinks in WordPress set to anything other than Plain.
  • WooCommerce API key: under WooCommerce, Settings, Advanced, REST API, add a key for an administrator or shop manager, with Read permission. Copy the consumer key and secret: the secret is shown once. Orders are only read.

Test with a dry run before turning it on

A dry run reads up to 20 recent orders with real data and shows, for each one, what would be written to e-Boekhouden.nl: a new entry, or one it already has. It writes nothing and opens no problems.

Integrator does not delete entries, so anything it books stays in e-Boekhouden.nl until you remove it yourself. That makes the dry run the place to find mistakes. Go through it with your bookkeeper and check at least these cases:

  • An order with only 21% products: one row per line on the revenue ledger, each with the 21% code.
  • An order with 9% and 21% products, a discount and shipping: the discount sits on the right row and shipping has its own row with its own VAT rate.
  • A refunded order: a credit entry with negative rows and a matching negative payment.
  • A business customer and a returning customer: each goes to the relation you expect.
  • An order with a fee, if your shop uses them: it should stop for review rather than be booked.
  • The invoice number: easy to find in e-Boekhouden.nl and not too long once a refund is added.
  • Payment ledger: payments land on the account where your bank or payment provider settles them.

When an order stops

Open the order's record. Each record shows when it was found, how it was prepared and what e-Boekhouden.nl answered. The explanation names the cause and the fix, in wording the CLATE team wrote and approved. An error without an approved explanation is shown as not yet explained; nothing is guessed.

Fix the cause, then send the order again; it will not create a duplicate. When an order cannot be booked safely, such as one with another EU country's VAT rate or totals that do not add up, book it by hand in e-Boekhouden.nl and mark the problem as solved. If every order stops as needing review, ask your Integrator administrator to check the setup.

If e-Boekhouden.nl or WooCommerce refuses the login itself, the run stops until you reconnect the app. Other problems stop only the order concerned. Common causes and fixes:

  • Period closed: ask your accountant to reopen it, or book the order by hand in an open period, then mark the problem as solved.
  • Several relations share the email: merge them in e-Boekhouden.nl, or book every order to one relation in the settings, then try again.
  • Invoice number too long: shorten the invoice number rule, for example to the order number alone, then try again.
  • e-Boekhouden.nl does not accept the token: it was revoked, expired, or made for the old SOAP API. Create a new token under e-Boekhouden API and reconnect.
  • WooCommerce does not accept the key: it was deleted or revoked, belongs to another shop, or your web host removes the login header. Add a new Read key; if that fails too, ask your host to pass the Authorization header to WordPress.
  • e-Boekhouden.nl asks to slow down: Integrator tries again automatically. If it keeps happening, check which other apps use your administration.
  • Free trial full: upgrade the e-Boekhouden.nl subscription, then try these orders again.