Horizon Visma -

Visma’s strategy, often dubbed the “house of brands,” leveraged the trust inherent in local providers. A Finnish accountant would rather use a product named “Procountor” (a Visma acquisition) than a generic European brand. This allowed Visma to dominate market share rapidly. However, this came at a cost: technical debt. Integrating dozens of legacy codebases into a single cloud ecosystem (Visma Sky) has been a Herculean, decade-long task.

Yet, Visma had a secret weapon: private equity. Backed by Hg and later CVC Capital, Visma could outspend Horizon on R&D and acquisitions. When Horizon faltered in mobile user experience, Visma bought the best mobile-first startup in the region. When Horizon struggled with e-invoicing standards, Visma simply acquired the company that wrote the standard. horizon visma

The true battleground was not the software, but the accountant. Visma understood that in Europe, the accountant is the ultimate decision-maker for SME software. By acquiring accounting firms themselves (a controversial move), Visma locked in users. Horizon, sticking to a pure software vendor model, relied on partner channels. During the COVID-19 pandemic, when governments needed rapid payroll loan processing, Visma’s owned accounting firms could pivot overnight. Horizon, reliant on independent partners, suffered a two-month lag. Visma’s strategy, often dubbed the “house of brands,”

In the annals of European enterprise software, few rivalries have been as consequential—or as complementary—as that between Norway’s Visma and the Anglo-Dutch entity Horizon (formerly known as Exact and its associated brands). While neither is a household name like Salesforce or SAP, their battle for control of the small-to-medium enterprise (SME) accounting space has fundamentally altered how Northern Europe does business. The story of Horizon and Visma is not merely one of competition; it is a masterclass in two divergent strategies: Visma’s aggressive, debt-fueled roll-up of vertical software houses versus Horizon’s product-centric, platform-integration approach. However, this came at a cost: technical debt

The watershed moment arrived with the EU’s Open Banking directives (PSD2) and the forced shift to cloud compliance. Visma’s fragmented model initially struggled with API standardization—getting a payroll app in Oslo to talk to an inventory app in Copenhagen was a nightmare. Horizon, with its monolithic cloud architecture, sailed through this transition, offering bank feeds and automated reconciliation years ahead of its rival.

Today, the lines have blurred. Horizon has been largely subsumed into broader groups (with parts sold to Visma’s allies), while Visma has finally unified its core data model under “Visma.net.” The essay’s verdict is this: Horizon won the product war—its architecture was cleaner, its APIs more robust. But Visma won the market war—its understanding of local trust, distribution, and financial engineering proved unbeatable.