Andrew:
I zipped the files and they are on their way to you.
Thank you.

No sign of them so far.

Hi Andrew:
Has there been a resolution to this issue? I'm going to visit a client this week where February 29 reporting will be involved.

Well, I got the data and hour or so ago, but Feb 29 was this company's year end and so the AR posting journal I need is not available. I'm waiting to see whether it can be provided.

There was a reason for the posting in the Adagio Notes about avoiding having February 29th as a business day. Has your client said there is a problem at their site?

Andrew:
Not at all. I just want to be prepared so I know what to consider in case of a discrepancy.

OK. The normal rules for tracking down a discrepancy prevail until something else raises its head.

OK. There's a problem with this report if it is backdated to February 29. With Sam's data, the general ledger value is correct, but the total at the bottom of the AR ATB is incorrect.

I've asked R&D to investigate the problem.

To close this thread...

As far as we can determine, this data had a Period End run on March 6, and then a Year End dated February 29. This meant that transactions are in history that would not have been moved if the Period End had been run on February 29.

This report uses the Last Period End date in the company profile to determine whether the report being requested is back dated or not. Since the Year End date matches the Report date, the transactions in history are not being inspected (and are therefore missed in the report).

If it is critical to get an ATB to tie back to Ledger, then you can change the Last Period End date in the AR company profile using GridView Read-Write, or run a Period End dated March 1. Both of these actions will cause the ATB report to inspect the transactions that have been moved to History.

As mentioned previously, all the accounting entries are correct, and it turned out that this had nothing to do with the February 29th date. It would happen regardless of the number of days in the month.

Andrew:
As you suggested, running a Period-End for March 1, 2012 does reset the ATB back to the correct values for a report as at Feb 29 (although I am not sure why).

I was unaware that the data had a Period-End performed on a date later than the Year-End date. (I am going to guess that this was done unintentionally by one of the users.)

I have to recommend you for delving into this matter, and for your detective work on this matter. Thank you for your assistance!