Cost Objects, Cost Units, and Coding: Building a Useful System

Learning objectives

By the end of this chapter you should be able to:

• Explain what acost objectis and why defining it clearly improves pricing, planning, and performance analysis.
• Distinguishcost units,cost centres, andprofit centres, and select appropriate measures for different organisations.
• Design a practicalcoding structurethat supports consistent transaction capture and useful internal reporting.
• Apply basicdata quality controlsto reduce miscoding and strengthen the audit trail.
• Reconcile internal cost reports to ledger totals using an agreed scope and clear exclusions.

Overview & key concepts

Good cost information starts with three decisions:

1. What are we trying to cost?(thecost object)
2. How will we measure it?(thecost unit)
3. How will we record it consistently?(thecoding system, often incorporatingcost centresandprojects/jobs)

These are management accounting tools. They do not change the accounting equation by themselves; they help you classify and analyse transactions that are already recorded in the accounting records.

Cost objects

A cost object is anything for which you want to measure and report costs separately. Common examples include:

• a product or product line
• a customer or contract
• a project or job
• a service offering
• a location (for example, a branch)

Cost objects support decisions such as pricing, margin analysis, tendering, and performance evaluation. In published financial statements, cost object detail is usually aggregated into headings such as cost of sales or operating expenses.

Cost units

A cost unit is the unit of measurement used to express the cost of a cost object in a meaningful way. Examples include:

• cost per unit produced (manufacturing)
• cost per labour hour (service and repair work)
• cost per delivery or per kilometre (transport)
• cost per patient day (healthcare)

A good cost unit reflects how resources are consumed and allows comparisons across periods or between departments.

Cost centres and profit centres

A cost centre is an organisational segment where costs are collected and controlled (for example, production, sales, administration). Managers are typically accountable for costs within that area.

A profit centre is accountable for both revenue and costs, so performance can be assessed on profitability (for example, a store, a region, or a product division).

Coding scheme

A coding scheme is a structured set of reference codes used to classify transactions consistently at entry. Codes commonly combine:

• thenature of cost(account)
• thelocation or responsibility(cost centre)
• thepurpose/output(project, job, customer, product)

A strong coding scheme improves reporting speed, consistency, and traceability. It also supports reconciliations from detailed records back to the general ledger.

Source documents and audit trail

Source documents (invoices, purchase orders, goods received notes, timesheets, expense claims) provide evidence that a transaction occurred and support correct coding.

A good audit trail means someone can start with a figure in a cost report and work back to the underlying transaction and evidence (and also go the other way—from a source document to where it appears in internal and financial reports). Clear coding and well-kept source documents make that traceability routine rather than investigative.

Core theory and frameworks

A quick exam-ready distinction (keep this clear)

• Cost object:whatyou want to cost (project, product, customer, job).
• Cost unit:howyou measure the cost object (per unit, per hour, per kilometre).
• Cost centre:wherecosts are collected for control (department, function, location).
• Profit centre: a segment responsible for both revenue and costs.

1. Defining the cost object and cost unit

Start by identifying the decision or report you need, then choose a cost object and a cost unit that fit that purpose.

A practical approach:

• Step 1: Define the question.
• Examples: “Which project is profitable?” “Which department is overspending?” “What should we charge per unit?”
• Step 2: Choose the cost object.
• Project, product, customer, service line, contract, or location.
• Step 3: Choose the cost unit.
• The unit should reflect output and resource consumption (units, hours, kilometres, etc.).
• Step 4: Decide how to treat shared costs.
• Decide which costs are direct, and which must be apportioned using an objective basis.

2. Designing a coding structure

A coding structure should be:

• Consistent(same logic everywhere)
• Readable(users can interpret codes without guesswork)
• Scalable(room for growth: new departments/projects)
• Controlled(codes are created, amended, and closed through a clear process)

A common three-part pattern:

Account – Cost centre – Cost object (Project/Job/Customer)
Example: 5200–220–P301

• 5200= travel expense (nature of cost)
• 220= sales department (responsibility/location)
• P301= project identifier (purpose/output)

Caution: avoid over-encoding meaning into the digits. If the code itself tries to describe organisational structure in too much detail, reorganisations and reporting changes can break comparability. Keep codes stable and let reporting tools handle flexible grouping.

3. Document-to-ledger flow

A typical flow for coded transactions:

