Enha Security Settings for Transaction Approvals - To provide a workflow similar to A/P to other types of transactions
I believe there should be more workflow settings for approvals to enhance the security and internal controls system-wide. Whether it is a General Ledger Batch, Cash Receipt Batch or Payment Window Batch, [etc.] one user [at a lower security setting] should be responsible for inputting the data and another user for approving the transactions. We use this process now via Adobe files, but it would be nice if different versions of a transaction were documented at that status level by the user who inputted it versus the user that approved it.
Security allows for the ability to input and not update a batch.
Sherrie Leverett commented
I would like to see this for Budget Preparation as well. Departmental user needs access to requested level of budget only. The recommended and adopted columns should be under the control of management.