2.5 Exceptions

This topic helps you quickly get acquainted with the Exceptions process.

As per regulatory requirement, all tasks are scrutinized for KYC, Compliance and Sanctions. Task. The checks to external system/internal system is initiated after the DE Stage. The amount Block earmark and Limit Earmarks if applicable are also initiated after the DE stage.

If a negative response is received for any of the calls, the task lands in respective exceptional queue which require further manual handling/approval.

Amount Block Exception Approval

As part of amount block validation, application will check if sufficient balance is available in the account to create the block. On hand-off, system will debit the blocked account to the extent of block and credit charges/ commission account in case of charges block or credit the amount in suspense account for blocks created for collateral.

The transactions that have failed amount block due to non-availability of amount in respective account will reach the amount block exception stage.

Log in into OBTFPM application, amount block exception queue. Amount block validation failed tasks for trade transactions will be listed in the queue. Open the task to view summary of important fields with values.

On Approval, system should not release the Amount Block against each applicable account and system should handoff the “Amount Block Reference Number “to the back office. On successful handoff, back office will make use of these “Amount Block Reference Number” to release the Amount Block done in the mid office (OBTFPM) and should debit the CASA account from the Back office. If multiple accounts are applicable, Amount Block. Reference for all accounts to be passed to the back office.

Exception is created when sufficient balance is not available for blocking the settlement account and the same can be addressed by the approver in the following ways:

  • Approve:
    • Settlement amount will be funded (outside of this process)
    • Allow account to be overdrawn during hand-off
  • Refer:
    • Refer Refer back to DE providing alternate settlement account to be used for block.
    • Different collateral to be mapped or utilize lines in place of collateral.
  • Reject: Reject the transaction due to non-availability of sufficient balance in settlement account

Amount Bock Exception

This section will display the amount block exception details.

Summary

Tiles Displayed in Summary:
  • Main Details - User can view the application details details and export LC details.
  • Availability - User can view already captured availability and shipment details.
  • Payment - User can view all details related to payments.
  • Documents and Conditions - User can view the document details and additional condition details.
  • Additional Fields: Banks can configure the additional fields during implementation. User can view the details of additional fields.
  • Advices - User can view the details of the advices.
  • Revolving Details: User can drill down into revolving details tile to see more information on revolving LC if applicable.
  • Commission, Charges and Taxes: User can see the details provided for charges. User can update the details if required.
  • Preview Messages - User can view the preview of the message.
  • Settlement Details - User can view the settlement details.
  • Accounting Details - User can view the accounting entries generated in back office.

    Note:

    When the Value Date is different from the Transaction Date for one or more accounting entries, system displays an Alert Message “Value Date is different from Transaction Date for one or more Accounting entries.
  • Party Details - User can view party details like applicant, advising bank etc.
  • Compliance - User can view the compliance details.
  1. Click Approve. to approve thw export booking amount bolck exception check.

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

Table 2-32 Amount Bock Exception - Action Buttons - Field Description

Field Description
Documents View/Upload the required document.
Remarks Specify any additional information regarding the Export LC Transfer. 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.
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..
View Events Click to view the details of the details of LC , amendments (if any), drawings (if any) and liquidations if any under the LC in chronological sequence from LC drawing.
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.

User can refer the task back to the Data Enrichment user. User must select a Refer Reason from the values displayed by the system. Refer Codes

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.

Approve On approve, application must validate for all mandatory field values, and task must move to the next logical stage.
Back Task moves to previous logical step.

Exception - Know Your Customer (KYC)

As part of KYC validation, application will check if necessary KYC documents are available and valid for the applicant. The transactions that have failed KYC due to non-availability / expired KYC verification will reach KYC exception stage.
  1. Log in into OBTFPM application, KYC exception queue. KYC exception failed tasks for Trade Finance transactions will be listed in your queue.
  2. Open the task, to see summary tiles that display a summary of available updated fields with values.

    User can pick up a transaction and do the following actions:

    Approve
    • After changing the KYC status in the back end application (outside this process).
    • Without changing the KYC status in the back end application.
    • Reject (with appropriate reject reason).
