ERP Selection Consultant, Denmark

Danish shortlists, from cloud accounting upward

Plenty of Danish companies arrive at this decision while running e-conomic, Dinero or Billy as their cloud accounting tool, with a webshop, a stock spreadsheet and a CRM around it. Others are leaving an older on-premise Microsoft system such as C5 or NAV that has served them for years. The starting point shapes the shortlist more than company size does.

• Firms leaving a cloud accounting tool often compare a stronger accounting setup with apps against a suite such as Zoho or Odoo.
• Wholesalers and brands with stock and webshop sales commonly line up Odoo, Dynamics 365 Business Central and Danish-built ERP products such as Uniconta.
• Producers wanting open-source control can add ERPNext, provided they accept more responsibility for Danish compliance and reports.
• Companies on an older Microsoft system face a different question: move to Business Central with a partner who knows the old setup, or use the change to reconsider the platform entirely.

I keep the list small enough that every option is tested properly. Deeper notes on individual platforms in Denmark are on the Odoo in Denmark and Zoho in Denmark pages.

Treating bookkeeping rules as a knock-out test

Danish legislation has pushed businesses toward digital bookkeeping systems that meet set standards, with expectations about storing vouchers digitally, backups and the ability to handle electronic invoices. For a selection, that turns into a simple principle: an option that cannot show how it meets the requirements that apply to you should not reach the demo stage.

In practice I ask each vendor and partner for written documentation. Is the standard product registered as a digital bookkeeping system with the Danish authorities, or would your setup be treated as a separate system with its own obligations? Does any customization or third-party app change that position? Where are vouchers stored, and who is responsible for backups? How would an auditor or authority get access to the records?

I do not decide whether a system complies. Your accountant or auditor confirms which rules apply to your company and whether the vendor's answers satisfy them. My part is to collect the answers in a comparable form, make sure they are on the record before the commercial discussion, and carry any conditions into the contract and test plan.

This step often removes an option early, which saves everyone demo time. The ERP business analyst page for Denmark describes how these rules become written requirements.

Demo scripts with OIOUBL, FIK codes and batches

A Danish demo script has to go beyond a sales order and a dashboard. I write scenarios from your processes and add the local checks, then have every bidder perform them live on data you supply:

1. Issue an invoice, then a credit note, to a public customer in OIOUBL or Peppol format, with the location number and order reference the customer requires, and show what happens when one is rejected.
2. Take in a supplier e-invoice, send it through approval and book it with the correct VAT treatment.
3. Print an invoice with an FIK payment code, import a bank file containing the payment and match it automatically.
4. Sell to a customer in another EU country in euros, then show the VAT reporting fields and the exchange difference in kroner.
5. For life sciences or food: receive a batch, block it pending quality release, sell part of it and trace it forward.
6. For project or shipping businesses: cost a job or shipment and show its margin while still open.

Your team records, step by step, whether the result came from standard features, setup, an app or bespoke development. Your accountant reviews the VAT and payment results. Where an app is needed, its maintainer and licensing join the comparison. VAT and e-invoicing details should be confirmed with your advisor. The scoring approach follows my ERP evaluation method.

Choosing among Danish implementation partners

Business Central grew out of Navision, which was developed in Denmark, and Danish buyers usually find several partners ready to propose it. Odoo and other platforms have their own Danish implementers, from established firms to small specialists. More choice helps, but it also makes the comparison harder, because each partner frames the project in its own way.

I give every invited partner the same brief: company background, requirement annex, demo script and a response template that separates licenses, apps, implementation phases, migration, integrations, training, testing support and the ongoing service agreement. When the offers come back, I normalize them and list what each one assumes your staff will do. A low price that leaves data cleansing, testing and app subscriptions to you is not a low price.

I also look at who would be on your project. Named consultants, their experience with your industry, how the partner handles staff changes and how quickly support responds after go-live all matter more than the size of the firm. Structured reference calls with customers of similar size help confirm the picture.

If you would rather run a formal tender, my ERP RFP consulting page explains the document. For offers already on your desk, see the freelance ERP consultant page for Denmark.

Hosting, voucher storage and the agreement

GDPR applies to the customer, employee and supplier data your ERP will hold, and Danish bookkeeping expectations add questions about where vouchers and records are stored and how they are backed up. A cloud system hosted outside Denmark can be entirely acceptable, but the details belong in writing before signature.

Every vendor and partner answers the same short questionnaire: where production data, backups and attachments are held, which subprocessors are used, which people can reach your environment and whether their access is logged, which data processing agreement is offered, and how you would export all records and vouchers if you changed system. Your accountant and whoever owns data protection review the answers. Legal judgment is theirs; my role is to get every question answered and scored.

The agreement review then checks the statement of work and service agreement against the demo results. Typical points include e-invoicing access and Danish bank connections priced as separate subscriptions, acceptance based on the partner's own tests, change requests billed without your approval, and support terms that do not mention updates when Danish rules or formats change. Contract language itself is a matter for your lawyer.

After signature, the Danish implementation oversight I provide keeps delivery tied to the agreement. The Denmark overview and the ERP consultant page for Denmark describe how the wider remote engagement works.