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

1. On Document Details screen, specify the fields.

   Figure 2-20 Data Enrichment - Document Details
   
   Description of the illustration dedocumentsandconditions.png
   

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

   Table 2-21 Document Details - Field Description

   Field	Description
   Document Details	Specify the document details based on the descriptio of following table: Click the '+' iconto add multiple document details.
   Document Code	Document code is auto-populated from the latest LC. 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.
   Document Description	System dispalys the document description based on the document code from the latest LC.
   Copy	System defaults the number of duplicate copies of documents as required in LC. User can edit the actual copies received. Specify the number copies received.
   Original	System defaults the number of documents in original as required in LC. User can edit the actual originals received. Specify the number of original documents received.
   Clause Description	System populates the description of the clause required as per LC. User can view the description of the clause by clicking the link in the ‘Document Clause’ column.
   Document Received	Enable the option, if original document is required. Disable the option, if original document is not required.
   Action	Click Edit icon to edit the document details. Click Delete icon to delete the document details.

   Additional Conditions

   Online Channel - System will default the details received in the description column. System will parse the additional conditions required field into multiple line items based on line de-limiter (+) and shall populate each line item as a separate description. User can read the description and make any changes required to the description, also must be able to add more conditions.

   Non Online Channel - User can use FFT to capture additional conditions and can edit the description populated from FFT. User should also be able to add additional FFT.

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

   Table 2-22 Additional Conditions - Field Description

   Field	Description
   Additional Conditions	Specify the Additional Conditions based on the descriptio of following table: Click the '+' icon to add multiple Additional Conditions.
   FFT Code	Click Search to search and select the FFT code from the look up.
   FFT Description	This field displays the description of the FFT code based on the selected FFT code.
   Action	Click Edit icon to edit the additional condition details. Click Delete icon to delete the additional condition 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-23 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 export lc Transfer amendment. 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.
   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.
   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	Click the Back button, to go back 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.