Project-Based Accounting: How to Monitor Site and Project Profitability

What is Project Accounting?

Project accounting tracks the financial performance of each project independently.

Project accounting is an accounting methodology that enables the tracking of revenue and expenses on a project, site, or work-package basis. Unlike traditional calendar-based accounting, project accounting tracks the entire financial lifecycle of a project from inception to completion.

The core characteristics of this approach include:

• Project profit center: Each project is treated as an independent profit/loss center.
• Cost allocation: All costs are assigned to specific projects or work packages.
• Revenue matching: Revenue is recognized in the same period as the associated costs.
• Lifecycle tracking: The project is monitored financially from start to finish.
• Profitability visibility: Current profitability status can be reported at any time.

Why is Project Accounting Necessary?

In project-based sectors (construction, engineering, consulting, software development), calendar-based accounting falls short:

Limitations of Calendar-Based Accounting

• What does the year-end mean for a 24-month project?
• What does the total profit of 15 different projects in the same period tell us?
• How do we identify which project is profitable and which is losing money?
• How do we detect cost overruns in work-in-progress?

Benefits of Project Accounting

• Independent profit/loss status for every project
• Early warning signs for cost overruns within projects
• Realistic completion projections (EAC)
• Progress billing and cash flow management
• Project-based decision making

Core Concepts

Understanding the fundamental concepts of project accounting is critical:

• WBS (Work Breakdown Structure): The hierarchical work package structure of the project.
• Cost Center: An organizational unit where costs are aggregated.
• Cost Element: Types of costs (labor, material, subcontracting, etc.).
• Budget: Planned cost and revenue values.
• Actual: Realized cost and revenue values.
• Commitment: Costs that have been committed but not yet realized.
• EAC (Estimate at Completion): The estimated total cost at the end of the project.
• ETC (Estimate to Complete): The estimated cost of the remaining work.
• POC (Percentage of Completion): The percentage of work completed.

WBS – Work Breakdown Structure Design

WBS enables control by breaking the project down into manageable work packages.

WBS (Work Breakdown Structure) is the structure that hierarchically divides project deliverables into smaller, manageable components. In project accounting, the WBS forms the framework for cost aggregation and reporting.

WBS Design Principles

1. The 100% Rule

The WBS must cover the entire project—no more, no less. Each work package must represent 100% of its parent level.

2. Mutually Exclusive

There should be no overlap between work packages. The same work should not be assigned to two different packages.

3. Manageable Size

Work packages should be of a size that is trackable, assignable, and measurable. Neither too large nor too small.

4. Result-Oriented

WBS elements should be defined by deliverables/results, not by activities.

WBS Levels

A typical construction project WBS structure:

WBS Coding System

Establish an effective WBS coding system:

• Hierarchical code: 1.0 > 1.1 > 1.1.1 > 1.1.1.1
• Project prefix: PRJ001-1.1.1
• Phase/area indicator: STR (Structural), FIN (Finishing), MEC (Mechanical)

Example coding: PRJ001-STR-01-003

• PRJ001: Project code
• STR: Structural phase
• 01: Foundation work package group
• 003: Concrete pouring work package

WBS and Accounting Integration

The WBS works integrated with the accounting system:

• Cost collection point: Every WBS element collects costs.
• Budget allocation: Budgets are assigned to WBS levels.
• Actual cost: All expenses are recorded against the WBS element.
• Comparison: Budget vs. Actual analysis is performed on a WBS basis.
• Reporting: Consolidation is possible at any desired level.

Cost Center and Chart of Accounts Structure

The cost center structure is the foundation of financial tracking for projects.

A cost center is an organizational unit where costs are collected and controlled. In project accounting, each project, site, or job is typically defined as a separate cost center.

Cost Center Hierarchy

A typical project organization’s cost center structure:

• Level 1 – Company: The top level where all costs are consolidated.
• Level 2 – Business Unit: Lines of business such as Construction, Contracting, Real Estate.
• Level 3 – Project Group: Grouping by region, client, or project type.
• Level 4 – Project: Individual project or site.
• Level 5 – Sub-Project: A phase or section within a project.

Chart of Accounts Design

The chart of accounts for project accounting should be designed to capture cost elements:

Direct Costs

• 510 – Material Expenses
  • 510.01 – Construction Materials
  • 510.02 – Electrical Materials
  • 510.03 – Mechanical Materials
  • 510.04 – Consumables
