RE: [Emerald] 4.5.2 Feature Request

Marti Preuss ( (no email) )
Thu, 12 Sep 2002 12:01:09 -0500

So, How and where do I find that, and how do I do it?

Marti

-----Original Message-----
From: Ronnie Franklin [mailto:ronnie@itexas.net]
Sent: Thursday, September 12, 2002 11:50 AM
To: emerald@iea-software.com
Subject: RE: [Emerald] 4.5.2 Feature Request

Void payments is already in 4.5.1.....

> -----Original Message-----
> From: emerald-request@iea-software.com=20
> [mailto:emerald-request@iea-software.com] On Behalf Of Marti Preuss
> Sent: Thursday, September 12, 2002 11:44 AM
> To: emerald@iea-software.com
> Subject: RE: [Emerald] 4.5.2 Feature Request
>=20
>=20
> Another thing you can work on Dale, is a way to prevent an=20
> accidental 'double click' when one sends out an individual=20
> Credit Card payment. We have a couple of sales personnel who=20
> always tap twice and if I don't catch it and void the=20
> transaction with the Merchant, I find myself having to credit=20
> back the cards. Somehow, Emerald needs to recognize that a=20
> card transaction is going out twice, often within just=20
> seconds of each other.
>=20
> It would also be VERY nice if we were able to 'void' a=20
> payment entered incorrectly, or when the above happens and a=20
> card is tapped twice without having to enter an 'adjustment'=20
> to void out the second payment in the customers payment=20
> history. If we were able to 'void' an accidental payment,=20
> then it wouldn't show up on the Daily Payment report as it=20
> does now, or on the customers Billing Statement.
>=20
> Any thoughts here?????
>=20
> Marti
> Net Star Telecommunications
>=20
> -----Original Message-----
> From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
> Sent: Thursday, September 12, 2002 11:35 AM
> To: emerald@iea-software.com
> Subject: RE: [Emerald] 4.5.2 Feature Request
>=20
>=20
> > If it helps to know he isn't alone. I agree with 1,2 & 3=20
> and #2 would=20
> > be huge for us.
>=20
> 1 and 3 should be in 4.5.2. We're working on some additional=20
> parts of the CC batch (ie, automatically declining expired=20
> dates and notification to users of upcoming expirations on=20
> their Cards), but I doubt its going to make it into 4.5.2=20
> (little more involved than the rest). We are working on=20
> them, though. :)
>=20
> Dale
>=20
> ------------
>=20
> This is a user supported list. If you require assistance from=20
> IEA Software's Support Engineers, please check out our=20
> Support resources at http://www.iea-software.com/support.
>=20
> For more information about this list (including removal) go=20
> to: http://www.iea-software.com/support/maillists/liststart
> ------------
>=20
> This is a user supported list. If you require assistance from=20
> IEA Software's Support Engineers, please check out our=20
> Support resources at http://www.iea-software.com/support.
>=20
> For more information about this list (including removal) go=20
> to: http://www.iea-software.com/support/maillists/liststart
>=20

------------

This is a user supported list. If you require assistance from IEA =
Software's
Support Engineers, please check out our Support resources at
http://www.iea-software.com/support.

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
------------

This is a user supported list. If you require assistance from IEA Software's
Support Engineers, please check out our Support resources at
http://www.iea-software.com/support.

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart