Scheduled Jobs

Scheduled 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 FintechOS Studio User Guide's dedicated page. The following scheduled jobs are configured per module.

Scheduled Jobs

Scheduled At 02:00 AM, daily run
Description This job creates payment returns for payments which are in Unallocated status for more than the number of days set by the No. of Days Before Return parameter.
For example,: If a payment is in Unallocated status for more than 5 days, a payment return is automatically generated for this unallocated payment, in the sixth day.
Scheduled At 12:46 PM, daily run
Description This job generates a statement (invoice) for policies and masterpolicies in Proposal, Issued or InForce status. This replaces the FTOS_PYMT_InsertStatementDueDate, which is no longer available and will be deactivated. Find information on how to configure invoice generation at product level in the Product Admin Configuration page, section Invoice Generation.
NOTE  
Policies in Cancelled status are excluded for new invoice generation.
Scheduled At 05:00 AM, daily run
Description For all the mandates registered in the system, the job checks the Begin and End Dates against the current date and it updates the mandate statuses accordingly. For example, if the current date is passed the End Date set for a mandate, the mandate status is changed to Expired.
Scheduled At 05:00 AM, daily run
Description Job purpose: to generate a payment instruction file with all outgoing payments complying with he following conditions:

  • the outgoing payment is in Scheduled status;

  • the payment date is scheduled for the current date, or before the current date.

File format: .csv with .txt extension; time stamped.
File structure: Reference No; Beneficiary’s Name; Beneficiary's IBAN; Beneficiary's Bank; Payment Amount; Currency; Scheduled Date; Payer's Name; Payer's IBAN; Payer's Bank.
Scheduled At 5:15 AM, daily run
Description This job is scheduled to perform status changes (canceling, modifying or reactivating) on the existing mandates, based on the unprocessed records from the buffer - the FTOS_PYMT_DIDE_ADDACS entity.
IMPORTANT!  
When trying to run FTOS_PYMT_DIDE_ADDACS and DIDEUK_Instructions jobs, while the FTOS_PYMT_DIDEProcessor is set to SEPA type, the system will log an error and stop running the job.
Scheduled At 04:00 AM, daily run
Description The job is scheduled to generate mandate activation instructions for the BACSClosed BACS Payment Schemes Limited, previously known as Bankers' Automated Clearing System, is responsible for the clearing and settlement of UK automated direct debit and BACS Direct Credit and the provision of third-party services. system, in a standardized .txt file (DIDEUK_Instructions) - based on which the system starts the mandate activation procedure. This job is dedicated to the UK direct debit processing, only. It is the job that collects all the Draft mandates and sends instructions for their activation to BACS - in a file that complies with the format requested by BACS.
IMPORTANT!  
When trying to run FTOS_PYMT_DIDE_ADDACS and DIDEUK_Instructions jobs, while the FTOS_PYMT_DIDEProcessor is set to SEPA type, the system will log an error and stop running the job.
Scheduled At 03:00 AM, daily run
Description This job uses the FTOS_PYMT_DIDEConfiguration parameter in order to generate the direct debit instruction file in the system. The file is generated in a standardized .txt format, in order to be suitable to the bank that is going to process it. The file contains the instructions for direct debit billings for an active mandate - based on which the bank transfers the installment amount from the insured into insurer's account. Depending on the configuration, this job generates the DIDEPaymentsInstructionFile (for SEPA) and DD_BACSPayments (for UK), also.
Scheduled At 06:00 AM, daily run
Description This job sends notifications to invoices that are still in status Generated x days before the invoice’s due date. The number of days is determined by the NoOfDaysFollowUpInvoice insurance parameter.
Scheduled 00:00:01 AM, daily run
Description This job changes the business status of the quote and the master quote.
The FTOS_QA_ExpireQuotes service checks the Quote Expiring Date of the quote or master quote, and if it is passed this date, it changes the quote status into Expired.
Scheduled every 30 seconds, starting at :00 second after the minute
Description This job migrates the quotes from the Quote entities to the Quote Admin entities.
The following services run as a part of this job:

  • FTOS_QA_MigrateManualAnalysisQuotes: migrates the quotes that are in Manual Analysis status.

  • FTOS_QA_MigrateDecisionPassedQuotes: migrates the quotes that have the Client Decision as Accepted.

  • FTOS_QA_MigrateNotPassedQuotes: migrates the quotes that are in Declined by UW status.

  • FTOS_QA_MigratePassedQuotes: migrates the quotes that are in Passed status.
Scheduled every 30 seconds, starting at :00 second after the minute
Description This job migrates the master quote and the quotes belonging to it from the Master Quote Admin entity to the Master Quote entity.
The FTOS_QA_MigrateMasterQuote service migrates the master quote and the quotes belonging to it from the Master Quote Admin entity to the Master Quote entity.
Scheduled once a day at 09:30:00 AM
Description This job deletes migrated quotes.
The FTOS_QA_DeleteMigratedOffers service deletes the quotes/ master quotes from the Quote entities, that are migrated into the Quote Admin entities.

