Rewrite and Rewrite New Account

A rewrite is a policy transaction that creates a new policy from an existing policy. Typically, a rewrite is done when some significant error occurred during the initial submission of policy. The original policy does not reflect the original intent of policy, and a new set of policy documents showing correct information is required.

A rewrite new account is a policy transaction that takes data from an existing policy and creates a new policy with a new policy number in new account. Rewriting a policy to another account means moving the policy going forward to another account, but the policy history including earlier policy terms stay with its current account.

This topic covers how to manage rewrites through Cloud API. For details on the business functionality of rewrites, see the Application Guide.

There are three types of policy transaction rewrites:

Full term rewrite: Overwrites the entire term of an existing policy
New term rewrite: Creates a new term for the policy
Mid-term rewrite: Rewrites the remainder of an existing policy term

The full term and new term policy rewrites are called flat rewrites.

With the system APIs, a policy rewrite transaction is preceded by a cancellation policy transaction. When canceling a policy in preparation for a rewrite, the value provided for the cancellationReasonCode property must be either flatrewrite or midtermrewrite, as described above. When rewriting the policy, the value provided for the rewriteType property must be either rewriteFullTerm, rewriteNewTerm, or rewriteRemainderOfTerm, as described above.


Rewrite period	`cancellationReasonCode` property value	`rewriteType` property value
Full term	`flatrewrite`	`rewriteFullTerm`
New term	`flatrewrite`	`rewriteNewTerm`
Mid-term	`midtermrewrite`	`rewriteRemainderOfTerm`

Overview of policy transaction management

Work with policy transactions typically involves endpoints from two different APIs:

The Policy API, which has endpoints to:
- Initiate all types of policy transactions except for submissions
The Job API, which has endpoints to:
- Initiate submissions
- Modify the contents of a policy (such as its coverables, coverages, and policy contacts)
- Quote jobs
- Bind and issue jobs, or withdraw jobs
- Work with objects owned by jobs, such as activities and underwriting issues

Conceptually, a policy transaction is completed in four steps:

Initiate the policy transaction.
- This creates a new Job element whose status is "Draft".
Modify the job as needed.
- The status remains "Draft".
Quote the job.
1. The rating engine or rating service generates a quote for the job.
2. The status advances to "Quoted".
3. The job can be modified at this point. But if it is modified, the policy transaction falls back to the previous step. In other words, the status reverts to "Draft" and the job must be later requoted.
Complete the job.
1. This can be done by binding the job or by withdrawing or canceling the job.
2. The status advances to "Bound", "Declined", or "Withdrawn", depending on the outcome and job type.

Rewrite transaction

The rewrite policy transaction can be executed on a canceled policy.

Initiate the rewrite policy transaction.
- Submit a POST request to the /policy/v1/policies/{policyId}/rewrite endpoint
- The request payload must contain a value for the rewriteType property. Acceptable values are rewriteFullTerm, rewriteNewTerm, and rewriteRemainderOfTerm.
```
{
  "data": {
    "attributes": {
      "rewriteType": {
        "code": "RewriteFullTerm"
      }
    }
  }
}
```
- The response payload contains the associated job, which is in Draft state. Use the job ID in subsequent calls.
Revise the job as needed, to reflect changes to the policy. (For more information on how to modify a policy within the context of a job, see Overview of modifying jobs.)
Generate a quote.
Submit a business action POST to the /job/v1/jobs/{jobId}/quote endpoint.
Complete the policy transaction.
Submit a business action POST to the /job/v1/jobs/{jobId}/bind-and-issue endpoint.

Rewrite new account transaction

Initiate the rewrite new account policy transaction.
Submit a POST request to the /policy/v1/policies/{policyId}/rewrite-account endpoint. The request payload must contain a valid account ID value for the account.id property.
```
{
  "data": {
    "attributes": {
      "account": {
        "id": "pc:102"
      }
    }
  }
}
```
The response payload contains the associated job, which is in Draft state. Use the job ID in subsequent calls.
Revise the job as needed, to reflect changes to the policy.
Generate a quote.
Submit a business action POST to the /job/v1/jobs/{jobId}/quote endpoint.
Complete the policy transaction.
Submit a business action POST to the /job/v1/jobs/{jobId}/bind-and-issue endpoint.