CIMA P2: Where Activity-Based Costing Answers Actually Go Wrong

Activity-Based Costing (ABC) is introduced in CIMA's Management Level Advanced Management Accounting (P2) syllabus specifically as a response to a known weakness in traditional absorption costing: spreading all overhead using a single volume-based basis (typically labour hours or machine hours) systematically distorts product costs when products don't actually consume overhead resources in proportion to that single measure — the same distortion our guide to absorption costing versus marginal costing explores from a slightly different angle.

Why traditional absorption costing distorts costs

Under traditional absorption costing, overhead is absorbed into products using one basis, usually related to production volume. This works reasonably well when overhead costs genuinely vary with volume in a simple way, but breaks down when a significant portion of overhead is actually driven by complexity, variety, or batch-related activity rather than by the sheer number of units produced. A low-volume, highly customised product that requires frequent machine setups, complex quality inspection, and multiple small production runs consumes a disproportionate amount of overhead relative to its unit volume — but under a single volume-based absorption rate, it gets allocated overhead roughly in line with its unit output, effectively being subsidised by higher-volume, simpler products that consume comparatively less overhead-driving activity per unit.

This cross-subsidisation is the core problem ABC is designed to correct: high-volume, simple products end up over-costed and low-volume, complex products end up under-costed under traditional absorption costing, which can lead to poor pricing and product-mix decisions if managers aren't aware of the distortion.

How ABC assigns overhead differently

ABC groups overhead costs into cost pools based on the activities that cause them to be incurred, then assigns each cost pool to products using a cost driver — the specific factor that actually causes that activity's cost to arise. Machine setup costs are pooled and assigned based on the number of setups each product requires; quality inspection costs are pooled and assigned based on the number of inspections; ordering costs are pooled and assigned based on the number of purchase orders raised. CIMA's syllabus draws on the established cost hierarchy — unit-level, batch-level, product-sustaining, and facility-sustaining activities — to help categorise which driver is appropriate for which type of cost.

The step where P2 answers actually lose marks

Correctly identifying cost pools and calculating cost driver rates is usually done competently. Where P2 scripts lose marks is in two related areas that come after the driver rates have been calculated.

The first is confusing cost pools with cost drivers in the write-up, even when the underlying numbers are calculated correctly — a cost pool is the accumulated cost for an activity (for example, total setup costs of $80,000), while a cost driver is the measure used to spread that pool across products (for example, the number of setups). Answers that use these terms interchangeably tend to also make the corresponding calculation error of applying the wrong basis at the wrong stage.

The second, more consequential error concerns facility-sustaining costs — overheads like general factory rent or senior management salaries that don't vary with any specific product-related activity at all. These costs exist to sustain the whole facility's operation regardless of what's produced, and ABC's own logic implies they shouldn't be forced through a specific activity-based driver, since doing so implies a causal relationship between the driver and the cost that doesn't actually exist. Candidates who mechanically apply an activity-based driver to facility-sustaining costs anyway (simply because ABC is the technique being used throughout the question) are misapplying the very principle ABC is built on — these costs are better treated as a general apportionment or excluded from the product-level ABC analysis, and a scenario that includes a facility-sustaining cost is often specifically testing whether candidates recognise this distinction rather than driver-costing everything indiscriminately.

A related but smaller error is using budgeted driver volumes inconsistently with the costs being spread — mixing an actual cost pool with a budgeted driver volume, or vice versa, produces a cost-per-driver-unit rate that doesn't correspond to any real basis, even though the arithmetic itself may be internally consistent.

Why this distinction matters beyond the exam

The facility-sustaining cost issue isn't just an exam technicality — it reflects a genuine limitation of ABC that CIMA's syllabus expects candidates to recognise: ABC improves cost allocation accuracy for activity-driven overheads, but it doesn't eliminate the need for some form of apportionment for costs that genuinely aren't driven by measurable product-level activity. A complete P2 answer often needs to explicitly acknowledge this boundary, rather than presenting ABC as a technique that perfectly traces every overhead cost to a causal driver.

Frequently asked questions

What's the difference between a cost pool and a cost driver in ABC?

A cost pool is the accumulated total cost for a specific activity (such as total machine setup costs); a cost driver is the factor used to spread that pool across products (such as the number of setups each product requires).

Should facility-sustaining costs be assigned using an activity-based driver?

Generally no — facility-sustaining costs like general factory rent don't vary with any specific product-related activity, so forcing them through an activity-based driver implies a causal relationship that doesn't exist. They're typically better handled through general apportionment or excluded from the product-level ABC analysis.

Why does traditional absorption costing under-cost complex, low-volume products?

Because it spreads overhead using a single volume-based measure, while complex, low-volume products often consume disproportionate amounts of batch-related or product-sustaining overhead (like setups and inspections) relative to their unit volume — a cost pattern a single volume-based rate can't capture.

ABC's real exam difficulty isn't building the driver rates — it's correctly judging which costs an activity-based driver genuinely applies to, and recognising that facility-sustaining costs sit outside that logic even within an ABC-based answer. Learnsignal's CIMA P2 course covers ABC and its boundaries alongside the full costing syllabus.