XML Implementation Guide:
Credit Reporting – Version 2
Document Date
Change List
Jan 13 2002 o Original Version (Draft).Jan 28 2002 o Minor corrections to text.
o Update with Version 2 Release Candidate 2 changes from Jan 16, 2002 Credit Work Group meeting in Nashville, TN.
o Added Error Codes & Descriptions – Chapter 4. o Added Chapter 5 – Credit Status Response. Feb 14 2002 o Minor corrections to text.
o Updated RMCR Request Example on page 2-14.
Dec 26 2002 o Add section to Chapter 2 that lists the additional elements added to the AUS Loan Application structure for the use in the Credit Request.
o Add section to Chapter 2 to describe request for update of Credit Inquiry data. o Add sections to Chapter 2 for new inquiry elements added in Version 2.1.1. o Update the Chapter 3 Credit Response with text regarding Borrower and Credit
Request elements specifying that IDs from the request should be returned in the response.
o Update Chapter 6 – DTD Change List – to include information about Version 2.1.1 changes.
o Add Chapter 8 – MISMO Credit Work Group Recommendation for the California Credit Report Freeze Law.
Feb 11 2003 o Clarified text in the “Required?” block of the Credit Request sections for Credit Inquiry Element, Credit Liability Element and Credit Public Record Element.
Aug 28 2003 o Update Chapters 2, 3 and 6 with Version 2.3 changes.
o Update Chapter 3 section – “Manner of Payment (MOP) Codes” to correct CreditRatingCodeType value in second sample credit report.
Oct 02 2003 o Update Chapter 7 question – “What are the minimum elements required for a “Merge” credit report?” to show that the BorrowerID attribute should be included.
o Update Chapter 8 to include information about the Texas Credit Freeze Law and latest recommendations of the MISMO Credit Work Group.
o Miscellaneous changes throughout document to clarify text.
Oct 16 2003 o Update Chapter 1 to add section “Repositories and Credit Bureaus – Defined”. o Update Chapter 4 Suggested Error Codes to include E061 and E062.
Jan 17 2005 o Update Chapter 3 to correct CREDIT SUMMARY example to show proper element name.
o Update Chapter 3 section on Manner of Payment Codes to clarify text and table. o Update Chapter 6 with Version 2.3.1 changes.
Mar 29 2007 o Update Chapter 1 to add a “MISMO MXCompliance Program” section. Rename the “Overview” section to “Files Included with the Data Standards Download”. Updated list of example Credit Bureau names in the “Repositories and Credit Bureaus – Defined” section.
o Update Chapter 2 “Update Request” section’s sample XML to show the “Instruction” Comment Type attribute.
o Update Chapter 2 “Credit Request Data” section to add notes about requesting credit scores using score model names and score category types.
o Update Chapter 3 “Prior Adverse Rating and Payment Pattern Data” section to correct Months Delinquent range as 1-6 to match LDD.
o Update Chapter 3 “Manner of Payment Codes” section to add notes about how Experian classifies bankruptcies under codes 7 and 9.
o Update Chapter 3 to add an “Including Code Values with Credit Comments” section. o Update Chapter 3 Credit Score Element section to add “Valid Credit Score Values”,
“Standard Credit Score Record”, “Expanded Credit Score Record”, and “Credit Score Record with an Exclusion Reason” sub-sections.
o Update Chapter 3 “Embedded File” section to show additional Version 2.4 attributes. o Update Chapter 6 with Version 2.4 changes.
o Update Chapter 7 to add FAQ regarding difference between Loan App Liability Type and Credit Loan Type.
Document Date
Change List
Nov 19 2007 o Update Chapter 2 Credit Request Data section to update “Reissue Request” info and add “Force New Request” and “Secondary Use Notification Request” info.
o Update Chapter 2 to add “Embedded File Element” section.
o Update Chapter 3 Credit Bureau Element section to add “FNM Credit Bureau Identifier” attribute info.
o Update Chapter 3 to add “Alert Message Element” section.
o Update Chapter 4 Error Code table to add “E038 – Invalid Login or Password”. o Update Chapter 6 with Version 2.4.1.1 changes.
o Update Chapter 9 with multiple changes, including addition of “Using a KEY element for Specifying a Billing Instruction” section.
XML Implementation Guide: Credit Reporting – Version 2
Table of Contents
XML Implementation Guide:
Credit Reporting – Version 2
Document Revision Date: August 22, 2010
Copyright 2007 - Mortgage Industry Standards Maintenance Organization (MISMO). All rights reserved
Permission to use, copy, modify, and distribute the MISMO DTD and its accompanying documentation for any purpose and without fee is hereby granted in perpetuity, provided that the above copyright notice and this paragraph appear in all copies. The copyright holders make no representation about the suitability of the DTD or documentation for any purpose.
TABLE OF CONTENTS
CHAPTER 1: INTRODUCTION... 1-1
P
URPOSE OF THISD
OCUMENT... 1-1
MISMO
MXC
OMPLIANCEP
ROGRAM... 1-1
T
RANSITIONING FROME
ARLIERS
TANDARDSV
ERSIONS... 1-2
W
HATE
LSEY
OUW
ILLN
EED... 1-2
F
ILESI
NCLUDED WITH THED
ATAS
TANDARDSD
OWNLOAD... 1-2
T
HEMISMO
T
RANSACTIONE
NVELOPE... 1-3
R
EPOSITORIES ANDC
REDITB
UREAUS–
D
EFINED... 1-3
Repositories ... 1-3
Credit Bureau ... 1-3
CHAPTER 2: CREDIT REQUEST – SECTION BY SECTION ... 2-1
CREDIT
REQUEST
E
LEMENT... 2-2
CREDIT REQUEST Attributes ... 2-2
CREDIT REQUEST Element Usage ... 2-3
CREDIT
REQUEST
DATA
E
LEMENT... 2-4
Typical “Merge” Request Options ... 2-5
“Force New” Request Option ... 2-5
Selecting Number of Repositories to Be Requested ... 2-6
Reissue Request ... 2-6
Secondary Use Notification Request ... 2-6
Retrieve Request ... 2-7
Upgrade to RMCR Request ... 2-7
Update Request ... 2-8
Requesting Credit for Multiple Borrowers on a Loan ... 2-10
Requesting Credit Scores ... 2-11
Checking on the Status of a Request ... 2-12
DATA
INFORMATION
E
LEMENT... 2-13
SERVICE
PAYMENT
E
LEMENT... 2-14
CREDIT
INQUIRY
E
LEMENT... 2-15
CREDIT
LIABILITY
E
LEMENT... 2-16
CREDIT
PUBLIC
RECORD
E
LEMENT... 2-17
LOAN
APPLICATION ... 2-18
XML Implementation Guide: Credit Reporting – Version 2
Table of Contents
Loan Application Additions for the 2.x Credit Request ... 2-21
EMBEDDED
FILE
E
LEMENT... 2-23
CHAPTER 3: CREDIT RESPONSE – SECTION BY SECTION ... 3-1
CREDIT
RESPONSE
E
LEMENT... 3-2
CREDIT RESPONSE Attributes ... 3-3
CREDIT RESPONSE Element Usage ... 3-5
DATA
INFORMATION
E
LEMENT... 3-6
CREDIT
BUREAU
E
LEMENT... 3-7
CREDIT
REPORT
PRICE
E
LEMENT... 3-8
CREDIT
REPOSITORY
INCLUDED
E
LEMENT... 3-9
REQUESTING
PARTY
E
LEMENT... 3-10
CREDIT
REQUEST
DATA
E
LEMENT... 3-11
CREDIT
ERROR
MESSAGE
E
LEMENT... 3-12
BORROWER
E
LEMENT... 3-13
CREDIT
LIABILITY
E
LEMENT... 3-14
CREDIT LIABILITY and UNMERGED LIABILITY Data ... 3-15
Prior Adverse Rating and Payment Pattern Data ... 3-16
Manner Of Payment (MOP) Codes ... 3-17
Credit Liability Late Count and Periodic Late Count ... 3-20
Including Code Values with Credit Comments ... 3-20
CREDIT
PUBLIC
RECORD
E
LEMENT... 3-23
CREDIT
INQUIRY
E
LEMENT... 3-24
CREDIT
FILE
E
LEMENT... 3-25
CREDIT
SCORE
E
LEMENT... 3-27
Valid Credit Score Values ... 3-27
Standard Credit Score Record – Versions 2.1 - 2.3.1 ... 3-27
Expanded Credit Score Record – Version 2.4 & Later ... 3-28
Credit Score Record with an Exclusion Reason ... 3-30
CREDIT
TRADE
REFERENCE
E
LEMENT... 3-31
CREDIT
COMMENT
E
LEMENT... 3-32
CREDIT
CONSUMER
REFERRAL
E
LEMENT... 3-33
CREDIT
SUMMARY
E
LEMENT... 3-34
REGULATORY
PRODUCT
E
LEMENT... 3-35
EMBEDDED
FILE
E
LEMENT... 3-36
Before Version 2.4 ... 3-36
Version 2.4 and Later ... 3-37
ALERT
MESSAGE
E
LEMENT... 3-38
CHAPTER 4: CREDIT ERROR RESPONSE ... 4-1
CHAPTER 5: CREDIT STATUS RESPONSE ... 5-1
CHAPTER 6: CREDIT REPORTING DTD CHANGE LIST ... 6-1
V
ERSION2.1.1 ... 6-1
V
ERSION2.3 ... 6-4
V
ERSION2.3.1 ... 6-7
V
ERSION2.4 ... 6-10
V
ERSION2.4.1.1 ... 6-17
CHAPTER 7: QUESTIONS AND ANSWERS ... 7-1
W
HAT ARE THE MINIMUM ELEMENTS REQUIRED FOR A„M
ERGE‟
C
REDITR
EPORT? ... 7-1
W
HAT IS THEMISMO
XML
EQUIVALENT TO THEX12
R
ATINGR
EMARKS? ... 7-2
W
HICH CREDIT RESPONSE ELEMENTS INDICATE THAT A REQUEST TO A CREDIT REPOSITORY FAILED? ... 7-2
W
HERE IS THE“W
HOSEF
ILE”
FLAG FOR LIABILITIES,
PUBLIC RECORDS,
ETC.? ... 7-3
W
HY IS THE LIST OFL
OANA
PPL
IABILITYT
YPES DIFFERENT FROM THEL
OANT
YPES USED IN THEC
REDITXML Implementation Guide: Credit Reporting – Version 2
Table of Contents
CHAPTER 8: CREDIT REPORT FREEZE LAWS RECOMMENDATION ... 8-1
B
ACKGROUND... 8-1
California ... 8-1
Texas ... 8-2
MISMO Credit Work Group Recommendations ... 8-2
R
ECOMMENDATION–
MISMO
XML
F
ORMATS... 8-3
Key Names for California PIN values ... 8-3
Key Names for Other State’s PIN values ... 8-3
CHAPTER 9: REISSUE / SECONDARY USE REPORTING ... 9-1
B
ACKGROUND... 9-1
Repositories and Credit Bureaus – Defined ... 9-2
Reissue Reporting Overview ... 9-2
MISMO
S
UPPORT FORI
DENTIFYINGA
DDITIONALE
ND-U
SERS... 9-4
“Submit” Credit Request ... 9-4
“Reissue” Credit Request ... 9-4
“Secondary Use Notification” Credit Request ... 9-4
Credentials & Authentication ... 9-4
Backward Compatibility... 9-5
KEY Element Using Internal Account Identifier ... 9-5
KEY Element Using Login Account Identifier / Password ... 9-6
Using a KEY Element for Specifying a Billing Instruction ... 9-6
U
SINGMISMO
R
EQUESTS FORR
EISSUES ANDS
ECONDARYU
SEN
OTIFICATIONS... 9-9
Request a Previously Prepared Credit Report for One or More Additional End-Users ... 9-9
Request a New Credit Report and Simultaneously Provide It to One or More Additional End-Users ... 9-11
Send a Secondary Use Notification Request to a Credit Bureau ... 9-12
Setting “Secondary Use Notification” Action Type for Various MISMO Versions ... 9-14
R
EPORTINGA
DDITIONALE
ND-U
SERA
UTHENTICATIONE
RRORS... 9-15
CHAPTER 10: RISK BASED PRICING DISCLOSURE RECOMMENDATION ... 10-1
B
ACKGROUND... 10-1
Repositories and Credit Bureaus – Defined ... 10-1
Risk Based Pricing Overview ... 10-2
MISMO
S
UPPORT FORR
ISKB
ASEDP
RICING... 10-2
KEY Element for Credit Score Ranking ... 10-2
KEY Element for Credit Score Range ... 10-2
KEY Element for Histogram Information ... 10-3
EMBEDDED File for Histogram Graphic ... 10-4
EMBEDDED File for Risk Based Disclosure Letter ... 10-5
XML Implementation Guide: Credit Reporting – Version 2
Introduction
Chapter 1: Introduction
Purpose of this Document
This document is designed to assist individuals who are implementing the
MISMO XML Credit Reporting standards – for both credit request transaction
and for the credit response transaction. The guide covers the credit request
and credit response section by section. Numerous examples with sample
XML credit data are provided throughout the guide, along with detailed
explanations. Not all of the credit data elements attributes will be discussed in
detail in this guide. See the Credit Reporting LDD (Logical Data Dictionary)
for definitions of the data attributes not covered in this section.
Version and Release
This implementation guide is based on versions 2.1, 2.1.1, 2.3, 2.4 and 2.4.1.1
of the MISMO standard. The MISMO Logical Data Dictionary (LDD), and
Document Type Definitions (DTDs), sample files and implementation guides
can be downloaded from the www.mismo.org web site.
Comments
Comments, questions, and suggestions for improvement of this document may
be submitted directly to either of the Credit Reporting Work Group Co-Chairs.
Mike Bixby – LandAmerica Credit Services [[email protected]]
Paul Wills – Equifax Mortgage Services [[email protected]
]
MISMO MXCompliance Program
To protect the investments of the lender and vendor community who
participate in developing and implementing standards-based solutions, the
Mortgage Industry Standard Maintenance Organization (MISMO) established
a voluntary compliance service, known as MXCompliance.
Defining compliance objectively and providing “marks” of compliance to
those organizations that meet the testing standards will provide assurance to
providers and purchasers that the interfaces marked as “MXCompliant” are
truly mapped to and supportive of the standards as published on the MISMO
web site, and thus provide for maximum reuse from trading partner to trading
partner.
More information about the program is on the MISMO MXCompliance web
site at: http://mxcompliance.mismo.org/.
XML Implementation Guide: Credit Reporting – Version 2
Introduction
Transitioning from Earlier Standards Versions
If you have implemented earlier standards versions, you may find it helpful to
review the “Change List” documents included with each release of the
standard. The document is part of the Credit Reporting DTD package when
you download it from the MISMO web site. It contains a list of changes
implemented since the previous version.
What Else You Will Need
This guide covers aspects of the MISMO standard that are specific to credit
reporting. To fully implement the standard, MISMO provides other files that
can be downloaded from the MISMO web site (http://www.mismo.org).
o MISMO XML Implementation Guide: General Information –
Version 2 – This guide covers the MISMO architecture, a general
discussion of types of MISMO elements and attributes, plus an
overview of the MISMO Transaction Envelope.
o Credit DTD Files – The Document Type Definition (DTD) files
define the structure of each of the process area data sets. These files
are utilized to develop, write and read XML data files.
o Credit LDD File – Each mortgage process area also provides a
Logical Data Dictionary (LDD), which defines each data element and
attribute used in the DTD.
o Sample XML Credit Files – These can also be downloaded from the
MISMO web site.
Files Included with the Data Standards Download
Three separate Credit Reporting DTDs are provided in the MISMO Version 2
of the XML mortgage standards:
CREDIT_REQUEST_v2_x.dtd – used to request any type of credit
reporting product. This DTD included the AUS 2.x Loan Application in
its entirety, to allow for easy implementation by those who are already
supporting the AUS (Automated Underwriting System) standard.
CREDIT_REQUEST_v2_x_MergeOnlydtd – used only to request
“Merge” credit reports. Only the basic borrower information is supported,
such as borrower name, SSN, date of birth and address.
This DTD is a subset of the CREDIT_REQUEST_v2_x.dtd. XML
request files created using the “Merge Only” DTD will also validate
against the full CREDIT_REQUEST_v2_x.dtd file.
XML Implementation Guide: Credit Reporting – Version 2
Introduction
CREDIT_RESPONSE_v2_x.dtd – used to generate any type of credit
response – such as “Merge”, “Merge Plus”, “RMCR” (Residential
Mortgage Credit Report), error reports and others.
XSD Schema Files - are included with Versions 2.4 and later. Some
XML software uses XSD Schema files for the data definitions, rather than
DTDs. These files are provided as an alternative to DTDs but are
equivalent to the DTDs.
The MISMO Transaction Envelope
MISMO has developed a set of Transaction Envelope DTDs that can be used
to wrap the credit request and credit response transaction data. The MISMO
Transaction Envelope DTDs are fully incorporated within the Credit
Reporting DTDs.
The Transaction Envelope elements and attributes cover the basic information
common to most transactions – elements that identify the requesting party,
receiving party, responding party and other reference data that is commonly
exchanged between business partners.
The envelope transaction elements and attributes will not be covered in this
document. The MISMO XML Implementation Guide: General
Information – Version 2 describes the MISMO Transaction Envelope in
detail.
Repositories and Credit Bureaus – Defined
Before getting into the details of the credit request and credit response
transactions, it‟s probably a good idea to identify and define two of the parties
involved in the production of the credit report.
Repositories
The credit data “repositories” are the companies that collect and store that
credit data on individuals. Equifax™, Experian
SMand Trans Union
®are the
three primary “repositories” for credit data.
Credit Bureau
The “credit bureau” is the agency that creates the credit report for the lender.
They are also sometimes referred to as the “credit reporting agency” (CRA),
or sometimes as the “credit vendor”. For consistency, in this document and
the MISMO DTD and LDD files, we will always use the term “credit bureau”.
XML Implementation Guide: Credit Reporting – Version 2
Introduction
Advantage Credit, Equifax Mortgage Services, Fiserv CredStar, First
American Credco, Kroll Factual Data, LandSafe Credit Services,
LandAmerica Credit Services and LSI Credit Services are examples of
credit bureaus.
When a credit request is received by a credit bureau, the credit bureau then
requests the raw credit data from one or more of the repositories. The credit
bureau then processes and formats the credit data into a final credit report,
which is returned to the lender.
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Chapter 2: Credit Request – Section By Section
This section of the manual provides general information about each section of
a credit report request. Below is a sample credit request file. The outlined
area of the sample, beginning the CREDIT REQUEST element, is the portion
of the standard that is covered in this section of the guide.
Sample XML Credit Request (with MISMO Request Envelope)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE REQUEST_GROUP SYSTEM "CreditRequest_v2_1.dtd"> <REQUEST_GROUP MISMOVersionID="2.1">
<REQUESTING_PARTY _Name="MFC Mortgage"
_StreetAddress="21650 Oxnard Street"
_City="Woodland Hills" _State="CA" _PostalCode="91364"/> <RECEIVING_PARTY
_Name="ABC Services"
_StreetAddress="7200 Peachtree Street"
_City="Atlanta" _State="GA" _PostalCode="30010"/> <REQUEST RequestDatetime="2002-01-08T17:19:01" InternalAccountIdentifier="ABC-0732">
<KEY _Name="MFC Transaction ID" _Value="702430023"/> <KEY _Name="MFC Portfolio ID" _Value="MFC2002-0030"/> <REQUEST_DATA>
<CREDIT_REQUEST MISMOVersionID="2.1" LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R">
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> </CREDIT_REQUEST_DATA> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK" _SSN="530889999"
_UnparsedName="MARION C BRICK"> <_RESIDENCE
_StreetAddress="3750 S BRANDES AV # 242" _City="LAS VEGAS"
_State="NV" _PostalCode="89103"/> </BORROWER> </LOAN_APPLICATION> </CREDIT_REQUEST> </REQUEST_DATA> </REQUEST> </REQUEST_GROUP>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
CREDIT REQUEST Element
The DTD segment below shows the major component elements of the
CREDIT REQUEST element. Normally, the only two major components used
are the CREDIT REQUEST DATA element and the LOAN APPLICATION
element. The CREDIT INQUIRY, CREDIT LIABILITY and CREDIT PUBLIC
RECORD elements are only used when ordering an Update to a liability or
public record that appeared in a previous credit report.
The DATA INFORMATION element records information about the software
version that produced the credit request. (DATA INFORMATION is only
available in Version 2.3 and later.)
The SERVICE PAYMENT element is used to collect payment data such as
credit card data for online consumer reports. (SERVICE PAYMENT is only
available in Version 2.1.1 and later.)
The EMBEDDED_FILE element is used to send borrower authorizations or
loan applications that may be in a PDF, TIFF or HTML format.
(EMBEDDED_FILE is only available in Version 2.4.1.1 and later.)
An asterisk (
*
) appearing after an element indicates that it is optional, and it
can be used in an XML file more than one time. A question mark (
?
) after an
element indicates that it is optional, but it can only be used once in an XML
file.
Major CREDIT REQUEST Elements from DTD
<!ELEMENT CREDIT_REQUEST(CREDIT_REQUEST_DATA*,
_DATA_INFORMATION*, NEW: Ver 2.3
SERVICE_PAYMENT*, NEW: Ver 2.1.1
CREDIT_INQUIRY*, CREDIT_LIABILITY*, CREDIT_PUBLIC_RECORD*, LOAN_APPLICATION?,
EMBEDDED_FILE*)> NEW: Ver 2.4.1.1
CREDIT REQUEST Attributes
The CREDIT REQUEST element has several attributes worth mentioning here
because of their importance.
CREDIT REQUEST Element with Attributes
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R">
... Other CREDIT REQUEST elements and attributes go here ...
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
MISMO Version ID – identifies which version of the DTD this section of
the data conforms to. This attribute is required.
Lender Case Identifier – the lender enters the loan number, reference
number, or case number related to this credit request. This reference
number will normally appear on the human readable version of the credit
report. This attribute is required by most credit bureaus.
Requesting Party Requested By Name – the name of the person actually
requesting the credit report. In the future, if the borrower ever asks why a
credit report was requested, this data attribute will provide the name of the
person who authorized pulling the borrower‟s credit data. This attribute is
required by most credit bureaus.
CREDIT REQUEST Element Usage
The remainder of this chapter gives a brief overview of each section of a
credit request. The Credit Request DTDs do not control the usage of the
individual data elements that comprise the credit request. This document
provides guidance for how and when to use the data elements. One of the
categories of information provided for each section is “Usage”. YES
indicates that a data element is generally used for a particular credit request
type, and NO indicates that the data element is generally not used for that
credit request type.
The most commonly used types of credit requests are:
Merge – A merge report (also called merged infile) includes data on
file from the selected credit data repositories.
RMCR – Residential Mortgage Credit Report is an enhanced credit
product that contains verified information and/or additional
investigation.
Score Only – Provides credit risk scores only.
Other categories provided for each element are “Required?” – describes
whether or not the data element is required, “Purpose” – a short summary
describing what the data element is used for.
The final category, “Restrictions” lists any DTD or Version restrictions for
the data element.
Examples: Not available in Merge-Only DTD.
Available only for Version 2.1.1 and later.
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
CREDIT REQUEST DATA Element
Usage:
Merge = YES RMCR = YES Score Only = YES
Required?
Normally appears in all requests, but this element may not
required by a credit vendor if credit request parameters are
always the same for a customer, and they are on file with the
credit bureau processing the request.
Purpose:
Specifies the credit report type requested, the action requested,
credit repositories requested and other request parameters.
Multiple CREDIT REQUEST DATA elements can appear in a
CREDIT REQUEST element – one for each credit report being
requested.
Restrictions: None.
Sample CREDIT REQUEST DATA Element
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> <CREDIT_SCORE_MODEL_NAME _Type="EquifaxBeacon5.0"/> <CREDIT_SCORE_MODEL_NAME _Type="ExperianFairIsaac"/> <CREDIT_SCORE_MODEL_NAME _Type="TransUnionEmpirica"/> </CREDIT_REQUEST_DATA>
<LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999"
_UnparsedName="MARION C BRICK">
<_RESIDENCE _StreetAddress="3750 S BRANDES AV # 242" _City="LAS VEGAS" _State="NV"
_PostalCode="89103"/> </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Typical “Merge” Request Options
The most common type of report in use today in the mortgage industry, is the
three-repository Merge file. To submit a new request, the Credit Report
Request Action Type is set to Submit, and the Credit Report Type is set to
Merge. If you are ordering a combined credit report for a borrower / spouse
pair, set the Credit Request Type to Joint, otherwise set the attribute‟s value to
Individual.
The CREDIT REPOSITORY INCLUDED element is used to identify which
repository bureaus should be included in the request. In the sample below, all
three repositories – Equifax, Experian and Trans Union are being requested.
Of course, if you did not want to request data from all of the repositories you
would set the attribute value of the ones you didn‟t want to N (No).
Sample CREDIT REQUEST DATA – “Three Repository Merge”
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> </CREDIT_REQUEST_DATA>
“Force New” Request Option
When the Credit Report Request Action Type is set to Submit, as in the above
example, the Credit Bureau will normally first determine if a recent copy of
that credit report data already exists on their system. Beginning with Version
2.4.1.1 and later, when the Credit Report Request Action Type is set to Force
New, the Credit Bureau will request new credit data from the repository
bureaus. This option is normally used only when credit data has been recently
corrected or updated, and the requestor wants to “force new data” to be
requested. Verify that your Credit Bureau supports this option before using it..
Sample CREDIT REQUEST DATA – “Force New” Request
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="ForceNew" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> </CREDIT_REQUEST_DATA>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Selecting Number of Repositories to Be Requested
The previous example showed a request with specific repository bureaus
being selected. It is also possible to just choose the number of repositories to
be requested, and let the credit bureau choose the specific repository bureaus
based on a zip-code table or some other method agreed upon by the credit
trading partners.
Sample CREDIT REQUEST DATA – Repositories Selected Count
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRepositoriesSelectedCount=”2” CreditRequestType="Individual"/>
Reissue Request
To request that the credit bureau re-send you an existing report, you normally
need to send the original credit report number in the Credit Report Identifier
attribute and set the Credit Report Request Action Type to Reissue. One of
the common uses of a Reissue Request is where a lender requests that a Credit
Report “reissue” a credit report that was originally ordered by a mortgage
broker. See Chapter 9 of this document for more detailed information on
reissues and secondary use notifications.
Sample “Reissue” Credit Request
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Reissue" CreditReportType="Merge" CreditReportIdentifier=”02-0027388” CreditRequestType="Individual"/>
Secondary Use Notification Request
In some business scenarios, the entity that ordered the original credit report,
may have forwarded a copy of the credit report to another entity that has a
permissible purpose to view or use the credit report data. In this case, there
may be a requirement to notify the Credit Bureau about the “secondary use”
of the original credit report, but it is not necessary for the Credit Bureau to
send another copy of the credit report. In Version 2.4.1.1 and later, this
notification can be accomplished by setting the Credit Report Request Action
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Sample “Secondary Use Notification” Credit Request
<REQUEST_GROUP MISMOVersionID="2.4.1.1"> <REQUESTING_PARTY _Name="Lender"/> <RECEIVING_PARTY _Name="Credit Bureau"/> <REQUEST InternalAccountIdentifier="Lndr001">
<KEY _Name="Additional End-User (1) Name" _Value="Mortgage Insurer"/>
<KEY _Name="Additional End-User (1) Internal Account Identifier" _Value="MtgIns001"/> <REQUEST_DATA> <CREDIT_REQUEST> <CREDIT_REQUEST_DATA CreditReportIdentifier="07031113" CreditRequestActionType="SecondaryUseNotification"/> </CREDIT_REQUEST>
... LOAN_APPLICATION DATA GOES HERE ...
</REQUEST_DATA> </REQUEST>
</REQUEST_GROUP>
Retrieve Request
In Version 2.1.1 and later, to request the delivery of an updated, upgraded or
completed report, set the Credit Report Request Action Type to Retrieve and
set the original credit report number in the Credit Report Identifier attribute.
Sample “Retrieve” Credit Request
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" CreditRequestDateTime="2002-08-08T17:19:01" CreditReportIdentifier="14-0022558" CreditReportRequestActionType="Retrieve" CreditReportType="RMCR"/>
Upgrade to RMCR Request
Commonly a mortgage broker will order a one, two or three repository Merge
file to see if the loan applicant qualifies for the loan. Depending on the result,
the broker may then request that the Merge report be upgraded to a RMCR
(Residential Mortgage Credit Report). To request such an upgrade, the Credit
Report Request Action Type is set to Upgrade, the Credit Report Type is set to
RMCR and the credit report number of the original credit report is entered in
the Credit Report Identifier attribute.
Sample “Upgrade to RMCR” Credit Request
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001"
CreditRequestDateTime="2002-01-09T10:58:43" CreditReportRequestActionType="Upgrade" CreditReportType="RMCR"
CreditReportIdentifier=”02-0027388” CreditRequestType="Individual"/>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Update Request
After a lender receives and reviews the credit report, sometimes there is a
need to have the credit bureau “update” incorrect or outdated information on
the initial credit report.
For example, the borrower may advise the lender that his Sears account,
which had shown a $250 past due balance, has now been paid in full and the
account is closed. Credit request transactions created with the
CREDIT_REQUEST_v2_x.dtd allow liability and public record element
data from the original credit response transaction to be transmitted back to the
credit bureau to be updated. After the credit bureau verifies the new
information and has the correction made at the repositories, an updated
version of the credit report is returned to the lender.
To request a credit report update, the Credit Report Request Action Type is set
to Update and the credit report number of the original credit report is entered
in the Credit Report Identifier attribute. Any CREDIT LIABILITY or CREDIT
PUBLIC RECORD element from the original report should also be included,
along with a CREDIT COMMENT that identifies what information needs
updating.
Version 2.1.1 and later of the Credit Request DTD also supports sending
CREDIT INQUIRY elements for updating. This may be useful to a lender that
wants to know, for example, if a recent credit inquiry by GMAC resulted in a
new loan debt that was not reported by the borrower.
Version 2.3 and later of the Credit Request DTD also supports a new _Type
attribute for the CREDIT COMMENT element. For Update requests, this
attribute should be set to Instruction.
NOTE: The CreditRequest-MergeOnly_v2_x.dtd does not have any of the
CREDIT LIABILITY, CREDIT PUBLIC RECORD or CREDIT INQUIRY
elements used in Update requests. If you plan to use the Update request, you
will need to implement the CreditRequest_v2_x.dtd.
A sample Update request is shown on the following page that asks the credit
bureau to verify the balance and account status on a Sears liability and
whether or not a loan was issued by GMAC. The liability and inquiry records
from the original credit report are included along with a comment giving the
credit bureau instructions for each item. Since the Update request includes a
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Sample “Update” Credit Request
<CREDIT_REQUEST MISMOVersionID="2.3"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="ssn555336666" CreditRequestDateTime="2003-08-08T13:29:41" CreditReportIdentifier="14-0022558" CreditReportRequestActionType="Update" CreditReportType="MergePlus" CreditRequestType="Individual"> </CREDIT_REQUEST_DATA>
<CREDIT_INQUIRY CreditInquiryID="CRInq0007" BorrowerID="ssn555336666"
_Name="GMAC"
_Date="2003-07-10"
CreditBusinessType="Finance" CreditLoanType="AutoLoan"/>
<CREDIT_COMMENT _SourceType="Lender" _Type="Instruction"> <_Text>PLEASE VERIFY WHETHER CREDIT WAS ISSUED</_Text> </CREDIT_COMMENT>
</CREDIT_INQUIRY>
<CREDIT_LIABILITY CreditLiabilityID="CRLiab0034" BorrowerID="ssn555336666" _AccountIdentifier="1743911111" _AccountOpenedDate="1999-12" _AccountOwnershipType="Individual" _AccountReportedDate="2003-06" _AccountStatusType="Open" _PastDueAmount="75" _UnpaidBalanceAmount="220" CreditLoanType="CreditCard"> <_CREDITOR _Name="SEARS"/>
<_CURRENT_RATING _Code="2" _Type="Late30Days"/>
<CREDIT_COMMENT _SourceType="Lender" _Type="Instruction"> <_Text>Borrower says Account is paid/closed</_Text> <_Text>PLEASE VERIFY ZERO BALANCE/STATUS</_Text> </CREDIT_COMMENT>
</CREDIT_LIABILITY> <LOAN_APPLICATION>
<BORROWER BorrowerID="ssn555336666" _BirthDate="1978-09-01" _FirstName="JEAN" _LastName="LAPHROIG"
_SSN="555336666"/> </LOAN_APPLICATION>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
Requesting Credit for Multiple Borrowers on a Loan
Most loans involve a single borrower or a borrower / spouse pair. For
mortgage loans, however it is not uncommon to have additional borrowers on
the loan. When requesting credit reports for a loan with multiple sets of
borrowers, there needs to be a separate CREDIT REQUEST DATA
element for each borrower data set. A Joint credit request may include a
borrower / spouse pair; otherwise, it is an Individual credit request.
A separate credit response will be returned for each CREDIT REQUEST
DATA element present in the request.
The next sample file includes three borrower sets – one married couple, John
Doe Jr. and Jane Doe, and two single unmarried relatives, John Doe Sr. and
Henry Block. The married couple is referenced in one CREDIT REQUEST
DATA element. Each of the unmarried relatives has their own CREDIT
REQUEST DATA element, for a total of three credit requests.
The Borrower ID attributes are used to link each CREDIT REQUEST DATA
element to specific BORROWER elements.
Sample Credit Request – Multiple Borrower Sets
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001"
BorrowerID="BorRec0001 BorRec0002" CreditReportRequestActionType="Submit" CreditReportType="Merge"
CreditRequestType="Joint">
<CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y"/> </CREDIT_REQUEST_DATA>
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0002" BorrowerID="BorRec0003" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y"/> </CREDIT_REQUEST_DATA>
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0003" BorrowerID="BorRec0004" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y"/> </CREDIT_REQUEST_DATA>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
<LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _SSN=”123457001” _FirstName="John" _LastName="Doe"
_NameSuffix="JR"> </BORROWER>
<BORROWER BorrowerID="BorRec0002" _SSN=”123457002” _FirstName="Jane" _LastName="Doe">
</BORROWER>
<BORROWER BorrowerID="BorRec0003" _SSN=”123457003” _FirstName="John" _LastName="Doe"
_NameSuffix="SR"> </BORROWER>
<BORROWER BorrowerID="BorRec0004" _SSN=”123456001” _FirstName="Henry" _LastName="Block"> </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
Requesting Credit Scores
Many lenders and other parties requesting a credit report are setup to
automatically receive one or more credit scores with each credit report. The
CREDIT REQUEST DATA element allows the inclusion of one or more
CREDIT SCORE MODEL NAME elements, which can be used to specify one
or more score models on a report-by-report basis.
There are three methods for requesting specific score models on an individual
report. Check with your credit bureau to see which one(s) they support:
1. No action is required if your credit bureau has setup default scores to order
for each of your credit requests. In this situation is it not necessary to add
CREDIT SCORE MODEL NAME elements to your request.
2. The second method is to specify the exact Credit Score Model Name Type
- for example; Equifax Beacon 5.0, Experian Fair Isaac or Trans Union
Empirica. In this example, credit reports are being ordered from all three
repositories and in addition, three score models are being requested using
the repository bureau‟s product name.
Sample Credit Score Request Using Credit Score Model Name Type
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2007-01-18T09:29:47" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> <CREDIT_SCORE_MODEL_NAME _Type="EquifaxBeacon5.0"/> <CREDIT_SCORE_MODEL_NAME _Type="ExperianFairIsaac"/> <CREDIT_SCORE_MODEL_NAME _Type="TransUnionEmpirica"/> </CREDIT_REQUEST_DATA>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
3. Beginning with Version 2.4, score models can also be requested by
specifying the Credit Score Category Type. This allows a lender to order
a score model from the repository bureau without having to know each
repository bureau‟s product name for the score model. In this example,
credit reports are being ordered from Equifax and Trans Union and
“FICO” category score models are being requested from those two
repositories. When the credit bureau received the credit request, they will
order the appropriate repository bureau score model name that matches the
specified score category type.
Sample Credit Score Request Using Credit Score Category Type
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2007-01-18T09:29:47" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _TransUnionIndicator="Y"/> <CREDIT_SCORE_MODEL_NAME CreditScoreCategoryType="FICO"/> </CREDIT_REQUEST_DATA>
Checking on the Status of a Request
Since an RMCR (Residential Mortgage Credit Report) is manually
investigated, it is not returned immediately like a “Merge” report. Some
credit bureaus will allow you to send an electronic “Status Query” transaction
to check on the status of RMCR requests. To create a status query, the
Requested Action Type is set to Status Query, and the credit report number (if
known) is entered in the Credit Report Identifier attribute.
Sample “Status Query” Credit Request
<CREDIT_REQUEST_DATA CreditReportRequestActionType="StatusQuery" CreditReportType="RMCR"
CreditReportIdentifier=”02-0027388” />
For information on how the credit bureau may respond to a “Status Query”
using the MISMO Version 2 Credit Response, see “Chapter 5: Credit Status
Response” in this document.
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
DATA INFORMATION Element
Usage:
Merge = YES RMCR = YES Score Only = YES
Required?
No.
Purpose:
This data structure is available to record the source data
versions used to produce the MISMO XML transactions. This
information may be useful for troubleshooting problems in
production.
Restrictions: Available only for Version 2.3 and later.
Sample Credit Request with DATA INFORMATION Element
<CREDIT_REQUEST MISMOVersionID="2.3"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <_DATA_INFORMATION>
<DATA_VERSION _Name="BEST-LOS" _Number="5.0"/> </_DATA_INFORMATION>
<CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="Bor001" CreditRequestDateTime="2003-01-03T13:21:58" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> </CREDIT_REQUEST_DATA> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999"
_UnparsedName="MARION C BRICK">
<_RESIDENCE _StreetAddress="3750 S BRANDES AV # 242" _City="LAS VEGAS" _State="NV"
_PostalCode="89103"/> </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
SERVICE PAYMENT Element
Usage:
Merge = YES RMCR = YES Score Only = YES
Required?
Only if needed for billing of a service.
Purpose:
This data structure is available in the CREDIT REQUEST
element to facilitate billing of online consumer reports using a
credit card or other payment method.
Restrictions: Available only for Version 2.1.1 and later.
Sample Credit Request with SERVICE PAYMENT Data
<CREDIT_REQUEST MISMOVersionID="2.1.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001"
CreditRequestDateTime="2002-08-13T13:21:42" CreditReportRequestActionType="Submit" CreditReportType="MergePlus"/>
<SERVICE_PAYMENT _AccountIdentifier="5432200232559994" _AccountHolderName="MARION C BRICK"
_AccountHolderTelephoneNumber="4893440338" _AccountExpirationDate="2005-04"
_SecondaryAccountIdentifier="6425" _MethodType="MasterCard"/>
<LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999" >
<_RESIDENCE _StreetAddress="3750 S BRANDES AV # 242" _City="LAS VEGAS" _State="NV"
_PostalCode="89103" BorrowerResidencyDurationYears="2" MonthlyRentAmount="1500"> </_RESIDENCE> </BORROWER> </LOAN_APPLICATION> </CREDIT_REQUEST>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
CREDIT INQUIRY Element
Usage:
Merge = YES RMCR = YES Score Only = NO
Required?
Only used when requesting an Update to an inquiry record by
the credit bureau.
Purpose:
This element is used to return the original copy of a Version
2.x CREDIT INQUIRY element from a previous Credit
Response transaction, for the current status of the earlier
inquiry.
Restrictions: Available only for Version 2.1.1 and later.
Not available in Merge-Only DTD.
.
Requesting Updates to Inquiry Data
The Version 2.1.1 Credit Request supports ordering of updates to inquiry data
on a previously ordered credit report. To order an update, set the Request
Action Type to Update and include one or more CREDIT INQUIRY elements
from the original credit report that should be updated. Notice the CREDIT
COMMENT element has instructions to the credit bureau from the lender.
Sample Credit Request for update of CREDIT INQUIRY Data
<CREDIT_REQUEST MISMOVersionID="2.1.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001"
CreditRequestDateTime="2002-08-28T14:23:27" CreditReportRequestActionType="Update" CreditRequestType="Individual">
</CREDIT_REQUEST_DATA>
<CREDIT_INQUIRY CreditInquiryID="CRInq0001" BorrowerID="BorRec0001"
_Name="MONEY STORE" _Date="2002-07-25"
CreditBusinessType="Finance"
CreditLoanType="HomeEquityLineOfCredit"/> <CREDIT_COMMENT _SourceType="Lender">
<_Text>PLEASE VERIFY WHETHER CREDIT WAS ISSUED</_Text> </CREDIT_COMMENT>
</CREDIT_INQUIRY> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999" > </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
CREDIT LIABILITY Element
Usage:
Merge = YES RMCR = YES Score Only = NO
Required?
Only used when requesting an Update to a liability record by
the credit bureau.
Purpose:
This element is used to return the original copy of a Version
2.x CREDIT LIABILITY element from a previous Credit
Response transaction, for re-verification of a balance or some
other type of update.
Restrictions: Not available in Merge-Only DTD.
Requesting Updates to Liability Data
The Version 2.x Credit Request supports ordering of updates to liability data
delivered on a previously ordered credit report. To order an update, set the
Request Action Type to Update and include one or more CREDIT LIABILITY
elements from the original credit report that should be updated. The CREDIT
COMMENT element has instructions to the credit bureau from the lender.
Sample Credit Request for update of CREDIT LIABILITY Data
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Update" CreditReportType="Merge" CreditRequestType="Individual"> </CREDIT_REQUEST_DATA>
<CREDIT_LIABILITY CreditLiabilityID="CRLiab0001" BorrowerID="BorRec0001" _AccountIdentifier="1743911111" _AccountOpenedDate="1998-06" _AccountOwnershipType="Individual" _AccountReportedDate="2001-12" _TermsDescription="$70/MO" _UnpaidBalanceAmount="420" CreditLoanType="InstallmentSalesContract"> <_CREDITOR _Name="AFFILIATED ACCEP CORP"/> <_CURRENT_RATING _Code="1" _Type="AsAgreed"/> <CREDIT_COMMENT _SourceType="Lender" _Code=”01”> <_Text>Borrower Says Account Now Paid</_Text> <_Text>PLEASE VERIFY ZERO BALANCE</_Text> </CREDIT_COMMENT>
</CREDIT_LIABILITY> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
CREDIT PUBLIC RECORD Element
Usage:
Merge = YES RMCR = YES Score Only = NO
Required?
Only used when requesting an Update to a public record by
the credit bureau.
Purpose:
This element is used to return the original copy of a Version
2.x CREDIT PUBLIC RECORD element from a previous
Credit Response transaction, for re-verification of a case
disposition or some other type of update.
Restrictions: Not available in Merge-Only DTD.
Requesting Updates to Public Record Data
The Version 2.x Credit Request supports ordering of updates to public record
data delivered on a previously ordered credit report. To order an update, set
the Request Action Type to Update and include one or more CREDIT
PUBLIC RECORD elements from the original credit report that should be
updated. Notice the CREDIT COMMENT element has instructions to the
credit bureau from the lender.
Sample Credit Request for update of CREDIT PUBLIC RECORD
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Update" CreditReportType="Merge" CreditRequestType="Individual"> </CREDIT_REQUEST_DATA>
<CREDIT_PUBLIC_RECORD CreditPublicRecordID="CRPubR0001" BorrowerID="BorRec0001" _DispositionDate="2001-10" _DispositionType="Unsatisfied" _DocketIdentifier="99-044444" _FiledDate="1999-01" _LegalObligationAmount="512"
_PlaintiffName="COLLECTION, CBCMERCY AMB, COLL" _Type="Judgment">
<CREDIT_COMMENT _SourceType="Lender" _Code=”22”> <_Text>Borrower Says Judgment Now Paid</_Text> <_Text>PLEASE VERIFY JUDGMENT IS SATISFIED</_Text> </CREDIT_COMMENT>
</CREDIT_PUBLIC_RECORD> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999" > </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
XML Implementation Guide: Credit Reporting – Version 2
Credit Request – Section By Section
LOAN APPLICATION
Usage:
Merge = YES RMCR = YES Score Only = YES
Required?
Yes.
Purpose:
Provides borrower-identifying data required for a credit
request transaction. Borrower data for a Merge or Score Only
Request includes the full name, plus current and recent
previous Residence Addresses. For RMCR Requests, the
Loan Application element may also include, Alias/AKA data,
Assets and Liabilities, Declarations, Employment and
Landlord data.
Restrictions: None.
Borrower Data Used in a Merge or Score Only Request
The borrower data needed for a Merge or Score Only Request is the
borrower‟s name (including generation), SSN and current address. Any
additional information that is provided, such as date of birth and previous
addresses will improve the search criteria used by the credit repositories when
they are matching that data to the information in their credit files.
Sample LOAN APPLICATION Element for Merge Credit Request
<CREDIT_REQUEST MISMOVersionID="2.1"
LenderCaseIdentifier="MFC2002-0030" RequestingPartyRequestedByName="Sean R"> <CREDIT_REQUEST_DATA CreditRequestID="CRReq0001" BorrowerID="BorRec0001" CreditRequestDateTime="2002-01-08T17:19:01" CreditReportRequestActionType="Submit" CreditReportType="Merge" CreditRequestType="Individual"> <CREDIT_REPOSITORY_INCLUDED _EquifaxIndicator="Y" _ExperianIndicator="Y" _TransUnionIndicator="Y"/> </CREDIT_REQUEST_DATA> <LOAN_APPLICATION>
<BORROWER BorrowerID="BorRec0001" _BirthDate="1972-03-09" _FirstName="MARION" _LastName="BRICK"
_SSN="530889999"
_UnparsedName="MARION C BRICK">
<_RESIDENCE _StreetAddress="3750 S BRANDES AV # 242" _City="LAS VEGAS" _State="NV"
_PostalCode="89103"/> </BORROWER>
</LOAN_APPLICATION> </CREDIT_REQUEST>
