Project Cost Estimation & Budgeting

Chapter 3
Cost Data, Accounting and Cost Allocation

Post Graduate Program in Project Management
Project Cost Estimation & Budgeting   •   Post Graduate

Cost Data, Accounting and Cost Allocation

Introduction

Project cost estimation is only as reliable as the cost information on which it is based. Estimates are developed from historical costs, supplier quotations, labour records, engineering quantities, productivity assumptions and financial-accounting data. If these data are classified inconsistently, recorded in the wrong period or allocated to the wrong project, the resulting budget may appear precise while being economically misleading.

Cost accounting provides the language and control structure through which project costs are identified, measured, assigned and reported. In a project environment, it must connect three perspectives:

  1. Operational reality—what work is performed, by whom, where and when.
  2. Managerial control—whether resources are being used efficiently and whether the forecast remains credible.
  3. Financial reporting—how costs, assets, liabilities, revenue and profit are recognized in formal accounts.

These perspectives overlap but are not identical. A project manager may need a detailed work-package cost view, whereas the general ledger may record costs by legal entity and accounting period. Effective project cost management therefore depends on reconciled coding structures, transparent allocation rules and disciplined treatment of accruals, commitments and capital expenditure.

Learning objectives

By the end of this chapter, the reader should be able to:

  • interpret cost codes and project chart-of-accounts structures;
  • distinguish direct, indirect, fixed, variable, committed, accrued and paid costs;
  • explain job costing and activity-based costing and select between them;
  • calculate and evaluate overhead allocation rates;
  • account for accruals, commitments, capitalization and depreciation;
  • reconcile project-control information with the general ledger and financial reports;
  • identify governance, ethical and data-quality risks in project cost reporting.

1. The architecture of project cost information

A cost object is anything for which cost is measured. It may be a project, contract, work package, activity, asset, product, location or customer. A cost centre is an organizational or operational unit used to accumulate costs, such as an engineering department or construction site. A cost driver is a factor that causes or explains cost, such as labour hours, machine hours, purchase orders or square metres constructed.

Project organizations commonly use several dimensions simultaneously. A transaction might be coded as follows:

DimensionExampleQuestion answered
ProjectPRJ-2407Which project incurred the cost?
Work breakdown structure3.2.1 FoundationWhich deliverable or work package?
Cost element6100 LabourWhat type of resource?
Cost centreENG-04Which organizational unit?
LocationSITE-NORTHWhere was it incurred?
Funding sourceCLIENT-AWho funds or owns it?
Period2026-Q2When is it recognized?

A cost code is a structured identifier assigned to a cost category or transaction. A code may be hierarchical, for example 6100 for labour, 6110 for direct craft labour and 6111 for electrical installation labour. A sound code structure should be mutually understandable, stable over time, sufficiently detailed for decisions and compatible with the organization's general ledger and enterprise resource planning system.

Work breakdown structure and cost breakdown structure

The work breakdown structure (WBS) decomposes project scope into deliverables and work packages. The cost breakdown structure (CBS) decomposes cost into categories such as labour, materials, equipment, subcontracting, travel, overhead and contingency. A cost-loaded WBS links these structures so that each approved budget amount has a defined scope, responsible manager, schedule and measurement basis.

The lowest practical control level is often called a control account. It should have one responsible manager, a defined scope, a budget, planned timing and a method for measuring performance. Excessive detail increases transaction-processing costs; inadequate detail conceals variance. The appropriate level is the lowest level at which management can take meaningful corrective action.

2. Chart of accounts and coding governance

A chart of accounts (COA) is the organized list of ledger accounts used to classify financial transactions. Typical account classes are assets, liabilities, equity, revenue, cost of sales and operating expenses. Project-control systems often add dimensions that do not exist in the statutory ledger, especially WBS, activity and resource codes.

The basic double-entry relationship is:

Assets = Liabilities + Equity

This identity applies to the financial statements of an entity under double-entry accounting. Project cost reports are usually managerial schedules and do not, by themselves, constitute a complete balance sheet.

A project COA should distinguish at least:

  • direct labour and indirect labour;
  • purchased materials and consumables;
  • subcontractor costs;
  • equipment ownership and usage costs;
  • travel and site expenses;
  • allocated overhead;
  • approved changes and claims;
  • contingency and management reserve;
  • capital expenditure and operating expenditure;
  • accruals, reversals and reclassifications.

