Contact Info
Netherlands
What is an ERP audit for a company in the Netherlands?
An ERP audit gives a live but disappointing business system an independent check-up. For a Dutch company I test whether stock, orders and finance agree across the ERP, warehouse provider and webshop, prepare BTW, listing and audit file evidence for your accountant, review roles and approvals, and rank findings by risk. It runs remotely and does not replace your accountant's audit.
Last reviewed by Vikas Saroj
In a Dutch distribution or trading business, the ERP is one link in a chain. Orders arrive from a webshop or EDI partner, stock sits with a logistics provider, invoices leave over Peppol or email, and the accountant receives an export at period end. When figures stop agreeing somewhere along that chain, staff start keeping their own lists and trust in the system fades.
I carry out ERP audits for companies in the Netherlands remotely and in English. The review follows transactions through the whole chain, checks the finance setup your accountant depends on, and looks at access, licenses and reports. You receive a findings report ranked by business risk, with each item tied to a cause and a practical fix.
Nothing in the audit replaces your external accountant's work or tax advice. Points about BTW, customs or personal data are written as questions for them to answer.
What I Review
The review follows real transactions rather than settings alone, because most problems sit in the handoffs between systems.
A handful of real orders traced from webshop or EDI through picking at the warehouse provider, invoicing, payment and the ledger, recording every manual touch and every delay along the way.
Quantities and values in the ERP compared with the logistics provider's stock report, with each difference traced to a cause such as late messages, returns or unit mismatches.
Tax codes in use, sample postings for domestic, intra-EU and import flows and the data behind the ICP listing, organized so your accountant can review treatment quickly.
A trial export of the audit file your accountant may request, checked for completeness against the ledger. Whether it meets their needs is for them to confirm.
Users, roles and approval limits mapped against duties such as changing supplier bank details and releasing SEPA batches, with conflicts and dormant accounts listed.
Paid users, modules and connector subscriptions compared with real use, then a ranked findings report presented to management in a remote readout.
How I Work
Agree questions and gather access
Kick-off with the controller
Map systems and providers
Request read-only access
Pick sample transactions
Evidence across the whole chain
Follow orders end to end
Compare stock with provider
Run trial audit file export
Export roles and limits
Findings people can act on
Validate drafts with owners
Separate accountant questions
Present ranked findings
Agree owners and order
The request usually follows a moment when the numbers stopped adding up. The warehouse provider reports one stock figure and the ERP another. The accountant asks for an audit file and the export takes days of correction. A controller joins from a larger company and cannot work out why the margin report differs from the ledger. Or the business has grown from a small package such as Exact or AFAS into a fuller ERP, and the setup still reflects the first year.
An ERP audit answers a simple question: does the configuration, and the way staff use it, still match the business the company has become? It is not the audit your external accountant performs on the annual accounts, and it does not give tax or legal opinions. It is a structured review of configuration, data, interfaces, access, reports and licenses, carried out by someone with no stake in selling more software or more implementation days.
I run it remotely, in English, which suits Dutch international businesses and the European headquarters of foreign groups. Your staff explain Dutch-language screens and documents as we go. I describe the general method on my ERP health check page. What follows is how it adapts to a Dutch company, where much of the risk lives in links between systems rather than inside the ERP.
Many Dutch traders and distributors keep stock with a third-party logistics provider, sometimes several, and sell through a webshop, marketplaces and EDI. The ERP then depends on a stream of messages: order releases going out, shipment confirmations, receipts and stock adjustments coming back. When one of those messages is late, duplicated or rejected, the ERP and the warehouse drift apart without anyone noticing until a customer complains or a stock count disagrees.
I compare the ERP's stock by item and location with the provider's own report for a chosen date, then trace each difference to its cause. Typical causes include returns processed at the warehouse but never booked, unit-of-measure mismatches between systems, connector errors that sit in a log nobody reads, and manual corrections made on one side only. I also check how the webshop and marketplace connectors map products, prices and VAT codes, because a wrong mapping there flows straight into invoices.
Each finding lists the interface, the frequency of the problem, the business effect and the owner who should fix it, whether that is your team, the connector supplier or the logistics provider. Where the fix needs integration work, the ERP integration page describes how that is approached. Contracts and service levels with the provider remain between you and them.
Your accountant prepares or reviews the BTW return and the intra-community listing, and may also ask for an audit file export from the ledger. All three depend on configuration that tends to drift over time. My job is to make that drift visible, not to rule on tax treatment.
The evidence pack I prepare covers every tax code in use with sample transactions and the return field each one reaches; the customer VAT numbers and amounts that feed the listing, compared with the ledger; postings for imports, including how they are booked where you hold an import VAT deferment license; and sales through foreign warehouses or to consumers in other EU countries if those apply to you. I add a trial export of the audit file and note any accounts, journals or periods that look incomplete.
The accountant reviews the pack and decides what, if anything, should change. Their answers become configuration items in the fix list. I also record where the system stands on structured invoicing: whether invoices can be sent and received over Peppol today, how rejected messages are handled and which customers already expect them. The EU is moving toward wider e-invoicing and digital reporting, and the timing for your company is a question for your advisor. My Odoo Accounting page for the Netherlands shows how these checks look on one platform.
Access rights are where a growing company quietly accumulates risk. A buyer who moved into sales still approves purchase orders, a temporary controller's account is still active, and the person who maintains supplier bank details can also release the SEPA batch. None of this means anything is wrong today, but together they weaken the controls your accountant and management rely on.
From a full export of users, roles and approval limits I build a matrix against the tasks that ought to sit with different people: supplier master changes, invoice approval, payment release, manual journals, credit limits and price changes. Every clash gets a named user, a description of what could go wrong and a remedy, which might be a narrower role, a second approver or a monthly check by the controller.
The same exports show who can see salary journals, employee data and customer contact details, and how long records are kept. Under GDPR, with the Dutch data protection authority as regulator, retention and access decisions belong to your privacy contact or lawyer, so I phrase findings as questions for them. Where activity logging or reports could be used to monitor staff, I note it, because a works council, if you have one, may need to be involved; HR and management decide how to handle that with their advisors.
The last part of the review asks whether management can trust what the system tells them. Starting from the reports that management and the group actually read, such as margin by customer, stock value, overdue receivables and cash, rebuild a few of their totals from the underlying entries and record wherever a definition is unclear or a spreadsheet bridges a gap. Often the cause is upstream: missing cost prices, a connector that books revenue to a default account, or returns posted without value.
License usage gets a separate look. Paid users who have left, full licenses used for occasional read-only access, modules bought for a later phase and connector subscriptions that duplicate each other are all listed for discussion at renewal.
The report opens with a short assessment for management, then sets out findings by area with a priority, cause and recommended action. Questions for your accountant, privacy contact and logistics provider are grouped so they can be forwarded as they are. The readout happens on a video call with those who will carry out each fix; a visit can be arranged if it genuinely helps. If the review shows a project that is still failing rather than a system needing tuning, see the ERP rescue page for the Netherlands. Broader context is on my ERP consultant page for the Netherlands and the Netherlands overview.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
I run a trial export and check it for completeness against the ledger, for example missing journals, periods or accounts. Whether the file meets the expectations of your accountant or the tax authority is for your accountant to judge. My contribution is a clean, documented test they can review instead of a surprise at year-end.
Ideally, yes, at a light level. I need their stock report for a chosen date and, where messages fail, a contact who can explain their side. Their contract and service levels stay between you and them. The findings show which differences come from the ERP, which from the connector and which from the warehouse.
Yes. The engagement runs in English, which suits most Dutch international businesses. Key users can show their daily work on screen in the Dutch interface while explaining in English, and any Dutch documents are summarized or checked by your team where needed. The report is written in English for management and any foreign parent.
Often it is. The audit shows which problems come from the platform and which come from setup, data or habits that would follow you into a new system. That evidence makes a replacement decision sounder, and sometimes shows that targeted fixes are enough. It also produces a clean list of requirements for any selection that follows.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
