A cost object is whatever a business has decided to measure the cost of: a product, a service, a job, a client, a department, a program or a single activity. It is a choice rather than a fact about the business, and nothing downstream in a costing system means anything until it has been made, because a cost is only ever direct or indirect with respect to a stated object.
The assignment methods that get costs onto one are set out in cost accounting. This entry is about the two vocabularies the term travels under, and about the consequences of the choice itself.
Cost Object and Cost Objective Name the Same Thing
Two bodies of US guidance name it differently, and a firm working on a government contract will meet both words in the same week.
Federal managerial cost accounting standards use cost object. Federal contract cost accounting standards use cost objective, and define it as a function, organizational subdivision, contract, or other work unit for which cost data are desired and for which provision is made to accumulate and measure the cost to processes, products, jobs, capitalized projects (48 CFR 9904.402-30).
Read that definition closely, because it carries a condition the shorter textbook versions drop. Something is a cost objective when cost data are desired for it and provision is made to accumulate the cost. Wanting to know is not enough on its own. If the ledger has no way to collect against it, it is not a cost objective yet, whatever anyone intended.
Cost objects also nest. A final cost objective is one which has allocated to it both direct and indirect costs and, in the contractor’s accumulation system, is one of the final accumulation points, while an indirect cost is any cost not directly identified with a single final cost objective but identified with two or more final cost objectives or with at least one intermediate cost objective (the same section). What that layering does to the direct test is set out in direct cost.
The Choice Decides the Answer
This is the practical consequence, and it is the reason the object is chosen first rather than assumed. Indirect is not defined by the nature of the cost, by how it behaves or by who approved it. It is defined by whether the cost lands on one final objective or has to be gathered before it gets there, so changing which objectives are final changes the category of the same expense.
Take the salary of a manager who runs one client engagement and nothing else. Against the engagement as the cost object it is traceable to exactly one thing, so it is a direct cost of that engagement. Against a single tax return inside that engagement it now reaches many returns, so it is indirect and has to be spread on some basis. Same salary, same person, same month.
cost object = the engagement manager's salary is DIRECT
cost object = one return manager's salary is INDIRECTNothing about the cost changed. The question changed. Which is why a costing answer that arrives without its cost object named is not an answer, and why two people arguing about whether something is overhead are usually disagreeing about the object rather than about the cost. The traceability test itself, and the consistency rule that stops a firm treating one cost both ways, are worked through in direct cost.
Picking One
Three questions settle it in practice.
What decision is the number for? A pricing decision needs the object the price is quoted against, usually the engagement or the job. A staffing decision needs a service line or an office. Costing something nobody will decide anything about is measurement for its own sake.
Can the ledger actually collect against it? This is the federal standard’s own condition. If time is captured by client but not by return type, the return type is not yet a cost object and no amount of analysis will make it one.
Is the object stable enough to compare? A cost object that is redefined every year produces figures that cannot be read as a trend.
Common Questions
The cost object is what is being costed. The cost driver is the activity whose level causes the cost to move, and the two are set out in cost drivers.
Yes, and it is one of the more useful choices a service business can make. Costing by client rather than only by engagement is what surfaces the client whose individual jobs each look profitable while the relationship as a whole is not, because the unbilled calls, the chasing and the rework attach to the client and not to any one file.
No. A cost center is either a unit whose manager answers for its spending or a segment of the account code that costs are accumulated against, and both senses are set out in cost center. A cost object is whatever is being measured, so a cost center in the second sense is often used as one, while a product, a job or a client is a cost object with nobody accountable for it.
Accountably places trained offshore accountants and tax preparers inside US CPA and EA firms, and a firm can put a real block of its own recurring work through a trial task before anything client facing depends on it.
