One of the most frustrating forms of revenue delay happens after the hard part appears to be finished: the customer approved the change order, but the approved amount never reaches the next billing cycle.
The problem is usually not the approval itself. It is the handoff between approval and billing.
Treat approval as a trigger
An approved change order should immediately create a billing-related next action. The record should show the approved amount, approval date, billing owner and whether the amount has entered the next eligible billing process.
This is a core step in change-order tracking for subcontractors.
Keep submitted and approved amounts separate
The amount originally proposed may not be the amount ultimately approved. Store both values when they differ. Billing should follow the approved commercial amount, not an older proposal value that happens to remain in an email thread or spreadsheet.
Know the billing cutoff
Every company has some practical point at which information must be ready for the next billing cycle. It may be a formal monthly cutoff, a customer-specific deadline or an internal accounting schedule.
Record the relevant cutoff or next billing date when it matters. If approval occurs too late for the current cycle, schedule the item for the next eligible cycle rather than leaving it open-ended.
Use an “approved, not billed” exception queue
This is one of the simplest controls a subcontractor can create. Filter all change orders where the status is approved but the billing status is not yet billed.
Then sort by age, value or upcoming billing deadline. Ownership does not need to review the entire change log; it only needs to see approved revenue that has not yet crossed into invoicing.
Confirm the billing package is complete
Some customers require backup, signed documentation, schedule-of-values changes or other materials before an approved change can appear on an invoice. Track the missing requirement as the blocker rather than treating the item as generally “waiting.”
Requirements vary by customer and contract, so the governing agreement and customer process remain authoritative.
Do not close the change order at approval
Operationally, approval is only one stage in the financial path. A stronger status path is potential → priced → submitted → approved → billed → paid.
That lets the same record answer two different questions: has the customer accepted the change, and has the company converted that approval into billed revenue?
Carry the amount into receivables after billing
Once billed, the collection question moves into accounts-receivable control. The change-order record can preserve the approval history while the invoice follows its own age, blocker and next action.
A practical weekly control
- List every approved change that is not yet billed.
- Confirm the approved amount and approval date.
- Identify the next billing opportunity or cutoff.
- Confirm required backup is complete.
- Assign the billing owner and next action.
- Move the item to billed only when the invoice process actually includes it.
Approved revenue should not depend on somebody remembering to carry it forward.
EarnedShield is built to make these revenue handoffs visible so approved work can move from change control into billing and then into receivables without disappearing between systems. For the broader model, see Revenue Control for Commercial Subcontractors.