if i give the team access to bulk approve journal entries does that mean i can approve my own journal? what segregation exists to ensure i cant

AI generated answer (using internal Slack threads):

Based on the conversations, it appears that if you give the team access to bulk approve journal entries, there is a possibility that a user could approve their own journal entries. This is because the bulk approval page might not respect the same segregation rules as individual approval workflows. However, there are several ways to ensure segregation and prevent a user from approving their own journal entries: 1. After Submit Workflow: You could create an After Submit workflow that gets triggered after the Approve Journals page is submitted. This workflow could check if the Current User is the same as the Created By user for the journal entry, and if so, it would not approve the entry. 2. Custom Approval Field: You could add a custom accounting approval field (list type = employee) in the employee record and use this value to route the approval to a designated person, as long as this designated person is not the same as the one who created the journal entry. 3. Supervisor Approval: You could use the employee's supervisor as the approver in the workflow. 4. Segregation of Duties (SOD) Based Role: You could use a different SOD based role than the JE creator to route approval. 5. Locking Approved JEs: You could lock approved journal entries to prevent them from being edited without approval. This could be done with a button on the locked, approved JE to ‘unlock’ which then allows the user to edit and then on save kicks it back into approval flow. Remember, these are just suggestions based on the conversations and you might need to adjust them to fit your specific needs and workflows. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******