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?

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.  

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

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.