• 520 – Labor Expenses
  • 520.01 – Direct Labor
  • 520.02 – Overtime
  • 520.03 – Social Benefits
• 530 – Subcontractor Expenses
  • 530.01 – Structural Subcontractors
  • 530.02 – Mechanical Subcontractors
  • 530.03 – Electrical Subcontractors
• 540 – Equipment/Machinery Expenses
  • 540.01 – Rented Equipment
  • 540.02 – Owned Equipment Depreciation
  • 540.03 – Fuel and Maintenance

Indirect Costs

• 550 – Site General Expenses
  • 550.01 – Site Management Personnel
  • 550.02 – Site Facilities
  • 550.03 – Health and Safety
• 560 – General Administrative Overheads
  • 560.01 – Head Office Overhead Allocation
  • 560.02 – Insurance Expenses

Cost Allocation Rules

Clear rules must be established for assigning costs to the correct project and WBS element:

• Direct costs: Assigned directly to the specific project.
• Common costs: Distributed using allocation keys.
• Overheads: Applied using a pre-determined rate or formula.

Allocation Keys

• Direct labor hour rate
• Direct cost ratio
• Revenue ratio
• Square meter ratio

Revenue Recognition Methods and Percentage of Completion

Accurate revenue recognition ensures realistic reporting of project profitability.

In project accounting, revenue recognition determines when and how much revenue a project reports. This is a critical accounting policy for long-term projects.

Core Revenue Recognition Methods

1. Percentage of Completion (POC) Method

The POC method recognizes revenue gradually as the project progresses:

• Revenue is recognized in each period as the project progresses.
• Revenue and cost matching is achieved.
• Profitability can be reported in every period.
• The preferred method under accounting standards (IFRS 15).

2. Completed Contract Method

The Completed Contract method recognizes all revenue at the end of the project:

• Revenue is reported only when the project is completed.
• Profitability is not visible during the project duration.
• May be preferred for projects with high uncertainty.
• A conservative approach.

Percentage of Completion Calculation Methods

Cost-to-Cost

The most commonly used method:

Completion % = Actual Cost / Estimated Total Cost x 100

• Advantage: Objective and verifiable.
• Disadvantage: Cost overruns artificially increase completion.

Units Delivered

Physical progress measurement:

Completion % = Units Completed / Total Units x 100

• Advantage: Reflects physical progress.
• Disadvantage: Suitable for uniform work, difficult for complex projects.

Milestone-Based

Based on milestone completion:

• Advantage: Captures major stages.
• Disadvantage: High fluctuation between periods.

Revenue Recognition Formula

Revenue recognized in each period:

Revenue in Period = (Total Contract Value x Cumulative Completion %) – Total Revenue Recognized in Previous Periods

Example calculation:

• Contract value: 100 units
• Estimated total cost: 80 units
• Actual cost at period end: 40 units
• Completion %: 40 / 80 = 50%
• Recognized revenue: 100 x 50% = 50 units
• Recognized cost: 40 units
• Gross profit: 10 units

Progress Billing Process

The progress billing process is the backbone of project cash flow.

Progress billing refers to the gradual payments requested from the employer or client in exchange for work performed. The progress billing system, which is standard practice in the construction sector, directly affects cash flow.

Types of Progress Billing

Progress Payment

• Performed periodically (usually monthly).
• Measurement and evaluation of work performed.
• Withholding tax is usually applied (5-10%).

Final Payment

• Performed when the project is completed.
• All work items are closed.
• Withholdings are released.

Steps in the Progress Billing Process

1. Measurement: Physical measurement of the work performed.
2. Evaluation: Calculation of total value using unit prices.
3. Report Preparation: Creating the report with supporting documents.
4. Internal Approval: Project manager and finance approval.
5. Client Presentation: Submitting the billing file.
6. Client Review: Technical review and approval.
7. Invoicing: Issuing the invoice for the approved amount.
8. Collection Tracking: Due date tracking and collection.

Progress Billing Performance Metrics

• Billing Cycle Time: Time from measurement date to billing submission.
• Approval Time: Time from submission to client approval.
• Collection Time: Time from invoice to collection.
• DSO (Days Sales Outstanding): Number of days for billing receivables.
• Withholding Accumulation: Total pending withholding amount.

