RE: [Emerald] Payments

New Message Reply Date view Thread view Subject view Author view
Joe Reynolds (joe@outdoors.net)
Thu, 7 Nov 2002 09:25:35 -0500



From: "Joe Reynolds" <joe@outdoors.net>
Subject: RE: [Emerald] Payments
Date: Thu, 7 Nov 2002 09:25:35 -0500
Message-ID: <BDEPKHFAFGIMOEFNADFIEEDIDBAA.joe@outdoors.net>

>>>Do you have the ability to call a DLL API rather than adding
the payment to the DB directly? If you do, then you can use the Payment API and not have to worry about this stuff.<<<<<

Our custom entry program is written in Visual Basic dotNet. If you have some piece of code that would do what you suggest above it would be much appreciated.

-----Original Message----- From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com]On Behalf Of Dale E. Reed Jr. Sent: Wednesday, November 06, 2002 6:03 PM To: emerald@iea-software.com Subject: RE: [Emerald] Payments

> After a payment of 79.95 was added to payment table by custom program, the
> numbers/dates above remained the same.

And they will. :)

> Am I correct in assuming that a statement will be created at some
> point that
> will zero out the numbers and advance the expire date? Reason I
> ask is that
> a preview batch report for Statements does not create a new statement for
> this user.

Yes. After the next invoice/statement is created for the customer, the dates will advance. However, this is NOT the typical behavior and only done because you are not using Emerald to make the payment. Using Emerald to make the payment would advance the dates and numbers for you. As a side note, you should also update PendingCredits if you want the Current Balance to reflect the payment.

> At this point, even though the member record shows a payment of
> 79.95 AFTER
> the Statement of 79.95, it looks like Emerald will need to create another
> statement to bring the account into balance.

Which is the expected behavior for what you are trying to do. If you used Emerald to make the payment, that would be an issue. Do you have the ability to call a DLL API rather than adding the payment to the DB directly? If you do, then you can use the Payment API and not have to worry about this stuff.

Dale

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

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



New Message Reply Date view Thread view Subject view Author view
This archive was generated on Thu Nov 07 2002 - 06:11:23 Pacific Standard Time