Fetch Contracts for Forward Processing

6.3.1 Fetch Contracts for Forward Processing

In this screen, you can filter the contracts required for forward processing based on the following parameters:

Table 6-4 Contracts for Forward Processing

Fields	Description
Date Range	The From and To dates consider Archive days and Limit days for forward processing. These dates are automatically calculated by the system based on the application date considering the Limit Days and Archive Days maintained as part of branch parameters (in the Syndication Loans and Commitments – Branch Parameters screen). For more details on maintaining branch parameters, refer the heading titled Indicating branch parameters for loan syndication in the Reference Information for Loan Syndication chapter of this User Manual.
Processed Status	You can also filter the required contracts based on a processing status of the contracts. The available options are: All: If you select this option, system filters all the contracts, irrespective of the processing status. Processed: This option filters only those contracts that are already processed. For such contracts, the messages are released into the Outgoing Message Browser. Partial Processed: Applicable if there are pending components for the contract (not all the components of a specific type – for example., fee, interest, tax - are processed). For instance, a contract may have four fee components associated with it and only two of them may be processed. In this case, the contract is said to be partially processed. Not Processed: This option displays only those contracts that are yet to be processed. After specifying the filter criteria, click the Refresh button to fetch the contracts. The following details are displayed in the screen: Name of the borrower Description of the event to be processed User Reference Number of the contract Contract Currency Amount and Value Date Payment Value Date Contract Reference Number Counterparty Event Code Process Status: Not, Partial, Full You need to check the Hold Transaction option after the message generation and before the fee liquidation (FLIQ) of payment, if the payment has to be stopped. During the batch, the system verifies if the payment is on hold. If so, it won't pass the accounting entry and the schedule does not get liquidated. If you select the Hold Transaction box, the system deselects and disable the Confirmed to Auto check box. It also disables the D button. If the Hold Transaction option is deselected for the payment on/before the schedule date of the payment, then the FLIQ event is triggered during the EOD batch of the payment schedule date and the new payment message is generated with new payment value date. There is no change in participant ratio/SSI if there is no back valued activity impacting the schedule amount. If the payment is closed manually, then the fee liquidation entries are passed using the suspense GL and SSI propagation for amount tags till the next hold date/ latest SSI based on the components in next schedule is on hold on or before the current application date. The Sanction Checked box is selected automatically once Sanction Check system confirms all the payment messages in detail block with value -1 (COMPLETE). If any of the payment messages in the detail block is not -1 (COMPLETE), then the system deselects the Sanction Checked box. The SC N/A box is selected systematically if sanction check is not applicable for a payment. Depending on the module and payment type, the payments for which SC is not applicable is handed off as soon as they are generated, or manual intervention is required to release the payments. The system displays the payment messages for the below payments in the Payment Browser screen: Loan Disbursement from LD module when INIT mode is Semi-Auto at the contract level. Outgoing Payments from FT module when the Populate FT to Payment Browser box is selected at the Loans Parameters screen. Adhoc Fee Payment from LS and LD module where fee liquidation mode is manual and the Populate Adhoc Fee(LD/LS) to Payment Browser box is selected at the Loans Parameters screen. The system performs sanction screening process for LS, LD, SLT, Adhoc Fee and FT modules, if the Sanction Check Required box in Loans Parameter screen is selected. This is done once the payment message is generated and displayed in the Payment Browser screen with status code as 0 - TRANSMITTED TO SANCTIONS. If the status code received from Sanction Check system is -1, then: You are allowed to confirm and manually release the payment messages for LS and SLT payments. If the message is on Hold, It is not possible to confirm and manually release the payment messages even if the status code received is -1 (COMPLETE). On UnHold, again system allows to confirm and manually release the payment messages if the status code received from Sanction is not -1 (COMPLETE). Oracle Lending systematically releases the payment messages for LD, FT and Adhoc Fee payments and there is no user intervention required. Audit trail details are updated with Maker and Checker as SYSTEM along with Entry Time and Auth Time for such systematic release of payment. Once the status is updated to -1 in forward processing browser, further amendment to the status is not allowed. In addition, the only future action expected is to confirm and release the payment message from Oracle Lending. If the status code received from Sanction Check is not -1, then system does not allow to confirm and manually release the payment messages for LS and SLT payments. If the status code received from Sanction Check system is 03 (Terminate), then the payment message can neither be released manually / systematically nor be resent to SC. If the status code received from Sanction Check system is 04, 05 or 06, then: You are allowed to confirm and release the payment messages for LS and SLT payments after confirming the override message. Oracle Lending does not systematically release the payment messages for LD, FT and Adhoc Fee payments You are allowed to select and resend such message to Sanction Check system for confirmation. On click of OK button, staging table is populated with the status and Java adapter resends those messages for sanction screening Payment messages once marked for Resend to SC, system updates back the status code to 0 - TRANSMITTED TO SANCTIONS and does not allow to Release/Confirm/ Resend till return message is received from sanction check. If the status code is 0, -1, 01, 02, 03 then you are not allowed to resend the message for Sanction Check processing. Payment cannot be released manually or systematically when the status is 0. The status can be systematically re-updated more than once for the payment messages that are re-sent from Oracle Lending. For example, If the current status of a payment message is 04, you are allowed to resend the message to SC and the status is received as -1, then system re-updates the status from 04 to -1. If the current status of a particular message is already -1 or message is confirmed and released, then no modification of the status are allowed. If the status code is 01, 02, 04, 05, 06, then you are allowed to confirm and manually release the message with maker/checker process for payments across LS, SLT, LD, Adhoc Fee and FT modules. However, the status code remains same and there is no change in the status codes even after releasing the payment messages. You can view the payments based on status code: Payments with status code 01, 02, 03, 04, 05 or 06 are displayed at the top highlighted in Red color (Only the display text is in Red color with the existing background color). Payments having status code -1 are displayed at the end. During end of day batch processing, the payment messages cannot be released from forward processing browser, though the status code received from Sanction Check system is -1. Once the batch is completed and online jobs are started, status code in the forward processing browser gets updated which was received during the batch. The payment messages for FT and LD modules including Adhoc Fee is systematically released if the status code is -1. However, the payment messages for LS and SLT modules are allowed to be released manually through maker/checker process when the status code is -1.

