X12 transaction guide · Healthcare and insurance
EDI 872 Residential Mortgage Insurance Application
The X12 document a mortgage originator uses to request mortgage insurance and supply the information needed for a commitment.
- Sent by
- Mortgage originator or lender
- Received by
- Mortgage insurer
- Standard
- ANSI ASC X12
What is an EDI 872?
The EDI 872 Residential Mortgage Insurance Application is the ANSI X12 transaction set a mortgage originator uses to request mortgage insurance and to provide the supporting information needed to obtain a mortgage insurance commitment on one or several residential mortgages.
The application carries the borrower's credit profile, income, the property, the loan terms and the coverage requested. The insurer underwrites the loan and replies with the 263. Electronic applications let lenders obtain coverage decisions quickly within their origination workflow. Applications may cover several loans.
How to read this diagram: the top row shows who sends the 872, 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 872 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
- Applying for mortgage insurance on a loan
- Applying for coverage on several loans at once
- Resubmitting applications with updated data
Where it fits in the document flow
Structure
Mandatory segments in the 872 (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
- NM1
- LRQ
- LN1
- CDI
- LX
- SCM
- NX1
- NX2
- PAS
- REF
- IN1
- IN2
- REA
- MCD
- PRJ
- SE
Practical example
The 872 in practice
A lender originates a loan with a 5 percent down payment. Its origination system sends the mortgage insurer an 872 with the borrower's credit and income data, the property value, the loan amount and the coverage percentage required. The insurer approves the application and returns a 263.
Implementation
Implementation considerations for the 872
- Send complete data to avoid suspended applications.
- Protect borrowers' personal and financial data.
- Keep application data consistent with the loan file.
- Track applications through to commitment.
How ECOM helps
Automate the 872 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 healthcare and insurance documents
- 263Residential Mortgage Insurance Application Response
- 259Residential Mortgage Insurance Explanation of Benefits
- 260Application for Mortgage Insurance Benefits
- 273Insurance/Annuity Application Status
- 100Insurance Plan Description
- 111Individual Insurance Policy and Client Information
- 186Insurance Underwriting Requirements Reporting
- 252Insurance Producer Administration
- 267Individual Life, Annuity and Disability Application
- 112Property Damage Report
- 124Vehicle Damage
- 148Report of Injury, Illness or Incident
Need help with the EDI 872?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.