#ju4njo-tax-calculation
azure crag
wary mesa
@earnest jetty we don't really control what Avalara does though
It's really hard to grasp from me from all those pictures and drawings. What matters here as the developer is what do you pass in the API and what do you see in the response
it's likely that Avalara doesn't round the same way maybe?
earnest jetty
I think so ... 🤔
wary mesa
ju4njo-tax-calculation
earnest jetty
However, as you can see in the screeshot 🖼️ . We made those calculations manually and it seems that Avalara returns the correct value ... 🤔
wary mesa
yeah I mean it's a picture and I'm not sure what you're asking. Our API doesn't surface numbers with that many decimals for amounts
https://stripe.com/docs/billing/taxes/tax-rates#rounding maybe this will help @earnest jetty ?
earnest jetty
Yes, you are right. Sorry, please take a look at this image. On the right you can see the Avalara value $3.08 (TAXES/FEES column in the sales table) and on the left the Stripe value $3.07. As you can see the returned values are different and my question is why if we are using the same values to calculate the taxes.
wary mesa
I'm trying really hard to not look at huge pictures
I want to talk to you as a developer to developer solely focusing on code and API Responses if possible
earnest jetty
Got it!
Therefore, I assume that the difference between the API responses is because they round those values differently.
Sorry for the interruption, I know it is difficult to understand questions without sufficient context.
Thank very much 🌝
wary mesa
All good, I get what you're trying to do with that picture representation and it makes sense. The problem is by now looking at the exact raw API response it's hard to grasp where the discrepancy happened