Usage records should not enter a small SaaS accounts receivable forecast until the billing process turns them into an issued, open invoice. Metered events, aggregated usage, upcoming invoice estimates, drafts, finalized invoices, and open receivables are different states. Only a supported open invoice belongs in the invoice-level collections population.
Stripe's usage-based billing overview describes meter events, aggregation, billing, and monitoring as parts of the usage-billing lifecycle. Stripe's invoice-state documentation distinguishes draft, open, paid, void, and uncollectible invoice states. These sources describe Stripe's workflow; AR Pulse does not claim a Stripe integration and uses them only to clarify the billing boundary.
Separate the usage-to-cash stages
- **Usage event recorded:** a product or service event enters the metering source.
- **Usage aggregated:** the billing system summarizes events under its configured rule.
- **Draft or upcoming invoice:** billing calculates a provisional amount that can still change.
- **Finalized and issued invoice:** the customer obligation is created under the approved billing process.
- **Open receivable:** the issued invoice remains unpaid in the accounting receivables source.
- **Observed receipt:** a supported payment is recorded and applied.
The collections forecast begins at stage five. Earlier stages belong in revenue or billing-readiness planning, not in the open-AR total.
Preserve corrections without double counting
Usage events can arrive late, be adjusted, or be aggregated asynchronously. A provisional billing amount can therefore differ from the final invoice. Keep the meter-period reference, aggregation cutoff, draft identifier, final invoice identifier, issued amount, accounting-posting status, and open balance connected.
If usage changes after finalization, follow the business's approved billing and accounting process. Do not edit the AR forecast to simulate a credit, replacement, or new invoice that has not appeared in the authorized source.
Maintain two forward views
A SaaS finance owner may need both:
- a **billing pipeline**, showing expected but unissued usage charges with their readiness and uncertainty; and
- an **AR collections forecast**, showing issued open invoices with evidence-based receipt timing.
Label and reconcile the handoff so the same amount cannot appear in both totals without an explicit elimination.
When a configured usage threshold can trigger an invoice before period end, use the billing-threshold boundary to separate measured usage, threshold invoices, and later unbilled activity.
The draft-versus-open invoice guide defines invoice states. The enterprise invoice checklist covers customer billing evidence, and the failed-payment guide handles a payment failure after issuance.
Decision rule
Do not forecast raw usage, an aggregation, or a draft invoice as open AR. Wait until the billing and accounting sources support an issued, open invoice. Then assign a collection week only from current evidence and keep later corrections traceable to a new source state.
AR Pulse analyzes an authorized QuickBooks receivables export to produce a ranked cash-action list and four-week collections forecast. It does not access billing systems, change books, contact customers, or promise an outcome. Small SaaS finance owners can apply for AR Pulse once issued invoices are in the export.