A pending invoice item should stay outside a small SaaS open-AR forecast until it is attached to an issued invoice that represents an open receivable. Keep pending items in a billing-readiness schedule so expected future billing is visible without being double counted as current AR.
Draw the object boundary
Stripe describes a pending invoice item as an item not attached to any invoice. A user can later invoice those items or include them in another billing flow. That makes the item an upstream billing input, not an issued customer invoice by itself.
Use two ledgers:
| Ledger | Included records | Management question | | --- | --- | --- | | Billing pipeline | Pending items, draft invoices, unresolved usage or adjustments | What still needs to become an invoice? | | Open AR | Issued open invoices with invoice IDs and balances | What customer cash is currently collectible? |
The small SaaS draft-invoice boundary applies the same rule to draft invoices. A draft and a pending item may be operationally important without being an open receivable.
Build a bridge when the invoice is issued
For every pending item, store the customer, source period, amount, currency, item ID, expected invoice path, approval state, owner, and next review date. When an invoice is finalized, link the pending item ID to the issued invoice ID and confirm which amount moved into open AR.
Do not leave the item total in a pipeline subtotal while also adding the resulting invoice to current AR. Mark the item as invoiced or otherwise resolved. If only part of the item is billed, preserve the residual and explain the split.
Usage-based billing adds another upstream source. The usage-charges versus open-receivables guide shows how to keep measured or estimated usage separate until billing creates the receivable.
Forecast each ledger differently
Open invoices can receive invoice-level collection assumptions when delivery, due date, buyer requirements, commitments, and payment evidence support them. Pending items should receive billing-readiness actions, not collection dates. Their timing depends on invoice creation, approval, finalization, and delivery before the customer payment workflow begins.
If an item is intentionally deferred, record the reason and next billing decision. If it is erroneous or duplicated, resolve it in the billing system through the authorized owner. AR Pulse does not create invoices or change the books.
Once the issued invoice exists, classify its collection method using the autocharge versus send-invoice comparison. Do not carry a pipeline estimate forward as a confirmed cash date.
Decision rule
Pending invoice items belong in a billing pipeline, not in current open AR. Move the supported amount once, retain the item-to-invoice lineage, and begin the collections forecast only from the issued open invoice. Small SaaS finance teams can apply for AR Pulse for an invoice-level action list and four-week range from an authorized receivables export.