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 144 Student Loan Transfer and Status Verification

The X12 document lenders, guarantors and secondary markets use to exchange information on transfers of student loan ownership and loan status.

Sent by
Lender, guarantor or secondary market
Received by
Lender, guarantor or secondary market
Standard
ANSI ASC X12

What is an EDI 144?

The EDI 144 Student Loan Transfer and Status Verification is the ANSI X12 transaction set lending institutions, guarantee agencies and secondary markets use to send and receive information about the transfer of ownership of a student loan. It can also be used to verify the status of loans.

Student loans are often sold by the originating lender to secondary market investors. The transfer must be recorded with the guarantor and the new holder must know each loan's status and balance, so that servicing and any claims continue correctly.

How the EDI 144 worksDiagram of the EDI 144 Student Loan Transfer and Status Verification. Lender, guarantor or secondary market sends it to lender, guarantor or secondary market. 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), GR (Guarantee Result Detail) and the required ENT loop with ENT (Entity). 0 optional loops are listed by their first segment.How the EDI 144 worksStudent Loan Transfer and Status Verification: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 144SENDERLender, guarantor orsecondary marketRECEIVERLender, guarantor orsecondary market997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code LTGS … GETransaction set 144ST … SEHEADINGBGNBeginning SegmentGRGuarantee Result DetailRequired loop ENT · repeats up to 10ENTEntityBlue 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 144. Your trading partner's implementation guide adds its own requirements.
How the EDI 144 worksDiagram of the EDI 144 Student Loan Transfer and Status Verification. Lender, guarantor or secondary market sends it to lender, guarantor or secondary market. 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), GR (Guarantee Result Detail) and the required ENT loop with ENT (Entity). 0 optional loops are listed by their first segment.How the EDI 144 worksStudent Loan Transfer and Status Verification:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 144SENDERLender,guarantor orsecondarymarketRECEIVERLender,guarantor orsecondarymarket997 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 LT (GS … GE)Transaction set 144 (ST … SE)HEADINGBGNBeginning SegmentGRGuarantee Result DetailRequired loop ENT · repeats up to10ENTEntityBlue 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 144. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting sales of student loans
  • Notifying guarantors of new loan holders
  • Verifying loan status before transfer

Where it fits in the document flow

This document 144 Student Loan Transfer and Status Verification
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 144 (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
  • GR
  • ENT
  • SE

Practical example

The 144 in practice

A lender sells a portfolio of 5,000 student loans to a secondary market investor. It sends the guarantor and the buyer 144 transactions identifying each loan, its balance and status, and the transfer date. The guarantor updates the loan holder of record.

Implementation

Implementation considerations for the 144

  • Reconcile loan balances at the transfer date.
  • Notify all parties that must record the new holder.
  • Protect borrowers' personal data under applicable law.
  • Verify loan status before completing transfers.

How ECOM helps

Automate the 144 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 144?

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

Request a Demo Contact us