Jobs
Jobs are automated procedures that perform certain tasks, running at a specific time or on a recurring schedule. Read detailed information about scheduling jobs in the Innovation Studio User Guide's dedicated page.
Core Banking has the following scheduled jobs that perform repetitive banking procedures for the purpose of closing one day and opening the next one, or for processing or cleaning up queued transactions:
Start Of Day (SOD) Job
The Core Banking Start Of Day job is made up of a series of services, which are run one by one each day before the banking day is initiated.
The following services are run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | Disburse Contracts With Approved Tranches In Current Date | When successfully run, the service performs the disbursements of contract tranches approved on the current date (the day that is about to be opened/ initiated). |
3 | Set Limit Available Amount Due To FX Change | When successfully run, the service recalculates the available amount on limits depending on the currency's exchange rate on a specific day. The service does not take into consideration past versions of the limit up to a given day. It only takes into consideration the current limit version and uses those results for calculating the limit available value. |
4 | Set Collateral Available Amount And Contract Collateral Value Due To FX Change | When successfully run, the service recalculates the available amount on collaterals and the collateral value on contracts depending on the currency's exchange rate on a specific day. |
5 | Set Contract Amount (Overdraft) Due To Plan Due Date Reached (Increase/ Decrease) | When successfully run, the service increases/ decreases the limit amount on overdraft contracts that reached their reevaluation plan due date. |
6 | Set Credit Facility Amount Due To Plan DueDate Reached (Increase/ Decrease) | When successfully run, the service increases/ decreases the limit amount on credit facilities that reached their reevaluation plan due date. |
7 | Set Credit Facility Available Amount Due To FX Change | When successfully run, the service recalculates the available amount on credit facilities depending on the currency's exchange rate on a specific day. |
8 | Set Contract Covenant Status Due To Review Date Reached | When successfully run, the service changes the status of covenants on contracts that reached their review date. |
9 | Set Contract Category Based on Overdue Days | When successfully run, the service changes the category of contracts based on overdue days. |
10 | Schedule versioning after stop accrual | When successfully run, the service creates new schedule versions for the contracts that were marked for stopping the accrual process calculation. The new version of the schedule has the Process of Loss reason and all the un-notified installments are updated. |
11 | Calculate Accrual For Overdraft Contracts and Current Accounts With Overdraft Contracts | When successfully run, the service recalculates the accrual for utilization and for unusage for overdraft contracts and for current account with overdraft contracts. |
12 | Calculate Accrual For Credit Facility | When successfully run, the service recalculates the accrual for utilization and for unusage for credit facilities. |
13 | Calculate Accrual And Provisions For Loan Contracts | When successfully run, the service recalculates the accrual and provisions for loan contracts. |
14 | Calculate Overdraft Debt to recover | When successfully run, the service recalculates the overdraft debt still to recover from contracts. |
15 | Calculate Penalties for Contracts and Credit Facility | When successfully run, the service recalculates the penalties for contracts and for credit facilities. |
16 | Calculate Interests For Deposit Contracts | When successfully run, the service recalculates the interests for deposit contracts. |
17 | End Job Log | When successfully run, the service updates the same record that the Start Job Log service inserted within the FTOS_CB_ScheduleJobLog entity, writing information about the job ending time. |
End Of Day (EOD) Job
The Core Banking End Of Day job is made up of a series of services, which are run one by one each day after the banking day is closed.
The following services are run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | Set Limit Expired | When successfully run, the service sets the limits which are about to expire in the current day as Expired. |
3 | Set Accrual Amounts on Repayment Schedule for Overdraft Contract and Current Account with Overdraft | When successfully run, the service recalculates the accrual for utilization on repayment schedules for overdraft contracts and for current account with overdraft contracts. |
4 | Run Recover Debts | When successfully run, the service performs the direct debit transactions to recover all debts at that point in process. |
5 | Set Accrual Amounts Unusage Commission Values on Repayment Schedule for Contracts | When successfully run, the service recalculates the accrual for unusage commissions on repayment schedules for contracts. |
6 | Update Expiry Date for Overdraft installment | When successfully run, the service updates all the expiry dates for overdraft installments for the current account with overdraft contracts. |
7 | Generate Repayment Notifications | When successfully run, the service generates the repayment notifications for all the contracts with due amounts on schedule on that day. |
8 | Recover Debts After Generate Notification | When successfully run, the service performs the direct debit transactions to recover all debts after generating the repayment notifications. |
9 | Run Payment Allocation | When successfully run, the service performs the payment allocation operations for unallocated or partially allocated payments. |
10 | Generate Accounting Entries | When successfully run, the service generates the accounting entries for all transactions performed on that day. |
11 | Set Limit Available Amount Due To FX Changes | When successfully run, the service sets the limit amounts available to all contracts due to exchange rates changes. |
12 | End Job Log | When successfully run, the service updates the same record that the Start Job Log service inserted within the FTOS_CB_ScheduleJobLog entity, writing information about the job ending time. |
Bank Account Transaction Queue Processing (CB) Job
The Bank Account Transaction Queue Processing scheduled job was created in order to process all the bank account transactions that were placed in a queue instead of being processed in real-time at transaction approval. Each time a transaction is performed on a bank account, the system verifies its transaction type's Real Time Process field. If the value is True
, then the transaction is processed right away. If the value is False
, then the transaction is inserted as a record in the FTOS_CB_BankAccountTransactionQueue
entity, with the isProcessed
attribute set to False
and isWithError
set to False
. The Bank Account Transaction Queue Processing scheduled job runs every 1 minute, taking the top 10 records from the entity with the attribute isProcessed = False
, and processing the transactions. Any errors encountered on processing are logged in the errorMessage
attribute.
The following service is run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | FTOS_CB_BankAccountTransactionQueue_Process | When successfully run, the service takes the top 10 records from the bank account transactions queue (the FTOS_CB_BankAccountTransactionQueue entity) with the attribute isProcessed = False , and processes the transactions. After each processing, the isProcessed , isWithError , and errorMessage attributes are updated. |
3 | End Job Log | When successfully run, the service updates the same record that the Start Job Log service inserted within the FTOS_CB_ScheduleJobLog entity, writing information about the job ending time. |
Bank Account Transaction Queue Cleanup (CB) Job
The Bank Account Transaction Queue Cleanup scheduled job runs once each night and deletes the already processed transaction records with the isWithError
attribute value False.
The following service is run as part of this job:
Running Order | Service Name | Details |
1 | FTOS_CB_BankAccountTransactionQueue_Cleanup | When successfully run, the service deletes the records from the bank account transactions queue (the FTOS_CB_BankAccountTransactionQueue entity) with the attribute isProcessed = True and isWithError = False . |
Close Contracts (CB) Job
The Close Contracts scheduled job was created to close automatically all contracts with Automatic Closure = True
and Real Time Closure = False
, with zero available amount and with no further amounts to be recovered, that have Balance Off Date
filled in and Closure Date = Current Date
. The job runs by default at 11:00 PM system time.
The following services run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | FTOS_CB_CloseContract | When successfully run, the service closes all contracts with Automatic Closure = True and Real Time Closure = False , with zero available amount and with no further amounts to be recovered, that have Balance Off Date filled in and Closure Date = Current Date . |
3 | End Job Log | When successfully run, the service updates the same record that the Start Job Log service inserted within the FTOS_CB_ScheduleJobLog entity, writing information about the job ending time. |
Close Contracts RealTime(CB) Job
The Close Contracts RealTime scheduled job was created to close automatically all contracts with Automatic Closure = True
and Real Time Closure = True
, with zero available amount and with no further amounts to be recovered. The job runs by default every 5 seconds, between 06:00 AM and 07:59 PM system time.
The following services run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | FTOS_CB_CloseContractRealTime | When successfully run, the service closes all contracts with Automatic Closure = True and Real Time Closure = True , with zero available amount and with no further amounts to be recovered. |
3 | End Job Log | When successfully run, the service updates the same record that the Start Job Log service inserted within the FTOS_CB_ScheduleJobLog entity, writing information about the job ending time. |
Run Loan Payment Allocation (CB) Job
The Run Loan Payment Allocation scheduled job was created to process almost in real-time the payment allocation operations for payments with Unallocated or Partially Allocated statuses. The job runs by default every 5 seconds, between 06:00 AM and 07:59 PM system time.
The following services run as part of this job:
Running Order | Service Name | Details |
1 | Start Job Log | When successfully run and if another SOD or EOD job is not currently running within Core Banking, the service inserts a record into the FTOS_CB_ScheduleJobLog entity, containing information about the job starting time. |
2 | FTOS_CB_Debt_to_Payment | When successfully run, the service processes the payment allocation operations for unallocated or partially allocated payments. |
TPM Invoices (TPM) Job
The TPM Invoices (TPM) scheduled job runs once each night and creates third-party invoices and payments, for the combination of third-party entity/ agreements currency, during the validity of the agreement, on the Payment Day of each agreement, as defined in the third-party agreement's Payment Periodicity
(daily, monthly, or weekly).
The following services run as part of this job:
Running Order | Service Name | Details |
1 | Generate Invoices Automatically | When successfully run, the service generates third-party invoices as mentioned above, for the combination of third-party entity/ agreements currency, during the validity of the agreement, on the Payment Day of each agreement, as defined in the third-party agreement's Payment Periodicity (daily, monthly, or weekly).
If invoice details were already created on a manual invoice, then these details are excluded from the automatic process. |
2 | Charge Not Paid Invoices | When successfully run, the service creates the bank account transactions for the due payments for invoices with Not Paid status. |