It happens to all hosts once in a while; you need to suspend a client for non-payment. Recently, I had an otherwise good client decide they could no longer pay for their hosting, but instead of telling me so we could work something out, they simply stopped paying. A shame, but it happens.
So yesterday, I suspended the account via Cpanel. What I hadn't remembered at the time was that this client had a daily cron job that would back up and mail (to me) her database. It was only this morning that I realized I hadn't killed this cron, and since it was listed in the server's crontab (which exists outside of cpanel), it kept running despite the account being suspended.
Now, I could have gone in through the shell and edited the crontab file, but if done wrong, bad things© happen. Instead, I tried logging into her cpanel using the regular login (hers) and it didn't let me in, as expected. Good.
Then, using her name and my reseller password, it still allowed access (as it would have when the account was 'live', much to my surprise. This allowed me to kill the cron job from within cpanel.
Just another one of those tips to recall when dealing with clients and cpanel servers. Account suspension does not remove crons, but you can kill them after the fact if you need to. This is useful if the client has not paid, and you want to "motivate" them by not providing access to their files and db backups until they do...I mean...they should have a backup on their local disk too, no?