Accenture Life Insurance Platform (ALIP) will receive Custodians (ACORD 186) requests from external system as a real-time call. ALIP should save the received data as a new client or update an existing client in the CRM schema based on the Message Transaction Type and Transaction Sub type.
Client Type will always be 'Company' and Company Type will be ‘Custodian’ for this interface.
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 shall be used to communicate between ALIP and external system. |
| TR2 | The externalsystem will place anCreateUpdateCustodianrequest message in the ACORD XML format, to the ALIP Request Queue. (TransTypetc=”186”, and TransSubTypetc=”18600”) |
| TR3 | ALIP’s Process Server would receive the message and validate the incoming request. This will include XSD validations, existence check for the contract in ALIP and any other business validations based on the corresponding business requirement. |
| TR4 | If there are any issues with validation, it will be returned as a failure response and will also be stored as an Integration Failure in the ALIP system. |
| TR5 | After successful validation, the Integration interface would save the CustomAttributes in ALIP’s Contract tables. |
| BR ID# | Business Requirements |
| BR1 | The external systemwould sendan CreateUpdateCustodianRequest in ACORD format to ALIP. |
| BR2 | On successful processing, a success response message would be sent by ALIP to the client system. |
| BR3 | Any failure or error should be sent as an error response by ALIP to the client system. |
| BR4 | For termination date update, a check should be performed to verify thattermination date for the given distribution channel is less than the current system date. |
| BR5 | For approval date update, a check should be performed to verify thatapproval date for the given distribution channel is not same or earlier than the original approval date |
ALIP will receive a ACORD request for custodian import, in the Alip Request Queue.
The ALIP process server will pick up the message, validate the request against the XSD and perform necessary validations.If there are any issues finding the custodian data to be create / update, an Integration Failure would be created and stored in ALIP.
In case there is no failure, the request will be processed and the custodian will be saved in the ALIP database.
If the Custodian does not exist in ALIP, a new Custodian will be created, If the Custodian in the incoming request already exists in ALIP, it will be updated with the incoming details.
ALIP will convert the response from ALIP format to ACORD and send it back to ALIP response queue.
None
Custodian import is a 'send and wait' integration. A response is expected by the external system for the request that was sent to ALIP.
Any failures in the processing of this interface in an Integration Failure and a response will be returned to external system.
The custodian’s custodial approval date for the given distribution channel can change. It can only be earlier than the original approval date. If it is after the original Approval Date, an error will be returned to external system.
The interface currently supports to save a maximum of twenty-five distribution channels per Custodian in ALIP. If it receives more than twenty-five distribution channels per custodian in the request, an error will be returned to external system and no subsequent processing will occur within ALIP.However the interface provides the ability to configure any other number of distribution channel also, based on Client’s requirement.
Custodians will have only one permanent address in ALIP, i.e. custodian will not have any mailing or seasonal address and will not have more than one permanent Address.
ALIP will receive all applicable distribution channels pertaining to each custodian in the request. For an existing custodian in ALIP, this interface will delete all existing distribution channels and recreate them with the received distribution channels from the request.
NA
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | Custodian create /update successfully | 1 | Success | Informational | Successful entry will be logged on the integration history page. |
| Error | Error Scenario Description | Message Description | Message Type | Additional Comments |
| #1 | Custodian Import interface was NOT successful due to technical errors. | Internal Error | Fatal | Technical Error |
| #2 | Custodian create /updatefail due to mandatory fields like -Custodian Name, Address, TIN, Cert Date, Distribution Channel, Approval Date missing from the request. | Internal Error | Fatal | For example, if address is missing then validation error - “Address1 is Required” will be received.’”Same for other missing fields. |
| #3 | Incoming approval date for the distribution channel does not match existing approval date | Internal Error | Information | A validation error - ‘Approval date is not valid for |
| #4 | Incoming termination date for the distribution channel does not match existing termination date | Internal Error | Information | A validation error -Termination date is not valid for < Distribution ChannelName name>.’” will be received.’” |
| #5 | Custodian create / update fail due to invalid Tax ID | Internal Error | Fatal | A validation error -TransType' is not valid with respect to its typewill be received.’ |
| #6 | Custodian create / update fail due to distribution channels are more than 25 | Internal Error | Fatal | XSD error will be received. |
| xsd |