A recurring invoice template is not yet an open receivable. Keep it in the billing schedule until QuickBooks creates the actual invoice; only then confirm that the invoice is issued, open, dated, and present in the receivables export before assigning a collection week.

Intuit's recurring-transaction guidance distinguishes scheduled, reminder, and unscheduled templates. It also notes that recurring invoice transactions are saved as drafts for review and finalization. Intuit's transaction comparison separates invoices, which record amounts a customer owes, from sales receipts used when payment happens at the sale.

Use three separate populations

Maintain a clean boundary among:

  • **Template schedule:** the instruction to create a future transaction.
  • **Draft or review queue:** a generated billing record that is not yet confirmed as an issued receivable.
  • **Open AR:** an issued invoice with a customer, invoice date, due date, and remaining balance in the dated export.

The template can inform a billing outlook, but adding its expected amount to an AR forecast before an invoice exists would mix future billing with current receivables. That can duplicate expected cash when the generated invoice later enters the export.

A QuickBooks delayed charge follows the same non-posting boundary but begins with a recorded billable item rather than a recurring schedule.

Review the generated invoice

When the recurring date arrives, check the generated record rather than assuming the template ran correctly. Confirm the customer, amount, service period, invoice and due dates, delivery status, and remaining balance. If the invoice is still a draft, needs approval, or was not sent, keep it in a billing exception list.

If the template produced a recurring sales receipt instead, do not place that paid-at-sale transaction in the open-invoice population. The invoice-versus-sales-receipt guide explains that boundary. For draft status controls, use the draft-invoice guide.

Forecast only the supported open balance

Once the invoice appears in the dated AR export, use its remaining balance as the maximum forecastable amount. Assign timing from evidence such as the contractual due date, delivery confirmation, a current promise to pay, or a documented payment plan. Do not copy a template's future cadence into the collection forecast as though it were observed customer behavior.

Record the template identifier as lineage when useful, but preserve the issued invoice number as the forecast key. If a template is paused, changed, duplicated, or converted to another payment workflow, flag the next generated record for review.

Decision rule

Templates predict billing activity; issued open invoices establish accounts receivable. Keep those populations separate, reconcile each generated invoice, and forecast only a traceable remaining balance. The QuickBooks export-column checklist shows the fields needed for a review-ready population. Finance teams can also view the AR Pulse example to see the intended invoice-level evidence boundary.