When an invoice goes unpaid, WHMAZ escalates automatically on a fixed schedule. Understanding the ladder tells you exactly when a customer's service will be affected.

The three stages

1. Renewal invoice generated ahead of the expiry date and emailed to the customer. Where a domain and its linked hosting service share a renewal date, they are combined onto a single invoice.
2. Suspension once the invoice is overdue by suspension_days_after_due days. The hosting account is suspended and the customer is emailed.
3. Termination after a further cancellation_days_after_suspension days still unpaid. The hosting account is deleted.

Paying the invoice at any point stops the ladder.

Configuring it

Both intervals are set under Settings → Automation. Choose them deliberately:

• Too short and you will suspend good customers over a payment that was a few days late, generating angry tickets.
• Too long and you carry unpaid accounts for months.
• A common starting point is suspension around 7 days after the due date and termination around 14 days after suspension.

Termination deletes data

The termination pass removes the hosting account from the control panel. Make sure your suspension and termination emails say clearly what will happen and when, and that your backup policy is documented, before you let this run against live customers.

Pausing the ladder

Set cron_enabled to 0 in Settings → Automation to freeze the suspension and termination passes while leaving other tasks running. This is worth doing while you are still testing, or during a billing dispute.