bollocks Posted December 11, 2013 Share Posted December 11, 2013 I have the following issue. When someone orders and pays for an .com domain transfer and the transfer takes too long for whatever reason the system generates a 'renewal invoice'. When I look at such domains in the system, they often have due dates like 00/00/0000 or something like 01/01/2000. This changes ofcourse after the domain transferred and the system syncs it with the registry. But if it does not transfer, WHMCS apparently thinks the domain is past due and generates an invoice after a couple of days. How do I solve this? It sees when a domain is not transferred, so it should be able to not generate a renewal invoice despite the due date. Thanks! 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Product Manager WHMCS John Posted December 12, 2013 WHMCS Product Manager Share Posted December 12, 2013 Hi, The Next Due Date of transfer requests is set 1 year from the ordering date. So WHMCS wouldn't generate another invoice until the following year, and a domain transfer certainly shouldn't take that long At that point I think it's clear the client doesn't actually intend on transferring the domain, so the domain's status can be changed to Cancelled. 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted December 13, 2013 Author Share Posted December 13, 2013 Hi John, The issue is that its not set to 'one year from ordering date'. I could make a screenshot of an example but it would show you nothing more then I can tell here. This is domein xxxxx.net ordering date 02-12-2013 Due date: 00/00/0000 Next due date: 00/00/0000 If you prefer a screenshot I can show you one but I would have to blank out the domainname etc for security reasons. Any idea how this can happen? Could it be the API of the registrar that causes this? Thanks! 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted December 31, 2013 Author Share Posted December 31, 2013 Its a pity no reaction is coming as this is very inconvenient. its very possible that I made a configuration error somewhere that causes this, but where? I've attached a screenshot to make things hopefully even clearer. Thanks 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Product Manager WHMCS John Posted January 2, 2014 WHMCS Product Manager Share Posted January 2, 2014 Hi, I've not been able to reproduce the issue with the Next Due dAte being left as 00/00/0000 when a transfer order is placed in v5.2.15. If you're still experiencing the issue, please record a video showing the exact step-0by-step, a good free tool is: http://www.techsmith.com/jing 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted January 3, 2014 Share Posted January 3, 2014 The issue is that its not set to 'one year from ordering date'. Unless it's a domain-type that doesn't extend on transfer, and they're ordering the transfer exactly 1 year prior to expiry, then WHMCS should _NEVER_ be setting the next-due-date to today+1year Better to leave it as 00/00/00 and allow the sync to report/fix or the admin(s) to do so, than give the false impression that the dates make any sense at all ... 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted January 17, 2014 Author Share Posted January 17, 2014 Thee is absolutely nothing to record. Someone places an order to transfer a .com domein. They fill in the worng EPP code or for some other random reason the domain does not transfer. Then the expiry date will be set to 00/00/00 as shown in the picture. After that WHMCS generates invoices for renewal while the domain is not transferred at all. @ Othellotech, I agree with your observation, but the problem is that invoices get generated and some customers pay them although the domain is not (yet) registered with us. 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted February 12, 2014 Author Share Posted February 12, 2014 Another example I found this morning. Domaintransfer has been requested and paid yesterday. Tonight a renewal invoice is created tonight for 00/00/0000 to 29/11/2000 (must be the cheapest registration in history ) See attachment: 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted March 7, 2014 Author Share Posted March 7, 2014 This is a really annoying problem, I can't believe noone is responding to it anymore. We have to scan constantly to see if there are no invoices created for domains that are not transferred yet and have 00/00/000 as their date. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Product Manager WHMCS John Posted March 11, 2014 WHMCS Product Manager Share Posted March 11, 2014 Hi, That's a good indicator that no-one else is experiencing the same problem (and therefore unlikely to be a software problem). Feel free to open a support ticket with login details and we'll be happy to investigate the cause of the issue on your installation. 0 Quote Link to comment Share on other sites More sharing options...
yemiadejuwon Posted March 19, 2014 Share Posted March 19, 2014 Hi,That's a good indicator that no-one else is experiencing the same problem (and therefore unlikely to be a software problem). Feel free to open a support ticket with login details and we'll be happy to investigate the cause of the issue on your installation. I'm experiencing the same problem as stated on the thread I created here: http://forum.whmcs.com/showthread.php?86946-Newly-setup-domain-name-hosting-account-in-WHMCS-is-set-to-00-00-0000 Any hopes of a solution soon? 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted March 21, 2014 Share Posted March 21, 2014 We have to scan constantly to see if there are no invoices created for domains that are not transferred yet and have 00/00/000 as their date. If WHMCS is creating invoices when the date is still set to 00/00/0000 you need to open a ticket with them as that's a bug and something I've not seen on dozens of WHMCS installs, so may be 'peculiar' to your configuration 0 Quote Link to comment Share on other sites More sharing options...
bollocks Posted October 8, 2014 Author Share Posted October 8, 2014 Unfortunatly this is still an issue thats popping up once a week orso. Could it be something in the registry's API that triggers this? If so what? Then I can send an email to our domain provider and ask then to take a look at it. Thanks! 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.