0
Your Cart
No products in the cart.
Course Content
Job and Process Costing
Four written lessons with worked examples, independent practice and a topic self-assessment.
0/4
Allocation and Costing Choices
Four written lessons with worked examples, independent practice and a topic self-assessment.
0/4
Standards, Variances and Cost-System Review
Four written lessons with worked examples, independent practice and a topic self-assessment.
0/4
Cost Accounting
About Lesson

Cost objects and direct versus indirect costs

Content revised on 3 October 2026. Any completion marker earned before this revision refers to the earlier content version and does not confirm completion of this revised lesson.

Learning goals

  • Define a cost object before classifying costs.
  • Distinguish tracing from allocation and keep behavior separate.

Assumptions and scope

  • All amounts are fictional monetary units (MU).
  • One monthly period; the allocation is an internal toy policy.
  • No inventory valuation or selling-price conclusion is implied.

Content revised on 3 October 2026. Any completion marker earned before this revision refers to the earlier content version and does not confirm completion of this revised lesson.

A cost object is the thing whose cost you want to measure. It might be a customer order, a repair visit, a product family or a whole workshop. Naming it first prevents an important error: treating a cost as permanently direct or indirect. The relationship changes when the object changes. The salary of a supervisor dedicated to one workshop can be traced to that workshop, yet cannot usually be traced economically to each item passing through it.

A direct cost has an identifiable connection to the chosen object and a practical measurement route. A material issue note can link a sheet of metal to an order; a time record can link a technician's work to a repair. Traceability is stronger than a convenient arithmetic split. If a workshop divides its electricity bill equally across orders without metering their use, it has allocated a shared cost. It has not discovered an individually measured cost for each order.

Indirect costs are gathered in a pool and assigned using an agreed basis. That basis might be machine hours or occupied space. Allocation is a measurement policy rather than proof of causation. A report should distinguish traced amounts from assigned amounts so a reader can challenge the basis without disputing the original invoice. The total cost pool is still real even when the way it is divided is contestable.

Materiality and measurement effort matter. A tiny amount of glue may be physically traceable but not worth recording separately. The firm might consistently treat such consumables as overhead. Conversely, expensive components usually deserve individual records. A sensible policy states the object, the evidence required, the treatment of small items and who approves exceptions. Consistency helps comparison, but a poor policy should be revised transparently rather than preserved merely for convenience.

Directness does not tell you whether a cost varies with production. A specialist hired at a fixed monthly salary for one project is direct to that project and fixed for that month. Shared power may be indirect to an order while increasing with machine use. Similarly, production versus selling describes function, not traceability. Keep these questions in separate columns rather than forcing every cost into one all-purpose label.

Use a short audit trail when building a cost sheet: identify the object and period, list source documents, trace supported amounts, collect the remainder into described pools, and record the allocation rule. Then check that the amount traced plus the amount pooled equals the costs included in the stated scope. A total that reconciles can still use an unsuitable allocation rule; a persuasive explanation therefore needs both arithmetic and a reason for the classification. This distinction will remain important when you compare job costs and activity-based costs later in the course.

Concept verification: [OpenStax, job and process costing](https://openstax.org/books/principles-managerial-accounting/pages/4-1-distinguish-between-job-order-costing-and-process-costing): production cost records distinguish traceable job costs from pooled costs; verified 3 October 2026. Original course examples.

Worked example: Worked example: One custom rack order

For September, a workshop incurs 720 MU of steel identified to order R, 480 MU of labor recorded on R, and 600 MU of shared workshop support. R used 20 of 100 recorded machine hours. Determine traced cost, assigned support and reported cost. There are no other costs in this scope.

Solution

Traced cost = 720 + 480 = 1,200 MU. The stated support rate is 600 / 100 = 6 MU per machine hour. Assigned support = 20 × 6 = 120 MU. The order report is 1,320 MU. The 120 MU is allocated, not directly traced. The remaining 480 MU of support belongs to other orders; 120 + 480 = 600 MU.

Cost objects and direct versus indirect costs reference table

Read by row; each named column is a text label. Monetary figures are fictional MU. This table is also available as plain text.

Cost Order R treatment Evidence
Steel Direct Issue note naming R
Recorded labor Direct Time record naming R
Workshop support Indirect, allocated Pool ledger plus machine hours

Independent practice

  1. A customer project has 350 MU of identifiable parts and 14 recorded labor hours at 25 MU/hour. Find direct cost.

  2. A laboratory lease is 900 MU/month and serves three projects without usage records. Is it direct to the laboratory? Is it direct to one project?

  3. A shared support pool of 840 MU is assigned over 120 support hours. An order uses 18 hours. Find its allocation and the amount left for other orders.

Practice answers and reasoning
  1. 700 MU.

    Parts are 350 MU and recorded labor is 14 × 25 = 350 MU; both are traced to this object.

  2. Direct to the laboratory; indirect to an individual project.

    The physical resource is identified to the laboratory. Dividing by three would be an allocation rather than individual tracing.

  3. 126 MU assigned; 714 MU remaining.

    The rate is 7 MU/hour. Multiply by 18, then reconcile 126 + 714 to the pool.

Common errors to avoid

  • Calling any evenly divided cost direct.
  • Confusing the cost object with the activity driver.

Exit check

  1. Does direct automatically mean variable?

  2. What must be named before deciding direct versus indirect?

Exit-check answers
  1. No.

    A fixed monthly fee can belong entirely to one cost object.

  2. The cost object and scope.

    A cost can be direct at one level and indirect at another.

0% Complete