Construction financial glossary
Drawings, dollars, and the decisions between them.
This glossary covers the terms contractors, project managers, controllers, and estimators use when discussing budgets, commitments, billing, and field reporting. Definitions are written for construction practice, not for accounting theory, and each entry stays close to how the term appears in an active job. Terms are grouped by workflow so you can read a section at a time.
Eight sections, grouped by workflow
Cost and job costing
Job costing is the practice of assigning every cost to a specific job and cost code so a report can show, at any point, what a project has spent against its budget. Get the code structure wrong at setup and every report after it has to be read with an asterisk.
Cost code
A category within the job's cost structure, such as 03-100 for concrete or 09-250 for drywall. The numbering convention matters more than most contractors expect, because changing it mid-job forces a migration and every prior report loses its footing.
Cost report
The output of job costing: a summary of actual cost, committed cost, and remaining budget, usually viewed per job or per cost code. A cost report only means something when those three columns agree with the ledger behind them.
Budget transfer
The internal move of money between cost codes on the same job, typically after a scope change or a re-estimate. A transfer shifts where the money sits; it does not change the contract value, which is why it stays separate from a change order.
The three terms work as one set. A cost code gives a cost a home, the cost report reads what lives there, and a budget transfer re-plans the neighborhood when a scope shifts under the job. If your team uses the terms loosely, the first symptom shows up in a variance report nobody trusts.
Commitments and contracts
A commitment is money the contractor has promised to spend but has not been billed for yet. Purchase orders and subcontracts are the primary examples, and a change order joins them the moment it is approved. The distinction matters because a commitment is real exposure to the budget even while the ledger still shows it as available.
Keep the terms straight when you review a job's position: the commitment column tells you what is already spoken for, and anything you read as "remaining" without reading commitments beside it is a number in disguise.
A purchase order or subcontract that has been issued and approved. It reduces the money you still have to spend, even before the first invoice arrives.
A formal authorization to a supplier for materials or equipment at an agreed price. The delivered price, not the quoted one, is what the commitment should carry.
The equivalent agreement with a trade contractor, covering scope, price, schedule, and terms. A subcontract usually carries the retainage and lien-waiver provisions the rest of the page depends on.
A written modification to the contract scope, price, schedule, or some combination. It becomes a commitment the moment it is approved, which is why the approval date and the commitment date should never be argued about later.
A budget line reserved for unforeseen conditions. Contingency sits inside the approved budget; a change order modifies contract value. Spending contingency does not raise the contract sum, and treating the two as the same line quietly breaks the job's cost report.
Billing and payment
Billing terms describe the path money takes from the contract price to the contractor's bank account. Each term in this section feeds the next one, and a misread in the first few rows shows up as a disputed pay application a month later.
The breakdown of the contract price into line items tied to cost codes, forming the basis for each pay application. A line item that no longer matches its cost code fights the cost report for the rest of the job, which is why both lists belong to the same structure.
Also called a progress payment request.
The contractor's periodic request for payment based on work completed. It is usually submitted on a standard form and depends on the schedule of values, the billing period, and the retainage withheld to date.
The percentage of each payment withheld by the owner until substantial completion or a defined milestone. The percentage lives in the contract, and the amount actually withheld lives in the pay application - read both before you forecast cash.
The point at which the work is sufficiently complete for its intended use, and it typically triggers retainage release and the start of the warranty period. It is a documented date, not a feeling, and the record of it usually sits in the project's closeout correspondence.
The end of the line: it follows the punch list and any remaining closeout items, and it usually releases whatever retainage remains. Between substantial and final completion, the job is still carrying cost with no new billing, which is exactly why the two dates are tracked separately.
Field and project documentation
Field documentation is the record that makes a cost report or a delay claim stand up. A daily log nobody reads is still evidence, and the difference between a defensible RFI and an argument is usually whether the question was written down the day it came up.
Schedule and coordination
Schedule terms carry a financial weight that is easy to miss: a delay that qualifies for a time extension protects the finish date, while a compensable delay can move money as well. Contract language decides which one you have, and the terms below are the ones that come up when you discuss it.
The project plan for sequencing work over time, usually including milestones, durations, and dependencies.
A significant date or event, such as topping out or substantial completion, that anchors the schedule.
A short-horizon view, typically three to six weeks, that coordinates near-term work across trades. It is the version the field actually works from.
Any event that pushes the schedule later than planned. Whether it is excusable or compensable depends on the contract language, not on how obvious the cause looks in the field.
A schedule adjustment granted for a qualifying delay. It moves the finish date without necessarily moving money, which is why the two are asked for on separate lines.
The milestone that most schedule disputes circle back to, because it sits at the intersection of retainage, warranty, and liquidated damages language.
Financial reporting
Work in progress is the accounting view of jobs that are underway, showing costs incurred, revenue recognized, and over- or under-billing. Over-billing means you have billed more than you have earned, which sits as a liability; under-billing means the reverse, which sits as an asset. A contractor who reads the WIP schedule with the same attention as the bank balance stops most cash surprises before they land.
The timing of money in and money out, and in construction it rarely matches the calendar of work performed. That gap is why a profitable job can still leave a contractor short on payroll Friday.
Two sides of the same WIP line. Reading them together tells you whether the business is funding the job or the job is funding the business.
A portfolio of projects managed under a single owner or institution, reported at the portfolio level rather than per job. A capital program rolls up WIP from dozens of jobs, and the terms above stack when it does.
Vendors, suppliers, and trades
A vendor bill is a supplier or subcontractor invoice, and matching it to a purchase order, subcontract, or delivery ticket is the core of accounts payable in construction. Without a match, a payable is just a claim - and every one of the terms below exists because that match tells you what to pay, when to pay it, and what to withhold until later.
The four terms on this side of the page are the ones most likely to appear on a compliance checklist or a payment condition. Read them with the billing section in mind, because a retainage release and a lien waiver are usually the same conversation.
A supplier or subcontractor invoice. Matching it to a purchase order, subcontract, or delivery ticket is the core of accounts payable in construction.
A document in which a party gives up its right to file a mechanic's lien, often required as a condition of payment. The waiver's scope should match the payment it accompanies.
A payment made to both a subcontractor and its supplier, used when the supplier's exposure to the sub is significant. It protects the supplier while keeping the sub's contract whole.
The documented payroll required on public works projects, showing each worker's classification and hours. It is a compliance record before it is a cost record.
Software and systems
Vendors describe their products with words that belong to two different layers: platforms that host many workflows, and tools that solve one job well. Knowing which layer a vendor is selling helps you compare proposals without comparing unrelated things. When you evaluate construction management software, the terms below are the ones that show up most often in a demo.
A software system that hosts multiple workflows, as distinct from a tool that addresses a single function. A platform handles job costing, commitments, and field reporting without a handoff to another product.
A connection between a project management system and an accounting system that moves records without manual re-entry. Its reliability varies by vendor, so the sync is worth testing against a live job before you commit.
A unified back-office system covering accounting, payroll, and cost control. Trimble Viewpoint is an example in construction. An ERP is where the general ledger lives; a project platform usually feeds it rather than replacing it.
One built for jobsite use, typically covering plans, tasks, punch lists, and daily reporting. Fieldwire is an example. The term names a tool, not a platform - the line between the two is what it can do alone.
How to use this glossary
This page is a working reference, not a course. Skim the section that matches your current question, and come back when the next one arrives. The routes below are the three ways contractors actually use it.
The commitment, billing, and software terms come up most often in demos. If a vendor uses them loosely, ask which one they mean - the answer tends to reveal how the product is actually built.
The field documentation and financial reporting sections carry the vocabulary a new hire needs in the first month. Sit them on those two before their first pay application review.
If a cost report is being questioned in a meeting, read the term's definition back. Half of the disagreements are about the word, not the number.
If a term is missing or unclear, send a note and we will look at it. The glossary grows from the questions working contractors actually ask, and a definition that does not help the person reading it at the bench is not finished yet.
Cmigolabe Agent publishes this glossary as part of an independent educational resource for evaluating construction project management and construction business management software, with a focus on job costing, commitments, change orders, and office-to-field workflows for U.S. contractors.
Continue from here
If you are evaluating construction management software for your business, the next useful read is the job costing and financial management guide - it walks through the workflows whose terms are defined above. If you would rather start with the evaluation itself, the platform directory and the selection criteria give you a side-by-side way to compare products on the same terms.
If a term is missing or unclear, send us a note at Contact Us.
