An approved consulting change order should not enter an accounts receivable forecast until the authorized billing workflow creates an issued, open customer invoice. The change order can support invoice-readiness planning, but unbilled scope is not open AR and should not be counted in the same four-week collections total.

Microsoft's project invoicing documentation distinguishes unbilled sales transactions, invoice proposals, and posted invoices. Microsoft's invoice-proposal workflow guidance describes approval before an invoice proposal can be posted. The exact workflow varies by business, but the boundary is useful: scope approval, billing approval, posting, and open receivables are different states.

Use a four-stage billing bridge

  1. **Changed scope documented:** the work, price, timing, and approval evidence are recorded under the company's process.
  2. **Billing inputs complete:** time, expenses, milestone evidence, purchase-order references, and customer details required by the process are available.
  3. **Invoice approved and posted:** the billing owner creates the customer invoice in the authorized source.
  4. **Issued and open:** the invoice appears in the dated receivables export with a supported open balance.

Only stage four belongs in an invoice-level collections forecast. Earlier stages can appear in a separate invoice-readiness schedule so management sees potential timing without mixing pipeline and receivables.

Keep three management views separate

  • **Delivery or scope view:** what work was requested, completed, or approved.
  • **Billing-readiness view:** what can be invoiced and what evidence or approval is missing.
  • **Open-AR view:** what has been issued, remains unpaid, and can receive an invoice-level collection assumption.

This separation prevents the same changed scope from appearing first as projected unbilled value and again as an open invoice without a clear handoff.

Preserve the handoff evidence

Record project, change-order reference, approved amount, approval date, billing owner, required supporting documents, invoice proposal or draft reference, posting date, issued invoice identifier, due date, open amount, and first forecast review date. If the approved amount changes before posting, retain both values and the reason.

Do not infer customer acceptance or collection timing from internal scope approval alone. A posted invoice still needs current evidence for an expected receipt week.

The project invoice-proposal guide covers proposal-versus-AR status. The consulting milestone readiness guide covers milestone evidence, and the weekly consulting AR review begins after invoices are open.

Decision rule

Keep approved change orders in a billing-readiness schedule until the authorized source shows an issued open invoice. Then move the supported invoice row into the AR forecast once, with its own evidence, owner, and expected-date review. Never count unbilled scope as collected cash or a promised outcome.

AR Pulse analyzes an authorized QuickBooks receivables export and does not change project systems or accounting records. Consulting finance owners can apply for AR Pulse after the open-invoice population is ready.