Coding governance includes account ownership, definitions, permitted combinations, approval authority, effective dates and treatment of obsolete codes. A code dictionary should state what is included and excluded. For example, “direct materials” might include materials incorporated into the deliverable but exclude small tools, freight or recoverable taxes.

A coding matrix can prevent invalid combinations. For example, depreciation may be permitted for an equipment cost centre but not for a temporary labour code. Automated validation reduces miscoding, but it does not replace professional review: a technically valid code can still represent an economically inappropriate classification.

3. Cost classification for project decisions

Direct and indirect costs

A direct cost can be economically traced to a cost object using a practical measurement method. Labour charged to a project timesheet and steel purchased specifically for a bridge are common examples. An indirect cost supports several cost objects and must be allocated or treated as a period cost. Examples include corporate IT, finance, human resources and shared facilities.

The distinction is relative to the cost object. A site manager's salary may be direct to a construction project but indirect to an individual foundation work package. A cost should not be made direct merely because doing so improves a project's reported margin; the tracing method must be causal, reliable and consistently applied.

Fixed, variable and mixed costs

A fixed cost remains approximately constant within a relevant range and period, such as a monthly site office lease. A variable cost changes with an activity measure, such as concrete cost per cubic metre. A mixed cost contains both elements. These classifications support forecasting but are not identical to direct and indirect classifications: a fixed cost can be direct, and a variable cost can be indirect.

Controllable and uncontrollable costs

A cost is controllable when a manager can influence it within the relevant decision period. A project manager may control overtime but not a centrally negotiated insurance premium. Reports should avoid holding managers accountable for costs they cannot influence, while still showing those costs for full project economics.

Sunk, opportunity and avoidable costs

A sunk cost has already been incurred and cannot be changed by a current decision. An opportunity cost is the value of the best alternative use of a resource. An avoidable cost disappears if an option is rejected. These concepts are especially important in make-or-buy, acceleration and change-order decisions, where accounting cost alone may not reflect economic cost.

4. Job costing

Job costing accumulates costs for an identifiable job, contract, project or work package. It is appropriate when outputs are distinct and heterogeneous, as in construction, consulting, software implementation and aerospace production.

A job-cost record commonly contains:

  • approved contract or budget value;
  • direct labour hours and rates;
  • direct materials and purchase orders;
  • subcontractor invoices;
  • equipment usage;
  • allocated overhead;
  • approved and pending changes;
  • actual, accrued, committed and forecast costs.

The basic accumulated-cost relationship is:

Total job cost = Direct costs + Allocated indirect costs

This equation is a classification identity, not a universal pricing rule. It is meaningful only when direct costs are measured consistently and indirect costs are allocated under a documented policy.

Worked example: job costing and overhead

An implementation project records direct labour of $84,000, software purchased specifically for the project of $26,000 and subcontracting of $40,000. The organization applies overhead at 18% of direct labour. The overhead allocation is:

Overhead = 0.18 × $84,000 = $15,120

Therefore:

Total job cost = $84,000 + $26,000 + $40,000 + $15,120 = $165,120

The calculation assumes that the 18% rate is authorized, labour is the appropriate allocation base and the software cost is excluded from the overhead base. If the project manager uses the result for pricing, the estimate should also consider risk, profit, financing and contractual recoverability; job cost is not the same as price.

5. Overhead allocation

Overhead allocation assigns shared costs to cost objects using a rational and consistently applied basis. Common bases include direct labour hours, direct labour cost, machine hours, material cost, transaction counts and square metres. The strongest basis is not necessarily the easiest to measure; it is the one that best represents resource consumption.

A predetermined overhead rate is commonly calculated as:

Predetermined overhead rate = Budgeted overhead cost ÷ Budgeted allocation base

The rate is normally expressed in currency per unit of base, or as a percentage when the base is monetary. The approach assumes that the chosen base is sufficiently related to overhead consumption and that the budget is representative of the period or activity range.

Worked example: departmental rates

A fabrication department expects overhead of $360,000 and 12,000 machine hours. Its rate is:

$360,000 ÷ 12,000 = $30 per machine hour

A project uses 240 machine hours and therefore receives an allocation of:

240 × $30 = $7,200

If another department's overhead is driven mainly by engineering labour, applying the machine-hour rate to that department would distort cost. Departmental or activity-based rates may be preferable to a single organization-wide rate.

