The Ownership Transfer interface provided by ALIP, on receiving arequest for a Custodian to Custodian Transfer, performs necessary validations, invokesthe needed ALIP API, transfers the custodian on the contract along with other associated roles, and returns the status response.
Below are the input parameters, that this interface accepts as input:
Contract Number
Source Custodian Information
Servicing Agent Information
Writing Agent Information
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 shall be used to communicate. |
| TR2 | The external system will send an Ownership Transfer request message for a custodian, in the ACORD XML format to ALIP Process Server’s Request Queue. (TransTypetc=”186”). This message will be picked up and processed by the ALIP process server. |
| TR3 | The Contract Numberreceived in the requestwill be used to invoke ALIP API for performing the needed Ownership 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 database tables. |
| BR ID# | Business Requirements |
| BR1 | ALIP will apply the following business validations on the input request.Contract should exist in ALIPContract should not be ‘Pending’, not Annuitized, not Restricted and should not have any pending or processed Death ClaimsThe Custodian Agreement Approval Date i.e. Policy Effective Dateis prior tothe Transaction Received date.There should be no active SEPP Distribution Schedule events on the contract.The source party should be present in ALIPIf Source Party is a Custodian then the Target Party must be a CustodianClient types for custodians should be set correctly (2)Agents sent in the input, should exist in ALIPTotal allocation of all agents should be 100. |
| BR2 | If all the needed validations are satisfied, the interface will terminate existing Owner, Primary Beneficiary on the Contract and use the received Custodian to create a new Custodian Owner on the Contract. |
| BR3 | ALIP will use the received Servicing Agent ID to create new Servicing Agent role on the policy. Along with the Agent ID for Servicing Agent, allocation percentage will also be received and ALIP will use the same percentage to establish the Servicing Agent. |
| BR4 | ALIP will go through each Writing Agent's Agent ID in the input and use that corresponding client from ALIP database to establish them as Writing Agents on the policy. Along with each Agent ID, ALIP will receive corresponding allocation Percentage of Writing Agent on the policy which is to be updated. |
| BR5 | All scheduled events (Systematic withdrawal/RMD) on the contract will be terminated post transfer. |
| BR6 | The success or failure response would be transformed back to ACORD format and sent back to the calling system |
ALIP will receive a new request for a Custodian To Custodian transfer scenario, on the Alip Request Queue.
The ALIP process server will pick up the message, and use the Contract Number received in the request, to invoke the needed 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 interfacewill terminate existing Owner, Primary Beneficiary on the Contract and use the received Custodian to create a new Custodian Owner on the Contract after performing needed validations.
The following additional processing will be done, post creation of the new custodian owner, as defined in the business requirements.
The received Servicing Agent ID will be used, to create a new Servicing Agent role on the policy.
The interface will iterate through each Writing Agent's Agent ID in the input and use that corresponding client from the ALIP database to establish them as Writing Agents on the policy.
Allocation percentage received for the Servicing Agent and each Writing Agent, will be established on the new Servicing Agent and Writing Agents respectively.
Associated scheduled events on the contract will be terminated post transfer.
The success or failure response would be transformed back to ACORD format and sent back to the calling system.
None
Any Custodian that is being added to a policy through this interface is expected to be already part of ALIP database.
Owner and Primary Beneficiary should be same in the source Custodian.
NA
An average response time of under 5 secondsis expected for this interface.
| Request Parameters | Description | Mandatory | Allowed values |
| Contract Number | A number which uniquely identifies a Contract within ALIP. | Y | Detailed in the attached Data Elements. |
| Custodian Information | Source CustodianInformation. | 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 | Y | Detailed in the attached Data Elements. |
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Custodian to Custodian 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 Custodian to Custodian transferrequest was successful with details being returned in the output. | Success | Informational | |
| #2 | The Custodian to Custodian Transfercall wasNOT successfuldue to technicalerrors. | Internal Error | Fatal | |
| #3 | The Custodian to Custodian transfercall was NOT successful due to the contract not being present in ALIP. | Failure | Warning | |
| #4 | The Custodian to Custodian Transfer request was NOT successful, due to XSD failure. | Failure | Warning | |
| #5 | The Custodian to Custodian Transfer request was NOT successful, due to Contract being in a status where Custodian cannot be added i.e Pending or Annuitized or Restricted | Failure | Warning | |
| #6 | The Custodian to Custodian Transfer request was NOT successful, due to Contract consisting of pending or processed Death Claims | Failure | Warning | |
| #7 | The Custodian to Custodian Transfer request was NOT successful, due to Contract having active SEPP Distribution schedule events | Failure | Warning | |
| #8 | The Custodian to Custodian Transfer request was NOT successful, due to Custodian not existing in ALIP | Failure | Warning | |
| #9 | The Custodian to Custodian Transfer request was NOT successful, due to Transaction Execution Date being lesser than Contract Issue Date | Failure | Warning | |
| #10 | The Custodian to Custodian Transfer request was NOT successful, due to Agent not existing in ALIP | Failure | Warning | |
| #11 | The Custodian to Custodian Transfer request was NOT successful, due to allocation percentage of agents not totaling 100 | Failure | Warning | |
| #12 | The Custodian to Custodian Transfer request was NOT successful, due to source and target parties being of different types | Failure | Warning | |
| #13 | The Custodian to Custodian Transfer request was NOT successful, due to the custodian in the source not having the right client type | Failure | Warning |