We have an opportunity for 4 data analysts. These positions allow clients provide electronic transaction and inforce files to the Data Management Team. This data is converted to a standard format, validated, mapped to Treaties, mapped to standard transaction codes and loaded to the data warehouse, PODs. The client transaction files are primarily used to update and communicate client premium payments and policy movement (new issues, terminations, renewals, and changes). The clients Inforce file is the client's statement of all coverages that they have ceded to as of a period end date.
The initial Inforce was created based on the client inforce record as of December 2003. Beginning in January 2004 the process of applying the client transaction files to the initial Inforce began and continued to update the Inforce. Inforce then runs a comparison between what the client reports as inforce, and what we have extrapolated from the transactions provided by the client. In a perfect scenario they should exactly match, however often times they do not. That is where the Inforce Administration Team steps in, and reviews the coverages that do not match.
We have documented situations where the client company has issued a coverage that the means or method they used to issue that coverage is not recognized by our current understanding of a chosen transaction type; in which case would not recognize that coverage. There are times when coverages are terminated, and again through either data logic, or client error, our system does not interpret the transaction correctly. We have categorized 6 different types (that sub-divide into over 100 individual categories) of client reporting variances that cause coverages to not process properly in our system. These client reporting variances combine with other systemic issues and are incorporated into 20 Root Cause categories that categorize all data anomalies.
Through understanding of the Data Load process, communication with our client company's and interfacing with any number of different departments within, researches the disconnects, identifies root causes and seeks solutions to correct any future misalignments. We also communicate to any of the impacted departments adjustments that might be necessary to correctly balance our records to reflect a more true and accurate picture of the risk that we have assumed and to validate premium payments for those coverages. On a monthly basis we meet with key departments and distribute a report detailing the current Inforce compare analysis for each eClient.
Through the analysis process we have developed relationships with, and touch many different areas within. We have also been able to build wonderful relationships with our client company's by seeking a mutual understanding of their individual processes. Through that understanding, we can further identify and address any number of data issues to provide a much more accurate accounting of the risk that we as a company have assumed.
Major Responsibilities :
Minimum Requirements/Skills :
Competencies/Desired Behavioral Characteristics :