Cost centres and responsibility: defining where financial control belongs

A cost centre identifies a meaningful area of responsibility for financial activity. It can represent an overhead function, project, phase, activity or resource. Its purpose is to answer who or what the spending belongs to, rather than merely provide another code on a transaction.

A clear structure helps managers compare like with like. Combining unrelated projects in one centre can hide overspending; splitting every minor activity into a separate centre can make the structure difficult to maintain.

DNA's hierarchy

DNA's Cost Center master organises classes, groups, subgroups and cost centres. The cost-centre record carries its type, active status, budget-control level, warning threshold, default expense and revenue accounts, manager and budget controller. Project-related settings include dates, fiscal-year bridging and the preferred budget timeline.

These fields serve different purposes. The hierarchy organises responsibility. The manager and controller identify responsible roles. Default accounts provide starting financial classification. A warning threshold determines when attention is needed under the configured control. One field should not be used as a substitute for the others.

A practical structure

Northstar Services wants to distinguish recurring head-office costs from a customer installation project. The office centre represents overhead responsibility. The project centre represents the installation's defined scope and dates. Both may incur travel, but the same expense type belongs to different business responsibilities.

Assigning both to one centre would make it harder to explain whether office spending or project delivery caused a variance. A meaningful structure keeps the responsibility visible while allowing related centres to be reviewed together.

Dates and responsibility change

A project that crosses a year-end needs a timeline that represents the full work and its reporting periods. A fiscal-year view and a project-life view answer different questions. The master settings support that distinction, but a selected timeline does not prove every transaction has been assigned correctly.

Changes to responsibility also need context. A new manager needs the open commitments and explanations behind the figures, not only a changed name. Likewise, deactivating a centre is not a substitute for resolving its remaining operational work.

Good assignment makes control meaningful

A correctly calculated transaction charged to the wrong centre can still produce misleading budget results. The centre should reflect the work that benefits from the cost and the organisation's agreed responsibility model.

The hierarchy is useful when a reviewer can move from a broad responsibility to the specific centre, budget and transactions that explain its performance. The aim is understandable accountability, not the longest possible code.