|
|
 |  |
Re: Usage billingFrom: Alan Williamson Date: Tuesday, February 3, 2004
Time: 5:22:26 amHi Shawn,
On Tue, 03 Feb 2004 01:04:47 -0800, Shawn Hogan wrote:
>The "delay" setting applies to usage that is automatically added=
to the
>customer's generated invoice. =A0Although, I changed it so it=
applies to the
>manual usage billing as well (for 3.3.2).
Cool; thanks.
>>So... What I need is to be able to generate usage-only invoices=
mid-
>>month, after I've done my regular invoicing (which will include=
excess charges
>>as applicable for some customers). =A0At the moment, I have no=
automated way
>>of doing that because the list on offer includes current month=
charges that
>>shouldn't be billed. =A0Ideally, we would generate usage-only=
invoices
>>only for amounts above the $20 threshold, but I'm guessing the=
chances of this
>>aren't good. =A0(We'll have to settle for putting up with=
customers who ignore
>>the "If the balance due is less than $20, please don't pay now"=
notes I guess
>>...)
>
>Well, instead of doing it based on a dollar amount, why not=
raise their
>allowed limit?
I understand what you're thinking, but in reality it doesn't=
matter where we set the limit. A percentage of customers will=
always go over it, and most often by fairly insignificant=
amounts. If we write those amounts off (using "omit"), they'll=
soon learn that we do it and eventually they'll push it too far.=
(We already have three different plans/limits for one type of=
product, and we see over-usage every month at every level).
(Customers follow Boyle's Law for Gases: they instantly use all=
of the available capacity you give them. Unlike gas though, they=
don't know when to stop.)
Here's an idea I was thinking of that I hope you like. I think=
it would be great, giving us the flexibility we'd like with=
minimal manual work.
The idea involves two steps to the process of billing excess=
usage, using Pending Charges as a sort of "preview". Here's how=
I picture it.
Part 1 of the process involves a monthly function (could be=
launched by the auto-tasks workstation maybe, or from the GUI)=
that bills the excess usage charges (for completed months in our=
case) as pending charges. It doesn't raise invoices, but it=
does turn the excess usage amounts into dollar amounts. This=
has the advantage that excess usage is charged at the then=
current rate, which is great if you change rates down the track=
and have old charges at old rates that haven't been invoiced.
Part 2 of the process would be a new function which would enhance=
the abilities of pending charges in the process. Simply, a=
function like "Generate Invoices" (or maybe becoming part of=
that) which checks on pending charges not yet billed, shows a $=
total for each customer and has an "Omit" button (like generate=
invoices). Think of it like a preview mode for invoicing=
pending charges.
A system like this would be ideal for us, and I think it would=
add value to "Pending charges" too. I also suspect it wouldn't=
be as much work as it first appears based on my limited=
understanding of filemaker intricacies.
I guess I'll leave this thought with you. I'd love to see it, I=
think others would also, but it's your code. I do appreciate=
the change you've already made though.
Regards,
Alan Williamson
Virtual Access
Web: www.virtual.net.au
---------------------------------------------------
To subscribe, unsubscribe or to search list archive
please visit http://www.optigold.com/lists/isp.html
---------------------------------------------------
|

Return to Digital Point Solutions' Home Page |