Definition: Whatever you’re trying to measure the cost of.

Examples of Cost Objects

Cost ObjectLevel
Single unitMost granular
Batch / production runGroup of units
Product lineAll units of one type
DepartmentOrganizational unit
CustomerExternal party
ProjectTime-bounded work
Geographic regionLocation-based

Why It Matters

The same cost can be direct or indirect depending on which cost object you choose:

CostDirect to…Indirect to…
Factory supervisor salaryManufacturing divisionIndividual product unit
Machine depreciationProduct line using that machineIndividual unit
Battery in electric vehicleSpecific vehicleFactory 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 LevelQuestion 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 level

What Textbooks Simplify

Textbook SaysReality
”Hospital uses patient as cost object”Hospitals track at multiple levels simultaneously
One cost object per systemHierarchical cost objects with drill-down capability
Pick job-order OR processHybrid 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 ObjectApproach
Cost per custom orderJobJob-order costing
Cost per identical unitProcessProcess costing
Cost per customer relationshipCustomerCustomer profitability analysis
Cost per activity performedActivityActivity-based costing (ABC)
Cost per channelDistribution channelChannel 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

East: What opposes this?

South: Where this leads

West: What’s similar?