2.4.7 Additional Details
This topic provides the systematic instructions to capture the additional details
- On Additional Details screen, click
on any Additional Details tile to view the details.
Figure 2-28 Additional Details
Description of the illustration deadditionaldetails.png - Click Save and Close to save the details and close the
screen.
Limits and Collaterals
Limit availability needs to be checked if amendment involves increase in amount or tolerance or both.Provide the Limit Details based on the description in the following table.
Description of the illustration scrutinylimitdetails.pngFigure 2-29 Collateral Details
Description of the illustration scrutinycollateraldetails1.pngFor more information on fields, refer Table 2-17 of Scrutiny stage.
- Click Save and Close to save the details and close the
screen.
Charge Details
This section displays charge details.For more information on fields, refer Table 2-18 of Scrutiny stage.
- Click Save and Close to save the details and close the
screen.Preview Messages
User can view the draft LC amendment message (outgoing MT707 SWIFT message format) being displayed on the preview message text box.
A copy of draft LC amendment can be sent for customer confirmation and the same can be done by choosing the customer response toggle as ‘yes’. The Draft MT707 message along with up to seven MT708 messages is sent to the applicant by Email as an attachment to the customer.
On submit, the message will be sent to the customer. The task will be moved to ‘pending customer response ‘stage. Upon receipt of customer’s confirmation, the transaction moves to approval.
In case the customer has requested for changes, the transaction will move to Data Enrichment and once the necessary changes made, the request moves to approval stage.Note:
A bank user can share the Draft SWIFT message to the customer through email, before the actual transmission of SWIFT message to the Advising Bank.
Description of the illustration deadditionaldetailspreview.pngFor more information on fields, refer to the field description table below.
Table 2-26 Preview Messages - Field Description
Field Description Preview SWIFT Message This section displays the Preview SWIFT Message details. Language Read only field. English is set as default language for the preview.
Message Type Select the message type. Message Status Read only field. Display the message status of draft message of liquidation details.
Repair Reason Read only field. Display the message repair reason of draft message of liquidation details.
Preview Message This field displays a preview of the draft message. Preview Mail Device This section displays the Preview Mail Device details. Language Read only field. English is set as default language for the preview.
Advice Type Select the advice type. Message Status Read only field. Display the message status of draft message of liquidation details.
Repair Reason Read only field. Display the message repair reason of draft message of liquidation details.
Preview Message This field displays a preview of the draft message. Draft Confirmation This section displays the Draft Confirmation details. Draft Confirmation Required Enable the option, if draft confirmation is required. Customer Response Specify the response received from customer. If the response is received online, the response is auto populated in this field by the system.
Customer Remarks Remarks from the customer for the draft. Response Date Customer Response received date. Customer Email ID 1 Default email address of the customer. System fetches the Email ID from Customer Address maintenance in Back office and auto populates the available Email ID.
Customer Email ID 2 By default this field is blank. Click search icon to seearch and select the Email ID from lookup from the Customer Email Address field of the customer maintenance in Back Office and replicated in OBTFPMCS.
- Click Save and Close to save the details and close the
screen.FX Linkage
This section enables the user to link the existing FX contract(s) to the Bill. User can link one or more FX deals to a bill. The linked value of an FX deal(s) must not exceed the value of the bill.
FX contract linkage with the Bill booking can happen only for immediate liquidation of sight payment or for Usance. For manual sight payment, the user needs to link the FX contract on the date of liquidation of the bill.
Following are the features of FX Linkage in BC.- FX linkage cannot be linked at Bills at initial stage.
- When a bill is drawn under LC, the details of forward contract linked as a part of the LC, will be defaulted at bill.
- Linked amount will be defaulted against the corresponding FX sequentially.
- User can delink or modify the defaulted FX details at in the Bill.
- Bill maturity date should be greater than or equal to FX Value date.
- Sum of Linked amount will not be greater than Bill contract amount.
- Linked amount will not be greater than the available amount for linkage.
- Current Utilized amount will display the liquidated/purchased/discounted/negotiated amount of Bill contract. It cannot go beyond the linked FX amount.
- When a bill is drawn under LC, delink of FX at BC is allowed only if the linked FX is not utilized by the bill.
- Multiple forward FX contract could be linked and exchange rate of FX contract vary from each. Hence, effective exchange rate for bill would be arrived using weighted average method and it is utilized during purchase/negotiation/discount or liquidation of the bill. The same will be populated in the Average FX Rate.
Description of the illustration fxlinkagedetails.png
Description of the illustration fxlinkagedetails1.pngFor more information on fields, refer Table 2-19 of Scrutiny stage.
- Click Save and Close to save the details and close the screen.
- 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-27 Additional 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 applicationRemarks Specify any additional information regarding the lc 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 Instructions 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.
Incoming Message This button displays the multiple messages (MT760 + up to 7 MT761. In case of MT798, the User can click and view the MT798 message(770,700/701).
View LC Click to view the details of the LC. Signature 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 available, system should display all the signatures.
Request Clarification 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 Scrutiny 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.
Parent topic: Data Enrichment