We Make EDI Integration Easy

Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

>>  Request a Demo
>>  Map Your Ideal Integration

What is a 135 - Student Aid Origination Record document?

The 135 EDI document type contains information regarding the Student Aid Origination Record Transaction Set (135) for use within the context of an Electronic Data Interchange (EDI) environment. Standard EDI formats include X12, ANSI, EDIFACT and its subsets.

What makes up the 135 - Student Aid Origination Record document?

An EDI 135 - Student Aid Origination Record document is organized into segment and data elements. Examples of data elements on the 135 Student Aid Origination Record includes student and applicant identification, school enrollment data, borrowing history, the terms of the loan and other related data. There are an infinite number of possibilities available for a company to include data on an 135 - Student Aid Origination Record.

How is a 135 - Student Aid Origination Record used?

The 135 Student Aid Origination Record is used by lending institutions ("lenders"), colleges, universities and trade schools ("schools"), and loan guarantee agencies ("guarantors") to exchange information relating to the certification, approval, and guarantee of specific student loan applications. Additionally, the student loan application process typically begins with an applicant submitting a student loan application to the financial aid officer at the student's school. This transaction set supports multi-program transactions to exchange information about a student loan, or grant between schools and fund source. A Fund source could be a guarantor and lender combination, private lender, and scholarship agency.

How is a 135 - Student Aid Origination Record processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.