cedricrausch Posted June 25, 2017 Share Posted June 25, 2017 Hi I'm having a wrong total price.. I made a package called "Advanced" which costs 179.88 yearly, i setup a one-time free domain on this package (normally 9.99/yearly). The checkout shows everything right, except the "next time" payment amount (see attachement). Does anyone know where the "€275,44 EUR Annually" comes from? Thank you! King Regards Cedric - - - Updated - - - I'm sorry, posted in the wrong thread. 0 Quote Link to comment Share on other sites More sharing options...
Remitur Posted June 25, 2017 Share Posted June 25, 2017 net price (€ 179,88 ) + VAT 21% (€ 37,77 ) = € 217,65 What's the issue? 0 Quote Link to comment Share on other sites More sharing options...
cedricrausch Posted June 25, 2017 Author Share Posted June 25, 2017 (edited) The issue is the 275,44 annualy, not the 217.65. The price customers should be next year should be: hosting: net price (€ 179,88 ) + VAT 21% (€ 37,77 ) = € 217,65 domain: net price (€ 9,99 ) + VAT 21% (€ 2.09 ) = € 12.08 TOTAL: 229.73. But there is written €275.44 annually. Where does those additional €45 come from? Edited June 25, 2017 by cedricrausch 0 Quote Link to comment Share on other sites More sharing options...
Remitur Posted June 25, 2017 Share Posted June 25, 2017 Reading with more attention, I found the issue you're asking for... Is maybe pro-rata billing enabled? 0 Quote Link to comment Share on other sites More sharing options...
cedricrausch Posted June 25, 2017 Author Share Posted June 25, 2017 No it isn't . Already thank you for the help. 0 Quote Link to comment Share on other sites More sharing options...
cedricrausch Posted June 25, 2017 Author Share Posted June 25, 2017 Maybe it's a bug? If i turn of VAT for that product, it shows all the prices without VAT, but the annual price with VAT. So if i turn on VAT on the product, it's calculated double i think? 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted July 2, 2017 WHMCS Support Manager Share Posted July 2, 2017 Hi, We've been bale to reproduce this issue and case CORE-11347 is open internally with our development team to correct this in the next 7.2 maintenance release as a priority. Please accept my apologies for the inconvenience caused. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.