Relationship Between Billing and Revenue Recognition

Issuing a progress invoice and recognizing revenue are different concepts:

• Progress Billing: Amount requested from the client (invoicing).
• Revenue Recognition: Revenue recognized according to accounting standards.

These two amounts may differ:

• Billing > Recognized Revenue: Contract liability (deferred revenue).
• Billing < Recognized Revenue: Contract asset (unbilled revenue).

EAC/ETC Calculations and Projections

EAC/ETC calculations are critical for forecasting the financial status at the end of the project.

One of the most critical questions in project accounting is “where will we be at the end of the project?” EAC (Estimate at Completion) and ETC (Estimate to Complete) calculations answer this question.

Core Concepts

• BAC (Budget at Completion): Original total budget.
• AC (Actual Cost): Cost realized to date.
• EV (Earned Value): The budget value of the work performed.
• PV (Planned Value): The budget value of the work that should have been performed.
• ETC (Estimate to Complete): Estimated cost of remaining work.
• EAC (Estimate at Completion): Estimated total cost at the end of the project.
• VAC (Variance at Completion): Budget – EAC difference.

Performance Indices

CPI (Cost Performance Index)

CPI = EV / AC

• CPI > 1: Under budget (good).
• CPI = 1: On budget.
• CPI < 1: Over budget (bad).

SPI (Schedule Performance Index)

SPI = EV / PV

• SPI > 1: Ahead of schedule.
• SPI = 1: On schedule.
• SPI < 1: Behind schedule.

ETC Calculation Methods

Method 1: Based on Original Estimate

Assumption that remaining work will be completed within the original budget:

ETC = BAC – EV

Method 2: Based on Current Performance

Assumption that current cost performance will continue:

ETC = (BAC – EV) / CPI

Method 3: Detailed Re-estimation

Re-evaluation of remaining work packages:

ETC = Updated estimate for each work package

EAC Calculation Formulas

Basic EAC

EAC = AC + ETC

CPI-Based EAC

EAC = AC + (BAC – EV) / CPI

or

EAC = BAC / CPI

CPI and SPI-Based EAC

Considering both cost and schedule performance:

EAC = AC + (BAC – EV) / (CPI x SPI)

Example Calculation

Comment: The project is 40% complete, but with a CPI of 0.89, it is trending toward a budget overrun. If current performance continues, the budget will be exceeded by 12.4% at the end of the project.

EAC Update Discipline

• EAC should be updated at least monthly.
• Must be updated immediately for significant changes (scope, risk).
• Detailed analysis should be performed at the WBS level.
• Update history and justifications must be documented.

Field Example: Project Accounting Implementation

7 Most Common Project Accounting Mistakes

1. Working Without a WBS

Aggregating costs at the project level without tracking them at the work-package detail. Result: You don’t know where the cost overrun is; you only say “the project was expensive.” Meaningful analysis is impossible without a WBS.

2. Incorrect Cost Allocation

Assigning costs to the project where they are easiest to find rather than using allocation keys. Some projects appear more profitable than they are, while others appear to be losing money. True profitability is hidden.

3. Not Tracking Commitments

Monitoring only realized costs while ignoring committed costs. Materials ordered but not yet invoiced are not seen. Sudden “surprise” costs emerge.

4. Neglecting EAC Updates

Not updating the initial estimate throughout the project. In an 18-month project, you are still comparing against the original budget in the 12th month. No realistic projection is made.

5. Revenue-Cost Matching Error

Recognizing revenue when the bill is issued and cost when the invoice arrives. Periodic profitability reports become misleading. Incompatibility with accounting standards.

6. Ignoring Overhead Distribution

Assigning only direct costs to projects and not distributing overheads. Projects appear profitable, but there is a loss across the company. Pricing decisions are made incorrectly.

7. Not Linking Billing to Cash Flow

Treating the billing process only as an accounting task and separating it from cash flow projections. Billing delays lead to financing crises. Proactive management is not performed.

Project accounting mistakes eliminate profitability visibility.

Project Profitability Metrics Table

Track the following metrics to measure the effectiveness of your project accounting system and project performance:

Measurement frequency: CPI/SPI and EAC should be tracked weekly, profitability metrics monthly, and DSO weekly. Real-time visibility should be provided in dashboards.

Project Accounting Checklist

Frequently Asked Questions (FAQ)