Canceling a Stripe Subscription: What Reaches QuickBooks

A customer emails to cancel. You open the subscription in Stripe, click Cancel subscription, and Stripe asks you three questions you may not have thought about: when should it end, should the customer get money back, and if so, how much. Every combination of answers is a different set of records in your books.

Some of them produce nothing at all. Some produce a refund. One produces a credit that looks like a refund in conversation but sits on the customer's account in Stripe until the next invoice, which for a customer who just canceled may never come. And one side effect of every cancellation catches bookkeepers who never touched the subscription: Stripe stops trying to collect the customer's open invoices.

Stop rebuilding cancellations by hand in QuickBooks. Acodei syncs Stripe invoices, payments, credit notes and refunds into QuickBooks Online as they happen. Start a free trial.

This post walks through each way a subscription ends, what Stripe does with the money in each case, and what you should expect to see in QuickBooks afterwards.

A cancellation is not itself an accounting event

Start with what a cancellation actually is. Stripe's cancellation guide says that by default "cancellation takes effect immediately and invoices are no longer generated for canceled subscriptions." After that, the subscription is largely frozen: you can still change its metadata and its cancellation_details, and nothing else.

So the cancellation is a change of state, not a movement of money. Stripe announces it with two events. customer.subscription.updated fires for any change to a subscription, including setting it to cancel at the end of the period. customer.subscription.deleted fires when the subscription actually ends, whether that is the moment you cancel it or the end of the period you scheduled.

Neither event is a sale, a refund or an invoice. That matters for anything that syncs Stripe to QuickBooks, because what reaches QuickBooks follows the money, not the subscription status. Acodei's Invoice Sync is built on invoice and charge events: it creates a QuickBooks invoice when a Stripe invoice is finalized, a payment when the invoice is paid, a credit memo when a credit note is created, and it voids or credits the invoice when Stripe voids it or marks it uncollectible. A subscription event is not on that list.

The practical result is simple to state. What shows up in QuickBooks after a cancellation is whatever invoices, refunds and credit notes the cancellation caused. If it caused none, QuickBooks sees nothing, and the only sign of the cancellation is that next month's invoice never arrives.

Four ways to end a subscription

Stripe offers four routes, and each one leaves a different trail.

How it ends	What Stripe creates	What reaches QuickBooks
Immediately, no refund (the default)	Nothing new. The last paid invoice stands.	Nothing new
Immediately, with a refund chosen in the Dashboard	A refund on the customer's payment	A refund record
Immediately, prorated through the API with a final invoice	A final invoice carrying a credit for unused time, held on the customer's credit balance	The final invoice, if it syncs. No refund unless you issue one.
At the end of the period	Nothing until the period ends, then no further invoices	Nothing new, unless pending prorations bill at the end
On a custom date	A prorated invoice for a shortened period, or prorations on the next one	That invoice, at its prorated amount

The rest of this post takes them one at a time.

Canceling immediately with no refund

This is what happens if you accept Stripe's defaults. The subscription ends now, no further invoices are generated, and nothing is credited or refunded. If the customer paid on the first of the month and you cancel on the twentieth, you keep the whole month's payment.

In QuickBooks nothing changes. The invoice for this month was finalized and paid before the cancellation, and with Invoice Sync on, Acodei recorded it then as a QuickBooks invoice with a payment applied to it. That pair stays exactly as it was.

The decision this leaves you with is about revenue rather than records. If you book subscription revenue when it is invoiced, you are done. If you defer it and recognize it over the service period, you have a schedule that now runs past the date service stopped. Whether the remainder is recognized at cancellation or left on the schedule is an accounting policy question for you and your accountant, but it is a question you have to answer, because no system will answer it for you. Our post on Stripe revenue recognition in QuickBooks covers the mechanics of deferring it in the first place.

The side effect: open invoices stop collecting

Here is the part of cancellation that surprises people who never touched the subscription.

Stripe's API reference for canceling a subscription says that "by default, upon subscription cancellation, Stripe stops automatic collection of all finalized invoices for the customer." The cancellation guide describes the same thing from the invoice side: every open and draft invoice for that subscription has its auto_advance set to false, which pauses automatic collection and stops the automatic reminder emails.

