What it means
Activity-based costing (ABC) assigns indirect costs to products using cost drivers, which are measurable units of activity such as setups, orders or inspection hours. A driver is only useful while it tracks real resource use.
Validation is the periodic test of that link. Suppose a model charges inspection cost by the number of inspections, but a new automated test halves the labour per inspection.
The count looks unchanged while the true effort has fallen, so every product is still charged the old amount. Validation catches this by comparing the driver with operational evidence such as time samples and work orders.
Start with the pool and the definition. Confirm that the pool holds costs belonging to one activity, and write down exactly what counts as one driver unit.
Otherwise two teams can log different events under the same label. Next test the causal link and the data.
Ask whether more driver units generally need more resources, compare system counts with time samples or work orders, and make sure the cost pool and the driver quantity cover the same period. A yearly pool divided by one month of activity produces a meaningless rate.
Complexity and change need a second look. If one inspection takes two minutes and another takes two hours, a simple count may need to be replaced by hours or by complexity bands.
After automation, new software or a revised quality protocol, the rate should be refreshed. Validation also protects against over-reading the result.
An accurate allocation shows who uses the activity, not what cash would be saved if a product were dropped, because shared capacity and idle cost often stay. Keep a record of the driver, the data source, the tests, the approval and the effective date, and bridge old and new product costs so a method change is not mistaken for operating improvement.
In practice
Real-world examples.
Example
A precision-engineering firm replaces "number of inspections" with "inspection hours" after a time sample shows custom parts take far longer to test than standard ones. Margins on custom parts fall and margins on standard parts rise, while total cost is unchanged.
Example
A logistics company automates its parcel scanning, which cuts labour per scan. Finance notices that the cost per scan no longer matches the rate in the model and updates it before the next pricing round. Without that check, customers with scan-heavy shipments would have kept paying for effort that no longer exists.
Example
A software support team allocates support cost to customers by ticket count. A validation test shows that one large customer files few tickets but each takes many hours, so the driver switches to handling time, and finance explains the resulting margin shifts to management.
Formula
Calculation
Activity rate = verified activity pool cost / verified driver units. Suppose an inspection pool costs $60,000 and the records show 3,000 inspection hours, which a time sample confirms within a small tolerance. The rate is $60,000 / 3,000 = $20 per hour. A product that used 450 hours is assigned 450 x $20 = $9,000, and the reconciliation check is that the amounts assigned to all products add back to the $60,000 pool.Case study
Seen in the real world.
Maple Instruments is an entirely fictional manufacturer used here for illustration. Its costing model charged every product the same amount per inspection, even after its custom calibration tests grew much longer than its standard ones.
Finance sampled 40 jobs, found that inspection hours tracked effort far better than counts, and recalculated the rate. The sample also showed that a handful of unusually long jobs were pulling the average up, so finance reported them separately as special cases. It documented the change, published a bridge showing how much of each product's margin movement came from the new method, and made clear that quality-team salaries would not disappear if one product were stopped.
Watch out
Common mistakes.
- Using a convenient count without checking its relationship to resource use; an easy-to-collect number can be a poor proxy for effort.
- Mixing a full-year pool cost with driver data from only one month, which produces a rate that is wrong for every product.
- Treating a margin change caused by a corrected driver as an operating improvement, when only the allocation method has changed.
Questions
People also ask.
How often should a driver be validated?
After any material change in process, technology or product mix, and otherwise at a cadence that matches how much the pool affects pricing decisions. A large pool that drives prices deserves an annual review, while a small pool may only need a light check.
Does a good driver show avoidable cost?
Not necessarily. A validated driver shows who uses the activity, so separately test which cash costs would actually change before acting on a decision such as dropping a customer.
What records should be kept?
The driver definition, the source data, the reconciliation to the pool, the test results, any exceptions, and the approval and effective date of every change.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related