Change producer mid-term on a policy

In an agent portal, agents can transfer control of an existing policy from the current agent to another agent.

You can transfer control of a policy to another producer by processing a Producer Change transaction. This transaction can be done mid-term. After you transfer control of a policy to another producer, you can no longer access or modify the policy.

Use the following steps to process a mid-term producer change transaction:
  1. Identify the policy transaction.
  2. Gather the producer change details.
  3. Submit and process the producer change.

Identify the policy transaction

Initiating a mid-term producer change starts with an agent or agency deciding to transfer producer control on a policy. Then, you call an agent portal API to determine the types of transactions that are valid for a policy.

Process to identify the policy transaction.

After you select a Producer Change transaction, the agent portal must note the code value of the transaction, because this code value is required in a later step to request the transaction.

For example, you might configure the following steps:
  1. View the policy details:
    1. The portal submits the following API call:
      GET /policies/systemid
    2. The portal displays the policy details provided in the response.
  2. View the list of available transactions:
    1. The portal submits the following API call:
      GET /policies/systemid/availableTransactions
    2. The portal returns a list of available transactions based on the API response.
    3. The agent selects the Producer Change transaction.
    4. From the API response, the portal uses the value of the Producer Change option.
      [
  ...
  {
    "value": "Producer Change",
    "name": "Producer Change"
  },
  {
  "value": "Endorsement",
  "name": "Endorsement"
  },
  ...
]

Gather the producer change details

Before an agent portal can submit a Producer Change transaction request, the agent portal needs to gather the following details:
newProducerRef
The agent portal calls one of the following APIs to determine valid newProducerRef values:
GET /providers?providerTypeCd=Producer&inNetworkOnly=true
GET /providers?providerTypeCd=Producer&inNetworkOnly=true&agencyCd=MyAgency
or many other options within the GET /providers endpoint to find the producer to which you want to change. The agent then selects the appropriate code.
newSubProducerCd
Producer selected from the API endpoint might have sub-producers. If so, the portal can select the sub-producer that will control the policy. This value, if it exists, is listed in the subProducers object of the response. Determine the valid SubProducer.subProducerCd and use the value here.
effectiveDate
Date on which the producer change is to take place.
description
Optional short description of the reason for the mid-term producer change.
additionalDescription
Optional detailed description for the mid-term producer change.

Submit and process the Producer Change transaction request

Submitting and processing a producer change starts with the agent portal calling an API to initiate a producer change request. Then, the system creates an application and the agent processes the application.

Process to complete a mid-term producer change.
The following scenario is a typical Producer Change transaction cycle:
  1. Start the producer change transaction request:
    1. The portal executes the following API request:
      Endpoint POST /policies/systemId/startProducerChangeTransactionRequest
      Example Request Body 
      {
  "newProducerRef": "15",
  "newSubProducerCd": "",
  "effectiveDate": "2024-12-09",
  "description": "Producer is moving to another agency",
  "additionalDescription": "This policy needs to switch to the new producer right away."
}

      Provide the value of the Producer Change transaction, such as the newProducerRef and newSubProducerCd, from the previous endpoint GET /providers.

      Note: The other values differ based on agent selections.
    2. From the API response, note the systemID of the application in the location header:
      ...
  location: https://hostname/coreapi/v5/applications/systemID
...
  2. View the new application
    1. The portal executes the following API call:
      GET /applications/systemid
    2. The portal displays the Producer Change transaction details provided in the API response.
    3. The agent completes the transaction.