Calculating the cancellation effective date

PolicyCenter calculates the earliest cancellation effective date, based on cancellation reason, jurisdiction, line of business, and other factors. Methods in CancellationEnhancement.gsx calculate the date. In some cases, the calculation calls the Notification plugin which references the notification_configs.xml system table. The notification_configs.xml system table is where you specify the cancellation lead time by jurisdiction, line of business, and cancellation reason. You can view this table by navigating to System Tables in Product Designer.

Calculating the cancellation effective date if the source is insured

If the Source is Insured, return the current date. However, if the reason is that the policy is not taken, return the date that the policy went into effect.

Calculating the cancellation effective date if the source is insurer

This topic describes how PolicyCenter calculates the cancellation effective if the Source is Insurer.

Note: The cancellation lead time returned by the notification_config.xml system table is described in Lead time in NotificationConfig system table. This topic also describes how the application determines the lead time.

If the cancellation reason is equal to Policy rewritten or replaced (flat cancel), then the cancellation effective date is equal to starting date of the policy period. You are done.
Else, determine if the policy is in the underwriting period.
1. Calculate the number of the days (xDays) between the Policy Effective Date and the current date.
2. The Notification plugin retrieves the underwriting period from the notification_configs.xml system table. The underwriting period is specified in rows with ActionType of Underwriting Period. The underwriting period is the value in the LeadTime column.
  If xDays is less than or equal to the LeadTime, then the policy is in the underwriting period.
  If the policy is in the underwriting period, the application will use underwriting period action types and categories in the notification_configs.xml system table to determine the cancellation lead time.
The Notification plugin retrieves the maximum lead time required for notification from the notification_configs.xml system table. The plugin retrieves the maximum lead time based on the cancellation reason, whether the policy is in the underwriting period, the policy jurisdiction, and the line of business.

Cancellation reason	Category	ActionType
Fraud	`Cancellation`	`fraudcancel`
	`UW Period Cancellation`	`uwperiodfraudcancel`
Non payment	`Cancellation`	`nonpaycancel`
	`UW Period Cancellation`	`uwperiodnonpaycancel`
Any other reason	`Cancellation`	`othercancel`
	`UW Period Cancellation`	`uwothercancel`

Note: If a policy includes multiple jurisdictions, there can be multiple matching rows. A policy that includes more than one line of business (such as a commercial package policy) can include both multiple jurisdictions and lines of business. In this case, the Notification plugin retrieves the maximum lead time. Therefore, the plugin returns the longest lead time specified for any of the jurisdiction and line of business combinations in the policy.

The cancellation effective date is equal to the current date plus the LeadTime for the matching row plus one day. Cancellation does not take place until the full notification period has passed. If ten days notification is required, cancellation does not take place earlier than 10:01 a.m. on day 11.