Customer Address Changes, Stripe Tax and QuickBooks

A subscriber moves and Stripe Tax quietly changes the next invoice. Which address it reads, when it applies, prorations, and what reaches QuickBooks.

Acodei Content Team · 11/18/2026 · 13 min read

A subscriber pays you $200 a month. In April they move to a new city and type the new address into their billing details. Nothing errors. No webhook says "tax jurisdiction changed." On May 1 the renewal goes out with a different tax amount, Stripe Tax files it under a different jurisdiction, and your QuickBooks customer record still shows the old street.

That is how an address change works with Stripe Tax: quietly, and on a delay. The rate moves when the next invoice finalizes, not when the address is saved. Which address counts is not always the one that was edited. And the QuickBooks side changes in ways that depend on how you record Stripe Tax there.

Stripe Tax lines, in QuickBooks the way you record tax. Acodei's Invoice Sync turns finalized Stripe invoices into QuickBooks invoices, with tax lines attached according to the tax approach you choose in Acodei: one tax product mapped to a liability account, or each Stripe tax rate mapped to a QuickBooks tax code. Start a free trial.

This post follows one subscriber through a move: which address Stripe Tax reads, when the change takes effect, what happens to prorations that straddle the move, the moves that change more than the rate, and what reaches QuickBooks under each tax approach.

Which address does Stripe Tax use for a subscription invoice?

One address, chosen by a fixed priority. Stripe's customer location rules say "Stripe Tax uses a single address as your customer's location when calculating tax," and it takes the first viable one of these: the customer's shipping address, then the billing address, then the billing details on the most specific payment method, then the customer's IP address.

The order matters more than people expect when someone moves.

The shipping address wins. If the customer object has a shipping address, Stripe Tax uses it, even if the customer has just updated their billing address. A subscriber who changes their billing address in April but leaves an old shipping address on file keeps getting taxed at the old location. For digital subscriptions the shipping address is often a leftover from an earlier physical order, which is exactly why nobody thinks to update it.

A bad address does not fall through. Stripe is explicit: "If a shipping address is present but invalid, we raise a customer_tax_location_invalid error instead of trying the next address in this list." The same rule applies to the billing address. A half-typed new address does not politely step aside for the payment method's details.

The payment method sits below both. Stripe checks the invoice's default payment method, then the subscription's, then the customer's. A card update with a new billing ZIP code changes nothing if the customer has a valid address on file. It only matters for customers with no address at all.

In the US, precision matters even for a short move. Stripe asks for a full address where possible and calls the result rooftop-accurate, noting that "two houses located side-by-side on the same street might be subject to different tax rates, because of complex jurisdiction boundaries." A move across town can change the rate. So can a move across the street.

When does the new address take effect on a subscription?

When the next invoice finalizes. Stripe's invoicing tax guide says "Stripe calculates the tax at the published rate at the time of invoice finalization," using "the customer's tax settings and location" among its inputs. The address saved in April does nothing to April's invoice, which already finalized on April 1. It applies to the next invoice that finalizes after the change.

Stripe's subscription tax guide states the consequence directly: "If your customer has other existing subscriptions with automatic tax enabled and you update their address information, the tax and total amounts on their future invoices might be different. This is because tax rates vary depending on customer location."

Three practical consequences follow.

  1. Past invoices never change. An invoice finalized at the old address keeps its old tax. Nothing gets recalculated retroactively, so nothing in QuickBooks needs to be reversed when an address changes.
  2. The draft window counts. A subscription renewal invoice is created as a draft and finalized later (about an hour by default). An address change saved in that window applies to the renewal, even though the draft already existed when the customer moved.
  3. Several subscriptions move together. The location belongs to the customer, not to a subscription. A customer with two subscriptions on different billing dates gets the new location on both, each from its own next finalization.

If you want to know what the next invoice will carry before it exists, a preview invoice calculates it for you. That is the cheapest way to check a move before it hits your books.

A worked move: the first renewal at the new address

Here is the simplest case, using illustrative rates. Your real rates come from Stripe Tax.

  • Subscription: $200 a month, tax exclusive, renews on the 1st.
  • Old address: a combined rate of 7.25%.
  • New address: a combined rate of 8.5%. The customer saves it on April 12.
  • Shipping address on file: none.
InvoiceFinalizesLocation usedSubtotalTaxTotal
April renewalApril 1Old$200.00$14.50$214.50
May renewalMay 1New$200.00$17.00$217.00

Nothing about the May invoice looks unusual in Stripe apart from the tax line. Same price, same customer, same subscription. The difference is $2.50 a month, which is easy to miss in a close and easy to misread as a rate change.