Stripe's reasoning is fair. A customer who has just canceled should not be charged unexpectedly a week later. But if that customer had an unpaid invoice when they canceled, say a renewal that failed and was waiting for its next retry, that invoice now just sits. Nobody retries it, and nobody reminds the customer.

If you sync Stripe invoices to QuickBooks, that invoice already exists in QuickBooks as an open receivable. It will stay open in your A/R aging until somebody decides what it is. There are three honest answers, and each one leaves a different record:

1. Collect it. Stripe notes that you can still attempt payment manually or resume automatic collection. If it is paid, Acodei records the payment against the QuickBooks invoice like any other.
2. Void it. If the customer never owed it, void the invoice in Stripe. Acodei's documented handling for a voided invoice is to void the QuickBooks invoice or create a credit memo against it.
3. Write it off. If the customer owed it and will not pay, mark it uncollectible in Stripe. Acodei handles that the same way as a void, and if the invoice is later paid after all, it reopens the invoice and processes the payment.

What you should not do is leave it. An open invoice for a canceled customer is the single most common reason a receivables report stops matching reality, and it is created by a click nobody in accounting made. For more on the void and write-off paths, see voided and uncollectible Stripe invoices in QuickBooks.

Prorated cancellation through the API: a credit, not a refund

The API route is where the most money goes missing in people's heads.

When you cancel a subscription partway through a paid period, Stripe lets you pass prorate to credit the customer for the unused time, and invoice_now to create a final invoice immediately. Stripe's proration documentation says credit prorations "are issued when customers downgrade their subscriptions or cancel subscription items before the end of their billing period."

The important sentence is in the cancellation guide: "If you owe the customer a credit after cancellation, you can add the credit to their credit balance to apply to future invoices. To refund your customer, issue refunds and then adjust their account balance back to zero."

Read that twice. A prorated cancellation does not send money back to anyone. It leaves you owing the customer a credit, and Stripe's answer is to hold it on the customer's invoice balance, which Stripe's customer balance documentation describes as an adjustment you "can apply to future invoices." A credit balance is a negative number on the customer in Stripe, meaning you owe them. For a customer who has just left, there is no future invoice to apply it to.

A worked example

A customer pays 90 USD on November 1 for a monthly plan that runs to November 30. On November 21 you cancel through the API with prorate and invoice_now. Ten of the thirty days are unused, so the credit proration is about 30 USD (Stripe calculates prorations down to the second by default, so the exact figure depends on the time of day).

Stripe's final invoice carries that negative 30 USD line. With nothing else on it, the invoice comes out below zero, and the 30 USD you owe sits as a credit on the customer's balance, waiting for a future invoice. Your Stripe balance has not moved. The customer's bank account has not moved. The customer, who asked for a prorated refund, has received neither.

If you then do what the guide says and refund 30 USD against the November 1 payment, two things are now true in Stripe: 30 USD has left your Stripe balance, and the customer still carries a 30 USD credit until you adjust it back to zero. Skip the adjustment and the credit sits there indefinitely. If the customer ever resubscribes, Stripe applies it to their first new invoice, so they get the same 30 USD twice.

What reaches QuickBooks

Two separate things happened, and they reach QuickBooks separately.

The refund is a charge refund like any other. By default, Acodei records a Stripe refund as a QuickBooks Refund Receipt against the customer, drawing from your Stripe holding account, with line items mirroring what was refunded. Acodei's documentation notes that refunds of invoice payments can instead reverse the original records, so if the November payment was an invoice payment, check which of the two you got.

The final invoice is the harder one, because its total is negative. QuickBooks has no sensible way to hold an invoice for less than zero, and how a negative Stripe invoice is represented on the QuickBooks side deserves its own explanation, which is in Stripe $0 and negative invoices in QuickBooks. Whatever form it takes, check one number after a prorated cancellation: the customer's balance in QuickBooks against their balance in Stripe. If you refunded the credit and zeroed it in Stripe, both should be zero. Acodei does not sync credit balances in both directions, so an adjustment you make in QuickBooks does not flow back to Stripe, and Stripe stays the record you correct.

