Glossary

Stripe Tax Threshold Monitoring

Stripe Tax threshold monitoring is the Stripe Tax tool that adds up your Stripe-processed sales, minus refunds, by customer location and compares them with each place's tax registration threshold, to flag where you might need to register.

Also called: Stripe Tax obligations monitoring, Monitor your obligations, Stripe Tax registration threshold monitoring, Stripe Tax threshold notifications

14-day free trial · card required · cancel anytime

Definition

Stripe's monitoring guide says the tool "provides insights about your potential tax registration obligations (called economic nexus in the US)." The mechanism is a comparison: Stripe Tax "tracks your Stripe-processed sales (minus refunds) based on each customer's location and compares these sales against local tax registration thresholds." It uses your preset product tax code, a location it attributes to every transaction, and the time window each place's rules define.

The result is an estimate, and Stripe says so. The tool "highlights potential registration obligations, but it's up to you to confirm whether registration is actually required in each jurisdiction." The gaps come from a published list of assumptions, and several of them matter more outside the US than inside it, because the tool applies one destination-based count to countries whose rules count different things.

The US side, including the notification conditions and why your home state never appears, is covered in the related post on Stripe Tax thresholds and QuickBooks. This entry covers what the count includes, how each sale gets a location, and where a country's own test differs from Stripe's number.

Key points

  • +It counts Stripe-processed sales, minus refunds, by customer location against each place's registration threshold.
  • +The only off-Stripe payments it includes are invoices processed off Stripe and transactions created through the Stripe Tax APIs.
  • +It assumes every sale uses your preset tax code and is taxable at the destination.
  • +It doesn't consider where goods ship from, so a parcel Stripe calculates as an export can still be counted as a sale in the customer's country.
  • +It skips your home US state or country, and it runs in live mode only.
  • +A Connect platform counts connected-account sales only after choosing to be liable for them, and then only for some charge types.
  • +Refunds and credit notes reduce the count, typically within 24 to 48 hours.

What each country page says it counts

Every Stripe country page has a line called "Transactions included in obligations monitoring." For Norway, the UK, Australia, New Zealand, Singapore and Japan it reads "Any taxable transaction." For Switzerland and Liechtenstein it reads "All transactions globally," next to a threshold of 100,000 CHF per rolling 12 months that Stripe notes "includes your world-wide sales."

That line is Stripe's counting basis, not the country's registration test, and the two can differ. Switzerland is the clearest case. The general rule Stripe describes counts global taxable turnover, but the same page describes a special rule for foreign businesses importing low-value goods, which must register "if their annual turnover from selling low-value imported goods exceeds 100,000 CHF." The Swiss Federal Tax Administration's page on registration for mail-order companies defines low-value consignments by their import tax: less than CHF 5. A US seller shipping parcels to Swiss customers is measured against that narrower count, which a worldwide total can't show.

Australia shows the reverse problem. Stripe's Australia page says remote sellers register when sales of services or low-value goods to Australian individuals exceed 75,000 AUD, and that sales to GST-registered Australian businesses that are subject to reverse charge "don't count toward the threshold." The monitoring guide doesn't say it removes those sales. Its stated assumption is that all sales are taxable at the destination, so a seller with many business customers should check how much of its Australian figure is business sales.

Goods shipped from abroad: counted, but not calculated

The monitoring guide says: "We assume that all sales are taxable at the destination. Stripe doesn't consider the actual location of supply, which might be the merchant's business address, where the goods are shipped from, or where an event occurs."

Stripe's calculation works differently. Its country pages for the UK, Norway, and Switzerland and Liechtenstein say that when goods are shipped in from abroad, Stripe "treats the sale as an export and doesn't calculate tax," unless you select the option to calculate tax on cross-border sales of goods on the registration. So the same parcel can be a sale in the customer's country for monitoring and an export for calculation.

The UK makes the gap concrete. Stripe lists its threshold as 1 transaction, counting taxable transactions that reverse charge doesn't apply to. Its UK page also says that if goods are imported in the customer's name, "the sale is considered to occur outside the UK, and no UK VAT is due." A US seller shipping a parcel that the customer imports can see the UK flagged, even though that sale created no UK VAT. Read the flag against the country's own rule for imported goods before registering.

How a sale gets a location

Stripe attributes a location to each transaction once per day, and new transactions reach your threshold within 7 days. This happens even when no tax is calculated, and Stripe says it is a different process from the address validation it uses to calculate tax.