Under- and over-applied overhead

At period end, applied overhead is compared with actual overhead. The difference is under-applied when actual overhead exceeds applied overhead and over-applied when applied overhead exceeds actual overhead. The variance may be closed to expense, prorated across work in process and completed work, or investigated under organizational policy. A large recurring variance indicates that the rate, forecast base, cost pool or allocation driver may be defective.

Allocation has behavioural consequences. A project may appear less profitable simply because it receives a large share of a centrally managed cost pool. Managers should therefore review both allocated cost and the underlying resource consumption. Transfer prices and allocation rules should not encourage managers to reject economically beneficial work merely because of arbitrary internal charges.

6. Activity-based costing

Activity-based costing (ABC) recognizes that resources are consumed by activities and that activities are consumed by cost objects. It normally follows four steps:

  1. identify significant activities;
  2. accumulate resource costs into activity cost pools;
  3. select cost drivers;
  4. assign pool costs to products, projects or customers according to driver usage.

For activity pool i:

Activity ratei = Cost pooli ÷ Expected driver volumei

The cost assigned to a project is:

Assigned ABC cost = ∑(Activity ratei × Project driver usagei)

The summation applies across all activity pools. ABC is useful where projects consume support resources in different proportions, for example procurement effort, design reviews, quality inspections and contract administration.

Worked ABC example

A project office has three pools:

ActivityPool costExpected driver volumeRate
Procurement$120,000600 purchase orders$200/order
Quality inspection$90,000300 inspections$300/inspection
Contract administration$150,000500 contract-months$300/contract-month

Project Z uses 18 purchase orders, 12 inspections and 10 contract-months. Its assigned cost is:

(18 × $200) + (12 × $300) + (10 × $300) = $3,600 + $3,600 + $3,000 = $10,200

ABC can improve cost visibility, but it is not automatically more accurate. Driver measurement may be expensive, activities may be correlated, and causal relationships may be uncertain. A simple volume-based rate can be adequate when the cost structure is homogeneous and decision consequences are modest.

7. Accruals, commitments and cash

Project reporting must distinguish the timing of economic activity from the timing of cash payment.

An accrual recognizes a cost when goods or services have been received or consumed, even when the invoice has not yet arrived. A commitment is a future contractual or authorized obligation, usually represented by a purchase order, subcontract or signed contract. A cash payment occurs when money is disbursed. These are different states and must not be added indiscriminately.

A useful project-control view is:

Forecast final cost = Actual cost to date + Accrued cost + Remaining committed cost + Uncommitted forecast cost

This relationship assumes the components are mutually exclusive and that commitments are shown net of amounts already invoiced or accrued. Organizations may define “actual” differently, so the data dictionary must specify whether actual cost includes accruals.

Accrual example

At month end, a subcontractor has completed work estimated at $22,000, but the invoice will arrive next month. The project records a $22,000 accrued cost and an accrued liability, subject to approval and subsequent reversal or settlement. If the invoice later equals $21,500, the $500 difference is investigated and recorded according to policy. Accruals should be evidence-based, documented and reversed or trued up promptly.

A commitment report should show original commitment, approved changes, invoiced amount, accrued amount and remaining commitment. A purchase order is not necessarily a final cost: it may be cancelled, varied or only partially fulfilled. Conversely, costs may be incurred before a purchase order is issued, creating compliance and forecast risk.

8. Capitalization and depreciation

A cost is generally capitalized when it meets the applicable accounting framework's recognition criteria for an asset: the entity controls a resource, future economic benefits are probable or otherwise supportable under the framework, and cost can be measured reliably. Costs that do not meet the criteria are expensed. Exact rules vary by jurisdiction and standards; project managers must consult the organization's accounting policy.

Capitalization is not justified merely because a project is large or because expensing would reduce current profit. Typical capital project costs may include directly attributable design, construction and installation costs incurred to bring an asset to the location and condition necessary for intended use. Training, abnormal waste, general administration and post-completion operating costs are often expensed, subject to applicable standards and policy.

When a qualifying asset is available for use, depreciation allocates its depreciable amount over its useful life. Under straight-line depreciation:

Annual depreciation = (Cost − Residual value) ÷ Useful life

