Overview
ERPNext Netherlands turns a vanilla ERPNext install into something a Dutch auditor and the Belastingdienst will accept without complaint. It's a thin, opinionated layer — it doesn't fork ERPNext, it adds what's missing.
Who this is for
- Dutch-incorporated companies (BV, eenmanszaak, VOF) that need to file BTW returns, run SEPA payment batches, and produce XAF audit files on demand.
- EU companies trading in the Netherlands that need the same compliance primitives but may also need EU-wide ICP/Intrastat (see erpnext_europe).
- Accountants and auditors working in ERPNext who expect to see RGS reference codes on every GL account.
What's included
| Area | Purpose |
|---|---|
| BTW Returns | OB declaration boxes 1a–5g, with drill-down to source invoices |
| SEPA Payments | Batch credit transfers in PAIN.001.001.03 XML, ready for ABN/ING/Rabobank/etc. |
| XAF Audit Export | XAF 3.2.1 audit file generation, schema-validated |
| RGS Chart of Accounts | Reference codes linked to your accounts, used by every Dutch accountant |
| Tax Categories | Seven preset categories (NL-Domestic, EU-B2B, Non-EU, etc.) for automatic VAT routing |
| Account Mapping | Tax Category + Item Group → correct income/expense account on every invoice line |
What's not included
- Payroll — the Dutch payroll module is separate (HRMS-based, sold via Prilk's payroll partner).
- ICP / Intrastat reporting — moved to the
erpnext_europeapp to keep this localization focused on NL-only concerns. - e-Invoicing (PEPPOL) — handled by the separate
edocumentapp, which composes cleanly on top of this one.
Compliance scope
- Belastingdienst BTW filing requirements (current OB declaration form)
- SEPA SCT credit-transfer rulebook (currently no SDD direct debit)
- XAF 3.2.1 schema (the version Belastingdienst currently requires for audit exports)
- RGS 3.5 reference scheme
The next page walks through a first-time setup on a fresh company.
Last updated 3 days ago
Was this helpful?