Ask most hosting providers what "automation" means in their billing stack, and the honest answer is: a scheduled job that runs every hour or so, checks for overdue invoices, and suspends the matching accounts. That's automation in the loosest sense — it removes a manual step, but it also means every account you suspend is suspended late, and every account you reinstate sits suspended for up to an hour after the client already paid.
Webhosting automation done properly is event-driven, not schedule-driven. A payment clears — from M-Pesa, a card processor, or any other rail — and that event fires directly into the provisioning layer: reinstate the account, update the ledger, send the receipt, all within the same transaction. An invoice lapses and the same principle applies in reverse: suspension fires the moment the grace period ends, not whenever the next cron cycle happens to run.
This is the automation layer I build into every webhosting billing system I deliver — provisioning, suspension, reinstatement, upgrade proration and renewal reminders wired directly to payment and lifecycle events rather than batched into periodic jobs. The difference shows up immediately in support ticket volume: "why is my paid account still suspended" simply stops being a ticket category your team has to handle.