No, if the Administrator assigns a Bank role to Group Corporate, all the entitlements available in the selected roles will be assigned at Group Corporate level. Any modification required in the bank roles can be done using Role transaction mapping screen. If in future bank assigns a new transaction access in the bank role (from Role transaction mapping screen), it will automatically be given to the all the Group Corporates having that roles mapped

No. Administrator can select and assign the roles available at enterprise level as is, or he can create a custom role as per his requirement for the Group corporate by cloning a role available at Group Corporate level.

Admin will be able to assign a mix of bank roles and custom roles to a Group Corporate.

No, The Customize bank role will be available only for the Group Corporate for which it was created. Any changes done in the bank roles, from which this custom role has been created, will not have any impact on the custom created roles

Under Sequential approval flow, the approval can be done only in the sequence as mentioned in approval workflow. It is “Non-Sequential” type of approval flow, which does not follow any specific sequence. Any user (who is part of the approval flow) from any approval level can pick up the transaction/maintenance and approve it. This will be applicable across Group Corporate

Approval Currency is the preferred currency for setting up the approval rules.

During Group Corporate Profiling setup, the user has an option to select the workflow preference at Corporate Level or Rule Level. If Corporate Level is specified, then the approval flow (Sequential/Parallel/No Approval) can be captured on the same screen. If Rule Level is selected, then the approval flow (Sequential/Parallel) must be specified during rule creation.

Yes. For the Group Corporate, the party account access setup must be done before the user level mapping of accounts and transactions

Transaction groups are for the purpose of grouping transactions and maintaining access in Account Access screens.

There will be one factory shipped Transaction group for each module, which will have all transactions and inquiries grouped together. Factory shipped user group cannot be deleted or modified.

A new group can also be created by cloning/copying an existing transaction group. Deletion of custom transaction group will be allowed.

Transaction groups of one Group Corporate will be available for selection only for that Group Corporate

Yes, All the party ID mapped under Group Corporate will be listed in the dropdown. Admin can select one party at a time and setup the party account access for the same .Once he is done he can follow the same flow by selecting another party for Account maintenance before final submission.

OR

He can save the application in draft for further modification.

This feature allows the administrator to configure access policies for accounts and associated transactions, which may get added subsequently in the future.

Auto: Gives access to the newly added accounts and transactions of the party as soon as the account is opened. This option can be selected whenever bank administrator wishes to provide access by default

Manual: Denies the newly added accounts and transactions by default. This is to ensure that access to accounts and transactions is provided only upon receiving specific instructions from corporates

Yes. Deletion of account access for a party will lead to automatic deletion of access for the users of that party.

System administrator bank administrator and Corpprate administrators can create or edit the users.

Yes. An option to create a new user from by copying an existing user is provided.

If ‘Copy’ is selected, admin will be able to select an already created user (user created under the same Group Corporate) and screen will be displayed the copied data for all the sections except Personal and Contact information. Admin will be require to fill Personal and Contact information and he can make the changes in the copied data as well.

Yes, multiple Application roles can be assigned to the user. All the Roles (both Enterprise and Customer) mapped at the Group Corporate level will be available for selection while setting up the user management.

Corporate users at Group Corporate level will have one primary party and multiple assessable parties for each entity. Show primary party selected on the top will by default as selected under Primary Party for that Entity.

Yes, new limit package can be mapped to a user. Limits get applied from an immediate effect if the effective date is less than or equal to current date. And if the effective date is future date, the limit package will be applied from the date available in the package.

Corporate Administrator will be able to assign the limit packages created by any corporate administrators under the mapped GCIF. Corporate Administartor, will not be allowed to access the packages created by the Bank Administrator.

In case of any update of child roles mapped to the user as edit user functionality, the privileges associated with new child roles get applied to the user with an immediate effect.

So if any transaction is pending with approver for approval, user can view and approve those transactions only if checker role is mapped to him. As soon as checker role is unmapped, then user will not be able to view and approve the transactions which were pending for his approval.

No, user selection is not dependent on the parent corporate party. Application will list down the entire user associated with group corporate for user group creation irrespective of parent party.

Yes, same user can be part of multiple user groups under group corporate. Whereas, User Group would be allowed to create even without adding a single user.

No, user groups cannot be deleted but can be edited. Administrator can add new users and remove existing users of the user group.

Yes, All the party ID mapped under Group Corporate and associated with corporate user will be listed in the dropdown. Admin can select one party at a time and setup the user account access for the same .Once he is done he can follow the same flow by selecting another party for user Account maintenance before final submission.

OR

He can save the application in draft for further modification.

Yes, deletion of account access for a party will lead to automatic deletion of access for the users of that party.

Yes, access removal at party level for an account and/or transaction will automatically remove access at user level of the selected party.

There is a possibility that the maintenance is saved but the status is ‘Pending Approval’. For the maintenance, if there is an approval required then the changes will reflect only once the approver(s) approve the submitted request. If the setup does not require an approval workflow or is self / auto approved, then the same will reflect immediately.

The user report mapping maintenance allows the Corporate Administrators to map the report or set of reports to a specific corporate user. The corporate users can generate and view the reports to which they have an access.

No, user selection is not depend upon the parent corporate party. Application will list down the entire user associated with group corporate for user report mapping irrespective of parent party.

No, user selection is not dependent upon the parent corporate party. Application will list down the entire user associated with group corporate for workflow maintenance irrespective of parent party.

Approval workflows are created to support requirements where multiple levels of approval are required in a specific sequence for a transaction/maintenance. Each workflow can be configured to have up to five levels of approval with a specific user or a user group configured at each level.

Administrator can set up minimum one and maximum five levels of approvals as a part of approval workflow, however this can be configured as a Day 0 set up. .

Yes, list of the users associated with a group can be viewed using workflow management screen.

No, user selection is not dependent upon the parent corporate party. Application will list down the entire user associated with group corporate for approval -rules maintenance irrespective of parent party.

Administrator can set up minimum one and maximum five levels of approvals as a part of approval workflow. Whereas, maximum levels of approvals that the user can set is configurable as Day0.

If the rule is not maintained in specific currency, then the application will check the preferred currency selected while setting up the group corporate.