Scheduled for 04:00 AM, daily run.

Used for policies with last installments in Unpaid status, this job automatically moves policies from Enforced to Lapsed status, when the DAUDD parameter is fulfilled.

When in Lapsed, the policy is modified as follows:

  • The End Date becomes the Due Date of the unpaid installment;

  • If there are no claims registered, the Premium Amount becomes equal to the Paid Premium (sum of paid installments). If there are claims registered on the policy, the Premium Amount doesn't change;

  • If the Premium Amount is changed, the installment schedule is updated including just the paid installments.

The system also checks the Master Policies payment and, if there will be any installments still unpaid, being in the Unpaid status) after X days for a Master Policy (X days since the due date of the last unpaid installment of the Master Policy), then that Master Policy changes its status from Inforce to Lapsed.

After a Master Policy is moved in the Lapsed status, that Master Policy is modified as follows:

  • The end date becomes the due date of the unpaid installment;

  • The new premium amount is equal to the paid premiums (the sum of paid installments);

  • Because the premium amount is changed, the payment schedule of the Master Policy is updated and only includes the paid installments.

The number of days is set in the "Days after unpaid due date" existing and generic parameter, set at portfolio/contract level.

The following service runs as part of this job:

  1. FTOS_PA_PolicyLapsed

    This service automatically moves policies from InForce to Lapsed status, when the DAUDD parameter is fulfilled.

Scheduled for 03:00 AM, daily run.

This job searches for the End Date and the NDBR parameter in order to identify the policies in InForce status that are suitable for automatic or manual renewal, for renewal offers.
The job returns the policies with Policy End Date (Initial End Date) - No of days before renewal (parameter set) = Current Date.

The following service runs as part of this job:

  1. FTOS_PA_PolicyRenewal

    This service searches for the End Date and the NDBR parameter in order to identify the policies in InForce status that are suitable for automatic or manual renewal, for renewal offers.

Scheduled for 01:00 AM, daily run.

For the policies that are in the Issued business status, have the same Begin Date as the Current Date and have the Automatic InForce checkbox selected, at Product level.
This job verifies whether the above conditions are fulfilled and moves policies from Issued to InForce status.

The following service runs as part of this job:

  1. FTOS_INSPA_Policy_IssuedToEnforced

    This service verifies if policies that are in the Issued business status, have the same Begin Date as the Current Date and have the Automatic InForce checkbox selected, and moves them from Issued to InForce status.

Scheduled for 11:59 PM, daily run.

This job is set to transition the policy status from In Force or Suspended to the Maturity status when policies current date is greater than the end date. This job also automatically transitions the policy status from In Force to Maturity when the policy's current date is greater than the end date. If the end date is resulted from a cancellation, then the status is changed to the corresponding configured status on the cancellation reason.

The following service runs as part of this job:

  1. FTOS_PA_PolicyMaturity

    This service transitions the policies and master policies to the Maturity status, when their current date is greater than their end date. If the end date is resulted from a cancellation, then the status is changed to the corresponding configured status on the cancellation reason.

Scheduled for 03:40 AM, daily run.

This job approves pending policies, when the effective date is reached for MTA and Cancellation requests, and puts the policy in status.

The following service runs as part of this job:

  1. FTOS_INSPA_ApprovePendingPolicies

    This service approves pending policies, when the effective date is reached for MTA and Cancellation requests.

Scheduled for 04:31 AM, daily run.

This job finds all the policies with unpaid installments, that have also passed the grace period, and transitions them to the Suspended status.

The following service runs as part of this job:

  1. FTOS_PA_PolicySuspended

    This service transitions the policies with unpaid installments into the Suspended status, after their grace period has ended.

Scheduled for 01:00 AM, daily run.

For the masterpolicies that are in the Issued business status, have the same Begin Date as the Current Date and have the Automatic InForce checkbox selected, at Product level.
This job verifies whether the above conditions are fulfilled and moves masterpolicies from the Issued to the InForce status.

The following service runs as part of this job:

  1. FTOS_PA_MasterPolicy_IssuedToInforce

    This service verifies if masterpolicies that are in the Issued business status, have the same Begin Date as the Current Date and have the Automatic InForce checkbox selected, and moves them from Issued to InForce status.

Scheduled for 05:00, daily run.

This job checks the Master Policies payment and, if there will be any installments still unpaid, being in the Unpaid status) after X days for a Master Policy (X days since the due date of the last unpaid installment of the Master Policy), then that Master Policy changes its status from Inforce to Lapsed. This job does not delete Master Policies' installments.

