Starting renewals using a batch process

PolicyCenter has a batch process that automatically finds policies that are ready for renewal. In the default configuration, PolicyCenter starts renewals based upon the expiration date, the renewal process lead time, line of business, jurisdiction, and time of year. PolicyCenter first checks whether the expiration date of the policy period falls within the renewal process lead time. Then PolicyCenter determines the lead time required by regulations. PolicyCenter adds additional time for company practices. Finally, PolicyCenter adds a delay for concurrent policy transactions, if any. Because the renewal process lead time is checked first, no policy will start automatic renewal sooner than this.

Factors to consider in scheduling the Renewal batch process

There are several factors to consider in the schedule of the renewal batch process. Some of these factors are:

Frequency – Suppose you have a batch process that runs every Sunday. A renewal that could start on Wednesday will not start until the batch process runs several days later on Sunday.
Start time – The batch process starts at 11 p.m. on Sunday, and it may take several hours to run. Therefore, the batch process starts some renewals on Sunday and others early Monday morning.
Postal service – The renewal paperwork depends upon the working days of the postal service. Although the renewal was started on Sunday, the postal service picks up the renewal paperwork on Monday.