Cloud-based Accounting Integration
The #1 Integration Platform | 1 800 755 6921
Find us on:

EDI - Connecting your Accounting to a World of Trading Partners
Next Steps
Contact me
Request more information

Request Information
Name:*
Company:
Phone:*
Email:*
Accounting package:
Questions or comments:
Please include me in the eBridge mailing list.

EDI Document Type -135 Student Aid Origination Record

What is a 135 Student Aid Origination Record?

The 135 Student Aid Origination Record 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. Click here to read more about supported EDI Standards.


What makes up the 135 Student Aid Origination Record?

A 135 Student Aid Origination Record document is organized into the following segment and data elements. A segment can contain at least one data element. Each data element contains a data field. 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.

How is it 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.

The Process and Standards

An EDI solution is required to process the EDI documents received into a financial system (click here to view all available financial systems eBridge integrates into) 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. 

Click here to find your trading partner

Why eBridge Connections?

Integration with Sage MAS 90, MAS 200, MAS 500, PFW, Business Vision, Sage Pro and more
EDI integration with Microsoft Dynamics Navision, Microsoft Dynamics Axapta and more
 
Integration with Epicor Enterprise, Vantage and iScala
 

Click here for information on benefits, pre-configured trading partner connections, EDI document types and more