Track a construction change order from the field to the books

A construction change order can affect customer pricing, vendor commitments, job forecasts, billing and invoices at different times. The bookkeeper needs one reference that follows the change through those handoffs without treating a field request as approval or an approved customer change as permission to pay a vendor.

Keep the status of the customer side and the cost side separate. A single label such as “approved” is incomplete when it does not say who approved what.

Start one register when the field raises the change

Assign a stable ID such as 417-CO-12 as soon as the project team identifies the potential change. Record the job, description, request date, request owner and source documents. Do not invent a value when pricing is still open.

The register should keep two tracks:

These tracks may move on different dates and for different amounts. Keep both under the same change ID so the office can explain the relationship without collapsing them into one number.

Use status gates with evidence

A practical register can use requested, pricing, submitted, approved, rejected and closed on the customer side. The cost side may use quote received, approval required, committed, invoice received, prepared, payment approved and paid.

Intuit’s current Enterprise Suite guidance describes saving change orders to a project, sending them for customer review and tracking their status and history. That is a product-specific workflow. Confirm the contractor’s software and authority rules before relying on the same fields.

Procore’s change-management guide distinguishes pending and approved changes in its budget and commitment workflows. The exact tiers and terminology vary by configuration, but the control lesson is useful: pending and approved amounts should not be silently combined.

Attach the evidence that advances each status. A text saying “looks good” may need the authorized manager’s confirmation under the company’s process before the register shows approved.

Worked example: Job 417, change order 12

Illustrative example. The field opens 417-CO-12 for added drainage work:

• The project manager’s initial customer price is $14,800.
• The customer approves a revised $12,600 scope on September 8.
• The subcontractor commitment change is approved internally at $8,100 on September 7.
• A $4,050 subcontractor invoice arrives on September 9 and references 417-CO-12.

The bookkeeper links the customer approval, vendor commitment and invoice to the same change ID. The register shows $12,600 as the approved customer change and $8,100 as the approved cost commitment. The $4,050 invoice moves through the normal AP preparation and review path against that commitment.

The bookkeeper does not overwrite the original $14,800 request, describe the remaining $4,050 commitment as a second invoice or release payment because the customer side is approved. Customer acceptance, vendor obligation, invoice preparation and payment authority are separate facts.

The amounts and dates are illustrative. Contract interpretation, revenue recognition, liability recognition and payment authority remain with the responsible people and advisers.

Define the weekly bookkeeping handoff

For every open change, the project manager should send:

1. The stable change ID and current job.
2. New scope, quote, approval or rejection evidence.
3. The effective date and authorized person for each status change.
4. Customer billing support, if the approved workflow calls for it.
5. Vendor commitment, invoice, receipt or credit documents.
6. The next action, owner and due date for unresolved items.

The bookkeeper returns a short exception list: missing IDs, conflicting amounts, invoice references with no supported commitment, approved changes not yet reflected in the agreed reports and closed changes with open documents.

Close the change deliberately

Before marking the register closed, confirm that the customer-side and cost-side records reach their intended final states. Check the approved amount against the current project report, tie invoices to the approved commitment or documented exception, and retain any billing and payment references required by the contractor’s process.

Closing the customer change does not automatically close every vendor item. Likewise, paying a vendor invoice does not prove the customer change was approved or billed.

Use the weekly project-manager packet to collect new evidence and the invoice approval map to preserve decision authority. A dedicated construction bookkeeper can keep the register current while project managers and authorized approvers retain the decisions only they can make.