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 · Finance

EDI 135 Student Aid Origination Record

The X12 document lenders, schools and loan guarantors use to exchange information on the certification, approval and origination of student loans.

Sent by
School, lender or guarantor
Received by
Lender, guarantor or school
Standard
ANSI ASC X12

What is an EDI 135?

The EDI 135 Student Aid Origination Record is the ANSI X12 transaction set lenders, colleges, universities and trade schools, and loan guarantee agencies use to exchange information about the certification, approval and origination of student loans.

A student loan involves the school, which certifies enrollment and cost of attendance, the lender and the guarantor. Exchanging origination data electronically lets all three process loans before the term starts. Student loan programs have changed over the years, so current usage depends on the program and the parties.

How the EDI 135 worksDiagram of the EDI 135 Student Aid Origination Record. School, lender or guarantor sends it to lender, guarantor or school. It usually starts the exchange. It is usually followed by 139 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required ENT loop with ENT (Entity). 5 optional loops are listed by their first segment.How the EDI 135 worksStudent Aid Origination Record: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 135SENDERSchool, lender orguarantorRECEIVERLender, guarantor orschool997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY139Student Loan GuaranteeResult997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SLGS … GETransaction set 135ST … SEHEADINGBGNBeginning SegmentRequired loop ENT · repeats up to 6ENTEntity+ 5 optional loops, starting with:LXN1PLIIN1LMBlue 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 135. Your trading partner's implementation guide adds its own requirements.
How the EDI 135 worksDiagram of the EDI 135 Student Aid Origination Record. School, lender or guarantor sends it to lender, guarantor or school. It usually starts the exchange. It is usually followed by 139 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required ENT loop with ENT (Entity). 5 optional loops are listed by their first segment.How the EDI 135 worksStudent Aid Origination Record: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 135SENDERSchool, lenderor guarantorRECEIVERLender,guarantor orschool997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY139Student Loan Guarantee Result997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SL (GS … GE)Transaction set 135 (ST … SE)HEADINGBGNBeginning SegmentRequired loop ENT · repeats up to6ENTEntity+ 5 optional loops, starting with:LXN1PLIIN1LMBlue 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 135. Your trading partner'simplementation guide adds its own requirements.

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

  • Certifying student loan applications
  • Requesting guarantee approval
  • Reporting loan origination details

Where it fits in the document flow

This document 135 Student Aid Origination Record
Usually followed by 139 Student Loan Guarantee Result997 Functional Acknowledgment

Structure

Mandatory segments in the 135 (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
  • LX
  • ENT
  • N1
  • PLI
  • IN1
  • LM
  • SE

Practical example

The 135 in practice

A student applies for a loan to attend a trade school. The school sends the lender a 135 certifying the student's enrollment, cost of attendance and loan period. The lender forwards the loan for guarantee, and the guarantor returns the result with a 139.

Implementation

Implementation considerations for the 135

  • Protect students' personal and financial data.
  • Follow the rules of the loan program concerned.
  • Certify enrollment and costs accurately.
  • Track each loan through guarantee and disbursement.

How ECOM helps

Automate the 135 with ECOM

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

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.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 135?

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

Request a Demo Contact us