Now change one fact: the customer still has an old shipping address on file. The May invoice uses the shipping address, finalizes at 7.25%, and the tax is $14.50 again. Stripe is calculating correctly from the data it has. The data is stale. If the customer actually lives at the new address, that is under-collected tax in a jurisdiction you may owe, and the fix is the shipping address, not the billing one.

Prorations that straddle the move

Prorations are where a move gets harder to reason about. Say the same customer upgrades on April 20 to a $300 plan, with proration_behavior set to always_invoice, so Stripe invoices the change immediately. With 11 of 30 days left in April:

LineAmount
Unused time on the $200 plan (credit)-$73.33
Remaining time on the $300 plan$110.00
Net before tax$36.67

That invoice finalizes on April 20, after the move. Both lines sit on it, and Stripe's docs say tax is calculated when the invoice finalizes, from the customer's location at that point. What the docs don't spell out is a separate rule for a credit proration that covers time originally billed at the old address.

Here is why that matters. The 11 days being credited were taxed at 7.25% on April 1, which is $5.32 of tax. If the credit line is taxed at the new 8.5% instead, it reverses $6.23. The $0.91 gap is small for one customer and not small across a few hundred moves a year. Don't assume either answer. Before you make the change, preview the invoice and read the tax on each line, or check the finalized invoice's tax breakdown afterward.

If proration_behavior is create_prorations instead, the two lines wait as pending items and land on the May 1 renewal. Same question, one invoice later: they are taxed when May's invoice finalizes. For the proration settings themselves, see our proration glossary entry.

Moves that change more than the rate

Most moves just change a percentage. Three kinds change the shape of the invoice.

A move to a place where you aren't registered. Tax drops to zero and nothing errors. Stripe says it "doesn't return an error on transactions in jurisdictions where you have no registration; we just don't calculate or collect tax," and the line's taxability reason reads not_collecting. Stripe's zero tax guide adds that not_collecting can also mean a nontaxable product tax code, so check the product before concluding it's a registration gap. If moves are pushing customers into new states, our post on Stripe Tax registration thresholds covers when that zero becomes a problem.

A move that leaves an unusable address. Stripe's location guide says "Location details might be missing or invalid if you update or remove a customer's default payment method." For a subscription, the invoice then finalizes "without calculating or collecting taxes," automatic_tax[enabled] switches to false on the subscription, and payment is still collected. Fixing the address later does not switch automatic tax back on by itself. Our post on Stripe invoice finalization failures from tax walks through finding and repairing these.

A move that changes how many taxes apply. Outside the US, a move can change the number of tax lines, not just the rate. In Canada, for example, Stripe notes that location reports are available "for GST/HST registrations and for provincial registrations in British Columbia, Manitoba, Saskatchewan, and Quebec" (Stripe Tax in Canada). If you hold a provincial registration in the province a customer moves to, their invoices can go from one tax on each line to two. That matters for how the tax is mapped in QuickBooks, which is the next section.

What QuickBooks receives after an address change

What changes in QuickBooks depends on how you record Stripe Tax there. Acodei's Tax settings offer two approaches for Stripe Tax, and Invoice Sync attaches tax lines according to the one you chose.

US accounts: the tax product approach

US QuickBooks doesn't let third-party apps create official tax rates in its Sales Tax Center, so US accounts typically use Acodei's tax product approach. You create a non-inventory product called something like "Sales Tax," mapped to a liability account, and Acodei rolls all Stripe Tax on an invoice into a single line on that product.

After a move, that line simply carries a different amount. In the worked example, the QuickBooks invoice for May shows the $200 subscription line and a Sales Tax line of $17.00 instead of $14.50. QuickBooks has no idea that a jurisdiction changed, because under this approach it never knew the jurisdiction in the first place.

That is by design. Under the tax product approach, the jurisdiction breakdown for filing comes from Stripe Tax's reports, and the QuickBooks liability account holds the total you owe. So the move shows up where your filing data lives: in Stripe's tax location report, April's invoice under the old jurisdiction and May's under the new one. For more on that split, see our guide to recording Stripe Tax in QuickBooks Online.

Non-US accounts: mapping tax rates to QuickBooks tax codes

With Acodei's QuickBooks Tax Rate (Advanced) approach, each Stripe tax rate ID (txr_...) is mapped to a QuickBooks tax code, and each invoice line is assigned the matching code. Here a move can matter more, because the new jurisdiction can bring tax rate IDs your mapping has never seen.

