Most of our work starts with one company in one country. Then a group decides to open something in the Netherlands, and a different set of questions arrives: not “which modules do we need” but “what does this country demand that ours does not, and what does that do to the system we already run”. The incorporation itself is your lawyer’s and tax adviser’s job. What lands on the ERP team’s plate is everything after it, and that part is rarely written down anywhere.
Short answer: a Dutch entity registers for Dutch VAT and files its own return, quarterly by default, plus an ICP declaration listing its B2B supplies to VAT-registered customers elsewhere in the EU. If it imports from outside the EU it will want the article 23 deferment, which moves import VAT from the border to the return, and which a foreign company cannot apply for by itself. The chart of accounts is rebuilt rather than translated, annual accounts of a BV are public, and Dutch payroll runs on its own rules. In your ERP that means a second company with its own chart of accounts, tax regime and filing calendar next to the parent, not a second system.
Why an Odoo partner is writing this
To be clear about what this is and is not: we are not your notary, your tax adviser or a company formation agent, and nothing here replaces them. What we can tell you is what each of these choices does to your system, because that is the part we get handed once the entity exists and nobody planned for the filings, the chart of accounts or the second VAT calendar.
We deliver Odoo internationally, including in countries where Odoo shipped no fiscal localisation and we built one ourselves. This page is the reverse direction: not a Dutch group expanding outward, but a foreign group landing here. If you are the one expanding outward, the companion piece is international accounting with Odoo, which works through which country ledger belongs in your system and which is better kept local and connected.
What every foreign entity meets here
Six things apply regardless of where your parent sits.
- BV or branch. A BV is a separate legal entity with its own annual accounts deposited at the Chamber of Commerce. A branch is a registered presence of the foreign company and is not a separate legal entity. Your adviser decides which; your ERP has to reflect it.
- Chamber of Commerce registration. Every entity registers with the KVK, and that registration is public, including the deposited annual accounts of a BV.
- Dutch VAT and its filing rhythm. The Dutch entity registers for VAT and files its own returns, quarterly by default. The parent’s VAT number does not cover it.
- The ICP declaration. A separate filing listing your B2B supplies to VAT-registered customers in other EU countries, submitted next to the VAT return. This is the single most-missed obligation on this list.
- The chart of accounts. The Netherlands has a widely used reference chart, the RGS, but it is a reference rather than a strict statutory template. Dutch practice allows more freedom here than several neighbouring countries do, which is liberating or unnerving depending on where you come from.
- Payroll and the expat facility. Dutch payroll tax runs on its own rules, and the facility for incoming employees, long known as the 30 percent ruling and now the expat scheme, is being trimmed: it stays at 30 percent through 2026 and drops to 27 percent from 2027, with the salary threshold rising to 50.436 euro.
The Dutch VAT return, and the two things sitting next to it
Worth its own section, because this is the part that generates work every quarter for as long as the entity exists.
The Dutch VAT return is filed with the Belastingdienst, quarterly by default, monthly if your volume or history calls for it. It nets what you charged against what you paid, so unlike a US sales tax filing it is not purely a remittance. Miss the rhythm and the penalties are administrative rather than dramatic, but the filing calendar is a real operational commitment that someone has to own from month one.
Two things sit alongside it.
The ICP declaration. Short for intracommunautaire prestaties, this lists your B2B supplies to VAT-registered customers in other EU countries and is submitted next to the VAT return. Every EU country has an equivalent, generally called the EC Sales List. If your parent is German, Belgian or French this will look familiar. If it is British, American or Chinese, there is no analogue at home, and this is the obligation teams most reliably forget until the first reminder arrives.
The article 23 import deferment. If the Dutch entity imports goods from outside the EU, this is the single most valuable thing on the page. Without it, import VAT is paid at the border and reclaimed later, so the money is out of the business in the meantime. With an article 23 permit, the import VAT is declared and deducted on the same VAT return, which nets to zero and keeps the cash. For a business importing containers, that cash-flow difference is a large part of why groups pick the Netherlands for their EU entity in the first place.
The catch, and it surprises almost everyone: a foreign company cannot apply for an article 23 permit itself. You need to be established here, and to have imported from outside the EU more than once. A foreign entrepreneur works through a fiscal representative, who either applies on your behalf or lets you operate under theirs, and who reports and deducts the import VAT on the return. You also have to keep an administration that shows the import VAT owed separately, which is a system requirement rather than a paperwork one.
In practice that last point is where the ERP earns its place: the return, the ICP declaration and the separate import VAT trail should all fall out of transactions already recorded, not out of a quarterly spreadsheet reconstruction.
What surprises teams, by country of origin
| Coming from | What tends to catch teams out | What it changes in your ERP |
|---|---|---|
| United Kingdom | There is no ICP equivalent at home, and post-Brexit your Dutch entity now sits inside the EU while the parent does not | A second VAT regime plus an EU-specific filing the UK system was never built to produce |
| Germany | The chart of accounts does not map: SKR03 and SKR04 have no Dutch counterpart, and the Steuerberater-owned ledger is less the norm here | Chart of accounts and tax codes rebuilt rather than translated; bookkeeping more often in-house |
| Belgium | Your parent is likely ahead, not behind: domestic B2B e-invoicing via Peppol has been mandatory in Belgium since January 2026, and is not yet mandatory here | The Dutch entity may need less than you assume today, and more once the Dutch B2B mandate lands |
| France | The Plan Comptable Général is prescriptive; Dutch practice is not, which reads as missing structure rather than freedom | Fewer imposed account codes, so your group needs its own mapping discipline |
| United States | VAT is not sales tax with a different name; it is a different mechanism, reclaimable and filed periodically. Fiscal years here are usually calendar years | A tax engine and filing calendar with no US analogue, and a possible reporting-period mismatch with the parent |
| China | Money movement is not frictionless, and there is no fapiao here: in the Netherlands the invoice you issue is the document, with no government-issued equivalent | Intercompany settlement needs planning, and the Dutch entity has no fapiao workflow to replicate |
A note on the two that are furthest apart
Coming from the US, the VAT gap is conceptual, not administrative. Sales tax is charged at the end of the chain and is a cost to the buyer. VAT is charged at every step and reclaimed by businesses along the way, so your Dutch entity both collects and recovers it, and the return nets the two. Teams that treat it as “European sales tax” configure it as a tax rate and then cannot explain the balance sheet. It needs to be modelled as what it is.
Coming from China, the fapiao habit is the thing to unlearn. In China the fapiao is issued through the tax system and is what makes a transaction real. There is nothing equivalent here. A Dutch invoice is a document you produce yourself, and its validity rests on containing the required details, not on government issuance. Groups that run a Chinese ledger alongside a European one hit this from both sides, which we work through in Chinese accounting in Odoo.
What this means in the system
None of the above requires a separate Dutch system. It requires the one you have to hold two sets of rules at once.
- Multiple companies in one database, each with its own chart of accounts, tax regime, currency and reporting. The Dutch entity follows Dutch VAT while the parent follows its own.
- The Dutch fiscal localisation, which brings the chart of accounts and tax codes, so the VAT return and the ICP declaration come out of the transactions already in the system rather than a spreadsheet at quarter end.
- Intercompany entries and consolidation, so group reporting eliminates internal flows instead of double counting them.
- Multiple currencies where the parent does not report in euro.
- Payroll connected, not forced. Dutch payroll is limited in standard Odoo, so we connect a specialist and post the journals back. That is the honest arrangement rather than a claim we would have to walk back.
The decision that actually costs money if you get it wrong is not any of these settings. It is whether the Dutch ledger lives in the group system at all, or stays local with an accountant and gets connected. That choice deserves its own analysis, and it is the subject of international accounting with Odoo.
What we would tell you before you ask
Two things, in the spirit of how we work.
If your Dutch entity is a small sales office with a handful of invoices a month, putting it in the group ERP may be more machinery than the problem deserves. A local bookkeeper and a periodic journal entry is sometimes the right answer, and we will say so.
And if the real problem is incorporation, residency, or which structure is most tax-efficient, we are the wrong party. Talk to a Dutch tax adviser first. Come back when the entity exists and the question becomes what your system has to do about it.
Opening a Dutch entity and unsure what it does to your systems? Book a free Quickscan and we will map your entities, filings and the connection strategy before anything gets configured.
Read more: International accounting with Odoo · Chinese accounting in Odoo: l10n_cn, fapiao and Golden Tax · Odoo for international rollouts · Odoo hosting and data residency international · What we do differently