In order for an agent to obtain potential renter information for screening, a renter must allow the release of their information. A renter completes the required steps, agrees to terms, pays and submits, releasing their file to their associated agent.
Only after a renter has paid and submitted are credit and background reports released to the agent. When reports are released, and if a report is available, a credit score will be visible.
This article describes possible reasons why the agent is not seeing a credit score:
This article provides details and next steps for the following:
- Dash (–)
- Report Off
- Not Enough Data
- Yellow X symbol
- Red exclamation point
- Credit Score = 1
- Credit Score = 4
- Credit Score = 9000
- Error: 9193 No record found Report
Dash (–)
When an application is part of a group, after the Primary applicant has paid, an agent is able to see the application data for the remaining applicants before those remaining applicants have paid and passed the TransUnion IDV.
In this example, the Roommate has not paid and submitted their application.
Since the TransUnion IDV happens when the applicant pays and submits, there is no score or credit reports. An agent should ask the applicant to login to complete and pay their application fee.
Report Off
In response to the California SB-267 when enabled, if a potential renter identifies that they receive a government rent subsidy, and they request that their credit history is not considered during the screening process, after submission, an agent will see the Report Off icon in place of a credit score.
Although the credit history report and score are not present, upon submission, the potential renter will still be required to complete the identity verification and the agent will receive any housing court records (eviction), and/or criminal records, when applicable.
When clicking on the report off icon, the agent will navigate to the credit history section of the Renter Resume as normal, however, since no score or credit history details will be present, the agent will see an empty state message.
The agent can scroll or use the left navigation bar to view background reports when present.
Not Enough Data
AKA: Thin File. Not Enough Data means that although the renter has successfully verified their identity by passing the TransUnion's IDV security step, the renter does not have enough credit history for TransUnion to generate a credit score.
There are a couple of reasons why an applicant may not have enough credit history to generate a
- The applicant has never used their credit or has very little credit history. This is typical of applicant's close to the age of 18 years old. An agent should check the applicant's date of birth.
- The applicant has a new social security number and has never used their credit or has very little credit history. An agent should understand if the applicant has a newly issued social security number.
The credit report may have additional identifiers reported to the bureau such as a previous address or employment. Clicking on Not Enough Data will take you to the renter's TransUnion credit report where you can view all personal data TransUnion has on record.
In very rare cases, the renter could have entered personal data incorrectly and while TransUnion may have been able to verify their identity, the report TransUnion returned is a "split file".
If you believe the renter may have a split file, the applicant should contact TransUnion to understand if there were any errors entered on their application causing an issue.
Yellow X symbol
The application has paid the fee submitted then immediately logged out of their Intellirent account without passing the TransUnion IDV.
The applicant should log back into their Intellirent account to complete the IDV. When the applicant logs back into their account they will see the {TransUnion IDV questionnaire}.
The renter should log back into their Intellirent account to complete the IDV. When the applicant logs back into their account they will see the TransUnion IDV questionnaire.
Red exclamation point
The applicant has paid the fee and submitted but they ran into an issue with the TransUnion IDV.
The applicant should log back into their account and follow the steps that are displayed to them in their application account. The applicant is further provided with Intellirent's Knowledge Base article, "{Error Message: Identity Verification, Action Required!}"
Agents/landlords should help ensure that their applicant contacts TransUnion as soon as possible, or you may also ask the applicant to choose the {International reports option}.
It's possible the applicant pay have incorrectly entered data or ran into a different issue that Intellirent could not immediately identify.
The applicant should reach out to Intellirent directly in order for us to better identify the cause and quickly return results.
*Note: If you see a red exclamation icon next to your applicant's credit score (see example below), this is an indicator of a Criminal/Eviction record.
Credit Score = 1
The renter for which this report was requested is deceased. If you believe this may be an error, please contact support.
Credit Score = 4
There is not enough relevant information to factor a score for the requested report, otherwise known as a thin file.
Credit Score = 9000
The requested report cannot be provided because it contains more than 500 tradelines, inquiries, and public records.
Error: 9193 No record found Report
There was a mismatch in the personal information provided by the applicant with what Experian has on file. Per Experian,
Experian uses a search and match engine for retrieving and loading consumer data onto the File One℠ Consumer Credit Database. The specific search and match algorithms used to retrieve a consumer record utilizes the key components of the consumer name and address along with any additionally provided information such as Social Security Number, telephone number, birth date, and/or driver’s license. The combination of name, address, Social Security Number are generally unique identifiers for a specific consumer and the architecture of the File One℠ database allows for the uniqueness of the data to be identified and used in the matching evaluation. However, the unique identity of a consumer is often complicated by human behavioral factors like misspellings, data-entry errors, etc. For this reason, Experian (and other credit reporting companies) use algorithms to assist in identifying logical variations of a consumer identity which complicate the matching process but also add flexibility in identifying a consumer across user applications and over time
Under FTC, clients are obligated to collect and provide accurate and complete information for identifying a consumer when pulling a credit report. The identifying information is used to search a reference repository for possible candidate “consumer” records, and then matches the input consumer identification data elements to the corresponding elements on the database to determine if there is a sufficient match to qualify the consumer. Therefore, the more complete and accurate identifying information provided on an inquiry by the client strengthening the match logic. Our system can provide credit report based upon minimal data, but in all cases, unless the provided information is a unique match to a consumer on our file, we will not return a report (a no hit will be returned). This is to accommodate FTC standards for protecting consumer privacy and ensuring that we are not delivering a credit information without permissible purpose.
Ultimately, the tighter protocols for matching an applicant to a credit file, and providing those reports to agents, is in the best interest of all applicants, agents, and owners.
Common invalid data entries include,
- Invalid SSNs, (e.g. incomplete SSNs, mistyped SSNs, etc.)
- Incomplete or invalid current addresses for applicants, (as a reminder, the current address field must always be that of a US address)
- Incorrectly formatted full names, (full first and last name are required, middle names are optional)
Still need help? Contact our live support team.
Comments
0 comments
Please sign in to leave a comment.