There is one more trap in the same guide. If you do not prorate, Stripe says "all metered usage gets discarded and the customer won't receive credit for any potential prorations." On a usage-based plan, canceling without prorate throws away the usage you were about to bill. That is lost revenue, not a bookkeeping difference.

Canceling in the Dashboard with a refund

The Dashboard asks the refund question directly. After you choose when the subscription ends, Stripe offers three refund options: refund a prorated amount, refund the last payment in full, or no refund.

This is the cleaner path for a customer who wants their money back, because the result is a refund on their payment rather than a credit on their balance. From the books' point of view it is the same as any other refund on that payment, so in Acodei it arrives as the refund record described above, with the caveat about invoice payments.

Two cautions. First, a refund of the last payment in full returns money for days the customer did use, so it is a business decision, not a correction, and it is worth recording why. Second, Stripe keeps the cancellation reason on the subscription's cancellation_details, which stays editable after cancellation, but nothing carries it into an accounting system on its own. Write the reason on the refund memo if your team ever audits refunds.

Canceling at the end of the period

Setting cancel_at_period_end to true lets the customer finish the time they paid for. Stripe sends customer.subscription.updated when you set it, and customer.subscription.deleted when the period ends and the subscription actually cancels.

For the books, this is the quietest option. No proration is created, no refund is issued, and the paid invoice stands. There are two things to know.

It can be undone. Stripe says you can reactivate a subscription scheduled for cancellation "at any time up to the end of the period" by setting cancel_at_period_end back to false. A subscription can look canceled in a mid-month report and be active again on the 30th. If you forecast revenue from subscription status, forecast from the subscriptions that actually reached customer.subscription.deleted.

Pending prorations still bill. Stripe's API reference says that if the subscription is set to cancel at the end of the period, "any pending prorations are also left in place and collected at the end of the period." A customer who upgraded mid-month and then scheduled their cancellation still gets a final invoice for the upgrade. That invoice syncs to QuickBooks like any other, and it is easy to mistake for an error because it arrives after the customer has "already canceled."

Canceling on a custom date

The cancel_at parameter ends a subscription at a future timestamp, and Stripe shortens the billing period to match. This changes the amount of the invoice rather than adding a refund.

Stripe's own example is a clean one. A customer has a 120 USD per year subscription that renews on January 1, 2024, and sets it to cancel on July 1, 2024. On January 1, the final invoice subtotal is 60 USD, and the period end becomes July 1. If on February 15 they move the cancel date to October 1, Stripe creates prorations of 30 USD for the extra quarter.

Because Invoice Sync reproduces every line of the Stripe invoice, the QuickBooks invoice is 60 USD too. Your books show half a year's revenue for a half-year subscription, which is right. The thing to watch is the 30 USD. Unless the update passes proration_behavior of always_invoice, those prorations wait for the final invoice on October 1, so the extra quarter's revenue appears in QuickBooks months after the customer agreed to it.

Stripe also limits refunds on this route. "If you set a custom cancel date, you can't provide a refund," the guide says, and you can only prevent the credit proration when the cancel date falls within the current billing period.

The cancellations nobody clicked

Not every cancellation is a decision. Two kinds happen on their own, and both end with an invoice that needs a decision in QuickBooks.

Failed payments. Stripe cancels a subscription automatically after up to eight unsuccessful attempts to bill the customer, and you choose the number of attempts in your subscription settings. The renewal invoice that failed is usually still open when that happens. It is the open-invoice problem above, arriving without anybody having pressed Cancel.

Disputes. By default, a subscription keeps cycling when the customer disputes a charge, which can produce more disputed charges. Stripe lets you change that under Manage disputed payments: cancel immediately without prorating, or cancel at the end of the period, which gives you time to work through the dispute. Stripe notes this works only for card payments disputed for the full amount, and takes effect after about an hour.

In both cases, whatever Stripe does to the outstanding invoice is what QuickBooks should end up showing. If you void it, the QuickBooks invoice is voided or credited. If it is marked uncollectible, the same happens, and a later payment reopens it.

