Horizon Visma File

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.

Conversely, Horizon focused on building a single, cohesive cloud platform. By unifying CRM, inventory, and accounting into one interface, Horizon offered seamless real-time data that Visma’s patchwork quilt could not initially match. For the digitally native SME, Horizon’s offering was superior. But Horizon struggled with localization; its software often felt like a Dutch product exported to Sweden, rather than a native Swedish solution. 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. The watershed moment arrived with the EU’s Open