
This is the second client I have run into with this issue. They run an Account Transactions Report and they get erroneous information back. In both cases they were using Intercompany and they will get an account that when they drill back isn't on the journal entry at all. What I found in both cases is that these were intercompany accounts. And if you look at the other company and the account index on the account (other company), then look at the company they are reporting on and look are the erroneous account they have the same account index. Why in the company they are running the data on, is it reporting the inner company account at all. And has Microsoft come out with a fix for this. Customer is running 2016.00.0620. Has anyone seen a fix for this yet.
*This post is locked for comments
I have the same question (0)