CONTROLLER OR PROJECT ACCOUNTANT? ONE OWNS THE JOBS, ONE OWNS THE COMPANY.
A project accountant owns the job-level detail: cost coding, subcontractor invoices, change orders, pay applications, lien waivers and retainage on each job. A controller owns the company-level result: the close, the reconciliations, the WIP schedule, the financial statements and the controls that keep the job detail honest. Most subcontractors under about $10M need the controller function first, because a clean job ledger still produces a wrong P&L when no one reviews it against cost to complete.
The project accountant role shows on org charts once a company has enough jobs that the bookkeeper cannot keep up with pay applications and change orders. It is a production role, close to the project managers and the field. The controller role is a review role. The two work together: the project accountant makes each job's numbers complete, and the controller decides whether the company's numbers are right. When a company hires a project accountant before it has a controller, the job detail improves and the monthly profit figure still surprises the owner.
WHAT EACH ONE DOES.
| Capability | Project accountant | Controller |
|---|---|---|
| Focus | One job at a time | The whole company |
| Main output | Pay apps, coded costs, job files | Closed books, WIP, financial statements |
| Works most with | Project managers and the field | The owner, the CPA, the surety and the bank |
| Cost to complete | Supplies the cost detail | Reviews the estimate with the PM |
| Retainage | Bills and tracks it by job | Reconciles it and watches the aging |
| Controls | Follows the approval rules | Writes and enforces the approval rules |
| Usual first hire at | When billing volume outgrows the bookkeeper | When the owner stops trusting the P&L |
| Where it goes wrong | Clean job files and a wrong P&L | A good review of messy job detail |
Salary figure is the BLS median for accountants and auditors, May 2025. Project accountant pay varies with construction experience and market.
EVERY JOB'S NUMBERS, COMPLETE AND CODED.
A project accountant codes costs to the right job and cost code, processes subcontractor and supplier invoices against commitments, builds pay applications from the schedule of values, collects lien waivers and tracks retainage by job. They work beside the project managers and keep the job file current.
This is the right hire when pay applications go out late, change orders get billed months after the work, or subcontractor invoices are paid without a check against the commitment. The BLS median for accountants and auditors was $83,680 as of May 2025, which is a useful starting point for the salary.
THE COMPANY'S NUMBERS, REVIEWED AND SIGNED OFF.
A controller owns the month-end close, the bank and balance sheet reconciliations, the WIP schedule, the financial statements and the approval rules. They review cost to complete with the project managers and decide what the company's profit for the month is.
This is the right first step when the books close but the owner does not trust the profit figure, when the surety or the bank asks for statements no one can explain, or when jobs end far below the margin the WIP showed. It can be a full-time hire or a fractional service.
WHERE WE COME OUT.
Get the controller function in place first. A controller, full-time or fractional, sets the cost coding rules, the approval rules and the close, and those rules are what a project accountant follows. Hiring the project accountant first fills the job files and leaves the profit figure unreviewed.
Add a project accountant when pay applications, change orders and subcontractor invoices outgrow the bookkeeper. At that point the controller has someone to review, and the project managers get billing support that keeps cash coming in on schedule.
