X12 transaction guide · Finance
EDI 264 Mortgage Loan Default Status
The X12 document used to file notifications of mortgage loan default and foreclosure status with insurers, guarantors, investors or servicers.
- Sent by
- Mortgage servicer
- Received by
- Insurer, guarantor, investor or another servicer
- Standard
- ANSI ASC X12
What is an EDI 264?
The EDI 264 Mortgage Loan Default Status is the ANSI X12 transaction set that lets all notifications of mortgage loan default and foreclosure status be filed in the same way, whether to an insurer, guarantor, investor or servicer.
Insurers and investors must be told when loans become delinquent and as foreclosure progresses, under deadlines in their agreements. A single status format lets servicers report consistently to all of them and supports later claims (260). It standardizes reporting across recipients. Updates follow each milestone.
How to read this diagram: the top row shows who sends the 264, 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 264 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.
When it is used
- Reporting new loan defaults
- Reporting foreclosure milestones
- Reporting cures and loss mitigation outcomes
Where it fits in the document flow
Structure
Mandatory segments in the 264 (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
- N1
- LX
- DTP
- REF
- REC
- SE
Practical example
The 264 in practice
A servicer's monthly default report includes loans that became 60 days delinquent and loans that reached foreclosure milestones. It sends each mortgage insurer and investor 264 transactions with the loan, delinquency date, status and next action. The insurers update their exposure and later receive claims for loans that end in foreclosure.
Implementation
Implementation considerations for the 264
- Meet the reporting deadlines in each agreement.
- Use status codes that recipients recognize.
- Report cures and workouts as well as defaults.
- Keep status consistent with later claims.
How ECOM helps
Automate the 264 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
- 206Real Estate Inspection
- 202Secondary Mortgage Market Loan Delivery
- 139Student Loan Guarantee Result
- 144Student Loan Transfer and Status Verification
- 191Student Loan Pre-Claims and Claims
- 198Loan Verification Information
- 200Mortgage Credit Report
- 201Residential Loan Application
- 203Secondary Mortgage Market Investor Report
- 205Mortgage Note
- 266Mortgage or Property Record Change Notification
- 833Mortgage Credit Report Order
Need help with the EDI 264?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.