#frallain
1 messages · Page 1 of 1 (latest)
Taking a look!
thanks
Looks like there was an error on finalisation
Stripe Tax is enabled on the invoice, yet the related customer has no location info to determine whether tax is due
OK so Stripe Tax should not be enabled until a location is added to the customer?
Hmm, it'll be enabled. Just any calculation will fail if you we don't have sufficient location info in order to determine if we need to collect taxes: https://stripe.com/docs/tax/customer-locations
And we prevent invoice finalisation/payment in that scenario
OK, that's a problem for us, our flow until now was that customers getting out of trial wihtout having paid anything would get an invoice generated that would be unpaid, thus putting the subscriptoin into past_due status.
Now, the subscription is getting into the active, as the customer had paid.
What would you recommend?
I'd recommend you ensure you're collecting sufficient address/location information from your customers if you want to use Stripe Tax
OK but generally customers in trial do not input any location informationm they just want to try the product before use
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
You will need to collect their address at some point.
OK. also this specif subscription got created with:
no payment_behavior specified.
And generally, for all our other subscriptoins, we have have specified payment_behavior at ALLOW_INCOMPLETE and this "bug" does not happen.
Sorry for delay, still looking
Where do you see this?
Those are customers, but payment_behaviour is a property of a Subscription.
What do you mean by "bug" exactly?
the fact that before Stripe tax got enabled the subscriptions would get into status past_due , but now that it is enabled, they got into status active
OK. I think I need to toggle off Use automatic tax calculation at https://dashboard.stripe.com/settings/tax and wait for the customer to fill in his address to then enable Stripe tax on his subscription with
stripe.Subscription.modify(
subscription_stripe_id,
automatic_tax={"enabled": True},
)
Would that work?
Hey! Taking over for my colleague. I'm not fully understand the bug you are referring to
But then, all the support people in my company who create ad-hoc invoices would have invoices without Stripe Tax enabled, which is far from being ideal
OK. let me synthetize
You need to have stripe tax enabled in your dashboard in order to use automatic_tax={"enabled": True}
the fact that before Stripe tax got enabled the subscriptions would get into status past_due , but now that it is enabled, they got into status active
I don't think that this is related directly to Stripe Tax
I invite. you double check your subscription lifecycle and see why it was passed to active and not past_due
but ynnoj was saying that
Looks like there was an error on finalisation
Stripe Tax is enabled on the invoice, yet the related customer has no location info to determine whether tax is due
and it makes sense.
Yes that's true.
OK then my question is : what the behavior of the toggle Use automatic tax calculation at https://dashboard.stripe.com/settings/tax versus setting automatic_tax={"enabled": True}, on each subscription and invoice?
You need to have both
Are you sure you need the toggle to then use automatic_tax={"enabled": True}, on each sub and invoices?
because in my tests, once the toggle is ON, new subscriptoins and invoices will automatically have automatic_tax enabled.
Wait sorry, are you referring to this attribute?
https://stripe.com/docs/api/subscriptions/create#create_subscription-automatic_tax
yes
Ah sorry yes, I had a confusion with other param
So back to your question:
The toggle is for transactions made from the dashbaord
OK, if the toggle is ON, and I create a subscription manually via the API with
automatic_tax={"enabled": False}, does it overwrite it?
if you pass automatic_tax={"enabled": False} then stripe tax won't be applied
OK, I think I have everything needed to resolve my problem then. Thank you very much!