Acodei's documentation notes that with automatic tax, a rate "is automatically calculated and is not associated with a manually created tax rate object," and Stripe's tax rate list doesn't return it. You find the txr_ ID on the finalized invoice and add it to the Advanced mapping by hand. When a line carries more than one rate, such as a federal and a provincial tax together, you can map the set of Stripe rates to a single QuickBooks group tax code.

Acodei's Tax settings also have a Default Product Tax Rate, which its documentation suggests typically setting to Exempt so tax applies only to mapped rates. After a move into a new jurisdiction, check that the customer's next invoice came through with a mapped tax code. Our post on Stripe tax rate changes covers the same mapping gap from the other direction, when a rate changes rather than a customer.

The customer record keeps the old address

Acodei matches Stripe customers to QuickBooks customers by name, so an address change doesn't create a new QuickBooks customer. It also doesn't update the existing one. Acodei's customer documentation is direct: "We do not update customer data (address, email) after the first sync / customer creation." If you want the QuickBooks customer to show the new address, edit it in QuickBooks.

One more mismatch to know about. When Acodei creates a QuickBooks customer, by default it takes the address from the Stripe customer's billing address first, then a charge's billing details. Stripe Tax looks at the shipping address first. So the address on a QuickBooks customer is not necessarily the address Stripe Tax used. For tax questions, Stripe's records are the ones to trust.

A checklist for address changes on taxed subscriptions

  1. Find the address Stripe Tax is using. Retrieve the customer with expand: ['tax']. The response shows the computed location and its source, such as billing_address.
  2. Clear or update stale shipping addresses on subscription customers. They outrank the billing address.
  3. Validate on write. Update addresses with tax[validate_location]=immediately so a bad address fails now, not at the next renewal.
  4. Preview the next invoice for customers who moved, especially before a plan change that creates prorations.
  5. Watch for zero tax with a not_collecting reason on customers who moved into a new state or country.
  6. Filter subscriptions by "Automatic tax not enabled" in the Stripe Dashboard each month. That is where moves that broke the location end up.
  7. For mapped tax codes, check the first invoice after a move for a new txr_ ID, and add it to your Advanced mapping.
  8. File from Stripe's location reports, not from QuickBooks customer addresses.

Let Stripe Tax decide the jurisdiction and let QuickBooks hold the totals. Acodei's Invoice Sync puts each finalized Stripe invoice into QuickBooks with its tax lines attached per your tax settings, so a subscriber's move shows up as what it is: a different tax amount on the next invoice. Start a free trial.

FAQ

Does Stripe recalculate tax on past invoices when a customer's address changes?

No. Stripe Tax calculates tax when an invoice finalizes, using the customer's location at that point. Invoices finalized before the address change keep the tax they were issued with. The new location applies to invoices that finalize after the change, so there is nothing to correct in QuickBooks for earlier periods.

Why didn't the tax change after my customer updated their billing address?

Most often because the customer also has a shipping address on file. Stripe Tax uses the shipping address first and the billing address second, so an old shipping address keeps the old location in place. The other common cause is timing: the change applies from the next invoice that finalizes, not the invoice already issued.

Does a customer's address change create a new customer in QuickBooks?

Not through Acodei. Acodei matches Stripe customers to QuickBooks customers by name, so an address change alone leaves the match in place. Acodei also doesn't update the address on an existing QuickBooks customer after it creates it. If the QuickBooks record should show the new address, edit it in QuickBooks directly.

How do prorations work for tax when a customer moves mid-cycle?

Proration lines are taxed on the invoice they land on, when that invoice finalizes. With always_invoice that is immediately; with create_prorations it is the next renewal. Stripe's docs don't describe a separate rule for a credit covering time billed at the old address, so preview the invoice and check the tax on each line.

Where do I see which state a Stripe subscription's tax was filed under?

In Stripe Tax's reports, such as the location report, which break collected tax down by jurisdiction. If you record Stripe Tax in QuickBooks as a single tax product mapped to a liability account, QuickBooks holds the total you owe but not the jurisdiction split, so filing data comes from Stripe.

The short version

When a subscriber moves, Stripe Tax picks up the new location at the next invoice finalization, and only if the new address is the one it actually reads. Shipping beats billing, a bad address blocks the lookup, and a move into a jurisdiction where you aren't registered produces zero tax without an error. Prorations straddling the move are taxed when their invoice finalizes, so preview them. In QuickBooks, a US tax product line just shows a different amount, mapped tax codes may need a new txr_ ID, and the customer record keeps its old address until you change it.

Share

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

Get more operational finance guides like this one

We will only send high-value product and finance content.