Cost Driver

August 31, 2024 Accounting

A cost driver is a measurable factor used to explain resource consumption or assign an activity's cost to products, services, or customers.

On this page

A cost driver is a measurable factor used to explain resource consumption or assign an activity’s cost to a product, service, customer, channel, or other cost object. Examples include machine hours, production setups, purchase orders, inspection time, deliveries, or engineering-change hours.

The strongest driver has a plausible cause-and-effect relationship with the cost. A convenient allocation base can distribute a cost without actually causing it, so accountants and managers should distinguish a causal driver from a merely practical basis for allocation.

Key Takeaways

  • Cost drivers connect resource consumption, activities, and cost objects.
  • An activity cost pool should be reasonably homogeneous before one rate is applied to it.
  • Transaction, duration, and intensity drivers offer different tradeoffs between simplicity and accuracy.
  • Unit volume is often a poor driver for batch-, product-, customer-, or facility-level costs.
  • Allocated cost is not automatically avoidable, incremental, or relevant to a decision.
  • Driver quality should be tested over time because processes, capacity, technology, and cost behavior change.

Cost Driver vs. Allocation Base

The terms are often used interchangeably, but the distinction matters:

  • A cost driver is expected to explain why resource consumption changes.
  • An allocation base is the measured quantity used to spread a cost pool.

Direct labor hours might be an easy allocation base for factory overhead. If automation causes maintenance and power costs to vary mainly with machine hours, however, labor hours may produce a misleading product-cost assignment. The allocation can be mathematically correct while the model is economically weak.

How Activity-Based Costing Uses Drivers

Activity-based costing (ABC) commonly follows two stages:

  1. Resource costs are assigned to activities, sometimes using resource drivers such as floor area, headcount, or system usage.
  2. Activity costs are assigned to cost objects using activity drivers such as setups, orders, inspections, or delivery miles.

For one activity cost pool:

$$ \text{Activity Rate} = \frac{\text{Total Activity Cost Pool}}{\text{Total Practical Driver Units}} $$
$$ \text{Cost Assigned to a Cost Object} = \text{Activity Rate} \times \text{Driver Units Used} $$

The denominator should represent a supportable capacity concept and period. Using an unusually low actual activity level can load idle-capacity cost into products and make them appear more expensive than the resources they consumed.

Worked Example: Setup Costs

A factory expects $180,000 of setup-related cost and 120 setups during the period. Product A requires 20 setups, while Product B requires 100.

$$ \text{Setup Rate} = \frac{\$180{,}000}{120} = \$1{,}500\text{ per setup} $$
ProductSetupsAssigned setup cost
Product A20$30,000
Product B100$150,000
Total120$180,000

Suppose Product B is made in many small batches while Product A is made in long runs. Allocating setup cost by units produced could undercost Product B and overcost Product A because setups occur per batch, not per unit. A setup-count driver better reflects the activity, although setup hours may be better if setup complexity varies materially.

The example assigns the cost pool; it does not prove that all $150,000 would disappear if Product B were discontinued. Setup employees, equipment, and facility commitments may remain unless management can actually remove or redeploy them.

Common Driver Types

Driver typeExampleStrengthLimitation
TransactionNumber of orders or setupsSimple to collect and explainTreats every event as equally demanding
DurationSetup hours or support minutesCaptures time differencesTime may not reflect skill, equipment, or complexity
IntensityActual resources used by a specific jobCan be most accurate for unusual workExpensive to measure and maintain
VolumeUnits, labor hours, or machine hoursEfficient for unit-level costsDistorts batch-, product-, or customer-level activities
CapacitySquare feet, server capacity, or staffed hoursHelps expose committed and idle resourcesAllocation may not represent short-run avoidability

ABC systems also distinguish activity levels:

  • Unit-level: performed for each unit, such as machine processing time.
  • Batch-level: performed for a group of units, such as a setup or purchase order.
  • Product- or service-sustaining: supports a product line, such as design changes.
  • Customer-sustaining: supports a customer relationship, such as account service.
  • Facility-sustaining: supports the overall operation and may not have a persuasive lower-level driver.

Forcing facility-sustaining cost through a precise-looking product driver can create false accuracy.

How to Select a Cost Driver

Evaluate candidate drivers against these criteria:

  1. Causal logic: Does the activity plausibly consume the resource or change the cost?
  2. Cost-pool homogeneity: Are the pooled costs driven in roughly the same way?
  3. Measurability: Can the quantity be captured completely and consistently?
  4. Stability: Does the relationship hold across periods, products, and activity levels?
  5. Materiality: Would a better driver change pricing, mix, process, or customer decisions?
  6. Behavioral effects: Can employees or customers game the measure?
  7. Cost-benefit: Is the improvement worth the data and maintenance cost?

Statistical correlation can support a driver but does not establish causation. A time trend may make two variables move together even when neither causes the other. Process observation, operational evidence, and out-of-sample testing are important.

Decision Use and Limitations

Cost-driver analysis can improve product costing, customer profitability, process design, budgeting, capacity planning, and overhead control. It can show that a low-volume custom product consumes disproportionate engineering, ordering, setup, and support resources.

However, different decisions require different cost concepts:

  • Pricing: Allocated full cost can inform long-run sustainability but does not by itself set the market price.
  • Special order: Relevant incremental cost may be lower than full allocated cost when idle capacity exists.
  • Product discontinuation: Avoidable cost matters more than cost assigned under the existing model.
  • Capacity: The model should separate used, unused, and committed capacity where practical.
  • Performance evaluation: Managers should not be penalized for costs they cannot influence merely because an allocation assigns those costs to their unit.

Common failures include stale rates, too many tiny cost pools, broad pools containing unlike activities, driver quantities with missing records, circular allocations, and models built to justify a preferred answer. Reconcile activity-pool totals to the ledger and explain unreconciled or facility-level amounts.

This page is educational and does not provide accounting, pricing, management, audit, tax, or investment advice.

FAQs

Is sales revenue a good cost driver?

Sometimes it is a practical allocation base, but it is rarely a universal causal driver. Two customers with equal revenue can require very different ordering, delivery, customization, credit, and support activity. The intended use and process evidence determine whether revenue is suitable.

Can one cost pool use more than one driver?

If materially different activities drive the costs, splitting the pool and applying separate drivers is usually more informative than forcing one blended rate. The extra precision should still justify the data and administration cost.

Does an assigned cost equal the cost saved if an activity stops?

No. Assignment describes how a model distributes cost. Savings depend on which resources are variable, avoidable, contractually committed, or capable of being redeployed over the decision horizon.

Authoritative Sources

Browse Accounting