As long as you have a handful of orders per week, retyping orders into the accounting is manageable. But somewhere between ten and a hundred orders per week it becomes a structural leak: transferring invoices every Friday afternoon, checking VAT rates, unpicking payouts from your payment provider — and still the administration never quite adds up. A connection between your webshop and your accounting package fixes that for good. In this article: why the connection pays off, which three options there are (plugin, automation tool or custom work), what it costs and a step-by-step plan to tackle it well. Want to see first what such an automated flow looks like? Build one yourself in the Flow-Lab.
Why connect your webshop to your accounting?
A connection isn't a gadget but a calculation. This is what processing by hand structurally costs you:
- Hours of manual work, every week again. Exporting orders, creating invoices, reconciling payments. It's work that's never finished, because tomorrow more orders come in.
- Retyping errors. A wrong VAT rate, a forgotten credit invoice, a double-booked order. Every error costs more time to find and fix later than the booking itself.
- An administration that lags behind. If the accounting is only updated at the end of the month, you're steering your business on figures from weeks ago — and every VAT return becomes a catch-up race.
- No view of your true margin. You see revenue in your webshop, costs in your accounting. As long as those two don't know each other, your margin remains an estimate.
With a connection, orders, VAT and payouts go automatically to your accounting package, daily or in real time. The accounting keeps up, the return adds up and your figures are current enough to steer on — for example in a live dashboard that brings revenue and costs together.
Three options: plugin, automation tool or custom work
Option 1: native plugin or connector. For common combinations — Shopify or WooCommerce on one side, a Dutch accounting package such as Exact Online, Moneybird, e-Boekhouden or SnelStart on the other — there are off-the-shelf plugins and connectors. You configure them, you test them and they run. This is the cheapest and fastest route, provided your process fits what the plugin maker had in mind. Whichever shop side you choose: the trade-off between platforms is in Shopify vs WooCommerce.
Option 2: automation tool (Make, Zapier, Power Automate). If your process fits a plugin just not — you want to book orders per product group to different ledger accounts, only forward paid orders or bring multiple shops together into one administration — then you build the connection with an automation tool. More flexible than a plugin, and you see exactly what happens at each step. Against that stands a monthly tool subscription that grows with your order volume. Which tool fits, you can read in Zapier vs Make vs Power Automate.
Option 3: custom API integration. At high volumes, unusual business rules or a package without a usable connector, a connection directly on the APIs becomes the best route: full control over logic and error handling, no tool limits. It is the most expensive option, though — what such a project costs and what the price depends on, you can read in what does an API integration cost?
| Option | Setup cost | Ongoing | Suitable for |
|---|---|---|---|
| Native plugin / connector | Low | Plugin subscription | Standard process, common package |
| Make / Zapier / Power Automate | Medium | Tool subscription, grows with volume | Custom rules, multiple shops |
| Custom API | Highest | Management & monitoring | High volumes, unusual logic |
What does a webshop–accounting connection cost?
As a ballpark for 2026 we use indicatively €500 to €2,000 for setting up a connection between your webshop and your accounting package. A standard connection via an existing plugin, neatly configured and tested, sits at the lower end of that band. A connection with custom rules — deviating ledger accounts, multiple VAT scenarios, multiple sales channels — sits at the upper end. It is an order of magnitude, not a quote.
On top of that come the ongoing costs of the chosen route: the subscription of the plugin or automation tool, and possibly management and monitoring so someone notices if the connection stops. If your situation outgrows the band — for example because you also want to connect inventory, fulfilment or a point-of-sale system — then you shift towards the general band for custom API integrations of indicatively €1,500–15,000; see what does an API integration cost? for that calculation.
Set the investment against what it replaces: anyone who spends a couple of hours a week transferring orders and fixing errors soon loses more per year to manual work than to the connection. How to broaden that trade-off across all your processes, you can read in automating business processes: the best tools for SMBs.
Step-by-step plan: how to tackle it
A connection that's right the first time doesn't start with the technology but with agreements about what needs to be booked. This is the order that works:
- 1. Decide what you want to synchronise. Orders or invoices? Per order or as a daily booking? With or without customer data? The less you transfer, the more robust the connection — start narrow.
- 2. Set the accounting rules, together with your accountant. Which ledger accounts, how do VAT rates (including foreign ones) come across, how do you book shipping costs, discounts and payment fees? This half hour with your accountant prevents weeks of hassle afterwards.
- 3. Choose the route. If everything fits an existing plugin, that's the choice. If not: automation tool or custom work, based on volume and complexity (see the table above).
- 4. Build and test with real scenarios. Not just the standard order, but precisely the edge cases: a return, a discount, a partly paid order, a foreign customer. Test in a trial administration, not in your real accounting.
- 5. Run a period in parallel. Let the connection run alongside your manual process and compare the outcomes, for example for a week or a month-end close. Only when everything adds up do you stop the manual work.
- 6. Arrange monitoring and ownership. Agree who notices and who fixes it if the connection stops or refuses an order. A connection without an owner is a time bomb under your administration.
Where it goes wrong in practice
Most connections fail not on the technology but on the details of the administration. The four classics:
- Returns and credit invoices. The order went in automatically, but the return didn't — and after a quarter nothing adds up any more. A good connection automatically creates credit invoices; test that scenario before go-live.
- Payouts from the payment provider. Your payment provider pays out periodically, minus transaction fees. If the connection only books orders and no one reconciles the payouts, the matching stays manual work. Take the payouts into the design.
- VAT on cross-border sales. If you sell to consumers in other EU countries, different VAT rules apply. A connection that books everything at the Dutch rate makes your return wrong instead of easy.
- Polluted product data. Missing article codes, duplicate products or inconsistent VAT settings in the shop end up one-to-one in your accounting. Clean up your product data first, then connect.
The common thread: involve your accountant before the build, test with real edge cases and give the connection an owner. Then it's dull, reliable infrastructure — exactly as it should be.
In short
- A webshop–accounting connection structurally cuts manual work, prevents retyping errors and keeps your administration and VAT return up to date.
- Three routes: native plugin (cheapest, for standard processes), automation tool such as Make or Zapier (more flexible, monthly subscription) and custom API (high volumes, own logic).
- Ballpark 2026: indicatively €500-2,000 for the setup; more complex integrations shift towards the general API integration band of €1,500-15,000.
- Start with the accounting rules, not the technology: set ledger, VAT and costs with your accountant and test with real edge cases such as returns.
- Arrange monitoring and ownership — a connection without an owner is a time bomb under your administration.
Read more
- What does an API integration cost?
- Zapier vs Make vs Power Automate
- Business process automation: tools
- Shopify vs WooCommerce
- Shopify webshop development
Frequently asked questions
What does it cost to connect a webshop to the accounting?
As a ballpark for 2026 we use indicatively 500 to 2,000 euros for setting up a connection between your webshop and your accounting package. A standard connection via an existing plugin sits at the lower end; a connection with custom rules for, say, ledger accounts, VAT or returns sits at the upper end. It is an order of magnitude, not a quote.
Which data do you synchronise between webshop and accounting?
Usually orders or invoices with the correct VAT rates, payments and payouts from your payment provider, credit invoices for returns and sometimes customer data and inventory values. What exactly you synchronise you decide in advance: not everything is necessary, and the less you transfer, the simpler and more robust the connection.
Can I connect Shopify or WooCommerce to Exact, Moneybird or e-Boekhouden?
Yes. For the common combinations of webshop platforms and Dutch accounting packages there are off-the-shelf plugins and connectors, and otherwise the connection can be built via an automation tool such as Make or Zapier or via a custom API integration. Which route fits depends on your volume and how standard your process is.
Isn't an off-the-shelf plugin simply enough?
Often, yes. If your process fits what the plugin maker had in mind, a plugin is the cheapest and fastest route. Plugins get stuck as soon as you have deviating requirements: multiple shops in one administration, custom rules per product group or country, or an accounting package the plugin doesn't support. Then you end up at an automation tool or custom work.
What happens with returns and credit invoices?
That is one of the points where connections come unstuck in practice, so arrange it explicitly. A good connection automatically creates a credit invoice for a return and processes the refund, so your administration keeps matching your actual cash flows. Always test this scenario before go-live.
How long does it take to set up such a connection?
Indicatively: a standard connection via a plugin is often up within a few days, including testing. A connection with custom rules via an automation tool or custom work takes rather a few weeks, mainly due to testing edge cases such as returns, discounts and foreign VAT. The lead time depends strongly on how clean your product data and settings are.
Prefer these kinds of insights in your inbox?
Leave your email address and we'll add you to the list and email you as soon as the next edition on IT, automation and dashboards is out. You can unsubscribe at any time with a single email.