This topic provides the systematic instructions to initiate the Payment in Scrutiny stage of Export LC Amendment request.

1. On Scrutiny - Payment Details screen, specify the fields.

   Figure 2-10 Scrutiny - Payment Details
   
   Description of the illustration scrutinypaymentdetails.png
   

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

   Table 2-12 Payment Details - Field Description

   Field	Description
   Payment Details
   Special Payment conditions for beneficiary	System defaults the value of special payment conditions for beneficiary as per the LC and can be modified if required. Specify the details of special payment condition to the beneficiary, if any.
   Special Payment conditions for receiving bank	System defaults the value of special payment conditions for receiving bank as per the LC and can be modified if required. Specify the details of special payment condition to receiving bank, if any. This field specifies special payment conditions applicable to the receiving bank without disclosure to the beneficiary, for example, post-financing request/conditions for receiving bank only.
   Period for Presentation	System defaults the value of period for presentation as per the LC and can be modified if required. Specify the event name in text along with the number of days in number, if the period of presentation is based on any event other than shipment. In case of Online channel, this field is read only.
   Confirmation Instructions	System defaults the value of confirmation instructions. The options for confirmation instruction are: CONFIRM MAY ADD WITHOUT
   Partial Confirmation Allowed	Enable the option for partial confirmation. Diasable the option, if  partial confirmation denied. This field is enabled only if, Confirmation Instructions is set to Confirm.
   Silent Confirmation	This option when enabled: Confirmation Percentage should default as 100 and Silent Confirmation Amount should display the full LC outstanding value. User should not be able to modify them. All other confirmation fields to be blank and disabled. This field is added only for LC in which Issuing Bank does not request confirmation. This field is enabled, if Confirmation Instructions field has value Without or May Add
   Confirmation %	Specify the confirmation percentage. This field is applicable only if Confirmation Instructions is set to Confirm or May Add and Partial Confirmation Allowed Toggle is enabled. This field is alternate to ‘Confirmation Amount’.
   Confirmation Amount	Specify the confirmation amount. This field is applicable only if Confirmation Instructions is set to Confirm and Partial Confirmation Allowed Toggle is enabled. If Partial Confirmation Allowed field is enabled and Confirmation % is below 100, system allows to modify Confirmation % and Confirmation Amount.
   Requested Confirmation Party	Select the requested confirmation party from the drop-down. The options are: Advising Bank Advise Through Bank Others This field is enabled if Confirmation Instructions is set to Confirm or May Add.
   Requested Confirmation Party	System defaults the value of of requested confirmation party as per the issued LC and can be modified if required. Note: This field is applicable only for LC Type - Confirmed LC.
   Confirmation Expiry Date	Select the confirmation expiry date. This field indicates the date up to which the Confirmation is valid. When the underlying Confirmed LC is amended to have a new Expiry Date, the value will be populated in OBTFPM also. If new expiry date is to be confirmed, user can update the Confirmation Expiry Date to the new Expiry Date. If the new expiry date is not to be confirmed, user should not update the New Confirmation Expiry Date. System should validate that the value is only either the original expiry date or the new expiry date. In case Confirmation Expiry Date is to be extended, then on hand-off the related flag should be set to yes in back office system. In case Confirmation Expiry Date is not to be extended, then on hand off, related flag should be set to No in back office.
   Reimbursing Bank	Click Search to search and select the reimbursing bank. Party type with banks will be displayed in look-up. SWIFT code (if available), Name and address of the bank. SWIFT code (if available) Name and address of the bank On selection of the record if SWIFT code is available, then SWIFT code will be defaulted. If SWIFT code is not available then the bank's name and address to be defaulted. In case of Online channel, update the details received.
   Advise Through Bank	Click Search to search and select the advise through bank, in case of Non - Online channel. Party type with banks must be displayed in look-up. SWIFT code (if available) Name and address of the bank On selection of the record if SWIFT code is available, then SWIFT code will be defaulted. If SWIFT code is not available then the bank's name and address to be defaulted. Note: In case the selected Bank is not RMA Compliant, the system displays error message “RMA arrangement not available”. In case of SWIFT MT707 message, this field is empty. In case of online channel user can update the details received.
   Instructions to P/A/N Bank	System displays the value of Instructions to P/A/N bank as per the LC and can be modified if required. Click Search to search and select the instructions to P/A/N Bank.
   Sender to Receiver Information	System defaults the value of Sender to Receiver Information (FFT Details) as per the LC and can be modified, if required. Click Search to search and select thesender to receiver information.
   Charges	System defaults the charges details and can be modified, if required.
   Amendment charges payable by	System displays the party to pay the amendment charges. The options can be: Applicant Beneficiary Others
   Information to Issuing Bank Provide MT730 - Information to Issuing Bank details based on the description in the following table:
   Sender to Receiver Information	Click Search to search and select the FFT to provide the additional information to receiver.
   Narrative	Click Search to search and select the FFT to provide the additional information from the advising bank to the issuing bank.
   Issuing Bank Account No	Click Search to search and select the issuing bank account number from the look-up.
   Charges to be Claimed	Select the currency and specify the charges to be claimed.
   Charges	Specify the charge details for advising.
   Issuing Bank Date	Select the issuing bank date from the date picker.
   Account with Bank	Click Search to search and select the account to which the charges needs to be paid.
   Information to Advise Through Bank Provide MT710 - Information to Advise Through Bank details based on the description in the following table.
   Sender to Receiver Information	Click Search to search and select the FFT to provide the additional information to receiver.

2. Click Next.
   The task will move to next data segment. For more information refer Amendment Details

   Table 2-13 Payment Details - Action Buttons - Field Description

   Field	Description
   Documents	Upload the required 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 Amendment. This information can be viewed by other users handling the request.
   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 MT799 and MT999 messages from within the task.
   Incoming Message	Clicking this button allows the user to see the message in case of STP of incoming MT 767. Clicking this button allows parsing and processing MT 707 along with the MT708 messages.
   View LC	Clicking this button enables the user to view the latest LC 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.
   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 Scrutiny 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	On click of Back, task moves to previous logical step.
   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.