Mon – Sat: 9:00 AM – 7:00 PM IST
Finance

What is project costing?

Collecting cost against a job rather than a department — and seeing the overrun while it can still be fixed.

In short

Project costing collects cost against a project or job rather than only against a cost centre: labour, materials, subcontract, expenses and overhead, structured through a work breakdown structure. It allows actual cost to be compared with budget at any level of the project, and committed cost to be seen before it becomes actual.

Why It Matters

Why this matters in practice

Departmental accounting tells you the business spent money; project costing tells you which job consumed it. Without it, a loss-making project is invisible until the whole department's numbers move, by which point the job is finished. The commitment view matters most — a purchase order raised against a project is money gone, and waiting for the invoice to see it is waiting too long.

Cost attributed to the job that caused it
Budget versus actual visible at any WBS level
Commitments visible before they become actuals
Supports revenue recognition on long-running contracts
How It Works

How it works in practice

Work breakdown structure

The project decomposed into phases and tasks, each able to carry budget and cost. The depth should match how it will actually be managed.

Budgeting

Budget set at WBS level, by cost type, with a defined change process for revisions.

Cost collection

Timesheets, material issues, subcontractor invoices and expenses all coded to a WBS element.

Commitments

Open purchase orders against the project, visible alongside actuals so the true position is known.

Reporting and forecasting

Cost to date, committed, and estimate to complete. The last of these is a judgement and should be owned by the project manager.

Worked example

A worked example: a project 60% spent and 80% committed

A project reports 42 lakh spent against a 70 lakh budget at the halfway point. On actual cost alone this looks comfortable — 60 percent spent, roughly on track.

Including commitments changes it. Purchase orders issued but not yet received total a further 14 lakh, so 56 lakh of the 70 is already committed. That is 80 percent of the budget spoken for at the halfway point, and the remaining work includes a subcontract that has not been ordered yet. The project is heading for an overrun that the actual-cost view will not reveal for another two months.

This is why budget checking must include commitments rather than only actuals. A system that checks the budget at invoice posting will approve every purchase order up to the moment the money is gone, and the overrun will be discovered by the finance team rather than prevented by the control. Committing the budget at order rather than at invoice is usually a configuration setting, and it is frequently left at the less useful default.

Key terms

The vocabulary, briefly

Term What it means
WBS Work breakdown structure — the hierarchy costs and revenue are collected against.
Budget at completion The total expected cost for the project, against which progress is measured.
Estimate to complete The revised forecast of remaining cost, which is where overruns become visible.
Commitment Costs ordered but not yet incurred, which a budget check must consider.
Capitalisation Transferring project cost to a fixed asset when the project delivers one.
What Goes Wrong

Common mistakes worth avoiding

WBS too deep

A structure with hundreds of elements is coded inconsistently and reported on by nobody.

Timesheets late or absent

Labour is usually the largest cost. Weekly timesheets a fortnight late make the position permanently stale.

Commitments ignored

Reporting actuals only understates the position by every open order on the project.

No estimate to complete

Cost to date without a forecast tells you where you have been, not where you will end.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Actual plus committed against budget The real consumption picture. Actuals alone are a lagging view.
Estimate to complete movement Whether forecasts are being revised honestly or held at budget until too late.
Cost performance index Earned value against actual cost, where earned value is measured rather than assumed.
Unbilled work in progress Costs incurred but not yet invoiced to the customer, which is cash sitting in the project.
FAQ

Questions we are asked about this

A hierarchical decomposition of the project into manageable elements. Each can carry budget, collect cost and be reported on, which is what makes variance traceable to a part of the job.
Committed is money the organisation has obliged itself to spend — an open purchase order. Actual is money recorded as incurred. The commitment comes first and is the earlier warning.
Detailed enough that a variance points at something actionable, and no deeper. A WBS element covering six months of mixed work tells you there is a problem but not where. One covering every individual task produces precise numbers that cost more to maintain than they inform. A practical test is whether one person can be named as accountable for each element — if not, it is probably too granular or too broad.
When the project creates an asset meeting the recognition criteria in the applicable accounting standard, and only the costs that qualify. The common errors run in both directions: capitalising costs that should be expensed, which flatters current profit, and expensing costs that should be capitalised, which understates assets. Agree the policy with your auditors before the project starts, because retrospective reclassification of a year's project costs is unpleasant.
As formal budget revisions with their own approval, not as silent consumption of contingency. A project whose budget quietly absorbs scope changes will show a cost overrun that is actually a scope increase, and the distinction matters for both accountability and future estimating. Keep the original budget visible alongside the revised one so the history of changes is readable.
Largely scale and duration. Job costing typically covers shorter work with simpler structures — a repair, a batch, a single order — while project costing handles longer multi-phase work with a breakdown structure, milestones, revenue recognition and capitalisation. Many ERP systems use one engine for both with different configuration, and the risk is applying project-grade overhead to work that only needed job costing.
Related

Where to read next

Percentage-of-completion revenue

Read more

What is period close?

Read more

Our ERP software solutions

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.