The money side of the job
An independent guide to how job costing, commitments, change orders, retainage, and vendor bills actually connect — written for U.S. contractors who read a budget report weekly, not annually.
What this page is for
Construction financial management is the discipline of knowing what your job costs, what you have committed to spend, and what you are owed — before the job ends rather than after. Job costing is the accounting method underneath it. Contracts, change orders, retainage, the schedule of values, vendor bills, and field reporting all feed into the same picture, and when any one of them lives in a separate spreadsheet, that picture gets blurry at exactly the wrong moment.
This page walks through how those pieces fit together in practice. The vocabulary is defined in our glossary; here we are more interested in how the workflows interact — which is the part that usually decides whether your reporting tells the truth on a Wednesday or the following month.
How the picture forms
A single line on a job-cost report looks like a fact. It is actually the sum of several movements that arrive on their own schedules — some from the field, some from the office, some from the owner's reviewer. Knowing which input is late is half the diagnosis.
The structure that makes everything else legible. Every cost gets a job and a code, so a report can compare spend to budget mid-project. Renumber the codes halfway through a job and the migration is the kind nobody recovers from gracefully — which is why the setup phase deserves real hours, not a default template.
Set once · held for the life of the job
Purchase orders and subcontracts — money promised but not yet billed. The input that traditional reports miss for sixty days.
Scope you are already performing, waiting on a price. Kept in one tracked state from request to approval.
The percentage held back per pay application until substantial completion. A cash-flow story told one job at a time.
Every supplier invoice matched to something: a purchase order, a subcontract, a delivery ticket, a cost code.
Match, don't remember
When those five inputs arrive on time and route to the same account, the report narrows to a decision a superintendent and a controller can actually have. When one of them is late — usually commitments, sometimes the change order, often the vendor bill — the report still looks clean. It just is not true yet.
Commitment to billed
The schedule of values breaks the contract price into line items tied to cost codes, and it becomes the basis for every pay application from first invoice to closeout. Every amount you bill should map cleanly back to a cost you have already incurred — when the two diverge, the accounting gets messy, and the owner's reviewer notices before your controller does.
Contract price
Broken into line items at kickoff, mapped to cost codes the field already uses.
Field progress
Daily logs and site photos say what is complete; the line items give it a price.
Pay application
Amounts billed per line item, retainage withheld on each — a field, not an afterthought.
Reconciled job cost
Billed, committed, and actual sit beside each other without manual stitching.
Cash flow distortion
Retainage protects the owner from unfinished work and defective materials. It also means every active job ties up a share of working capital for months at a time. Track it per job and per pay application — not once a quarter — and the release dates stay visible instead of accidental.
The expensive gap
The financial risk is rarely the modified scope itself — it is the stretch between work beginning and the change being priced, approved, and reflected in the job cost report. When that stretch runs weeks long, you are financing the change out of your own cash flow, and the total exposure stays fuzzy until close.
Tracked states from request through approval collapse that gap: the committed amount updates the budget the same day the change is signed.
Field is finance
Daily logs, site photos, punch list items, RFIs, and submittals all carry financial weight. A weather delay written up properly becomes the basis for a time extension. A punch list that outlives substantial completion delays retainage release. Site photos prove work performed for a pay application.
How each input behaves
Contractors evaluating construction management software usually test one workflow in the demo and discover the others on the live job. The table is the shape to test against — what moves the budget, on what cadence, and what a clean report should show you without deep digging.
Questions worth asking
The same five questions surface in every contractor evaluation we have seen — general contractors, specialty trades, and owner-side teams all end up asking them in one form or another. They are the useful parts of a demo that a features comparison rarely reaches.
Which side of the table you sit on
A capital program is a portfolio of projects managed under a single owner or institution, and it lives in a different reporting universe than a contractor's job cost reports. The connection point is the contractor's billing, change order, and retainage history on each project — those become one input to the owner's schedule, budget, and cash-flow picture across the program.
Recognizing which side of that relationship you are on changes what you should ask from software. A contractor wants line-level job cost and a clean pay application; an owner wants portfolio-level schedule and cash flow. A system that tries to serve both without naming which it is optimizing for usually serves neither well.
Compare construction management platforms
Where this leaves you
The workflows on this page can sit in one platform, in two, or in three plus a spreadsheet. There is no single right answer for every contractor — but there is one wrong answer, and it is the setup where the field data and the financial data never meet. If you cannot trace a change order from field observation to approved cost to billing line without manual reconciliation, the software is not doing its job.