1. Source document created/received(invoice, timesheet, expense claim)
2. Coding applied at entry(validated against an approved list)
3. Recorded in a sub-ledger where appropriate(payables, receivables, inventory, fixed assets)
4. Posted to the general ledger(often via batch totals)
5. Reports producedby cost centre, project, and account code

This flow allows you to reconcile internal cost reports back to ledger balances.

4. Basic controls to protect data quality

Effective controls focus on preventing miscoding and detecting errors early:

• Approved code listswith restricted editing rights
• Validation rules(reject invalid combinations, such as a sales cost centre with a production-only project)
• Authorisation(especially for new codes and unusual postings)
• Exception reporting(high-value items coded to NA, suspense, or rarely used codes)
• Periodic code review(close inactive projects, merge duplicates, remove obsolete cost centres)
• Reconciliations(cost reports tied back to ledger totals, with explained differences)

5. Allocation and apportionment

• Allocation: charge a cost directly to one cost centre or cost object when the link is clear (for example, direct materials to a specific job).
• Apportionment: spread a shared cost across multiple centres or objects using a reasonable basis (for example, utilities by metered usage; rent by floor area).

Apportionment bases should be evidence-based and applied consistently. If the basis is weak, the resulting profitability analysis will also be weak.

6. Cost drivers

A cost driver is a factor that explains why a cost changes. Examples:

• machine hours driving power and maintenance
• labour hours driving supervision and support costs
• number of orders driving despatch and customer service costs

Choosing a cost driver is about selecting a reasonable explanation for cost behaviour and using it consistently.

Link to inventory and overheads (high-level)

When inventory exists, some production-related costs may be included in the cost of inventory and recognised as an expense only when goods are sold. Internal cost reporting often tracks production costs by job or product for decision-making, but reconciliation to published results must consider inventory movements and the timing of cost recognition.

Worked example

Narrative scenario

A small manufacturing company produces custom furniture. It analyses costs by department (production, sales, administration) and by project using a coding structure:

Account – Cost centre – Project

Cost centres:

• 210Production
• 220Sales
• 230Administration

Assume the following for January to keep the example focused on coding and cost reporting:

• All raw materials purchased in January areissued to production in January(no closing raw materials).
• The related output is treated assold in January(no finished goods inventory).
• Input VAT on costs isrecoverableand is therefore excluded from internal cost reports (anyirrecoverableVAT would be coded as part of the relevant expense).

During January, the following items arise (amounts are stated net of VAT unless noted otherwise):

1. Raw materials purchased£5,000, coded5100–210–P301.
2. Sales team travel expenses£1,200, coded5200–220–NA.
3. Temporary labour for production£2,500, coded5300–210–P302.
4. Marketing print and promotional materials£800, coded5410–220–P301.
5. Equipment maintenance for production£1,000, coded5500–210–NA.
6. Office stationery and general supplies£300, coded5420–230–NA.
7. Rent for production space£2,000, coded5600–210–NA.
8. Utilities for the entire facility£1,500, to be apportioned based on departmental usage.
9. Sales revenue£12,000(net), recorded separately from VAT.
10. Output VAT on sales at20%(recorded to a VAT control account, not as revenue).
11. Depreciation of production equipment£1,200, allocated to production.
12. Insurance premium for the facility£600, apportioned equally across the three departments.

Additional information for apportionment (utilities): meter readings show usage of 50% production, 30% sales, 20% administration.

Required

1. Calculate total costs for each department.
2. Prepare a summary report showing costs by project.
3. Reconcile the total costs to the general ledger using an agreed scope and clear exclusions.
4. Identify any miscodings and propose corrections.
5. Discuss the impact of these transactions on the financial statements.

Solution

1. Total costs by department

Utilities apportionment (£1,500):

• Production: 50% × £1,500 =£750
• Sales: 30% × £1,500 =£450
• Administration: 20% × £1,500 =£300

Insurance apportionment (£600 equally across 3 departments):

• Each department: £600 ÷ 3 =£200

Now total each department’s costs (including depreciation):

Production (210)

• Raw materials issued to production (assumed all issued and output sold):£5,000
• Temporary labour:£2,500
• Maintenance:£1,000
• Rent:£2,000
• Utilities apportioned:£750
• Insurance apportioned:£200
• Depreciation allocated:£1,200
• Total production costs = £12,650

Sales (220)

• Travel:£1,200
• Marketing print:£800
• Utilities apportioned:£450
• Insurance apportioned:£200
• Total sales costs = £2,650

