Sales entries, not a second invoice
e-Boekhouden.nl has two places where a sale can land. The invoicing module creates a new invoice with its own number and layout, and can email it to the customer. A sales entry is a booking in the ledger: it records that an invoice was sent, on your debtors ledger (the account that tracks what customers owe you). Shopify has already invoiced your customer, so a sales entry records the sale without making a second invoice.
Integrator books paid Shopify orders as sales entries. It makes no invoices in the invoicing module and emails nothing to your customers. One Shopify order becomes one sales entry, with the order reference as its invoice number. The integration runs every 15 minutes, and when you press Run now.
This integration is in beta. Check a dry run on your own orders before turning it on, then review the first entries with the person responsible for your books.
What moves from each order
Each entry needs a relation, e-Boekhouden's word for a customer record. Integrator looks for an existing relation with exactly the customer's email address. If there is none, it creates one: a business relation with the company as name and the person as contact when the order has a company, otherwise a private relation. You can also choose to book every order to one fixed relation.
Each order line becomes a row on the revenue ledger you choose, with the VAT code for that line's rate. Integrator supports Dutch administrations and the rates 21%, 9% and 0%. For 0% lines you choose the code, for example no VAT, or an EU or export code. e-Boekhouden calculates the VAT per row from the code and rounds per row, so its total can differ by a cent from Shopify's. Integrator accepts a difference of a few cents and does not try to correct e-Boekhouden's rounding.
A discount on a line is taken off that row's amount. Each shipping line gets its own row at its own VAT rate. This is what lets an order with both 9% and 21% products be booked correctly. The default mapping provides the VAT rate, discount and shipping per line; if a mapping lacks them, orders with more than one VAT rate stop instead.
e-Boekhouden keeps one description per entry: the order reference. The text of each line, such as the product name and its discount, does not reach the books. The rows keep ledger, VAT code and amount, and the line details stay in Shopify. Rows are booked as free rows, not against products in e-Boekhouden.
When payment booking is on, a paid order also gets a payment, booked as invoice payment received with the same invoice number. It goes to the payment ledger you choose: a bank account, a cash account or your payment provider's clearing account. If you already settle customer payments another way, for example from your bank import, you can turn payment booking off.
A refund becomes a credit entry: negative rows for the refunded items and shipping, each with its VAT code, and an invoice number made of the order reference plus the word refund and an id. A negative payment is booked on the payment ledger as well. A refund made after the order was booked is credited on the next run, once. There is one sales entry per order, one credit entry per refund and one payment per entry, also when an order is sent again, and existing entries are not changed or deleted.
What does not move, or stops for review
Some orders cannot be booked without a person deciding. Integrator stops these with an explanation and carries on with the rest. The list below shows what stops and what usually fixes it.
Other changes to an order after it was booked are not followed. If you edit an order in Shopify after it is in e-Boekhouden, correct the books by hand. Belgian administrations are out of scope, and orders older than 60 days can only be read once Shopify has approved access to older order history.
- A line at a VAT rate other than 21%, 9% or 0%, such as another EU country's rate: book the order by hand.
- Orders with tips, duties or additional fees.
- Orders 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 Shopify: book by hand.
- Orders Shopify has not finished: a pending refund, incomplete financial data, a refund adjustment or shipping tax that cannot be split clearly. Retry once Shopify is done.
- A refund that returns an amount that cannot be tied to one VAT rate: book it by hand.
- An order or refund dated in a period that is closed in e-Boekhouden.
- A customer email that belongs to more than one relation.
- A sales entry that was removed in e-Boekhouden after it was booked, or an invoice number that already exists under another relation.
Set up e-Boekhouden.nl first
Integrator connects to one e-Boekhouden administration with an API token. In e-Boekhouden, open Beheer, Inrichting, Koppelingen, then e-Boekhouden API, not API/SOAP, and add a token. Give it a recognisable name and a validity of at least a year. e-Boekhouden shows the token once, so copy it right away; it opens the administration it was made in.
Before the first run, decide which accounts the entries use. Ledgers are matched by code or description and checked for the right category before anything is written. Work through this list with whoever keeps the books.
- A Dutch administration.
- A revenue ledger: the code of a profit and loss revenue account from Beheer, Grootboekrekeningen.
- A debtors account (category Debiteuren). If your administration has more than one, fill in which one.
- A payment ledger for paid orders: a bank, cash or payment provider account (category Liquide middelen), or turn payment booking off.
- Which VAT code to use for 0% lines.
- Relations: merge relations that share an email address. If you book everything to one fixed relation, give it a code no other relation uses.
- Open periods for the dates you will book, and a subscription that allows the entries: a free trial of the accounting module has an entry limit.
- A short invoice number: e-Boekhouden limits its length, and refund numbers add text to it. The order number alone is a safe choice.
Test with a dry run before turning it on
A dry run reads up to 20 recent Shopify orders with real data and shows, for each one, what would be written to e-Boekhouden: a new entry, or one it already has. It writes nothing and opens no problems. The checks that run before a real booking also run on the preview, so an order that would stop shows up here.
Read each preview as your bookkeeper would. Check the relation, the invoice number, the rows and their VAT codes, the revenue ledger and the payment ledger. Compare the totals with the order in Shopify.
Integrator does not delete data in e-Boekhouden, so an entry that is booked stays until someone removes it by hand. If you have booked Shopify orders by hand until now, choose a start date after the last one you booked, so the same sale is not in the books twice. After turning the integration on, look at the first entries in e-Boekhouden before you stop watching.
- An order with a single 21% line and shipping.
- An order mixing 9% and 21% products, with a discount.
- An order with a 0% line, if you sell to other EU countries or abroad.
- An order paid partly with a gift card.
- An order with a full refund and one with a partial refund.
When an order stops
An order that fails does not stop the others. Integrator shows why, using explanations the CLATE team wrote and approved. An error without an approved explanation is shown as not yet explained, rather than guessed. Every order can be traced: when it was found, how it was prepared and what e-Boekhouden answered.
There are two kinds of fix. Some causes you fix in e-Boekhouden, Shopify or the settings, then send the order again; this does not create a duplicate entry. For others, such as a foreign VAT rate or a gift card, you book the order by hand in e-Boekhouden and mark the problem as solved.
If e-Boekhouden refuses the token itself, the run stops until you reconnect. This happens when the token was revoked or expired, or was made under API/SOAP: create a new token under e-Boekhouden API and reconnect with it. If e-Boekhouden asks to slow down, Integrator tries again automatically; the limit is shared with the other apps on your administration.
Without Integrator, the same habits help: keep a list of orders booked by hand, note why, and check refunds against their original order.
- Period closed: ask your accountant to reopen it, or book the order by hand in an open period.
- Several relations have this email: merge them in e-Boekhouden, or book every order to one relation, then try again.
- Revenue, debtors or payment ledger not found: fill in the right account code under Settings, then try again.
- Invoice number too long: shorten the Invoice number rule on the mapping page, for example to the order number alone.
- VAT does not match the order: check the order's taxes and the VAT rates of its products in Shopify, then try again.
- Free trial full: upgrade the e-Boekhouden subscription, then try these orders again.
