Re: [Emerald] Emerald.exe 2.5.322

Dale E. Reed Jr. ( (no email) )
Thu, 24 Feb 2000 15:49:38 -0800

PowerNet wrote:
> Why did Emerald try to bill 196 services in 2.5.322+ when in 300 it only should be invoicing about 20 services?
> "Its sorta covered here:
> v2.5.313 - 11/3/99
> * The batch criteria was checking the maExpireDate rather than the
> billed thru date to determine customers that needed to be billed
> for certain autobatch processed."
> We are using a manual list we check every day against the Emerald batch to make sure they match. It is correct with the 300 invoiced services but the 196 that v322+ wants to creat blows us away.
> Is there an SQL query I can run to get me the detail of what the 322+ (196 invoices) batch was doing so I can print it out and look at it before we create all these invoices and then have to go back and delete them if they are wrong?

What the note in changes.txt means is, that for those customers with
a blank/null expire date, 2.5.300 would not bill them. A blank
expire date typically means Balance forward, and you want the customer
to get another bill (unlike renewal), even if they don't pay their
last one (since thier account still works, if they don't have an
expire date).

Check to see what customers you have with a blank expire date. Those
are probably the ones you are missing.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list (including removal) go to: