Organisation
One organisation – one unit structure
Many public organisations assume the organisational structure lives either in the finance system or in the HR system. The result is two versions of reality that do not match.
By Jens Fahlén · Published · 6 min read
An organisation can only have one true unit structure. Yet many assume the structure lives either in the finance system or in the HR system. The result is two versions of reality that do not match – and neither system contains what a complete picture requires.
An obvious point often missed: there is only one unit structure
The formal unit structure is decided by the council, board or executive management: committees, administrations, departments and units. It is the organisation's official backbone and exists regardless of which system happens to handle it.
What is often missed is the difference between where the unit exists in reality and which system handles it for a particular purpose. Once that difference is blurred, the question "which system is master for the organisation?" cannot be answered – because neither of them is.
The limited lens of the finance system
The finance system is built for charts of accounts, budgeting, invoicing and reporting. It contains cost centers, responsibility codes and dimensions – not organisational units.
A cost center carries no employer responsibility, no legal entity and no workplace, and rarely reflects manager and employee relationships correctly. When the finance system is used as the organisation, temporary projects, allocation codes and fictitious accounts suddenly count as units.
The limited lens of the HR system
The HR system is built for employment contracts, salary reviews, employment law, time reporting and union reporting. It contains employment trees, management lines and salary structures.
The financial dimension is missing: cost centers with approval rules do not exist, and units that currently have no permanent staff are invisible.
The HR system's blind spot: external personnel
The most important thing to remember is that the HR system only sees people with an employment contract. Consultants, subcontractors, contracted specialists, agency staff and hired care or school personnel simply do not exist in HR's view of the organisation.
At the same time, these are the people doing the daily work in the units. They are led by the unit managers, need system permissions, access cards and equipment – and need to be followed up just like employees. An organisational picture built on employment contracts therefore misses a large share of the people actually working in the organisation.
Why neither of them is complete
Comparing what a complete picture requires with what the two systems hold makes it clear. The formal unit is distorted in both – it becomes either a cost center or a payroll group. The workplace, the geographical and legal establishment, is usually missing in both. Cost centers with approval rules exist only in finance. Managers with employer responsibility exist only in HR. External personnel and business services are missing in both.
The sustainable solution: the unit as a shared information set
The unit structure must be managed as its own, central information set – an organisational register that both HR and finance read from and enrich with their own objects. The starting point is a unit tree with one parent unit and two subordinate units.
Good solution
Manager, responsibility and employees on every unit
Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.
- Explanation
- Every unit in the tree – including the parent unit – has one manager with people responsibility, its own cost center one-to-one, and employees employed in the unit. The parent unit's manager leads their own staff while being responsible for the subordinate units through the unit hierarchy.
- Rationale
- One structure, one truth. Responsibility, finances and people hang together at every level, external personnel can be tied to the unit through the person without passing through the employment register, and business services can be published without leaking the internal structure. See Pattern B.
One detail the diagram deliberately leaves out is where the managers themselves are employed. The manager of a subordinate unit holds two relationships at once: the management relationship points downwards to the unit being led, while the employment points upwards to the parent unit – where their own manager sits and employer responsibility rests.
Keeping the two apart matters. Leading a unit is an assignment within the structure; being employed is a relationship to a unit. Both point towards the unit, but they mean different things and must never be merged into one connection.
The less good solutions: two partial unit trees
Both less good solutions start from a deeper unit tree with four units: one parent unit and three subordinate units. The difference lies in what is missing.
Less good solution
Less good solution 1: the finance system's unit tree
- Explanation
- The three lowest units each have their own cost center and point up to the parent unit. Managers and employees are absent from the model, and the parent unit has neither a cost center nor a responsible manager.
- Rationale
- Costs can be summed upwards mathematically, but there is no manager on the parent unit to show the total to or grant approval rights. The structure describes the path of the money, not the path of responsibility.
Less good solution
Less good solution 2: the HR system's unit tree
Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.
- Explanation
- HR follows the same four units, but cost centers, employees and managers are attached only to the three lowest units where salaries are coded. The parent unit is an empty shell without a manager and without staff, and external personnel are missing entirely.
- Rationale
- The management chain breaks on the way up: there is no staffed parent unit to aggregate to, and headcount only reflects people with employment contracts – not the consultants and agency staff doing the work.
Aggregating data to managers of parent units
As soon as information has to be summed up and shown to managers higher in the organisation, the partial models become unusable.
In the finance model the total can be calculated, but there is no recipient. The parent unit has no manager, so the system does not know who should see the consolidated picture, who should approve, or who should be granted access to the subordinate units' data. The sum exists – the responsibility does not.
In the HR model the managers exist at the bottom, but the chain upwards is broken. The parent unit is unstaffed, so report recipients and permission levels must be maintained manually in every report and every system. The volumes are wrong as well: consultants, agency staff and contractors are left out even though they do the work.
In the complete model the unit tree works in both directions. Bottom-up, costs, people, cases and key figures aggregate automatically to every parent unit, together with that unit's own staff data. Top-down, read and approval permissions follow the same hierarchy. And because both employees and external personnel are tied to the unit, the aggregated picture shows reality – not just the payroll.
The consequences in practice
The IT function faces an impossible question: should permissions and identities be driven from finance or from HR? Choosing HR shuts all external personnel out of automatic provisioning and loses the link to costs. Choosing finance brings in project codes that are not units, and leaves out the managers with people responsibility.
The effect shows up in everyday work: the consultant gets permissions manually as an exception, the approval flow stalls, and reports per manager either double-count or leave gaps.
The principle
Finance and HR use the organisation's unit structure – they do not own it. Only when the structure is managed jointly can both employees and external personnel, both money and responsibility, be described in the same information set.
Tags
- #unit
- #cost center
- #hr
- #finance
- #master data