The Ownership Transfer interface provided by ALIP, on receiving a request for an Agent to AgentTransfer, performs necessary validations, invokes the needed ALIP API, transfers the agent on the contract and returns the status response.
Below are the input parameters, that this interface accepts as input:
Contract Number
Servicing Agent Information
Writing Agent Information
As of Date
Primary Producer Indicator
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 shall be used to communicate. |
| TR2 | The external system will send an Ownership Transfer request message for an agent, in the ACORD XML format to ALIP. (TransTypetc=”161”). This message will be picked up and processed by the ALIP API processing server. |
| TR3 | The Contract Number received in the request will be used to invoke ALIP API for performing the needed Transfer. If there are any issues finding the contract, it will be returned as a failure response. |
| TR4 | Any failure during the Ownership Transfer will be treated as an Integration Failure in ALIP system and will be stored in the Integration history database tables. |
| BR ID# | Business Requirements |
| BR1 | ALIP will apply the following business validations on the input request.Contract should not be ‘Pending’, not Annuitized, not Restricted and should not have any pending or processed Death ClaimsAgents sent in the input, should exist in ALIPTotal allocation of all servicing agents should be 100Total allocation of all writing agents should be 100 |
| BR2 | If all the needed validations are satisfied,the interface will terminate existing Servicing Agent and/or Writing Agent on the Contract and use the received Servicing Agent ID and/or Writing Agent to create a new Servicing Agent and.or Writing Agent on the Contract with the incoming percentage details. |
| BR3 | The success or failure response would be transformed to ACORD format and sent back to the calling system |
| BR4 | ALIP will send an error response if any incoming Agent in the transfer request doesn’t exist in ALIP. |
| BR5 | ALIP Transfer API will support transfer from one-many Servicing Agents to one-many Servicing Agents. Percentage split across the incoming Agents should equal to 100. |
| BR6 | ALIP Transfer API supports accepting "As of Date" in the input request. The Agent transfer should be performed "as of the input date" as opposed to the current system date, if this value is provided. |
| BR7 | ALIP must ensure that the "As of Date" in the input request is not prior to the "Contract Issue Date". ALIP will send an error response if "As of Date" in the input request is prior to the "Contract Issue Date". |
| BR8 | ALIP Transfer API optionally accepts the ‘Primary Producer’ indicator for the incoming Agents and stores it appropriately at the role level information on the contract. |
ALIP will receive a new request for an Agent To Agent transfer scenario.
The ALIP API processing server will pick up the message, and use the Contract Number received in the request, to invoke the ALIP APIs. If there are any issues finding the contract, an Integration Failure would be created and stored in ALIP.
If the contract exists in ALIP, additional needed business validations as defined in the Business Requirements will be run, after which the interface will terminate existing Servicing Agent and/or Writing Agent on the Contract and use the received Servicing Agent ID and/or Writing Agent to create a new Servicing Agent and/or Writing Agent on the Contract after performing needed validations. The percentage details sent in the input will be used.
The success or failure response would be transformed back to ACORD format and sent back to the calling system.
None
Any Agent that is being added to a policy through this interface is expected to be already part of ALIP database.
An average response time of under 5 seconds is expected for this interface.
NA
| Request Parameters | Description | Mandatory | Allowed values |
| Contract Number | A number which uniquely identifies a Contract within ALIP. | Y | Detailed in the attached Data Elements. |
| Servicing Agent Information | Servicing Agent Information | Y | Detailed in the attached Data Elements. |
| Writing Agent Information | Writing Agent Information | Optional | Detailed in the attached Data Elements. |
| As of Date | As of Date | Optional | Detailed in the attached Data Elements. |
| Primary Producer Indicator | Primary Producer Indicator | Optional | Detailed in the attached Data Elements. |
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Agent to Agent transfer is complete and Success response is displayed in Outbound External on Integration History Page | 1 | Success | Informational |
| Error | Error Scenario Description | Message Description | Message Type | Additional Comments |
| #1 | The Agent Transferrequest was successful withdetails beingreturned in theoutput. | Success | Informational | |
| #2 | The Agent Transfer call was NOT successful due to technical errors. | Internal Error | Fatal | |
| #3 | The Agent Transfercall wasNOT successfulas Contract does not exist in ALIP. | Failure | Warning | |
| #4 | The Agent Transfer request was NOT successful, due to XSD failure. | Failure | Fatal | |
| #5 | The Agent to Agent Transfer request was NOT successful, due to Contract being in a status where non--Custodian transfer cannot happen i.e Pending or Annuitized or Restricted | Failure | Fatal | |
| #6 | The Agent to Agent Transfer was NOT successful, due to Contract consisting of pending or processed Death Claims | Failure | Fatal | |
| #7 | The Agent to Agent Transfer request was NOT successful, due to Agent not existing in ALIP | Failure | Fatal | |
| #8 | The Agent to Agent Transfer request was NOT successful, due to allocation percentage of all servicing/writing agents in input not being 100. | Failure | Fatal | |
| #9 | The Agent to Agent Transfer request was NOT successful, As of Date" in the input request is prior to the "Contract Issue Date". | Failure | Fatal |