Summary
Tiles Displayed in Summary:
  • Main Details - User can view the application details details and export LC details.
  • Availability - User can view already captured availability and shipment details.
  • Payment - User can view all details related to payments.
  • Documents and Conditions - User can view the document details and additional condition details.
  • Additional Fields: Banks can configure the additional fields during implementation. User can view the details of additional fields.
  • Advices - User can view the details of the advices.
  • Revolving Details: User can drill down into revolving details tile to see more information on revolving LC if applicable.
  • Commission, Charges and Taxes: User can see the details provided for charges. User can update the details if required.
  • Preview Messages - User can view the preview of the message.
  • Settlement Details - User can view the settlement details.
  • Accounting Details - User can view the accounting entries generated in back office.

    Note:

    When the Value Date is different from the Transaction Date for one or more accounting entries, system displays an Alert Message “Value Date is different from Transaction Date for one or more Accounting entries.
  • Party Details - User can view party details like applicant, advising bank etc.
  • Compliance - User can view the compliance details.

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

Table 2-33 Exception - Know Your Customer (KYC) Summary - Action Buttons - Field Description

Field Description
Documents View/Upload the required document.
Remarks Specify any additional information regarding the Export LC Drawing. 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.
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..
View Events Click to view the details of the details of LC , amendments (if any), drawings (if any) and liquidations if any under the LC in chronological sequence from LC drawing.
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.

User can refer the task back to the Data Enrichment user. User must select a Refer Reason from the values displayed by the system. Refer Codes

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.

Approve On approve, application must validate for all mandatory field values, and task must move to the next logical stage.
Back Task moves to previous logical step.

Exception - Limit Check/Credit

The transactions that have failed limit check due to non-availability of limits will be available in limit check exception queue for further handling.
  1. Log in into OBTFPM application, limit check exception queue. Limit check exception failed tasks for Trade Finance transactions must be listed in your queue.
  2. Click My Task. The summary tiles displays summary of important fields with values.

    Note:

    On Approval of the exception task, system should validate the Limit Availability, Limit Expiry Date in the Limit System and create Earmark in the ELCM system. In case if the Limit is not available or the Limit is expired, then system should display an error message and should not allow the user to approve and proceed.

Limit check Exception approver can do the following actions:

Approve
  • Limit enhanced in the back end (outside this process).
  • Without enhancing limit in the back end.
Refer
  • Refer back to DE providing alternate limit id to map
  • Refer additional collateral to be mapped

Reject

The transaction due to non-availability of limits capturing reject reason.

Limit/Credit Check

This section will display the amount block exception details.

Summary

Tiles Displayed in Summary:
  • Main Details - User can view the application details details and export LC details.
  • Availability - User can view already captured availability and shipment details.
  • Payment - User can view all details related to payments.
  • Documents and Conditions - User can view the document details and additional condition details.
  • Additional Fields: Banks can configure the additional fields during implementation. User can view the details of additional fields.
  • Advices - User can view the details of the advices.
  • Revolving Details: User can drill down into revolving details tile to see more information on revolving LC if applicable.
  • Commission, Charges and Taxes: User can see the details provided for charges. User can update the details if required.
  • Preview Messages - User can view the preview of the message.
  • Settlement Details - User can view the settlement details.
  • Accounting Details - User can view the accounting entries generated in back office.

    Note:

    When the Value Date is different from the Transaction Date for one or more accounting entries, system displays an Alert Message “Value Date is different from Transaction Date for one or more Accounting entries.
  • Party Details - User can view party details like applicant, advising bank etc.
  • Compliance - User can view the compliance details.
For more information on action butons, refer to the field description table below.

Table 2-34 Exception - Limit Check/Credit - Action Buttons – Field Description

Field Description
Documents View/Upload the required document.
Remarks Specify any additional information regarding the Export LC Drawing. 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.
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..
View Events Click to view the details of the details of LC , amendments (if any), drawings (if any) and liquidations if any under the LC in chronological sequence from LC drawing.
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.

User can refer the task back to the Data Enrichment user. User must select a Refer Reason from the values displayed by the system. Refer Codes

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.

Approve On approve, application must validate for all mandatory field values, and task must move to the next logical stage.
Back Task moves to previous logical step.