A SaaS invoice marked uncollectible should normally contribute zero to expected four-week collections unless new payment evidence supports a different treatment. Keep the record visible for reconciliation and management review, but separate platform status, accounting treatment, open amount, and forecast inclusion. Uncollectible is not the same as paid, and it is not the same as void.
Read the status precisely
Stripe documents that an open invoice can be marked uncollectible when the business considers it unlikely to be paid. The status keeps the amount available for reporting as part of a bad-debt process. Stripe separately describes void invoices as zero-value and no longer payable. Its collection-method documentation also notes that automation settings can affect whether failed payments remain open or later transition to another status.
Those distinctions matter for small SaaS teams serving invoiced enterprise customers. A status may reflect a deliberate finance decision, an automated retry policy, or a manual workflow. It should not be converted into a cash assumption without reviewing why and when it changed.
Build a status-to-forecast control
For each affected invoice record:
- invoice identifier, customer, amount, and currency;
- collection method and latest payment-attempt state;
- current invoice status and status-change timestamp;
- actor or automation that changed the status;
- any credit note, revision, refund, or out-of-band payment;
- accounting review owner; and
- expected-cash amount and reason.
An open invoice with a failed payment may remain an active collection exception. An uncollectible invoice usually stays visible but has no current-period expected cash. A void invoice should not remain as a payable customer balance. If the accounting records and billing platform differ, retain the difference as a reconciliation item rather than overwriting one with the other.
The failed SaaS invoice payment guide helps with active retry cases. The bad-debt forecast boundary separates a write-off decision from a timing assumption.
Reopen timing only with new evidence
Do not move an uncollectible invoice back into week four merely because the customer remains active. New evidence might include a documented payment plan, a corrected billing issue, or a confirmed payment event. Record the event, amount, date, and owner before changing the forecast.
Also keep draft and open states separate. The draft invoice versus open receivable guide explains why a pre-finalization document is not yet the same source object as an open invoice.
This workflow is operational guidance, not accounting or legal advice. Follow the company's documented accounting policy and consult qualified advisers for status and write-off decisions.
AR Pulse analyzes an authorized QuickBooks receivables export and can surface status mismatches as actions while keeping unsupported cash out of the four-week range. It does not change billing-platform records or guarantee collections. Apply for AR Pulse when a bounded receivables review fits the workflow.