#MikaelEliasson-proration-tax

1 messages · Page 1 of 1 (latest)

sturdy briar
#

Hey! How are you calculating tax in your Stripe integration?

balmy ibex
#

We set the tax rate on the items in the subscription. Which we had for both the source subscription and the new items when it happened. Since then we started to explicitly set the tax rate on the subscription which solves our issue. But I still think it's a bug or at least very unexpected behaviour

#

So no rush at all for us to get any response on this. I just figured it seems like something you might want to know about.

sturdy briar
#

Feel like I've seen something around tax and proration recently. Bear with me!

sturdy briar
#

Hey! Are you still around? I'm so sorry for the delay

#

Can you share some of the related object IDs? The subscription and/or invoices

balmy ibex
#

One invoice that became faulty is this one: in_1JpYxUGKlXGxR30sNOAoRGLC which is for the upgrade of subscription sub_1JmwyfGKlXGxR30sFyZTGfr4

#

We had like 20 of these but they should all be the same case.

reef lion
#

Hi @balmy ibex, thank you for your patience while I dug into this. I looked at the subscription that you shared and noticed that it was built in such a way as to not send an invoice until Oct 2022. When we're calculating tax prorations for negative proration amounts (credits), we look back to see what tax rate was used on the last invoice. Since this subscription hadn't been invoiced when we try to do this we don't find any information and therefore don't prorate any tax amounts as it seems the customer hasn't paid any tax yet.

honest mantle
#

@balmy ibex are you unblocked here?

balmy ibex
#

I see, that is very unexpected behaviour to me as a consumer.

We got around it by making sure to set the default tax rate. But I would honestly preferred if you had thrown an exception instead if you couldn't figure out the tax rate.

We are unblocked. I just wanted to report it if it was something you wanted to look into.