2.3.4 Additional Fields

This topic provides the systematic instructions to capture the additional fields.

This section displays the additional fields based on the User defined fields maintained in the system.

In case of STP of Incoming MT 765, values should be handled as done in Offline process for Guarantee Claim.

  1. On Additional Fields screen, specify the fields, if any.

    Figure 2-11 Scrutiny - Additional FieldsDescription of scrutinyadditionalfields.png follows
    Description of the illustration scrutinyadditionalfields.png

  2. Click Next.
    The task will move to next data segment. For more information refer Additional Details.

    For more information on action buttons, refer to the field description table below.

    Table 2-14 Additional Fields - Action Buttons - Field Description

    Field Description
    Clarification Details Clicking the button opens 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 application

    Note:

    Not applicable for STP of SWIFT MT 765.
    Remarks Specify any additional information regarding the Lodge Claim Guarantee Issued. 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.
    Incoming Message Clicking this button allows the user to see the message in case of STP of incoming MT 765.
    View Undertaking Clicking this button allows the user to view the undertaking details.
    Request Clarification Clicking this button allows the user to submit the request for clarification to the “Trade Finance Portal” for the transactions that are initiated offline.
    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
    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.

    Cancel Cancel the Scrutiny stage inputs. The details updated in this stage are not saved. The task will be available in 'My Task' queue.
    Save & Close Save the details provided and holds the task in ‘My Task’ queue for further update. This option will not submit the request.
    Back Clicking on Back button, takes the user to the previous screen.
    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.