Lindor Posted December 9, 2021 Posted December 9, 2021 Hi @Marc Stridgen, not runs correctly but I dont know if can be a new issue but is related. I've a Monthly Plan for 87€/month and a Annual Plan for 897€/year. If I update from actual monthly to annual plan charges a difference of 669.42€. So did not calculate correctly this upgrade. Should be 897€ - 87€ = 810€ if I update the same day that renew the monthly plan, If I consume some weeks should be more than 810€. Can you take a new look again? I deactivate the upgrade/downgrade function again.
Marc Posted December 10, 2021 Posted December 10, 2021 I have split this into a new topic, as its not the same issue there. Please let me know which user you attempted that upgrade on, so I can then take a look Lindor 1
Lindor Posted December 10, 2021 Author Posted December 10, 2021 1 hour ago, Marc Stridgen said: I have split this into a new topic, as its not the same issue there. Please let me know which user you attempted that upgrade on, so I can then take a look User id=471 for example, I test in more users with the same problem. I think that IPS not compare subscription time to calculate this charge. You compare the monthly price with annual price divided for 12 months, so the result allways will be wrong. If I change to annual subscription today will have access for 1 year since today, so should charge complete annual price less the monthly time not covered.
Marc Posted December 10, 2021 Posted December 10, 2021 I have created a ticket for you so that we can take a closer look
Marc Posted January 18, 2022 Posted January 18, 2022 Just updating from the ticket notes from my colleague Quote The difference in cost doesn't include the tax, that's why it doesn't look correct. The tax is added during the checkout process, so they'll still pay the correct amount. I have submitted a potential change for inclusion in a future release so that this upgrade charge amount will show the price including tax if applicable.
Solution Marc Posted January 25, 2022 Solution Posted January 25, 2022 This issue has been resolved in 4.6.10 beta 1. Feel free to give this a try, or await the full release if you prefer
Recommended Posts