A staffing VMS status supports a collection assumption only when it identifies an actual invoice and a sufficiently advanced buyer-side state. Approved time is evidence that work cleared one operational gate; it is not automatically an open receivable. A submitted invoice is stronger, an approved invoice is stronger still, and paid status should be reconciled to recorded cash rather than forecast again.
Do not collapse time and invoice workflows
SAP Fieldglass documents that timesheets can be pending approval or invoiced and that an approved timesheet may be ready for invoice creation. Depending on configuration, an invoice can be created automatically or manually. Its SOW invoice documentation separately lists draft, pending approval, approved, consolidated, rejected, and paid states.
The source objects therefore answer different questions. A timesheet can support billing readiness without proving an invoice exists. An invoice can exist without buyer approval. Approval can occur before payment processing. Each handoff can change the right owner and forecast confidence.
Use a status matrix
Apply these default boundaries, then adapt them to the customer's documented VMS setup:
- Draft or submitted time: operational backlog; no invoice cash assumption.
- Approved time not yet invoiced: billing-ready evidence; track invoice creation as the next action.
- Invoice draft: not yet a buyer-submitted receivable for forecast purposes.
- Invoice pending approval: preserve the amount and approval owner; use timing only if current workflow evidence supports it.
- Invoice approved: candidate for a collection week based on payment terms and buyer evidence.
- Pending consolidation or consolidated: confirm whether consolidation changes the payable identifier or timing before inclusion.
- Rejected or approval paused: exception; withhold ordinary timing and assign remediation.
- Paid: remove from expected collections after reconciliation to the accounting and bank records.
The staffing timesheet readiness guide covers the first handoff. The self-billing and ERS boundary applies when the buyer rather than the supplier creates the invoice.
Preserve identifiers through the handoff
Record timesheet ID, worker or assignment reference, invoice ID, buyer status, amount, status timestamp, payment terms, owner, and next action. If a time revision creates a related adjustment, link it to the invoice rather than adding an unexplained negative or duplicate amount.
A portal status should be checked against the accounting export. The supplier-portal acceptance guide explains why portal acceptance and book status can diverge. Keep the mismatch visible until it is reconciled.
When the portal creates a credit or debit memo against the invoice, use the staffing adjustment bridge to preserve the original amount and the adjustment separately.
When several source invoices or approved time sheets roll into one buyer document, use the consolidated-invoice reconciliation. It keeps the buyer-facing invoice as the cash control while preserving the child records that explain its amount.
This matrix does not promise payment at any particular stage. It creates a repeatable evidence boundary for deciding when staffing revenue has become a forecastable receivable.
AR Pulse analyzes an authorized QuickBooks receivables export and can rank VMS-related exceptions alongside invoice-level cash timing. It does not access the VMS, contact customers, or promise a collection outcome. Apply for AR Pulse if the export contains enough evidence for a focused review.