#mick23_code
mighty glacierBOT
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1247322715161890908
đź“ť Have more to share? Add details, code, screenshots, videos, etc. below.
quasi burrow
The value of automatic_tax has four possible states:
STATUS DESCRIPTION POSSIBLE ACTION
supported Automatic tax fully supported. No further action needed.
unrecognized_location The address isn’t valid for determining a tax location. Ask customer for an updated address and set customer.address to the new value.
not_collecting The address is resolvable to a location for which you haven’t set up a registration. Depending on your tax obligations, you can either proceed and Stripe Tax won’t assess any taxes, or you might want to add a new registration for the jurisdiction in which the customer is based.
failed An error occurred with Stripe’s servers. This is rare. Try the request again, or contact Stripe support for additional assistance.
See table at the end of that section
I don't really know what my question is at the moment either....
Me too 🤣
So... What my next step is, is basically;
- In SaaS App, if no subscription present (SaaS masters Subscripsions), then Present Stripe Pricing Table (with automated global tax calculations based on SaaS Mastered Customer Billing Address info)
night nimbus
Hey all, if you have questions, let's post them in the main channel so we're not clogging up other people's threads with unrelated issues.
@grim tangle can you post in #dev-help with a description of your question?
@quasi burrow feel free to continue describing your question. I'll circle back in a minute
quasi burrow
So for the 4x statuses;
- supported (I should be able to restrict this at the SaaS level - assuming that it's highly likely the Stripe Pricing Tables API/Embeddable Stuff actually handles this anyhow
- unrecognized_location (Should probably never happen, as I'm highly likely to restrict in SaaS App based on Customer Billing Address, SaaS Mastered, who can/can't purchase, and it's mastered in SaaS global Countries + Cities/States etc. for tax purposes)
- not_collecting (*** This is the question I'm asking really.... this bit I don't understand.....)
- failed (Fingers crossed, never happens etc. )
So I guess the question really is..... what does "Not Collecting" actually mean in this context?
Especially in regards to the Stripe Pricing Tables stuff
My understanding, at present, is that the Stripe Tax Registration Stuff is basically helping me as a company to determine when I need to go down the formal route of official tax compliance registration - but I wouldn't know that at the point of sale.
Is this stuff all handled by the Stripe Pricing Tables Embeddable Tech, or not?
I guess, what I'm trying to avoid is charging some random global tax, and my finance/accountancy team having to deal with the fallout of "where the hell do I account for this money" etc...
Hopefully that makes sense the question at hand?
@night nimbus
BTW will be logging off very shorly, so will pickup/reference this conversation at some point in the next week
night nimbus
The value for not_collecting is described:
The address is resolvable to a location for which you haven’t set up a registration.
Depending on your tax obligations, you can either proceed and Stripe Tax won’t assess any taxes, or you might want to add a new registration (https://docs.stripe.com/tax/registering) for the jurisdiction in which the customer is based.
What specifically about that value are you unsure of?
quasi burrow
@grim tangle Go away
@night nimbus I guess the question really is around the legalities. Like, if I don't Register for Tax in Jurisdiction X, and that's all "calculated" in Stripe Tax, and I do/don't charge Tax to a Global Customer. What happens?
For a simple example @night nimbus let's say I'm selling an Apple (the edible type, not the piece of junk), globally.
@night nimbus Let's then say "a single tax jurisdiction globally" requires for tax registration BEFORE a SINGLE sale, that causes a bit of a contradiction in the sense that I don't know what I don't know etc.
I appreciate @night nimbus that Stripe cannot provide tax advice, and I'm not expecting that to be absolutely clear. I'm in the situation that I don't know what I don't know and I don't know what to do best. I simply want to embed Stripe into the payment process to enable global sales for a single product.
night nimbus
<@852688350607310918> I guess the question really is around the legalities. Like...
I'm not sure. That's definitely a question for a CPA. We can only really assist with the technical side of things unfortunately
night nimbus
I think that you might be approaching this a little backwards. You want to know what your tax obligations are going to be for all your supported countries before you build an integration. You can rely on Stripe to accurately calculate your taxes, but if you choose not to use Stripe automatic tax (or Stripe doesn't support it in a country that you sell to), then you're going to want to know how to handle that before you build anything
night nimbus
Certified Public Accountant? (according to Google)
Yup. AKA a tax advisor
quasi burrow
I think that you might be approaching this a little backwards. You want to know ...
Yes, in normal circumstances I'd agree.
In this situation, I've got a challenge whereby I'm trying to monetise an already global audience on MySaaS.com (all free info etc) , into a paid service.
Which is probably why I'm finding this extremely difficult trying to basically sell 1x Edible Apple to the world in a legally and tax compliant way.
As it stands right now, I'm highly likely to just restrict sales to only UK registered companies, which is a tad annoying, but seems like the only rule-abiding approach I can possibly take.
i.e. I'm not going to be enabling a Global SaaS Purchase to take place via Stripe Tax, unless I'm confident that my tax advisors and accountants (which don't exist yet....) can handle the specifics. I'm a tech guy.
night nimbus
I hear you. One would think in 2024 that selling an apple to a guy in Spain would be as simple as taking payment and shipping the apple, but taxes make things very complication very quickly.
It's an interesting problem to have where you already have the clients, and just need to make sure the tax authorities are satisfied.
quasi burrow
Indeed.... This is a crazy world we live in!
night nimbus
I would think that you could probably use automatic tax calculation for any of the supported countries (https://docs.stripe.com/tax/supported-countries) in the meantime while you find a CPA, but that could be a bit dubious and I wouldn't recommend it without talking one first
quasi burrow
Yeah I completely understand and agree
I think I've got enough insights to go from now anyhow @night nimbus so I'll go with this direction of travel. Seems like the only genuine next step is basically to restrict global sales until a point in time where I can properly calculate, reconcile and remit taxes to the correct authorities. Seems such a daft global system we have in place right now.
Anyhow, at least you've helped clarify the situation at hand and the options available. Thanks for that.
night nimbus
Happy to assist, even when I too don't like the answers. Best of luck to you