#Vangelis
tender nacelle
Can you screenshot the Invoice of the next Sub that you think having the same issue?
I see it has the inclusive tax correctly and doesn't have duplicated tax item
cold sparrow
Sure, the invoices are the following (1st screenshot)
A sample of the invoice for 11 May is (2nd screenshot)
Invoice id: in_1N6ZUGFesvdn5rlRAZFYZoUm
tender nacelle
$10.78 * 5 = $53.9 which is correct and tax is included
cold sparrow
Correct, why the second invoice is $57.46?
tender nacelle
Umm TBH I still haven't got the calculation here yet. I think you have enabled Stripe Tax? And using it also with AvaTax somehow creates duplication
Have you tried turning off StripeTax on your account?
tender nacelle
But was it off when you created the Subscription?
That says "On new Invoices, Subscription...."
cold sparrow
Yes, it was off
tender nacelle
It was off all the time, like from the start?
cold sparrow
Correct, it was off all the time
tender nacelle
hmm, on this request https://dashboard.stripe.com/test/logs/req_BeGIxP3aecwp53 I see you specify a tax rate
So this is the Tax rate applied to the Subscription and all of its Invoice, different than the AvaTax item
cold sparrow
Correct, I calculated the tax_rate and passed it in the checkout session.
And the first invoice is correct, the next invoices add again the tax also from avalara
That is the problem
How we can avoid it?
tender nacelle
I am confused, this tax rate and Avatax is conflicting each other. If you use Avatax (which I suppose will automatically calculate tax as a separated item for you), why would you still use this Tax rate?
How about just removing this Tax Rate and simply use Avatax?
tired phoenixBOT
cold sparrow
And how we will pass the tax in the checkout session if we don't include the tax_rate?
tender nacelle
Is that a requirement for AvaTax integration?
cold sparrow
Yes, we should use AvaTAx integration
tender nacelle
I mean the Tax rate provided, is it a requirement for AvaTax?
I have no context on how AvaTax works, so if you have some documentable it would help!
cold sparrow
No, it is not, but we have to pass the tax_rate to charge the correct amount in the checkout session page
tender nacelle
That's where it felt through the cracks. Setting it will generate tax on every Invoices going on
And Avatax separately generate a different items representing tax, then there are duplications
cold sparrow
What should we do to avoid them?
The process we are implementing is the following:
- We calculate the tax rate (through AvaTax API) on our end before the Stripe's checkout session page
- The checkout session page shows the price with the calculated tax (inclusive)
- When the client completes the payment, we send a webhook from Stripe to AvaTax to add a new record in our Avalara account
tender nacelle
Just asking.. Is AvaTax a must?
cold sparrow
Yes it is 😞
tender nacelle
Okie, how about after the first Invoice, you Update the Subscription to remove the tax rate? https://stripe.com/docs/api/subscriptions/update#update_subscription-items-tax_rates
When updating, pass an empty string to remove previously-defined tax rates.
But be careful with your tax calculation that AvaTax will only reflect the Tax collected from 2nd Invoices
cold sparrow
Hmmmm, interesting! I will try it, thank you so much!
tender nacelle
good luck!
cold sparrow
One more question, should i use tax_behaviour as inclusive or exclusive? Which one is the correct for this case?
tender nacelle
Whichever one display correctly for your payment page. I guess it is exclusive
cold sparrow
As we checked both have he same result, but which one is the right way