Which action is not typically part of a Signatory's responsibilities?

• A. Creating new user accounts
• B. Approving transactions
• C. Denying transactions with comments
• D. Recycling transactions

Answer: (A)

The action being tested is the distribution of responsibilities in a workflow that involves reviewing and approving transactions. A Signatory’s role centers on evaluating a request, deciding whether it meets the criteria, and then either approving it or denying it with a justification so there is a clear audit trail. They may also trigger a recycle when a transaction needs to be reprocessed or reworked. Creating new user accounts, however, falls under identity and access management. It’s about provisioning access, assigning roles, and onboarding users—tasks that belong in IT or security rather than in someone who approves or denies individual transactions. Keeping these duties separate supports security and proper oversight, which is why creating new user accounts is not typically part of a Signatory’s responsibilities.