WHMCS automation should implement the hosting company's approved billing and service policy. Configure invoice timing, reminders, suspension and termination together so that customers receive the intended notices before an account action occurs.
IN THIS ARTICLE
01 Translate the policy into settings
- Write down the invoice lead time, payment due date, reminder schedule, suspension delay and termination delay for each product family. Identify exceptions such as disputed invoices or services with special contracts.
- Open System Settings and Automation Settings. Confirm that the cron is installed and that the daily Time of Day matches the team's operating schedule.
- Set invoice generation timing and review advanced cycle or domain settings where used. Confirm that the dates align with the service's Next Due Date.
- Configure payment reminders and overdue notices independently. Review the associated email templates before enabling them.
- Enable automatic suspension only after confirming the suspension delay and the provisioning module's supported behavior.
- Review automatic termination separately. Termination can delete the remote hosting account while retaining its WHMCS record, so it requires its own recovery and retention decision.
How do unsuspension and service exceptions affect automation?
Automatic unsuspension is intended for qualifying services suspended for nonpayment after the relevant invoice is paid. A service suspended for a custom administrative reason should not be assumed to reactivate in the same way. Record suspension reasons consistently and inspect the service before manually overriding an account action.
Review existing service dates and unpaid invoices before changing global delays. Shortening a delay can make older overdue services eligible immediately on the next run. Evaluate the affected records first and schedule the change when staff can review results.
02 Test and monitor the first cycle
Use a private test environment with external actions isolated to confirm how the settings affect representative services. In production, inspect Automation Status after the first relevant run, compare generated invoices and notices with expected dates, and resolve Module Queue failures individually.
Document which administrator owns future changes. Avoid solving a single customer's exception by changing a global policy that affects every eligible service.