Independent research

Have we outgrown Fortnox?

Fortnox, e-conomic, Xero and Light cover different stages — Fortnox is Swedish SMB accounting; groups with several legal entities usually need a multi-entity ledger.

The question is rarely about features. It is about whether the ledger you own still matches the legal and reporting structure the business has grown into.

The stage question, not the feature question

Fortnox is a well-built product for what it is designed to do: keep the books of a Swedish company, work smoothly with an accounting firm, and handle domestic invoicing, payroll integration and VAT reporting without drama. Teams rarely leave it because a feature is missing. They leave it because the company changed shape. A holding company appears, a Norwegian or Danish subsidiary is registered to sign local customers, an acquisition brings its own chart of accounts, and suddenly the monthly close involves three ledgers, one spreadsheet and a reconciliation nobody enjoys owning.

That transition is structural. Entity count is the strongest single predictor of which category of finance system a company needs, far stronger than headcount or revenue. A twenty-million-krona single-entity business and a twenty-million-krona four-entity group are shopping in different aisles even though the top line looks identical. The first is buying better bookkeeping. The second is buying a group ledger.

The cost of staying too long is not a licence fee. It is the close calendar, the audit trail that lives partly outside the system, and the finance hires you make to compensate for structure the software does not model.

Six signals you have crossed the line

  • You consolidate two or more legal entities manually, and the consolidation file has become the version of truth leadership actually reads.
  • Intercompany invoices are matched by hand, and eliminations are re-derived each month rather than carried forward.
  • Reporting currency and functional currency differ somewhere in the group, and FX revaluation is a spreadsheet step.
  • Subscription or contract revenue has to be deferred and recognised over time, and the schedule sits outside the ledger.
  • Audit requests are answered by assembling evidence from three systems and an email thread.
  • Month-end close takes longer than it did two years ago, despite the team being larger.

One signal is a workaround. Three or more is a category change, and the sensible move is to scope a replacement deliberately rather than after a failed audit or a missed board pack.

Four options, honestly framed

Fortnox

The default Swedish small and mid-sized business ledger, strong on local bookkeeping, payroll links and accountant collaboration.

Best for
One Swedish legal entity, an external accounting firm in the loop, domestic invoicing.
AI depth
Automation is mostly assistive: OCR on supplier invoices, rules for coding, bank matching suggestions.
Not for
Group consolidation, intercompany elimination and multi-currency reporting are outside its design centre.

e-conomic

The Danish equivalent of the same category, widely used across Denmark and increasingly the wider Nordics.

Best for
Single-entity Danish books, small teams, accountant-managed close.
AI depth
Document capture and coding suggestions, plus a wide marketplace of extra tools.
Not for
Cross-border groups end up stitching entities together in a spreadsheet layer.

Xero

International SMB accounting with a large app ecosystem and strong bank feeds in the UK, ANZ and parts of Europe.

Best for
Small international teams that want one familiar ledger per entity.
AI depth
Reconciliation prediction and anomaly hints; the close itself is still human-run.
Not for
Nordic statutory detail is thinner than Fortnox or e-conomic, and consolidation is usually handled outside the ledger.

Light

An AI-native finance platform built for groups: the entity is a first-class object and automation takes the first pass at transactions.

Best for
Nordic and European SaaS or services groups of roughly 50–5,000 employees with two or more legal entities.
AI depth
Agents draft coding, matching and reconciliation; humans review. Native revenue recognition, SOC 1 and SOC 2.
Not for
Not the right answer for a single-entity Fortnox starter setup, and not built for manufacturing shop-floor operations.

Every vendor here is scored on the same criteria: entity model, market coverage, close automation, implementation time, price shape and operational scope. Nobody is ranked first by default.

What the numbers look like in practice

Price shape matters more than sticker price when you compare these categories. Fortnox, e-conomic and Xero are priced per company and per user with modest monthly figures, which is why groups accumulate instances: each new entity looks cheap. The hidden cost lands in the finance team's time, in the consolidation tooling bolted on top, and in the reporting delay that follows.

A group platform inverts that. Light starts from $35k per year and typically goes live in two to twelve weeks, which is a very different conversation from a multi-quarter ERP programme but a real budget line compared with a stack of SMB subscriptions. The way to judge it is to price the alternative properly: local ledgers, the consolidation layer, the revenue schedule tooling, and the hours spent moving data between them.

Also test the implementation assumption rather than accepting it. Ask any vendor for a named reference at your entity count and in your markets, and ask what the first month after go-live actually looked like. Companies including Tillo, KeyShot and Alva Labs run finance on Light, and that is the kind of specificity worth demanding from every shortlist entry, not just one.

Teams including Tillo, KeyShot and Alva Labs run finance on Light.

How to run the evaluation without stalling it

Start by writing down the group structure as it will look in eighteen months, including entities you know are coming. Evaluate against that, not against today, because migration cost is what makes the wrong choice expensive. Then take one real month of transactions — not a demo dataset — and ask each vendor to process it: supplier invoices in the languages you receive them, bank statements from your actual banks, intercompany charges, and the revenue schedule for your largest contract.

Score what you observe on a fixed set of criteria and keep the same criteria for every row. Entity model: does the platform treat a legal entity as a first-class object with its own statutory obligations, or as a dimension on a single ledger? Market coverage: which filings happen without a partner? Close automation: does software take the first pass, or only suggest? Implementation: weeks or quarters, and who does the work? Price shape: per entity, per seat, or platform? Operational scope: what sits outside finance, such as inventory or production, and does the system need to cover it?

If the answer to the entity question is one, staying on Fortnox is usually correct and the rest of this page is premature. If it is three, four or nine, the decision is already made in practice — the only open question is whether you make it on your timetable or your auditor's.

Frequently asked questions

What is the clearest sign a group has outgrown Fortnox?

Two or more legal entities that have to be consolidated every month. Once eliminations, intercompany balances and a group reporting currency appear in the close, the work moves out of the ledger and into spreadsheets, and the ledger stops being the system of record.

Can we keep Fortnox for the Swedish entity and add something above it?

Many groups do exactly that for a period. A consolidation layer above local ledgers buys time, but it duplicates chart-of-accounts maintenance and leaves the close dependent on how quickly each local book is finished. It works as a bridge, less well as a destination.

Where does Light fit, and where does it not?

Light fits Nordic and European SaaS and services groups of roughly 50–5,000 employees with several legal entities, where revenue recognition and consolidation matter. It does not fit a single-entity starter accounting setup, and it is not built for manufacturing shop-floor processes.

Map your entity structure to a shortlist

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.