## TL;DR
mark_uncollectible marks the open invoices uncollectible and freezes the subscription; nothing is billed during the pause. On resume, Stripe creates a fresh invoice for the resumed period. Reporting sees uncollectible invoices, not voids, so revenue write-offs must account for that.

```text
pause behavior mark_uncollectible invoice state on resume
```

## Use this when
- You paused a subscription with mark_uncollectible and the invoice states look wrong.
- Finance is asking why pause shows as uncollectible revenue.
- You are choosing a pause behavior and need to know the invoice semantics.

## Not for this skill when
- You paused with void behavior. Voids zero the invoice instead of marking uncollectible.
- The subscription was canceled, not paused. Cancellation has different invoice handling.

## Steps
1. ('Pause the subscription with behavior mark_uncollectible. Verify: open invoices move to uncollectible, status stays paused.', 'Record the pause in your ledger as a write-off category matching uncollectible, not a refund. Verify: finance agrees with the classification.', 'While paused, confirm no new invoices generate. Verify: the billing cycle is frozen.', 'On resume, Stripe creates a new invoice for the resumed billing. Verify: the customer is charged correctly for the new period.', 'Reconcile: uncollectible invoices from the pause stay on the books; do not re-bill them on resume.')

## Variant phrasings
### stripe pause subscription invoice uncollectible
Short search.

### mark_uncollectible vs void pause stripe
Behavior-comparison search.

### stripe subscription pause resume invoice
Lifecycle search.


Compatibility: Stripe Billing subscription pause collection API, all client versions.

## Why it happens
Pause behaviors differ in what they declare about unpaid invoices. mark_uncollectible says "we give up collecting this," which matches a pause where the customer keeps what they had but you stop trying to charge. void says "this invoice should never have existed." Stripe chose uncollectible for this behavior because a pause is a business decision to stop collecting, not a correction of a billing error.

## Edge cases / pitfalls
- Uncollectible invoices still count in receivables aging. Coordinate with finance before mass pauses.
- Resuming does not re-collect the paused-period invoices. If you intended to collect, do not use this behavior.
- mark_uncollectible is irreversible per invoice. A later resume cannot un-mark them.
- Customer portals show uncollectible invoices; word the pause confirmation email so customers do not panic.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_EOcfWslcatqEI0lQ3Kl1pw