Every few years, the question of which ERP to use comes up in a growing Swiss company. Sometimes it is triggered by the business outgrowing its current system. Sometimes it is a new CFO who inherits a setup that was chosen five years ago by someone who no longer works there. Sometimes it is a growing frustration with reporting that requires too many manual steps and produces too many errors.

The market is full of ERP comparisons written by vendors, consultants with implementation relationships, or reviewers who have never actually closed a set of books on any of these systems. This one is written from the controller’s perspective: what it is like to do the actual work of financial reporting, variance analysis, and month-end close in each of these environments.

The three systems covered here, Abacus, Bexio, and SAP, cover the realistic choice set for most Swiss companies outside of the very largest enterprises. Each has a specific positioning, specific strengths, and specific limitations that matter enormously for the finance function.

Bexio: The Bookkeeping Tool That Grew Up

Bexio is the dominant small-business accounting platform in Switzerland. Its market success is justified: it is easy to set up, well-integrated with Swiss banking infrastructure, handles MWST correctly, and produces the basic accounting outputs a small company needs. For a business below about 15 employees and CHF 2M revenue, it is probably the right tool.

The limitation becomes apparent when the business grows. Bexio is fundamentally a bookkeeping platform. It records transactions accurately, but it was not designed for management accounting. The reporting layer is thin: standard P&L and balance sheet outputs, but minimal ability to slice by cost centre, project, or any dimension that is relevant for management reporting beyond the total.

Cost centre reporting in Bexio requires workarounds. You can tag transactions to cost centres, but producing meaningful cost centre P&Ls requires either using Bexio’s export and rebuilding the report in Excel, or adding a third-party reporting layer. Neither is a clean solution.

The month-end close in Bexio is straightforward for the accounting tasks it handles: bank reconciliation, invoice management, basic accruals. But the controlling layer, the variance analysis, the budget-to-actual comparison, the cash flow forecast, all of this has to be built outside Bexio because Bexio does not have the architecture to support it natively.

For a business that has outgrown Bexio, the typical sign is that the finance team is spending two to three days every month extracting data from Bexio, manipulating it in Excel, and building the management report manually. If that is your situation, Bexio is not the problem. It is doing what it was designed to do. The question is whether the business needs more than that.

Best suited for: Businesses below CHF 3M revenue, limited cost centre complexity, and teams without a dedicated controller. Service businesses with simple revenue structures.

Abacus: The Swiss Standard for Mid-Size Companies

Abacus is the closest thing Switzerland has to a market-standard ERP for mid-size companies. It handles the full range of Swiss accounting requirements cleanly: OR-compliant financial accounting, MWST, payroll with full Swiss social charge management, and fixed assets. It integrates well with Swiss banking and is supported by a large network of local implementation partners.

From a controlling perspective, Abacus is significantly more capable than Bexio. Cost centre reporting is built into the product properly: you can define a cost centre hierarchy, allocate costs, and produce cost centre P&Ls directly from the system without a major rebuild in Excel. The chart of accounts is based on the Swiss Kontenrahmen KMU, which is the standard Swiss account structure, and the system is flexible enough to extend it for management reporting needs.

The reporting in Abacus is serviceable for most Swiss mid-size company needs. Standard financial statements, cost centre reports, and budget comparisons are all producible within the system. Where Abacus shows its limitations is in advanced analytical reporting: multi-dimensional analysis, project-level profitability, and custom management report formats that go beyond the standard templates require either significant configuration effort or the addition of the Abacus BI module, which adds both cost and complexity.

The month-end close in Abacus is more structured than Bexio but still requires discipline. Abacus will not enforce a close sequence or prevent postings to closed periods without specific configuration. The ERP does what you tell it to do. If the team has not been trained on the close process and the system configuration does not enforce it, you can have the same data quality problems in Abacus that you have in any other system.

One specific observation: most Abacus implementations in Swiss SMEs are set up by accountants and Treuhänder whose primary purpose is statutory accounting, not management reporting. The result is a system that produces excellent statutory accounts and tax-compliant outputs but a management reporting layer that is thin or missing entirely. This is not an Abacus limitation. It is an implementation decision that can be corrected.

Best suited for: Swiss companies between CHF 2M and CHF 50M revenue, with a need for solid OR-compliant accounting, payroll, and cost centre reporting. Mid-complexity organisations where a local implementation partner relationship matters.

SAP (ERP Central Component and S/4HANA): Power and Complexity

SAP is the enterprise standard globally, and it is what most large Swiss companies and Swiss subsidiaries of international groups operate on. The SAP modules most relevant to the controller’s work are FI (Financial Accounting), CO (Controlling), and the reporting layers, either SAP BI/BW, SAP Analytics Cloud, or extractions into Excel.

The power of SAP from a controlling perspective is genuine. The CO module is built specifically for management accounting: cost centres, profit centres, internal orders, product costing, and profitability analysis are all native capabilities. When SAP is configured well and the team uses it properly, the management accounting output is more comprehensive and more reliable than what Abacus or Bexio can produce.

The month-end close in SAP is more structured than in smaller systems. Period locks, posting key controls, and the separation between FI and CO postings create a more controlled environment. The tradeoff is that errors upstream, a goods receipt posted to the wrong cost centre, an invoice approved without the correct account assignment, create distortions that are harder to find and correct than in a simpler system.

The honest limitation of SAP for smaller companies is not the system’s capabilities. It is the total cost of ownership and the expertise required to use it well. A SAP implementation for a mid-size company costs significantly more than Abacus and requires ongoing technical expertise to maintain. Standard SAP reporting, the reports that come out of the box, is not particularly user-friendly: most companies end up either building a custom reporting layer or extracting to Excel for the management pack.

SAP Business One, the version targeted at smaller companies, reduces the complexity and cost significantly while retaining the core accounting and controlling functionality. For Swiss companies in the CHF 10M to CHF 100M range that need multi-currency, intercompany, and multi-entity capabilities, SAP Business One is worth evaluating alongside Abacus.

Best suited for: Companies above CHF 20M revenue, multi-entity or international operations, businesses that are subsidiaries of groups running SAP centrally, or companies with complex manufacturing or project cost accounting needs.

The Decision Framework

The ERP choice is not primarily a technology decision. It is a finance function design decision. The right question is not which system has the most features. It is which system will support the financial reporting, controlling, and analysis the business needs for the next three to five years, at a total cost of ownership that is proportionate to the company’s size.

For a company considering an ERP upgrade or change, three questions are worth answering before any vendor conversations: what specific reporting and analytical capabilities does the current system not provide that are causing operational problems? What is the finance team’s realistic capacity to manage a more complex system? And what is the total cost of ownership including implementation, training, and ongoing maintenance, compared to the incremental value of the upgrade?

A note that applies to all three systems: if your management reporting is being rebuilt in Excel from ERP exports every month, the problem is almost certainly the reporting design and the system configuration, not the ERP itself. Fixing the reporting architecture within the current system is almost always faster and cheaper than an ERP change.

Need help getting better reporting from your ERP? Download professional Excel templates or book a free call.

Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).