Administration (230)

• Office stationery/supplies:£300
• Utilities apportioned:£300
• Insurance apportioned:£200
• Total administration costs = £800

Total costs across all departments = £12,650 + £2,650 + £800 = £16,100

2. Summary report: costs by project

Project totals are built from costs coded to that project. Shared costs should only be pushed into projects if there is a clear and consistent basis for doing so. In this example, shared costs remain as NA.

P301

• Raw materials:£5,000(5100–210–P301)
• Marketing print:£800(5410–220–P301)
• Total P301 = £5,800

P302

• Temporary labour:£2,500(5300–210–P302)
• Total P302 = £2,500

NA (not project-specific)

• Travel:£1,200
• Maintenance:£1,000
• Office stationery/supplies:£300
• Rent:£2,000
• Utilities (shared):£1,500
• Insurance (shared):£600
• Depreciation (production asset cost allocation):£1,200
• Total NA = £7,800

Check: £5,800 + £2,500 + £7,800 = £16,100 (agrees to departmental total).

3. Reconcile to the general ledger (scope and exclusions)

A reconciliation must start with an agreed scope. Internal cost reports often focus on operating expenses and production overheads for management analysis, while the general ledger includes additional postings and classifications.

A clear scope statement for this example:

• Included in the reconciliation: operating expenses and production-related costs included in the period’s cost report total (£16,100).
• Excluded from the reconciliation(typical examples):
  • VAT control accounts (input/output VAT)
  • inventory control postings and inventory movements where applicable
  • capital expenditure (items recorded as assets rather than expenses)
  • accruals and prepayments not yet reflected in cost reports (or reflected differently)
  • non-operating items and classification journals (for example, reclassifications between cost of sales and operating expenses)

How to reconcile in practice:

1. Identify the general ledger total for thesame scope(for example, “production costs and operating expenses, net of recoverable VAT”).
2. Compare it to the cost report total (£16,100).
3. Investigate and explain differences by category (uncoded journals, postings to suspense/NA, timing differences, inventory/capital items).

Because this worked example assumes no inventory movements (materials all issued; output treated as sold), the cost report total should be capable of agreeing closely to the in-scope general ledger expense total.

4. Miscodings and corrections

The codes used are consistent with the stated structure. Two practical improvements strengthen control and reporting quality:

• Separate “nature of cost” accountsimproves analysis: marketing print (5410) is distinguished from office stationery (5420).
• Post allocations through controlled journals: shared costs such as utilities and insurance can be posted initially to a holding account and then distributed to departments via an allocation journal generated by the system (or posted as a controlled monthly journal). This keeps the process auditable without relying on ad hoc manual adjustments.

Typical miscoding checks to apply:

• items coded to the wrong cost centre (for example, admin stationery coded to sales)
• project codes used without supporting evidence
• high-value items coded to NA where a project link exists and should be captured

5. Impact on the financial statements

The underlying transactions affect financial statements as follows:

• Sales and VAT: revenue is recognised net of VAT; output VAT is recorded as a liability, not as income.
• Recoverable input VAT on purchases: recorded separately in a VAT control account and excluded from cost figures. If VAT isirrecoverable, it becomes part of the related expense (and should be coded accordingly).
• Materials: on purchase, materials normally increase inventory; they become part of cost of sales when issued into production and sold, subject to inventory movements. This example assumes all purchased materials are issued and the output is sold in the same period.
• Operating and production costs: travel, marketing, rent, utilities, insurance, maintenance, and depreciation reduce profit for the period (classification between cost of sales and operating expenses depends on the entity’s presentation and inventory accounting).
• Cash vs credit: payment timing changes cash/bank and payables/receivables, but not the expense recognition for the period when costs are incurred (subject to accruals and prepayments).

Accurate coding does not change profit by itself; it ensures costs are analysed correctly by department and project, improving decision-usefulness and enabling clean reconciliations.

Interpretation of the results

Production bears the largest share of cost, driven by materials, labour, rent, utilities, and depreciation. Project P301 carries significant direct cost, so pricing and expected margin should be reviewed using direct costs and, where appropriate, an agreed share of overheads.

Where coding discipline is weak (for example, excessive “NA” postings or uncoded journals), managers may draw the wrong conclusions about project performance and departmental efficiency. Strong governance over master data and consistent allocation methods improve the reliability of internal reporting.

Common pitfalls and misunderstandings

