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 191 Student Loan Pre-Claims and Claims

The X12 document lenders, servicers and secondary markets use with guarantors for pre-claims assistance and claims on student loans.

Sent by
Lender, secondary market or loan servicer
Received by
Guarantee agency
Standard
ANSI ASC X12

What is an EDI 191?

The EDI 191 Student Loan Pre-Claims and Claims is the ANSI X12 transaction set lending institutions, secondary markets or student loan servicers use to exchange information with guarantee agencies about pre-claims assistance on delinquent student loans and about claims on loans that are in default.

When a borrower falls behind, the guarantor can help the lender bring the loan current before default. If default occurs, the lender files a claim with the guarantor for payment. Exchanging this data electronically speeds up both processes.

How the EDI 191 worksDiagram of the EDI 191 Student Loan Pre-Claims and Claims. Lender, secondary market or loan servicer sends it to guarantee agency. 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) and the required ENT loop with ENT (Entity) and the required REF loop with REF (Reference Information). 2 optional loops are listed by their first segment.How the EDI 191 worksStudent Loan Pre-Claims and Claims: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 191SENDERLender, secondarymarket or loanservicerRECEIVERGuarantee agency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SDGS … GETransaction set 191ST … SEHEADINGBGNBeginning SegmentRequired loop ENT · repeats up to 10ENTEntityRequired loop REF · repeats up to 100REFReference Information+ 2 optional loops, starting with:IN1Blue 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 191. Your trading partner's implementation guide adds its own requirements.
How the EDI 191 worksDiagram of the EDI 191 Student Loan Pre-Claims and Claims. Lender, secondary market or loan servicer sends it to guarantee agency. 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) and the required ENT loop with ENT (Entity) and the required REF loop with REF (Reference Information). 2 optional loops are listed by their first segment.How the EDI 191 worksStudent Loan Pre-Claims and Claims: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 191SENDERLender,secondarymarket or loanservicerRECEIVERGuaranteeagency997 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 SD (GS … GE)Transaction set 191 (ST … SE)HEADINGBGNBeginning SegmentRequired loop ENT · repeats up to10ENTEntityRequired loop REF · repeatsup to 100REFReference Information+ 2 optional loops, starting with:IN1Blue 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 191. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting pre-claims assistance on delinquent loans
  • Filing default claims with guarantors
  • Reporting claim status and payment

Where it fits in the document flow

This document 191 Student Loan Pre-Claims and Claims
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 191 (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
  • ENT
  • IN1
  • REF
  • SE

Practical example

The 191 in practice

A borrower is 60 days delinquent. The loan servicer sends the guarantor a 191 requesting pre-claims assistance with the loan and borrower details. The guarantor contacts the borrower, who arranges a repayment plan, and the loan returns to good standing without a claim.

Implementation

Implementation considerations for the 191

  • Follow program rules on timing of pre-claims and claims.
  • Protect borrowers' personal data under applicable law.
  • Include the loan history guarantors need to pay claims.
  • Track each pre-claim or claim through to its outcome.

How ECOM helps

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

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

Request a Demo Contact us