# EDE Processing

## Introduction

This section provides a more detailed description of the EDE process. It
provides instructions for each of the individual processes within EDE.

## Electronic FAFSA

The Electronic FAFSA process allows destination points to enter FAFSA
data and send it to the Central Processing System (CPS) for processing.
The FAFSA data can be collected on either a paper Renewal FAFSA or the
Free Application for Federal Student Aid (FAFSA). Once processed by CPS,
the results of the Electronic FAFSA are transmitted back to the
destination point.

EDESuite software is provided free to destination points by the U.S.
Department of Education (ED). It allows financial aid administrators
(FAAs) to enter the FAFSA information into a personal computer. However,
schools may choose to develop their own software instead. Regardless of
whether the FAFSA data is entered using EDExpress or other software, the
data must adhere to ED's editing rules in order to be accepted by CPS.

The remainder of this section includes specifications for developing
software to provide the required Electronic FAFSA functions.

### Electronic FAFSA Process

> The Electronic FAFSA process involves five steps:

1.  The student submits a completed and signed paper FAFSA to the
    school.

2.  The information on the FAFSA is key entered.

3.  The FAFSA data is edited and corrected until a file of clean data is
    created. The data elements for each field must be in the valid range
    with no inconsistencies in the data. For example, the system will
    generate an edit for inconsistent data in these fields when a
    student indicates a single status yet provides income earned from
    work for student and spouse.

4.  Th file is formatted and transmitted to CPS via the Student Aid
    Intateway (SAIG).

5.  Processed FAFSA records are transmitted back to the destination
    point as Institutional Student Information Records (ISIRs) under the
    message class EAPS03OP.

#### Receiving the Completed Paper FAFSA or Paper Renewal FAFSA

Schools participating in Electronic Applications must have their
students complete and sign a paper FAFSA or paper Renewal FAFSA. ED
provides the FAFSA form. The completed and signed document must be kept
on file at the school. If a student submits a paper Renewal FAFSA to the
school, the Renewal FAFSA should be entered as a FAFSA.

#### Entering the FAFSA Information

As part of the FAFSA entry, you are responsible for ensuring that the
data meets the field-by-field criteria provided in the 'Valid Field
Contents' column of the FAFSA Application Export Record Layout. The
record created by your software must adhere to the record layout
provided later in the Record Layout section with the addition of a
Carriage Return/Line Feed (CR/LF, ASCII 13, 10 HEX 0D and 0A
respectively) at the end of each record. Use of an end-of-file mark
(ASCII 26 or HEX 1A) is optional. FAFSAs with invalid dates or formats
are rejected.

#### Formatting and Transmitting the Records

Use EDconnect, the transmission software provided by ED, to format your
data records and transmit them over SAIG. The batch Header and Trailer
Records are provided in the Record Layouts section. Each batch to be
transmitted must start with a Header Record followed by the data records
followed by the Trailer Record.

#### Receiving Processed Records

You receive your processed FAFSA records in ISIR format in the EAPS03OP
message class.

> **Note:** See the Printing section for more information on printing
> ISIRs.

There may be instances when CPS does not accept your records for
processing. CPS returns a rejected electronic FAFSA error report to you
in the message class EAPR03OP. The Record Layouts section contains two
reject layouts. The first is for rejects at the batch level (the whole
batch rejects), EDE Batch Level Error Report Import Record Layout. The
second is for rejects at the record level (individual record(s) reject),
EDE Record Level Error Report Import Record Layout. The Processing Codes
section contains additional information on the reject reasons found in
the record layout.

#### Rejected FAFSA Records

> There are two categories of rejections for submitted FAFSA records:

1.  **Transaction Rejects**

> A transaction reject prevents the FAFSA record from being processed.
> If a record is rejected for one or more reasons, an error report is
> returned to the school in message class EAPR03OP (see layout in the
> Record Layouts section) and no ISIR is created. These rejects are also
> known as record level rejects.
>
> **2. Compute Rejects**
>
> CPS contains a series of edits that evaluates data on incoming FAFSA
> data for consistency and completeness. These edits apply to all data
> from electronic and paper input. An Expected Family Contribution (EFC)
> is not computed for a FAFSA rejected for a compute reject reason.
> However, an ISIR is produced. ISIRs with a compute reject are returned
> in the EAPS03OP message class. The reasons for the compute reject are
> coded on the ISIR. Refer to the Processing Codes section for
> information on interpreting these reject codes.
>
> There are two types of FAFSA compute reject reason codes:

-   Numeric: Certain data items MUST be corrected before a valid ISIR
    can be generated (Non-Verifiable).

-   Alphabetic: Certain data items be ither corrected or verified before
    a valid ISIR can be generated (Verifiable). An alpha reject reason
    code is a verifiable data element, meaning the data given is
    questionable but could be correct.

