Message-ID: <008101c3ce1d$65db4c30$05ae90c6@webadmin> From: "Billy Huddleston" <billy@nxs.net> Subject: Re: [Emerald] Emerald 4.5.6 + Statement creation Date: Mon, 29 Dec 2003 10:06:55 -0500
I've ran the global error report, and it says I have 1,087 Cards awaiting CC
response for more than 15 days.. How do I fix this? I suspect most of
these are from the old 2.5 upgrade... but, can't be for sure.. Please help
me get this cleared up so my accounting department doesn't kill me..
Thanks, Billy
----- Original Message -----
From: "Peter Deacon" <peterd@iea-software.com>
To: "Emerald List" <emerald@iea-software.com>
Sent: Wednesday, December 24, 2003 2:31 PM
Subject: [Emerald] Emerald 4.5.6 + Statement creation
> In Emerald 4.5.6 we made some improvements as to 'when' a statement is
> created. The two main senarios we want to avoid is the possibility of
> double billing credit card customers and statements that do not reflect
> current activity.
>
> Double billing of credit card/EFT customers can happen if there are
> pending card transactions waiting to be exported or imported. Since new
> automatic card payments are based on the statements ending balance these
> pending payments will not be reflected in the new statement or
> subsequent card payment and have almost always lead to the double billing
> of customers.
>
> To counter this Emerald 4.5.6 holds off on new statement creation for a
> customer until all pending card transactions for that customer have been
> processed. We have seen instances with some customers where throughtout
> time for whatever reason -- not all exported transactions have had results
> imported for them. For these customers a new statement is not generated.
> *All outstanding card transactions must be imported or voided*.
>
> Emerald 4.5.6's new global error report provides a count of all CC and EFT
> transactions that have been outstanding for more than 15 days.
>
>
> The second senario is one of the best timing for new statement creation.
>
> Generally you don't want to create monthly statements that show just a
> previous payment and the next day have a recurring invoice created that
> does not appear on a statement for another 29 days.. Had the statement
> been created a day later this problem would not occur. Similiar
> situations were caused by accidently running statements before invoices.
>
> Now Emerald looks into the future before deciding to create statements
> *when there are no unapplied invoices avaliable*. If Emerald sees a new
> invoice will be created within the next 15 days it will hold off on the
> new statement until that time. This may initially cause some accounts
> to have statements generated a little later than ususal.
>
> We've made additional corrections specifically for statement creation
> outligned in the Emerald change history for 4.5.7 (See
> http://www.iea-software.com/docs)
>
> The update is avaliable here as an sql script that can be run against your
> existing Emerald 4.5.6 database.
> ftp://ftp.iea-software.com/emeraldv4/sql/emer456_batchstatements.sql
>
> If you need further assistance feel free to contact our support
> department, if you currently do not have a contract our sales group can
> help you choose the right contract or per incident options.
>
> Happy Holidays,
> Peter
>