Managing underwriting issue approval

You can approve, reject, and reopen underwriting issues through Cloud API.

Approval underwriting issues

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.

Approval default type Request body property Datatype Corresponding field on the Risk Approval Details screen
Numeric default

One of the following, based on the underwriting issue type:

  • decimalApprovalValue
  • integerApprovalValue
String Value
Money default moneyApprovalValue, which must include a currency and amount value currency must be the value from the Currency typelist that matches the issue's currency. amount must be a string. Value
State default

stateSetValue object, which must include an inclusionType and a states array

inclusionType is typically set to inclusive. Members of the state array must come from the State typelist and there must be at least one value. Value
Approval editability canEditApprovalBeforeBind Boolean Allow Edit?
Duration by job stage approvalBlockingPoint From the UWIssueBlockingPoint typelist Through
Duration by time frame approvalDurationType From the UWApprovalDurationType typelist which Valid until

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"
        }
    }
  }
}

Rejecting underwriting issues

To reject an underwriting issue, use the following endpoint:

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

The /reject endpoint does not require a request body.

When you reject an underwriting issue:

  • currentBlockingPoint is set to Rejected
  • Both rejected and hasApprovalOrRejection are set to true

Reopening underwriting issues

Reopening an underwriting issue returns a previously approved or rejected underwriting issue to its open state. To reopen an underwriting issue, use the following endpoint:

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

The /reopen endpoint does not require a request body.

When you reopen an underwriting issue:

  • currentBlockingPoint is set to the default blocking point for the issue
  • hasApprovalOrRejection is set to false
  • If the issue was previous rejected, rejected is set to null