RE: [Emerald] 4.5.2 Feature Request

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

This won't work for me because you have told me to create invoices, then =
statements, then batch the Credit Cards. By this time, it is too late =
as the payments have already been applied to the statements. I need =
something for AFTER that will void the transaction in the customers =
history so I can make it match the void I had to do with Authorize.net. =
Our accountant doesn't want to see a credit card payment remaining in a =
customers account that hasn't been properly credited, and we cannot do =
that in Emerald. Once that incorrect payment amount has been applied, =
it will stay there forever! We need a way to void that payment just as =
we can void an invoice. Surely it can't be THAT hard to do. If =
Quickbooks can do it, you can do it too Dale:)))

marti

-----Original Message-----
From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
Sent: Thursday, September 12, 2002 12:40 PM
To: emerald@iea-software.com
Subject: RE: [Emerald] 4.5.2 Feature Request

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

As long as the payment hasn't been rolled up into a statement,
go to the customer's history screen, click the payment ID and
you can edit/delete the payment.

Note, Emerald 4.5.1 doesn't update the current balance DISPLAY
correctly when doing this. Don't panic or try to make the
current balance display correct. The statement processing=20
WILL come out fine with respect to your payment edit/delete.
The current balance display on the MBR is just a running
summary of changes to the account since the last statement
balance. It is NOT used for statement creation.
=20
> Marti
>=20
> -----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
>=20
>=20
> Void payments is already in 4.5.1.....
>=20
>=20
>=20
> > -----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
>=20
> ------------
>=20
> This is a user supported list. If you require assistance from IEA=20
> Software's
> Support Engineers, please check out our Support resources at
> http://www.iea-software.com/support.
>=20
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
> ------------
>=20
> This is a user supported list. If you require assistance from IEA=20
> Software's
> Support Engineers, please check out our Support resources at
> http://www.iea-software.com/support.
>=20
> For more information about this list (including removal) go 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