A QuickBooks delayed charge should not enter an accounts receivable forecast before it is added to an invoice. Intuit describes a delayed charge as a non-posting transaction used to hold an item for later billing. It can explain future invoice value, but it is not yet an issued receivable or customer payment obligation.
Keep three populations separate
Combining delayed charges with open invoices inflates the forecast population and hides the operational step that still has to happen. Use three views instead:
| Population | What exists | Forecast treatment | | --- | --- | --- | | Delayed charges | Work or a charge recorded for later billing | Keep in a billing-readiness queue, outside open AR. | | Issued invoices | A posted customer invoice with an open balance | Reconcile into the AR population, then assess timing evidence. | | Recorded receipts | A payment event applied or awaiting application | Reconcile separately so cash is not counted twice. |
This boundary is similar to the one in the recurring-template guide: a future billing instruction is not the same object as a posted invoice.
Build a delayed-charge handoff
For each delayed charge, preserve the customer, source date, service description, amount, responsible billing owner, invoice requirement, and intended billing date. The intended date is a work-queue field, not a collection date. Before moving the item into AR, confirm that it was added once to an issued invoice and that the invoice identifier and amount can be reconciled back to the source charge.
If several delayed charges are combined on one invoice, keep the many-to-one link. Do not leave the original delayed-charge amounts in the collections forecast after the invoice appears, or the same economic value will be represented twice.
The QuickBooks AR export checklist is the next control: it identifies the invoice-level fields needed after the billing step is complete.
Assign the right next action
A delayed charge usually creates an internal billing action, not a customer follow-up action. Record what prevents invoicing, who owns the conversion, and the next review date. Examples include missing approval, an incomplete service period, or a scheduled batch-billing date. These are workflow examples, not assumptions that every company uses the same process.
Once the invoice is issued, stop forecasting from the delayed charge and use the posted open balance. Then evaluate due date, delivery, dispute, promise-to-pay, and payment evidence before assigning a week. The invoice due-date guide explains why an invoice date or due date still does not prove a collection date.
Decision rule
Keep delayed charges visible as upstream billing backlog, exclude them from open AR, and transfer them into the forecast only through a reconciled issued invoice. AR Pulse works from an authorized QuickBooks receivables export, so its example output starts with posted invoice evidence rather than non-posting future charges.