From Change Order to Invoice in Construction

How connected contracts, subcontract commitments, and billing keep project changes visible

This is Part 3 of our construction project controls series. Part 1 covers the practices that build a reliable project record; Part 2 shows how that record supports a more useful ECAC forecast. Here, we follow a scope change through the contract and billing process.

A change in project scope can affect the budget, the customer contract, a subcontract, the forecast, and the next invoice. When each record is updated separately, it is easy for an approved change to reach the field before it reaches billing—or for costs to be committed before the team understands their effect on margin.

SIS Construct 365 Project Cost Management (PCM) works with Microsoft Dynamics 365 Finance to connect these financial steps and help teams see what has changed, what has been approved, and what remains to be billed.

Begin with a schedule of values that reflects the work

A construction contract’s schedule of values breaks the contract into billable work items. Each line gives project and finance teams a basis for tracking the scheduled value, work in place, billed amount, amount remaining, and retainage. A useful level of detail makes progress applications easier to prepare and easier to explain to the customer.

The billing method should fit the work. Percentage-complete billing can suit a work package whose progress is assessed as a whole. Quantity-based billing can be more useful where completed units can be measured. Either way, agreed methods and supporting field information help reduce disputes about what belongs in the current application.

Carry scope changes through approval and into the contract

When scope changes, the project team first needs to understand its expected revenue and cost effect. In Construct 365 PCM, a project change order can contain budget revisions for that analysis. Related project change orders can be grouped in a customer change order for approval. After approval, the change can be reflected in the construction contract schedule of values so it can enter the billing process.

Keep the timing of these steps visible. An internal estimate, a submitted customer change, and an approved contract adjustment are different things. Treating them separately helps teams discuss potential exposure without assuming that pending revenue can already be billed.

Update subcontract commitments for the same scope

A customer-approved change may also require additional subcontracted work. Subcontract change orders can revise the subcontract scope and schedule-of-values lines through an approval process. Keeping the commitment aligned with the revised work gives the forecast a more complete picture of expected cost, even when the vendor invoice has not arrived.

This is also a useful point to check vendor requirements. Compliance records and alerts can help teams identify documents that need attention before payment deadlines. The control is most valuable when someone is responsible for resolving exceptions, rather than merely receiving an alert.

Include retainage in the billing conversation

Retainage affects how much of an approved billing amount is collected now and how much remains for later release. Recording it with contract and schedule-of-values activity helps project and finance teams reconcile progress billing, receivables, and cash expectations. Teams should also make the conditions for release and the related approvals clear before automating that step.

See the effect in the forecast and project review

The commercial record should inform the project forecast. Compare approved contract changes and revised commitments with actual cost and estimated cost at completion (ECAC). If the expected final cost rises faster than approved customer value, the margin trend needs attention—even if the current month’s invoice looks healthy. Project financial views can help the team investigate those differences at a more useful level of detail.

A regular review can start with a few concrete questions: Which changes are awaiting customer approval? Which approved changes are not yet reflected in billing? Have subcontract commitments and the remaining cost estimate been updated for the same scope? These questions connect the contract process to the financial decisions discussed in Part 2 — From Budget to ECAC—Building a More Predictable Construction Forecast.

Automate routine steps while keeping exceptions visible

Automated posting or retainage release can reduce repetitive work when the rules, approvals, and exception handling are well defined. Review disputed quantities, missing documentation, unusual cost movement, and customer-specific billing requirements before relying on automation. The objective is a process that is both efficient and explainable.

Close the loop from project controls to cash

Across this series, the same principle runs from project setup through forecasting and billing: decisions are stronger when the budget, actual costs, commitments, approved changes, contract value, and invoices tell a consistent story. A connected record lets project and finance teams trace a change from its first estimate to its cost and billing effect—and address gaps before they become margin erosion or delayed cash.

Rick Crowley
Director, Global Solutions Engineering
SIS, LLC