Leftovers: pending invoice items

A subscription can have invoice items waiting for its next invoice: a one-off charge you added, or prorations from a mid-cycle change. Cancellation does not necessarily clear them.

Stripe's API reference is precise about this. Pending invoice items are included on a final invoice if you generate one. "Otherwise, they remain pending and can be billed on another invoice for the customer." If the customer has a second active subscription, those items can turn up on its next invoice. Only when the subscription is canceled immediately with both invoice_now and prorate set to false does Stripe remove the pending prorations.

That is how a canceled subscription's charge ends up on a different subscription's invoice, which then syncs to QuickBooks with a line nobody expected. If you do not want the items billed, delete them. Stripe publishes a Workflows template, Delete pending invoice items after subscription cancellation, that does it without code when the subscription ends.

A short checklist after any cancellation

Run these in Stripe and QuickBooks the same day:

1. Open invoices. Look for any open or draft invoice for the customer. Collect it, void it or mark it uncollectible. Do not leave it in A/R.
2. Credit balance. If you prorated, check the customer's invoice balance in Stripe. If you refunded the credit, adjust the balance to zero.
3. Refund. If you refunded, confirm the refund record exists in QuickBooks against the right customer and the right holding account.
4. Pending items. Check for pending invoice items that will otherwise bill on another invoice.
5. Revenue schedule. If you defer subscription revenue, decide what happens to the unrecognized remainder.
6. Customer balance in both systems. The customer's balance in QuickBooks should match their balance in Stripe once everything above is done.

If a record arrived wrong, fix it in Stripe and resync it. Acodei's guidance is to resync from the Data Feed rather than edit the transaction in QuickBooks, so the two systems keep agreeing.

Frequently asked questions

Does canceling a Stripe subscription refund the customer?

Not by default. Stripe's default cancellation takes effect immediately with no proration and no refund. In the Dashboard you can choose a prorated refund or a full refund of the last payment. Through the API, prorating a cancellation creates a credit on the customer's balance, not a refund. To return the money you issue a refund and then adjust the balance back to zero.

What happens to unpaid invoices when a subscription is canceled?

Stripe stops automatic collection of the customer's finalized invoices by default, and pauses collection and reminders on that subscription's open and draft invoices. They are not voided. If those invoices were synced to QuickBooks they stay open in A/R until you collect, void or mark them uncollectible in Stripe.

Why does a canceled customer still have a credit in Stripe?

Because a prorated cancellation through the API credits the unused time to the customer's invoice balance, which Stripe applies to future invoices. A customer who has left has no future invoice, so the credit stays. If you refunded the amount, adjust the balance to zero, or the customer will receive the credit again if they resubscribe.

Will a canceled subscription create anything in QuickBooks?

Only what the cancellation causes. The cancellation itself is a subscription status change, and Acodei's Invoice Sync acts on invoice, payment, credit note and refund events, not subscription events. A refund, a final invoice or a voided invoice reaches QuickBooks. A plain cancellation with no refund and no final invoice produces nothing new.

Can a customer undo a cancellation?

Only a scheduled one. A subscription set to cancel at the end of the period can be reactivated at any time until the period ends by setting cancel_at_period_end back to false. Once a subscription is actually canceled it cannot be reactivated, and the customer needs a new subscription.

Where this leaves you

A cancellation is one click in Stripe and anywhere from zero to three records in your books, depending on how you answered three questions. The default produces none. A Dashboard refund produces a refund. A prorated API cancellation produces a credit that is not a refund until you make it one. And every cancellation quietly stops collection on the customer's open invoices, which is the record most likely to sit wrong in QuickBooks for months.

The neighbouring cases are covered in what customers change themselves through the Stripe customer portal, pausing payment collection on a subscription and Stripe customer balance and credits in QuickBooks. For the proration mechanics themselves, see the Stripe proration glossary entry.

Let the records follow the money. Acodei syncs the invoices, payments, credit notes and refunds every Stripe cancellation produces into QuickBooks Online, so your A/R reflects what actually happened. Start a free trial.