Netting Agreement and Netting Decisioning

A Netting Agreement maintenance screen has been introduced to create netting rules to be linked to a relationship or to a corporate and counterparty pair. A Netting Decisioning maintenance screen has been introduced to link agreement rules with appropriate relationship and counterparty.

Netting Calculation and Settlement

A new batch has been introduced to create a netting transaction. Separate transactions are created for different currencies of receivables and payables.

The netting jobs include identification of receivables and payables as per the criteria defined in Decisioning screen. Post which these transactions go for approval /rejection and settlement cycle.

Reconciliation rules to include an ability to create rules with “Fixed Values” and Case Sensitivity

A Case Sensitive switch (Yes or No) is introduced in the exact recon condition to select whether the system needs to check the case sensitivity of the field value while recon execution.

Reconciliation rule addition of new pattern type “Contains”

A new pattern type Contains is introduced in Recon rule definition maintenance screen to check at the time of reconciliation that the LHS attribute field selected should contain any specified words or phrases entered as VALUE.

Alert generation for Cash Deposit and Withdrawal (on Approval)

A new alert categories Cash Collection and Cash Withdrawal are introduced in Alert Definition and Alert Decisioning screen to configure the alert and notification events for cash deposit and withdrawal transactions on approval.

Addition of Own Branches location network in Location maintenance

A new Location Network field is introduced in Location maintenance screen to display the extended screen and configure the bank details (Correspondent / Outside Network / Own Branches). An Own Branches option is introduced in Location Network field to process the cheque in the own branches locally

Placeholder for Debit/Credit Notes in Database for including/excluding in reconciliation

Debit and credit notes that are created directly in the application, are now included in cashflow forecasting. A flag or placeholder has been introduced in the database that indicates whether a newly created debit/credit note, which is consumed for cashflow forecasting, must be reconciled or not. This is applicable for manual, automatic or both options of reconciliation. The name of the flag is ‘Not to be directly Reconciled’. If this flag is set to ‘Y’, then the debit/credit note must NOT be picked up for reconciliation. And if set to ‘N’ or ‘Null’, then the debit/credit note must be picked up for reconciliation.

Placeholder for Debit/Credit Notes in File Upload and Service API for including/excluding in reconciliation

Debit and credit notes that are created though file upload or service API, are now included in cashflow forecasting. A flag or placeholder has been introduced in the database that indicates whether a newly created debit/credit note, which is consumed for cashflow forecasting, must be reconciled or not. This is applicable for manual, automatic or both options of reconciliation. The name of the flag is ‘Not to be directly Reconciled’. If this flag is set to ‘Y’, then the debit/credit note must NOT be picked up for reconciliation. And if set to ‘N’ or ‘Null’, then the debit/credit note must be picked up for reconciliation.

Provision to select between real and virtual credit account when marking instrument status

When marking instrument status, in the Instrument Management > Mark Instrument Status screen, a provision has been made to enable selection of either real or virtual option for credit account number. For this purpose, a new field called Account Type with two radio buttons: Real and Virtual, has been introduced. This field is available in the pop-up screen which appears on clicking search in the Credit Account Number field. Based on requirement, the user can either select the ‘Real’ option or the ‘Virtual’ option, when searching for credit account number.

KAFKA event trigger on instrument status change through Instrument Management

Whenever the status of an instrument is changed through the Instrument Management screen, KAFKA will trigger and send updates to the Instrument Collection reporting schema.

Refreshing of Deposit Slip Details segment during creation of Deposit Entry

In the Cash Transaction > Deposit Entry > Deposit Slip Detail segment, on searching for an external reference number, the deposit slip associated with that reference number is displayed in the left-hand pane. When the deposit slip in the left-hand pane is clicked, its details appear in the right-hand pane. On clicking the delete icon beside the deposit slip in the left-hand pane, the right-hand pane will now refresh and be available for creation of a new deposit slip.

Similarly, when the external reference number is searched, and the associated deposit slip is displayed in the left-hand pane, on clicking the delete icon directly without clicking on the deposit slip, the right-hand pane will now refresh and be available for creation of a new deposit slip.

Introduction of the Reject option for the Checker

Along with the Approve option, there is now a Reject option available to a Checker (Approver). Once the Checker rejects a record, there is a provision to enter relevant comments for the rejection. The record is then available to the Maker for modification/updating.

The View screens in the above modules have also been enhanced to display the number of submissions made by the Maker in the specific record tile.

Total Settlement Tranche Count and Tranche Average pay gap set to zero

The values of getTotalSettleTrancheCount and result.getTrancheAvgPayGap() should be greater than 0. If a negative value appears, it is replaced with 0. This is required to ensure that negative tranche count and negative average pay gap is handled logically.