Managing underwriting issue approval

Types of approval

There are two actions that can be taken to approve an underwriting issue.

In most cases, an underwriting issue is approved. This action is equivalent to clicking the Approve button on the Risk Analysis screen's UW Issues tab. In this circumstance:

• There is a user who has sufficient authority to approve the issue.

For example, suppose there is a personal auto policy with a driver who is 18 years old. The driver's age triggers the creation of a "PA: Primary driver under 25" underwriting issue. Alice Applegate is an underwriter who has authority to approve "PA: Primary driver under 25" underwriting issues for drivers who are 17 or older. Thus, Alice can approve the underwriting issue on this policy.

In rare cases, an underwriting issue is special approved. This action is equivalent to clicking the Special Approve button on the Risk Analysis screen's UW Issues tab, which is visible only to users with the uwapproveall system permission. In this circumstance:

• The underwriting issue is blocking a job that, for the sake of the business, must be moved forward.
• There is no user with sufficient authority to approve the issue.
• There is a user with the uwapproveall system permission.

For example, suppose there is a personal auto policy with a driver who is 16 years old. The driver's age triggers the creation of a "PA: Primary driver under 25" underwriting issue. There are no underwriters with authority to approve "PA: Primary driver under 25" underwriting issues for drivers who are 16. But, the decision has been made to move forward with the policy. Like all other underwriters, the supervisor Shelly Duggan does not have sufficient authority. But she does have the uwapproveall system permission. Therefore, Shelly can "special approve" the underwriting issue on this policy.

Approval endpoints

To approve an underwriting issue, use one of the following endpoints:

• POST /job/v1/jobs/{jobId}/uw-issues/{uwIssueId}/approve
• POST /job/v1/jobs/{jobId}/uw-issues/{uwIssueId}/special-approve

These endpoints do not require a request body.

When you either approve or "special approve" an underwriting issue:

• currentBlockingPoint is set to NonBlocking if the issue is fully approved
• hasApprovalOrRejection is set to true

Overriding approval defaults

When approving an underwriting issue, PolicyCenter provides default values for the following:

• The maximum, minimum, or acceptable value on the job that will permit the underwriting issue to be approved.
• Whether the approval can be edited before binding.
• The duration of the approval, both as a stage of job processing and as a timeframe.

When approving an underwriting issue through Cloud API, you do not need to specify this information. However, you can override the defaults by including the following properties in the approval request.

The following example approves underwriting issue pc:2177 for job pc:707 with overrides for the default values.

POST /job/v1/jobs/pc:707/uw-issues/pc:2177/approve

{
  "data": {
    "attributes": {
        "moneyApprovalValue": {
            "currency": "usd",
            "amount": "500.00"
        },
        "canEditApprovalBeforeBind": false,
        "approvalBlockingPoint": {
            "code": "BlocksIssuance"
        },
        "approvalDurationType": {
            "code": "ThreeYears"
        }
    }
  }
}