# Presentation: 160860

## Session 49 

***NSLDS***
***Helping You Find the Answers***

- Session 49-

## Presenters

**U.S. Department of Education**
**Pam Eliadis-NSLDS**
**Susan Morgan-NSLDS**
**Mary Lewis-Debt Collection**
**Bill Pranchke-Debt Collection**
**Guaranty Agency**
**Kay Morgan-Texas Guaranteed Student Loan Corporation**

- Session 49-

## Agenda

- What is NSLDS database?
- How is data loaded?
- What types of data conflicts will I see?
- What I should I do when I see a data conflict?
- What does the data provider do when I call?

- Session 49-

## Agenda

- What happens with Department-held loans at Debt Collection (DCS)?
- What is NSLDS doing to help me?

- Session 49-

## What is NSLDS?

- National database of title IV loans and grants established by the 1986 Amendments to the Higher Education Act
- FFEL
- FDSL
- Perkins
- Pell
- Information is updated monthly by data providers and in some cases weekly

- Session 49-

## Who provides the data? 

- FFEL data from tape dumps (initial load)
- ED-held portfolio from Debt Collection
- FFEL data from GAs
- Direct Loan data from Direct Loan Servicer
- Perkins Loan data from schools/servicers
- SSCR data from schools
- Pell Grant data from RFMS
- Demographic data from CPS

- Session 49-

## How big is NSLDS?

- Total Records			     3,088,855,059
- Students					  42,679,607
- Loans (FFEL, Direct, Perkins)	127,255,042
- Pell Grants (1993-present)	  28,667,211
- School Branches			         32,202
- Schools					         18,040
- Lenders						 31,093
- Guaranty Agencies				        60

- Session 49-

## How do we match data?

- Borrower Identifiers
- SSN
- Date of birth
- Name, primarily first

- Session 49-

## How do we match data? 

- Loan Identifiers
- Original school OPE ID
- Loan type
- Date of loan
- Indicator of separate loan (FFEL and Direct)
- PLUS borrower’s SSN (FFEL and Direct)

- Session 49-

## Identifier Conflicts

- Session 49-

**Notes:**
Identifier conflicts
SSN used by another student/parent
Name mismatch
DOB mismatch
Incorrect data on database
Data not updated 

## Incorrect Data on Database

- Session 49-

## Data Not Updated

- Session 49-

## What do I do about conflicts?

- Obtain the facts
- Gather the documentation
- Contact the dataprovider

- Session 49-

## Slide 14

- Session 49-

## Slide 15

- Session 49-

## Slide 16

- Session 49-

## Slide 17

- Session 49-

## Slide 18

- Session 49-

## What do I do about conflicts?

- Determine whether to award aid using authority of GEN-96-13
- if data provider is no longer viable or
- no immediate resolution
- Pursue correction of NSLDS database

- Session 49-

## FFEL Data and the GA

- GAs update NSLDS monthly
- report changes to existing loans
- status changes
- balances at least once per quarter, monthly by some
- report new loans

- Session 49-

## FFEL Data and the GA

- Data on NSLDS not updated
- Lender reporting to GA
- GA reporting to NSLDS
- Archived loans

- Session 49-

## FFEL Data and the GA

- Common approach to conflict resolution
- Common Manual
- NCHELP Operations Committee
- NCHELP/NSLDS Workgroup

- Session 49-

## FFEL Data and the GA

- Identifier Conflict
- when we change
- when we can’t change

- Session 49-

## FFEL Data and the GA

- Incorrect Data
- NSLDS says “DEFAULT,”  borrower says

- NO, NO

- Session 49-

## Direct Loans and the DL Servicer

- Correcting Direct Loan conflicts
- Fax information to:1 (800) 848-0984  Attn:  School Services or,
- Mail to:Direct Loan Servicing CenterAttn:  School ServicesPO Box 4609Utica  NY  13501

- Session 49-

**Notes:**
NOTE TO DAN:
  We changed the second date in your example so that the example would be of something that would not match in NSLDS and result in an identifier error.
  We don’t understand your second major item on this page, “Potential for no change.”

## NSLDS & DCS 

- Terminology
- DCS
- Subrogation
- Reporting from GAs, Direct Loans, and Perkins schools to DCS
- Monthly reporting to NSLDS

- Session 49-

## What is a Rolled Up Loan?

- Amount

- OPB

- Session 49-

## Types of ConflictsUnique to DCS

- Rolled up loans in one debt record
- Disbursements reported as loans
- Original provider reports differently to NSLDS than subrogation submission to DCS
- loans
- overpayments

- Session 49-

## If...       Then...

- You have a student with a conflict with DCS information:
- Please note:  This is not the point of contact for students.

- Contact the NSLDS Customer Service at:	1-800-999-8219
- Students contact the DCS Customer Service at:
- 	1-800-621-3115

- Session 49-

## Remember:

- Students must be referred to DCS Customer Service
- Schools must contact NSLDS Customer Service

- Session 49-

## What is NSLDS doing to help?

- NSLDS and DCS look for systemic errors
- DCS-created duplicate loans
- DCS cannot create loan on NSLDS database
- DCS use of loan status codes in their system versus NSLDS
- Transfer loans from DCS back to data provider
- Loan-level and account-level data
- NSLDS serving as data provider

- Session 49-

## Why is there no data provider?

- “Unowned” loan
- Closed GA still listed as current data provider
- Loan archived at data provider
- Identifiers entered incorrectly on NSLDS
- “Orphan” SSN

- Session 49-

## What do I do if there is no data provider ?

- Call NSLDS Customer Service
- 1-800-999-8219
- Provide your name, school name, and OPE ID
- Provide borrower’s identifiers
- Explain what is on NSLDS and what it should be

- Session 49-

## What do I do if there is no data provider ?

- E-mail NSLDS Customer Service
- nsldscoe@raytheon.com
- Do not include borrower’s identifiers
- Explain the situation
- Provide your name, school name, OPEID and your phone number

- Session 49-

## What do I do if there is no data provider ?

- You will be given a tracking number
- NSLDS will do preliminary research
- If NSLDS must correct the data
- Documentation must be provided by mail or fax
- Give Us Time To Correct NSLDS

- Session 49-

## NSLDS Customer Service

- 1-800-999-8219
- Call between the hours of 8:00 a.m. and 8:00 p.m. ET any weekday other than Federal holidays.
- Or, e-mail:  nsldscoe@raytheon.com

- Session 49-