Cost Centre

A cost centre is a unit against which expenditure is recorded: a department, a function, a site, a project. It absorbs cost and is not credited with revenue, which distinguishes it from a profit centre.

For HR the relevance is that every employee is mapped to one, and that mapping determines how their cost appears in financial reporting. A payroll run is, from finance's perspective, a distribution of cost across centres.

The mapping is an accounting decision rather than a management one, and this is the source of most of the friction. It is designed to produce useful financial reporting, which is not the same objective as describing how the organisation is actually run.

Ask HR how many people are in a function and ask finance the same question, and the answers commonly differ. Neither is wrong; they are counting different things.

The last row is a frequent cause of confusion in cost reviews, where a centre appears to be over budget on headcount that does not exist as people.

The productive response is not to force the structures to match, since they serve different purposes, but to be explicit about which question is being answered and to hold both mappings against the same employee record so the reconciliation is arithmetic rather than archaeology.

Salary is the visible part and often not the largest. What else is attributed determines whether one centre's cost per head can be compared with another's.

• Employer contributions and statutory costs, which vary with the composition of the workforce.
• Variable pay and bonus, which may land in a different period from the work.
• Benefits and insurance premiums, sometimes charged centrally and sometimes allocated.
• Recruitment and onboarding costs, which may sit with HR or with the hiring centre.
• Facilities, equipment and licences, which are frequently allocated on headcount and therefore penalise centres with more people rather than more consumption.

The last is worth watching. Allocating a shared cost on headcount makes a labour-intensive unit look expensive relative to a capital-intensive one, which is an artefact of the allocation rather than a finding about the unit.

Where cost per head is compared across centres, the comparison is only meaningful if the same elements are attributed in each. That is worth checking before any conclusion is drawn from the difference.

Cost centre structures are stable by design and organisations are not, so the mapping degrades continuously.

• Reorganisations move reporting lines immediately and the chart of accounts later, or never.
• New teams are created without a centre and are parked in an adjacent one, permanently.
• Closed centres remain open because historic transactions reference them.
• Employees transferred between units keep their old mapping until someone notices, often at year end.

The symptom is a cost report that nobody quite believes, followed by manual adjustment before it is presented, which then becomes the routine.

The control is to reconcile the mapping against the organisation structure on a schedule rather than after a query, and to make the cost centre a field on the employee record that changes with a transfer rather than a separate list maintained elsewhere.

Two misuses recur.

The first is treating cost centre performance as team performance. A centre that carries shared costs, absorbs an allocation, or holds a vacancy budget will look worse than one that does not, and none of that reflects how the people in it worked.

The second is using the cost centre structure as the organisation structure for HR purposes, because it is the one that exists in a system. Doing so produces approval routing that sends requests to whoever owns the budget rather than whoever manages the person, which is frequently not the same individual and is occasionally nobody.

Both are best avoided by keeping the two structures distinct and mapped, rather than collapsing them because maintaining one is easier than maintaining two.