As a mid-sized company adds subsidiaries, foreign currencies, and reporting complexity, the consolidation tool it uses becomes one of its most consequential infrastructure choices. Most companies outgrow manual spreadsheet consolidation between five and ten entities. When they evaluate alternatives, they face a choice between cloud-based platforms (SaaS, hosted by the vendor) and on-premise solutions (installed on internal servers, managed by internal IT). For most mid-sized companies evaluating this decision today, the context has shifted significantly: the question is no longer whether cloud is secure enough — it is — but whether the specific requirements of the business make on-premise genuinely preferable.
The Comparison at a Glance
| Dimension | Cloud (SaaS) | On-Premise |
|---|---|---|
| Deployment | Hosted by vendor on managed infrastructure | Installed on company-owned or leased servers |
| Implementation time | Weeks to months | 6–18 months typical for mid-sized companies |
| Software updates | Automatic; new features and standard updates delivered without IT involvement | Manual; each version upgrade requires IT project management |
| IT overhead | Minimal; infrastructure managed by vendor | Significant; requires internal IT for maintenance, security, backups, DR |
| Accessibility | Any device, any location, browser-based | Typically internal network or VPN; remote access requires additional configuration |
| Scalability | Elastic; new entities and users added without hardware changes | Constrained by physical infrastructure; scaling requires procurement and deployment |
| Cost model | Subscription (OPEX); predictable annual cost | Licence + hardware (CAPEX); significant upfront, ongoing maintenance costs |
| Customisation depth | Configured within platform parameters | Deep customisation possible but expensive and complicates future upgrades |
| Data residency | Depends on vendor — ask about regional hosting options | Data stays on company infrastructure in chosen location |
Why Cloud Has Become the Default for Mid-Sized Companies
Accounting standards change — and cloud platforms update automatically
Consolidation software must stay current with evolving accounting standards: IFRS 16 (leases), IFRS 17 (insurance contracts), changes to IFRS 10, and others. Cloud vendors absorb this maintenance — standard updates are deployed across the platform and available to all customers without an internal IT project. On-premise customers must upgrade their installation each time a standard change requires a software update, which typically means an IT project, testing, and a period of uncertainty during the transition.
For mid-sized finance teams with no dedicated software implementation capability, this maintenance burden of on-premise solutions accumulates significantly over a five-year horizon.
Implementation speed matters for growing groups
A cloud consolidation platform can typically be configured and deployed for a mid-sized group in four to twelve weeks. On-premise implementations at the same scale routinely take six to eighteen months — time during which the group continues running its consolidation manually or on the legacy tool while the new system is built out. The opportunity cost of eighteen months of continued manual consolidation is significant: delayed reporting, continued error risk, and finance team time consumed in the old process rather than building capability on the new one.
Distributed teams are the norm, not the exception
Group finance teams with subsidiaries across multiple countries cannot all work from the same office. Cloud platforms provide browser-based access from any location, supporting the distributed working model that multi-entity groups require. On-premise systems accessible only via VPN create friction that is manageable for a single office but becomes genuinely limiting when entity controllers in Singapore, the UK, and Australia need to submit data on the same close timeline.
When On-Premise Still Makes Sense
For most mid-sized companies, cloud is the right choice. But there are genuine scenarios where on-premise remains preferable:
- Highly regulated industries with specific data sovereignty requirements: Defence contracting, certain financial services, and government-adjacent organisations may face regulatory requirements that specify data cannot leave company-controlled infrastructure. These are real constraints, not preferences.
- Significant existing on-premise infrastructure investment: A company that has invested heavily in an on-premise ERP ecosystem, with established IT teams and DR capabilities, may find that consolidation on-premise integrates more naturally with its existing architecture than a cloud platform that requires building new integration points.
- Deep customisation requirements: Where the consolidation process has highly specific workflow requirements that a SaaS platform cannot accommodate within its configuration parameters, on-premise allows system-level modification. This is rare for consolidation — most groups’ requirements are well within what cloud platforms support — but it exists.
💡 The honest on-premise assessment: Many companies cite “data security concerns” as a reason to prefer on-premise — but enterprise cloud vendors typically invest more in security infrastructure than any mid-sized company’s internal IT team can. The genuine on-premise advantage is control and sovereignty, not security per se. If the requirement is “we must know exactly where the data is and who controls the servers,” that’s a legitimate on-premise argument. If it’s “cloud feels less secure,” the evidence doesn’t support that.
Data Residency and Compliance — A Genuine Consideration
For multi-jurisdictional groups, data residency is worth examining specifically rather than assuming it’s handled. Groups with EU-based entities need to understand whether their consolidation vendor stores data in the EU (UK GDPR and EU GDPR compliance). Groups in Singapore face PDPA requirements. Australian operations have obligations under the Australian Privacy Act.
When evaluating a cloud consolidation platform, ask specifically:
- In which countries are the primary and backup data centres located?
- Can data from UK or EU entities be restricted to UK/EU infrastructure?
- What certifications does the vendor hold (ISO 27001, SOC 2 Type II)?
- Are there data processing agreements available for GDPR compliance?
A vendor that cannot answer these questions with specificity should not be given access to group financial data.
TCO Over Five Years — Where the Real Difference Appears
| Cost category | Cloud | On-Premise |
|---|---|---|
| Initial licensing / setup | Low (subscription); implementation services fee | High; software licence + hardware procurement |
| IT staffing (annual) | Minimal; vendor manages infrastructure | Significant; dedicated IT resource for maintenance |
| Version upgrades | Included in subscription | IT project cost at each major version; typically every 2–3 years |
| Disaster recovery | Included; vendor manages multi-region redundancy | Separate DR investment required |
| Standard updates (IFRS) | Delivered automatically | IT project required for each standard-driven update |
| Scalability cost | Incremental subscription cost per additional entity/user | Hardware procurement + IT deployment project |
The on-premise TCO advantage — where it exists — is typically in large-scale deployments with high user counts where perpetual licensing costs less than ongoing subscription fees at scale. For mid-sized companies with fewer than 50 active users, cloud is typically lower TCO over a five-year horizon when IT staffing and upgrade costs are included.
Five Questions to Frame the Decision
- Do we have regulatory or sovereignty requirements that mandate data stays on our own infrastructure? If yes, on-premise may be necessary. If not, cloud is likely appropriate.
- How many entities do we expect to have in five years, and how distributed will the finance team be? Growth trajectory and distribution both favour cloud.
- How much internal IT capacity can we dedicate to maintaining a consolidation system? If the answer is “limited,” on-premise ongoing cost is underestimated in every evaluation.
- How often do our consolidation requirements change (new standards, new reporting lines, new entities)? Frequent change favours cloud’s automatic update model.
- What is our timeline to replace the current process? If urgency is high, cloud’s shorter implementation timeline is a direct advantage.
BrizoConsol is a cloud-based consolidation platform — hosted on regional infrastructure with data residency options for Singapore, UK, and Australia — designed specifically for mid-sized multi-entity groups. Learn more or see it in action →