Change-order billing automation connects approved scope with the billing packet and subsequent collection. Its job is to expose missing steps, not to assume that every project approval immediately creates a collectible invoice.
Use the control model below alongside your contract requirements and accounting policies. Approval, payment entitlement, lien rights, and revenue recognition require separate review; a workflow label does not decide them.
Keep five states separate
| State | Evidence to retain | Next owner |
|---|---|---|
| Proposed or disputed change | Scope, amount, correspondence, and outstanding approval | Project manager |
| Approved but not billing-ready | Approval plus missing schedule-of-values updates or backup | Project accountant |
| Ready for the next application | Approved billing amount, required documents, and cutoff date | Billing owner |
| Submitted or returned | Submission receipt, rejection reason, and correction history | Billing owner and project manager |
| Accepted and awaiting payment | Accepted amount, payment terms, deductions, and receipts | AR owner |
Keep approved value, previously billed value, current billing, retainage, and remaining value in separate fields. A status change should not silently overwrite those amounts.
A reconciliation example
Illustrative example, not a customer result: a $100,000 change order has $40,000 already billed. The current application includes another $25,000. The remaining unbilled amount is $35,000 before any separate treatment of retainage, tax, or disputed adjustments.
If the billing team imports the full $100,000 again, a duplicate-billing control should flag the difference. If the $25,000 misses the cutoff, that is a billing-readiness issue—not evidence that the customer has paid late.
The minimum case record
Retain the project and contract identifiers, change-order identifier, latest approved revision, approved amount, approval evidence, schedule-of-values line, prior billings, current application, supporting documents, submission receipt, and next owner.
Link to evidence rather than copying amounts into disconnected spreadsheets. Keep the earlier revision available when scope or value changes.
The billing-cutoff checklist
- Reconcile the approved change-order register with the billing schedule.
- Identify approved items absent from the current application.
- Check cumulative billing against approved values and prior applications.
- Confirm required backup and the customer’s submission requirements.
- Record submission or rejection evidence.
- Assign each returned item a correction owner and deadline.
- Match subsequent cash and deductions to the accepted billing.
A reviewer should be able to explain every difference between the project team’s approved register and the finance team’s billings.
Applying this around construction ERPs
The same control questions apply around CMiC, Viewpoint Vista, Acumatica, Sage 300 CRE, and FOUNDATION, but the records and supported integrations differ. Do not treat a product name as proof that an external tool can update its billing workflow.
Before implementation, have your ERP administrator demonstrate:
- The authoritative project, contract, change-order, and billing records.
- How revisions and prior applications are represented.
- Where approval documents and returned packets are retained.
- How an integration distinguishes a new write from a retry.
- Which role can update billing and which role can release a hold.
This is an ERP evaluation checklist, not a configuration guide or a claim of ProcIndex connectivity to those systems.
Metrics that reveal the bottleneck
Track approval-to-billing time, approved amounts missing the next cutoff, returned application rate, correction age, and unapplied receipts. Report reasons and owners alongside totals.
Keep unbilled scope separate from invoiced receivables when interpreting your AR measures. Do not improve a reported DSO number merely by changing classifications; preserve the approved accounting basis and explain changes.
Pilot one project before expanding
Run the new register and checklist alongside the existing process for a complete billing cycle. Review the differences, correct source ownership, and test repeated imports. Expand only when the project and finance teams can reconcile the same evidence.
For the wider process, see the AR automation guide. To discuss ProcIndex’s current supported workflows and ERP connections, book a workflow review.