Definition: Whatever you’re trying to measure the cost of.
Examples of Cost Objects
| Cost Object | Level |
|---|---|
| Single unit | Most granular |
| Batch / production run | Group of units |
| Product line | All units of one type |
| Department | Organizational unit |
| Customer | External party |
| Project | Time-bounded work |
| Geographic region | Location-based |
Why It Matters
The same cost can be direct or indirect depending on which cost object you choose:
| Cost | Direct to… | Indirect to… |
|---|---|---|
| Factory supervisor salary | Manufacturing division | Individual product unit |
| Machine depreciation | Product line using that machine | Individual unit |
| Battery in electric vehicle | Specific vehicle | Factory as a whole |
The Key Insight
Direct vs indirect isn’t an inherent property of the cost—it’s a relationship between the cost and the cost object you’ve selected.
Common Trap
Assuming a cost is “just indirect” without asking “indirect to what?” First identify the cost object, then classify.
Cost Object Hierarchies
Cost objects aren't flat—they form hierarchies. The same data supports multiple levels of analysis.
In practice, organizations track costs at multiple levels simultaneously:
Hospital Example:
Patient (lifetime)
└── Admission/Stay
└── Department (radiology, surgery, pharmacy)
└── Procedure/Service
└── Individual resource consumption
Each level answers a different question:
| Cost Object Level | Question It Answers |
|---|---|
| Patient (lifetime) | “Is this patient profitable overall?” |
| Admission/Stay | ”What did this ER visit cost vs. that surgery stay?” |
| Department | ”How much radiology resources did this stay consume?” |
| Procedure | ”What’s the cost of an MRI vs. a CT scan?” |
The database analogy: This is exactly like SQL aggregation—same underlying data, different GROUP BY:
SELECT SUM(cost) FROM services GROUP BY patient_id -- patient level
SELECT SUM(cost) FROM services GROUP BY patient_id, admission_id -- stay level
SELECT SUM(cost) FROM services GROUP BY patient_id, admission_id, dept -- department levelWhat Textbooks Simplify
Textbook Says Reality ”Hospital uses patient as cost object” Hospitals track at multiple levels simultaneously One cost object per system Hierarchical cost objects with drill-down capability Pick job-order OR process Hybrid systems with different methods at different levels
The consulting question: When someone says “we need to know our costs,” the first question is “at what level?” A hospital administrator asking about departmental efficiency needs different granularity than an insurance company negotiating reimbursement rates per procedure.
Cost Object Choice Drives System Design
The costing system follows from the cost object choice—not the other way around.
First ask: “What do we need to measure the cost of?” Then pick the system that accumulates costs around that object.
Process costing and job-order costing are just two answers to a more general question: “What do we want to measure the cost of?”
| If You Want to Know… | Cost Object | Approach |
|---|---|---|
| Cost per custom order | Job | Job-order costing |
| Cost per identical unit | Process | Process costing |
| Cost per customer relationship | Customer | Customer profitability analysis |
| Cost per activity performed | Activity | Activity-based costing (ABC) |
| Cost per channel | Distribution channel | Channel profitability analysis |
The underlying principle—choose a cost object, then design a system to accumulate costs around it—drives all cost analysis. Job-order and process costing are the foundational methods for external reporting, but the same logic extends to any cost measurement need.
Customer as cost object
A bank wants to know: “Which customers are profitable vs. unprofitable?”
- Cost object: individual customer
- Accumulate: service costs, transaction costs, support costs per customer
- Compare to: revenue from that customer
Same structure as job-order costing—just a different cost object answering a different question.
North: Where this comes from
- Cost Classification Framework (parent framework)
- Management Decision-Making (why we need to measure costs differently)
East: What opposes this?
- Aggregate Costing (treating all costs at company level)
South: Where this leads
- Direct vs Indirect Costs (classification depends on cost object choice)
- Activity-Based Costing (more granular cost object selection)
- Customer Profitability Analysis (customer as cost object)
- Job-Order Costing (job as cost object)
- Process Costing (process/department as cost object)
West: What’s similar?
- Unit of Analysis (research methods—what are you studying?)
- Granularity in Data (same data, different zoom levels)
- SQL GROUP BY (same underlying data, different aggregation levels)
- Dimensional Modeling (fact tables with multiple dimension hierarchies)