A completed consulting milestone is ready to enter an accounts receivable cash forecast only after the billing trigger is supported, required internal approval is complete, and a customer invoice has been issued and remains open. Completed work, a draft invoice, and an approved invoice are different states. Forecasting all three as open AR can count cash before a receivable exists.

Microsoft's project-invoicing documentation describes invoice proposals as preliminary invoices that are reviewed before a customer invoice is posted. Its project-contract documentation explains that milestone billing depends on the milestone being reached, and its proposal-workflow guidance describes formal approval before posting. The useful forecasting boundary is therefore invoice issuance, not project-completion language alone.

Keep four milestone populations separate

  • **Work in progress:** the milestone has not met the documented billing trigger.
  • **Trigger met but invoice not approved:** evidence supports completion but the billing workflow is still open.
  • **Invoice approved or proposed but not posted:** the amount is close to billing but is not yet an issued open receivable.
  • **Issued and open invoice:** the row can enter the AR population and receive a collection-timing review.

These states make the operating handoff visible without turning upstream project value into forecast cash.

Build the readiness handoff

For each milestone, preserve:

  1. contract or statement-of-work reference;
  2. milestone name and billing amount;
  3. completion evidence and completion date;
  4. customer acceptance or approval evidence when required;
  5. internal invoice-proposal owner and status;
  6. posted invoice number, invoice date, due date, and open balance;
  7. current exception, next action, owner, and review date.

If the scope changed, a deliverable was rejected, or approval evidence is missing, keep the item upstream. Do not invent an expected collection week merely because the project team considers the work complete.

Move only issued open invoices into weekly timing

Once an invoice is issued and open, review the evidence for Week 1 through Week 4. The contractual due date remains a source fact; the expected collection week is a separate assumption. A newly issued invoice can still be conditional if a portal, purchase-order, entity, or acceptance issue remains.

The agency approval-blocker guide covers client-approval handoffs, while the billable-expense boundary separates another form of unbilled project work from open receivables. This consulting workflow adds a milestone-specific proposal and posting control.

Review the upstream queue separately

Use a billing-readiness queue for milestones that are not yet invoices. It can inform management about possible future invoicing, but it should not inflate current open AR or the four-week expected-receipt total. When the invoice is posted, add it from a new dated accounting export rather than copying the proposal row into the forecast.

When scope changes after the original milestone was defined, route it through a separate approval and posting bridge. The consulting change-order boundary keeps approved changed scope upstream until an issued open invoice appears, preventing the original milestone and revised billing from entering the forecast twice.

AR Pulse analyzes an authorized QuickBooks receivables export and therefore begins with issued open invoices. It does not change project records or accounting books. Consulting finance owners with a clean export can apply for AR Pulse.