where cost is the depreciable asset cost, residual value is the expected value at the end of useful life, and useful life is measured in years or another appropriate time unit. The method assumes reasonably even consumption of benefits. If benefits are consumed according to usage, a units-of-production method may be more representative:

Depreciation per unit = (Cost − Residual value) ÷ Expected total units

Depreciation example

An item of project equipment costs $500,000, has an estimated residual value of $50,000 and a five-year useful life. Straight-line annual depreciation is:

($500,000 − $50,000) ÷ 5 = $90,000 per year

Monthly depreciation, assuming twelve equal months and availability at the beginning of a month, is $7,500. The assumption about the in-service date matters; depreciation generally begins when the asset is available for intended use, not necessarily when construction expenditure first occurs.

Capitalization affects both project cost reporting and financial reporting. A project dashboard may show total investment cost, while the income statement may show little immediate expense but later depreciation and impairment. Capitalized cost is not automatically recoverable from a customer, and contractual entitlement must be assessed separately.

9. Interfaces with financial reporting

Project systems and financial ledgers should reconcile through controlled interfaces. The general ledger provides authoritative financial postings, while project systems may contain richer operational detail. Common reconciliation differences arise from:

  • timing of accruals and invoice processing;
  • foreign-exchange remeasurement;
  • tax treatment;
  • capitalization journals;
  • intercompany charges;
  • overhead allocations;
  • work-in-progress and inventory adjustments;
  • rejected or corrected transactions;
  • different definitions of actual cost.

A monthly close process should include transaction cut-off, review of uninvoiced receipts, accrual calculation, commitment reconciliation, capitalization review, depreciation posting, variance analysis and sign-off. A reconciliation should explain the difference rather than simply force the two systems to agree.

For long-term contracts, revenue and profit recognition may involve estimates of progress, performance obligations, contract modifications, variable consideration and expected losses. Project cost information is therefore an input to financial reporting, not a substitute for accounting judgment. A project manager may report 70% physical progress, but the financial-reporting conclusion depends on the applicable accounting framework and evidence supporting progress measurement.

10. Integrated case: the North River Hospital Expansion

The following is an illustrative case, not a report of an actual organization.

Background

North River Health Authority is delivering a hospital expansion through a design-and-build contract. The project has a $48 million approved budget and uses a WBS covering design, enabling works, structure, building services, commissioning and handover. Management notices that the project dashboard shows a lower cost than the general ledger and that the forecast is improving despite several unresolved supplier claims.

Problem

Investigation identifies four issues. First, site supervision is charged directly to major work packages while corporate engineering support is allocated using a single labour-cost percentage. Second, a $1.2 million mechanical subcontractor invoice is recorded, but approximately $180,000 of work performed before month end has not been accrued. Third, purchase orders worth $2.4 million are included in the forecast as if they were additional costs, even though $900,000 has already been invoiced. Fourth, temporary power equipment is capitalized without a documented assessment of when it became available for use.

Analysis

The project controls team maps each transaction to project, WBS, cost element, cost centre and accounting period. It defines:

  • actual cost as posted invoices plus approved month-end accruals;
  • commitments as open, unperformed purchase-order value;
  • forecast final cost as actual cost plus remaining commitments and a separately justified estimate for uncommitted work.

The team reviews the overhead base and finds that engineering support is driven more by design hours and review packages than by labour cost. It develops two activity pools: design review and procurement administration. Site supervision remains direct because timesheets identify the project and work packages reliably.

The mechanical subcontractor's $180,000 accrual is supported by progress certification and is recorded with a reversal scheduled for the next period. The commitment schedule is corrected to exclude the $900,000 already invoiced. Equipment capitalization is reviewed: the temporary power unit was available for use on 1 April, so depreciation begins from that date under the entity's policy; costs for abnormal standby and unrelated training are expensed.

Outcome

The revised cost report increases actual cost by $180,000, reduces open commitments by $900,000 and reallocates shared support cost using documented drivers. The forecast does not simply improve or worsen; it becomes more credible. Management can distinguish a genuine saving from a timing difference and can challenge the unresolved supplier claim separately from recorded cost.

Learning points

  1. A project dashboard requires explicit definitions of actual, accrued, committed and forecast cost.
  2. Direct charging is appropriate only when tracing is reliable and economically meaningful.
  3. Allocation bases should reflect resource consumption, not merely data convenience.
  4. Capitalization decisions require evidence, policy compliance and an in-service date.
  5. Reconciliation is an analytical control, not a mechanical exercise in making numbers equal.

