Domain-expiry handling must reflect the actual extension and registrar lifecycle. WHMCS grace-period settings help control billing availability, but they do not guarantee that an expired domain remains recoverable.
IN THIS ARTICLE
01 Align the billing date with the registrar date
The domain's Expiry Date records the registration term reported by the registrar. Its Next Due Date controls customer billing and may deliberately be earlier. The dates should follow the approved renewal lead time rather than always being identical.
- Open the client's domain record and compare both dates with the authoritative registrar record.
- Confirm the billing buffer your company uses before actual expiry.
- In Automation Settings, inspect Domain Sync Enabled and Sync Next Due Date. When due-date sync is enabled, its offset sets how many days before expiry the billing date should fall.
- Review Domain Sync Notify Only before expecting changes. It reports proposed changes without applying them.
- Check the resulting domain record after the relevant sync and review already generated invoices separately.
A later sync can replace a manual due-date adjustment when the automatic setting remains enabled. Correct the governing policy and configuration instead of repeatedly editing the same date. Neither date editing nor a paid invoice extends registration at the registrar.
02 Configure the expiry workflow
- Confirm the registrar's current renewal, grace and redemption rules for each offered extension.
- Open Domain Pricing and review the extension's grace and redemption settings and fees.
- Review global domain grace and redemption behavior in General Settings.
- Configure domain renewal notices and verify the authorised recipients for customer accounts.
- Check domain-sync operation so that expiry dates and transfer states remain current.
- Test the billing and notice sequence using a controlled record, including how a mixed invoice is adjusted when a domain is no longer renewable.
03 Respond to an expired domain
Check the domain at the registrar immediately and establish whether normal renewal, a restore operation or no recovery is available. Confirm the current fee and required action before requesting payment. Do not promise recovery from the WHMCS date alone.
If the customer already paid an earlier invoice, reconcile that payment and any failed renewal attempt before creating another charge. Use the supported current invoice adjustment process and explain the revised amount clearly.
04 Example: keep a seven-day billing buffer
Suppose the registrar confirms that example.com expires on 30 November 2026, and the company's approved policy collects the renewal seven days earlier. These dates illustrate a configuration decision, not a registry grace-period promise.
| Field or setting | Expected example value |
|---|---|
| Expiry Date | 30 November 2026, matching the registrar. |
| Sync Next Due Date offset | 7 days before expiry, if automatic due-date sync is the chosen policy. |
| Next Due Date | 23 November 2026. |
After a supported sync applies, compare the record with this intended result. Invoice generation timing is configured separately relative to the billing date, so also inspect the renewal invoice schedule. A successful payment still needs a confirmed registrar renewal and a new expiry date.
Common questions
Is a grace period guaranteed for every domain?
No. Treat WHMCS defaults as configuration starting points and verify the actual provider and extension rules. An internal grace value cannot extend a registry deadline.
Where can staff check whether a notice was sent?
Review Sent Domain Reminders on the domain record or the Domain Renewal Reminder Emails report. Then check delivery evidence if the customer did not receive it.
Should an expired domain invoice stay payable?
Only when the offered renewal can still be fulfilled under the approved process. Review the provider state and WHMCS expiry handling before retaining or issuing a payment request.