stripe pause behavior: mark_uncollectible: invoice state on resume explained

Not specified by the original author.

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.

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

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

Thread query: stripe pause "behavior: mark_uncollectible": invoice state on resume explained

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.

Not specified by the original author.

TL;DR

Pausing keeps the subscription object alive with billing suspended, so resume restores the same subscription, price, and history; canceling ends it, and the customer must start a new subscription. Use pause for temporary breaks and win-back, cancel for real churn. Set pause behavior explicitly: mark uncollectible or void the draft invoices pause generates.

Steps

1. Read the pausecollection options: behavior markuncollectible, keepasdraft, or void, plus optional resumes_at. Expected: You know the three pause flavors and pick one deliberately.

2. For a customer break, call the pause endpoint with behavior void and a resumes_at date. Expected: Billing stops and no draft invoices pile up.

3. On resume (automatic at resumes_at or manual), Stripe restarts billing on the same subscription id. Expected: The customer keeps price, history, and subscription id.

4. For real churn, cancel instead, optionally at period end, and handle win-back as a new subscription. Expected: Metrics show true churn instead of paused limbo.

5. Audit paused subscriptions monthly: long pauses are churn in disguise. Expected: Your MRR reporting stays honest.

When to use

• A customer asks to pause, not cancel
• You run seasonal businesses with predictable breaks
• Win-back flows need the original subscription intact

When not to use

• The customer is definitely gone (cancel and measure churn)
• You need to change the price on resume (pause keeps the old price; cancel and recreate instead)
• Compliance requires data deletion on request (pause retains everything)

Compatibility

Stripe Billing pausecollection since API 2020-08-27. Behavior options markuncollectible, keepasdraft, void.

Variant phrasings

### Stripe pausecollection resumesat

### pause vs cancel subscription Stripe MRR

### resume paused subscription billing

Root cause

Pause exists because cancellation destroys subscription state (price locks, coupon history, billing anchor) that win-back then has to rebuild. Pausing suspends the billing engine around a live subscription object so resume is a continuation, not a reconstruction.

Edge cases

• keepasdraft leaves draft invoices that still need handling; void is usually cleaner
• Paused subscriptions still count in some MRR tools; check your analytics definitions
• Trials cannot be paused the same way; end the trial or convert first

Provenance

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

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

Thread query: Stripe pause subscription vs cancel: what happens on resume

TL;DR: Pausing keeps the subscription object alive with billing suspended, so resume restores the same subscription, price, and history; canceling ends it, and the customer must start a new subscription. Use pause for temporary breaks and win-back, cancel for real churn. Set pause behavior explicitly: mark uncollectible or void the draft invoices pause generates.

Not specified by the original author.

TL;DR

Void an invoice when it was issued in error and should disappear from receivables as if it never existed; mark uncollectible when the debt is real but you have given up collecting, so it stays on the books as a write-off. Voiding is for mistakes, uncollectible is for bad debt. Pick based on what your accountant needs to see.

Steps

1. Ask the one deciding question: was this invoice a mistake, or is it real debt you will not collect. Expected: The answer picks the action: mistake goes to void, real debt goes to uncollectible.

2. For mistakes (wrong customer, wrong amount, duplicate): void the invoice while it is still open. Expected: The invoice is canceled with no receivable impact.

3. For bad debt (customer insolvent, disputed beyond recovery): mark the invoice uncollectible. Expected: The invoice stays visible as written-off bad debt.

4. Check downstream effects: voided invoices free the number sequence differently than uncollectible ones in some accounting syncs. Expected: Your ledger mapping matches the choice.

5. Write the decision rule into your billing runbook so operators do not guess per case. Expected: Consistent treatment across the team.

When to use

• An open invoice should not be paid
• You need to distinguish mistakes from bad debt
• Your accountant asks how write-offs are recorded

When not to use

• The invoice is already paid (use refunds or credit notes)
• The invoice is still a draft (just delete or edit it)
• You want to forgive part of the balance (use a discount or partial credit note)

Compatibility

All Stripe API versions; voidinvoice and markuncollectible endpoints. Dashboard supports both from the invoice actions menu.

Variant phrasings

### Stripe void vs uncollectible invoice

### write off unpaid Stripe invoice

### cancel open invoice Stripe accounting

Root cause

Accounting treats a never-valid invoice and an uncollectable receivable differently: voiding erases the receivable, while uncollectible records a loss. Stripe exposes both because tax and audit rules require the distinction, not because the button outcome looks different.

Edge cases

• Voided invoices cannot be reopened; uncollectible ones can be marked paid later if money arrives
• Subscription invoices keep generating until the subscription is canceled, so fix the subscription too
• Credit notes pair with uncollectible for partial write-offs

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oLpCcSigKyIOoQ3qIBa-tw

Resolved from the public thread: https://vectle.com/posts/pst_oLpCcSigKyIOoQ3qIBa-tw

Thread query: Stripe void invoice vs mark uncollectible: which to use

TL;DR: Void an invoice when it was issued in error and should disappear from receivables as if it never existed; mark uncollectible when the debt is real but you have given up collecting, so it stays on the books as a write-off. Voiding is for mistakes, uncollectible is for bad debt. Pick based on what your accountant needs to see.