Fields

Description

Date Range

The From and To dates consider Archive days and Limit days for forward processing. These dates are automatically calculated by the system based on the application date considering the Limit Days and Archive Days maintained as part of branch parameters (in the Syndication Loans and Commitments – Branch Parameters screen).

For more details on maintaining branch parameters, refer the heading titled Indicating branch parameters for loan syndication in the Reference Information for Loan Syndication chapter of this User Manual.

Processed Status

You can also filter the required contracts based on a processing status of the contracts. The available options are:

All: If you select this option, system filters all the contracts, irrespective of the processing status.
Processed: This option filters only those contracts that are already processed. For such contracts, the messages are released into the Outgoing Message Browser.
Partial Processed: Applicable if there are pending components for the contract (not all the components of a specific type – for example., fee, interest, tax - are processed). For instance, a contract may have four fee components associated with it and only two of them may be processed. In this case, the contract is said to be partially processed.
Not Processed: This option displays only those contracts that are yet to be processed.

After specifying the filter criteria, click the Refresh button to fetch the contracts. The following details are displayed in the screen:

Name of the borrower
Description of the event to be processed
User Reference Number of the contract
Contract Currency
Amount and Value Date
Payment Value Date
Contract Reference Number
Counterparty
Event Code
Process Status: Not, Partial, Full

You need to check the Hold Transaction option after the message generation and before the fee liquidation (FLIQ) of payment, if the payment has to be stopped.

During the batch, the system verifies if the payment is on hold. If so, it won't pass the accounting entry and the schedule does not get liquidated. If you select the Hold Transaction box, the system deselects and disable the Confirmed to Auto check box. It also disables the D button.

If the Hold Transaction option is deselected for the payment on/before the schedule date of the payment, then the FLIQ event is triggered during the EOD batch of the payment schedule date and the new payment message is generated with new payment value date. There is no change in participant ratio/SSI if there is no back valued activity impacting the schedule amount.

If the payment is closed manually, then the fee liquidation entries are passed using the suspense GL and SSI propagation for amount tags till the next hold date/ latest SSI based on the components in next schedule is on hold on or before the current application date.

