Stop approved scope changes from disappearing before billing

An extra piece of work can disappear commercially long before it disappears operationally. The delivery team remembers the request and completes it. Finance sees the original contract. At month-end, nobody can confidently establish whether the additional work was included, separately authorized or simply provided as goodwill.

The answer is a change record that preserves the commercial decision. Revenue standards distinguish performance obligations and transaction price; invoicing alone does not determine earned revenue. IFRS 15 provides one authoritative framework for that distinction.^[1] The workflow below is an operational recommendation, with accounting treatment left to the business's applicable policies.

Keep three questions separate

Was the change requested? Was its price or calculation authorized? Has the agreed billing trigger occurred? A yes to the first question does not establish the other two. An email asking for another report may describe scope but say nothing about price. A signed amendment may authorize future work that cannot yet be invoiced.

Use statuses such as requested, priced, approved, delivered, billable, invoiced and closed. Attach the underlying evidence rather than relying solely on a status label. Record who approved the commercial terms and who confirmed delivery. When the same person holds both roles in a small business, retain evidence of each decision.

Preserve the original agreement

An illustrative architecture engagement includes two design revisions. The client requests a third. Before delivery, the firm records the requested change, its quoted price, authorized approval and intended billing event. The resulting invoice can reference that amendment instead of presenting an unexplained additional charge.

If the work was done before price approval, put it in an exception queue. Do not turn an internal estimate into a customer receivable simply because staff spent time on it. A commercial owner must decide whether to seek approval, absorb the work or resolve a disagreement. The dispute management article gives a structure for that conversation.

Reconcile changes to invoices in both directions

Each week, review approved changes whose billing conditions have been met. Compare them with invoice lines and their supporting references. Investigate eligible changes with no invoice, invoices with no authorization, and partially billed changes with no remaining schedule.

In an illustrative month, a firm has $15,000 in approved changes. Of that, $4,000 is already invoiced, $6,000 becomes billable only after future delivery and $5,000 is currently eligible but not invoiced. The immediate billing opportunity is $5,000, not $15,000. Whether any of it represents permanent loss depends on what would happen without the review.

This distinction matters to the automation business case. Calling all approved change value recovered revenue inflates the benefit and obscures the actual control failure.

Record deliberate concessions explicitly

If a manager waives a charge to preserve the relationship, retain the approved concession and its reason. Do not delete the change or silently reduce the original project value. A visible decision allows management to distinguish commercial generosity from missed administration.

Track the count and value of eligible changes awaiting billing, their age, and the number rejected for missing authorization. Review the most common source of missing evidence. If requests regularly arrive through informal messages, give the delivery team a short, usable way to capture and route them.

A workable change control should take less effort than reconstructing the same decision weeks later. Start with the billing readiness fields and add only the evidence needed for your actual contracting model.