Hi All
We have had two clients so far report an issue when running the N/L Year End routine in Opera 3.
The situation is as follows:
They do not use Open Period Accounting and do not use Realtime Update either.
Their N/L Year End was 31/12/2020.
They have run the N/L Year End routine, which involved running the N/L Period End for Period 12 followed by the N/L Year End.
The N/L is now in Period 1 (January 2021).
The issue is that transactions dated prior to 01/01/2021 that had not yet (intentionally) been transferred to the N/L, have now automatically appeared in the N/L for Period 1.
When you view the journal it actually shows (RT) to indicate that it was transferred in Realtime (when the N/L Year End was run).
I.e. the transactions in SNOML and PNOML dated prior to 01/01/2021 have been automatically transferred into the N/L Period 1 as if Realtime postings was being used, when in fact it is not being used at all.
This has created a reconciliation issue for them, because the January transactions are still sitting in SNOML and PNOML waiting to be transferred as a batch, when they are ready, by running the N/L Utilities S/L and P/L transfers, and they are not happy that these older transactions were transferred automatically in this way.
It only does this at Year End, when the N/L Year End is run. During the year they do not get this issue at all when running a regular N/L Period End.
Has anyone else come across this anomoly?
Pegasus support say it is by design and refuse to consider it as a bug.
Thanks