The Sanction Checked box is selected automatically once Sanction Check system confirms all the payment messages in detail block with value -1 (COMPLETE). If any of the payment messages in the detail block is not -1 (COMPLETE), then the system deselects the Sanction Checked box.

The SC N/A box is selected systematically if sanction check is not applicable for a payment.

Depending on the module and payment type, the payments for which SC is not applicable is handed off as soon as they are generated, or manual intervention is required to release the payments.

The system displays the payment messages for the below payments in the Payment Browser screen:

Loan Disbursement from LD module when INIT mode is Semi-Auto at the contract level.
Outgoing Payments from FT module when the Populate FT to Payment Browser box is selected at the Loans Parameters screen.
Adhoc Fee Payment from LS and LD module where fee liquidation mode is manual and the Populate Adhoc Fee(LD/LS) to Payment Browser box is selected at the Loans Parameters screen.

The system performs sanction screening process for LS, LD, SLT, Adhoc Fee and FT modules, if the Sanction Check Required box in Loans Parameter screen is selected. This is done once the payment message is generated and displayed in the Payment Browser screen with status code as 0 - TRANSMITTED TO SANCTIONS.

If the status code received from Sanction Check system is -1, then:

You are allowed to confirm and manually release the payment messages for LS and SLT payments.
If the message is on Hold, It is not possible to confirm and manually release the payment messages even if the status code received is -1 (COMPLETE).
On UnHold, again system allows to confirm and manually release the payment messages if the status code received from Sanction is not -1 (COMPLETE).
Oracle Lending systematically releases the payment messages for LD, FT and Adhoc Fee payments and there is no user intervention required. Audit trail details are updated with Maker and Checker as SYSTEM along with Entry Time and Auth Time for such systematic release of payment.
Once the status is updated to -1 in forward processing browser, further amendment to the status is not allowed. In addition, the only future action expected is to confirm and release the payment message from Oracle Lending.

If the status code received from Sanction Check is not -1, then system does not allow to confirm and manually release the payment messages for LS and SLT payments.

If the status code received from Sanction Check system is 03 (Terminate), then the payment message can neither be released manually / systematically nor be resent to SC.

If the status code received from Sanction Check system is 04, 05 or 06, then:

You are allowed to confirm and release the payment messages for LS and SLT payments after confirming the override message.
Oracle Lending does not systematically release the payment messages for LD, FT and Adhoc Fee payments
You are allowed to select and resend such message to Sanction Check system for confirmation. On click of OK button, staging table is populated with the status and Java adapter resends those messages for sanction screening
Payment messages once marked for Resend to SC, system updates back the status code to 0 - TRANSMITTED TO SANCTIONS and does not allow to Release/Confirm/ Resend till return message is received from sanction check.

If the status code is 0, -1, 01, 02, 03 then you are not allowed to resend the message for Sanction Check processing.

Payment cannot be released manually or systematically when the status is 0. The status can be systematically re-updated more than once for the payment messages that are re-sent from Oracle Lending. For example,

If the current status of a payment message is 04, you are allowed to resend the message to SC and the status is received as -1, then system re-updates the status from 04 to -1.
If the current status of a particular message is already -1 or message is confirmed and released, then no modification of the status are allowed.

If the status code is 01, 02, 04, 05, 06, then you are allowed to confirm and manually release the message with maker/checker process for payments across LS, SLT, LD, Adhoc Fee and FT modules. However, the status code remains same and there is no change in the status codes even after releasing the payment messages.

You can view the payments based on status code:

Payments with status code 01, 02, 03, 04, 05 or 06 are displayed at the top highlighted in Red color (Only the display text is in Red color with the existing background color).
Payments having status code -1 are displayed at the end.

During end of day batch processing, the payment messages cannot be released from forward processing browser, though the status code received from Sanction Check system is -1. Once the batch is completed and online jobs are started, status code in the forward processing browser gets updated which was received during the batch.

The payment messages for FT and LD modules including Adhoc Fee is systematically released if the status code is -1. However, the payment messages for LS and SLT modules are allowed to be released manually through maker/checker process when the status code is -1.

Parent topic: Forward Processing of Events