Domain next due date

[bear]

Moved to v9, we encountered an odd issue today.
We manually process domain renewals after invoices are paid. Overnight, an invoice was generated for a domain, and fully paid by credit. A few hours later, the domain sync cron ran and gave me this: domain.tld: Next Due Date updated to 06/29/2026 (domain obscured for this post). That was the original due date, and having just been paid a few hours earlier, this should have been updated to next year. This is how it had always worked before v9, and system date is accurate. 
I've since manually renewed (which incremented the expiry correctly), and will monitor the next domain sync(s) to see if that changes, but it's really odd in that a paid invoice should trigger the due date, not renewal status, no?

[bear]

Marked the task as done, and on the domainsync that followed it updated correctly. One would have thought paying the invoice would be the trigger for updating the next invoice due date. Strange. 

[RadWebHosting]

It sounds like your Automation Settings include DomainSync and Sync Next Due Date, which query the registrar, if supported, to generate these values. If so, the registrar might have been reporting the expiration date incorrectly or the domain was not successfully renewed at registrar.

Edited 14 hours ago by RadWebHosting

[bear]

It wasn't until I marked the task of renewing it as completed did it update the next due date. That really should not be relying on domain renewal, if it's setting the next date to invoice. Way less reliable than "invoice paid, increment next due date".

[DennisHermannsen]

This is not a result of upgrading to v9. It has always been like that.
If client pays an invoice for domain renewal, the next due date and expiry date is updated automatically by WHMCS. When WHMCS runs the Domain Sync task, it queries the registrar for domain details and it finds the expiration date is now inconsistent, so it changes it. This also updates the next due date.
It has been like that for as long as I can remember.

[bear]

Never once happened to us here, that the due date in domainsync was "changed" to the same date, nor that it was seemingly triggered to be correct by marking the renewal task as completed (it was delayed by investigating this time). Weird. I'd have assumed invoices are separate and didn't rely on registrar reporting.

[Damo]

Credits (including the new credit notes) have changed it seems. 
 

When you look at the invoice that was paid by the existing credit does the credit payment appear as a transaction at the very bottom of the invoice?  Also checkout the Transaction tab for this client.  It seems that the payment gets processed but the renewal 'action' remains pending. 

[DennisHermannsen]

24 minutes ago, bear said:

I'd have assumed invoices are separate and didn't rely on registrar reporting.

They are. They rely on the domain's next due date in WHMCS - but they Domain Sync changes the next due date if the expiry date with the registry doesn't match the value in WHMCS. 

[bear]

25 minutes ago, Damo said:

Credits (including the new credit notes) have changed it seems. 
 

When you look at the invoice that was paid by the existing credit does the credit payment appear as a transaction at the very bottom of the invoice?  Also checkout the Transaction tab for this client.  It seems that the payment gets processed but the renewal 'action' remains pending. 

Not as a transaction, but a credit note. Maybe that's the difference here. No transaction recorded for it.