ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> AR aging for one customer
http://www.istechforum.com/YaBB.pl?num=1260469732

Message started by cathyh on 12/10/09 at 11:28:52

Title: AR aging for one customer
Post by cathyh on 12/10/09 at 11:28:52

I have just been informed by my AR person that when she puts a single customer in the customer range, all the aging periods are zeroed out. I did a little experimenting and if I put in a range, even just to the next customer this does not happen. But a single customer zeros the periods and all transactions end up in the last column. We can manually add the periods back in and the report is fine.
Maybe this is fixed in the latest update?

Title: Re: AR aging for one customer
Post by dameng on 12/10/09 at 13:00:40

It is performing fine as of the 9/16/09 sp5.

Title: Re: AR aging for one customer
Post by cathyh on 12/16/09 at 14:31:03

Was this a problem before the 9/16 update? We are still on the May update, but don't remember this happening until very recently.

I forgot to mention-- the zeroed aging periods seem to happen only with those people who have certain terms (a couple of different prepaid terms) and if the terms are Net 30 the periods just go to 0,30,60,90 instead of 0,31,61,91.

Title: Re: AR aging for one customer
Post by cathyh on 12/17/09 at 16:00:53

I added the SP5 patch to my stand-alone and the AR aging acts the same there as my live company with the May update. Customer with Net 30 changed from 0,31,61,91,121 to 0,30,60,.90,120 and customer with PPD terms (changed after the customer who was net 30 did not pay) changes to all zeros.
It seems to be linked to the terms.....

Title: Re: AR aging for one customer
Post by dameng on 12/17/09 at 16:12:03

from your initial description, i thought you were relating that AR-F was changing from 0,30,60,90,120 to 0,0,0,0,0.

i have confirmed that if you have your A/R default aging periods set to 0,31,61,91,121 and you select a single customer that has a net 30 term it does indeed change the aging periods on AR-F to 0,30,60,120.
if i select all customers, then the aging remains as the default of 0,31,61,91,121.

that is a problem the programmer is going to have to fix. i don't know when this started happening. but you are right, it's the terms that are changing the values in AR-F

Title: Re: AR aging for one customer
Post by cathyh on 12/18/09 at 08:51:58

Initially we thought that the change for a single customer was zeroing out all periods because we were running only customers that had late balances and the terms had been changed (for future orders) to one of our two prepaid terms. When I ran a customer with net 30 terms I discovered that those periods changed also, but with the 0,30,60,90,120 numbers. That's when I figured out that the change was driven by the terms.

Thanks for confirming-- at least I know it's not just our data!

Title: Re: AR aging for one customer
Post by Lynn_Pantic on 12/21/09 at 18:58:13

If you run an aging for one customer, it sets the periods to a multiple of the Days Until Due on the customer default terms unless you change it. Multiple customers, it uses the default as seen on the AR-F screen. If a customer default terms has Days until due=0, it should use the master setting. I will pass on to programming.