11. Governance, ethics and professional judgment

Cost data can influence bonuses, contract claims, investment decisions and public accountability. Deliberately delaying an invoice, omitting a known accrual or moving an expense to a capital account to improve current performance is unethical and may breach law, accounting standards or contract terms. Cost coding should represent economic substance, not desired performance.

Important controls include segregation of duties, approval limits, audit trails, independent review of estimates, access controls, versioned budgets, supplier-master controls and documented override procedures. Estimates should record assumptions, confidence levels and evidence. A manager should be able to explain not only the reported number but also what could cause it to change.

Confidentiality and privacy also matter. Timesheets, supplier rates and employee information may be commercially or personally sensitive. Access should follow least-privilege principles, and data retention should comply with applicable law and contractual requirements.

12. Technology, data quality and contemporary practice

Enterprise resource planning platforms increasingly integrate procurement, timesheets, inventory, project controls and the general ledger. Application programming interfaces can transfer transactions automatically, while dashboards expose trends in commitments, accruals and forecast variance. These benefits depend on master-data governance and clear ownership.

Artificial intelligence can assist with invoice classification, anomaly detection, duplicate-payment identification and prediction of likely accruals. However, AI-generated classifications remain estimates or recommendations unless validated. Models can reproduce historical miscoding, misinterpret unusual contracts and create false confidence. Organizations should retain source evidence, monitor model performance, document human approval and prevent automated posting where the risk is material.

Useful data-quality measures include completeness of mandatory codes, percentage of transactions posted to valid WBS elements, age of unreconciled items, accrual reversal accuracy and commitment-to-invoice conversion. A precise dashboard built on incomplete data is less valuable than a transparent report with known limitations.

Best-practice framework

A mature project cost system should:

  1. design the WBS, CBS, COA and responsibility structure together;
  2. define every material cost category in a coding dictionary;
  3. distinguish traceable costs from allocated costs;
  4. select allocation drivers based on causality and proportionality;
  5. maintain separate actual, accrued, committed and forecast views;
  6. document capitalization criteria and asset in-service dates;
  7. reconcile project records to the general ledger each reporting period;
  8. investigate variances rather than merely explaining them after the fact;
  9. preserve audit trails for journals, overrides and estimate changes;
  10. review whether the reporting system supports decisions, accountability and fair contract administration.

Chapter Summary

Project cost accounting translates operational activity into controlled financial information. Cost codes, WBS elements and chart-of-accounts dimensions identify where, why and when costs arise. Direct costs are traced to cost objects, while indirect costs are assigned through rational allocation methods. Job costing is suitable for distinct projects; activity-based costing provides greater visibility where diverse activities consume shared resources.

Accruals recognize work performed before invoicing, commitments represent authorized future obligations, and cash records payment timing. These categories must be defined so that forecast calculations do not double-count costs. Capitalization records qualifying expenditure as an asset, while depreciation allocates depreciable cost over useful life. Project systems must reconcile with the general ledger while recognizing that managerial reporting and statutory financial reporting answer different questions. Ethical governance, reliable master data, documented assumptions and human judgment remain essential even when technology and AI automate transaction processing.

Key Terms

Cost object: An item, project, activity or asset for which cost is measured.

Cost centre: An organizational or operational unit that accumulates costs.

Cost driver: A factor that causes or explains resource consumption.

Cost code: An identifier used to classify and report a transaction.

Chart of accounts: The structured list of accounts used in an accounting system.

Work breakdown structure: A hierarchical decomposition of project scope.

Cost breakdown structure: A hierarchical classification of project costs.

Control account: A management control point linking scope, budget, schedule and responsibility.

Direct cost: A cost economically traceable to a cost object.

Indirect cost: A shared cost assigned through an allocation process or treated as a period cost.

Job costing: Accumulation of costs for an identifiable job or project.

Overhead rate: A rate used to assign shared costs to cost objects.

Activity-based costing: Costing that assigns activity-pool costs using activity drivers.

Accrual: Recognition of an incurred cost before invoice or payment.

Commitment: An authorized future obligation, commonly represented by a purchase order.

Capitalization: Recognition of qualifying expenditure as an asset.

Depreciation: Systematic allocation of an asset's depreciable amount over its useful life.

