Prepared by a joint committee of MnSCU, DCFL, U of M and Private Colleges. Direct all inquiries about this document to:
George Hudachek
Assistant Director of Admissions
Phone: 612/25-5010
Fax: 612/626-1693
E-mail: g-huda@tc.umn.edu
The purpose of this document is to assist secondary and post-secondary schools in Minnesota who wish to implement a process for exchanging student academic transcript information using Electronic Data Interchange (EDI). The potential benefits of using this technology to exchange information between schools and colleges are significant. This guide is intended for use by registrars and computer staff to aid in using EDI for student records.
These procedures refer to electronic transcripts exchanged by schools within Minnesota. We have attempted to create a process that includes information that currently appears on paper records for use by all institutions. These recommendations should, therefore, work for exchanges with schools in other states.
All institutions will continue to accept paper transcripts and other documents from schools who are not using EDI.
All sending institutions must have certain things in place to make transmission of electronic transcripts possible.
1. All data which is to appear on the student transcript must be maintained in a computer data base.
2. All individual courses must have a unique identifier, so that each course can be evaluated by the receiving institution. Students may be identified by Social Security Number but this is not a requirement.
3. A computer program must be in place to produce a transcript format report from the computer files and convert institution-specific information into standard codes and formats.
4. Translation software must be purchased to map information into the SPEEDE format.
5. A connection to the Internet is required. Although electronic transcripts could be transmitted with a diskette or over a telephone line, the Internet provides a more efficient and economical connection.
6. The sending institution will need to create a log of transcripts sent. This log will be used to verify acknowledgements sent by a partner institution upon receipt of an EDI transcript.
7. Each institution should register with AACRAO as a SPEEDE/Express participant. Registration forms are available at <web address>.
These procedures are based on the American National Standards Institute X12 Transaction Sets 130 and 131, version 3.0. (This is currently the only version supported.) Transaction Set 130 is the standard student academic record. Transaction Set 131 is the format for the acknowledgement that is returned to the sending institution upon receipt of an electronic transcript. These standards were developed by the American Association of Collegiate Registrars and Admissions Officers (AACRAO) in cooperation with the National Center for Educational Statistics (NCES) and the Council of Chief State School Officers (CCSSO). They have been in effect since 1990 and are currently used primarily in the United States and Canada.
There are several common coding structures for information such as student status and classification within the standards. Where this occurs, local codes at the sending institution will need to be converted to these standard codes before sending the transcript.
Creating an EDI formatted file directly from a student information system database requires a lot of time and detailed knowledge of electronic data interchange standards. Therefore, most institutions purchase translation software to create the EDI formatted file.
Each organization needs to have a computer program that extracts data from its record system. This program performs two functions: the first is the creation of a "flat" file that can be read by the EDI translation software; the second is to convert local data to standard coding structures so that it can be interpreted by the receiving institution. Once the "flat" file has been created for a transcript it is read by the EDI translation software and an EDI format file is created for transmission to the receiving institution.
There are three ways of transmitting EDI information over the Internet:
1. Attach the EDI file to an E-Mail message and send it to the receiving institution.
2. Use File Transfer Protocol (FTP) to log on to a computer at the receiving institution and copy the EDI file directly to that computer.
3. Send the EDI file to the AACRAO EDI server by either of the above methods and allow the AACRAO server to deliver the file to the receiving institution.
The third method is the one preferred by schools in Minnesota as it eliminates the need for multiple login sites and reduces security concerns.
Using an electronic method to transfer transcripts does not have some of the security processes that are currently available with paper. For example, there are no seals or postmarks to ensure that a transcript actually came from the institution indicated. To move to electronic transcripts, new processes need to be established to ensure the authenticity of records. We anticipate that each college will register with AACRAO as a SPEEDE/Express participant. Acknowledgements of transcript receipt will be sent to the registered Internet address for each institution and not to the address from which the transcript was sent. The sending institution will need to validate the acknowledgement using the process described in the following section.
To support the acknowledgement process, each sending institution should maintain a log of each transcript sent electronically. This log should contain the information expected to be returned in the acknowledgement file. Receiving institutions will return acknowledgements to the sending institution using the 131 transaction set. As each acknowledgement is received, it should be compared with the log to detect any discrepancies or errors. Any discrepancies found should be reported immediately to the partner institution. The receiving institution should follow up on any questionable transcripts to determine the reason for the discrepancy.
As with paper transcripts, all electronic transcripts will fall under the jurisdiction of the Family Educational Rights and Privacy Act of 1974. All incoming electronic records will be given the same protection as the paper records.
Receiving institutions should retain transcripts for students who apply, but do not enroll, for the same time period that they so for paper transcripts. If a student does not enroll within that time, the transcripts are destroyed. Transcripts for students who apply and subsequently enroll in the university are retained permanently. These retention rules will apply to both paper and electronic transcripts.
Electronic Data Interchange is used widely by business to conduct electronic commerce. Because many of the transactions in electronic commerce involve significant sums of money, it is common for trading partners in business to establish legal trading partner agreements with each other. Using Electronic Data Interchange for academic records involves a simple transfer of information and does not involve financial or liability issues. Therefore, we do not believe that legal trading partner agreements will need to be negotiated between each institution involved in trading electronic transcripts. It is our opinion that registration as a SPEEDE/Express participant with AACRAO constitutes a defacto trading partner agreement and that no further individual agreements will be necessary.
Once a school is ready to send test electronic transcripts it is recommended they begin a period where both paper and electronic transcripts are sent in parallel to one or more partner institutions. When these two documents are received, they should be compared for consistency. Once the institutions are assured that both the paper and the electronic transcript contain the identical information, a date can be established for cutover to electronic transcripts only.
Institutions may initially wish to produce a printed transcript from a SPEEDE record and process it internally the same as if a paper record was received from the school. This will speed processing of the transcript by 3-4 days over sending transcripts by U.S. mail. In addition, a common format for the transcript will allow evaluators to evaluate coursework faster. Eventually institutions will wish to develop software to transfer the SPEEDE transcript directly into their data files, and to evaluate by computer coursework for undergraduate admission. This will further reduce the time needed to respond to a prospective student with an admissions decision. When combined with an electronic application for admissions, electronic transcripts have the potential to significantly improve the time required to make an admissions decision, and to inform the applicant of that decision.
The SPEEDE standard does not provide for coding class rank types. If both a weighted and unweighted class rank are provided on the high school transcript and therefore are both sent in the data transmission, it is recommended that a comment indicating the type of rank be included in the Summary NTE segment.
The SPEEDE standard contains only a single code for an associates degree. We wish to differentiate between an Associate of Arts, or Science, and an Associates of Applied Science Degree, for example. It is recommended that schools further define the student's academic program by including curriculum codes in the session segment (SES 12) and field of study codes in the degree segment (FOS 03). The codes in the session fields will allow for correct evaluation of a student's record prior to the granting of a degree.
The recommended segments/fields to be included for the transcript are in the following section. In general, transcript components identified in the AACRAO Academic Record and Transcript Guide were used to develop this list. Some data fields are required by the SPEEDE transaction set.
Among other things, this section explains most of what might be received on an electronic SPEEDE transcript. You should have a copy of the SPEEDE/EXPRESS Implementation Guide. The SPEEDE/ExPRESS format was designed to be robust, allowing schools to send any information needed on their regular transcripts, as well as in the transfer of student records to other school districts or to state education agencies. It is very flexible, but you will use only a small portion of that capacity.
Note that data elements required by X12 are required for technical reasons - to make the format unambiguous, rather than to serve the business function of carrying transcript data. The fact that the same transaction set serves both Kindergarten thru 12th grade and postsecondary causes many “necessary” postsecondary items to not be required for the format, and the same for K-12 items.
1. ST segment. Starting segment for any transaction set, including a single TS130 transcript (which will be terminated with an SE segment). This segment is required by ANSI ASC X12, but contains no information found on a printed transcript, except perhaps the fact that it is a transcript.
ST01 Transaction set identifier ('130' for student educational transcript, '131' for acknowledgement)
ST02 Sender-generated control number, which will be checked against SE02 to be sure the transmission was accurate and complete
2. BGN segment. (Beginning Segment, following start). Also required, and containing mainly housekeeping data, such as dates, plus reference numbers for later identification of this document.
BGN01 transaction set purpose code ('00' for original transmission - use this as a default, '05' to replace a transcript sent earlier, '15' for resubmission, '18' for re-issue)
BGN02 reference number for transcript. (some schools use the yyddd date, followed by a sequence number for that date)
BGN03 date.
BGN04 time
BGN05 time code ('CT' for Central Time).
BGN06-08 rarely used for SPEEDE.
3. ERP segment (educational record purpose).
ERP01 'PS' for postsecondary transcript, 'DP' for a pk-12 transcript sent to a postsecondary institution.
ERP02 status reason code ('B48' sent at request of student, 'B49' record sent to replace earlier one, 'B50' requested record being sent).
ERP03 action code (used in TS146 Request for transcript, not here).
4. REF segment (Reference numbers for the individual for whom the transcript is issued). One or more numbers, along with their code set qualifiers. SSN would generally be carried in one of these segments.
REF01 reference number qualifier ('50' state student id, 'LR' local student id, 'SY' Social Security number).
REF02 number itself.
REF03 up to 80 character Description. Use this if number system requires explanation.
5. N1 segments. Two separate N1 segments (internal to transcript) to identify sender and recipient of transcript. The sender N1 segment is generally listed before the N1 for the recipient. Either can also have N2, N3, N4, and/or PER following to provide additional information, but these are rare with SPEEDE transcripts, with the possible exception of the PER, which can indicate the person who is to receive the transcript, if different from the usual (admissions office). General use is FICE, IPEDS, ATP or ACT.
N101 Entity identifier code ('AS' (AACRAO Sender) indicates that the institution identified is the sender of a postsecondary transcript. 'AT' signifies the recipient of a postsecondary transcript.)
N102 35 character textual name of the institution. This is optional, but strongly recommended.
N103 Code qualifier for institution. Most common examples are '71' for IPEDS Unit I.D., '72' for ATP (College Board's admissions testing program, codes maintained by ETS), '73' for FICE. '74 for American College Testing program (ACT).
N104 Institution code from the taxonomy indicated in N103. The ATP code for colleges is 4 digits, whereas FICE is 6.
Some programmer/analysts who handle SPEEDE transcripts have expressed a preference to receive a PER segment in the N1 loop for the sender, specifying name of administrative contact, and RG=registrar, EM=electronic mail address, and TE=telephone number. This information would not vary from transcript to transcript, and would likely be the Registrar.
6. IN1 and IN2 segments to identify the types, formats, and components of the name of the student for whom the transcript is issued. IN1 provides the type of individual being named, and one or more IN2 segments carry the name itself, or parts of the name. Sending upper/lower case is okay in the text part of the name. Recipients with upper case only need to watch for this and convert to upper case before storing or using for matching.
IN101 '1' for person.
IN102 Name type = '01' for given name, '02' for current legal name, '04' for name of record, '05' for previous name.
IN103 'S2' for student.
IN104 'SY' to indicate an SSN in IN105, '50' for a state number in IN105.
IN105 Value of student number, SSN or otherwise.
IN201 Name component qualifier. '01 for prefix, '02' for first name, '03 middle name, '04 second middle name, '05' last name, '06' first initial, ''07' first middle initial, '08' second middle initial, '09' suffix, '16' composite (last, comma, first, etc..).
IN202 Value of the name part specified in IN201.
If you carry them in your student data base, including a former name of the student is a good idea. It is done with a separate IN1 loop, and uses IN102='05' to separate that from the name of record. Please do not include an additional IN2 segment with IN201='15' (also maiden or former name) in the IN1 loop for name of record.
7. SE trailer segment for the transcript.
SE01 Total number of segments in the transcript, including this one.
SE02 Transaction set control number, must agree with ST02.
8. PCL records showing other colleges attended.
PCL01 Code qualifier, as in N103.
PCL02 Code for other institution attended, from code set specified in PCL01.
PCL03 Attendance date range format specification. 'RD2' for a format allowing 92-96, 'RD4' for a year range such as 1992-1996, 'RD6' for a format allowing 960118-970930.
PCL04 Date range attended, in format specified above.
PCL05 3 digit code for level of highest degree received. Examples are '2.3' for associate, '2.4' for baccalaureate, '2.5' for baccalaureate honors, '4.2' masters, '4.4' doctorate.
PCL06 Year highest degree awarded, in ccyy format.
PCL07 Text name of institution. highly recommended.
9. SST showing college scholastic status and high school data.
SST01 Three digit code for final status of pre-k thru 12th grade. Most colleges will omit this.
SST04 Current scholastic status at college issuing transcript. 'B27' for eligible to return or continue, 'B28' for suspension or dismissal, 'B39' for probation.
SST05 Qualifier for date eligible to return. CM for date in ccyymm format.
SST06 Date eligible to return (if suspended).
SST07 Current enrollment status. 'B30' for student currently enrolled, but courses in progress excluded from transcript, 'B31' for not currently enrolled, 'B34' for enrolled, with current courses included.
SST08 Current academic level of student. '23' for postsecondary junior, for example.
SST09 Optional 'Y', 'N', or 'U' (unavailable) for residency status.
N1 segment can follow the SST to identify high school attended.
10. At least one SUM segment to show overall academic summaries (hours and GPA). This is referenced in the TS131 acknowledgement, so really must be included. Most schools will also choose to include SUM records for each session attended. If a school computes graduate and undergraduate summaries separately, then two overall SUM records might be used.
SUM01 single byte for credit type, typically 'S' for semester hours, 'Q' for quarter hours, or 'C' for continuing education.
SUM02 Course or grade level for the student. 'G' for graduate level work, 'U' for undergrad.
SUM03 Use 'Y' because the overall summary is cumulative.
SUM04 GPA hours. Real number, with decimal inserted if needed to carry a non-integer value.
SUM05 Hours attempted.
SUM06 Credit hours earned.
SUM09 GPA, with decimal included if needed.
11. LX segment which adds nothing except a separator needed by X12 to guarantee unambiguity of notes and other segments.
12. An SES segment to label and summarize each session/semester the student attended.
SES01 Starting ccyymm of the semester, quarter, or term. For example, the spring semester of '97 would be represented by 199701 if it started in January.
SES02 Count for sessions with identical start months. This is a one-digit integer, generally 1. It could be two to represent concurrent work taken elsewhere, including correspondence work completed during the same term, or work taken from another consortium partner. We strongly recommend that transfer work taken concurrently with work taken at the sending institution be sent in a separate SES loop, rather than using an N1 override in a single SES loop.
SES04 Type of session. '2' for semester, '3' for trimester, '4' for quarter.
SES11 Not required, but of interest for research purposes, a code qualifier for CIP or HEGIS might be included for the major area of the student.
SES12 The actual CIP or HEGIS code for the major. Optional, but SES11 and SES12 must either both be included or both omitted.
SES14 Scholastic status for the semester. 'B39' for probation, 'B40' for suspended, 'B35' for highest honors.
13. A CRS record for each course taken at the issuing institution.
CRS01 Basis for credit, generally 'R' for regular enrollment. 'I' for international baccalaureate, 'N' correspondence, 'A' College Board's AP credit.
CRS02 Type of credit. 'Q' for quarter hours, 'S' semester hours, 'N' no credit.
CRS03 Credit associated with course, in hours identified in CRS02.
CRS04 Credit hours earned by student (usually 0 or = CRS03).
CRS05 Academic grade qualifier, as maintained by AMCAS. For instance, '25' means the institution awards grades of A, B, C, D, or F, and uses a standard 4-point scale. Special qualifiers in the 500-series cover incompletes, courses in progress, and so on. It would be good to avoid use of code 64 ("other" pass fail types), which is defined for non-standard symbol. It is a vague code and must be worked out with the sender before it can be processed by the recipient. It is preferred to convert these into 63's (Pass/Fail: S,U), 501/502's (Passing or Failing, respectively, in a pass/fail course), or 530's/540's (Other passing or Failing grade, respectively).
CRS06 Actual grade.
CRS07 'Y' if honors.
CRS08 Academic level of the course. 'L' for lower division, 'H' for higher or upper division, 'U' for undergraduate, 'R' for remedial, 'G' for graduate.
CRS09 Repeat indicator.
CRS10 Qualifier for curriculum code. This may be used more later for analysis and reporting purposes.
CRS11 CIP or other academic code from taxonomy specified in CRS10. Not initially used very much.
CRS12 Grade points earned.
CRS14 Department abbreviation for the course at the school issuing the transcript (equivalent course if transferred)
CRS15 Course number for course at issuing school.
CRS16 35 character text name of course (highly recommended).
CRS20 Credit source. 'IA' for institutional agreement, 'TC' for transfer credit (follow with CSU segment).
A 'T' can be sent in the CRS01 field for transfer work, but that field may be needed for another characteristic. CRS20 set to "TC" is a better bet. It is best to send the name of school even if you use code and code qualifier because there are so many different codes that can be used, and not everyone will have a code crosswalk table. List all prior colleges attended in PCL segments. List school at which student took transfer credit via an N1 segment in individual semester (session) segments.
14. CSU segment for supplementary info on special (or transfer - if you transcript them) courses.
CSU01 Department abbreviation for course at original school.
CSU02 Course number at school where course was taken.
15. A DEG record for each degree earned at the issuing institution. It must be included in the SES loop for the session or term awarded. It can, but often does not, include a special SUM segment and a FOS segment for field or study specification. NTE segments for special honors or specializations are quite appropriate.
DEG01 3 character degree code. For instance, '2.3' for associate degree, '4.2' for master's (as with PCL05).
DEG02 Qualifier for date awarded. D6 for yymmdd, D8 for ccyymmdd, YM for yymm.
DEG03 Date awarded, in format specified in DEG02.
DEG04 Degree title. Text such as 'Bachelor of Science'
DEG05 Honors level. 'B35' for highest honors, 'B36' 2nd highest honors, 'B37' third highest honors.
SUM02 'M' for work in major or program, if summaries are carried for this.
FOS01 Academic field of study level or type. 'M' for major, 'N' for minor, 'S' specialization, 'T' teaching.
FOS02 Qualifier for field of study code (optional).
FOS03 Field of study code (CIP, HEGIS, etc..).
FOS04 Text for field of study.
FOS05 Honors message for field of study.
16. Free form notes, which may be included almost anywhere (but please check the segment and loop diagram to be sure). Where possible, coded data elements rather than free form notes should be used to carry information, allowing procedures at the receiving school to be automated. The transaction set TS130 segment diagram shows where notes may be placed. Placement determines what higher segment is explained or expanded by the specific free-form note, but if possible, including the reference within the note will ensure the right interpretation. The NTE segment may occur just once, or up to 100 times in a particular location. The segment map provides that number.
NTE01 Never used in SPEEDE transcript
NTE02 60-character free-form message.
Consider adding the following additional items to those required by SPEEDE:
17. DMG segment (demographic information). Date of birth, and (optionally, sex, ethnicity, race, marital status, and citizenship status).
DMG01 Code for format of date of birth.
DMG02 Date of birth.
DMG03 Gender code (F, M, or U if provided).
DMG04 Marital status code.
DMG05 Race or ethnicity ('A' for Asian, 'B' for Black, 'C' Caucasian, 'E' other race or ethnicity, 'H' Hispanic, 'I' American Indian or Alaskan Native, 'N' Black Non-Hispanic, 'O' White Non-Hispanic).
DMG06 Citizenship status (example '1' U.S. Citizen).
18. SUM segments with GPA's and academic totals by semester. Generally similar to the overall academic summary (above).
SUM03 Cumulative summary indicator, 'Y' for cumulative, 'N' for non- cumulative (implies semester or term only). One may send multiple SUM segments in order to carry both session and cumulative totals.
19. RAP segments as needed to carry requirements, proficiencies, and attributes.
20. Additional REF segments for special course identifiers. Institutional researchers and those analyzing feedback transcripts may be assisted by other information, such as common course number or CIP code.
21. TST segments to carry test score records, including the test identity and date, along with SBT subtest (identification) segments and SRE (actual) test score segments.
22. N3 and N4 segments following the IN1 to provide student address info.
Receiving institution ISA08*, GS03*, N104
Sending institution ISA06*, GS02*, N104
Test/Prod transmission ISA15*
Date/time of transcript creation BGN03-05
Secondary vs Postsecondary ERP01
Reasons for delivery ERP segment
Student name IN202
SSN REF02
Student Address N3, N4 segments
Student Phone PER segment
Date of Birth DMG02
Gender DMG03
Marital status code DMG04
Ethnicity DMG05
Citizenship DMG06
High school attended N104 in SST loop.
High School Diploma status SST01
Current status at issuing institution SST04-06
Current Enrollment Status SST08
Residency SST09
Academic Status by Session SES segment
Tests Taken TST segment
Subtest identification SBT segment following TST
Test or subtest Scores SRE segment following TST
Information about test NTE segment following TST
College identifiers PCL01, 02, 07
Attendance Range PCL03-04
High Degree Earned PCL05-06
Cumulative undergrad GPA, hours Overall SUM segment
Cumulative graduate GPA, hours Another Overall SUM
Semester totals SUM following SES
Cumulative totals by semester Another SUM after SES
Credit basis (sem, qtr, etc..) SUM01
Where Codes Exist Overall RAP segments
With no codes NTE segments
Start date SES01-02
Override Institution N1 following SES segment
Sem/Qtr/Trimester SES04
Academic major SES11-12
Probation, dismissal, honors SES14
Term or session SES01
Basis for credit CRS01
Sem or Qtr Hrs type CRS02
Hours (value of course) CRS03
Hours Earned CRS04
Grade legend or special value CRS05
Grade awarded CRS06
Course level CRS08
Repeat indicator CRS09
Curriculum codes CRS10-11
Grade points earned CRS12
Department abbreviation for the course (at school issuing transcript) CRS14
Course number for course CRS15
Course title/description CRS16
Credit source CRS20
Info on transfer coursework (in terminology of initial school) CSU segment
Requirements or proficiencies met by, or attributes of course, where codes exist RAP segment after CRS
Special info about course – uncoded NTE segment after CRS
State or National Course reference nbr REF seg following CRS
Issuing Transcript Degree code (3 char) DEG01
Date awarded DEG02-03
Degree title DEG04
Degree honors DEG05
Academic Summaries for work on degree SUM segment after DEG.
Field of Study ident, honors FOS segment after DEG.
General NTE close to top of file
About individual or demographics NTE after IN1
About test scores NTE after TST
About academic summaries NTE after SUM
About Session or Term NTE after SES
About a Course NTE after CRS
About a Degree NTE after DEG.
1. ISA (outer envelope - external to a set of transcripts, acknowledgements, or other transaction sets) record codes for sender and recipient. Documentation for the ISA-IEA and GS-GE envelopes is found with Interchange Control information, rather than with the data definition of the transcript (transaction set #130). The ISA is the only fixed-length segment, and this allows it to be examined by the recipient to determine the values used for data element and segment delimiters. For schools using the AACRAO EDI Internet Server, the ISA address of both sender and recipient must agree with those in the Server registrant table.
ISA05 2 character code set qualifier for code identifying the sender of the transcript to the delivery medium (a VAN or the Internet Server, for instance). Typical values are 22 (FICE) and ZZ (mutually defined).
ISA06 15 character code identifying the sender. Must be from the code set identified in ISA05.
ISA07 code set qualifier for recipient.
ISA08 15 character code (counting spaces) for recipient, from set identified in ISA07.
ISA09 Date (19970803, for example, for August 3, 1997).
ISA10 Time of the interchange (2205 for 10:05 PM).
ISA12 Interchange control version number ("00304" for version 2). Note that interchange control standards do not incur significant change very often.
ISA15 'T' if test, 'P' if production (the Internet Server can use this to deliver test packets to different physical addresses).
2. GS envelope allows specification of a specific version or release of the standard being used, and it encapsulates like sets of transactions. That is, if an ISA envelope contains 4 transcripts (TS130) and 2 transcript acknowledgements (TS131) intended form the same destination, these should be wrapped in a pair of GS-GE envelopes within the ISA-IEA envelope.
GS01 Functional ID code ('ED' for student education record, or transcript, 'AK' for TS131 acknowledgements).
GS02 Code identifying sender. Codes agreed upon by trading partners, but without the usual (N103 and ISA07) code qualifiers.
GS03 Code identifying recipient.
GS08 Version/release identifier identifying the version of the X12 standards used for this transaction set. Examples are '003041ED0020' for release 2 and '003052ED0030' for release 3.
3. GE and IEA trailer segments for the outer envelopes.
An acknowledgement is to be generated for each transcript received, and it is to be delivered to the "certified acknowledgement address". Received acknowledgements are to be (programmatically) reconciled with records of transcripts sent, with discrepancies investigated and reported. This is a major part of the security built into the protocol, as it covers both authentication and modification (this leaves privacy, which can be covered by encryption or by contracts with public communication carriers). TS131 is very lean, with the following items automatically pulled from the received transcripts:
1. ISA, GS, ST, and BGN segments - all required by ANSI ASC X12, and the BGN02 ties back to the ST02 in the received batch, identifying the batch.
2. N1 records to identify sender and recipient.
3. REF to identify the individual.
4. QTY records showing the quantity (number) of degree and course records received.
5. SUM segment with last overall summary from the transcript sent.
6. IN1 and IN2 for student name.
7. SE terminator, along with GE, IEA.