>>Hi Stephen,
>>
>>>Don't you have to tie payments against / to an invoice or scheduled payment?
>>
>>I think I see where Peter is coming from on this issue. I had a similar application at one point with an insurance company. They wanted premiums applied to the earliest due and could have cared less what the payment was ostensibly for.
>
>
>It can get more complicated than this. In my aging routine, I have to apply payments first to finance charges (in date order), then penalties, then invoice amounts. I read all of the open items into an array and make multiple passes through. I also keep a CLOSED DATE in the item record that shows exactly when it was paid.
>
>Peter Robinson

Are all payments due on a monthly basis, or can the client be setup on any type of schedule?

I have a used car lot appliction that does much the same thing. What accounts are late and how much do they owe. I don't create an aging because my customer base has never asked for it. All I could see is that they are overloaded with data on a bad account. Money in multiple buckets + fines.

I give a # of outstanding payments, $ of fines, total due to become current. Oh yes I also print out the excuse file so the collections department can keep up to date on the accounts.

I do have to do alot of the # crunching that you are doing though! P & I, grace period dates, selling accounts to 3rd parties.

__Stephen