General ledger: The primary accounting record containing financial postings.

Cost reconciliation: An explanation and control comparison between project records and accounting records.

Review Questions

Short Answer Questions

  1. What is the difference between a cost object and a cost centre?
  2. Why should a project coding dictionary define both inclusions and exclusions?
  3. Distinguish an accrual from a commitment.
  4. State the straight-line depreciation formula and define its variables.
  5. Why may a single organization-wide overhead rate distort project cost?

Long Answer Questions

  1. Explain how a WBS, CBS and chart of accounts can be integrated into a project cost-control system.
  2. Compare job costing and activity-based costing, including their assumptions, benefits and limitations.
  3. Discuss how capitalization and depreciation affect both project-control reports and financial statements.
  4. Explain the controls required for a reliable month-end project cost close.
  5. Evaluate the ethical risks of manipulating accruals, commitments or capitalization classifications.

Analytical / Application Questions

  1. A project has direct labour of $150,000, direct materials of $80,000 and subcontracting of $45,000. Overhead is applied at 20% of direct labour. Calculate total job cost and explain one assumption behind the allocation.
  2. An activity pool costs $240,000 and has an expected driver volume of 800 purchase orders. A project uses 26 purchase orders. Calculate its assigned cost and explain when this rate might be inappropriate.
  3. A project report shows invoiced cost of $2.1 million, an evidence-based month-end accrual of $160,000 and open purchase orders of $900,000, of which $250,000 relates to already accrued work. Assuming no other forecast cost, calculate the non-duplicated forecast final cost and explain the treatment of the overlapping commitment.

Multiple Choice Questions with Answers

Question 1

Which item is a cost object?

A. A project work package for which costs are measured

B. The organization’s approval hierarchy

C. A supplier’s bank account

D. The accounting-period closing date

Correct Answer: A. A project work package for which costs are measured

Question 2

A predetermined overhead rate is calculated as:

A. Actual overhead divided by actual profit

B. Budgeted overhead divided by budgeted allocation base

C. Budgeted profit divided by actual labour

D. Actual cash paid divided by budgeted revenue

Correct Answer: B. Budgeted overhead divided by budgeted allocation base

Question 3

A project uses 240 machine hours at an overhead rate of $30 per machine hour. What overhead is assigned?

A. $7,200

B. $8,000

C. $27,000

D. $72,000

Correct Answer: A. $7,200

Question 4

Which statement best describes an accrual?

A. A future possibility with no authorization

B. A cost recognized when work has been received before the invoice arrives

C. Cash paid before any goods or services are received

D. The unused balance of a cancelled purchase order

Correct Answer: B. A cost recognized when work has been received before the invoice arrives

Question 5

Which item is normally a commitment rather than an actual cost?

A. An approved invoice already posted

B. A month-end estimate for work performed

C. The unperformed balance of an open purchase order

D. Depreciation already recorded in the ledger

Correct Answer: C. The unperformed balance of an open purchase order

Question 6

An asset costs $500,000, has a $50,000 residual value and a five-year useful life. What is annual straight-line depreciation?

A. $50,000

B. $90,000

C. $100,000

D. $110,000

Correct Answer: B. $90,000

Question 7

What is a central feature of activity-based costing?

A. It assigns all overhead using revenue

B. It assigns activity-pool costs using cost drivers

C. It excludes indirect costs from project reports

D. It records only cash transactions

Correct Answer: B. It assigns activity-pool costs using cost drivers

Question 8

Which condition most strongly supports treating a cost as direct?

A. The cost improves the project’s reported margin

B. The cost can be traced reliably and economically to the project

C. The cost was incurred by a senior manager

D. The cost is paid in the same month as the work

Correct Answer: B. The cost can be traced reliably and economically to the project

Question 9

If actual overhead exceeds applied overhead, overhead is:

A. Over-applied

B. Under-applied

C. Capitalized automatically

D. A commitment

Correct Answer: B. Under-applied

Question 10

In the formula forecast final cost = actual + accrued + remaining committed + uncommitted forecast, why must already accrued commitment value be excluded from remaining commitments?

A. To increase the reported project margin

B. To avoid double-counting the same work

C. To convert an expense into an asset

D. To eliminate all purchase orders

Correct Answer: B. To avoid double-counting the same work

Project Cost Estimation & Budgeting
Chapter 3 of 14