An issued annual SaaS invoice can be an open receivable even while much of the related revenue remains deferred. A cash forecast asks when the invoice will be paid. A revenue schedule asks when the service is delivered and revenue is recognized. Do not use one schedule as a substitute for the other.
Stripe's subscription revenue-recognition guide describes invoice line items and service periods as inputs to revenue timing. Stripe's reconciliation guidance explains that a finalized invoice can debit accounts receivable and credit deferred revenue while payment later moves cash against accounts receivable.
Define the two views
The open-invoice view should preserve invoice identifier, customer, issue date, due date, open amount, currency, payment status, credits, and collection evidence. This is the population used for a four-week collections forecast.
The revenue view should preserve service period, invoice line, recognition rule, deferred amount, and recognized amount under the company's approved accounting policy. This supports reporting and accounting, not expected receipt timing.
The same annual invoice can therefore be fully open in AR and partly deferred in revenue. That is not a mismatch by itself.
Use a three-date bridge
Preserve the invoice issue date, the customer payment or due date, and the service-period dates as separate facts. The issue and payment evidence govern the open receivable and short-term cash review. The service period belongs to the revenue-recognition schedule under the company's accounting policy.
For each annual invoice, link the AR row to the relevant revenue-schedule lines through stable invoice and line identifiers. Reconcile the invoice total, credits, applied payments, remaining open amount, deferred balance, and recognized amount without netting one schedule into the other. If the amounts do not bridge, flag the difference for accounting review rather than adjusting the cash forecast to make the totals agree.
Avoid three forecasting errors
First, do not spread expected cash across the service year merely because revenue is recognized over time. If the customer owes the annual invoice on one due date, collection timing needs its own evidence.
Second, do not treat a finalized invoice as observed cash. Payment state and receipt cutoff remain separate.
Third, do not reduce open AR because revenue remains deferred. A credit note, payment, void, or other supported source event changes the receivable; the revenue schedule alone does not prove that change.
The small SaaS draft-versus-open guide defines the issuance boundary. The usage-charges guide keeps metered inputs outside AR until invoiced. The failed-payment framework distinguishes an unsuccessful attempt from collected cash.
Build a bridge without netting
Use one row per open invoice for the collections forecast and a separate line-level revenue schedule. Connect them through invoice and line identifiers. Show payments, credits, or status changes as dated source events. Keep forecast evidence, owner, expected week, confidence label, and review trigger outside the accounting schedule.
Decision rule
Forecast annual SaaS invoice cash from invoice status and collection evidence. Account for revenue using the company's approved service-period policy. Reconcile the two views, but do not merge them.
AR Pulse analyzes an authorized QuickBooks receivables export into a ranked cash-action list and four-week collections forecast. It does not change revenue schedules or books. Small SaaS finance owners can apply for an AR Pulse review when annual open invoices need a clean cash-timing view.