Stripe uses the first source it has, in this order: the address Stripe Tax already validated when it calculated tax, the customer address on the Customer object, the AVS postal code (converted to a state for the US and Canada), the country of the card issuer, a country-specific payment method such as iDEAL for the Netherlands, and as a last resort the customer's IP address.

How much it needs depends on the country. In the US, country alone isn't enough: a transaction needs a state or a postal code Stripe can map to one, or it lands in US unattributed revenue. In Canada, country alone counts toward the country-wide threshold but not toward any province. For other supported countries, Stripe says the country is the only information it needs.

Unattributed revenue counts toward no location. A location with no registration can show as Not collecting tax because Stripe can't determine its threshold status, for example when the revenue is unattributed or your preset product tax code doesn't match that location's supported tax types.

Connect platforms and connected accounts

By default, Stripe says, transactions linked to a platform's connected accounts "don't count toward your platform's tax registration thresholds. They only count toward the connected accounts' tax thresholds." A platform can change that in its Connect settings by choosing to be held liable for sales made by its connected accounts.

After that choice, destination charges count toward the platform with or without on_behalf_of. Separate charges and transfers count only with on_behalf_of, because without it Stripe "can't know who the liable party for the transfer is" and treats the platform as the settlement party. Application fees a platform charges don't count toward its own thresholds, and neither do PaymentRecords a platform reports on behalf of its connected accounts.

For a liable platform, a location can show as Undetermined, which Stripe says means it "lacks the information needed to support you on tax obligations for this location." Stripe gives one cause: a customer location "outside the United States and not in the United Kingdom or European Union with a default PTC of Digital Goods."

What it changes in your books

Nothing, directly. Threshold monitoring is a report about sales Stripe already processed. It creates no transactions, charges no tax and records no liability.

The change comes when you act on it. Stripe's registration guide says adding a registration "allows Stripe to calculate and collect the taxes you're responsible for remitting." From then on, that location's sales carry a tax line, and the tax needs a home in your books, usually a liability account. Sales before you added the registration carry no tax line, so if a country expects tax from an earlier date, that difference has to be worked out with your accountant and recorded by hand. The registration date you choose is the line in your ledger where a location's tax begins.

Frequently asked questions

What does Stripe Tax threshold monitoring count?

Your Stripe-processed sales, minus refunds, grouped by the location Stripe attributes to each customer and compared with each place's registration threshold over that place's time window. Stripe also includes invoices processed off Stripe, transactions created through the Stripe Tax APIs, and transactions you import into Stripe Tax.

Does Stripe threshold monitoring decide whether I have to register?

No. Stripe says the tool highlights potential registration obligations and that it is up to you to confirm whether registration is actually required in each jurisdiction. It assumes every sale is taxable at the destination and doesn't consider where goods ship from, so its figure can differ from the country's own test.

Why does Stripe flag a country where it charges no tax on my parcels?

Because monitoring and calculation follow different rules. Monitoring assumes every sale is taxable where the customer is. Calculation treats goods shipped in from abroad as exports in countries such as the UK, Norway and Switzerland unless you select the cross-border goods option. Check the country's rule for imported goods before registering.

Do connected accounts' sales count toward a Connect platform's threshold?

Not by default. They count toward the connected accounts' own thresholds. If the platform chooses to be liable for its connected accounts' sales, destination charges count toward the platform, and separate charges and transfers count only when they use on_behalf_of.

Do refunds lower my Stripe Tax threshold figure?

Yes. Stripe says refunding a transaction or applying a credit note to an invoice reduces the threshold calculation, typically within 24 to 48 hours. If that takes you back under a threshold, the obligation status updates, but notifications you already received stay in the Dashboard.

What customers say about running Stripe through Acodei

Stripe Verified Partner BadgeIntuit QuickBooks
★★★★★
“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”
RyanOwner at Indie Music Academy
★★★★★
“Works well and is really helpful for massive transactions. The support is really fast and helpful. 100% recommended.”
AndresCo-founder and CEO at Kanguro Collections and Reinsurance

Related reading

More glossary terms

See the full glossary

Ready to try Acodei?

Connect Stripe to QuickBooks Online in minutes and let the fees, refunds, and payouts land where your accountant expects them.

14-day free trial · card required · cancel anytime