Social Security Administration Randomization of SSN Issuance Impact to LexisNexis Accurint XML Accurint XML Workflow and XML Tags

Transcription

1 Social Security Administration Randomization of SSN Issuance Impact to LexisNexis Accurint XML Accurint XML Workflow and XML Tags Overview The Social Security Administration (SSA) recently announced they will be changing their method for assigning social security numbers (SSN) to a randomized approach effective June 25, Under the current approach, SSNs are methodically assigned according to a specific format based on published ranges associated with the state (or area of issuance) and the time frames of issuance. This methodical assignment allowed for several risk assessments to be conducted when evaluating the validity of a SSN as well as the ability to return the SSN issuance information. Impact to Accurint XML Customers LexisNexis will continue reporting the SSN issuance information and risk assessments for SSNs that can be validated as being created prior to June 25, However, all SSNs that cannot be validated as being created prior to June 25, 2011 will be marked as a Randomized SSNs (via a new high risk indicator (HRI)). Planned Enhancements In addition, Accurint XML will include new insight (via another new HRI) that will identify consumers that were reported to be using an invalid SSN prior to the change on June 25, This HRI will be returned when an SSN, that cannot be validated as being created before June 25, 2011, was associated with the consumer prior to June 25, 2011 and was known to be invalid at that time. This addition will help preserve the risk assessment capabilities associated with SSN validation for consumers who are currently using invalid SSNs.

2 Impact to High Risk Indicators Impacted HRIs Risk Indicator Text Summary 0003 The input SSN was issued prior to the input date-of-birth UPDATED: 0006 Current Text: SSN is invalid or not yet issued Updated Text, effective June 25, 2011: SSN is invalid LexisNexis can no longer determine if the input SSN has been issued, so we will change the text description for this risk indicator. WILL BECOME OBSOLETE: 0039 SSN is recently issued This risk indicator will become obsolete shortly after the change by the SSA is implemented SSN was issued to a non-us citizen 0089 SSN was issued within the last three years 0090 SSN was issued after age five (post-1990) NEW: 0155 SSN potentially randomly issued by the SSA For designated searches, this new risk indicator will be returned when an input SSN cannot be validated as being created prior to June 25, 2011 (more specifically, it does not match a published valid SSN block group sequence). NEW: 0160 SSN potentially randomly issued by SSA, but invalid when first associated with the consumer For designated searches, this new High Risk Indicator will be returned when an input SSN cannot be validated as being created prior to June 25, 2011, but was first associated with the input identity prior to June 25, 2011 and was invalid at that time.

3 Impact to Accurint XML Tags Below we are offering examples of two common Accurint searches to demonstrate how an XML response might change based on SSN randomization. In the columns, we provide: XML Search Name Two common Accurint searches. Legacy SSN Valid responses for SSNs issued by the SSA prior to June 25, 2011 and invalid responses for SSNs that do not pass SSA SSN formatting rules. Randomized SSN Valid and invalid responses for potentially randomized SSNs issued by the SSA on or after June 25, Note: This XML code is for example purposes only; many different SSN conditions can return an array of different XML Tags, as well as XML Tag Values. XML Search Name VALID Legacy SSN VALID Randomized SSN BpsSearch: <Valid>yes</Valid> <IssuedLocation>Georgia</IssuedLocation> <IssuedStartDate> <Year>1990</Year> <Month>01</Month> <Day>01</Day> </IssuedStartDate> <IssuedEndDate> <Year>1991</Year> <Month>12</Month> <Day>31</Day> </IssuedEndDate> <Valid>yes</Valid> NOTE: Due to SSN randomization, the following information cannot be determined (after June 25, 2011) and the associated XML tags will NOT be returned for Randomized SSNs: Issue Location, Issue Start Date, and Issue End Date

4 XML Search Name INVALID Legacy SSN INVALID Randomized SSN BpsSearch: <Valid>no</Valid> <Valid>no</Valid> NOTE: Similar behavior may be found in other searches. XML Search Name VALID Legacy SSN VALID Randomized SSN RollupPersonSearch: <Valid>G</Valid> <IssuedLocation>Georgia</IssuedLocation> <IssuedStartDate> <Year>1990</Year> <Month>01</Month> <Day>01</Day> </IssuedStartDate> <IssuedEndDate> <Year>1991</Year> <Month>12</Month> <Day>31</Day> </IssuedEndDate> <Valid>G</Valid> <RiskIndex>0155</RiskIndex> <Description>SSN was possibly randomly issued by the SSA.</Description> NOTE: Due to SSN randomization, the following information cannot be determined and the associated XML tags will NOT be returned for randomized SSNs: Issue Location, Issue Start Date, Issue End Date or High Risk Indicators (3, 39, 85, 89, 90)

5 XML Search Name INVALID Legacy SSN INVALID Randomized SSN RollupPersonSearch: <SSN> </SSN> <Valid>B</Valid> <RiskIndex>0006</RiskIndex> <Description>SSN is invalid</description> <RiskIndex>0150</RiskIndex> <Description>SSN not recently reported for subject.</description> <Gender>Male</Gender> <Valid>B</Valid> <RiskIndex>0160</RiskIndex> <Description> SSN potentially randomly issued by SSA, but invalid when first associated with the consumer.</description> <RiskIndex>0150</RiskIndex> <Description>SSN not recently reported for subject.</description> NOTE: A randomized SSN can ONLY be INVALID due to High Risk Indicator 0160 (see table above for definition.) Similar behavior may be found in other searches. LexisNexis Accurint XML does not constitute a consumer report as that term is defined in the federal Fair Credit Reporting Act, 15 USC 1681 et seq. (FCRA). Accordingly, LexisNexis Accurint XML may not be used in whole or in part as a factor in determining eligibility for credit, insurance, employment or another permissible purpose under the FCRA. Due to the nature of the origin of public record information, the public records and commercially available data sources used in reports may contain errors. Source data is sometimes reported or entered inaccurately, processed poorly or incorrectly, and is generally not free from defect. This product or service aggregates and reports data, as provided by the public records and commercially available data sources, and is not the source of the data, nor is it a comprehensive compilation of the data. Before relying on any data, it should be independently verified. LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier Properties Inc., used under license. Accurint is a registered trademark of LexisNexis Risk Data Management Inc. Other products and services may be trademarks or registered trademarks of their respective companies. Copyright 2011 LexisNexis Risk Solutions. All rights reserved.