Dynamics 365 Consultant, Netherlands

European headquarters on Business Central

A Dutch company acting as a European hub may own sales companies in Germany, France or the Nordics, a warehouse entity, and a service company that recharges costs across the group. Business Central handles several companies in one environment, with shared or separate master data, intercompany postings and consolidation. That makes it a natural candidate, but the structure has to be designed before the partner starts configuring.

The first decisions are about scope. Which entities move onto Business Central now, and which stay on their current systems for a while? Does each company keep its local currency, and which reporting currency does the parent want? Business Central can carry an additional reporting currency, and I check whether that, consolidation in a separate company, or the group's own consolidation tool best meets the parent's needs.

I produce an entity and currency map, a local chart of accounts linked line by line to the parent's chart, dimension rules and a month-end calendar both the Dutch team and head office accept. These documents become the partner's brief. My multi-company ERP page explains the general design questions, and the Business Central page covers the product.

Dutch localization, BTW and e-invoicing checks

Microsoft publishes Business Central in a Dutch localized version, and the scope of country features can change between releases. I review what the current version provides and then test it on a sandbox with your advisor's scenarios, rather than relying on partner slides.

For a Dutch hub the scenarios often include domestic supplies, intra-EU deliveries and acquisitions, imports with any deferment arrangement your advisor has put in place, reverse charge services, fiscal representation for non-EU group companies and, where it applies, a VAT group. Each is checked on the document, in the ledger and in the BTW and intra-EU reports. Treatment is decided by your advisor; the test proves the system applies it.

Structured invoicing is the forward-looking item. Dutch public sector buyers generally expect structured electronic invoices, and EU policy is moving toward wider use and digital reporting. Depending on your version, Business Central may cover Peppol through standard features or require a partner app or access point service. I add this to the brief so every proposal answers it explicitly. Confirm current obligations with your advisor.

Selecting a Dynamics 365 partner without a vendor bias

Microsoft relies on partners to license and deploy Dynamics 365, so the firm you pick decides much of your experience: who configures, who supports, which add-ons appear and how licenses are bundled. Dutch buyers can choose from local partners and from firms based elsewhere in Europe or with offices near the parent. Proposals vary widely in method and assumptions.

Because I am outside the Microsoft's partner channel and receive nothing from licenses or services, I can run the selection for you. I send a single brief to each shortlisted partner, script demos around intercompany flows, warehouse processes and the Dutch tax cases, and score responses on fit, approach, team and support. Before signing, I review the license proposal and statement of work line by line.

During the build I attend design reviews, keep a decision log, track changes against the contract and lead acceptance sessions where your controllers and warehouse leads sign off each scenario. Delivery is remote and in English, and workshops are booked in the Dutch morning that overlaps my working day in India. The ERP vendor selection page details the method, and my Netherlands ERP consulting page covers the wider platform landscape.

Tenant, hosting and the parent's IT standards

Business Central online runs as a Microsoft-hosted service tied to an Entra tenant. For a Dutch subsidiary the first question is often political as much as technical: does the environment sit in the parent's global tenant or a European one, and who administers it? Confirm the environment's data location when it is created, record it with Microsoft's processing terms, and make sure your GDPR documentation reflects the decision.

Group IT standards then shape the rest: single sign-on, security groups, Power BI workspaces, approved integration tools and audit expectations. I gather these early, because a design that ignores the parent's controls tends to be reworked late. Inside Business Central I set permission sets so personal data, payroll journals and sensitive pricing are visible only by role, and agree retention with your privacy lead.

Payroll in the Netherlands stays with a payroll provider, posting summarized journals by entity and cost center. Warehouse tools, carrier platforms and EDI links connect through integrations I specify with clear ownership. The method is on my ERP integration page, and the Netherlands hub lists my other work for Dutch companies.

Where Dynamics 365 is the wrong choice in the Netherlands

Dynamics 365 suits many Dutch hubs and mid-sized groups. I would advise a different route, or a sharper comparison, in these cases:

• Single-entity service firms with simple billing, where partner-led implementation adds cost that Zoho for Dutch service companies would avoid.
• Distributors wanting webshop, stock and accounting in one low-cost suite, who may find Odoo in the Netherlands closer to their needs.
• Groups standardized on another ERP, where the Dutch entity should join the group system or feed it rather than add Microsoft.
• Teams unwilling to depend on a partner for changes and support over many years.

An ERP evaluation compares Dynamics 365 with these options using your scenarios, your entity map and your support expectations. The aim is the right system for the Dutch entity and the group, not a particular brand, and a written rationale that head office can review before any license is ordered. That rationale also helps later, when auditors or a new finance director ask why the platform was chosen.