A professional-services firm should forecast near-term invoice collections separately from proposals, work in progress, billing backlog, and revenue schedules. Start with posted open customer invoices, reconcile their remaining balances, assign timing only from current evidence, and keep unbilled work in a connected upstream schedule.
Microsoft's Project Operations guidance distinguishes billing backlog from posted customer invoices. Its project invoicing documentation describes the proposal and posting workflow. Those boundaries matter because the service may be delivered and economically valuable before it becomes open accounts receivable.
Use a two-stage cash bridge
The first stage moves billable work toward an issued invoice. The second moves an open invoice toward observed cash.
| Stage | Typical evidence | Four-week treatment | | --- | --- | --- | | Work in progress or approved time | Project record | Upstream billing schedule only | | Billing backlog or invoice proposal | Draft or review object | Track readiness and blocker | | Posted open invoice | Accounting source and remaining balance | Eligible for invoice-level collections review | | Applied receipt | Payment record linked to invoice | Actual cash; reduce open balance once |
This bridge prevents double counting. When backlog becomes a posted invoice, link the records and remove the upstream amount from the near-term billing schedule before adding the invoice to open AR.
Add project evidence without replacing AR facts
For each open invoice, preserve customer, project, invoice number, open amount, invoice date, due date, and source status. Add the service period, milestone or billing rule supplied by the business, client acceptance, purchase-order or portal requirement, dispute status, latest payment evidence, owner, next action, expected week, and confidence label.
Project details can explain a blocker, but they do not change the source open balance by themselves. A completed milestone is not payment. A target billing date is not a collection date. A revenue-recognition schedule is not a cash forecast.
The billing-backlog boundary explains what belongs outside open AR. The billable-expense guide covers customer-reimbursable costs before and after invoicing.
Build the weekly range
Define four explicit date intervals after the snapshot cutoff. Assign an invoice amount to a week when recent, specific evidence supports it. Use conditional or unconfirmed states for missing approval, disputed scope, stale follow-up, unmatched payment, or an undated promise. Keep amounts outside the horizon visible rather than forcing them into Week 4.
For firms with milestone, retainer, reimbursable, or retainage models, use the relevant linked schedule to explain the invoice. Do not net unrelated future billing or outbound obligations against the verified customer receivable unless the authorized accounting source records that change.
Turn the forecast into an action list
Rank material exceptions by the next internal decision: resolve invoice readiness, supply buyer documentation, reconcile a payment, clarify a dispute, refresh a promise, or escalate a concentration exposure. Give each action an owner and review date. At the next snapshot, compare assumed timing with observed receipts and preserve the reason for every movement.
Decision rule
Keep unbilled work upstream, reconcile posted invoices into open AR, forecast cash from current invoice-level evidence, and measure every week against actual receipts. The result is a management range and action queue, not certain cash.
AR Pulse analyzes an authorized QuickBooks receivables export and produces a ranked cash-action list plus a four-week collections range. It does not change books, contact customers, or promise a payment outcome. Professional-services finance teams can apply for AR Pulse.