> In the paper system, a student can verify a data field by re-entering
> the same information in the (SAR) correction coumnfor the field in
> question. In the electronic process, the school verifies the data
> (re-enters the data as a \"correction\") and transmits the correction
> record to CPS. Data that must be verified or corrected in response to
> each reject reason is provided in the Processing Codes section.
>
> A student's record nothave an EFC if the record contains questionable
> data and has a FAFSA reject reason code(s). The reject reason code(s)
> are found in positions 611-624 on the ISIR. T

## Electronic PIN Mailer Requests

> Schools can request that PIN mailers be sent to eligible applicants
> instead of the paper Renewal FAFSA. The PIN would allow the student to
> access their electronic 2002-2003 Renewal FAFSA data on the Web.
> Renewal FAFSAs are for returning students. The Renewal FAFSA displays
> the 2001-2002 information. The student applicant either verifies that
> the 2001-2002 information is still correct for 2002-2003 or updates
> the information on file at the Central Processing System (CPS) as of
> October 2001.
>
> The Renewal FAFSA process has changed for the 2002-2003 year. Please
> refer to section 1, Overview, and to Action LetterAFSA process,
> available on the IFAP for additional information.

### Renewal PIN Mailer Process

> There are two options to request that PIN Mailers be sent to the
> student instead of paper Renewal FAFSAs:

1.  Type 2 Request - This request is sent via SAIG. You will need to
    create a file that contains a CPS Header, Type 2 Individual PIN
    Mailer Request Export and PIN Error Import Record Layout, and the
    CPS Trailer. All of these layouts are found in section 3, Record
    Layouts.

2.  FAA Access - Use FAA Access over the Web to make your request.

> After the Renewal FAFSAs are printed, each destination point will
> receive a report in the format of the RAPP PIN/Print Notification
> layout, found in section 3, Record layouts. This report will identify
> which students received a paper Renewal FAFSA or a PIN mailer.
>
> If a student returns a completed Renewal FAFSA to the school, the data
> can be entered, edited, and transmitted to CPS as if it were a FAFSA.

## ISIR

> The ISIR is a fixed-length record containing reported information from
> the FAFSA), as well as key processing results. The names and addresses
> of the colleges the student plans to attend in 2002-2003 are
> translated to a 6-digit identifying Federal School Code on the ISIR.
> The preparer\'s name or address is not entered by the MDEs
> (application processors). For the most part, all information printed
> by CPS on SAR is coded on the ISIR.
>
> **Note**: The average CPS processing time is between 48-52 hours*.*

### NSLDS Data 

> The ISIR carries National Student Loan Data System (NSLDS)
> information, which is located at the end of the ISIR Record
> Description.

### ISIR Receipt Process

> ISIRs are transmitted by CPS to the SAIG in batches containing a batch
> header record, one or more ISIRs, and a batch trailer record.
> Descriptions of the contents of the ISIR are in the Record Layouts
> section. CPS Header and Trailer records are described in the Record
> Layouts section and at the end of this section.

#### ISIR Types

> There are four reasons why CPS generates an ISIR:

1.  ISIRs are automatically generated in response to a FAFSA or
    correction entered at a site other than your school or state agency.
    These \"automatic ISIRs\" are generated following the entry of a
    paper FAFSA or SAR by the MDE application processors or by an
    electronic FAFSA from the FAFSA Express, FAFSA on the Web, Renewal
    on the Web, or Correction on the Web user. They may also be produced
    following the entry of an electronic FAFSA or correction by another
    EDE school. ISIRs resulting from students correcting their data on
    the Web are sent to the school this way.

    Automatic ISIRs are sent to school destination points in the
    SARA03OP message class. State agencies receive Non-Resident ISIRs in
    the ESFN03OP message class and Resident ISIRs in the ESFR03OP
    message class.

2.  ISIRs are generated in direct response to electronic FAFSAs,
    correction/duplicate records, and signature correction records
    submitted by your school. ISIRs are returned to destination points
    in the EAPS03OP, CORR03OP, and SARA03OP message classes,
    respectively.

3.  ISIRs are generated in response to a request by state agencies
    through the Federal Data Request (FDR) process. This process allows
    agencies to request a processed FAFSA record for any student on CPS
    database. ISIRs are returned to the State agency's destination point
    in FDRF03OP message class.

4.  ISIRs are system-generated due to reprocessing by CPS, NSLDS
    post-screening, INS Secondary process, Prisoner match, and an
    applicant being released from a hold file. These ISIRs are returned
    in the SYSG03OP message class. Any ISIR that has a value in the
    systems generated field are returned in the SYSG03OP message class
    except when the value is L, duplicate request, or blank.

######## 

######## *Automatic ISIRs for Schools*

> All automatic ISIRs (for example, ISIRs generated in response to input
> by a site other than your school or state agency) are transmitted
> daily from CPS to the SAIG in message class SARA03OP for schools,
> ESFR03OP (state residents), or ESFN03OP (non-residents) for state
> agencies.
>
> Each school subscribing to the ISIR service automatically receives one
> ISIR for every student who lists their school on the FAFSA. Servicers
> receive only one ISIR per destination point.
>
> If an ISIR receives a reject code of 14, 15 or 16 (missing
> signatures), the school and state agency receive the full ISIR
> electronically. As with other rejects, an EFC is not computed until
> the reject is resolved.

######## *Requested ISIRs*

> Requested ISIRs are generated in response to input from the school or
> state agency. ISIRs requested by schools are transmitted to the SAIG
> in one of four message classes, depending upon the type of input.

-   EAPS03OP

