RE: SL 2011 Period Sensitive Aged A/R Inaccurate
Anita,
Your assumption the March invoices should not be showing on a February period sensitive aging report is correct. Without seeing the actual documents I cannot say for certain but I suspect there is some sort of mix up with the perpost, perent, perclosed values on the documents in question.
In order for the period sensitive aging report to work retrospectively it has to calculate the document balance for the period in question. ARDoc only carries the original document balance and the current balance. It does not have fields for the document balance each month. Therefore, it has to look at ARAdjust (the table that records the application of payments and credit memos) to invoices and debit memos) and adjust to the document balance as of the period you specified. In looking at ARAdjust, it looks at when the payment or credit memo was applied (posting period wise) to add back to the documents current balance. The logic works quite well for invoices and debit memos but not always so good for payments and credit memos that have an open balance for the period of the report but have been subsequently applied.
You did not indicate whether the documents show in February were debits (invoices and debit memos) or credits (payments and credit memos) so the possible explaining as to what you are seeing would be different for the two classes of documents.
What I suspect you have going on is that you have documents posted to a future period (relative to whatever current period AR is in) that is contributing to your issue. SL allows you to do things like this but it means you need to be watchful as to the posting period of the documents when creating the batch. You indicated that February is closed but, in SL, closing is a "soft close" not a "hard close". Closing really only makes the incoming AR period the default period. Your setting in GL as to whether you allow posting to a prior period sort of sets a hard close.