Share
Report
10I'm a relatively new user of Dynamics AX. We have a situation where a user is able to post to a module even though the Module Access level is set to 'None'.
Rather than set a Period Status to 'On hold' so no-one can post to a period, once we have completed a monthly reconciliation for a specific module we set the Module access level to 'None'. For example, when we complete the bank reconciliation on 1 Jan, we set the bank module access level for December to None. Similarly, once AP have entered all December invoices we set the Vendor access level to None. However, an AP clerk was able to enter a late invoice with a posting date of December and then create, post and print a cheque also dated December. My understanding is that no-one, not even a system admin, could post without changing the Module access level to something other than 'None'. We want to understand why this was able to be done and also how we can restrict it from happening in future, as once a period is considered to be closed we don't want to allow employees to create backdated transactions. Once all entries are complete for a period we do put the Period in 'On hold' status. If anyone is able to help with this, it would be appreciated.
All responses (
Answers (
