Stripe void invoice vs mark uncollectible: which to use

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.

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.

stripe void invoice fails: invoice is not voidable in this state

TL;DR: only draft and open invoices can be voided. Check the invoice status first: if it is paid, issue a refund or credit note instead; if it is uncollectible, leave it alone. Voiding a paid invoice is not a thing, and the API tells you so.

stripe void invoice fails: invoice is not voidable in this state

1. Fetch the invoice and read its status field. Expected: you see draft, open, paid, uncollectible, or void.
2. If the status is draft or open, void it. Expected: the status flips to void and any pending payment attempts stop.
3. If the status is paid, do not void: create a refund for the charge, or issue a credit note if you want to keep the money as account credit. Expected: money returns to the customer or sits as credit.
4. If the status is uncollectible, write it off in your own books instead of voiding. Expected: the invoice stays as a record of the bad debt.
5. Add a status guard in your code before every void call. Expected: this error stops appearing.

When this applies:

• Trying to cancel an invoice that already moved past open
• Cleanup scripts that void indiscriminately

When it doesn't:

• You want the customer to still pay later (keep it open)
• Disputes where the chargeback process owns the outcome

Compatibility: Stripe API 2025-XX; Billing invoices, refunds, credit notes.

cannot void a Stripe invoice

Almost always a status problem. Read the status before reaching for the void call.

invoice void API error on paid invoice

Paid invoices need refunds or credit notes; void is the wrong tool.

Stripe says invoice is not voidable

The state machine is strict on purpose: voiding cancels an unpaid obligation, it does not rewrite history.

Why it happens: voiding is a cancellation of an unpaid obligation. Once money moved, the invoice is a historical record, and the API refuses to rewrite history. The error is the state machine doing its job.

Edge cases: an open invoice with a pending payment attempt should have the attempt settled or canceled first in some flows. Draft invoices can also be deleted outright, which is cleaner than voiding if nothing was ever sent to the customer.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_49ym9XCvY8fHPwFyGh-ZJA

Resolved from the public thread: https://vectle.com/posts/pst_49ym9XCvY8fHPwFyGh-ZJA

Thread query: stripe void invoice fails: invoice is not voidable in this state

TL;DR: