A staffing finance team should connect weekly payroll obligations to customer invoice timing in one cash view, but it should not use an invoice due date as proof that payroll cash will arrive. Payroll and collections are separate event streams with different evidence, owners, and failure modes.
Build two dated schedules
Start with a payroll schedule based on the business's approved time, pay dates, and observed cash obligations. Then build a collections schedule from issued open invoices. QuickBooks documents that timesheets can be approved, unapproved, or rejected before they feed later workflows. Microsoft describes cash-flow forecasting as incorporating forecasted transactions and source-system information. Neither source turns approved time into customer cash.
| Schedule | Minimum evidence | Key question | | --- | --- | --- | | Payroll | Approved time, pay date, expected cash outflow | When must the business fund payroll? | | Billing | Invoice-readiness status and issued invoice ID | Has approved work become posted AR? | | Collections | Open balance plus customer timing evidence | Which receipt week is supportable? | | Liquidity bridge | Dated inflows and outflows | Where is the timing gap? |
The staffing timesheet readiness guide covers the handoff from approved time to an invoice. The staffing AR forecast guide covers the customer-receipt side.
Do not net the schedules invisibly
Preserve gross expected receipts and gross payroll outflows before calculating a net position. If an invoice slips, update the collections schedule from new evidence while leaving the payroll date unchanged unless its own source changes. This exposes the actual timing risk instead of burying it in a single net number.
For each material invoice, record the customer, invoice ID, open balance, service period, due date, expected collection week, evidence, confidence label, owner, and review date. For payroll, use only authorized internal totals and dates; do not place employee-level data in SEO content or a public artifact.
Use explicit gap scenarios
A practical review can show a base view plus clearly labeled alternatives: collection occurs in the supported week, collection moves later, or the invoice remains unassigned because evidence is weak. Do not invent a standard customer delay or present a scenario as a prediction. Cap expected collections at the current open balance and update observed receipts only once.
The confidence-label guide helps distinguish stronger and weaker invoice evidence without pretending to know a probability.
Decision rule
Keep payroll and invoice collections as separate dated schedules, reconcile each to its source, and use the combined view to identify funding gaps and collection priorities. AR Pulse supplies a ranked receivables action list and four-week collections forecast from an authorized QuickBooks export; it does not forecast payroll or guarantee customer payment. Review the example output to see the invoice-level evidence format.