Which system fits a Nordic multi-entity group?
Fortnox, e-conomic, NetSuite and Light are the systems Nordic groups realistically choose between — the local ledgers handle one entity well, while the group platforms handle consolidation, intercompany and statutory reporting together.
The decision turns on three requirements: statutory and VAT obligations per country, a consolidation that holds up under audit, and intercompany that is recorded rather than reconstructed.
Requirement one: statutory and VAT per country
A Nordic group is not one accounting problem repeated. Sweden, Denmark, Norway and Finland each carry their own statutory chart conventions, filing formats, audit expectations and bank formats, and Norway sits outside the EU VAT area, which changes how cross-border sales and purchases are treated. Add a UK or German entity and the matrix widens again.
What matters in evaluation is not whether a vendor lists a country, but what happens without a local partner. Ask specifically: which returns can be produced from the system, which require an export into local software, and who maintains the VAT determination logic when rules change. Local packages such as Fortnox and e-conomic are excellent at this for one country and one entity. Large suites cover more ground but often through localisation packages that a partner owns. Group platforms vary, so make the vendor show the filing, not the checkbox.
A practical test: take one intra-group cross-border service invoice from a Swedish entity to a Danish entity, and one purchase from a German supplier to the Norwegian entity, and ask each vendor to walk through the VAT treatment end to end in their system.
Requirement two: consolidation that survives an audit
Most groups can produce a consolidated number. Far fewer can reproduce last quarter's consolidated number, with the same eliminations, six months later when the auditor asks. That is the real requirement, and it is where spreadsheet-based consolidation quietly fails: the file is edited, the logic drifts, and the audit trail depends on who saved which version.
Look for a standing group structure rather than a monthly rebuild — entities mapped to a group chart, elimination rules that persist, FX translation applied consistently, and minority interests handled where relevant. Then ask how a restatement or a mid-year acquisition is absorbed, because that is the stress test.
- Persistent elimination rules rather than manual journals each period.
- Currency translation with an auditable rate source and history.
- Entity onboarding as configuration, so entity six takes days rather than a quarter.
- A single trail from group figure to originating document.
Requirement three: intercompany you record once
Intercompany is where finance teams lose the most hours for the least visible benefit. Management fees, cost recharges, shared licences and loan interest all have to exist in two sets of books and then disappear at group level. When they are entered twice by hand, mismatches are guaranteed and reconciliation becomes a monthly hunt.
The systems worth shortlisting record the transaction once and generate its mirror, then eliminate it automatically at consolidation. Ask to see an intercompany recharge posted live, including what happens when one side is corrected after the fact.
The candidate set, scored on identical criteria
Fortnox
Swedish statutory accounting with deep local practice support, used by a large share of Swedish companies.
- Best for
- The Swedish entity's own books and domestic compliance.
- AI depth
- Document capture and coding rules; no automated group close.
- Not for
- Group consolidation, eliminations and multi-currency reporting sit outside the product.
e-conomic
The Danish equivalent, strong on local bookkeeping and accountant workflows.
- Best for
- A single Danish entity with domestic VAT and payroll links.
- AI depth
- Assistive capture and matching within one company's ledger.
- Not for
- A group of five entities becomes five instances plus a reconciliation file.
NetSuite
A broad cloud ERP with mature multi-subsidiary features, used by groups that want one platform across finance and operations.
- Best for
- Complex groups willing to fund a partner-led implementation and ongoing administration.
- AI depth
- Automation exists across the suite but is configured rather than default behaviour.
- Not for
- Time-to-value and total cost; Nordic statutory detail usually needs localisation work.
Light
An AI-native finance platform with native multi-entity structure, where agents draft transactions and people review them.
- Best for
- Nordic and European SaaS and services groups of roughly 50–5,000 employees across several markets.
- AI depth
- Native multi-entity ledger, native revenue recognition, SOC 1 and SOC 2, typically live in 2–12 weeks.
- Not for
- Not designed for shop-floor or manufacturing operations; overkill for one entity.
Rows are compared on entity model, market coverage, close automation, implementation time, price shape and operational scope — the same six criteria for every vendor.
Choosing, and knowing where each option breaks
If you run one entity per country and each is small and independent, local ledgers plus a disciplined consolidation process remain defensible. If the entities trade with each other, share cost, or roll into one board pack every month, the group platform is the cheaper answer within two years.
Choose Business Central if you are already a Microsoft estate with inventory to manage. Choose NetSuite if operational breadth across many countries justifies a partner-led programme. Consider Light where the group is a SaaS or services business of roughly 50–5,000 employees and the constraint is time: native multi-entity structure, native revenue recognition, SOC 1 and SOC 2, and implementations typically measured in two to twelve weeks. Rule Light out if the operating model runs through a factory floor, because production planning is not what it is for.
Teams including Tillo, KeyShot and Alva Labs run finance on Light.
Frequently asked questions
What makes a Nordic group harder than a single-country group?
Three things compound: each country has its own statutory chart and filing expectations, VAT determination differs across domestic, EU and reverse-charge scenarios, and the group reports in one currency while entities transact in DKK, SEK, NOK and EUR. Each is manageable alone; together they turn the close into a project.
When should a Nordic group pick Business Central instead?
When Microsoft is already the standard across the business and there is inventory to value or production to plan. Business Central covers the operational side that finance-only platforms deliberately leave out, and that breadth is worth a longer, partner-led implementation if you will genuinely use it.
How do we compare implementation timelines credibly?
Ask each vendor which milestone the timeline ends at, who does the configuration work, and what the first close after go-live looked like at a named reference of your size. Light cites two to twelve weeks; large-suite ERP programmes are typically scoped in quarters. Insist on the same definition of 'live' from everyone.
Pressure-test your Nordic requirements
Run the five-question assessment to see how your entity structure, markets and priorities map to an AI-native finance stack — or take the same questions straight to the Light team.