After a Master Policy is moved in the Lapsed status, that Master Policy is modified as follows:

  • The End Date becomes the Due Date of the unpaid installment;

  • The new premium amount is equal to the paid premiums (the sum of paid installments);

  • Because the premium amount is changed, the payment schedule of the Master Policy is updated and only includes the paid installments.

The number of days is set in the "Days after unpaid due date" existing and generic parameter, set at portfolio/contract level.

The following service runs as part of this job:

  1. FTOS_PA_MasterPolicyLapsed

    This service automatically moves masterpolicies from InForce to Lapsed status, if there will be any installments still unpaid, being in the Unpaid status) after X days for a Master Policy (X days since the due date of the last unpaid installment of the Master Policy).

Scheduled for 11:50 PM, daily run.

This job is set to transition the master policy status from InForce or Suspended to the Maturity status when the current date is greater than the end date. This job also automatically transitions the master policy status from In Force to Maturity when the master policy's current date is greater than the end date. If the end date is resulted from a cancellation, then the status is changed to the corresponding configured status on the cancellation reason.

The following service runs as part of this job:

  1. FTOS_INS_MasterPolicy_Maturity

    This service transitions the master policy to the Maturity status, when their current date is greater than their end date. If the end date is resulted from a cancellation, then the status is changed to the corresponding configured status on the cancellation reason.

Scheduled for 03:00 AM, daily run.

This job is set to find all the policies from the system which have to be renewed according to their End date and the parameter set for the No. of day before renewal. The job verifies all the policies which have the Policy End Date (policy to be renewed Initial End Date) - No. of days before renewal (parameter set) = Current Date, and applies the renewal process to them.

If there is a Cancellation request approved on the policy or masterpolicy, then the Pending record is not taken into consideration for automatic renewal.

In case any of the the policies or the Masterpolicy to be renewed are already subject to a MTA (Mid-term adjustments) process in progress while the automatic renewal offer process is going on (including the current policy/masterpolicy), then the MTA process can proceed, but a warning message is displayed informing the user that there is already a renewal offer for the Masterpolicy.

In case the Masterpolicy to be renewed is already subjected to a Cancellation process in progress while the automatic renewal offer process is going on (including the current masterpolicy), then when the cancellation process is completed (approved), the renewal offers corresponding to the cancelled masterpolicy (masterpolicy offers and policy offers under it) are deleted.

The following service runs as part of this job:

  1. FTOS_PA_MasterpolicyRenewalOffers

    This service finds all the masterpolicies and related policies in the InForce status which have to be renewed.

Scheduled for 4:50 AM, daily run.

This job approves pending masterpolicies, when the effective date is reached for MTA and Cancellation requests, and puts the masterpolicy in status.

The following service runs as part of this job:

  1. FTOS_INSPA_ApprovePendingMasterpolicies

    This service approves pending masterpolicies, when the effective date is reached for MTA and Cancellation requests.

Scheduled to run once a day at 09:35 AM.

The job updates the status of draft alterations group to expired when the effective date is smaller than the system date.

Scheduled to run once a day at 09:35 AM.

The job generates quotes for the policies configured with renewal offer, logged in the Renewal Offer entity.

Scheduled to run once a day at 09:40 AM.

The job updates on effective date the policy clones resulted from alterations to policy versions. This job also calculates the premium due based on the current version of the policy, using the due date minus statement generation days (SGDays) to determine when to generate the bill.

Scheduled to run once a day at 12:00 PM.

The job updates the status for cancellations in progress to Cancelled, if the creation date exceeds the CloseSurrenderNoDays configured in processor FTOS_PA_PolicyCancellation.

Scheduled to run once a day at 09:15 AM.

The job generates new master policy for the products configured with renewal for a new or the same policy.

Scheduled to run once a day at 06:59:59 PM.

Generates notification to customer for policy that has an installment in grace, and the due date is greater than systemDate - insurance paratemer value DBEGP.

Scheduled to run once a day at 09:10 AM.

The job updates the status of the policy from Proposal to Withdraw if it has an installment in status unpaid and that installment transitioned to the Unpaid status for more than the number of day set in insurance parameter PWDAY.

Scheduled to run once a day at 09:05 AM.

The job evaluates all installments and updates the status to In Grace or Unpaid.

Scheduled to run once a day at 09:10 AM.

The job generates invoices based on payment schedule. It replaces the old job FTOS_PYMT_InsertStatementDueDate, which is no longer available and will be deactivated.

Scheduled to run once a day at 09:10 AM.

The job updates the status of a payment from Closed to Paid when the payment due date is greater than the system date.

Scheduled to run once a day at 09:55:53 AM.

The job updates Invoice status from Generated to OnGrace and from OnGrace to Unpaid.

Scheduled to run every 10 minutes, between 09:00 AM and 09:59 AM.

The job processes async events from the Payment HUB.

Scheduled daily, at 12:00 pm
Description Automatically moves records through different business statuses, according to different conditions.