Return a service from Hosting Suite renewals to WHMCS billing

Use the explicit billing handoff when a connected service should return to standard WHMCS invoicing. Turning automatic renewal off or disabling the product does not by itself resolve open renewal records and assign future billing safely.

01 Prepare the service

  1. Open Hosting Renewals and Renewal studio.
  2. Find the service and inspect its latest renewal, current due date, cycle and recurring amount.
  3. Resolve open renewal invoices. Check payment and applied credit before deciding whether an invoice should be paid or cancelled.
  4. Review any active recurring promotion that prevents handoff and decide how the customer's future price should be represented.
  5. Confirm the service should remain active or suspended under the intended policy after the change.

02 Apply the handoff

Choose Actions > Return to WHMCS billing, or select services and use Renewal invoicing. In the handoff dialog, select the intended action and review the current invoicing owner.

Enter a useful reason and select Apply to selected. Each service is checked independently, so review every result. A failure on one service should not be treated as proof that the others also stayed unchanged.

03 Verify the new owner

A returned service is invoiced by WHMCS again and no longer shows the Hosting Suite renewal card. It is not automatically reconnected merely because the product remains enabled; an administrator must connect it again deliberately.

Verify the service's next due date and recurring amount, then confirm the native invoice-generation schedule will cover the next period. Check that an old subscription or open invoice will not create a duplicate collection. Automatic renewal preferences and external payment subscriptions are different mechanisms.

04 Reconnect when appropriate

Use Connect to the suite when returning a service to module-managed renewals. Resolve unpaid native WHMCS invoices and pending cancellation requests first. Only eligible active or suspended recurring services can be connected.

Read the result and recheck the customer renewal card. Do not force connection by directly editing module tables or deleting an unresolved billing record.

What should I do before deactivating the renewal engine?

Inventory every connected service and complete the handoff requirements before deactivating the module. The supplied renewal implementation requires WHMCS 8, so include this handoff in any plan that moves beyond that supported accounting scope.

Retain backups and a report of the final service dates, ownership and unresolved cases. A successful handoff is demonstrated by correct future invoicing and no duplicate charge path, rather than by the disappearance of a button alone.

Sources and further reading

  • 0 Users Found This Useful
  • hosting-suite, resellers
Was this answer helpful?

Related Articles

Configure Hosting Suite access rules and verify effective permissions

Hosting Suite access rules add module-specific restrictions to the permissions already granted...

Configure free AI allowances and service usage limits

Free AI allowances and purchased AI credits are different controls. The free allowance permits...

Set safe operating expectations for AI changes and Undo

The Engineers can inspect supported information and propose changes through available tools....

Price paid AI credits and check the protected minimum

Paid AI credits convert model usage into a service balance customers can buy through WHMCS....

Reconcile AI credit purchases, invoices and refunds

AI credit purchases create WHMCS invoices and add credits after successful payment. Use the...