2.3.2 Document Details

This topic provides the systematic instructions to capture the details of the documents received.

This section enables the user to enter/ update Documents and conditions details for Islamic Import Collection Update.
As part of document details screen in DE stage the user can capture the Transport Document reference and document date. On click of ‘Next’ system should validate the value in Document Reference field against the transport document/Bill of Lading (MARDOC) against any Outstanding Shipping Guarantees issued for the drawee and is not linked to any Documentary Collection or Import Letter of Credit. System should default the Shipping Guarantee Reference in the next screen.

System defaults the Shipping Guarantee Reference in the next screen. System displays an override if the Bill Of Lading reference mentioned in the document details screen matches with that of the Bill of Lading reference in any of the unlinked Shipping Guarantees issued for the customer.

  1. On Document Details screen, specify the fields.

    Figure 2-8 Data Enrichment - Document Details
    Description of dedocumentdetails.png follows
    Description of the illustration dedocumentdetails.png

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

    Table 2-9 Document Details - Field Description

    Field Description
    Document Code System defaults the document codes based on the product selected.

    Click Search to search and select the document code based on the document received .

    User can add or delete the code by deleting the line on the grid.

    Click + to add multiple Document Details.

    Document Type System defaults the document type based on the product selected.
    Document Description System will populate the document description based on the document code. User can view the description, by clicking the link.
    Document Reference Specify the document reference.
    Copies Received System defaults the number copies received from the Drawer. User can edit the actual copies received.
    Originals Received System defaults the number of original documents received from the Drawer. User can edit the actual originals received.
    Document Date System defaults the document date. User can edit the date on which the document is received.
    Action Click Edit icon to edit the document details.

    Click Delete icon to delete the document details.

  2. Click Next.
    The task will move to next data segment.

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

    Table 2-10 Document 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 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

    Remarks Specify any additional information regarding the collection. 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, OBTFPMCS user can input any Customer Instructions received as part of transaction processing. This section will be enabled only for customer initiated transactions.
    Common Group Messages Click to send MT799 and MT999 messages from within the task.
    View Collection Enables the user to view the latest collection values displayed in the respective fields.
    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 required, system should display all the signatures.

    Request Clarification User can specify the clarification details for requests received online.
    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
    Back On click of Back, system moves the task back to previous data segment.
    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.