This topic provides the systematic instructions to initiate the Data Enrichment stage of import documentary collection liquidation - Islamic request.

1. On Data Enrichment - Main Details screen, specify the fields that were not entered at Registration stage.

   Figure 2-7 Data Enrichment - Main Details - Application Details
   
   Description of the illustration demainapplicationdetails.png
   

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

   Table 2-6 Main - Application Details - Field Description

   Field	Description
   Documentary Collection Number	Read only field. This field displays the documentary collection reference number as selected in Registration stage.
   Drawee	Read only field. Drawee ID and Drawee Name will be auto-populated from Registration stage.
   Branch	Read only field. Branch details is auto-populated from Registration stage.
   Priority	System populates the priority of the customer based on priority maintenance. If priority is not maintained for the customer, system will populate 'Medium' as the default priority. User can change the priority populated any time before submit.
   Submission Mode	The submission mode of Import Collection Liquidation request. By default the submission mode will have the value as ‘Desk’.
   Remitting Bank/Remitter	Read only field. Remitting Bank/Remitter will be auto-populated based on the selected Documentary Collection Number in Registration stage.
   Remitting Bank/Remitter Reference	Read only field. Remitting Bank/Remitting Bank Reference will be auto-populated based on the selected Documentary Collection Numbe in Registration stage.
   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.
   Remitting Bank Date/Remitting Date	Read only field. Remitting Bank Date/Remitting Date will be auto-populated from Registration stage.
   Liquidation Date	Read only field. By default, the application displays branch’s current date. User can change the liquidation date.
   Version Number	Read only field. This field displays the latest version of the bill.

   Collection Details

   The fields listed under this section are same as the fields listed under the Collection Details section in Registration. For more information of the fields, refer Registration stage. During Registration, if user has not captured input, then user can capture the details in this section.

   Figure 2-8 Data Enrichment - Collection Details
   
   Description of the illustration demaincollectiondetails.png
   

   Table 2-7 Main - Collection Details - Field Description

   Field	Description
   Documents Received	Read only field. Documents received details will be auto-populated from Registration stage.
   Tenor Type	Read only field. Tenor will be auto-populated from Registration stage.
   Product Code	Read only field. Product code will be auto-populated from Registration stage.
   Product Description	Read only field. This field displays the description of the product as per the product code.
   User Reference Number	Read only field. User reference number is defaulted based on the description of the product as per the product code.
   Operation Type	Read only field. Operation Code will be auto-populated from the collection booking.
   Stage	Read only field. System displays the stage of the transaction.
   Co Acceptance Required	Read only field. Co-Acceptance Required will be auto-populated from Registration stage.
   Contract Reference Number	Read only field. System populates contract reference number from the back end system once the Documentary Collection Number is selected in Registration stage..
   Bill Amount	Read only field. Bill currency and amount will be auto-populated from Registration stage.
   Amount In Local Currency	Read only field. System fetches the local currency equivalent value for the LC amount from back office (with decimal places).
   Bill Outstanding Amount	Read only field. Bill Outstanding Amount will be auto-populated from Registration stage.
   Liquidation Amount	Specify the bill amount to be liquidated. If Tenor Type is Both, system disables the user to input in this field. On Submit and on click of Next, system displays message “This is a Multi-Tenor bill. Liquidation Details are to be input in Multi-Tenor Grid”.
   Finance Amount	Read only field. Finance Amount will be auto-populated from Registration stage.
   Drawer	Read only field. Drawer ID and Drawer Name will be auto-populated from Registration stage.
   Unlinked FX Rate	Specify the unlinked FX rate. If Tenor Type is Both, system disables the user to input in this field. On Submit and on click of Next, system displays message “This is a Multi-Tenor bill. Liquidation Details are to be input in Multi-Tenor Grid”.
   Rebate Amount	Read only field. This field displays the rebate to the bill outstanding amount.

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

   Table 2-8 Main 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, OBTFPM user can input any Customer Instructions received as part of transaction processing. This section will be enabled only for customer initiated transactions.
   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
   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.