Cost Allocation Key

A company pays $600,000 a year for a building used by three departments and needs a basis for showing each unit's share of rent. Occupied floor area may be more informative than each department's revenue.

Start by asking why the cost is shared: rent supports space, payroll support serves employees, and a software licence may serve named users. Distinguish direct costs from shared costs, because a dedicated machine's repair belongs to the unit using it and only the cost that genuinely serves multiple recipients needs a sharing rule.

Define the cost pool, meaning what expenses are included and for what period, since a combined pool can distort comparisons if one office's rent includes utilities and another's does not. Choose an observable driver such as floor area for premises, user count for some licences or measured hours for a shared technician; headcount can approximate HR effort, but complex cases may consume more support than the number of employees suggests.

Calculate each recipient's share of the total driver: if a unit occupies 300 of 1,200 square metres, its share is 25%, and applied to a $600,000 rent pool its allocated cost is $150,000. ACCA's cost-centre guidance explicitly checks that overhead going in equals overhead going out, and ACCA describes service-cost-centre re-apportionment based on use, with direct, step-down and reciprocal methods where support units serve each other.

Do not use one universal key merely because it is easy to collect: revenue may allocate central administration for one purpose but says little about which team uses server capacity, so multiple pools with different keys can give a more useful picture. An allocation is an estimate, not proof that a unit caused every dollar, and a department might occupy a floor area because of a prior decision it cannot change this quarter, so distinguish controllable costs from charges assigned for full-cost reporting.

Product costing can have additional accounting rules, and IFRS IAS 2 says fixed production overhead allocated to inventory is based on normal capacity, with abnormal idle capacity not inflating unit cost. That is a specific inventory measurement rule, not an endorsement of any convenient internal key.

For management decisions, compare alternative keys, because if a large warehouse has few employees, allocating rent by headcount may make its margin look artificially strong. For intercompany charges, consider agreements, tax rules and documentation separately, since a key that seems fair for internal scorecards is not automatically acceptable for transfer pricing or a statutory filing.

Set a data owner for each driver, because staff counts change monthly, floor plans change when teams move and usage meters can fail, and state the measurement date and refresh frequency instead of silently reusing an old baseline. Apply a chosen key consistently within a reporting period and, if the method changes, explain why and show the effect on comparisons.

Consider materiality, because a complex time-tracking system to allocate a tiny shared bill may cost more than the insight it adds, and tell affected managers what is in the pool, why the key was selected and what they can influence. Check for double counting, since an expense directly assigned to a site should not also sit in the central pool, and remember that the point for an owner is not a mathematically perfect split but comparable unit results, visible resource use and decisions not built on arbitrary charges, so revisit the key when operations change.