> ISIRs in this message class are returned to the school in response to
> electronic FAFSAs. The school receives one ISIR for every FAFSA
> submitted that did not receive a transmission reject. Refer to the
> Record Layouts section for EDE Batch or EDE Record Level Error Report
> Record Layout and Processing Codes section for batch and record level
> reject error messages.

-   CORR03OP

> ISIRs in this message class are returned to the school in response to
> electronic corrections or duplicate requests. The school receives an
> ISIR for every correction or duplicate request submitted that did not
> receive a transmission rejection. Refer to the Record Layouts section
> for the EDE Record Level Error Report Import Record Layout, and the
> Processing Codes section for record level error messages.
>
> **Note:** A school, with the student's consent, is able to
> electronically add its Federal School Code to the list of school
> choices on the student's ISIR record with the Data Release Number
> (DRN). Instructions for this are explained later in this section*.*

-   SYSG03OP

> ISIRs in this message class are sent to the school as a result of a
> transaction automatically created by CPS. The school does nothing to
> initiate these ISIRs. There are several instances when CPS generates
> an ISIR for a student:

-   Hold File status changes

-   CPS Reprocessing of records due to formula changes

-   CPS receives changed information via NSLDS Post-Screening INS
    Secondary Match

-   Prisoner post-screening

-   SARA03OP

> Requested ISIRs in this message class are sent to the school as a
> result of the school sending a signature for an applicant and/or the
> parent who filed using one of the Web products or FAFSA Express.
> Automatic ISIRs in this message class are also received from paper
> FAFSAs and corrections, from another school filing an electronic FAFSA
> or electronic correction with your school listed, or a student filing
> a FAFSA on the Web or making corrections on the Web.

### State Agency Options

> State agencies can combine processed FAFSA data from CPS with common
> loan application data to guarantee federal student loans and/or with
> state data to award state scholarships and grants.
>
> As destination points, state agencies have two options for obtaining
> processed FAFSA data:

-   Automatic ISIR Processing

-   Federal Data Request (FDR)

#### Automatic ISIRs for State Agencies

> Each state agency subscribing to the ISIR service can choose to
> automatically receive one ISIR for every student who:

-   Indicates that state on the FAFSA as the state of legal residence

-   Is a non-resident but lists a college within the state

-   Both

> **Note:** If the student indicates on the FAFSA more than one school
> that is located in your state, your state agency receives only one
> ISIR.
>
> Automatic ISIRs are transmitted daily from CPS to the SAIG in one of
> two message classes:
>
> ESFR03OP State Agency ISIR Resident
>
> ESFN03OP State Agency ISIR Nonresident
>
> **Note:** The state agency indicates what type of ISIRs (residents,
> non-residents or both) it wants to receive on the SAIG Agency
> Enrollment Form*.*

### Federal Data Request Processing (FDR)

> A Federal Data Request (FDR) is the process by which a state agency
> can request the electronic processed FAFSA record for any student in
> the CPS database.
>
> In the case of students who are neither residents of the state nor
> attend a school in the state, an FDR can be made if the student has
> signed a loan or state grant application that releases CPS data to the
> state agency. The agency must retain the signed FAFSA. When requesting
> and receiving this data from CPS, use the following message classes:

  ---------------------- ------------------------------------------------
  FDRS03IN               FDR Request

  FDRF03OP               Processed FDRs

  FDRU03OP               Unfulfilled FDRs not on CPS Database after 30
                         days
  ---------------------- ------------------------------------------------

####  Requesting a FDR Record

> To request a specific applicant\'s record, the agency must transmit
> over the SAIG the Social Security Number (SSN) and the first two
> letters of the last name. Use the record layout FDR Export Record
> Layout (FDRS03IN) in the Record Layouts section. Use the following
> steps to create a request for a single applicant's record:

1.  In the first position of the record, enter 3 to indicate this is a
    request for a 2002-2003 applicant transaction.

2.  Leave positions 2 through 14 blank.

3.  Enter 199 in positions 15 through 17. This indicates a request for
    an ISIR record.

4.  Enter the student's SSN as reported on the original FAFSA in
    positions 18 through 26.

5.  In positions 27-28, enter the first two letters of the student's
    last name as entered on the original FAFSA.

6.  Leave positions 29 through 579 blank.

7.  Enter F (FDR) in position 580.

> Remember, prior to sending the file, you must add a header record
> before the FDR request record(s) and a trailer record after the FDR
> request record(s).

#### Requesting More than One FDR Record

> Up to 12 FDRs can be requested on a single record (message class
> FDRS03IN). To request up to 12 records, repeat steps 4 and 5 using the
> remaining data fields on the FDR record. The second record begins in
> position 53, the third in position 91, the fourth in position 129, the
> fifth in position 167, the sixth in position 205, the seventh in
> position 243, the eight in position 281, the ninth in position 319,
> the tenth in position 357, the eleventh in position 395, and the
> twelfth in position 433.
>
> To request more than 12 ISIRs, create an additional record by
> repeating steps 1 through 7.

#### Response to an FDR Request

> State agencies receive one batch of ISIRs in response to each batch of
> FDR records submitted. The batch of ISIRs will be returned in the
> FDRF03OP message class. It contains one ISIR for every submitted FDR
> record that was not rejected.
>
> If a requested student record is not found on the CPS database after
> 30 days, a notice is returned to the requesting agency in message
> class FDRU03OP.

