1. List every prepaid provider account and the services charged to it. Record the account currency, balance source, funding method and responsible operator.
2. Review normal sales and upcoming renewals to estimate the funds needed before the next funding opportunity. Include unusual renewal clusters and provider price changes.
3. Set a low-balance threshold that gives the team enough time to act. Configure the provider's supported alerts and verify they reach a monitored mailbox or workflow.
4. If automatic top-up is supported and approved, review the trigger, amount, payment method and failure notification. An expired card or rejected payment can still interrupt funding.
5. Check the provider balance after a deposit and compare it with the receipt. Do not repeatedly submit deposits while an earlier one is still processing.
6. Review provisioning and renewal failures for balance errors, especially after a sales increase or large renewal batch.

For example, WHMCS Marketplace provides low-balance alerts and optional automatic reloading for MarketConnect funds. Its alert threshold, recipients and reload settings belong to that Marketplace account. Other providers have their own controls, limits and funding methods.

Keep customer credit balances separate from supplier funding. Crediting a customer in your billing system does not transfer money to the upstream registrar or hosting provider.

• Reconcile hosting orders invoices payments and provisioned services
• Prepare a hosting reseller launch checklist
• Prepare a useful escalation to your upstream hosting provider
• Investigate stalled HostBill background and provisioning tasks

• WHMCS Marketplace balance alerts
• WHMCS Marketplace automatic balance reloading
• HostBill domain automation
• WHMCS domain renewals