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 133 Educational Institution Record

The X12 document that conveys descriptive characteristics of postsecondary and elementary or secondary educational institutions.

Sent by
Educational institution or education agency
Received by
Agencies, institutions or service providers
Standard
ANSI ASC X12

What is an EDI 133?

The EDI 133 Educational Institution Record is the ANSI X12 transaction set that conveys descriptive characteristics of postsecondary and elementary or secondary educational institutions. Its data includes information about the institution's location, type, student population and programs.

Institution data is used by admissions offices, financial aid systems, accreditation and statistics agencies to identify institutions and understand what they offer. A standard record keeps directories consistent across these systems. Institutions should send updates whenever campuses, programs or other key characteristics change, so that directories used by other institutions stay accurate.

How the EDI 133 worksDiagram of the EDI 133 Educational Institution Record. Educational institution or education agency sends it to agencies, institutions or service providers. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), ERP (Educational Record Purpose) and the required N1 loop with N1 (Party Identification) and detail: the required HL loop with HL (Hierarchical Level) and the required N1 loop with N1 (Party Identification). 6 optional loops are listed by their first segment.How the EDI 133 worksEducational Institution Record: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 133SENDEREducational institutionor education agencyRECEIVERAgencies, institutionsor service providers997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CWGS … GETransaction set 133ST … SEHEADINGBGNBeginning SegmentERPEducational Record PurposeRequired loop N1 · repeats many timesN1Party IdentificationDETAILRequired loop HL · repeats many timesHLHierarchical LevelRequired loop N1 · repeats many timesN1Party Identification+ 6 optional loops, starting with:YNQFOSSPSLAENMATVBlue 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 133. Your trading partner's implementation guide adds its own requirements.
How the EDI 133 worksDiagram of the EDI 133 Educational Institution Record. Educational institution or education agency sends it to agencies, institutions or service providers. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), ERP (Educational Record Purpose) and the required N1 loop with N1 (Party Identification) and detail: the required HL loop with HL (Hierarchical Level) and the required N1 loop with N1 (Party Identification). 6 optional loops are listed by their first segment.How the EDI 133 worksEducational Institution Record: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 133SENDEREducationalinstitution oreducationagencyRECEIVERAgencies,institutions orserviceproviders997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CW (GS … GE)Transaction set 133 (ST … SE)HEADINGBGNBeginning SegmentERPEducational Record PurposeRequired loop N1 · repeats manytimesN1Party IdentificationDETAILRequired loop HL · repeats manytimesHLHierarchical LevelRequired loop N1 · repeatsmany timesN1Party Identification+ 6 optional loops, starting with:YNQFOSSPSLAENMATVBlue 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 133. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 133, 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 133 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

  • Publishing institution profile data
  • Updating directory information after changes
  • Supporting statistics and accreditation reporting

Where it fits in the document flow

This document 133 Educational Institution Record
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 133 (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
  • N1
  • HL
  • YNQ
  • FOS
  • SP
  • SLA
  • ENM
  • ATV
  • SE

Practical example

The 133 in practice

A university opens a new campus and adds degree programs. It sends the state higher education agency a 133 with the campus location, institution type, programs offered and enrollment figures. The agency updates its directory, which other institutions use when evaluating applicants' records.

Implementation

Implementation considerations for the 133

  • Use standard identifiers for each institution.
  • Update records when campuses or programs change.
  • Align enrollment figures with official reporting.
  • Follow the recipient's data definitions.

How ECOM helps

Automate the 133 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 133?

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

Request a Demo Contact us