Batch Description

Account Status Change

The status change of an account is performed automatically if the Automatic Account Status Change field is enabled at Account level. A number of statuses and rules are maintained in the rule engine. The status rules are attached to the Business Product at every stage movement. Finally, the batch picks up such accounts based on the below conditions, where -

The Automatic Account Status Change flag is set to Yes.
The rules maintained in Business Product are evaluated.

The new status for the account is derived and the status of the account is updated automatically by the system.

Account Revaluation

Revaluation is a calculated upward adjustment to a country's official exchange rate relative to a selected baseline.

The Account Revaluation batch is run to revalue the balances of foreign currency customer accounts and thus, the local currency balance is restated. The required revaluation setup is captured under Configurations. As a result of the batch, the system revalues the account balances and posts the revaluation profit or loss into a predefined account and the revaluation profit / loss is then handed over to the GL system.

Reval Split Required

Reval Split Required indicates that the user requires trading split in revaluation for the GL. You can choose to break-up the revaluation Profit / Loss for the GL that you are defining.

Trading Profit / Loss – Profit or loss due to revaluation of FCY entries posted into the FCY account during the day.
Revaluation P&L – Profit or loss due to revaluation of opening balances (balances without current day’s turnover).

Based on the Configurations, the system books profit and loss to the Profit GL and Loss GL respectively. When Reval Split Required is selected, the booking of the profit and loss happens to both Trading Profit and Trading Loss GLs.

GL HandOff

The Credit GL Line and Debit GL Line for every status is captured at the business product.

The Reporting GL is determined based on the sign of account balance. If the account balance is positive, it reports to the Credit GL and likewise to the Debit GL, if negative.

To facilitate balance posting, an Intersystem Bridge GL is maintained at source code preference. The offset entries for each of the scenarios is posted to Intersystem Bridge GL.

The following GL's are defined in the Business Product maintenance to post account balances when a status movement occurs on any account belonging to that business product.

Debit and Credit GL's to which account balances must be posted, for movement to each status.

The following conditions are handled in the batch process.

No change in the balance sign and the account has net credit turnover.
No change in the balance sign and the account has net debit turnover.
No change in the account balance, as there are no transactions for the day.
No change in the account balance, since the net turnover (sum of debits and credits) is zero.
Net credit turnover in the account changing the account's balance sign from negative to positive.
Net debit turnover in the account changing the account's balance sign from positive to negative.

Dormancy

As a part of transaction processing depending on the flags and attributes sent in the transaction, the system sets the last credit activity date or the last debit activity date for an account. The dormancy date in the account is set based on the account’s activity date and dormancy days from the business product.

This batch job picks all accounts which are (i) not dormant, and (ii) whose dormancy date is lesser than the branch date; and marks it dormant.

Auto Cheque Book Request

The automatic reordering of Cheque Books is processed at EOD by executing a batch function. The following conditions should be satisfied for initiation of automatic reordering of cheque books:

The Auto Reorder of Cheque Book option is enabled at the Account level.
The number of unused check leaves for the account is less than or equal to the reorder level maintained at the Account level.

The system picks up the number of leaves to be reordered from Reorder Number of Leaves maintained for the account and issues a cheque book for the account.

Release Legal Amount Blocks

This API also performs the following actions -

It picks all the accounts having amount blocks that are expiring earlier or on the branch date.
It derives the value of the amount block that must be retained/valid.
It expires the Legal Block and updates the account balance.

Stop Payment

This batch job also performs the following actions -

Fetches Expired Stop Payments - It closes all stop payments for the branch date and if there are no active stop payments for the account, it updates the account's stop payment status to Yes.
Activates Stop Payments - It updates the stop payment flag in the account to Yes when there are active stop payments for the account on the branch date.

Statement Batch

This BOD batch generates periodic statements and swift messages for all accounts configured for periodic statement / swift message generation. Statement preferences for primary statement, secondary statement, tertiary statement and swift configuration is maintained for the account. Advice names are maintained in the advice maintenance screen and the report template is maintained with same name in report format maintenance screen. The advice is linked with the report format in the report linkage screen. OBA supports the pre-defined advices - Primary Detail, Primary Summary, Secondary Detail, Secondary Summary, Tertiary Detail and Tertiary Summary. As the batch is run in the BOD, the input to this batch is the previous working day and all statements due for the previous working day is generated in the BOD. Statement in PDF form is generated for all media except for Swift.

Courtesy Pay Evaluation

This EOD batch process applies the Courtesy Pay (CP) charge if the CP limit is utilized by the account.

The following conditions are handled as part of this batch process:

Application of CP charge based on the configured charge code at the business product level.
A fee will be applied per CP limit utilization transaction.
In case there are intra-day credits to the account which bring the account to a positive balance, then the batch will not apply the CP utilization transaction fee.

RegD Violation Evaluation

This EOD batch process performs the below actions:

Evaluate if a there is a RegD violation in the account for the month (No. of transactions for the month > Configured RegD monthly transaction threshold at business product).
Reset the Reg D counter for the accounts to start afresh for the next month.

Escheatment

This EOD batch process performs the below actions:

Calculation of the Escheatment Date based on the last activity date for the account.
Identify accounts to be escheated when the Escheatment Date equals the current business date.
Appropriating the account balances (after interest liquidation processing) to Bank and State GL accounts based on configured threshold and percentage.
Closing the account post appropriating the balance in the account.

Product Switch

This EOD batch process performs the below actions:

Identify the accounts that have breached the configured no. of monthly Reg D violations allowed in a 12-month rolling period.
Automatic product switch from the existing business product to the new business product as per product switch configuration for the identified accounts.

Garnishment

This EOD batch process will release the Garnishment block amount placed on the account when the end date of Garnishment equals the current business date.