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 833 Mortgage Credit Report Order

The X12 document a mortgage originator uses to request, track and cancel the credit reports required in mortgage lending.

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

What is an EDI 833?

The EDI 833 Mortgage Credit Report Order is the ANSI X12 transaction set a mortgage originator uses to request, track and cancel the investigative credit reports typically required in mortgage lending. It carries borrower information and the type of report requested.

Mortgage credit reports often combine data from several credit bureaus with verification. The lender orders them electronically, and the agency returns the report, for example as a 200 mortgage credit report. The mortgage industry has largely moved to its own XML standards, so the 833 is found in older integrations.

How the EDI 833 worksDiagram of the EDI 833 Mortgage Credit Report Order. Mortgage originator or lender sends it to credit reporting agency. It usually starts the exchange. It is usually followed by 200 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required CRO loop with CRO (Credit Report Order Details) and 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) and NX2 (Location ID Component). 6 optional loops are listed by their first segment.How the EDI 833 worksMortgage Credit Report Order: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 833SENDERMortgage originator orlenderRECEIVERCredit reportingagency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY200Mortgage Credit Report997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MEGS … GETransaction set 833ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 100N1Party Identification+ 1 optional loop, starting with:N4DETAILRequired loop CRO · repeats up to 200CROCredit Report Order DetailsRequired loop LX · repeats up to 2LXTransaction Set Line NumberRequired loop IN1 · repeats up to 30IN1Individual IdentificationRequired loop NX1 · repeats up to 10NX1Property or Entity IdentificationNX2Location ID Component+ 5 optional loops, starting with:N1NX1AMTREABlue 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 833. Your trading partner's implementation guide adds its own requirements.
How the EDI 833 worksDiagram of the EDI 833 Mortgage Credit Report Order. Mortgage originator or lender sends it to credit reporting agency. It usually starts the exchange. It is usually followed by 200 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required CRO loop with CRO (Credit Report Order Details) and 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) and NX2 (Location ID Component). 6 optional loops are listed by their first segment.How the EDI 833 worksMortgage Credit Report Order: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 833SENDERMortgageoriginator orlenderRECEIVERCredit reportingagency997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY200Mortgage Credit Report997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code ME (GS … GE)Transaction set 833 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats up to100N1Party Identification+ 1 optional loop, starting with:N4DETAILRequired loop CRO · repeats up to200CROCredit Report Order DetailsRequired loop LX · repeats upto 2LXTransaction Set LineNumberRequired loop IN1 ·repeats up to 30IN1IndividualIdentificationRequired loop NX1 ·repeats up to 10NX1Property or EntityIdentificationNX2Location IDComponent+ 5 optional loops, starting with:N1NX1AMTREABlue 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 833. Your trading partner'simplementation guide adds its own requirements.

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

  • Ordering credit reports for mortgage applicants
  • Tracking the status of report orders
  • Cancelling report orders

Where it fits in the document flow

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

Structure

Mandatory segments in the 833 (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
  • N4
  • CRO
  • NX1
  • LX
  • AMT
  • REA
  • IN1
  • NX2
  • EMP
  • EMS
  • FAA
  • CDA
  • SE

Practical example

The 833 in practice

A lender receives a mortgage application from two co-borrowers. Its loan origination system sends the credit agency an 833 with both borrowers' identifying details and the report type. The agency returns the merged credit report, which the underwriter reviews.

Implementation

Implementation considerations for the 833

  • Protect borrowers' personal data under applicable laws.
  • Obtain borrower authorization before ordering reports.
  • Check whether partners now require mortgage industry XML formats.
  • Track orders until reports are received.

How ECOM helps

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

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

Request a Demo Contact us