Introduction to Activity-Based Cost Allocation

Every product a factory makes shares the same electricity bill, the same supervisor’s salary, and the same machine maintenance crew. The tricky part has always been deciding how much of that shared, indirect cost each product should carry. Traditional costing methods answer this with a single blanket rate, usually based on machine hours or direct labour hours. Activity-based costing (ABC) answers it differently: by tracing overheads to the actual activities that consume them, and then to the products that use those activities. It sounds like a small shift in logic, but it changes cost figures dramatically once a business makes more than one product.

The problem with traditional overhead allocation 🔗

Under traditional absorption costing, all overheads are pooled together and divided across products using one or two broad bases, such as direct labour hours or machine hours. This works reasonably well when a factory makes similar products in similar volumes. It breaks down when products differ in complexity, batch size, or the number of setups, inspections, or purchase orders they require.

A low-volume, highly customised product might need frequent machine setups, special quality checks, and multiple small purchase orders, yet it gets charged overheads only in proportion to the labour or machine hours it uses. A high-volume, standardised product ends up silently subsidising it. The result is cost distortion: complex products look cheaper than they really are, and simple products look more expensive. Pricing and product-mix decisions built on these numbers can quietly erode profitability.

What activity-based cost allocation actually does 🔗

Activity-based costing was developed to fix exactly this distortion. Instead of asking “how many machine hours did this product use,” ABC asks “which activities did this product actually consume, and how much of each.” Overheads such as machine maintenance, material handling, and quality inspection are each linked to the specific driver that causes them, rather than being lumped into one overhead rate.

The core idea, as summarised in the Institute of Chartered Accountants of India’s study material on cost and management accounting, is that ABC creates a direct link between resource consumption, the activity that consumes it, and the product or service that triggers the activity. This link is what traditional costing skips over.

The four building blocks of ABC 🔗

Before working through an ABC system, it helps to know the vocabulary cost accountants use:

• Activity: Any event or task that causes cost to be incurred, such as setting up a machine, processing a purchase order, or inspecting a batch of finished goods.
• Cost pool (or activity cost centre): A bucket where all the costs related to one activity are accumulated before they are assigned onward. A cost pool totals up the overheads for a specific group of similar activities so an overhead rate can be worked out for that group.
• Cost driver: The factor that causes the cost of an activity to rise or fall, such as the number of setups, number of purchase orders, or number of inspections carried out.
• Cost object: The final item, usually a product, service, or customer, to which the accumulated activity costs are eventually charged.

Building an ABC system step by step 🔗

Setting up activity-based costing generally follows four stages.

Step 1: Identify the major activities 🔗

The first task is to list out the significant activities performed in the production process. In a typical manufacturing unit, these might include machine operations, material purchasing, machine setups, order processing, quality inspection, and dispatch. Only activities that consume a meaningful share of overheads are worth tracking separately; minor ones can be grouped together to keep the system manageable.

Step 2: Create cost pools for each activity 🔗

Once activities are identified, related overhead costs are grouped into cost pools, sometimes called activity cost centres. For instance, all costs connected with machine setups, such as operator time during changeovers and tooling adjustments, are pooled together separately from costs connected with purchasing, such as the buying department’s salaries and communication expenses.

Step 3: Choose an appropriate cost driver for each pool 🔗

Each cost pool should contain only costs that share the same driver, otherwise the resulting allocation will not reflect how the cost actually behaves. Common cost drivers used in practice include number of machine setups, number of purchase orders raised, number of quality inspections, number of material movements, and machine or labour hours for purely volume-driven activities.

Step 4: Compute the cost driver rate and assign costs 🔗

For every cost pool, the total cost is divided by the total quantity of the cost driver to arrive at a cost driver rate. This rate is then multiplied by the amount of the driver each product actually consumes, giving that product its fair share of the overhead. Identifying which activities consume the biggest share of resources also helps management see where cost-reduction efforts will have the most impact.

