Cost centre reporting is one of those topics that sounds technical but is fundamentally a business design question. Before you configure anything in your ERP, before you map a single account, you need to answer one question: how does this business actually make and spend money, and how does leadership need to see that information to make good decisions?
Get that question right and the rest is implementation. Get it wrong and you will spend years producing reports that nobody trusts, reclassifying postings that went to the wrong centre, and explaining to frustrated managers why the numbers in the system do not match their intuition of how their part of the business is performing.
This article walks through the full process: defining your cost centre structure, mapping it in your ERP, handling shared costs, and producing meaningful cost centre P&Ls. It is written for Swiss companies using SAP, Abacus, or similar ERP systems, but the logic applies regardless of the platform.
Step 1: Define Your Structure Before Touching the System
The most common mistake in cost centre implementations is opening the ERP configuration before the structure has been agreed. The system will accept almost anything you put into it. That flexibility is a trap. An ERP configured with a poorly designed cost centre structure is harder to work with than one with no structure at all, because the bad structure produces reports that look credible but are analytically wrong.
Start with a blank piece of paper and ask three questions.
What decisions does management need to make? If the CEO needs to compare the profitability of three product lines, those are your three profit-oriented cost centres. If the CFO needs to monitor IT costs separately from facilities costs, those are two overhead cost centres. If the business operates across two locations and performance needs to be compared, those are two geographic cost centres. The structure should follow the decision, not the org chart and not the accounting hierarchy.
What is the right level of granularity? More cost centres means more analytical detail but also more maintenance burden. Every cost centre you create needs to be populated with postings, reviewed each month, and explained when it behaves unexpectedly. A structure with fifty cost centres in a business with eighty employees is almost certainly too granular. A structure with two cost centres in a business with five product lines is almost certainly too aggregated. The right answer is usually between five and twenty cost centres for a Swiss SME, depending on complexity.
How will shared costs be handled? Almost every business has costs that serve multiple cost centres: rent, IT infrastructure, HR administration, senior management time. Deciding in advance how these will be allocated, and at what level of precision, prevents a significant amount of monthly confusion. More on this in Step 4.
Step 2: Design the Structure
A cost centre structure typically has two layers: a top level that reflects the business model, and a detail level that provides the analytical granularity management needs.
For a manufacturing company, the top level might be: Production, Sales and Marketing, Administration, and Group (for items that genuinely cannot be allocated). For a services firm, it might be: Client Service Delivery, Business Development, Operations, and Group. For a multi-location retail or hospitality business, the top level is usually geographic: each location is its own cost centre or profit centre, with a central overhead pool allocated across them.
Within each top-level unit, you may want sub-cost centres if the detail is genuinely needed for management decisions. A Production unit might break down into Assembly, Quality Control, and Logistics if each of those has meaningful standalone cost visibility. But resist the temptation to create sub-cost centres speculatively, just in case someone wants the detail later. Start with the minimum structure that answers the real management questions, and add granularity when there is a specific need for it.
The structure should also distinguish between cost centres, which track costs only, and profit centres, which track both revenues and costs to produce a bottom-line contribution. If your business has segments where you want to see a full P&L, configure them as profit centres. If you only need to see cost visibility for a given unit, a cost centre is sufficient.
In the Swiss context, your structure also needs to be compatible with OR-compliant statutory reporting. The segmented management P&L and the statutory Jahresrechnung draw from the same posted data, so the cost centre structure cannot conflict with the chart of accounts used for statutory purposes. In practice this means ensuring that the account-to-cost centre mapping is consistent and that any management-level reclassifications are documented and reconcilable back to the statutory accounts.
Step 3: Map the Structure in Your ERP
Once the structure is agreed on paper, the ERP configuration is relatively straightforward, though the details vary by system.
In SAP, cost centres are configured in the CO (Controlling) module. Each cost centre is assigned to a controlling area, a cost centre category (production, administration, sales, and so on), and a hierarchy node that determines how it rolls up in standard reports. The chart of accounts in FI maps to cost elements in CO, and every posting that hits a cost-relevant account must be assigned to a cost centre. Mandatory cost centre assignment can be enforced through field status groups, which means incomplete postings are rejected rather than landing in a suspense account.
In Abacus, cost centres are configured as Kostenstellen within the accounting setup. The mapping between accounts and cost centres is defined in the account properties, and allocations can be configured as fixed percentages or driver-based rules. Abacus handles the basic cost centre structure well for Swiss SMEs, though its management reporting layer requires more manual configuration than SAP to produce segmented P&Ls in a flexible format.
In Bexio, cost centres are supported but the functionality is limited relative to the other two systems. Bexio is suitable for basic cost tracking across a small number of cost centres but is not the right platform for complex multi-dimensional management reporting.
Regardless of the system, three configuration principles apply universally.
Every posting must hit a cost centre. Postings that land in a default or catch-all cost centre are a sign that the coding rules have not been enforced upstream. Audit your default cost centre balance monthly and drive it to zero.
The cost centre structure in the ERP must match the structure agreed in Step 2. It sounds obvious, but ERP configurations frequently diverge from the intended design as people add cost centres ad hoc over time without updating the reporting framework. Maintain a master document of the intended structure and review it annually.
Train everyone who posts transactions. A goods receipt posted to the wrong cost centre by a warehouse operative produces the same analytical distortion as a deliberate misposting. The people who touch the system need to understand the rules well enough to apply them correctly.
Step 4: Allocate Shared Costs
Shared costs are where most cost centre implementations get messy. The allocation question has no universally correct answer, but it has several clearly wrong ones.
The wrong answers are: not allocating at all (which leaves overhead costs in a pool that is never assigned to the business units consuming them), allocating everything on a single driver that does not reflect reality (allocating IT costs by headcount when some departments use almost no IT), or allocating with such precision that the allocation process takes more time each month than the value of the insight it produces.
The right approach is proportional to the materiality and complexity of the shared cost. For most Swiss SMEs, a pragmatic allocation framework looks like this.
For facility costs (rent, utilities, building maintenance): allocate by square metres occupied. This is measurable, objective, and relatively stable month to month. Set the allocation percentages once a year and update them only when the space usage changes materially.
For IT and systems costs: allocate by number of users or by number of active licences. IT costs that are genuinely infrastructure-level and serve the whole business equally can reasonably be allocated by headcount.
For central management and administration costs: the most common approach is to allocate by revenue contribution. The larger a business unit’s share of total revenue, the larger its share of central overhead. This is a simplification, but it produces a result that is defensible and easy to explain to business unit managers.
For HR and recruitment costs: allocate based on headcount in each cost centre, either at the time of the expenditure or as a fixed percentage updated annually.
Document your allocation methodology and make it visible. The single biggest source of disputes about cost centre reporting is when a business unit manager does not understand why a certain cost has been allocated to their centre. A one-page allocation methodology document, shared with all cost centre owners at the start of the year, eliminates most of those conversations.
Step 5: Produce the Monthly Cost Centre P&L
With the structure in place and the allocations defined, the monthly cost centre P&L should be a near-automatic output of the close process rather than a manual exercise.
The format that works best for most businesses is a contribution margin approach: show revenue at the cost centre level (if applicable), then direct costs, then a contribution margin, then allocated shared costs, then a net operating result. This format makes it immediately visible whether a business unit is covering its own direct costs and how much it is contributing to shared overhead.
For cost-only centres (administration, IT, HR), the format is simpler: budget versus actual for each major cost category, with a total variance and commentary on anything material.
The cost centre P&L should be part of the monthly management report package, not a separate document that circulates independently. Business unit managers should receive their own cost centre view alongside the consolidated company report. They need to see their numbers in the context of the whole business, not in isolation.
A few things to check each month before distributing the cost centre reports. The default cost centre balance should be zero or near-zero. The sum of all cost centre results should reconcile to the consolidated P&L. Any cost centre that shows a significantly different result from the prior month warrants a check before the report goes out, because unusual movements are often caused by a posting error rather than a business event.
The Payoff
A well-designed cost centre structure pays back its implementation cost within a few months of operation. The payback comes in several forms: faster identification of underperforming business units, clearer accountability for cost discipline among department managers, better data for pricing and investment decisions, and a more credible conversation with the bank or potential investors who want to understand the business at a segmented level.
It also makes the controller’s monthly work more efficient, because the data is organised the way the analysis needs it to be, rather than requiring manual reworking after each close.
Cost centre reporting is not a luxury for large companies. It is a basic management infrastructure for any business that needs to understand where its money is coming from and where it is going. The earlier it is built, the more useful it becomes.
Ready to improve your financial reporting? Book a free 30-minute call to discuss your situation.
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).
