There are several policies and entitlements that need to be configured to achieve the specific transaction behavior for open banking transaction draft approvals, including the Open Banking policy settings (set in Q2 Console or Q2central), the Open Banking allowed actions (set in Q2 Console or Q2central), and the allowed actions set in the Customer policy (set in the Company Policy page within Q2 digital banking/UUX). For more information on changing these setting, see Setting up a Customer.
Because the Open Banking policy is evaluated independently of the Customer policy in UUX, both sets of policies and allowed actions must be taken in account when setting up a customer to use the Direct Payables service. This policy structure is necessary to allow for the use case where a customer does not want to have any secondary approval(s) performed on Open Banking transactions.
Refer to Setting up customers for specific approval scenarios for more information on the specific settings to use to achieve the setup your customer requires.
At the time of transaction file submission, the Open Banking policy is evaluated for allowed actions (including approvals), but the Group policy is evaluated to determine aggregate transaction limits.
|
Desired results |
Open Banking Policy settings for the User |
Open Banking Policy Allowed Actions Approvals settings |
Customer Policy Allowed Actions settings |
Details |
|---|---|---|---|---|
|
Transactions are imported into UUX with a processed status, with no approval required in digital banking |
Draft and Approve |
One approver |
Does not apply. |
The Customer policy is not evaluated for these transactions because no digital banking login occurs. |
|
Transactions are drafted, and a single approval is required from a logged in user in digital banking |
Draft and Approve |
Two approvers |
Set one approver in the Allowed Actions within the Customer Policy. |
The initial Direct Payables transaction submission is the first approval (because the user is enabled to Approve transactions), and then the transaction comes in as drafted and ready for a second approval from a logged-in digital banking user. |
|
Transactions are drafted, and a single approval is required from a logged in user in digital banking |
Draft only |
One approver |
Set one approver in the Allowed Actions within the Customer Policy. |
The initial Direct Payables transaction submission is not approved (because the user does not have Approve enabled in their Open Banking Policy settings), so the transaction requires a single approval from a logged-in digital banking user. |
|
Transactions are drafted, and two or more approvals are required from logged in users in digital banking |
Draft and Approve |
Two or more approvers |
Set two or more approvers in the Allowed Actions within the Customer Policy. |
The initial Direct Payables transaction submission is the first approval (because the user is enabled to Approve transactions), and then the transaction comes in as drafted and ready for additional approvals from two or more logged-in digital banking users. |
|
Transactions are drafted, and two or more approvals are required from logged in users in digital banking |
Draft only |
Two or more approvers |
Set two or more approvers in the Allowed Actions within the Customer Policy. |
The initial Direct Payables transaction submission is not approved (because the user does not have Approve enabled in their Open Banking Policy settings), so the transaction requires additional approvals from two or more logged-in digital banking users. |