A simplified worked example 🔗

Assume a company produces two products, A and B, and has already pooled its overheads into two activity cost pools: machine setups costing ₹1,00,000 in total, and quality inspection costing ₹60,000 in total.

If Product A needs 120 setups and 100 inspections in a period, it is charged ₹60,000 for setups and ₹20,000 for inspections, a total of ₹80,000. Product B, which needs fewer, more standardised runs (80 setups and 200 inspections), is charged ₹40,000 and ₹40,000, a total of ₹80,000. Under a traditional single overhead rate based only on machine hours, these two products could easily have been shown as costing roughly the same, even though Product A’s frequent setups actually make it more expensive to produce per unit. ABC brings this difference to the surface.

This kind of gap widens further once more cost pools, such as material handling, order processing, and packaging, are added to the picture. In a real factory producing dozens of product variants, a handful of low-volume, customised items often turn out to be quietly loss-making once every activity they trigger is properly costed, even though they looked perfectly profitable under the old system.

The cost hierarchy behind ABC 🔗

A more advanced version of ABC classifies activities into levels, based on what triggers them, so that costs are matched even more precisely to their true cause.

• Unit-level activities: Performed for every single unit produced, such as machine running time or direct inspection of each piece. These costs increase in proportion to production volume.
• Batch-level activities: Performed once for each batch, regardless of batch size, such as machine setup or a single purchase order covering many units.
• Product-sustaining activities: Incurred to support a particular product line as a whole, such as product design or engineering changes, and do not vary with volume or batch count.
• Facility-sustaining activities: General costs of running the plant, such as factory rent or the plant manager’s salary, which cannot be meaningfully traced to any specific product.

This hierarchy explains why traditional volume-based costing is especially unfair to low-volume, high-variety products: most of their extra cost comes from batch-level and product-sustaining activities, which a single volume-based rate simply cannot capture.

Why this matters for cost control and decision-making 🔗

Once overheads are traced to real activities, managers get far more than an accurate product cost. They get a map of where money is actually going. If machine setups are consuming a disproportionate share of overheads, the business has a clear signal to invest in faster changeover techniques or to rethink production scheduling to reduce the number of setups needed.

ABC data also feeds directly into pricing and product-mix decisions. A product that looked profitable under a blanket overhead rate might turn out to be a loss-maker once its true share of setup, inspection, and handling costs is counted. This is why ABC is often paired with activity-based management, where the activity data is used not just to cost products but to redesign processes and cut out activities that add cost without adding value.

Cost control benefits too. Once a cost pool such as purchasing is tied to a driver like the number of purchase orders raised, managers can see immediately what it costs to process each order and can push for fewer, larger orders instead of many small ones. Traditional costing, which buries purchasing costs inside one overhead figure, rarely surfaces this kind of actionable insight.

Where ABC has its limits 🔗

ABC is not free of trade-offs. Identifying activities, assigning cost pools, and tracking multiple cost drivers takes considerably more time, data, and coordination across departments than a traditional system. Smaller businesses with few products and simple operations may find the extra precision is not worth the added cost of maintaining the system. There is also room for judgement in deciding which activities deserve their own cost pool, which means two accountants analysing the same factory could still arrive at somewhat different figures.

What do you think? If a college canteen wanted to price its menu items more accurately using activity-based costing, which activities do you think would deserve their own cost pool? And do you think the extra accuracy ABC offers is always worth the extra effort of tracking multiple cost drivers?

References

1. https://www.projectmanager.com/blog/activity-based-costing
2. https://resource.cdn.icai.org/87793bos-aps2161-ch5.pdf
3. https://www.myaccountingcourse.com/accounting-dictionary/activity-cost-pool
4. https://www.mrpeasy.com/blog/activity-based-costing/
5. https://www.netsuite.com/portal/resource/articles/accounting/activity-based-costing-abc.shtml