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 200 Mortgage Credit Report

The X12 document that carries the data of a mortgage credit report, in response to a mortgage credit report order.

Sent by
Credit reporting agency
Received by
Mortgage lender
Standard
ANSI ASC X12

What is an EDI 200?

The EDI 200 Mortgage Credit Report is the ANSI X12 transaction set used to transmit the data that makes up a mortgage credit report. It is the electronic response to the Mortgage Credit Report Order (833).

A mortgage credit report typically merges information from several credit bureaus, with the borrower's accounts, payment history, public records and inquiries, and sometimes credit scores. Delivering it as data lets underwriting systems analyze it automatically. The industry largely uses MISMO XML for credit reports today.

How the EDI 200 worksDiagram of the EDI 200 Mortgage Credit Report. Credit reporting agency sends it to mortgage lender. It usually follows 833. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), CRO (Credit Report Order Details) and the required N1 loop with N1 (Party Identification) and detail: the required LX loop with LX (Transaction Set Line Number), the required IN1 loop with IN1 (Individual Identification) and the required NX1 loop with NX1 (Property or Entity Identification). 8 optional loops are listed by their first segment.How the EDI 200 worksMortgage Credit Report: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS833Mortgage Credit ReportOrderEDI 200SENDERCredit reportingagencyRECEIVERMortgage lender997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MEGS … GETransaction set 200ST … SEHEADINGBGNBeginning SegmentCROCredit Report Order DetailsRequired loop N1 · repeats up to 20N1Party IdentificationDETAILRequired loop LX · repeats up to 2LXTransaction Set Line NumberRequired loop IN1 · repeats up to 15IN1Individual IdentificationRequired loop NX1 · repeats up to 10NX1Property or Entity Identification+ 8 optional loops, starting with:N1TLNROCCIINQVARNTEREFBlue 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 200. Your trading partner's implementation guide adds its own requirements.
How the EDI 200 worksDiagram of the EDI 200 Mortgage Credit Report. Credit reporting agency sends it to mortgage lender. It usually follows 833. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), CRO (Credit Report Order Details) and the required N1 loop with N1 (Party Identification) and detail: the required LX loop with LX (Transaction Set Line Number), the required IN1 loop with IN1 (Individual Identification) and the required NX1 loop with NX1 (Property or Entity Identification). 8 optional loops are listed by their first segment.How the EDI 200 worksMortgage Credit Report: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS833Mortgage Credit Report OrderEDI 200SENDERCredit reportingagencyRECEIVERMortgage lender997 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 ME (GS … GE)Transaction set 200 (ST … SE)HEADINGBGNBeginning SegmentCROCredit Report Order DetailsRequired loop N1 · repeats up to20N1Party IdentificationDETAILRequired loop LX · repeats up to2LXTransaction Set LineNumberRequired loop IN1 · repeatsup to 15IN1IndividualIdentificationRequired loop NX1 · repeatsup to 10NX1Property or EntityIdentification+ 8 optional loops, starting with:N1TLNROCCIINQVARNTEREFBlue 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 200. Your trading partner'simplementation guide adds its own requirements.

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

  • Delivering merged credit reports to lenders
  • Updating reports after reissues
  • Supporting automated underwriting

Where it fits in the document flow

Usually follows 833 Mortgage Credit Report Order
This document 200 Mortgage Credit Report
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 200 (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
  • CRO
  • N1
  • LX
  • IN1
  • NX1
  • SOI
  • AIN
  • TLN
  • AMT
  • RO
  • CCI
  • INQ
  • VAR
  • SCM
  • NTE
  • REF
  • G32
  • SE

Practical example

The 200 in practice

A lender orders a credit report for two co-borrowers with an 833. The credit agency merges data from the bureaus and returns a 200 with each borrower's accounts, balances, payment history and scores. The lender's underwriting system calculates debt-to-income ratios from the data.

Implementation

Implementation considerations for the 200

  • Comply with consumer credit reporting laws.
  • Protect borrowers' personal data under applicable law.
  • Check whether partners use MISMO XML instead of X12.
  • Match each report to its original order.

How ECOM helps

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

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

Request a Demo Contact us