When cost allocation bases go stale

The most common failure in cost management is an allocation basis that stops matching how work is done. Drivers are measured at setup, then left alone while operations change. Indirect costs keep flowing to cost objects on old ratios, so unit costs, bills and budget requests quietly drift from reality.

How it starts

It rarely begins with a mistake. When the cost model is built, someone determines the key cost drivers with real care. Headcount might drive facilities cost. Transaction volume might drive shared processing. Machine hours might drive maintenance. Those choices are sound on the day they are made.

Then the organisation moves. A team goes remote and stops using the floor space it is still charged for. A new system automates a task, so volume no longer tracks effort. A program winds down but its cost center stays open and keeps absorbing overhead. Nobody changes the allocation basis, because nobody owns the job of checking it.

The basis often lives in a spreadsheet or a static table in the ledger. Updating it feels like a technical chore. Under close pressure it gets skipped, and skipping it once makes skipping it again easier.

Why it hides so well

The totals still balance. Every dollar of indirect cost lands somewhere, so pool-level reconciliations pass. The general ledger ties out. Financial statements trace cleanly. The damage sits below the surface, in how cost is split between cost objects, and that split is exactly what most controls never test.

How it gets spotted

The first signal usually comes from outside finance. A program manager disputes a charge and cannot see why their share of shared services rose when their use of them fell. Treat that complaint as data. One dispute can be noise. A pattern of disputes from the same direction points at the basis.

Other clues appear in cost reporting. Unit costs for a service move while the underlying activity stays flat. A cost object that should be shrinking shows rising overhead. Reimbursable work gets billed at rates that customers challenge, because the cost information feeding the invoice reflects an old mix.

Budget formulation can expose it too. When a budget request built on reported costs looks oddly inflated for one activity and thin for another, the allocation is a likely suspect. So is a cost center that should have been closed but still collects charges.

A useful test is simple. Take the current allocation ratios and set them beside a fresh measurement of each driver. Where the gap is wide, the basis has gone stale.

Questions to ask the people who run it

The documented model and the working model often differ. Staff close to the work will know where. Ask them:

• When was each driver last measured, and who did it?
• Where does the allocation basis physically live, and who can edit it?
• Do you ever override the system allocation by hand at month end? Why?
• Which cost centers or projects are still open but no longer active?
• Which charges do managers push back on most often?
• When a new service or team appears, how does it get a share of overhead?
• Is there a driver everyone knows is wrong but nobody has time to fix?

Manual overrides deserve special attention. They are usually a sign that someone noticed the problem and patched it locally without fixing the source.

Fixing it

Start by measuring the drivers again from current activity data. Use operational sources where possible: badge records, ticket systems, usage logs. Estimates from managers are a fallback, not a first choice.

Next, check whether each driver still reflects what causes the cost. Measurement alone is not enough. If automation has broken the link between volume and effort, a new driver may be needed. Determine which activities are now critical and which have faded, and let that reshape the pools.

Close out cost centers, pools and cost objects that no longer represent real work. Leaving them open invites leakage.

Then rerun the allocation and compare old against new results by cost object. Decide with the controller whether prior periods need restating. Where costs fed into customer billing, check whether invoices must be adjusted. Where they fed a budget submission, tell the budget office what changed and why.

Explain the change to affected managers before the new figures land. A shift in charges with no warning creates more disputes than the stale basis did.

Keeping it fixed

Give the allocation basis a named owner. Put a driver review on the planning calendar, tied to budget formulation so the refreshed numbers inform the next request. Require that any new cost center, project or service comes with a defined driver at setup.

Move the basis out of loose spreadsheets and into a controlled table with change history. Log every manual override with a reason, and review that log. Recurring overrides mean the model needs work.

Finally, add one control most teams lack: a periodic comparison of allocated cost against measured activity for each major cost object. Balanced totals prove the arithmetic. This comparison proves the logic.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.