ERP Selection Consultant, Norway

How Norwegian shortlists differ by company size

Most Norwegian companies come to an ERP selection from a cloud accounting service such as Tripletex, PowerOffice or a Visma product, often surrounded by a separate project tool, a webshop and spreadsheets. The first question is whether that combination really has to go, or whether better integration would carry the business through its next stage.

When a change is justified, the shortlist depends on shape more than headcount:

• Service and technology firms with simple stock often compare Zoho or Odoo against keeping the accounting service and adding a stronger CRM and project tool.
• Wholesalers and product companies usually test Odoo against Dynamics 365 Business Central and Nordic ERP products their peers also consider.
• Asset-heavy or manufacturing firms that want open-source control can add ERPNext, knowing that more of the Norwegian localization becomes their own work.
• Groups with several companies look hard at consolidation and intercompany, which often narrows the list quickly.

I keep the list short enough that each option gets a proper test. Background on each platform in a Norwegian setting is on the pages for Odoo in Norway and ERPNext in Norway.

Selection for project, rental and offshore businesses

Plenty of Norwegian companies weighing an ERP do not simply buy and sell goods. They run jobs for energy and maritime customers, rent out equipment, manage crews or deliver long service contracts. Generic demo scripts tell them almost nothing.

For these businesses I write scenarios that follow money through a real job. A request arrives from an operator with its own purchase order format. A quote becomes a contract with a rate schedule in dollars. Equipment goes out on hire and comes back damaged. A subcontractor invoices in euros. A change order adds scope halfway through. The client's portal rejects the first invoice because a reference is missing. At the end, the job shows its margin while still open, not weeks after the final invoice.

Watching each bidder handle that sequence reveals far more than a feature list. Some platforms manage job costing natively, others rely on an add-on or a separate project system, and some need custom work for rental or vessel tracking. Each answer has consequences for cost, upgrades and partner dependency, so I record them in the scoring sheet with the evidence behind them.

Industry context for this kind of work sits on my engineering ERP page, and the job costing page looks at the problem from the finance side.

The Norwegian tests every bidder should pass

Every serious platform claims Norwegian support. The useful question is what that support looks like with your data, so I ask each bidder to run these checks live:

1. SAF-T export. Post a set of realistic transactions, map your accounts and VAT codes to the standard codes, export the file and have your accountant review it.
2. EHF outbound. Send an invoice and a credit note to a test public buyer, with the order reference and contact the buyer requires, and show what happens on rejection.
3. EHF inbound. Receive a supplier invoice, route it for approval and post it with the right VAT code.
4. KID matching. Issue an invoice with a KID reference and import the bank file that pays it.
5. Goods to the EU. Ship an order to a customer in an EU country with commodity code, origin and delivery terms carried onto the documents.

Where a bidder passes only with a third-party app, I note who supplies and maintains it. Rules and file versions change, so confirm current requirements with your accountant and bank. My ERP business analyst page for Norway explains how these needs are written up as requirements before selection begins.

Comparing offers from Norwegian partners

Norwegian implementation offers can look similar on the first page and differ widely further in. One partner prices a fixed scope with tight assumptions, another offers an estimate on hourly rates, another bundles localization, EHF connectivity and support into a monthly fee. Laid side by side without adjustment, the cheapest looking offer is often simply the one that excluded the most.

I normalize the offers into the same structure: licenses or subscriptions, localization and connector apps, implementation phases, data migration, integrations, training, testing support and support after go-live. For each line I record what is included, what the partner assumes your staff will do and what is explicitly excluded. Missing items become clarification questions sent to every bidder at once, so nobody gains an advantage from a private conversation.

I also look at who would actually do the work. Named consultants, their experience with the chosen platform in Norway, and how the partner covers holidays and staff changes all matter on a project that runs for many months. Reference calls with customers of a similar size help confirm what the offer promises.

The method follows my ERP vendor selection service, and the vendor proposal review page covers offers you have already received.

Data location, accounting records and the contract

Norway follows GDPR through the EEA, and Norwegian bookkeeping rules also say something about where and how accounting records are kept and how long they must stay available. A cloud ERP hosted in another country can be perfectly acceptable, but the question deserves a written answer before you sign, not after an auditor asks.

I send every vendor and partner the same short questionnaire: where production data and backups are held, which subprocessors are involved, who can access your environment and how that is logged, what data processing agreement they offer, and how you would extract all data, vouchers and attachments if you left. The answers go to your accountant and whoever handles data protection, who judge whether they are acceptable. I do not give legal advice; I make sure the questions are asked while you can still negotiate.

The contract review then checks the statement of work against the demo results. I look for localization and EHF connectivity priced separately from the main offer, acceptance tied to the partner's own tests, change requests without client approval, support terms that ignore regulatory updates, and subscription prices quoted in a currency different from your books. Final wording stays with your legal advisor.

When the contract is signed, my ERP implementation consultant role for Norway keeps delivery tied to it. The Norway overview and the ERP consultant page for Norway describe the wider remote engagement.