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

1. On Document Details screen, specify the fields.

   Figure 2-9 Scrutiny - Document Details
   
   Description of the illustration scrutinydocumentdetails.png
   

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

   Table 2-10 Document Details - Field Description

   Field	Description
   Document Details - As per LC	Specify the Document Details - As per LC based on the description of following table:
   Document Code	Read only field. System defaults the document code from the latest LC.
   Document Reference Number	Specify the document reference number.
   Copy	Read only field. Number of duplicate copies of documents as required in LC.
   Original	Read only field. Number of documents in original as required in LC.
   Description	Read only field. System dispalys the document description based on the document code.
   First Mail Received Original	Specify the number of originals of documents received.
   First Mail Received Copy	Specify the number of duplicate copies of documents received.
   Second Mail Received Original	Specify the number of originals of documents received from second mail.
   Second Mail Received Copy	Specify the number of duplicate copies of documents received.
   Document Clause	Read only field. System populates the document Clause based on the document code. User can view the document clause by clicking the link in the ‘Document Clause’ column.
   Received Description	System populates the description of the documents received from presenting bank. User can edit the description clause by clicking the link in the ‘Received Description’ column.
   Discrepant	System marks the discrepant toggle as ‘Yes’ if there is difference between number of documents required and number of documents received. It also enables the user to make the changes, if any discrepancy identified in the document.
   Discrepancy Code	Click Search to search and select the discrepancy code based on the discrepancy identified. This field is enabled, if Discrepant option is enabled.
   Discrepancy Description	Description will be displayed based on the discrepancy code. The user can change the description.
   Action	Click Edit icon to edit the document details.
   Additional documents presented	Specify the additional documents presented details. The user can click + to add multiple document details. This table fetches document details as maintained for the specific bill drawing product (BCDPRMNT). Here user can add/modify/delete additional document received, if any, during bill drawing. Once bill drawing is authorized, details from this table will be fetched in update drawing operation also.
   Document Code	Document code is auto-populated from the latest LC. User can click plus + icon and 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. Note: The User is not allowed to add any document code which is already existing in any of the two tables.
   Document Reference Number	Specify the reference number available in the documents. Note: If “Document date” is more than “Shipment Date” system displays an override alert.
   Document Date	Specify the document date of the underlying document. Note: If “Document date” is more than “Shipment Date” system displays an override alert.
   Description	Displays the description of the additional documents based on the document code selected. Click the link to view the description of the document.
   First Mail Received Original	Specify the number of originals of documents received from first mail.
   First Mail Received Copy	Specify the number of duplicate copies of documents received from first mail.
   Second Mail Received Original	Specify the number of originals of documents received from second mail.
   Second Mail Received Copy	Specify the number of duplicate copies of documents received from second mail.
   Action	Click Edit icon to edit the document code. Click Delete icon to delete the document code.

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-11 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 update drawings. 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.
   Common Group Messages	Click Common Group Message button, to send MT759,790,91,92,95,96,98,799,9999 messages from within the task.
   Incoming Message	Displays the incoming message, if any. In case of MT798-MT726-MT759 request, user can view MT798 message(726-759) in this placeholder in Header of the task. In case of MT798_MT788-MT799 request, user can view MT798 message (788-799) in this placeholder in Header of the process-task.
   View LC	Click to view the latest LC values displayed in the respective fields. All fields displayed in LC details section are read only 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	Click the Request Clarification button to submit the request for clarification to the “Trade Finance Portal” User for the transactions 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	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.