### Rejected FDR Records

A transaction reject prevents the FDR record from being processed at
CPS. If a record is rejected for one or more reasons, an error report is
returned to the agency in a message class titled FDRE03OP.

## Electronic Corrections

> Schools with destination points enrolled for electronic correction
> processing are able to transmit corrections to FAFSA data via the
> SAIG.
>
> EDExpress allows schools to enter and edit correction data according
> to system requirements. It also creates an electronic correction
> record ready for transmission using the communications interface
> software, EDconnect. Schools, however, may choose to develop their own
> software to enter, edit, and format correction data. Specifications
> for developing correction software are provided in the remainder of
> this section.

### General Correction Entry Specifications

> Only corrected information from a student\'s record, not the complete
> applicant record, is transmitted to CPS. This approach minimizes the
> transmission volume. Corrected information is transmitted as a
> fixed-length record. The layout and description of this record is in
> the Record Layouts section, Correction Export Record Layout
> (CORR03IN).

### Creating a Correction Record

> Use the following steps to create a correction record:

1.  In the first position of the record, enter 3 to indicate this is a
    correction to a 2002-2003 applicant transaction.

2.  In positions 2 through 10, enter the applicant\'s original Social
    Security Number (SSN). This is the number reported by the applicant
    on the FAFSA form and does not reflect any corrections to the SSN
    that might have been made.

3.  In positions 11 and 12, enter the first two letters of the
    applicant\'s last name. These are the letters reported by the
    applicant on the FAFSA form and do not reflect any corrections to
    the last name that might have been made.

4.  In positions 13 and 14, enter the transaction number of the
    applicant record being corrected. For example, enter 01 to correct
    the first transaction on file at CPS. The transaction does not
    necessarily have to be the latest one on file at CPS. If the
    transaction number being corrected is not on the CPS database, the
    record is rejected. If you want to correct the most recent
    transaction, you can enter 99.

> **Note:** When making a correction using transaction 99, field number
> 086 (the first Federal School Code) and field number 112 (DRN) must be
> provided on the record.

5.  In positions 15 through 17, enter the SAR number of the SAR field
    being corrected. Each correctable field has a 3-digit SAR number
    associated with it. For example, enter 001 to correct the student\'s
    last name. The SAR numbers with valid field content are provided in
    the Correction Data Entry Specifications table found in the
    Processing Codes section.

6.  In positions 18 through 52, enter the new value for the field being
    corrected.

7.  In positions 471 through 476, enter the Federal School Code of the
    school making the correction.

8.  In positions 477-526, enter or correct the student's e-mail address.

9.  In positions 553-560, enter the transaction receipt date. This is
    the date you received the correction information from the student.

10. In positions 575-579, enter the serial number, the sequential
    position of the correction record in the batch. For example, the
    first student\' s correction record will have a serial number of
    00001, and the second student's serial number will be 00002, etc.

```{=html}
<!-- -->
```
1.  In position 580, enter H (correction).

> Up to 12 SAR data fields can be corrected on a single record. Repeat
> steps 5 and 6 using the remaining data fields on the correction record
> if more than one field is being corrected. If more than twelve fields
> require correction, an additional record must be created, repeating
> steps 1 through 10. Both data records for the student have the same
> serial number.
>
> **Note:** To correct a field to blank, enter a single asterisk (\*)
> left justified in that field. The Correction Data Entry Specification
> table, in section 4, distinguishes which fields can be corrected to
> blank as not all fields can be.

### Detailed Data Entry Specifications

> Each corrected value must meet certain standards; otherwise, the
> correction record is rejected. Field-by-field data entry
> specifications are provided in the Processing Codes section. For each
> field, these specifications identify the type (character, numeric, or
> signed/numeric), acceptable length, whether the field is correctable,
> whether the field is correctable to blank, and the valid values for
> the correction. Keep the following items in mind:

-   Left-justify the corrected value within the data field on the
    correction record, while zero filling numeric fields up to the valid
    maximum length of the field. For example, to correct the number of
    family members to 5, enter 05 in positions 18 and 19, leaving
    positions 20 through 52 blank. To correct the student\'s last name
    to Smith, enter SMITH in positions 18 through 22, leaving positions
    23 through 52 blank.

```{=html}
<!-- -->
```
-   All 9s in a field indicate the reported or calculated value is
    greater than or equal to the value of all 9s. Blanks are allowable
    in some fields.

```{=html}
<!-- -->
```
-   Fields can contain one of three data types:

-   Character

-   Numeric

-   Signed Numeric

```{=html}
<!-- -->
```
-   A negative entry is acceptable for a limited number of fields. The
    Correction Data Entry Specifications table in the Processing Codes
    section identifies the fields in which a negative is acceptable
    under the Justify/Signed column and the valid field content column.
    The Signed Numeric Field table below also defines the signed fields.
    With signed numeric fields, the sign is always implied in the right
    most character of the field. For example, if the Student's Adjusted
    Gross Income field contains a value of negative 3507, it appears as
    00350P. The following chart explains the conversion of the sign and
    the number:

