972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Education

EDI 130 Student Educational Record (Transcript)

The X12 document schools, districts and colleges use to send current and historical records of students' educational accomplishments.

Sent by
School, school district or postsecondary institution
Received by
Another educational institution or authorized recipient
Standard
ANSI ASC X12

What is an EDI 130?

The EDI 130 Student Educational Record (Transcript) is the ANSI X12 transaction set used by schools, school districts and postsecondary institutions to transmit current and historical records of students' educational accomplishments and other significant information.

Transcripts list courses, grades, credits, degrees and test results. Sending them electronically between institutions replaces mailed paper transcripts, speeds up admissions and transfer credit decisions and reduces fraud. The receiving institution confirms receipt with the 131. In many systems, newer XML transcript standards are now used alongside or instead of the 130.

How the EDI 130 worksDiagram of the EDI 130 Student Educational Record (Transcript). School, school district or postsecondary institution sends it to another educational institution or authorized recipient. It usually follows 146. It is usually followed by 131 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), ERP (Educational Record Purpose), REF (Reference Information), the required N1 loop with N1 (Party Identification) and the required IN1 loop with IN1 (Individual Identification) and IN2 (Individual Name Structure Components). 6 optional loops are listed by their first segment.How the EDI 130 worksStudent Educational Record (Transcript): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS146Request for StudentEducational Record(Transcript)EDI 130SENDERSchool, school districtor postsecondaryinstitutionRECEIVERAnother educationalinstitution orauthorized recipient997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY131Student EducationalRecord (Transcript)Acknowledgment997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code EDGS … GETransaction set 130ST … SEHEADINGBGNBeginning SegmentERPEducational Record PurposeREFReference InformationRequired loop N1 · repeats up to 2N1Party IdentificationRequired loop IN1 · repeats up to 15IN1Individual IdentificationIN2Individual Name Structure Components+ 5 optional loops, starting with:N3SSTATVTSTSUMDETAIL+ 1 optional loop, starting with:LXBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 130. Your trading partner's implementation guide adds its own requirements.
How the EDI 130 worksDiagram of the EDI 130 Student Educational Record (Transcript). School, school district or postsecondary institution sends it to another educational institution or authorized recipient. It usually follows 146. It is usually followed by 131 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), ERP (Educational Record Purpose), REF (Reference Information), the required N1 loop with N1 (Party Identification) and the required IN1 loop with IN1 (Individual Identification) and IN2 (Individual Name Structure Components). 6 optional loops are listed by their first segment.How the EDI 130 worksStudent Educational Record (Transcript): whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS146Request for Student Educational Record(Transcript)EDI 130SENDERSchool, schooldistrict orpostsecondaryinstitutionRECEIVERAnothereducationalinstitution orauthorizedrecipient997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY131Student Educational Record(Transcript) Acknowledgment997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code ED (GS … GE)Transaction set 130 (ST … SE)HEADINGBGNBeginning SegmentERPEducational Record PurposeREFReference InformationRequired loop N1 · repeats up to 2N1Party Identification+ required IN1 (IN1) and 5 optionalloops, starting with:N3SSTATVTSTSUMDETAIL+ 1 optional loop, starting with:LXBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 130. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 130, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 130 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Sending transcripts to colleges for admission
  • Sending transcripts between colleges for transfer students
  • Supplying records when students change schools

Where it fits in the document flow

Usually follows 146 Request for Student Educational Record (Transcript)
This document 130 Student Educational Record (Transcript)
Usually followed by 131 Student Educational Record (Transcript) Acknowledgment997 Functional Acknowledgment

Structure

Mandatory segments in the 130 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • ERP
  • REF
  • N1
  • IN1
  • IN2
  • N3
  • SST
  • ATV
  • TST
  • SBT
  • SUM
  • LX
  • HC
  • SP
  • OPS
  • SES
  • CRS
  • MKS
  • DEG
  • SE

Practical example

The 130 in practice

A high school senior applies to three universities. When each university requests the transcript, the school's student information system sends a 130 with the student's courses, grades, credits and graduation status. Each university loads the transcript into its admissions system and acknowledges it with a 131.

Implementation

Implementation considerations for the 130

  • Comply with student privacy laws and obtain any required consent.
  • Check whether partners now use XML transcript standards instead.
  • Verify that transcripts come from authorized institutions.
  • Map course and grade codes between institutions carefully.

How ECOM helps

Automate the 130 with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related education documents

All 10 education documents

Need help with the EDI 130?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us