Where cost management breaks: handoffs, exceptions and workarounds

Cost management usually breaks where finance depends on someone else: new cost centers set up late, driver data from operations that arrives incomplete, allocation bases nobody owns, and cost figures handed to billing or budgeting that no longer match the ledger. Each of these leaves a visible trace.

The cost structure lags behind the organisation

Cost centers, projects, cost pools and cost objects are meant to mirror how the organisation actually works. They rarely keep up. A team is reorganised or a programme starts, and the request to create a new cost object reaches finance after spending has begun. Charges land in a holding center or a parent code. Someone moves them later by journal.

Close-out is the quieter failure. Finished projects stay open because closing them feels risky, and stray charges keep arriving long after the work ended.

The trace is easy to find. Look for suspense or default cost centers with growing balances. Look for closed projects that still receive postings. Spend limits that are breached without anyone being warned point to the same gap, because the limit was never set on the new code.

Driver data comes from outside finance

Determining cost drivers is an analytical exercise. Measuring them is an operational one. Headcount by function, floor space, machine hours, transaction volumes and case counts all come from systems that finance does not control. They arrive in spreadsheets, often from a single person who knows where to pull them.

When that person is absent, last period's figures get reused. When a source system changes its definitions, the driver shifts with no notice to finance.

Watch for allocations that stay perfectly flat while activity clearly moved. A driver file with no named owner or no record of its source query is another warning. So is a sudden jump in one department's allocated cost that nobody in that department can explain.

Allocation bases that nobody owns

Accumulating direct cost is mostly mechanical. The trouble starts with indirect cost. The basis for spreading shared services, facilities or IT was agreed at some point, captured in an allocation rule, and then left alone. Over time the business changes and the basis stops reflecting consumption.

Budget holders notice before finance does. They dispute their share, and finance responds with manual overrides for the loudest voices. Those overrides become permanent.

Signs of this include allocation rules with hardcoded exceptions, side agreements recorded in email, and a reallocation journal posted after the system allocation run as a matter of routine. If the people who run the allocation cannot say why a given basis was chosen, it probably no longer fits.

Reclassifications after the close

Much of the real work in cost management happens after the period is closed. Miscoded invoices, payroll charged to the wrong center and late corrections from project managers all arrive as reclass requests. Each one changes figures that have already been reported.

High volumes of reclass journals point back upstream, usually to coding at the point of purchase or time entry. Repeated requests from the same few cost center owners suggest the coding guidance is unclear to them, or the code they need does not exist.

The handoff to billing, budgeting and the statements

Cost information feeds other processes. It sets rates for invoices and reimbursable work, it informs budget formulation, and it rolls into the statement of net cost. Each consumer often takes an extract at a different moment. The billing team prices on one version, the budget team plans on another, and the ledger carries a third.

The symptom is reconciliation work at the edges. Teams keep bridging schedules to explain why cost reports and ledger balances differ. Rates are challenged by customers or internal clients. Budget submissions get restated late because the cost base underneath them moved.

Asset deployment and utilisation

Managing asset utilisation depends on knowing where assets are and how much they are used. The fixed asset register usually records location and cost center at acquisition and is rarely updated after equipment moves. Depreciation then sits with the wrong owner, and any utilisation analysis is built on stale data.

Physical counts that turn up assets in unexpected places are the plainest sign. Departments carrying depreciation for equipment they no longer hold is another.

Questions to ask the people who run the process

The documented procedure describes the intended flow. These questions surface what actually happens.

• When a new team or project starts, how do its costs get coded before the cost center exists?
• Which driver figures do you gather by hand, and who do you go to for them?
• What do you do when a driver file is late or missing?
• Which allocations get adjusted after the system run, and who asked for that?
• Is there a spreadsheet you rebuild at every close that is not in the procedure?
• Which cost center owners send the most reclass requests, and what are they usually correcting?
• When billing or budgeting asks for cost data, which version do they get, and how do you tie it back to the ledger?
• Who decides when a project can be closed, and what stops it from happening?
• If you were away, which step would stall first?

The answer to the last question usually identifies the workaround that matters most.

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.