Automation
Bookkeeping
Finance
Scalability factors in Dutch bookkeeping software
Is your Dutch bookkeeping tool still enough for your BV? Six scalability factors, each with a test question: transactions, payroll, holdings, EU BTW, reporting, updates.
•
15 mins

Intro
The friction appears long before the failure. A Dutch BV that has outgrown its bookkeeping platform rarely gets a clear error message. It gets a series of quiet complications. The bank reconciliation takes longer than it used to. The accountant asks questions the system should be answering. The WKR vrije ruimte lives on a separate spreadsheet because the platform cannot track it. The quarterly BTW return needs a manual step for the ICP listing, because the platform does not prepare it.
None of this means the platform is broken. It still works. The question is whether it will keep working correctly as the business grows, and six factors decide that. Each section below names the symptom, explains the factor, and ends with a test question you can put to any platform, including your own, along with what a good answer looks like.
Key takeaway: Outgrowing a bookkeeping platform is not a failure. It is a sign of growth. The mistake is not noticing the friction until an error surfaces in a letter from the Belastingdienst. The six factors below help you find the ceiling before it becomes a compliance problem.
Factor 1: Transaction Volume
The first sign is usually a bank transaction count creeping towards the plan's limit. The DGA moves up a tier, then up again, and eventually finds that the tool chosen for simplicity and low cost now costs more per month than a platform built for their current size.
Volume grows faster than most founders expect. A B2B consulting BV that invoices 15 clients a month, pays three salaries, settles a handful of suppliers, insurance, and pension, makes the quarterly BTW payment and the monthly loonheffingen payment, and moves the occasional amount to the DGA can run well over 100 bank transactions a month at modest revenue. Add iDEAL payment links, payouts from a payment provider, and expense claims, and the number climbs again. A plan designed for freelancers is structurally underpriced for that profile: the cap either blocks imports or triggers an automatic jump to a much more expensive tier. If imports stop mid-month, the BTW return gets prepared from an incomplete picture. Reconciliation problems compound the effect, which why bookkeeping never matches bank statement explains in detail.
The test question is this: what is the maximum number of bank transactions this platform processes per month on my current plan, what happens when I reach it, and what is the price at the next three tiers? What good looks like is unlimited transaction processing at a fixed monthly price, with no escalation tied to transaction count.
Factor 2: Payroll Integration
The symptom is a monthly bridge between two systems. Payroll runs in one tool, and someone exports a journal and imports or retypes it into the bookkeeping. Sooner or later the two disagree.
Every Dutch BV that pays a DGA salary has a payroll obligation. The gebruikelijk loon has to be set correctly, with 58,000 euros as the statutory norm amount for 2026, loonheffingen calculated and filed every period, payslips issued, and the posting reconciled against the te betalen loonheffingen balance in the books. Hiring a first employee adds social contributions, CAO checks, and WKR tracking. The vrije ruimte is calculated from the fiscal loonsom, which lives in payroll, and compared with WKR spending, which lives in the bookkeeping. A platform without payroll cannot produce that comparison, so it ends up on a spreadsheet, and the founder discovers in December that the limit was passed in September, with an 80% eindheffing on the excess.
Kilometervergoeding has the same split: the reimbursement is a payroll item while the cost sits in the books. When the two systems use different account codes, the loonheffingen balance in the books drifts away from the filed return, and the mismatch surfaces when someone finally compares them. Gaps between payroll and bookkeeping are among the most common sources of error, as payroll errors Dutch employers shows.
The test question: does this platform process DGA salary, employee loonheffingen, and WKR tracking in the same tool as the bookkeeping, without a manual export and import step between them? What good looks like is payroll and bookkeeping in one platform, the salary posted automatically to the right accounts, loonheffingen filed electronically, and the WKR balance tracked against the year-to-date fiscal loonsom.
Factor 3: Holding Structure
The symptom is two logins, two sets of books, and an intercompany invoice entered twice.
Adding a holding BV alongside an operating BV is one of the most common structural moves for a growing Dutch entrepreneur, for asset protection, tax planning, and the ability to retain profit at holding level. It also doubles the administration at once. Two legal entities mean two sets of accounts and two jaarrekeningen, two VPB positions unless a fiscale eenheid is set up, and often two BTW registrations once the holding charges a management fee. That fee is revenue in the holding and a cost in the operating BV, and a platform that treats the two as unrelated administrations forces the DGA to mirror every intercompany transaction by hand.
The same applies to dividends paid by the operating BV to the holding, which are exempt under the participation exemption but must still be recorded correctly in the holding's books, and to any rekening-courant between the entities, which has to agree on both sides. If the holding is not yet in place, setting up a BV and holding together covers the costs and the timeline.
The test question: how many separate administrations can I run under one account, can I see a consolidated position across all of them, and is there an extra cost per administration? What good looks like is multiple administrations under one login, a consolidated view, no per-administration fee, and intercompany transactions handled without manual duplication.
Factor 4: Cross-Border BTW
The symptom is a manual step every quarter: the ICP listing compiled from a spreadsheet, or OSS figures pulled from a separate export.
A Dutch BV that starts invoicing clients in Germany, France, or Belgium picks up new obligations. Sales of goods and services to businesses in other EU countries are usually reported under BTW verlegd, reverse charge, in rubriek 3b of the BTW return, and each customer must also appear on the ICP listing filed alongside the return. For sales to EU consumers, once cross-border B2C sales pass 10,000 euros a year, destination-country BTW applies, and the OSS lets you declare it in a single return. Goods bought from outside the EU bring import BTW, which has to flow correctly from the customs documents into the books.
A platform that handles domestic Dutch BTW well does not necessarily handle these. If intra-EU transactions are not coded to the correct rubriek when they are entered, the ICP listing has to be corrected by hand every quarter, and a wrongly coded invoice produces a wrong BTW return, which is the kind of discrepancy that draws an inspector's attention. How these returns fit together is covered in when to file VAT Netherlands.
The test question: does this platform handle OSS return data, ICP listing preparation, reverse-charge coding, and import BTW automatically, or do they need manual intervention every quarter? What good looks like is all four obligations handled inside the platform, with no manual export and no separate tool.
Factor 5: Real-Time Reporting
The symptom is a decision made without current numbers. A monthly-processed system produces a profit and loss account when the books are processed, and between runs the DGA is steering without an instrument panel.
The most expensive effect is not the processing time. It is the decisions made on stale information. A DGA who does not know the year-to-date profit in October cannot time a dividend well. One who does not know the rekening-courant balance cannot judge a borrowing decision ahead of 31 December, the peildatum for the 500,000-euro threshold. One who does not know the remaining WKR vrije ruimte risks an 80% eindheffing on a December gift round. The figures that matter are the bank balance reconciled to the books, year-to-date profit against last year, outstanding debiteuren with ageing, the WKR vrije ruimte remaining, the RC against the threshold, and a running estimate of VPB. How profit timing shapes dividend decisions is covered in DGA salary vs dividend, and the threshold itself in borrowing from your own BV.
The test question: can I see the current bank balance, year-to-date profit, outstanding debiteuren, remaining WKR vrije ruimte, and my RC balance in real time, without waiting for a monthly or quarterly run? What good looks like is a live dashboard that updates whenever a transaction is processed, showing the DGA's key figures without manual processing or an accountant's involvement.
Factor 6: Regulatory Update Pace
The symptom is finding out after filing that a rate or table was wrong.
Dutch tax law changes every year, and not only on 1 January. Prinsjesdag, the third Tuesday of September, announces the next year's changes, but other changes arrive mid-year or retroactively. Consider what a platform has had to absorb recently: the BTW rate on accommodation moving from 9% to 21% on 1 January 2026; the tax-free mileage rate rising to 0.25 euros per kilometre with effect from 1 January 2026; the first bracket of the WKR vrije ruimte rising from 2.00% to 2.16% from 2027, together with a proposal to abolish the exemption for staff discounts on a company's own products; and the box 3 overhaul planned for 2028. E-invoicing is moving too. It is already mandatory when invoicing the Dutch government, still voluntary between businesses, and due to become mandatory for cross-border B2B invoices in the EU from 1 July 2030, with the Dutch government working towards domestic B2B as well. E-invoicing becomes mandatory Netherlands covers that timeline.
A platform that updates its BTW forms but not its loonheffingen tables will calculate payroll on old rates until it catches up. The underpayment comes back as an assessment with belastingrente, 5.0% a year in 2026, usually found in a mid-year reconciliation. Belastingplan 2027 Prinsjesdag lists what the latest Prinsjesdag changed.
Watch out: The kilometervergoeding rose from 0.23 to 0.25 euros per kilometre with retroactive effect from 1 January 2026, through a ministerial policy decree published in May 2026. A platform that only applied the new rate from the date it updated leaves every employee with a shortfall of 0.02 euros per kilometre for the earlier months. The correction is a retroactive payment that still has to go through a payroll run before the year closes. How a platform handled this change is a good test of how it handles all of them.
The test question: when a Dutch tax change takes effect, such as the kilometervergoeding increase or the WKR adjustment, how does this platform notify me, when is it implemented, and do I need to do anything, or is it automatic? What good looks like is automatic updates to all rates and tables on or before the effective date, retroactive changes applied retroactively, and a proactive note to the DGA about changes that call for a decision.
The Six-Factor Summary
Factor | Symptom you have outgrown it | Test question to ask | What good looks like |
|---|---|---|---|
Transaction volume | Plan upgrades every 6 to 12 months; bank imports pause at month-end | What is my true monthly cost at 300 bank transactions? | Unlimited transactions at a fixed monthly fee |
Payroll integration | Monthly manual export and import between payroll and bookkeeping; WKR tracked on a spreadsheet | Are DGA salary, loonheffingen filing, and WKR tracking in the same tool as the bookkeeping? | Payroll and bookkeeping in one platform; salary posting automated |
Holding structure | Two logins for two administrations; intercompany fees entered twice | Can I manage multiple BV administrations under one account with a consolidated view? | Multiple administrations, one login, no per-administration fee |
Cross-border BTW | ICP listing compiled by hand each quarter; OSS needs a separate tool | Does the platform produce the ICP listing and OSS data automatically? | ICP, OSS, reverse-charge, and import BTW handled natively |
Real-time reporting | Year-to-date profit only visible after monthly processing; WKR balance unknown mid-month | Can I see my RC balance, WKR vrije ruimte, and year-to-date profit without asking my accountant? | A live dashboard updated with every transaction |
Regulatory updates | Found incorrect tax rates after filing; had to file a correction for a platform error | How quickly does the platform update when Dutch tax law changes, and do I have to do anything? | Automatic updates before the effective date; proactive notice to the DGA |
How Neno Handles All Six
Neno is an AI-native bookkeeping and payroll platform built for Dutch BVs. It is not a general-purpose accounting tool with a Dutch skin. It is designed around Dutch tax law, Dutch payment methods, and the administrative obligations a BV carries from incorporation through growth. Here is how it answers each of the six factors.
On transaction volume, Neno's fee does not depend on how many bank transactions a business processes. A BV with 20 transactions a month and one with 2,000 are on the same fee structure, so there is no tier to outgrow and no cap that pauses imports. Bank transactions come in through a PSD2 connection with Dutch banks including ABN AMRO, ING, Rabobank, and bunq. The AI reads each invoice, receipt, and bank transaction, proposes the grootboek account, BTW code, and cost category, and learns from corrections. It handles standard invoices, credit notes, reverse-charge invoices, and BTW-free invoices, and it reconciles iDEAL, Mollie, Stripe, and Tikkie payments.
On payroll, Dutch payroll runs in the same platform as the bookkeeping. DGA salary is processed with a gebruikelijk loon check, loonheffingen are calculated at current rates and filed monthly via Digipoort, and payslips are generated. The salary posting lands in the correct grootboek accounts without manual entry. For employees, Neno handles CAO-configured salary scales and tracks the WKR vrije ruimte against the fiscal loonsom in real time, with an alert as the remaining space approaches zero. The kilometervergoeding is applied at 0.25 euros per kilometre, retroactively from January 2026.
On holding structures, multiple BV administrations sit under one account, with a consolidated view and no per-administration fee. Intercompany management fees are processed in both administrations at once, so nothing is entered twice.
On cross-border BTW, intra-EU B2B transactions are coded automatically to the correct BTW rubriek based on the customer's VAT registration country and the nature of the supply. The ICP listing is generated from those transactions, ready for filing. Reverse-charge invoices carry the required btw verlegd reference, OSS data is prepared for B2C sales by destination country, and import BTW from customs documents flows into the books.
On real-time reporting, the dashboard updates every time a transaction is processed. It shows the live bank balance, year-to-date profit against the prior year, outstanding debiteuren with ageing, upcoming crediteuren, the remaining WKR vrije ruimte, the RC balance against the 500,000-euro excessief lenen threshold, and an estimated VPB accrual. Dividend timing, rekening-courant reduction, and year-end WKR spending can be decided from it, without waiting for a review call.
On regulatory updates, rates and tables are updated before each Dutch effective date, with loonheffingen tables changed at the January and July dates and no action needed from the DGA. The WKR increase to 2.16% will be applied from 1 January 2027, and Peppol e-invoicing is supported. Beyond rate updates, a team of Dutch tax professionals watches the regulatory calendar and contacts clients when a change calls for a decision, for example when a higher WKR limit creates planning room.
Neno is software plus people. Dutch tax professionals review the AI's output, handle BTW and VPB filings, and monitor compliance, and the team works in English for international founders. The full interface and help centre are in English, while documents that Dutch law requires in Dutch, such as invoices with the right legal elements and submissions to the Belastingdienst, are produced in Dutch. Plans start at 80 euros a month, are set by the size and reporting needs of the business, and do not rise with transaction counts, users, or administrations. Routine filings by the professional team are included, with no separate accountant invoice. The wider shift towards this model is covered in outsourcing bookkeeping Netherlands.
If you want to test your current setup against the six questions, book a demo and we will walk through it with you. Our team can also help you incorporate your BV or get bookkeeping and payroll running correctly from the first invoice.
FAQs
When should I consider switching my Dutch bookkeeping platform?
When two or more of the symptoms above appear together, and ideally before a filing deadline rather than after an error. A plan upgrade, a manual payroll bridge, a spreadsheet for WKR, or a hand-compiled ICP listing are all signals that the platform's ceiling is near.
What is the most common sign that a Dutch BV has outgrown its bookkeeping software?
A manual step that did not exist a year ago, such as exporting payroll into the books or compiling the ICP listing by hand. Repeated plan upgrades for transaction volume are the second most common sign.
Does integrated payroll matter if I only have a DGA salary?
Yes. Even one DGA salary needs a gebruikelijk loon check, monthly loonheffingen filing, payslips, and a salary posting that reconciles to the books. With separate tools, a single salary can still cause reconciliation gaps that build up month by month.
How does WKR tracking break when payroll and bookkeeping are separate tools?
The vrije ruimte depends on the fiscal loonsom, which lives in payroll, and on WKR spending, which lives in the bookkeeping. With two tools, nobody sees the running balance, it moves to a spreadsheet, and an overshoot is found late, with an 80% eindheffing on the excess.
What is the ICP listing and does my bookkeeping software need to produce it?
The ICP listing is a statement filed with the BTW return that lists your EU business customers and what you supplied to each. Your software should prepare it from correctly coded transactions, because compiling it by hand each quarter invites errors.
Can I manage a holding and operating BV in one bookkeeping tool?
Yes, if the tool supports multiple administrations under one login, a consolidated view, and intercompany processing. Without these, management fees and intercompany balances have to be entered and matched twice by hand.
What real-time financial metrics should a Dutch DGA be able to see without calling their accountant?
The reconciled bank balance, year-to-date profit, outstanding debiteuren with ageing, BTW payable for the current quarter, remaining WKR vrije ruimte, the rekening-courant balance against the 500,000-euro threshold, and an estimated VPB accrual.
How quickly should a bookkeeping platform update when Dutch tax law changes?
Before the effective date for rates and tables, automatically, and with a note to you when a change needs a decision. Retroactive changes, such as the 2026 kilometervergoeding increase, should be applied retroactively, not only from the date of the update.
What is the difference between a bookkeeping platform and an AI-native bookkeeping platform?
A conventional platform stores and reports what you enter or categorise with fixed rules. An AI-native platform reads the documents and transactions itself, proposes accounts and BTW codes, learns from corrections, and leaves people to review the exceptions.
Does Neno work for both ZZP and BV structures?
Yes. Neno is built around the Dutch BV, and ZZP entrepreneurs can use it as well. For a ZZP, transaction volume, cross-border BTW, and update pace matter most; payroll integration and holding support become important once the business incorporates.
Written by
Nick Knuppe
CEO & Founder

