SilverNodashi Posted January 22, 2010 Share Posted January 22, 2010 I setup overusage billing on our shared cPanel accounts, and noticed that some of the accounts got incorrect invoices. Clients can choose extra bandwidth using "Configurable Option", so if the account they choose has 100MB bandwidth as standard, they can choose to add 100MB (or more) extra bandwidth using the "Configurable Options". We then change their plans in WHM with the new bandwidth limits. So, in this example, Daleen has 200MB bandwidth limit: Disk Usage:0 MB, Disk Limit: 50 MB, 0% Used :: BW Usage: 149 MB, BW Limit: 200 MB, 75% Used (Last Updated: 22/01/2010 00:14) She uses the account for email only, no website files (hence 0MB disk usage). Last month, she used 246MB bandwidth, and therefore should be billed for 46MB extra bandwidth, right? But, the invoice shows different: White_ZA - mydomain.co.za (01/12/2009 - 31/12/2009) Total Bandwidth Usage = 246 MB - Overage Charge = 146 MB @ 0.2/MB This is clearly incorrect, and the invoice should have looked as follow: White_ZA - mydomain.co.za (01/12/2009 - 31/12/2009) Total Bandwidth Usage = 246 MB - Overage Charge = 46 MB @ 0.2/MB From here, I guess the script that calculates the bandwidth takes the initial limit from the package, and not from the actual limits reported in the client's account . 0 Quote Link to comment Share on other sites More sharing options...
headout Posted February 10, 2010 Share Posted February 10, 2010 We saw the same thing happening. Looks like a little bug in the overusage system? 0 Quote Link to comment Share on other sites More sharing options...
Troy Posted February 10, 2010 Share Posted February 10, 2010 If you only change the package in WHM, but don't have a separate package in WHMCS, since the soft limits are specified at the product level you'll have the same soft limits no matter what you do in WHM. If you are billing overusage, you shouldn't set any limits at all in WHM - give them unlimited and let WHMCS decide when to charge and how much. It makes your admin job easier too - no need to worry about changing quotas or bandwidth limitations in WHM. 0 Quote Link to comment Share on other sites More sharing options...
SilverNodashi Posted February 15, 2010 Author Share Posted February 15, 2010 Hi Troy, What are your saying is a bit "bogus", and won't work as you said. The client's package in this case has a 100MB limit, and the chose an addon option for another 100MB - so the additional 100MB isn't part of the package default. WHMCS does see that the client has used say 240MB of her 200MB bandwidth, but the over-usage billing doesn't see this. Setting the packages to unlimited in WHM is just plain stoopid and we'll loose out BIG TIME. P.S. Why was this thread marked as [NOT A BUG], when it clearly is a bug?????? 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted February 15, 2010 Share Posted February 15, 2010 P.S. Why was this thread marked as [NOT A BUG], when it clearly is a bug?????? I'd imagine because it works as intended (and as used by most of us) ? It compares the current usage to the package settings in *WHMCS* and charges accordingly, what you have you *WHM* settings as is irrelevant 0 Quote Link to comment Share on other sites More sharing options...
SilverNodashi Posted March 11, 2010 Author Share Posted March 11, 2010 Rob, I don't agree. Why is what is in WHM irrelevant? Does it not matter what WHM reports as actual bandwidth usage? And yes, you're right, it doesn't apply to unlimited bandwidth providers, so who cares right? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.