I think this may be a bug in the system so I wanted to throw it out there in case anyone ever runs across it. We have had it happen to a client twice and I finally figured out what it is.
The transaction itself will be set to a certain period, but the detail lines of the transaction get posted to a different period.
How I have seen this happen:
- The client has “Restrict Access to Closed Periods” selected
- The previous periods are closed
- Client enters a transaction for a previous period and gets the warning message
- In our case, they were fixing a transaction so they reversed a transaction
- We go in and Uncheck “Restrict Access to Closed Periods” and open the periods
- The client posts the transaction they created
We realized there was an issue when they ran financials and the changes were not appearing in the historical month and instead appeared in the first open period. I went back to the transaction. The Date, and Period ID were set correctly. In the Details section, I added the Period ID column and there was the problem.
Funny enough, when I go to reverse the transaction to correct it, it changes the periods IDs at the detail level to match the header transaction date. I could have just changed the date, but I’m not one of those people. For the reverse to work, I had to check “restrict access to closed periods” and close the periods, then reverse the transaction, uncheck the setting and open the periods back.
