Jump to content

backtogeek

Member
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

4 Neutral

About backtogeek

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Feature requests don't get taken seriously now even if they do pick up interest, it is at the point that the entire feature request thing has lost the interest of the majority of your client base. Some are 7+ years old with a LOT of up votes (considering the very small pool of people active on the requests site) that have not even been acknowledged by WHMCS in any meaningful way. The obvious solution to this problem is NOT to get in to the habit of keeping a copy of the six theme as any important changes will then likely be missed as that bad habit forms, the proper solution as implemented in the majority of serious projects is the ability to either point at a custom css file via the web ui so theme: six Custom css: template/custom/mycustom.css I might put in a feature request to abolish the feature requests section and start it again with a fresh clean slate and invite the entire customer base to participate again with the promise that WHMCS will acknowledge and make final decisions within 3 months of XX threshold being reached, then I will check back on this request in 2025 🙂
  2. I did get a reply yesterday after getting is escalated, it is quite a complex issue though so I had to re-iterate a few things, waiting on a reply again. top and bottom of it being they know whmcs is not complaint but they are saying HMRC wont give them the info they need, I am part of the EU VAT Action group and WHMCS's responses were actually seen by the policy office at 10 downing street today. WHMCS have not yet told me who they contacted to get the info they need though so it was 'information only' With so many payment gateways and platforms moving to handle the VATMOSS on behalf of customers my feeling is (and I could be wrong) WHMCS do not want to put the effort in to get things compliant and are instead looking at ways to deflect responsibility. If I am wrong and I could well be, WHMCS should know this is how it looks from the outside.
  3. Just to add to this there are a number of gateways and services that could be easily integrated in to WHMCS by WHMCS (I have contacted them and they confirmed they would work with WHMCS on this) that essentially takes the burden away from the hosts as they fully handle all VAT on behalf of the merchant. examples are: Paddle.com taxamo.com
  4. sorry thanks, i saw it said your comment is held for moderation but then it vanished.
  5. Hi Folks, I have been looking for info for a while on how WHMCS can be made compliant and given the vast resources WHMCS has I have to say this response is VERY disappointing. A few points. Point 1: The VAT rate is to be charged based on the customers LOCATION at the time of order, not in accordance with the address they enter. e.g. I am from the UK, my billing address may well be in the UK however if I order service from a digital merchant while I am in Germany then I pay the rate of VAT for Germany. When I return to the UK I then need to pay VAT at the UK Rate and so on. Point 2: Merchants need to be able to display the prices pre order including VAT based on the location of the visitor, not post order confirmation. Point 3: 3 Pieces of corroborating information that confirms the customers location at the time of sale (and all subsequent transactions) must be stored for no less than 10 years. Point 4: Individual VAT specific reporting must be available per EU state. As far as I can see all the WHMCS plugin lets you do is set a VAT rate per country which only kicks in after the user presses "buy" or "order" and then enters 1 bit of information. As such WHMCS is not compliant, this plugin does not make you compliant 1 bit and additionally as it turns out if you are in the EU (or are registered in the EU) and you decide not to sell to others outside you own state to avoid complexity you are breaking anti-discrimination laws. I have sent a ticket to WHMCS, waiting for a reply. Sorry but very little info in this thread is correct, doing it the way this thread is suggesting may be convenient but it is not compliant. Also in terms of this blog post: http://blog.whmcs.com/?t=96594 it is just wrong for the reasons above and the MOSS team have had an open system and support staff in place to help people and software vendors be complaint since October, who exactly have WHMCS tried to contact?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated