- Guarantee/SBLC Advise Amendment Beneficiary Consent User Guide
- Guarantee Advise Amendment Beneficiary Consent
- Data Enrichment
- Main Details
2.3.1 Main Details
This topic provides the systematic instructions to initiate the Main details of Data Enrichment stage of Guarantee Advise Amendment Beneficiary Consent request.
- Application Details
- Beneficiary Response Capture
- Information to Issuing Bank
All fields displayed under Application details section, would be read only except the Priority field.
- On Data Enrichment - Main Details screen, specify the
fields that were not entered at Registration stage.
Figure 2-7 Data Enrichment - Main Details
Description of the illustration demainapplicationdetails.pngFor more information on fields, refer to the field description table below.Table 2-7 Guarantee Advise Amendment Beneficiary Consent - Main - Application Details - Field Description
Field Description Advising Bank Reference Number Read-only field. Displays the Advising Bank Reference Number as selected in Registration stage.
Received From - Customer ID Read only field. Customer ID is auto-populated from the Guarantee /SBLC Amendment.
Received From - Customer Name Read only field. Customer name is auto-populated from the Guarantee /SBLC Amendment.
Branch Read only field. Branch details is auto-populated from the Guarantee /SBLC Amendment.
Process Reference Number Read only field. Unique OBTFPM task reference number for the transaction.
This is auto generated by the system based on process name and branch code.
User Reference Number Read only field. System defaults the user reference number, depending on the selection of Advising Bank Reference Number.
Priority This field will be defaulted based on the priority maintenance. If priority is not maintained for a customer, ‘Medium' priority will be defaulted.
User can change the priority populated.
Submission Mode Read only field. System defaults the submission mode as ‘Desk’ for the transactions created via Registration Users. The values can be:
- Desk - Request received through Desk
- Courier - Request received through Courier
Transaction Date Read only field. System defaults the current branch date. User can not change the date to a back date and future date.
Beneficiary Response CaptureThe fields listed under this section are same as the fields listed under the Beneficiary Response Capture section in Registration stage. During Registration, if user has not captured input, then user can capture the details in this section.
Figure 2-8 Beneficiary Response Capture
Description of the illustration demainbenificiaryresponsecapture.pngFor more information on action buttons, refer to the field description table below.
Table 2-8 Guarantee Advise Amendment Beneficiary Consent - Main - Beneficiary Response Capture - Field Description
Field Description Amendment Number Read only field. Amendment number will be auto-populated from the Guarantee /SBLC Amendment.
Amendment Date Read only field. This field displays the date on which the amendment was made to Guarantee/ SBLC.
Beneficiary Consent Required Read only field. Beneficiary Consent Required (Y/N) will be auto-populated from the Guarantee /SBLC Amendment.
Beneficiary Response Select the beneficiary response from the drop-down. The values are:- Confirmed
- Unconfirmed
- Rejected
Remarks Specify the remarks of the beneficiary response. Action Click the edit icon to edit the remarks and Beneficiary Response. Information to Issuing Bank
For more information on fields, refer to the field description table below.
Table 2-9 Information to Issuing Bank - Field Description
Field Description Narrative Specify the narrative for MT799. The user modifies the details of the FFT text concerning beneficiary consent responses.
Note:
The user is prompted to review MT799 narrative details and the system suppresses the error message if it is not required.Audit
Description of the illustration audit.pngThis button provides information about user initiated the transaction, initiated date, stage wise detail etc.
For more information on audit, refer to the field description table below.Table 2-10 Audit - Field Description
Field Description Application No. This field displays the appliation number of the process. Branch Code This field displays the branch code. Initiated Date This field displays the date on which process is initiated. Initiated By This field displays the user ID of the user who had initiated the process. Process Name This field displays the name of the process which is initiated. S. No This field displays the serial number of the audit record. Stage Name This field displays the current stage of the process. Completed Time This field displays the time on which the audit of the current stage is completed. Completed By This field displays the user ID of the user who had completed the audit. Outcome This field displays the outcome of the audit. - Click Next.The task will move to next data segment. For more information refer Additional Fields.
Table 2-11 Main Details - Action Buttons - Field Description
Field Description Clarification Details Click to open a detailed screen, user can see the clarification details in the window and the status will be Clarification Requested. Documents Click to View/Upload the required document. Application displays the mandatory and optional documents.
The user can view and input/view application details simultaneously.
When a user clicks on the uploaded document, Document window get opened and on clicking the view icon of the uploaded document, Application screen should get split into two. The one side of the document allows to view and on the other side allows to input/view the details in the applicationRemarks Specify any additional information regarding the Guarantee Advise Amendment Beneficiary Consent. This information can be viewed by other users processing the request. Content from Remarks field should be handed off to Remarks field in Backend application.
Overrides Click to view the overrides accepted by the user. Customer Instruction Click to view/ input the following - Standard Instructions – In this section, the system will populate the details of Standard Instructions maintained for the customer. User will not be able to edit this.
- Transaction Level Instructions – In this section, OBTFPM user can input any Customer Instructions received as part of transaction processing. This section will be enabled only for customer initiated transactions.
View Undertaking Clicking this button allows the user should to view the undertaking details. View Events Click View Events button to view the snapshot of various events under the Guarantee Advised Amendment Beneficiary Consent. Signatures Click the Signature button to verify the signature of the customer/ bank if required. The user can view the Customer Number and Name of the signatory, Signature image and the applicable operation instructions if any available in the back-office system.
If more than one signature is available, system should display all the signatures.
Request Clarification Click the Request Clarification button to request for an Online clarification from customer. Clicking the button opens a detailed screen to capture the clarification details. Save & Close Save the details provided and holds the task in ‘My Task’ queue for further update. This option will not submit the request. Cancel Cancel the Data Enrichment stage inputs. The details updated in this stage are not saved. The task will be available in 'My Task' queue. Hold The details provided will be saved and status will be on hold. User must update the remarks on the reason for holding the task. This option is used, if there are any pending information yet to be received from applicant.
Reject On click of Reject, user must select a Reject Reason from a list displayed by the system. Reject Codes are:
- R1- Documents missing
- R2- Signature Missing
- R3- Input Error
- R4- Insufficient Balance/Limits
- R5 - Others
Select a Reject code and give a Reject Description.
This reject reason will be available in the remarks window throughout the process.Refer Select a Refer Reason from the values displayed by the system. Refer Codes are:
- R1- Documents missing
- R2- Signature Missing
- R3- Input Error
- R4- Insufficient Balance/Limits
- R5 - Others
Next On click of Next, system validates if all the mandatory fields have been captured. Necessary error and override messages to be displayed. On successful validation, system moves the task to the next data segment.
Parent topic: Data Enrichment