Preview Confirmation Details

Introduction

The details of LC transfer are summarised and presented for user confirmation. The corporate user has to select the appropriate rule and authenticate LC issuance as per bank’s approval policies configured by Admin.

Navigation

Click the Continue button in the Request LC Transfer screen, after completing data entry.
The Preview Confirmation Details is displayed.

What you can do

The table below provides a brief description of the data that should be entered on the screen and the functions you can perform:

Field

Description

APPROVER DETAILS

Note:

All fields in this are display fields.

Select

The approval rule selected by the initiator.

Rule ID

The rule ID of the selected approval rule.

Authority

The approving authorities as per a particular rule.

Follow Hierarchy

Whether the rule follows hierarchy or not.

Incase of non-hierarchical workflow rules the Corporate User can send the transaction to any user or role in the workflow rule. Also any corporate user or role in non-hierarchical workflow rule will be able to initiate the transaction and send it for approval.

For hierarchical workflow rules, the approval process will be as per the set hierarchy.

Select User

The corporate user can select the approver to whom the transaction has to be sent for approval. The Lookup button displays the user details like user ID, name, his role and whether he is available for approving or out of office.

Remark

Provide remarks for confirmation of the payment batch.

CONFIRMATION DETAILS

User ID

The user ID of the administrator making the changes.

Transaction Password

For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.

Note:

The administrator has to choose any of the given security modes, as per process followed in bank.

Secure Token Passcode

For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.

SMS based Mobi Token

For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.

Device based Mobil Token

For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.

Digital Signature needed during initiation

For authenticating the changes done to the user record regarding enable or disable of signon or transaction.

Click

Submit

Submit the LC transfer request with the above details after authorization. A reference number is generated on successful Submit. If further corporate approval is required the request is routed as per workflow approval of the corporate.

Back

Go back to previous screen.

Field	Description
APPROVER DETAILS Note: All fields in this are display fields.
Select	The approval rule selected by the initiator.
Rule ID	The rule ID of the selected approval rule.
Authority	The approving authorities as per a particular rule.
Follow Hierarchy	Whether the rule follows hierarchy or not. Incase of non-hierarchical workflow rules the Corporate User can send the transaction to any user or role in the workflow rule. Also any corporate user or role in non-hierarchical workflow rule will be able to initiate the transaction and send it for approval. For hierarchical workflow rules, the approval process will be as per the set hierarchy.
Select User	The corporate user can select the approver to whom the transaction has to be sent for approval. The Lookup button displays the user details like user ID, name, his role and whether he is available for approving or out of office.
Remark	Provide remarks for confirmation of the payment batch.
CONFIRMATION DETAILS
User ID	The user ID of the administrator making the changes.
Transaction Password	For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.
Note: The administrator has to choose any of the given security modes, as per process followed in bank.
Secure Token Passcode	For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.
SMS based Mobi Token	For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.
Device based Mobil Token	For authenticating the changes done to the user record regarding enable or disable of sign on or transaction.
Digital Signature needed during initiation	For authenticating the changes done to the user record regarding enable or disable of signon or transaction.