PEO underwriting approval process

This topic describes the Underwriting Approval process for RFP and Renewal Batches. It is intended for Business Analysts to aid in understanding the process and configuration of the system. It identifies the technical features of the Underwriting Approval process.

Underwriting approval process overview

The Underwriting Approval Process concept is:

  • To create Approval records based on specific Pricing Batch criteria (which it has always done).

  • Re-use existing Approval records whenever possible to preserve audit data (which it has done although not always appropriately).

  • Resolve shortcomings in the existing process when changing Contract Status after Approvals have been generated (which left some Approvals in place although they were not applicable to the business).

  • Add Task Triggering to Dependent Approval Escalation.

The process is designed so that certain key Milestones generate Clone Tasks or perform dataform pipeline Saves so that Task Triggering can be initiated. Other minor Milestones are performed directly in the database which will NOT generate Task Triggering.

In this document, the following conventions are used to identify which type of action is performed for those Milestones:

  • [Db] indicates a database action that does not generate Task Triggering

  • [CloneTask] indicates a custom Clone Task action is broadcast

  • [Pipeline] indicates a record is either added or modified through Business Logic causing Task Triggering to fire

The following Processes are evaluated:

  • Creating Underwriting Definitions

  • Creating Underwriting Approval Dependencies

  • Accept the RFP Batch the first time

  • Approve or Decline Approval Records

  • Reprocess the Batch

  • Accept the RFP Batch on subsequent attempts

  • Submit the Renewal Batch

  • Approve the Renewal Batch Approval Records

  • Decline the Renewal Batch

  • Changing Contract Types

  • Additional Client Master RPF Actions that affect Approvals (Decline, ReActivate)

  • Additional Renewal Batch Actions (Kill, Clone)

  • Comparison Batches

  • Approval State Diagrams

What happens in the system when an RFP is "killed"?

When a "Kill" workflow process is initiated on an RFP from the Pricing Console or Client Master record , the following occurs:

  • The Locked checkbox located in the Sales/Broker Information section of the Client Master record is unchecked and the Locked Expiration Date is also cleared.

  • The Client Master record and all associated underwriting approval records are set to a status of "Dead". 

  • All associated underwriting approval records are marked Inactive (i.e., the Active checkbox is cleared) and the Audit field of each underwriting approval record is updated with the status change details.