Stripe Tax for Existing Subscriptions and QuickBooks
Turning on Stripe Tax doesn't tax subscriptions you already have. How the migration tool works, when tax starts, and what changes in QuickBooks.
You turn on Stripe Tax, add your registrations, and the first new subscription that afternoon charges tax. The 640 subscriptions you already had keep renewing exactly as before: no tax line, same total, same QuickBooks invoice. Nothing is broken. Stripe Tax simply doesn't touch existing subscriptions until you tell it to.
Getting Stripe Tax onto existing subscriptions is its own project. Stripe gives you a Dashboard migration tool for it, a set of eligibility rules that decide which subscriptions the tool can move, a fallback called an inferred location for customers with no address, and one sentence that shapes the whole timeline: "We don't prorate the tax changes. The updates take effect at the start of the next billing cycle."
The first taxed renewals, recorded the way you file. Acodei's Invoice Sync turns each finalized Stripe invoice into a QuickBooks invoice, with tax attached according to the approach you pick: one tax product on a liability account, or each Stripe tax rate mapped to a QuickBooks tax code. Start a free trial.
This guide covers what the migration tool does and doesn't do, which subscriptions you have to move by hand, how inferred locations work, why an annual subscriber might not see tax for eleven months, what the price you already charge turns into once tax applies, and what changes in QuickBooks on the first taxed renewal.
Why turning on Stripe Tax skips your existing subscriptions
Stripe Tax calculates tax on a subscription only when that subscription has automatic tax enabled (automatic_tax.enabled). A subscription created before you activated Stripe Tax doesn't have it, and activating Stripe Tax on your account doesn't switch it on for subscriptions that already exist.
Stripe's guide to updating existing subscriptions puts it plainly: "When you integrate with Stripe Tax, you need to update existing subscriptions to make sure that tax is automatically calculated going forward."
So your account ends up with two populations:
- New subscriptions created with automatic tax on, which get tax from their first invoice.
- Existing subscriptions, which keep renewing tax-free (or keep using whatever manual tax rates you attached) until each one is updated.
If you are moving off QuickBooks sales tax at the same time, our guide to switching from QuickBooks sales tax to Stripe Tax covers the cut-over date and the filing overlap. This post is about the subscriptions themselves.
How the Stripe Tax migration tool updates existing subscriptions
Stripe's Dashboard has a tax migration tool built for this job. It works only in live mode. Stripe says it "doesn't support sandboxes, test subscriptions, or legacy test mode," so you can't rehearse it on test data. To test automatic tax in a sandbox, you edit subscriptions one at a time instead.
The flow has seven steps:
- Open the tax migration tool in the Dashboard, in live mode.
- Review the subscriptions that need updating.
- Review Stripe's recommended actions.
- Decide whether to include subscriptions with no billing address, using an inferred location (on by default).
- Review the projected outcome: subscriptions ready to collect tax from a billing address, subscriptions ready to collect tax from an inferred location, and subscriptions that can't be resolved.
- Confirm.
- Fix the remaining subscriptions by hand.
Two things happen when you confirm. Stripe enables automatic tax on the eligible subscriptions, and "Stripe removes manual tax rates from the subscriptions." When the run finishes, Stripe emails you.
Which subscriptions the tool can move
The tool only handles subscriptions that meet all four of Stripe's criteria:
- They are active.
- They don't already collect tax automatically.
- They have enough address information to calculate tax, or an inferred location.
- Their price has a tax behavior set.
The last one is easy to miss. Every price needs to be inclusive or exclusive before Stripe Tax can calculate on it. If you set a default tax behavior in your Stripe Tax settings, Stripe's tax behavior guide says every price without its own tax_behavior uses that default and is "ready for Stripe Tax."
Which subscriptions you must update yourself
Stripe lists two kinds the tool won't handle:
- Subscriptions with schedules. A schedule can carry
automatic_tax[enabled]=falsein its phases, and you have to remove it from every current and future phase and setdefault_settings[automatic_tax][enabled]=true. Our glossary entry on the Stripe subscription schedule explains how phases work. - Connect subscriptions using destination charges or separate charges and transfers.
The tool can also fail on individual subscriptions, usually because it couldn't infer a location: the customer has no email on file, or the email doesn't match a previous transaction on the Stripe network. After a run, "you have to wait a few days before you can run it again," so fix the failures in that window rather than waiting to rerun.
What is an inferred location in Stripe Tax?
An inferred location is a customer location Stripe works out by matching the customer's email address to location data from a previous transaction on the Stripe network. It can include the country, postal code and first address line. Stripe uses it only when the alternative is collecting no tax at all, and it is the lowest-priority location source.
For context, Stripe Tax normally reads a customer's location from the first viable source in a fixed order, per its customer location rules: shipping address, then billing address, then the billing details on the most specific payment method, then the IP address. An inferred location sits below all four.
Stripe's rules for it are strict:
- It fills a gap only when the higher-priority sources are missing or empty. Stripe "doesn't substitute an inferred location for a present, but invalid or incomplete higher-priority address."
- It requires an active customer portal with address updates enabled, so customers can give a full address at any time.
- It can be less precise than a street address. Stripe notes that where tax rates vary inside one postal code, the postal code "might not reflect the exact tax jurisdiction," while adding that postal code resolution is enough for most US calculations.
- It is labeled Inferred on the customer details page and in transaction details.
Later customer edits interact with a stored inferred location in specific ways. A valid billing or shipping address takes precedence over it. An invalid or incomplete address also takes precedence, and then invalid-location behavior applies ("Any non-empty address supersedes an inferred address"). Changing the email or name doesn't recalculate it. And customer updates never create a new inferred location: only an eligible migration does.
The practical read for a bookkeeper: inferred locations get tax flowing on accounts that would otherwise sit at zero, but they are a starting point. Treat every Inferred label as a request to collect a real address.
Why tax changes aren't prorated, and when the first taxed invoice arrives
Here is the sentence again: "We don't prorate the tax changes. The updates take effect at the start of the next billing cycle."
No mid-cycle proration means no surprise invoice when you run the migration. Each subscription just renews with tax at its next cycle. The catch is how far away "next cycle" can be.
| Subscription | Current period | First invoice with Stripe Tax |
|---|---|---|
| Monthly, renews on the 1st | Nov 1 to Dec 1 | Dec 1 |
| Quarterly, renewed Oct 15 | Oct 15 to Jan 15 | Jan 15 |
| Annual, renewed Oct 20 | Oct 20 to next Oct 20 | Next Oct 20 |
That annual subscriber was charged on October 20 for a year of service, with no tax. If you were registered in their jurisdiction on that date, the tax on that sale is a question for your tax adviser, not for Stripe Tax: the migration doesn't go back and recalculate invoices that already finalized.
If you update subscriptions manually instead, the proration question comes back. Stripe's manual path for a subscription that already carries manual tax rates is to clear default_tax_rates and each item's tax_rates, set automatic_tax.enabled to true, and set proration_behavior to none. The alternative it documents is a subscription schedule with two phases: the current period keeps the old tax rates, and the next phase removes them and turns on automatic tax. Either way, the goal is the same one the tool has: tax changes at a cycle boundary, never in the middle.
Before trusting the first renewal, Stripe recommends creating a preview invoice for each updated subscription and checking its automatic_tax status:
completemeans Stripe Tax calculated tax.requires_location_inputsmeans it couldn't find a location.failedis a Stripe-side error worth retrying.
Inclusive or exclusive: what the price you already charge turns into
Every migrated subscription keeps its price. What changes is what that price means once tax applies, and that depends on tax behavior. Stripe's tax behavior guide describes both:
- Exclusive: tax "is added on top of the price."
- Inclusive: "the amount your customer pays remains constant, regardless of the tax amount."
Stripe's Automatic default picks exclusive for USD and CAD prices and inclusive for every other currency.
Take one subscriber at each. The rates below are illustrative, not any jurisdiction's actual rate.
A US subscription at $50 a month, exclusive, at an illustrative 8% rate.
| Before migration | First taxed renewal | |
|---|---|---|
| Subscription amount | $50.00 | $50.00 |
| Tax | $0.00 | $4.00 |
| Customer pays | $50.00 | $54.00 |
| Your sales | $50.00 | $50.00 |
The customer sees a bigger charge. Your revenue doesn't move. That's a customer-communication problem, not a bookkeeping one, and it is worth an email before the renewal.
A European subscription at €40 a month, inclusive, at an illustrative 20% rate.
| Before migration | First taxed renewal | |
|---|---|---|
| Customer pays | €40.00 | €40.00 |
| Tax inside the price | €0.00 | €6.67 |
| Your sales | €40.00 | €33.33 |
The customer notices nothing. Your net revenue on that subscription drops by €6.67 a month, about 16.7%. Across 300 subscribers, that's €2,000 a month moving from your income line to a tax liability. The cash you collect doesn't change; the migration makes the tax inside your price visible.
One trap: you can't change tax_behavior once it is set to inclusive or exclusive. To change it, Stripe says to create a new price with the behavior you want and archive the old one, which means moving subscriptions to the new price. Decide before you run the tool, not after. Our guide to inclusive and exclusive tax in Stripe and QuickBooks covers how each one posts.
What changes in QuickBooks on the first taxed renewal
With Acodei's Invoice Sync, a finalized Stripe invoice becomes a QuickBooks invoice that reproduces its line items and tax lines as your tax settings allow. What the first taxed renewal looks like depends on which tax approach you use in Acodei.
US accounts: the tax product
QuickBooks' Sales Tax Center doesn't let a third party create official tax rates, so Acodei's approach for US companies is a single non-inventory product, such as "Sales Tax," mapped to a liability account. All the Stripe Tax on an invoice rolls into one line on that product.
For the $50 subscriber above, the QuickBooks invoice goes from one line to two:
| Line | Before | After |
|---|---|---|
| Subscription product | $50.00 | $50.00 |
| Sales Tax (liability) | none | $4.00 |
| Invoice total | $50.00 | $54.00 |
The liability account grows by the tax collected, and you file from Stripe Tax's reports, because QuickBooks holds the total owed but not the split by jurisdiction. Our post on Stripe Tax in QuickBooks Online goes deeper on that setup. Because every rate lands on the same product, a migration that swaps old manual rates for Stripe Tax's calculated ones doesn't change the line, only the amount.
If you didn't track tax in Acodei before, there is one switch to flip. In Acodei's Account Mapping, the Stripe Tax section starts with "Do you need to track Stripe Tax?" Set it and choose the tax product before the first taxed renewal syncs.
Non-US accounts: mapped tax codes
Outside the US, Acodei can map each Stripe tax rate ID (txr_...) to a QuickBooks tax code, such as a VAT or GST code. Acodei finds the IDs to map by calling Stripe's list tax rates endpoint. Where one line carries two rates, such as GST plus PST, Acodei can map the pair to a QuickBooks group tax code; our post on GST and PST group tax rates walks through it.
This is where the migration bites. The tool removes your manual tax rates, and the rates Stripe Tax applies afterward are calculated automatically. Acodei's documentation notes that automatically calculated rates aren't returned by that list endpoint, so they won't appear in the mapping screen on their own. You add each new txr_ ID by hand. To find one, open a finalized invoice in Stripe, go to its events, open the finalized event and search the JSON for txr.
The sequence that works:
- Run the migration, or update a first batch of subscriptions.
- Wait for the first taxed renewals to finalize.
- Copy the new
txr_IDs from the finalized invoices. - Add each one in Acodei's advanced tax mapping and pick its QuickBooks tax code.
- Check the first synced QuickBooks invoices against Stripe, line by line.
Acodei's docs suggest setting the Default Product Tax Rate to Exempt when you only want mapped rates to apply tax. And if your prices are inclusive, choosing Inclusive in Acodei turns on its manual inclusive tax calculation, so the QuickBooks invoice shows €33.33 net plus €6.67 tax instead of €40 of sales.
Pitfalls that leave subscriptions untaxed after a migration
The migration report shows what moved. These are the cases worth chasing after it:
- Customers in places you aren't registered. A recognized address that resolves to a jurisdiction without an active registration gets the status
not_collecting, and Stripe Tax assesses no tax. That's correct if you have no obligation there, and silent if you do. Our post on Stripe Tax registration thresholds covers when you need one. - Unrecognized addresses. A status of
unrecognized_locationmeans the address on file can't place the customer. Inferred locations don't rescue these, because a present but invalid address outranks an inference. - Schedules and Connect subscriptions. The tool skips them, so they need the manual path.
- The rerun gap. You can't rerun the tool for a few days. Fix failures in between.
- Payment method changes after migration. Stripe warns that location details might be missing or invalid if a customer's default payment method is updated or removed. Our post on Stripe invoice finalization failures from tax shows what that does to the invoice.
To find what's left, filter the Subscriptions page by Automatic tax: Disabled. To check customers in bulk, export them with all columns and look at the Tax Location Recognized column.
A checklist for moving existing subscriptions to Stripe Tax
- Add or schedule your Stripe Tax registrations.
- Set a preset product tax code, and give products that differ their own
tax_code. - Set a default tax behavior, and decide inclusive or exclusive per price before anything migrates.
- Turn on the customer portal with address updates if you will use inferred locations.
- Email exclusive-price subscribers that their next renewal includes tax.
- Run the migration tool in live mode, and note the unresolved count.
- Move schedules and Connect subscriptions by hand, with
proration_behaviorset tononeor a two-phase schedule. - Preview a sample of invoices and confirm
automatic_tax.statusiscomplete. - In Acodei, turn on Stripe Tax tracking and choose the tax product (US) or advanced mapping (non-US).
- After the first renewals finalize, add any new
txr_IDs to Acodei's advanced mapping. - Compare the first synced QuickBooks invoices with Stripe.
- Work through every Inferred and
unrecognized_locationcustomer.
FAQ
Does Stripe Tax apply to existing subscriptions automatically?
No. Activating Stripe Tax affects new objects created with automatic tax on. Each existing subscription has to be updated, either with Stripe's Dashboard migration tool or by setting automatic_tax.enabled to true on the subscription. Until then it renews without Stripe Tax, or with whatever manual tax rates it already had.
Will my customers be charged a prorated tax amount when I migrate?
Not through the migration tool. Stripe says it doesn't prorate the tax changes and that the updates take effect at the start of the next billing cycle. If you update subscriptions with existing tax rates by hand, Stripe's guidance is to set proration_behavior to none or schedule the change for the next cycle, which avoids prorated items.
What happens to subscriptions with no billing address?
The migration tool can give them an inferred location, matching the customer's email to a previous transaction on the Stripe network. This option is on by default. It needs an active customer portal with address updates enabled, and it only applies when there's no higher-priority location. Customers with no email, or no match, can't be resolved by the tool.
Can I test the Stripe Tax migration tool in a sandbox first?
No. Stripe says the automated migration tool works only in live mode and doesn't support sandboxes, test subscriptions or legacy test mode. In a sandbox, you can edit each subscription in the Dashboard and turn on Calculate tax automatically, then preview invoices to see the result.
Do I need to change anything in QuickBooks after migrating?
With the US tax product approach, the tax line starts carrying amounts on the same liability product, so the main job is filing from Stripe's reports. With mapped tax codes, add the new automatically calculated txr_ IDs to Acodei's advanced mapping, because they aren't returned by Stripe's list tax rates endpoint.
The short version
Turning on Stripe Tax doesn't tax the subscriptions you already have. Stripe's live-mode migration tool turns on automatic tax for active subscriptions with a location and a tax behavior, removes manual tax rates, and can use an inferred location for customers with no address. It doesn't prorate: each subscription picks up tax at its next billing cycle, which for annual plans can be most of a year away. Exclusive prices raise what the customer pays, while inclusive prices shrink your net revenue. In QuickBooks, US accounts on the tax product approach see a tax line where there was none. Non-US accounts using mapped tax codes need each new txr_ ID added to Acodei's advanced mapping by hand.
Let the first taxed renewal land correctly. Acodei's Invoice Sync turns each finalized Stripe invoice into a QuickBooks invoice, with its tax on a liability product or mapped to your QuickBooks tax codes. Start a free trial.
Automate your Stripe to QuickBooks sync
Save hours every month. Acodei automatically syncs your Stripe transactions, invoices, and payouts to QuickBooks Online.
14-day free trial · card required · cancel anytime
How Acodei handles this in your stack
Stripe QuickBooks Integration
See how Acodei syncs Stripe payments, fees, refunds, invoices, and payouts into QuickBooks Online automatically.
Or go straight to a capability
Advanced Product Mapping
Map Stripe products to QuickBooks with rule-based logic on product ID, price ID, metadata, and account. Set rule priority and extend mapping to refunds and fees.
Automated Invoice Sync
Bring Stripe invoices into QuickBooks and auto-apply payments and credit memos, with invoice numbering suffixes and quantity tracking to cut double-entry.
Multi-Currency Mastery
Sync Stripe transactions across currencies with automatic exchange rate handling and currency-specific customer records. Our team enables multicurrency on request, and zero-decimal currencies such as JPY are not supported.
Class Mapping
Map Stripe products to QuickBooks classes for scalable categorization and multi-entity reporting. Class tracking requires QuickBooks Online Plus or Advanced.
Historical Data Import
Backfill historical Stripe data into QuickBooks by month range. Preview volume and cost before syncing so reporting starts from a complete baseline.
How to Connect Stripe to QuickBooks Online
Connect Stripe to QuickBooks Online in minutes. Acodei links both accounts with secure OAuth and syncs payments, fees, refunds, and payouts automatically.
Reconcile Stripe Payments in QuickBooks
Reconcile Stripe in QuickBooks Online automatically. Acodei splits out fees, matches payouts to deposits, and keeps every charge audit-ready.
Related articles
Acodei Journal
Customer Address Changes, Stripe Tax and QuickBooks
Acodei Content Team
Customer Address Changes, Stripe Tax and QuickBooks
11/18/2026
Acodei Journal
Stripe Free Trials and QuickBooks: Signup to First Invoice
Acodei Content Team
Stripe Free Trials and QuickBooks: Signup to First Invoice
11/18/2026
Acodei Journal
Stripe Flexible Billing Mode Migration and QuickBooks
Acodei Content Team
Stripe Flexible Billing Mode Migration and QuickBooks
11/17/2026
Get more operational finance guides like this one
We will only send high-value product and finance content.