Completed field work does not enter an accounts receivable forecast until it becomes an issued, open invoice. Use a readiness gate that connects the work order to billing evidence, confirms invoice creation, and reconciles the remaining balance before assigning a collection week.

Microsoft's field-service invoicing guidance describes generating invoices from completed work orders and the associated billing records. Its work-order and booking-status documentation separates the overall work-order state from technician booking progress.

Operations evidence

Before billing handoff, confirm:

  • work-order identifier and customer;
  • current system and booking status;
  • completed service lines, products, time, or expenses included for billing;
  • customer acceptance or internal approval required by the contract;
  • exceptions, credits, warranty items, or nonbillable work;
  • named owner for any missing evidence.

A completed booking can be useful evidence, but it does not by itself create an open receivable. Keep operational work in a billing-readiness queue until the invoice step is complete.

Billing evidence

Confirm that the invoice was created from the intended work order or agreement, reviewed, posted, and delivered through the business's normal process. Retain the invoice number, invoice and due dates, original amount, taxes or adjustments already recorded, and source work-order link.

If an agreement invoice and a work-order invoice could cover related value, use the agreement-versus-work-order guide to prevent overlap. For staged jobs, the progress-invoice guide separates the billed portion from remaining scope.

Receivables evidence

Run a dated AR export and verify that the issued invoice appears with the correct customer and remaining balance. Reconcile payments, credits, voids, or replacements before adding it to expected collections. Forecast no more than the open balance in the source.

Assign a collection week from invoice-specific evidence: due date, delivery status, approved payment schedule, current customer commitment, or another documented timing input. Work completion can support billing readiness but should not substitute for payment evidence.

Exception routing

Keep exceptions explicit: work complete but not approved; approved but not invoiced; invoiced but not delivered; invoice missing from AR; balance mismatch; or payment evidence stale. Each exception needs an owner and next review date. Do not manufacture a collection date to fill an empty forecast cell.

The unbilled-sales guide provides a parallel boundary for other service businesses.

If the work order carries a price or cost ceiling, use the not-to-exceed amount comparison. It keeps that operational limit separate from used work, the posted invoice, and expected customer cash.

If the job is covered by a warranty or entitlement, use the warranty-work-order boundary before treating the work-order value as a customer receivable. Coverage, customer pricing, invoice issuance, and the open balance remain separate checkpoints.

Decision rule

Move value through four gates: completed work, billing approval, issued invoice, and reconciled open balance. Only the last state belongs in an invoice-level collections forecast. AR Pulse works from an authorized QuickBooks receivables export and does not contact customers or change books. Field-service finance teams can apply for AR Pulse for a ranked action list and four-week forecast.