> Signed Numeric Fields:
>
> { +0 E +5 } -0 N -5
>
> A +1 F +6 J -1 0 -6
>
> B +2 G +7 K -2 P -7
>
> C +3 H +8 L -3 Q -8
>
> D +4 I +9 M -4 R -9

The table listed on the next three pages defines all the signed fields
that can be sent to and received from CPS.

### Signed Numeric Fields Table 

+-----+-----+-------+---------------------+-------------------+------+
| **  | **  | **    | **Field Name**      | **Valid Field     | **F  |
| ISI | SAR | Field |                     | Content**         | ound |
| R** | Fi  | Len   |                     |                   | Only |
|     | eld | gth** |                     |                   | on   |
| *   | \   |       |                     |                   | IS   |
| *Fi | #** |       |                     |                   | IR** |
| eld |     |       |                     |                   |      |
| \   |     |       |                     |                   |      |
| #** |     |       |                     |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 44  | 039 | 6     | Student's Adjusted  | -999999 to 999999 | N    |
|     |     |       | Gross Income from   |                   |      |
|     |     |       | IRS form            | Blank             |      |
+-----+-----+-------+---------------------+-------------------+------+
| 47  | 042 | 6     | Student's Income    | -999999 to 999999 | N    |
|     |     |       | Earned from Work    |                   |      |
|     |     |       |                     | Blank             |      |
+-----+-----+-------+---------------------+-------------------+------+
| 48  | 043 | 6     | Spouse's Income     | -999999 to 999999 | N    |
|     |     |       | Earned from Work    |                   |      |
|     |     |       |                     | Blank             |      |
+-----+-----+-------+---------------------+-------------------+------+
| 78  | 073 | 6     | Parents' Adjusted   | -999999 to 999999 | N    |
|     |     |       | Gross Income from   |                   |      |
|     |     |       | IRS form            | Blank             |      |
+-----+-----+-------+---------------------+-------------------+------+
| 81  | 076 | 6     | Fa                  | -999999 to 999999 | N    |
|     |     |       | ther's/Stepfather's |                   |      |
|     |     |       | Income Earned from  | Blank             |      |
|     |     |       | Work                |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 82  | 077 | 6     | Mo                  | -999999 to 999999 | N    |
|     |     |       | ther's/Stepmother's |                   |      |
|     |     |       | Income Earned from  | Blank             |      |
|     |     |       | Work                |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 195 | []{ | 7     | TI: Total Income    | -9999999 to       | Y    |
|     | .ma |       |                     | 9999999           |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 197 | []{ | 7     | STX: State and      | -9999999 to       | Y    |
|     | .ma |       | Other Tax Allowance | 9999999           |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 200 | []{ | 7     | AI: Available       | -9999999 to       | Y    |
|     | .ma |       | Income              | 9999999           |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 201 | []{ | 7     | CAI: Contribution   | -9999999 to       | Y    |
|     | .ma |       | From Available      | 9999999           |      |
|     | rk} |       | Income              |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 202 | []{ | 9     | DNW: Discretionary  | -999999999 to     | Y    |
|     | .ma |       | Net Worth           | 999999999         |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 205 | []{ | 7     | PCA: Parents'       | -9999999 to       | Y    |
|     | .ma |       | Contribution from   | 9999999           |      |
|     | rk} |       | Assets              |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 206 | []{ | 7     | AAI: Adjusted       | -9999999 to       | Y    |
|     | .ma |       | Available Income    | 9999999           |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 210 | []{ | 7     | STI: Student's      | -9999999 to       | Y    |
|     | .ma |       | Total Income        | 9999999           |      |
|     | rk} |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 211 | []{ | 7     | SATI: Student's     | -9999999 to       | Y    |
|     | .ma |       | Allowance against   | 9999999           |      |
|     | rk} |       | Total Income        |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 213 |     | 9     | SDNW: Student's     | -999999999 to     | Y    |
|     |     |       | Discretionary Net   | 999999999         |      |
|     |     |       | Worth               |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 214 |     | 7     | SCA: Student's      | -9999999 to       | Y    |
|     |     |       | Contribution from   | 9999999           |      |
|     |     |       | Assets              |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+

###  Signed Numeric Fields Table (Continued)

+-----+-----+-------+---------------------+-------------------+------+
| **  | **  | **    | **Field Name**      | **Valid Field     | **F  |
| ISI | SAR | Field |                     | Content**         | ound |
| R** | Fi  | Len   |                     |                   | Only |
|     | eld | gth** |                     |                   | on   |
| *   | \   |       |                     |                   | IS   |
| *Fi | #** |       |                     |                   | IR** |
| eld |     |       |                     |                   |      |
| \   |     |       |                     |                   |      |
| #** |     |       |                     |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 215 |     | 7     | FTI: FISAP Total    | -9999999 to       | Y    |
|     |     |       | Income              | 9999999           |      |
|     |     |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 216 |     | 7     | SEC TI: Secondary   | -9999999 to       | Y    |
|     |     |       | Total Income        | 9999999           |      |
|     |     |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 218 |     | 7     | SEC STX: Secondary  | -9999999 to       | Y    |
|     |     |       | State Tax Allowance | 9999999           |      |
|     |     |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 221 |     | 7     | SEC AI: Secondary   | -9999999 to       | Y    |
|     |     |       | Available Income    | 9999999           |      |
|     |     |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 222 |     | 7     | SEC CAI: Secondary  | -9999999 to       | Y    |
|     |     |       | Contribution From   | 9999999           |      |
|     |     |       | Available Income    |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 223 |     | 9     | SEC DNW: Secondary  | -999999999 to     | Y    |
|     |     |       | Discretionary Net   | 999999999         |      |
|     |     |       | Worth               |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 226 |     | 7     | SEC PCA: Secondary  | -9999999 to       | Y    |
|     |     |       | Parents'            | 9999999           |      |
|     |     |       | Contribution from   |                   |      |
|     |     |       | Assets              | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 227 |     | 7     | SEC AAI: Secondary  | -9999999 to       | Y    |
|     |     |       | Adjusted Available  | 9999999           |      |
|     |     |       | Income              |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 231 |     | 7     | SEC STI: Secondary  | -9999999 to       | Y    |
|     |     |       | Student's Total     | 9999999           |      |
|     |     |       | Income              |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 232 |     | 7     | SEC SATI: Secondary | -9999999 to       | Y    |
|     |     |       | Student's Allowance | 9999999           |      |
|     |     |       | Against Total       |                   |      |
|     |     |       | Income              | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 234 |     | 9     | SEC SDNW: Secondary | -999999999 to     | Y    |
|     |     |       | Student's           | 999999999         |      |
|     |     |       | Discretionary Net   |                   |      |
|     |     |       | Worth               | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 235 |     | 7     | SEC SCA: Secondary  | -9999999 to       | Y    |
|     |     |       | Student's           | 9999999           |      |
|     |     |       | Contribution from   |                   |      |
|     |     |       | Assets              | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 236 |     | 7     | SEC FTI: Secondary  | -9999999 to       | Y    |
|     |     |       | FISAP Total Income  | 9999999           |      |
|     |     |       |                     |                   |      |
|     |     |       |                     | Blank = None      |      |
|     |     |       |                     | Calculated        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 239 |     | 6     | Assumed Student's   | -999999 to 999999 | Y    |
|     |     |       | AGI                 |                   |      |
|     |     |       |                     | Blank = No        |      |
|     |     |       |                     | assumption        |      |
+-----+-----+-------+---------------------+-------------------+------+

###  Signed Numeric Fields Table (Continued)

+-----+-----+-------+---------------------+-------------------+------+
| **  | **  | **    | **Field Name**      | **Valid Field     | **F  |
| ISI | SAR | Field |                     | Content**         | ound |
| R** | Fi  | Len   |                     |                   | Only |
|     | eld | gth** |                     |                   | on   |
| *   | \   |       |                     |                   | IS   |
| *Fi | #** |       |                     |                   | IR** |
| eld |     |       |                     |                   |      |
| \   |     |       |                     |                   |      |
| #** |     |       |                     |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 241 |     | 6     | Assumed Student's   | -999999 to 999999 | Y    |
|     |     |       | Income from Work    |                   |      |
|     |     |       |                     | Blank = No        |      |
|     |     |       |                     | assumption        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 242 |     | 6     | Assumed Spouse's    | -999999 to 999999 | Y    |
|     |     |       | Income from Work    |                   |      |
|     |     |       |                     | Blank = No        |      |
|     |     |       |                     | assumption        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 256 |     | 6     | Assumed Parents\'   | -999999 to 999999 | Y    |
|     |     |       | AGI                 |                   |      |
|     |     |       |                     | Blank = No        |      |
|     |     |       |                     | assumption        |      |
+-----+-----+-------+---------------------+-------------------+------+
| 258 |     | 6     | Assumed             | -999999 to 999999 | Y    |
|     |     |       | Fa                  |                   |      |
|     |     |       | ther's/Stepfather's | Blank = No        |      |
|     |     |       | Income Earned from  | assumption        |      |
|     |     |       | Work                |                   |      |
+-----+-----+-------+---------------------+-------------------+------+
| 259 |     | 6     | Assumed             | -999999 to 999999 | Y    |
|     |     |       | Mo                  |                   |      |
|     |     |       | ther's/Stepmother's | Blank = No        |      |
|     |     |       | Income Earned from  | assumption        |      |
|     |     |       | Work                |                   |      |
+-----+-----+-------+---------------------+-------------------+------+

### Making Signature Corrections

> Signature information is required to resolve signature rejects
> (rejects 14, 15 and 16). Signature information does not need to be
> provided on other standard corrections unless you are using 99 as the
> transaction number. If you have a transaction that was a reject 14, 15
> or 16, simply correct SAR field #099 (Signed By) to A (Applicant) or B
> (Both = Student and Parent), as appropriate.
>
> If you need to add a signature to a student's record on the Web hold
> file you must use the layout for Signature Correction Export Record
> Layout (SIGS03IN) found in section 3, Record Layouts. You can correct
> the student or parent signature using this layout. You must make sure
> the student included your school on the FAFSA or correction.

### Adding Your Federal School Code to Receive Electronic Data

> A school cannot make an electronic correction unless the school has
> been designated on the applicant transaction. You can add your Federal
> School Code to the list of schools receiving data electronically along
> with correcting other fields on the record by using the Correction
> Record layout (CORR03IN).
>
> Follow these steps to add your Federal School Code and/or to make
> corrections:

1.  In the first position of the record, enter 3 to indicate that this
    is a correction to a 2002-2003 applicant transaction.

2.  In positions 2 through 10, enter the applicant\'s original SSN. This
    is the number reported by the applicant on the FAFSA form and does
    not reflect any corrections to the SSN that might have been made.

3.  In positions 11 and 12, enter the first two letters of the
    applicant\'s last name. These are the letters reported by the
    applicant on the FAFSA form and does not reflect any corrections to
    the last name that might have been made.

4.  In positions 13 and 14, enter the transaction number of the
    applicant record being corrected. For example, enter 01 to correct
    the first transaction on file at CPS. The transaction does not
    necessarily have to be the latest one on file at CPS. If the
    transaction number being corrected is not on the CPS database, the
    record will be rejected. You can use transaction 99 to add your
    school code to the most recent transaction on the CPS Database.

5.  Enter 112 in the SAR Field Number Correction #1 field, positions 15
    through 17 (corresponding to the SAR Field #112, the Data Release
    Number (DRN).)

6.  Enter the student\'s DRN in Correction Data 1 field, positions 18 to
    52 (Remember to make it left justified, and leave any unused bytes
    blank.)

> **Note:** A unique DRN is assigned to each Title IV applicant. It
> appears only on paper SARs and ISIR records generated in response to
> electronic FAFSAs. If a valid DRN is not present on the correction
> record containing the Federal School Code change, the record is
> rejected.

7.  Enter the SAR field number associated with the Federal School Code
    position being changed in the SAR Field Number Correction #2 field,
    positions 53 through 55. Possible field numbers are 086, 088, 090,
    092, 094, and 096.

8.  Enter the Federal School Code in the Correction Data 2 field
    positions 56 to 61. Leave positions 62 to 90 blank.

-   The number can be changed only to the number of the participating
    Electronic Data Exchange (EDE) school. You also must enter this
    number in the EDE Federal School Code field, (position 471-476). If
    the codes in these two fields do not match, the record is rejected.

-   Schools may modify the Federal School Code and make other
    corrections to the applicant record on the same correction
    transaction.

9.  Enter the date you created this record in positions 553-560, the EDE
    Transaction Receipt Date in CCYYMMDD format.

10. Enter 00001 in positions 575-579, the serial number field. If you
    exceed 12 corrected fields, create a new record. The serial number
    on the second record is also 00001. The serial number increments
    with a second student's record.

11. Enter an "H" for Correction in position 580, Record Type.

### Tips for Corrections

When your school submits an ISIR correction to CPS, we use the
transaction number provided in positions 13 to 14 as a template. We make
changes to the fields you indicated, leaving other fields unchanged.
Your Federal School Code must be one of the six listed, but it does not
have to be the first college choice on the transaction to be processed
by CPS. You receive the processed results in the CORR03OP message class;
all other schools listed on the transaction will receive the new ISIR in
the SARA03OP message class.

If you are submitting a Dependency Override or FAA Adjustment
(professional judgment) as part of the correction record, only your
school receives the resulting corrected ISIR transaction. Also, do not
send a Dependency Override correction with a FAA Adjustment to a
transaction without an EFC. If there is no EFC, first send the
Dependency Override with any other corrections necessary to obtain an
EFC. Then, submit the FAA Adjustment to the transaction with the
dependency override and the EFC.

### Requesting a Duplicate ISIR

> Schools request duplicate ISIRs using the correction message class
> (CORR03IN). To see a full record layout refer to the Record Layout
> section under Duplicate Request Export Record Layout. Use the
> following steps to create a record requesting a duplicate ISIR:

1.  In the first position of the record, enter 3 to indicate that this
    is a correction to a 2002-2003 applicant transaction.

2.  In positions 15 through 17, enter 199. This signifies a request for
    an ISIR record. (Note: Leave positions 2 through 14 blank.)

3.  In positions 18 through 26, enter the applicant\'s original Social
    Security Number (SSN). This is the number reported by the applicant
    on the FAFSA form and does not reflect any corrections to the SSN
    that might have been made.

4.  In positions 27 and 28, enter the first two letters of the
    applicant\'s last name. These are the letters reported by the
    applicant on the FAFSA form and do not reflect any corrections to
    the last name that might have been made.

5.  In positions 29 and 30, enter the transaction number of the
    applicant record being requested. For example, enter 01 to request
    the first transaction on file at CPS. The transaction does not
    necessarily have to be the latest one on file at CPS. If the
    transaction number being requested is not on the CPS database, the
    record is rejected. You can use transaction '99' to request the most
    recent transaction on the CPS database provided your Federal School
    Code is listed on the most recent transaction.

6.  In positions 471 through 476, enter your Federal School Code.

7.  In positions 553 through 560, enter the Transaction Receipt Date,
    the date you are requesting the duplicate transactions.

8.  In position 580, enter D (duplicate) for the Input Record Type.

> Up to 12 duplicate ISIRs can be requested on a single record.
>
> Repeat steps 2 and 3, using the remaining data fields of the layout to
> request more than one record. If more than 12 ISIRs are required, then
> create an additional record by repeating steps 1 through 6.
>
> **Note:** The school can request, as a duplicate, any existing
> transaction for a student as long as that transaction number contains
> the school\'s Federal School Code. Transaction 99 can be used as
> described in step 5 above. If the latest transaction on the CPS
> database does not include that school, the request is rejected.

### Response to a Correction/Duplicate Record

> Schools receive one batch of ISIRs for each batch of correction
> records submitted. The batch, or message class, of ISIRs is titled
> CORR03OP. It contains one ISIR for every submitted student correction
> or student duplicate request, not rejected for a transaction reject
> reason.

#### Rejected Correction/Duplicate Records

> There are two categories of rejections for submitted correction
> records,transaction and compute rejects.

1.  **Transaction Rejects**

> A transaction reject prevents the correction record from being applied
> to the student\'s record. If a record is rejected for one or more
> reasons, the school receives an error report in message class CORE03OP
> (see EDE Record Level Error Report Import layout in the Record Layouts
> section). No ISIR is created.

2.  **Compute Rejects**

> CPS contains a series of edits that evaluate all incoming FAFSA and
> correction data for consistency and completeness. These edits apply to
> all data from electronic, Web, and paper input. An Expected Family
> Contribution (EFC) is not computed for a correction rejected for a
> compute reject reason. However, an ISIR is produced. Correction and
> duplicate ISIRs with a compute reject are returned in the CORR03OP
> message class. The reasons for the compute reject are coded on the
> ISIR in positions 611-624. Refer to the Processing Codes section for
> information on interpreting these reject codes.
>
> There are two types of FAFSA compute reject reason codes:

-   Numeric: Certain data items be orre a valid ISIR can be generated
    (Non-Verifiable).

-   Alphabetic: Certain data items be ither corverified balid ISIR can
    be generated (Verifiable). An alphabetic reject reason code is a
    verifiable data element, meaning the data given is questionable but
    could be correct.

> In the paper system, a student can verify a data field by re-entering
> the same information in the SAR correction column for the field in
> question. In the electronic process, the school may verify the data
> (re-enter the data as a \"correction\"), or set the appropriate reject
> override (found at the end of the CORR03IN record layout in positions
> 527-535), and transmit the correction record to CPS. Data that must be
> verified or corrected in response to each reject reason is provided in
> the Processing Codes section.
>
> A student's record may not have an EFC if the record contains
> questionable data and has an FAFSA reject reason code(s). The reject
> reason codes are found in positions 611-624 on the ISIR. They explain
> the questionable and highlighted field(s).

## CPS Header and Trailer Records

> Data transmitted through the SAIG are separated by message class for
> identification and processing purposes. Each message class consists of
> the following segments:

-   Header record

-   Data record(s)

```{=html}
<!-- -->
```
-   Trailer record

> Data records vary by processing function. Each record format is
> provided in the Record Layout section of this Technical Reference.
>
> Each batch of data records must be preceded by a header record and
> followed by a trailer record. The end of each record (header, trailer,
> and data) is marked by a CR/LF (carriage return/linefeed, ASCII 13,
> 10). An EOF marker (end of file, ACSII 26) is optional.
>
> The format and content of header and trailer records are found in the
> Record Layout section:

-   Received from the Central Processing System (CPS) message header and
    trailer records -- those records produced by CPS to send to the
    destination point, such as SARA03OP.

-   Sent to CPS message header and trailer records --those records
    produced by the destination point to send to CPS, such as CORR03IN
    messages.

> ***Note the following about batch headers and trailers:***

-   The header and trailer records are the same lengths as the detail
    (data) records.

-   Only data records of the same type (for example, FAFSAs) and the
    same year can be batched together. (There is one exception --
    Corrections and Duplicates can be batched together.)

-   The Counts in the trailer are for the number of student records, not
    the number of data records.

> ***Note the following about batch numbers:***

-   Destination points are responsible for supplying a unique batch
    number on the header and trailer records sent to CPS.

-   The structure of the 23-character unique batch number is as follows:

> #X3ZZZZZZCCYYMMDDHHMMSS where,
>
> #X = the record type indicator, with a pound sign (#) followed by the
> character below to signify the record type:
>
> A = Electronic App ISIRs
>
> C = Correction/Duplicate ISIRs
>
> E = Automatic ISIRs
>
> F = Federal Data Requests
>
> G = System Generated
>
> I = Year To Date (YTD)
>
> K = State Agency NonResident ISIRs
>
> L = State Agency Resident ISIRs
>
> S = Signature Corrections
>
> 3 = year indicator (always "3" for 2002-2003 data)
>
> ZZZZZZ = the 6-digit valid Federal School Code
>
> CCYYMMDD = the current date in century, year, month, day format
>
> HHMMSS = the current time in hours, minutes, seconds format
>
> *Example*:
>
> A batch number of #C3E1234520020509141532 signifies a batch of
> 2002-2003 corrections transmitted to CPS from a school with a 6-digit
> code of E12345 on May 9, 2002 at 2:15:32 PM.

-   Batch level errors can be found in section 4 under Batch Level Error
    Messages

> **Note:** Non-unique batch numbers are considered a duplicate batch
> and are not processed by CPS.