2.4.6 Additional Details

This topic provides the systematic instructions to capture the additional details in Data Enrichment stage of Lodge Claim Guarantee Issued request.

  1. On Additional Details screen, click View on any Additional Details tile to view the details.
  2. Click Save and Close to save the details and close the screen.

    Limits and Collaterals

    For more information, refer to the field description table Table 2-15 in Scrutiny stage.

  3. Click Save and Close to save the details and close the screen.

    Charge Details

    For more information, refer to the field description table of Table 2-16 in Scrutiny stage.

  4. Click Save and Close to save the details and close the screen.
    Tracer Details
    The bank users can capture these tracer details for Claim Lodgement in Guarantee and should send the tracers to the customer till its Settled / Extended / Rejected / Injunction.

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

    Table 2-22 Tracer Details - Field Description

    Field Description
    Tracer Code Read only field.

    Tracer code is defaulted by the system maintained in the product level.

    Description Read only field.

    Description of the racer code is auto populated.

    Party Type Specify the party type of the tracer or click Search to search and select from the party type from the look-up.
    Required Enable the option, if respective tracer is required.
    Maximum Tracers Specify the maximum number of tracers to be sent.

    Maximum allowed is 99 exceeding the same system should prompt an error message for the same “Maximum number of numerals allowed is: 2” and should clear the field to enter the correct value by the user.

    Maximum Tracers cannot be less than the “Number Sent”, system needs to validate the same.

    Number Sent Number Sent is defaulted by the System with the value, where the number of tracers sent so far. And it cannot be greater than the “Maximum Tracers”.

    The user can change the value.

    Start Days Specify the number of days after which the tracer has to be sent from the Tracer Start date.

    It should be positive numeric value.

    Last Sent On Read only field.

    Tracer last sent date is defaulted by the system.

    Medium Select the medium in which the Tracer has to be generated from the drop-down list.

    It lists all the possible mediums maintained in the system.

    • MAIL
    • SWIFT
    Frequency Specify the medium in which the Tracer has to be generated.

    It should be positive numeric value.

    Template ID Specify the template ID or click Search to search and select the template ID in which the tracer has to be generated from the lookup.

    It is a lookup which lists all the possible templates maintained in the system.

    Template ID is nothing but the data that goes in Tag 79 in MT799.

    This template ID is applicable only for medium 'SWIFT'.

    Template lookup displays all the template ids applicable for the given Tracer Code.

    Action Click Edit icon to edit the tracer details.
  5. Click Save and Close to save the details and close the screen.
    Preview Mesage

    This screen provides preview of draft guarantee details.

    Based on details captured in the previous screen, the preview message simulated from the back office and the user can view the message.

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

    Table 2-23 Preview Message - Field Description

    Field Description
    Preview SWIFT Message This section displays the Preview SWIFT Message details.
    Language Read only field.

    English is set as default language for the preview.

    Message Type Select the message type from the drop down.

    User can choose to see preview of different message like MT 700, MT 740 and MT 701.

    Message Status Read only field.

    Display the message status of draft message of guarantee details.

    Repair Reason Read only field.

    Display the message repair reason of draft message of guarantee details.

    Preview Message This field displays a preview of the draft message.

    Based on the guarantee text captured in the previous screen, guarantee draft is generated in the back office and is displayed in this screen.

    Preview - Mail Device This section displays the Preview - Mail Device details.
    Language Read only field.

    The language for the advice message.

    English is set as default language for the preview.

    Advice Type Select the advice type.
    Message Status Read only field.

    Display the message status of draft message of guarantee details.

    Repair Reason Read only field.

    Display the message repair reason of draft message of guarantee details.

    Preview Message This field displays a preview of advice.
  6. Click Save and Close to save the details and close the screen.
  7. Next.
    The task will move to next data segment.

    Table 2-24 Additional Details - 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 Data Enrichment 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.