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 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.
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
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.
How ECOM helps
Automate the 190 with ECOM
Industry
Financial Services
Secure file transfer and B2B integration for banks and financial institutions.
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.
More general questions about EDI are answered in the EDI FAQ.
Need help with the EDI 190?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.