• Treating purchases of materials as an immediate expense: materials are usually an inventory asset on purchase; they become an expense when issued/sold (subject to inventory movement).
• Mixing up cost objects and cost centres: “what we are costing” (project/product) is not the same as “where costs are collected” (department).
• Using cost units that do not reflect activity: a poor unit can hide inefficiency or exaggerate trends.
• Overcomplicated codes: long, over-meaningful codes increase miscoding and become fragile when the organisation changes.
• Uncontrolled ‘NA’ usage: if too many costs are “not applicable”, project and product profitability becomes unreliable.
• Weak apportionment bases: shared costs should be spread using evidence (meter readings, floor area, headcount), not convenience.
• Leaving journals uncoded: depreciation, accruals, and reclassifications must be coded properly or reconciliations become time-consuming.
• Confusing VAT treatment: cost reports typically use net amounts when VAT is recoverable; irrecoverable VAT should be included in cost.

Summary and further reading

Cost objects, cost units, cost centres, and coding systems are the foundation of useful internal cost reporting. Clear definitions and disciplined coding allow costs to be analysed consistently by responsibility and by output. A well-structured coding scheme, supported by basic controls and a reliable audit trail, improves data quality and speeds up reporting. Finally, cost reports should reconcile back to ledger totals using an agreed scope and explicit exclusions, so internal analysis remains anchored to recorded transactions.

FAQ

What is the difference between a cost object and a cost centre?

A cost object is what you want to measure (for example, a project, product, or customer). A cost centre is where costs are collected for control purposes (for example, production, sales, administration). One transaction can be analysed by both: the same cost can belong to a cost centre and relate to a cost object.

How do coding schemes improve reporting?

Coding schemes reduce ambiguity at entry. When transactions are coded consistently, reports can be produced quickly by account, department, and project, and reviewers can trace figures back to source documents and ledger postings. This strengthens control and improves decision-usefulness.

Why does the cost unit matter?

The cost unit determines how costs are expressed and compared. A good unit matches how activity happens (hours, units, kilometres). A poor unit can mislead users, especially when volumes change.

What are the risks of misclassifying costs?

Misclassification distorts departmental performance, project profitability, and budgets. It can also create reconciliation problems between internal reports and ledger totals, and may lead to poor decisions (for example, underpricing a project or penalising the wrong department).

Why use apportionment at all?

Some costs support multiple departments or outputs and cannot be traced directly. Apportionment spreads these shared costs using a reasonable, evidence-based method so that reports present a more complete view of cost.

Should VAT be included in cost reports?

Where VAT is recoverable, management cost reports typically use net amounts and exclude VAT. Where VAT is irrecoverable, it forms part of the expense and should be coded as part of the cost.

Summary (Recap)

This chapter explained how to build a practical cost information system using cost objects, cost units, cost centres, and a consistent coding structure. It showed how codes connect the nature of cost, responsibility area, and the output or purpose of spend, supported by source documents and an audit trail. The worked example demonstrated departmental and project reporting, correct handling of materials (purchase versus issue), appropriate treatment of VAT in internal reporting, and the importance of reconciling internal cost reports back to ledger totals using an agreed scope and clear exclusions.

Glossary

Allocation
Charging a cost directly to a single cost centre or cost object because the link is clear and supportable.

Apportionment
Spreading a shared cost across two or more cost centres (or cost objects) using a reasonable basis, such as usage, floor area, or headcount.

Audit trail
The traceable path from source document to transaction record, ledger postings, and reported outputs.

Coding scheme
A structured set of codes used to classify transactions consistently (commonly by account, cost centre, and cost object).

Cost centre
An organisational segment where costs are collected and controlled (for example, a department).

Cost driver
A factor that explains why a cost occurs or changes (for example, machine hours, labour hours, number of orders).

Cost object
Anything for which costs are measured separately for analysis (for example, a project, product, customer, or service).

Cost unit
The measurement unit used to express costs meaningfully (for example, per unit, per hour, per kilometre).

Ledger
The accounting records that summarise transactions, including the general ledger and supporting sub-ledgers.

Profit centre
A segment responsible for both revenue and costs, allowing profitability to be measured.

Source document
Evidence supporting a transaction (for example, invoice, purchase order, goods received note, timesheet, expense claim).

Sub-ledger
A detailed ledger supporting the general ledger in specific areas (for example, payables, receivables, inventory, fixed assets).