> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nextlevelmca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I pull an owner's credit?

> Connect your own CRS account and soft-pull a deal owner's credit from Experian, TransUnion and Equifax.

From a deal's **Underwrite** tab you can pull an owner's personal credit from Experian, TransUnion and Equifax through **CRS**. It's a **soft pull**: it doesn't affect the owner's credit score. Pulls run on **your own CRS account**, and CRS bills that account for each bureau pulled.

<Note>
  Connecting CRS needs Settings access (admins, or a role that includes it). Pulling credit needs the **Pull Credit** permission, which admins and managers have by default. Anyone who can see a deal can see its results.
</Note>

## Before you pull: authorization

You need the owner's permission to obtain their credit report.

* **When the owner e-signed your application in the last 120 days**, the pull uses that signature.
* **Otherwise**, you confirm you have their signed credit authorization before pulling. The confirmation is recorded with your name and the time.

Your application's disclaimer is what authorizes the pull, so make sure it covers credit reports. The default text does. If you've written your own under **Settings → General → Branding → PDF authorization disclaimer**, that field reminds you, and warns you when your text doesn't mention credit.

## Connect your account

<Steps>
  <Step title="Get your CRS API login">
    The username and password are in your CRS (FinStack) portal. Contact CRS if you don't have an account yet.
  </Step>

  <Step title="Open Settings → Integrations">
    On the **CRS** card, click **Connect**.
  </Step>

  <Step title="Enter your login">
    Fill in **CRS username** and **Password**, then click **Connect & test**. The login is stored encrypted, checked once, and never shown again.
  </Step>

  <Step title="Choose the bureaus and the score">
    Back on the CRS card, switch on the bureaus every pull should use (**Experian**, **TransUnion**, **Equifax**, at least one) and pick the **Score model**: **VantageScore 4.0** or **FICO Score 9**. These apply to every pull in your workspace.
  </Step>
</Steps>

Each bureau is its own pull, billed by CRS, so three bureaus cost three pulls. The CRS card in Settings has **Test**, **Replace** and **Disconnect**, and a switch in its header to turn credit pulls off without forgetting the login.

## Pull an owner's credit

The **Credit** card is on the deal's **Underwrite** tab, next to DataMerch and PACER. It lists each owner on the deal.

<Steps>
  <Step title="Check the owner's details">
    An owner needs a full name, a home address, and an SSN or a date of birth. If something is missing, the card says what to add: edit the owner on the deal's **People & Business** tab. An SSN gives the most reliable match.
  </Step>

  <Step title="Click Pull credit">
    The card shows which bureaus and score model will be used, and how many pulls CRS will bill.
  </Step>

  <Step title="Confirm the authorization if asked">
    If the owner hasn't e-signed recently, tick **I have a signed authorization from this owner to obtain their credit report for this funding request.**
  </Step>

  <Step title="Pull">
    Click **Pull credit**. The bureaus answer within a few seconds.
  </Step>
</Steps>

## Reading the results

* **The qualifying score** is the large number on the right: the middle of three scores, or the lower of two. It replaces the owner's credit score on the deal, so [lender matching](/help/match-score) uses it. The deal's activity log shows the old and new score.
* **Each bureau's score** shows as a chip, for example **EXP 671**. Click it to open that bureau's full report.
* **Key facts** from the report: revolving utilization, length of credit history, past-due balances, late payments, charge-offs, collections, inquiries and any bankruptcy (open or closed). Red and amber mark the ones lenders usually care about.
* **What's holding the score down** lists the bureau's reasons for the score.
* **Bureau alerts**, such as an address that doesn't match the bureau's file, are listed when there are any.

The full report shows every account (only the last 4 digits of each account number), inquiries and public records. It's fetched from CRS when you open it. NextLevel MCA keeps the scores and key facts, not the report itself, and there's no PDF.

## Pulling again

* **Pull again** on an owner gets a fresh report from each bureau, even within the same day. CRS bills each pull.
* A renewal is a new funding request: pull again rather than relying on an old report.
* Every pull and every report you open is written to the deal's activity log.

## Common problems

<AccordionGroup>
  <Accordion title="There's no Credit card on the Underwrite tab">
    The card only shows when CRS is connected and switched on. Someone with Settings access connects it, or turns its switch back on, under **Settings → Integrations**. People with that access see a line on the Underwrite tab naming what isn't connected yet. A deal pulled before CRS was disconnected or turned off still shows those results, read-only.
  </Accordion>

  <Accordion title="There's no Pull credit button">
    Either the owner is missing details (the card says which), or you don't have the **Pull Credit** permission. Ask an admin to turn it on for you under **Settings → Team**.
  </Accordion>

  <Accordion title="A bureau returned no file">
    The owner's credit may be frozen at that bureau. Ask them to lift the freeze, then click **Pull again**. If the bureau said why it couldn't return a file, for example a missing SSN, the card shows its message instead.
  </Accordion>

  <Accordion title="A bureau failed">
    The card shows what went wrong for that bureau, for example CRS rejected the login or isn't responding. The other bureaus' scores still show. If the login was rejected, ask someone with Settings access to **Test** the connection and **Replace** the login if it changed.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.