X12 transaction guide · Education

EDI 190 Student Enrollment Verification

The X12 document used to request and receive the information needed to verify a student's enrollment status.

Sent by
Guarantor, lender, school or secondary market
Received by
School or loan program party
Standard
ANSI ASC X12

What is an EDI 190?

The EDI 190 Student Enrollment Verification is the ANSI X12 transaction set guarantee agencies, lenders, schools, secondary markets and others use to request and receive the information needed to verify a student's enrollment status.

Student loan terms depend on enrollment: repayment usually begins after a student leaves school or drops below half-time. Lenders and guarantors therefore need regular enrollment updates from schools to manage deferments and repayment start dates. Schools usually report enrollment changes on a regular schedule, and also on request, so that lenders and guarantors can manage deferments and set repayment start dates correctly.

How the EDI 190 worksDiagram of the EDI 190 Student Enrollment Verification. Guarantor, lender, school or secondary market sends it to school or loan program party. 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). 5 optional loops are listed by their first segment.How the EDI 190 worksStudent Enrollment Verification: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 190SENDERGuarantor, lender,school or secondarymarketRECEIVERSchool or loan programparty997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SVGS … GETransaction set 190ST … SEHEADINGBGNBeginning Segment+ 5 optional loops, starting with:AMTN1ENTSESDEGBlue 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 190. Your trading partner's implementation guide adds its own requirements.
How the EDI 190 worksDiagram of the EDI 190 Student Enrollment Verification. Guarantor, lender, school or secondary market sends it to school or loan program party. 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). 5 optional loops are listed by their first segment.How the EDI 190 worksStudent Enrollment Verification: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 190SENDERGuarantor,lender, school orsecondarymarketRECEIVERSchool or loanprogram party997 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 SV (GS … GE)Transaction set 190 (ST … SE)HEADINGBGNBeginning Segment+ 5 optional loops, starting with:AMTN1ENTSESDEGBlue 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 190. Your trading partner'simplementation guide adds its own requirements.

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

  • Verifying that borrowers are still enrolled
  • Reporting changes in enrollment status
  • Supporting deferment and repayment decisions

Where it fits in the document flow

This document 190 Student Enrollment Verification
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 190 (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
  • AMT
  • N1
  • ENT
  • SES
  • DEG
  • SE

Practical example

The 190 in practice

A guarantor sends a university a 190 listing borrowers whose enrollment it needs to confirm. The university responds with each student's current status, such as full-time, half-time, graduated or withdrawn, and the effective dates. The guarantor updates loan records so repayment starts at the right time.

Implementation

Implementation considerations for the 190

  • Protect students' personal data under privacy laws.
  • Report status changes with effective dates.
  • Respond within the program's reporting timelines.
  • Match students using reliable identifiers.

Need help with the EDI 190?

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