Re: [Emerald] Emerald doesn't calculate past 2 decimals when using "invoice next term"

Josh Hillman ( (no email) )
Tue, 3 Oct 2000 13:17:11 -0400

From: "Nelson Valverde" <>
> > Emerald 2.5.339 seems to have a problem calculating invoices past 2
> decimal
> > places when using "invoice next term."
> And where did you get 339? The Emerald ftp site only has 337.
> I would like to try it out also ;-)

IEA Support sent it to me. I've been going back and forth with them on
various issues for quite a long time, so they sent me that one recently (as
well as others in the past). I don't know if there's a specific reason why
2.5.339 is not on the FTP site. Maybe they're going to skip over it and put
a newer one up there soon??


Emerald 2.5 Updates and Changes

v2.5.339 - 9/15/00

* The PC Transact_IT format was changed to a generic CSV batch out
of Emerald, and not includes batch in support. You will need to
obtain the definition file and re-configure the out file for this
to work.

* Printing the radlogs report with a Database not named Emerald would
display an error (new ralogs.rpt). (RQST00000008826)

* Line items totals which included a tax in the emailed invoices were
not displayed correctly, although the invoice total was correct.

* If you have Restrict client reports enabled, the auto-batch could
not find the global reports.

* Adding or changing the home directory of an existing service will
now cause Emerald to create the new directory. (RQST00000008862)

* Customers who had an unapplied charge could cause the SQL connections
to block each other and hang the invoice creation. (RQST00000008834,

* Deleting an operator in the Emerald Admin required hitting delete
twice. (RQST00000008732)

* Added Support for X-Stop Class definition in the Emerald Admin.

* Taxes with an accumulative floor definition where not being cleared
between customers. Floor definitions were not tracking per month
correctly (ie, monthly floor, not pay period floor).
(RQST00000008655, RQST00000008705)

* Taxes for charges are not calculated until applied to an invoice,
to allow for accumulative floor definitions to turn our correctly
for pro-rate and setup charges. (RQST00000008655, RQST00000008705)

* The billing engine now uses a blocking SQL connection when creating
invoices. This can cause a slight pause in the display update, but
offers a 50 times performance advtange with the DB-lib interface.

* Added support for Telecheck EFT batch out.

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