<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 19%" />
<col style="width: 0%" />
<col style="width: 8%" />
<col style="width: 3%" />
<col style="width: 8%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="13"><strong>Student’s Social Security Number</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="2"><strong>Loan Identifier</strong></td>
<td colspan="2"><strong>History Kept</strong></td>
<td><strong>Reason-ability</strong></td>
<td colspan="3"><strong>Date Sequence Edit</strong></td>
<td colspan="2"><strong>Type</strong></td>
<td><strong>Size</strong></td>
<td><strong>Position</strong></td>
<td><strong>Field Code</strong></td>
</tr>
<tr class="even">
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="3">No</td>
<td colspan="2">Character</td>
<td>9</td>
<td>4-12</td>
<td>021</td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Description</strong></td>
<td colspan="8">Title IV aid recipient or beneficiary’s Social Security
Number.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Comments</strong></td>
<td colspan="8"><ul>
<li><p>May be a real or pseudo Social Security number (SSN). A pseudo
SSN may not be used in place of a real one if the Data Provider has the
valid SSN.</p></li>
<li><p>Whenever a real SSN is located for a borrower, the Data Provider
must change the Pseudo SSN to the real SSN.</p></li>
<li><p>SSN history should be maintained during SSN changes and updates.
All student loan records should be merged into the current SSN by using
the current and new identifier fields.</p></li>
<li><p>Where a real SSN is not on file, a pseudo SSN must be generated
for the record, as follows:</p></li>
</ul>
<ul>
<li><p>The first position of the SSN must contain a ‘9’ to clearly
identify the record as a pseudo SSN. The second through fourth positions
must contain the Guaranty Agency’s code. Pseudo SSNs <em>must be
unique</em> to each student, so one student’s records can be
distinguished from another’s. Using the Guaranty Agency’s code will help
ED to distinguish the pseudo SSNs reported by different
agencies.</p></li>
<li><p>If a pseudo SSN is used, it may not be substituted for a real SSN
if the Data Provider has the real SSN.</p></li>
<li><p>If a pseudo SSN is used, populate the student’s SSN Indicator
(Field 074) with a ‘P’.</p></li>
</ul>
<ul>
<li><p>When a loan is transferred to your agency from another and it
identifies the student with a pseudo SSN, do not change the Guaranty
Agency Code portion of the number that represents your own agency’s
code. This will create a new record.</p></li>
<li><p>Whenever a Social Security Number is reported, the system checks
whether the number has already been reported to NSLDS. If not, the
student is added to NSLDS. If it was previously reported, NSLDS uses the
following match logic to confirm the identity of the person.</p></li>
</ul>
<p>1. First Name and Date of Birth (DOB) matches.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Three of first four characters of first name on incoming record
(excluding punctuation and spaces) match three of four characters of
first name (excluding punctuation and spaces) in NSLDS (current or
history), or alias matches exactly. The letters must match in the same
sequence. If fewer than three characters, all characters must
match;<br />
and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<blockquote>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary would match, as “ary” is in same sequential order. So would Maty
and Mary, as “may” is in the same sequential order.</p>
</blockquote>
<p>2. Transposed first name and last name with DOB match.</p>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Three of the first four characters of last name on incoming
record (excluding punctuation and spaces) match three of first four
characters of first name (excluding punctuation and spaces) in NSLDS
(current or history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<p>3. Match on first initial of first name when NSLDS’ first name is
only an initial and no other first names exist in NSLDS.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Incoming first name begins with same letter as NSLDS’ first
initial (a name that is an initial only or an initial followed by a
period, not a comma, and no first name in history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Exact match and is not a plug date: 19000101, 18991231, 18581117,
19581117, 19040404, 19600101, or 19??1111, where ?? can be any year.
(Note: If both incoming and NSLDS have same plug date, this is
considered an exact match.)</p></li>
</ul>
<p>4. Match on first initial and part of last name with DOB match.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>First character of first name matches first character of first
name or first initial (current or history); and</p></li>
</ul>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Five of first seven characters of last name (excluding
punctuation and spaces) match five of first seven characters of last
name (excluding punctuation and spaces) in NSLDS (current or history).
If fewer than five characters, all characters must match; and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
<li><p>For loans or grants made before 1-1-1997, incoming DOB is plug
date and NSLDS DOB is a real date.</p></li>
</ul>
<blockquote>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary would match, as “ary” is in same sequential order. So would Maty
and Mary, as “may” is in the same sequential order.</p>
</blockquote>
<p>5. Match on student SSN and a single loan is found using the
non-student related identifiers. This loan was last reported on by the
current provider.</p>
<ul>
<li><p>When this Loan Identifier information changes, leave the existing
value in this field and report the new value in the New Student’s Social
Security Number field (e<em>.</em>g., its counterpart New Identifier).
Do this until the updated information is accepted by NSLDS. Once
accepted, the updated value is reported in the standard Loan Identifier
field and the New field is filled with the default value (zeroes or
blanks).</p></li>
<li><p>Changes made to Loan Identifier fields are mapped as a block, so
when the information contained in one of the key data elements is
changed, the information belonging in all of them must be re-confirmed.
Therefore, fill all the New Identifier fields (listed below) for this
loan with the values that they should contain − whether those values are
new ones or the ones that you have been reporting all along.</p></li>
<li><p>Changes made to Identifiers are processed before Past Period
Change records are processed. Therefore, if you are submitting an
Identifier change and a PPC against the same loan record in the same
reporting cycle, the PPC should refer to the New Identifiers, not the
old. We recommend submitting PPC changes after the Identifier changes
have passed NSLDS’ Load-Level edits (e.g., they do not appear on the
subsequent Load Process Error File).</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Part of Event Type</strong></td>
<td colspan="8">Loan Identifier / Student Identifier</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Companion Field(s)</strong></td>
<td colspan="8"><ul>
<li><p>Linked through edit</p></li>
</ul>
<ul>
<li><p>Date of Student’s Birth (022)</p></li>
<li><p>Student’s First Name (023)</p></li>
<li><p>Student’s Last Name (076)</p></li>
<li><p>Student’s Social Security Number Indicator (074)</p></li>
</ul>
<ul>
<li><p>Related field that checks value here</p></li>
</ul>
<ul>
<li><p>PLUS Borrower’s First Name (071)</p></li>
</ul>
<ul>
<li><p>Remaining Identifier Fields</p></li>
</ul>
<ul>
<li><p>Code for Original School (027)</p></li>
<li><p>Date of Guaranty (025)</p></li>
<li><p>Date of Student’s Birth (022)</p></li>
<li><p>Indicator of Separate Loan (026)</p></li>
<li><p>PLUS Borrower’s Social Security Number (028)</p></li>
<li><p>Student’s First Name (023)</p></li>
<li><p>Type of Loan (024)</p></li>
</ul>
<ul>
<li><p>Remaining ‘New Identifier’ Fields</p></li>
</ul>
<ul>
<li><p>New Code for Original School (047)</p></li>
<li><p>New Date of Guaranty (045)</p></li>
<li><p>New Date of Student’s Birth (042)</p></li>
<li><p>New Indicator of Separate Loan (046)</p></li>
<li><p>New Student’s First Name (043)</p></li>
<li><p>New Type of Loan (044)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Default Value / Use</strong></td>
<td colspan="8">Must always be filled.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Reporting</strong></td>
<td colspan="8">Report in regular update.</td>
</tr>
<tr class="odd">
<td><strong>Edit Level</strong></td>
<td colspan="5"><strong>Verifies</strong></td>
<td><strong>Error</strong></td>
<td colspan="2"><strong>Error No.</strong></td>
<td colspan="4"><strong>Error Message</strong></td>
</tr>
<tr class="even">
<td>Domain-Level Error</td>
<td colspan="5">If SSN Indicator is ‘R’ (i.e., SSN is Real), this field
must be numeric.</td>
<td>Isn’t numeric.</td>
<td colspan="2">0235</td>
<td colspan="4">Invalid Student SSN</td>
</tr>
<tr class="odd">
<td>Record-Level Error</td>
<td colspan="5">Must be reported.</td>
<td>Is blank or zeroes.</td>
<td colspan="2">0258</td>
<td colspan="4">Student SSN is required</td>
</tr>
<tr class="even">
<td>Load-Level Error</td>
<td colspan="5">NSLDS determines whether NSLDS database already has a
different student associated with that SSN. (See comments.)</td>
<td>Conflicting first name or date of birth information exists.</td>
<td colspan="2">0408</td>
<td colspan="4">Student SSN currently used by another Student</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>Date Revised</strong></td>
<td colspan="10"><strong>3-13-2006</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 19%" />
<col style="width: 0%" />
<col style="width: 8%" />
<col style="width: 3%" />
<col style="width: 8%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="13"><strong>New Student’s Social Security
Number</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="2"><strong>Loan Identifier</strong></td>
<td colspan="2"><strong>History Kept</strong></td>
<td><strong>Reason-ability</strong></td>
<td colspan="3"><strong>Date Sequence Edit</strong></td>
<td colspan="2"><strong>Type</strong></td>
<td><strong>Size</strong></td>
<td><strong>Position</strong></td>
<td><strong>Field Code</strong></td>
</tr>
<tr class="even">
<td colspan="2">Yes (New)</td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="3">No</td>
<td colspan="2">Character</td>
<td>9</td>
<td>63-71</td>
<td>041</td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Description</strong></td>
<td colspan="8">Title IV aid recipient or beneficiary’s Social Security
Number.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Comments</strong></td>
<td colspan="8"><ul>
<li><p>May be a real or pseudo Social Security Number (SSN). A pseudo
SSN may not be used in place of a real one if the Data Provider has the
real SSN.</p></li>
<li><p>Whenever a real SSN is located for a borrower the Date Provider
must change the Pseudo SSN to the real SSN.</p></li>
<li><p>SSN history should be maintained during SSN changes and updates.
All student loan records should be merged into the current SSN by using
the current and new identifier fields.</p></li>
<li><p>Where a real SSN is not on file, a pseudo SSN must be generated
for the record, as follows:</p></li>
</ul>
<ul>
<li><p>The first position of the SSN must contain a ‘9’ to clearly
identify the record as a pseudo SSN. The second through fourth positions
must contain the Guaranty Agency’s code. Pseudo SSNs <em>must be
unique</em> to each student, so one student’s records can be
distinguished from another’s. Using the Guaranty Agency’s code will help
ED to distinguish the pseudo SSNs reported by different
agencies.</p></li>
<li><p>If a pseudo SSN is used, it may not be substituted for a real SSN
if the Data Provider has the real SSN.</p></li>
<li><p>If a pseudo SSN is used, populate the student’s SSN Indicator
(Field 074) with a ‘P’.</p></li>
</ul>
<ul>
<li><p>When a loan is transferred to your agency from another and it
identifies the student with a pseudo SSN, do not change the Guaranty
Agency Code portion of the number to your own agency’s code. This will
create a new record.</p></li>
<li><p>Whenever a SSN is reported, the system checks whether the number
has already been reported to NSLDS. If not, the student is added to
NSLDS. If it was previously reported, NSLDS uses the following match
logic to confirm the identity of the person.</p></li>
</ul>
<p>1. First Name and Date of Birth (DOB) matches.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Three of first four characters of first name on incoming record
(excluding punctuation and spaces) match three of four characters of
first name (excluding punctuation and spaces) in NSLDS (current or
history), or alias matches exactly. The letters must match in the same
sequence. If fewer than three characters, all characters must match;
and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<blockquote>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary</p>
<p>would match, as “ary” is in same sequential order. So would Maty and
Mary, as “may” is in the same sequential order.</p>
</blockquote>
<p>2. Transposed first name and last name with DOB match.</p>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Three of the first four characters of last name on incoming
record (excluding punctuation and spaces) match three of first four
characters of first name (excluding punctuation and spaces) in NSLDS
(current or history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<p>3. Match on first initial of first name when NSLDS’ first name is
only an initial and no other first names exist in NSLDS.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Incoming first name begins with same letter as NSLDS’ first
initial (a name that is an initial only or an initial followed by a
period, not a comma, and no first name in history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Exact match and is not a plug date: 19000101, 18991231, 18581117,
19581117, 19040404, 19600101, or 19??1111, where ?? can be any year.
(Note: If both incoming and NSLDS have same plug date, this is
considered an exact match.)</p></li>
</ul>
<p>4. Match on first initial and part of last name with DOB match.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>First character of first name matches first character of first
name or first initial (current or history); and</p></li>
</ul>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Five of first seven characters of last name (excluding
punctuation and spaces) match five of first seven characters of last
name (excluding punctuation and spaces) in NSLDS (current or history).
If fewer than five characters, all characters must match; and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<ul>
<li><p>For loans or grants made before 1-1-1997, incoming DOB is plug
date and NSLDS DOB is a real date.</p></li>
</ul>
<blockquote>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary would match, as “ary” is in same sequential order. So would Maty
and Mary, as “may” is in the same sequential order.</p>
</blockquote>
<p>5. Match on student SSN, and a single loan or grant overpayment is
found using the non-student related identifiers. This loan or grant
overpayment was last reported on by the current provider.</p>
<ul>
<li><p>When this Loan Identifier information changes, leave the existing
value in this field and report the new value in the New Student’s Social
Security Number field (e<em>.</em>g., its counterpart New Identifier).
Do this until the updated information is accepted by NSLDS. Once
accepted, the updated value is reported in the standard Loan Identifier
field and the New field is filled with the default value (zeroes or
blanks).</p></li>
<li><p>Changes made to Loan Identifier fields are mapped as a block, so
when the information contained in one of the key data elements is
changed, the information belonging in all of them must be re-confirmed.
Therefore, fill all the New Identifier fields (listed below) for this
loan with the values that they should contain − whether those values are
new ones or the ones that you have been reporting all along.</p></li>
<li><p>Changes made to Identifiers are processed before Past Period
Change records are processed. Therefore, if you are submitting an
Identifier change and a PPC against the same loan record in the same
reporting cycle, the PPC should refer to the New Identifiers, not the
old. We recommend submitting PPC changes after the Identifier changes
have passed NSLDS’ Load-Level edits (e.g., they do not appear on the
subsequent Load Process Error File).</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Part of Event Type</strong></td>
<td colspan="8">Loan Identifier / Student Identifier</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Companion Field(s)</strong></td>
<td colspan="8"><ul>
<li><p>Linked through edit</p></li>
</ul>
<ul>
<li><p>New Date of Student’s Birth (042)</p></li>
<li><p>New Student’s First Name (043)</p></li>
<li><p>Student’s Last Name (076)</p></li>
<li><p>Student’s Social Security Number Indicator (074)</p></li>
</ul>
<ul>
<li><p>Related field that checks value here</p></li>
</ul>
<ul>
<li><p>PLUS Borrower’s First Name (071)</p></li>
</ul>
<ul>
<li><p>Remaining Identifier Fields</p></li>
</ul>
<ul>
<li><p>Code for Original School (027)</p></li>
<li><p>Date of Guaranty (025)</p></li>
<li><p>Date of Student’s Birth (022)</p></li>
<li><p>Indicator of Separate Loan (026)</p></li>
<li><p>PLUS Borrower’s Social Security Number (028)</p></li>
<li><p>Student’s First Name (023)</p></li>
<li><p>Type of Loan (024)</p></li>
</ul>
<ul>
<li><p>Remaining ‘New Identifier’ Fields</p></li>
</ul>
<ul>
<li><p>New Code for Original School (047)</p></li>
<li><p>New Date of Guaranty (045)</p></li>
<li><p>New Date of Student’s Birth (042)</p></li>
<li><p>New Indicator of Separate Loan (046)</p></li>
</ul>
<ul>
<li><p>New PLUS Borrower’s Social Security Number (048)</p></li>
</ul>
<ul>
<li><p>New Student’s First Name (043)</p></li>
<li><p>New Type of Loan (044)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Default Value / Use</strong></td>
<td colspan="8">Report blanks when Loan Identifier information has not
changed.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Reporting</strong></td>
<td colspan="8">Report actual value if change in Student’s Social
Security Number occurs.</td>
</tr>
<tr class="odd">
<td><strong>Edit Level</strong></td>
<td colspan="5"><strong>Verifies</strong></td>
<td><strong>Error</strong></td>
<td colspan="2"><strong>Error No.</strong></td>
<td colspan="4"><strong>Error Message</strong></td>
</tr>
<tr class="even">
<td>Domain-Level Error</td>
<td colspan="5">If Student’s SSN Indicator is ‘R’ (Real), this field
must be numeric and not all zeroes.</td>
<td>Isn’t numeric or is zeroes.</td>
<td colspan="2">0224</td>
<td colspan="4">Invalid New Student SSN</td>
</tr>
<tr class="odd">
<td>Domain-Level Error</td>
<td colspan="5">Change value given when made to another Loan Identifier
field.</td>
<td>No value entered (whether new or existing).</td>
<td colspan="2">0246</td>
<td colspan="4">New Student SSN is required</td>
</tr>
<tr class="even">
<td>Load-Level Error</td>
<td colspan="5">Whether NSLDS database already has a different student
associated with that SSN. (See comments.)</td>
<td>Conflicting first name or date of birth information exists.</td>
<td colspan="2">0407</td>
<td colspan="4">New Student SSN currently used by another student</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>Date Revised</strong></td>
<td colspan="10"><strong>3-13-2006</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 19%" />
<col style="width: 0%" />
<col style="width: 8%" />
<col style="width: 3%" />
<col style="width: 8%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="13"><strong>PLUS Borrower’s Social Security
Number</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="2"><strong>Loan Identifier</strong></td>
<td colspan="2"><strong>History Kept</strong></td>
<td><strong>Reason-ability</strong></td>
<td colspan="3"><strong>Date Sequence Edit</strong></td>
<td colspan="2"><strong>Type</strong></td>
<td><strong>Size</strong></td>
<td><strong>Position</strong></td>
<td><strong>Field Code</strong></td>
</tr>
<tr class="even">
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="3">No</td>
<td colspan="2">Character</td>
<td>9</td>
<td>52-60</td>
<td>028</td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Description</strong></td>
<td colspan="8">PLUS Borrower’s Social Security Number.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Comments</strong></td>
<td colspan="8"><ul>
<li><p>May be a real or pseudo Social Security Number (SSN).</p></li>
<li><p>Where a real SSN is not on file, a pseudo SSN must be generated
for the record, as follows:</p></li>
</ul>
<ul>
<li><p>The first position of the SSN must contain a ‘9’ to clearly
identify the record as a pseudo SSN. The second through fourth positions
must contain the Guaranty Agency’s code. Pseudo SSNs <em>must be
unique</em> to each borrower , so one borrower’s records can be
distinguished from another’s. Using the Guaranty Agency’s code will help
ED to distinguish the pseudo SSNs reported by different
agencies.</p></li>
<li><p>A pseudo SSN may not be used in place of a real one if the Data
Provider has the real SSN.</p></li>
</ul>
<ul>
<li><p>Whenever a real SSN is located for a borrower the Date Provider
must change the Pseudo SSN to the real SSN.</p></li>
<li><p>SSN history should be maintained during SSN changes and updates.
All student loan records should be merged into the current SSN by using
the current and new identifier fields.</p></li>
<li><p>When a loan is transferred to your agency from another and it
identifies the borrower with a pseudo SSN, do not change the Guaranty
Agency Code portion of the number to your own agency’s code.</p></li>
<li><p>Whenever a PLUS Borrower’s SSN is reported, the system checks
whether the number has already been reported to NSLDS. If not, the
student is added to NSLDS. If it was previously reported, NSLDS uses the
following match logic to confirm the identity of the PLUS
borrower.</p></li>
</ul>
<p>1. First Name and Date of Birth (DOB) matches.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Three of first four characters of first name on incoming record
(excluding punctuation and spaces) match three of four characters of
first name (excluding punctuation and spaces) in NSLDS (current or
history), or alias matches exactly. The letters must match in the same
sequence. If fewer than three characters, all characters must
match;<br />
and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary would match, as “ary” is in same sequential order. So would Maty
and Mary, as “may” is in the same sequential order.</p>
<p>2. Transposed first name and last name with DOB match.</p>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Three of the first four characters of last name on incoming
record (excluding punctuation and spaces) match three of first four
characters of first name (excluding punctuation and spaces) in NSLDS
(current or history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<p>3. Match on first initial of first name when NSLDS’ first name is
only an initial and no other first names exist in NSLDS.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>Incoming first name begins with same letter as NSLDS’ first
initial (a name that is an initial only or an initial followed by a
period, not a comma, and no first name in history); and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Exact match and is not a plug date: 19000101, 18991231, 18581117,
19581117, 19040404, 19600101, or 19??1111, where ?? can be any year.
(Note: If both incoming and NSLDS have same plug date, this is
considered an exact match.)</p></li>
</ul>
<p>4. Match on first initial and part of last name with DOB match.</p>
<blockquote>
<p><em>First Name</em></p>
</blockquote>
<ul>
<li><p>First character of first name matches first character of first
name or first initial (current or history); and</p></li>
</ul>
<blockquote>
<p><em>Last Name</em></p>
</blockquote>
<ul>
<li><p>Five of first seven characters of last name (excluding
punctuation and spaces) match five of first seven characters of last
name (excluding punctuation and spaces) in NSLDS (current or history).
If fewer than five characters, all characters must match; and</p></li>
</ul>
<blockquote>
<p><em>Date of Birth</em></p>
</blockquote>
<ul>
<li><p>Year matches exactly; or</p></li>
<li><p>Year matches plus or minus one, with month matching exactly;
or</p></li>
<li><p>Year matches plus or minus ten, with month and day matching
exactly; or</p></li>
</ul>
<ul>
<li><p>Incoming DOB is real and NSLDS’ DOB is one of the following plug
dates: 19000101, 18991231, 18581117, 19581117, 19040404, 19600101, or
19??1111, where ?? can be any year.</p></li>
</ul>
<ul>
<li><p>For loans or grants made before 1-1-1997, incoming DOB is plug
date and NSLDS DOB is a real date.</p></li>
</ul>
<blockquote>
<p><em>Note:</em> When NSLDS performs the analysis on the three of first
four characters in first name or five of first seven characters in last
name, the letters must match in the same sequence. For example, Nary and
Mary would match, as “ary” is in same sequential order. So would Maty
and Mary, as “may” is in the same sequential order.</p>
</blockquote>
<p>5. Match on student SSN, and a single loan or grant overpayment is
found using the non-student related identifiers. This loan or grant
overpayment was last reported on by the current provider.</p>
<ul>
<li><p>When more than one loan exists for the same student, at the same
school, with the same Date of Guaranty, and the only key identifier that
differs between the loans is the PLUS Borrower’s SSN (e.g., Where one
parent signed one loan, the second parent signed the other – as opposed
to an inconsistency or error with the number itself), each of the loans
must be assigned a different Indicator of Separate Loan.</p></li>
<li><p>When this Loan Identifier information changes, leave the existing
value in this field and report the new value in the ‘New PLUS Borrower’s
Social Security Number’ field (i.e., its counterpart ‘New’ Identifier).
Do this until the updated information is accepted by NSLDS. Once
accepted, the updated value is reported in the standard Loan Identifier
field and the ‘New’ field is filled with the default value (zeroes or
blanks).</p></li>
<li><p>Changes made to Loan Identifier fields are mapped as a block, so
when the information contained in one of the key data elements is
changed, the information belonging in all of them must be re-confirmed.
Therefore, fill ALL the New Identifier fields (listed below) for this
loan with the values that they should contain − whether those values are
new ones or the ones that you have been reporting all along.</p></li>
<li><p>Changes made to Identifiers are processed before Past Period
Change records are processed. Therefore, if you are submitting an
Identifier change and a PPC against the same loan record in the same
reporting cycle, the PPC should refer to the New Identifiers, not the
old. We recommend submitting PPC changes after the Identifier changes
have passed all NSLDS Load Processing Error File (i.e., they do not
appear on the subsequent Load Processing Error File).</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Part of Event Type</strong></td>
<td colspan="8">Loan Identifier</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Companion Field(s)</strong></td>
<td colspan="8"><ul>
<li><p>Linked through edit</p></li>
</ul>
<ul>
<li><p>Date of PLUS Borrower’s Birth (073)</p></li>
<li><p>PLUS Borrower’s First Name (071)</p></li>
<li><p>PLUS Borrower’s Last Name (072)</p></li>
<li><p>PLUS Borrower’s Social Security Number Indicator (070)</p></li>
<li><p>Type of Loan (024)</p></li>
</ul>
<ul>
<li><p>Related field that checks value here</p></li>
</ul>
<ul>
<li><p>PLUS Borrower’s First Name (071)</p></li>
</ul>
<ul>
<li><p>Remaining Identifier Fields</p></li>
</ul>
<ul>
<li><p>Code for Original School (027)</p></li>
<li><p>Date of Guaranty (025)</p></li>
<li><p>Date of Student’s Birth (022)</p></li>
<li><p>Indicator of Separate Loan (026)</p></li>
<li><p>Student’s First Name (023)</p></li>
<li><p>Student’s Social Security Number (021)</p></li>
<li><p>Type of Loan (024)</p></li>
</ul>
<ul>
<li><p>Remaining ‘New Identifier’ Fields</p></li>
</ul>
<ul>
<li><p>New Code for Original School (047)</p></li>
</ul>
<ul>
<li><p>New Date of Guaranty (045)</p></li>
<li><p>New Date of Student’s Birth (042)</p></li>
<li><p>New Indicator of Separate Loan (046)</p></li>
<li><p>New Student’s First Name (043)</p></li>
<li><p>New Student’s Social Security Number (041)</p></li>
<li><p>New Type of Loan (044)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Default Value / Use</strong></td>
<td colspan="8">Must always be filled for PLUS loans.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Reporting</strong></td>
<td colspan="8">Report in regular update.</td>
</tr>
<tr class="odd">
<td><strong>Edit Level</strong></td>
<td colspan="5"><strong>Verifies</strong></td>
<td><strong>Error</strong></td>
<td colspan="2"><strong>Error No.</strong></td>
<td colspan="4"><strong>Error Message</strong></td>
</tr>
<tr class="even">
<td>Record-Level Error</td>
<td colspan="5">Must be numeric if PLUS Borrower’s Social Security
Number Indicator is ‘R’.</td>
<td>Isn’t numeric.</td>
<td colspan="2">0160</td>
<td colspan="4">Invalid PLUS Borrower SSN</td>
</tr>
<tr class="odd">
<td>Record-Level Error</td>
<td colspan="5">Must be blank if Type of Loan is other than ‘PL’.</td>
<td>Isn’t blank.</td>
<td colspan="2">0193</td>
<td colspan="4">Field not required on this type of loan</td>
</tr>
<tr class="even">
<td>Record-Level Error</td>
<td colspan="5">This field must be reported if Type of Loan is
‘PL’.</td>
<td>Is blank.</td>
<td colspan="2">0250</td>
<td colspan="4">PLUS Borrower SSN is required</td>
</tr>
<tr class="odd">
<td>Load-Level Error</td>
<td colspan="5">For loans already reported to NSLDS, the incoming PLUS
Borrower SSN is associated to the loan identified.</td>
<td>PLUS Borrower’s SSN does not match (See comments).</td>
<td colspan="2">0160</td>
<td colspan="4">Invalid PLUS Borrower SSN</td>
</tr>
<tr class="even">
<td>Load-Level Error</td>
<td colspan="5">Whether NSLDS database already has a different PLUS
Borrower associated with that SSN.</td>
<td>Conflicting first name or date of birth information exists.</td>
<td colspan="2">0409</td>
<td colspan="4">PLUS Borrower SSN currently used by another
borrower</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>Date Revised</strong></td>
<td colspan="10"><strong>3-13-2006</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 10%" />
<col style="width: 0%" />
<col style="width: 19%" />
<col style="width: 9%" />
<col style="width: 3%" />
<col style="width: 8%" />
<col style="width: 12%" />
<col style="width: 14%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="12">New PLUS Borrower’s Social Security Number</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="2"><strong>Loan Identifier</strong></td>
<td colspan="2"><strong>History Kept</strong></td>
<td><strong>Reason-ability</strong></td>
<td colspan="2"><strong>Date Sequence Edit</strong></td>
<td colspan="2"><strong>Type</strong></td>
<td><strong>Size</strong></td>
<td><strong>Position</strong></td>
<td><strong>Field Code</strong></td>
</tr>
<tr class="even">
<td colspan="2">Yes (New)</td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">Character</td>
<td>9</td>
<td>111-119</td>
<td>048</td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Description</strong></td>
<td colspan="7">PLUS Borrower’s Social Security Number.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Comments</strong></td>
<td colspan="7"><ul>
<li><p>May be a real or pseudo Social Security Number (SSN).</p></li>
<li><p>Where a real SSN is not on file, a pseudo SSN must be generated
for the record, as follows</p></li>
</ul>
<ul>
<li><p>The first position of the SSN must contain a ‘9’ to clearly
identify the record as a pseudo SSN. The second through fourth positions
must contain the Guaranty Agency’s code. Pseudo SSNs <em>must be
unique</em> to each borrower , so one borrower’s records can be
distinguished from another’s. Using the Guaranty Agency’s code will help
ED to distinguish the pseudo SSNs reported by different
agencies.</p></li>
<li><p>A pseudo SSN may not be substituted for a real one if the Data
Provider has the real SSN.</p></li>
</ul>
<ul>
<li><p>Whenever a real SSN is located for a borrower the Data Provider
must change the Pseudo SSN to the real SSN</p></li>
<li><p>SSN history should be maintained during SSN changes and updates.
All student loan records should be merged into the current SSN by using
the current and new identifier fields.</p></li>
<li><p>When a loan is transferred to your agency from another and it
identifies the borrower with a pseudo SSN, do not change the Guaranty
Agency Code portion of the number to your own agency’s code. This will
create a new record.</p></li>
<li><p>When the PLUS Borrower’s SSN changes, leave the previously
reported value in the ‘PLUS Borrower’s Social Security Number’ field,
and report the new value here.</p></li>
<li><p>Changes made to Loan Identifier fields are mapped as a block, so
when the information contained in one of the key data elements is
changed, the information belonging in all of them must be re-confirmed.
To permit this, you must fill ALL the New Identifier fields (listed
below) for this loan with the values that they should contain − whether
those values are new ones or the ones that you have been reporting all
along.</p></li>
<li><p>Changes made to Identifiers are processed before Past Period
Change records are processed. Therefore, if you are submitting an
Identifier change and a PPC against the same loan record in the same
reporting cycle, the PPC should refer to the New Identifiers, not the
old. We recommend submitting PPC changes after the Identifier changes
have passed all NSLDS edits (i.e., they do not appear on the subsequent
Load Processing Error File).</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Part of Event Type</strong></td>
<td colspan="7">Loan Identifier</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Companion Field(s)</strong></td>
<td colspan="7"><ul>
<li><p>Linked through edit</p></li>
</ul>
<ul>
<li><p>Date of PLUS Borrower’s Birth (073)</p></li>
<li><p>New Type of Loan (044)</p></li>
<li><p>PLUS Borrower’s First Name (071)</p></li>
<li><p>PLUS Borrower’s Social Security Number Indicator (070)</p></li>
</ul>
<ul>
<li><p>Related field that checks value here</p></li>
</ul>
<ul>
<li><p>PLUS Borrower’s First Name (071)</p></li>
</ul>
<ul>
<li><p>Remaining Identifier Fields</p></li>
</ul>
<ul>
<li><p>Code for Original School (027)</p></li>
<li><p>Date of Guaranty (025)</p></li>
<li><p>Date of Student’s Birth (022)</p></li>
<li><p>Indicator of Separate Loan (026)</p></li>
<li><p>Student’s First Name (023)</p></li>
<li><p>Student’s Social Security Number (021)</p></li>
<li><p>Type of Loan (024)</p></li>
</ul>
<ul>
<li><p>Remaining ‘New Identifier’ Fields</p></li>
</ul>
<ul>
<li><p>New Code for Original School (047)</p></li>
</ul>
<ul>
<li><p>New Date of Guaranty (045)</p></li>
<li><p>New Date of Student’s Birth (042)</p></li>
<li><p>New Indicator of Separate Loan (046)</p></li>
<li><p>New Student’s First Name (043)</p></li>
<li><p>New Student’s Social Security Number (041)</p></li>
<li><p>New Type of Loan (044)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Default Value / Use</strong></td>
<td colspan="7">Report blanks when Loan Identifier information has not
changed.</td>
</tr>
<tr class="even">
<td colspan="5"><strong>Reporting</strong></td>
<td colspan="7">Report actual value if change in PLUS Borrower’s SSN
occurs.</td>
</tr>
<tr class="odd">
<td><strong>Edit Level</strong></td>
<td colspan="5"><strong>Verifies</strong></td>
<td><strong>Error</strong></td>
<td><strong>Error No.</strong></td>
<td colspan="4"><strong>Error Message</strong></td>
</tr>
<tr class="even">
<td>Domain-Level Error</td>
<td colspan="5">If PLUS Borrower’s Social Security Number Indicator is
‘R’ (Real), this field must be numeric.</td>
<td>Isn’t numeric.</td>
<td>0160</td>
<td colspan="4">Invalid PLUS Borrower SSN</td>
</tr>
<tr class="odd">
<td>Record-Level Error</td>
<td colspan="5">Field must be blank if identifier fields haven’t
changed, or if Type of Loan isn’t ‘PL’.</td>
<td>Is filled.</td>
<td>0193</td>
<td colspan="4">Field not required on this type of loan</td>
</tr>
<tr class="even">
<td>Record-Level Error</td>
<td colspan="5">Change value given when made to another Loan Identifier
field and New Type of Loan is PL.</td>
<td>No value entered here (whether new or existing).</td>
<td>0473</td>
<td colspan="4">New PLUS Borrower SSN is required</td>
</tr>
<tr class="odd">
<td>Load-Level Error</td>
<td colspan="5">Whether NSLDS database already has a different PLUS
Borrower associated with that SSN.</td>
<td>Conflicting first name or date of birth information exists.</td>
<td>0410</td>
<td colspan="4">New PLUS Borrower SSN currently used by another
borrower</td>
</tr>
<tr class="even">
<td colspan="3"><strong>Date Revised</strong></td>
<td colspan="9"><strong>3-13-2006</strong></td>
</tr>
</tbody>
</table>