Change order accounting in construction: how COs affect job GP, WIP, and billing
Change order accounting in construction is the process of recording, recognizing, and reflecting contract modifications in a job's cost budget, revised contract value, and WIP schedule — distinct from a standard AR or cost entry because a CO changes the financial baseline of the entire job, not just a single transaction. The primary failure mode is straightforward: costs hit the job before the revised contract value and cost budget are updated in the accounting system, which distorts the WIP schedule and produces a false over- or underbilling position. For controllers managing multiple jobs or entities, an unapproved or undocumented CO is one of the fastest routes to margin erosion that doesn't surface until the job is nearly done.
Key takeaways
Here is what matters most before you compare options.
Change order definition: Change order accounting is the practice of updating a job's revised contract value, cost budget, and WIP schedule whenever the original scope changes — a fundamentally different process from posting a standard vendor invoice or customer payment.
Revenue recognition risk: Unapproved or unpriced change orders cannot be recognized as revenue under ASC 606 unless it is highly probable that a significant revenue reversal won't occur, which means premature recognition is a real audit exposure.
WIP consequence: Every CO that doesn't update revised contract value and cost budget will distort the WIP schedule, producing a false underbilling or overbilling position that misrepresents the job's true financial status.
Process chain: A CO must travel four steps — CO log, revised contract value, cost budget update, WIP recalculation — before it is correctly reflected in the WIP schedule and billing.
Tool fit: Flow ERP handles this chain natively for multi-entity construction operators; LiveFlow FP&A gives QBO-based teams live CO and WIP visibility without changing their existing stack.
Why do change orders cause job gross profit to fade and WIP to break?
Change orders cause job gross profit to fade when costs are incurred before the revised contract value and cost budget are updated in the accounting system. The job absorbs new costs against an unchanged budget, so the cost-to-budget variance widens and the percentage-of-completion calculation shifts — producing a WIP schedule that either overstates progress or understates the billing right a controller should have. For job costing reporting for specialty trade contractors, this gap between field reality and accounting records is one of the most consistent sources of close-day surprises.
The breakdown compounds in multi-entity or multi-job environments where the controller isn't physically close to the field. A project manager may approve a scope addition verbally, costs flow in immediately, and the accounting system doesn't see a CO log update until days or weeks later. By then, the WIP schedule for that reporting period is already wrong. This is a systems and process problem, not simply a project management failure — and it requires an accounting fix, not just a reminder to the field team.
What is profit fade in construction accounting?
Profit fade is the gradual erosion of a job's gross margin as actual costs outpace the revised estimate, typically only visible at project closeout when it's too late to recover. Change orders are one of the two primary causes of profit fade — the other being untracked cost overruns that never generate a formal CO at all. McKinsey's analysis of large construction projects found average cost overruns of approximately 80%, underscoring how pervasive budget drift is and why the accounting process must catch scope changes in real time, not retrospectively.
How change orders distort percentage-of-completion calculations
Percentage-of-completion (POC), the revenue recognition method standard for construction contracts, is calculated as costs incurred to date divided by total estimated cost. When a CO adds scope and associated cost but the denominator — total estimated cost — isn't updated, POC overstates the job's progress. Overstated progress means overstated recognized revenue, which can produce overbilling relative to actual work completed and inflate the job's reported GP before the project is done.
The reverse also happens: if a CO adds contract value but the cost budget isn't updated, the denominator stays low, POC climbs artificially, and the contractor bills ahead of where the job actually stands. Either distortion creates a WIP schedule that doesn't reflect reality, which is the document lenders, sureties, and auditors rely on most. For a deeper look at how over and underbilling work in construction, the mechanics connect directly to whether COs are hitting the accounting system on time.
What is the difference between approved and unapproved change orders for revenue recognition?
Approved change orders modify the original contract and are recognized as revenue immediately upon approval; unapproved or unpriced change orders require a probability assessment before any revenue can be recorded under ASC 606's variable consideration constraint. This is the gap most construction accounting resources skip over, and it's where controllers face the most audit exposure.
There are three CO states that carry different recognition and WIP treatment:
Approved and priced: Owner has signed the CO and the dollar amount is agreed upon. The revised contract value updates immediately, and revenue is recognized in the current period.
Approved but unpriced (time-and-materials or TBD): Owner has approved the scope change but the final price isn't set. Costs can flow, but revenue recognition is constrained until pricing is established or a reliable estimate is probable of collection.
Pending or disputed: Owner has not approved the CO; the contractor is performing the work under a claim or reservation of rights. Revenue recognition is constrained under ASC 606 unless highly probable collectibility criteria are met.
Change order states: accounting treatment by approval status | |||||
CO state | Revenue recognition timing | Revised contract value updated? | Cost budget update required? | Balance sheet presentation | Documentation required before recognition |
|---|---|---|---|---|---|
Approved and priced | Immediately upon approval | Yes | Yes | AR or contract asset if billed; underbilling if not yet billed | Signed change order with agreed price |
Approved, unpriced (TBD or T&M) | When price is reliably estimable and probable of collection | Partially — estimate only | Yes | Contingent asset; disclose in notes until priced | Written approval of scope; time and material logs |
Pending / disputed | Only when highly probable no significant reversal will occur | No (until approved) | Yes — costs still hit the job | WIP or CIP for costs; revenue constrained | Written claim, contract language supporting entitlement, prior owner behavior |
How to account for unapproved change orders under ASC 606
Under ASC 606, revenue from an unapproved CO is treated as variable consideration — meaning it is constrained unless the contractor can demonstrate that it is highly probable a significant revenue reversal won't occur when the uncertainty is resolved. In practice, "highly probable" means the contractor has documented evidence: the contract grants entitlement to the extra work, the owner has acknowledged the scope change in writing, prior dealings show the owner has honored similar claims, and there is no active dispute on record.
Controllers should document the basis for any unapproved CO revenue recognized in the period. Auditors scrutinize this heavily because revenue recognized on disputed or pending change orders is a leading source of construction company restatements. The safer position — and the one most advisors recommend — is to hold recognition until written approval is received unless entitlement is clearly supported by contract language and contemporaneous documentation.
What journal entries does a change order generate?
A CO generates two distinct journal entry moments. The first occurs when the CO is approved and added to contract value. In that scenario, the contractor debits Contracts Receivable (or Billing in Excess of Costs, depending on the billing position) and credits Contract Revenue for the approved CO amount. Account naming varies by firm and ERP, but the principle is consistent: the approved CO increases the revenue side of the job.
The second journal entry moment occurs when CO costs are incurred before owner approval. In a pending or disputed CO scenario, the contractor debits WIP or Construction in Progress (CIP is the balance sheet account that accumulates costs on uncompleted contracts) for the costs incurred. The revenue credit stays constrained — it does not flow to Contract Revenue until the variable consideration criteria under ASC 606 are satisfied. Controllers running multi-job portfolios need this two-stage entry logic built into their close process, not patched in after the fact via a spreadsheet adjustment.
What is the correct accounting path from a change order log to a WIP schedule update?
A change order must travel four steps — CO log, revised contract value, cost budget update, WIP recalculation — before it is correctly reflected in the WIP schedule and billing. Skipping or delaying any step produces a WIP schedule that is out of sync with the job's actual financial position. For teams building their process from scratch, the guide to building your WIP schedule in QuickBooks Online covers the foundational mechanics that this four-step chain feeds into.
Log the CO and assign status. Every CO, regardless of approval status, gets entered into the CO log with a status: pending, approved, or disputed. The log is the source of truth that reconciles the PM system to the accounting system. If a CO exists in the project management tool but not in the accounting log, the WIP will be wrong before the process even starts.
Add the approved CO to revised contract value in the accounting system. Revised contract value is the original contract price plus the net of all approved change orders to date. This update must happen in the accounting system, not just in a project management tool or spreadsheet. An approved CO that lives only in the PM software will never reach the WIP schedule.
Update the cost budget for the approved scope. The CO adds scope, and scope costs money. The cost budget for the job must increase by the estimated cost of the approved CO work. Failing to update the cost budget means the percentage-of-completion denominator stays understated, which inflates POC and recognized revenue before the work is done.
Recalculate the WIP schedule for affected jobs. With a new contract value and updated cost budget, the WIP schedule must be rerun before the period closes. The new calculation produces the correct percent-complete, billing right, and over/underbilling position. Any WIP schedule produced before step 3 is complete will overstate or understate the job's billing position.
What belongs in a change order log for accounting purposes?
The CO log is the single source of truth that connects PM activity to accounting entries. A mismatch between what the project manager sees and what the controller sees is the primary cause of WIP errors at close. The log must capture at minimum:
CO number (unique identifier linking to PM system)
Job or entity assignment
Date submitted and date approved
Scope description (brief but specific)
Dollar value of the CO
Status (pending, approved, disputed)
Impact on revised contract value
Impact on cost budget
Billing trigger (when CO invoice or AIA billing line is due)
What underbilling red flags should controllers catch every month?
Underbilling in construction almost always traces back to a CO that was approved in the field but never updated in the accounting system or WIP schedule. The monthly close review is the controller's best opportunity to catch these gaps before they become a cash flow problem — and before an auditor or surety finds them first. Understanding how over and underbilling work in construction is the prerequisite; this section focuses on the specific signals that point to a CO-driven underbilling problem.
Watch for these five red flags at every monthly close:
CO log shows approved COs not reflected in revised contract value. If the PM log and accounting system don't match on approved COs, the WIP is wrong. Corrective action: reconcile the CO log to the accounting system before running the WIP schedule.
WIP shows costs ahead of billing without an overbilling explanation. Costs running ahead of billing is the textbook underbilling pattern — but the cause is often an approved CO that was never invoiced. Corrective action: trace the billing position back to the CO log and issue the CO invoice.
Job GP% declining month-over-month without a scope explanation on record. GP fade without a documented scope change or cost overrun on file is a signal that CO costs are flowing without a corresponding contract value update. Corrective action: pull the CO log and compare to the original budget.
Billing at original contract value despite owner-approved extras. If billings are still referencing the original contract amount after COs have been approved, the contractor is leaving money on the table and the WIP will show escalating underbilling. Corrective action: update billing to reflect the revised contract value.
Cost budget unchanged from original estimate despite an active CO log. An unchanged cost budget in a job with active COs means the POC denominator is stale. Corrective action: update the cost budget to reflect all approved CO scope, then rerun the WIP.
Each of these flags requires a specific corrective action before the WIP is finalized. Carrying a known error into the period-end WIP creates a compounding problem at the next close. For teams also managing cash timing across multiple jobs, the connection between underbilling and working capital is explored in more depth in this guide to construction cash flow software.
Where does QuickBooks Online fall short for change order and WIP tracking?
QuickBooks Online has no native change order module, no revised contract value field, and no automated WIP schedule — which means CO tracking and WIP updates are manual, disconnected, and error-prone for growing GCs and specialty trades. One CFO described the problem plainly: "QuickBooks lacks the number of fields and dimensions, like to put a project ID, but everything coming in and tag it with a project ID." That dimensional gap is exactly where CO tracking breaks down. For teams using project management integrations, the Procore and QuickBooks integration covers the specific sync limitations that affect CO and WIP data flow.
The gap shows up in three specific ways: QBO has no CO status workflow to track pending versus approved COs, no automatic WIP recalculation when contract value changes, and no multi-entity consolidation of WIP across jobs or locations. Teams on QBO typically manage COs in a separate spreadsheet and manually update the WIP schedule each month — a process where a single mapping error forces rework across the entire workbook.
LiveFlow FP&A for QBO-based construction finance teams
LiveFlow FP&A connects directly to QuickBooks Online and gives controllers live, consolidated reporting across jobs and entities — including job cost and WIP views — without manual exports or spreadsheet reconciliation. For teams that aren't ready to migrate their ERP but need better CO and WIP visibility today, LiveFlow FP&A pulls live data from QBO into structured dashboards and reports that update automatically when the underlying QBO data changes.
LiveFlow FP&A is the right fit for construction finance teams that need consolidated job-level visibility across multiple QBO instances without rebuilding their reporting process from scratch every month. The platform sits on top of your existing QBO stack, so your team keeps working the way it already works while getting the consolidated view your leadership needs. See what's possible for construction finance teams on LiveFlow.
Flow ERP for multi-entity GCs and specialty trades ready to move off QuickBooks
Flow ERP is an AI-native ERP built specifically for multi-entity physical businesses — construction, healthcare, real estate, and food and beverage — where job costing, intercompany workflows, and multi-entity consolidation are core requirements, not workarounds. Unlike QuickBooks Online, which treats every entity as an isolated company file with no CO or WIP logic, Flow ERP houses all entities in a single workspace with native job costing and cost tagging, real-time consolidated reporting, and AI agents that handle routine accounting tasks throughout the period. Teams migrate from QuickBooks Online to Flow ERP in under 2 minutes, with books live in 11 days or less.
Change order accounting, revised contract value tracking, and WIP are built into the core of Flow ERP — not bolted on via a third-party connector that breaks when the PM tool updates its API. For multi-entity GCs managing multiple jobs across multiple legal entities, the ability to drill from a consolidated WIP view down to an individual transaction on a single job is the difference between a three-day close and a three-week one. Learn more about Flow ERP at liveflow.com/flow.
Change order accounting process checklist for GC and specialty trade controllers
A reliable change order accounting process requires eight recurring actions that must happen in sequence at the job level before each monthly close. This is an accounting and reporting action list, not a project management reminder — these steps belong on the controller's close checklist, not the PM's punch list.
Pull the CO log from PM software and compare to the accounting system. Identify any COs that appear in the PM tool but haven't been entered in the accounting system. Reconcile the two lists before running the WIP.
Confirm all approved COs are reflected in revised contract value. For every CO with an approved status, verify the accounting system's revised contract value has been updated. An approved CO that hasn't updated the contract value will produce an understated WIP billing right.
Update cost budgets for all approved CO scope additions. Revised contract value without a corresponding cost budget update will inflate the percentage-of-completion calculation and overstate recognized revenue. Both sides must move together.
Recalculate the WIP schedule for all affected jobs. Run the WIP schedule after steps 2 and 3 are complete — not before. A WIP run on stale contract values produces a close report that doesn't reflect actual job status.
Review percent-complete and billing position for each job with open COs. Flag any job where billing is running below the revised contract value billing right. These are candidates for immediate CO invoicing or AIA billing updates.
Flag unapproved COs that have incurred costs and assess the variable consideration constraint. For any pending or disputed CO where costs have been recorded, document whether the ASC 606 criteria for recognition are met. If not, hold the revenue side and disclose the contingent position.
Issue CO invoices or AIA billing updates where applicable. Approved COs that have been added to contract value but not yet invoiced represent cash that's sitting uncollected. Issue billing before the period closes.
Reconcile the CO log to AR aging for open CO billings. CO invoices that have been issued but not collected should appear in AR aging. Match the CO log to the aging to confirm all approved, billed COs are in the collection process. A downloadable construction P&L template can serve as a companion reporting resource for tracking job-level margin alongside this close process.
According to LiveFlow's Finance in the AI Era report (May 2026), 78% of finance leaders cite waiting on data from other systems as the number one cause of close delays. For construction controllers, that wait is almost always traceable to CO and WIP data that hasn't flowed from the PM system into the accounting system in time for close.
Get your change order accounting and WIP under control
Unapproved and undocumented change orders are the leading cause of margin fade and WIP inaccuracy in construction — and the fix is a system and process change, not a field reminder. When COs don't travel the full path from log to revised contract value to cost budget to WIP recalculation, the financial statements don't reflect the job's true position, and controllers are left defending numbers that don't hold up under audit or surety review.
If you're managing multiple jobs or entities and your current stack is QuickBooks Online plus spreadsheets, LiveFlow FP&A gives you live, consolidated CO and WIP visibility without replacing your ERP today. If you're ready to move to a purpose-built system, Flow ERP handles change order accounting, revised contract value, job costing, and multi-entity consolidation natively — with books live in 11 days or less after migration. Book a demo to see how it works for your specific structure.
Frequently asked questions
Quick answers to the questions contractors ask most about this topic.
How do you do a change order in construction accounting?
In construction accounting, a change order is processed by first logging the CO with a status in your CO log, then updating the revised contract value in your accounting system once the CO is approved, updating the cost budget to reflect the added scope, and recalculating the WIP schedule. Flow ERP handles this chain natively for multi-entity construction operators, with job costing and revised contract value tracking built into the core platform. In QuickBooks Online, all four steps are manual and disconnected, which is why CO-related WIP errors are so common on QBO-based teams.
What is an example of a change order in construction and how is it recorded?
A straightforward example: a general contractor's original contract is $1,000,000. The owner approves a CO to add HVAC upgrades for $50,000, bringing the revised contract value to $1,050,000. The accounting entry credits Contract Revenue for $50,000 and debits Contracts Receivable or Billing in Excess, depending on whether billing has already been issued. The cost budget for the job also increases by the estimated cost of the HVAC work, and the WIP schedule is rerun using the new $1,050,000 revised contract value and updated cost denominator.
What is the difference between an RFI and a change order in construction accounting?
An RFI (request for information) is a project management document used to clarify design intent or scope ambiguity — it does not change the contract and generates no accounting entry. A change order is a formal contract modification that adds, removes, or changes scope, price, or schedule, and it does require accounting entries: updating the revised contract value, adjusting the cost budget, and recalculating the WIP schedule. Treating an RFI as a CO substitute, or tracking COs only at the PM level without pushing updates to the accounting system, is a reliable path to WIP inaccuracy and underbilling.
Who pays for change orders in construction, and how does that affect revenue recognition?
The owner pays for approved change orders, and once the owner signs, the contractor recognizes the CO amount as additional contract revenue under the percentage-of-completion method. For disputed or pending COs where the owner hasn't approved, the contractor bears the cost but cannot recognize the revenue until the variable consideration constraint under ASC 606 is satisfied — meaning it must be highly probable that no significant revenue reversal will occur. In practice, this means controllers should hold unapproved CO revenue off the income statement unless written acknowledgment and contract entitlement language support recognition.
What happens to the WIP schedule when a change order hasn't been approved yet?
When a CO is pending or disputed, costs incurred under that CO flow to the job's WIP or CIP balance, but the revised contract value does not increase. The result is a widening cost-to-contract gap that the WIP schedule will show as underbilling — costs are running ahead of the billing right supported by the current approved contract value. Controllers should flag these positions explicitly in the WIP notes, document the pending CO and its expected approval timeline, and monitor cash timing carefully, since unbilled work tied to unapproved COs is a direct drag on working capital until the CO is approved and invoiced.
