This XML Credit Report Notes document (hereafter referred to as just “Notes”) was created so that the viewer would be able to study and critique the proposed Credit Report structure without having to view the actual Document Type Definition (DTD) or Schema files. Since the Extensible Markup Language (XML) and its editing tools are still in their infancy, most reviewers will be able to more easily digest this document rather than looking directly at the DTD file itself.

This draft of these “Notes” was created using a word processor. I plan to generate future versions directly from the DTD file, with formatting provided by either Cascading Style Sheet (CSS) or Extensible Style Language (XSL). For me, being able to automatically generate documentation and implementation guides directly from a DTD or Schema is just one of the validations for the all of the “hype” surrounding XML and its extensions – XSL, XLink and XPointers.

If this proposed credit report structure is to become a “standard” that will be actually be used by credit bureaus, mortgage companies, brokers, mortgage insurers and others in the industry, it will have to be understandable and complete. It should also be able to support the “little details” in the credit report that are needed by its users. For that reason, please send suggestions and corrections to my email address, Info1EDI@mindspring.com, or give me a call (305-829-5549). If you would like to participate in this review process, or monitor its progress, check the www.mbaxml.org web site on a regular basis.

XML CREDIT REPORT DESIGN GOALS

The XML Credit Report is not just a conversion from an X12 format to an XML format. The XML Credit Report structure attempts to utilize all of the data elements present in the X12 credit transactions, while simplifying or eliminating some of the confusing structures present in those transactions (especially in the X12 833 Credit Request).

Here are several goals of the XML Credit Report design goals that are worth highlighting:

· Maximize Re-Use of Data Structures – The XML Credit Report and XML Credit Request would share the same “Applicant” and “Entity” data structures that are being incorporated into the XML Loan File. The Credit Request would have a “Request Header” structure that could also be used for Flood Certifications, Appraisals, Appraisal Request, Mortgage Insurance, Title Insurance and other transactions requested by loan processors. The Report Header incorporated into the XML Credit Report would also be generic enough to allow its use in other mortgage transactions. This greatly simplifies the programming requirements for the Loan Origination Software companies, and makes widespread adoption of the XML mortgage transactions more likely.

· Make the Data Structures Comprehensive But Simple – The emphasis in X12 transaction development was to make transaction sets as compact as possible and to use existing generic transactions as much as possible. These were worthwhile goals because of the limitations of the computer hardware and software at the time, but it made the transactions, especially larger ones like the Credit Report, very difficult to implement. In developing the XML Credit Report transactions, the emphasis is making all of the information available, and laying out the information in a manner that makes the data easy to grasp for those familiar with credit report data.

· Use X12 Codes Wherever it Makes Sense – Many man-hours were spent developing the code lists used in the X12 transactions and many computer software systems are designed to accept and store these codes. Whenever it is logical to do so, X12 Credit Report has been designed to allow the credit processor to supply the equivalent X12 code for an Account Type, Account Rating, Public Record Type, Status, etc.

· Support the Optional Use of Credit Bureau Codes – Many credit bureaus supply their own common codes on their credit reports that designate Account Ratings, Account Ownership, Account Type, etc. These bureau codes can continue to be supplied by the credit bureaus in the XML Credit Report.

· Allow For Optional Inclusion of Original Repository Bureau Data – Although today’s trend in credit reporting is to supply merged – three bureau reports, some credit report users want to see the original credit repository data and codes that were used to generate the final credit report output. The XML Credit Report can supply this data at several levels of detail – for Payment Pattern Data only, for other specific Liability data elements only, or for the entire Liability record. The same levels of original data can also be supplied for Public Record data.

CHANGES SINCE DRAFT 0.1

The first draft of the XML Credit Report laid out an initial proposal for a standard. This draft builds on the first one and corrects some of its deficiencies. Comments and suggestions from the reviewers of the first draft have either been incorporated into this draft, or are scheduled for inclusion in the next draft. One of the main focuses of this draft is to begin the process of merging data structures from the XML Loan File into the XML Credit Report.

The following is a list of changes since the “0.1” draft of the XML Credit Report.

· “dtdVersion” attribute default value set to “0.2” – Since the XML Credit Report is still in its early stages of development, backwards compatibility to version “0.1” has not been maintained. (“Backward Compatibility” WILL be a concern after we reach the “1.0” version of the standard.

· Incorporate standard abbreviations into element and attribute names – Since some element and attribute names can tend to be quite long, abbreviations are have been implemented discriminately. See the table in the “Element/Attribute Name Abbreviations” section later in this document.

· Add missing codes to “x12Action” attribute – Some of the codes were inadvertently left out of the first draft.

· Change spelling of the “ownerType” attribute “CoBorrower” value to “Coborrower” – This matches the spelling used in the XML Loan File.

· Rename the “Verification” element to “Verified” – This matches the spelling used in the XML Loan File.

· Incorporate XML ENTITY references for reusable attributes and elements – This was done to make the DTD and Schema files smaller and to allow the attributes and elements, that are used more than once, to be defined in a single location. Attribute Entities will always begin with “%a-“ and Element Entities will always begin with “%e-“.

· Incorporate XML ENTITY references for external DTDs – The “Applicant”, “Entity”, and “Verified” data structures from the XML Loan File, were copied into separate DTD files. They were included into the XML Credit Report DTD using an XML “SYSTEM” Entity. These Reference Entities will always begin with “%s-“.

· Disable several XML Credit Report elements that were also included in external DTDs – The “Collateral”, “DateOpened”, “MonthlyPayment”, and “MonthsRemaining” elements in the XML Credit Report DTD were marked as comments. (The XML IGNORE directive is not supported by my DTD Editor – XML Authority – at this time).

· Add support for “original” bureau data for liabilities and public records – The “primaryTradeLine” attribute from the 0.1 draft was deleted. Support for this feature as implemented in the 0.1 draft did not provide a mechanism for linking the original bureau data records (duplicates) to the “primary” or “merged” record. In this draft of the standard, this “linking” is accomplished for liability records by allowing for the definition of an “OriginalLiability” structure that is identical to and a “child” of the “CreditLiability” structure. For public records, an “OriginalPublicRec” structure is provided that is identical to and a “child” of the “CreditPublicRec” structure.

· Modify the “Consumer.xml” credit report sample to match the 0.2 draft version – The Applicant, Entity and Location element structures have been added. The updated sample also includes all of the element and attribute name changes.

ANTICIPATED FUTURE CHANGES

This stage of the XML Credit Report is definitely a “work-in-progress”. There are several important changes already in the works for the next draft, and they are listed below:

· Synchronize the XML “CreditLiability” Element Names with the XML Loan File “Liability” element names.

· Add “Infile Date” to the “CreditFileVariation structure.

· Make the “ReportHeader” and “RequestHeader” element structures more generic. Moving the “ServiceRequested” structure out of the Request Header allows the “RequestHeader” structure to be more generic and re-used in other XML mortgage DTDs. Similar “cleanup” can be done to the “ReportHeader” structure by relocating “RepositoriesReturned” element.

· Create separate DTD files for the “CreditScore”, “ReportHeader” and “RequestHeader” element structures. The CreditScore DTD can be included into the XML Loan File.

· Build a separate CreditRequest DTD that can be used for merged infile requests and RMCR requests. The can be accomplished by just including the Request Header DTD and the Applicant DTD file.

· Add a structure for Document Routing.

· Add support for error elements.

· Include more credit report and credit request samples. The next draft will include a credit report sample that demonstrates the inclusion of duplicate or “original” repository bureau data, and the inclusion of original payment pattern data. Two types of credit request files will be included – merged infile request and RMCR request – both based on the CreditRequest.dtd.

DTD vs XML SCHEMA FORMAT

Should the MBA XML Work Group adopt the XML DTD format or the XML Schema format? The questione could be expanded to include the possibility of using other proposed schema formats such as “XML Data”, “BizTalk”, or SOX (Schema for Object-oriented XML). I’m not going to go into long discourse on which format is better to use, because at this stage it does not really matter. Briefly, the debate centers around which data definition format allows for better data validation and more precise definition of the data format. The XML Schema format does provide these desired features, but it is not yet part of the approved XML standard and is not fully supported in the current internet browsers and data parsers. The XML 1.0 DTD format is an approved standard, but does not allow for precise definition of the data.

What is important right now, is that we agree on an overall XML Credit Report structure, and the element and attribute names that will be used. Once these decisions are made, the conversion of the XML Credit Report data model from one schema format to another is relatively easy.

Accompanying this “Notes” document, I have provided the XML Credit Report structure files in the DTD format:

CreditReport.dtd – XML DTD format – this is the main XML Credit Report DTD.
Applicant.dtd – XML DTD format – this DTD is from the XML Loan File and is included in the CreditReport.dtd
Entity.dtd – XML DTD format – this DTD is from the XML Loan File and is included in the CreditReport.dtd
Verified.dtd – XML DTD format – this DTD is from the XML Loan File and is included in the CreditReport.dtd

In this version of the specification I did NOT include the DTD in the XML Schema format. When I split the DTD into components, I had a problem creating the XML Schema format files. These will be included again in the next draft. If you have Internet Explorer 5.0 you can browse the provided sample credit report file “Consumer.xml”. (If you don’t have IE 5.0 you can still load the sample credit report into any text editor).

PLAGIARISM 101

The XML Credit Report structure steals (re-uses, if you prefer) as much as it can from the XML Loan File structure, which is also currently under development. The MBA XML Work Group has decided that the XML Loan File structure is to be the central document structure on which other mortgage-related documents will be based, so it only makes sense that related data structures should have as much in common as possible.

For example, to generate an XML Credit Report Request transaction, all that a broker or mortgage company would have to do is build a short “Request Header” followed by the same XML “Applicant” data elements from their XML Loan File. When the credit bureau returns the XML Credit Report, it will build a “Report Header”, followed by the same “Request Header” and “Applicant” data elements from the request, followed by the rest of the credit report data.

Re-using XML Loan File element names is just as important as the re-use of element groups such as “Applicant”. For example, it would be simpler for everyone if all mortgage-related transactions used the same spelling for the “PhoneNumber” element. As the MBA XML Work Group approves element and attribute names for the XML Loan File, those same names will be imple mented in the XML Credit Report.

ELEMENTS AND ATTRIBUTES 101

I’m not going to go into an XML tutorial here, but it may be useful to go into a brief description of two frequently used terms that are used when describing an XML data structure: elements and attributes.

Elements (as used in the XML Credit Report) will typically contain actual text or data that you might see on a human-readable credit report. Attributes, on the other hand, provide more information about the element that it is included with, such as the source of the data or code values for the data. You can specify an enumerated list of allowable values for an attribute, which make them handy for storing X12, repository bureau or credit vendor codes for data like account ratings, public record types and so on.

Elements

There are five types of elements used in this document:

· Container Element – This type of element is just a container for other elements. It may or may not have attributes. The “ReportHeader” element is an example of a container element.

· Date Element – This element holds date data, stored in a CCYY-MM-DD format (e.g. 1999-09-01). If there is no “day” value for a date it will be stored in a CCYY-MM format (e.g. 1999-09). The “PaymentPatternStartDate” is an example of a date element.

· Date-Time Element – This element holds date and time data stored in a CCYY-MM-DDTHH:MM:SS format. Note that the date and time are separated by the letter “T” (e.g. 1999-09-01T13:45:03). The “seconds” value may be omitted (e.g. 1999-09-01T13:45). Time values use the “military format” (i.e. 13:00 = 1pm, 14:00 = 2pm, etc.). The “ReportDateTime” is an example of a date-time element.

· Empty Element – This is a special type of XML element that contains only attributes. The only “empty” elements in this document are “RepositoriesRequested” and “RepositoriesReturned”. These elements have an attribute for each repository bureau that tell whether or not that bureau was requested (or returned). Here is an example of what the Repositories Requested element may look like in an actual XML data file:

<RepositoriesRequested equifax=”Yes” experian=”No” transUnion=”No”/>.

· Text Element – This element may hold a text value consisting of a word, phrase, sentence or paragraph depending on where it is used. It could also contain numeric values such as account balances. “ProcessorReportNum” is an example of a text element.

Attributes

There are four types of attributes used in this document:

· Enum Attribute – This type of attribute has an enumerated list of allowable values. This can be as simple as “Yes | No”, as in the “equifax” attribute, to a long list of codes as in the “x12LoanType” attribute.

· ID Attribute – Each XML “ID” attribute used in an XML data file must be unique. In the XML Credit Report DTD, the “creditRecID” attribute has a unique value that is not duplicated. For example, the first credit file from Equifax might have a “creditRecID” attribute set to “EFX-01”, the second Equifax file’s attribute might be set to “EFX-02” and so on. The first Experian file might have a “creditRecID” attribute set to “EXP-01”, the second – “EXP-02”. These ID attributes are used in conjunction with IDREF attributes, to link liability, public record, credit score and inquiry data to the specific repository bureau “credit file” that provided the data.

· IDREF Attribute – The “IDREF” attribute is used in data records that “refer to” or “reference” a record that has the same “ID” attribute. For example, each liability, public record, credit score, and inquiry record has a “CreditDataSource” element, which has multiple credit file IDREF attributes (“creditRecIDREF01”, “creditRecIDREF02”, etc.). If a credit report liability record came from a Equifax credit file with a “creditRecID” equal to “EFX-01”, then that liability record’s “creditRecIDREF01” attribute would be set to “EFX-01”, since it “references” the unique “creditRecID” attribute. There may be more than one “IDREF” attribute with a value of “EFX-01” referring to the unique “ID” attribute of the same value. To hopefully help clarify this concept further, a liability record appearing in a credit report may actually be a “blend” or “merge” of data from two or three different sources. For example, a “Sears” liability may contain data from Equifax credit file “EFX-01”, Experian credit file “EXP-01”, and Trans Union credit files, “TU-01” and “TU-02”. In this case the “Sears” liability record would have four IDREF attributes in its “CreditDataSource” element - creditRecIDREF01=”EFX-01” creditRecIDREF02=”EXP-01” creditRecIDREF03=”TU-01” creditRecIDREF04=”TU-02”.

· String Attribute – This type of attribute contains a text string, which could be a code, word or phrase. Unlike the “Enum” attribute there is no list of valid values provided in the DTD or Schema file. Examples of “string” attributes in the XML Credit Report are the “codeFromRepository” and “codeFromVendor” attributes. These attributes are used to store coded values for their associated element’s text values, but an enumerated list of valid values is not maintained in the XML Credit Report DTD.

Using Understandable Tag Names

One of the original “intents” of the proponents of XML, was that XML files should be easily understandable to a human viewing the file with a text editor or browser. The meaning of Elements and Attributes tag names were supposed to be understandable to the average reader. For example, an X12 data segment might appear as “AMT~T4~250”, whereas the same data might appear in an XML file as “<CurrentBalance>250</CurrentBalance>”.

A computer can be programmed to properly handle either data format, but if a loan officer opens up a credit report file with his favorite web browser, the X12 data will still display as “AMT~T4~250”, while the XML data would display as “Current Balance: 250”. (This might be jumping ahead just a little bit, but the future browser versions will probably have that capability).

Element/Attribute Name Abbreviations

Some element and attribute names are long. I have followed the XML philosophy of making the element names clear and understandable. Using descriptive element names distinguishes XML from more cryptic formats such as X12. Using descriptive element and attribute names, allows the data files to be understood using a browser or text editor.

In some cases, using descriptive names can result in some long element tag names. To alleviate this somewhat, this draft of the XML Credit Report DTD incorporates “Abbreviations for Terms used in XML Element Names”, which is in Appendix D of the document, “X12-XML: Representation of X12 Semantics in XML Syntax”. Other abbreviations that I’ve incorporated on my own are identified in the Source column as “Local”.

The following table is a list of the name abbreviations that are currently used in the XML Credit Report DTD.

Name	Abbreviation	Source
Account	Acct	X12-XML Doc
Amount	Amt	X12-XML Doc
Amounts	Amts	Local
Delinquency	Delinq	Local
Evaluation	Eval	Local
Frequency	Freq	X12-XML Doc
Identifier	ID	X12-XML Doc
Number	Num	X12-XML Doc
Record	Rec	Local

Naming Conventions (UpperCamelWhat?)

Reading specifications documents must be more potent than sleeping pills, but every once in a while something raises my eyelids a little. One of the XML documents I read recently, (visit www.biztalk.org/addMsging2xml.asp, if your interested) used the terms “UpperCamelCase” and “lowerCamelCase” in discussing style guidelines for XML capitalization of element names. (I said it raised my eyelids “a little”, not a lot).

In the proposed XML Credit Report structure, I used the “UpperCamelCase” format for element names, and “lowerCamelCase” for Attribute Names. This makes it easy to tell whether a tag name is an element or attribute since all of my elements begin with an upper case letter, and attributes begin with a lower case letter.

· Element Name examples: CreditReport, CurrentRating, PaymentPattern, RequestDateTime

· Attribute Name examples: creditRecID, ownerType, scoreEval, x12AcctRating

Once again, if we (i.e. the MBA XML Work Group) decide to go with a different naming style, I will modify the XML Credit Report structure to comply.

Using X12 Codes As XML Attributes

Once you get into the Credit Report section of the “Notes” you will see that I have used X12 Codes as XML Attributes for several data elements. Years ago, I sat through several long X12 Work Group meetings where the arduous process of creating these code sets occurred. Since many of the credit report processing systems that I am familiar with, either generate or use these X12 codes, I have included them as optional attributes wherever they would be useful.

Other Codes Used As XML Attributes

In addition to X12 code attributes, there is an optional “codeFromVendor” attribute that can be used to hold data codes that are supplied by the credit vendor that processed the credit report. For example, if you have been getting credit reports that use a particular set of ECOA codes to designate account ownership, the credit bureau or vendor can supply these codes in the “codeFromVendor” attribute.

For some elements I have also included an optional “codeFromRepository” attribute. This attribute can be used for storing the original data codes that were received from the repository bureaus (i.e. Equifax, Experian, Trans Union). This can be useful for auditing credit report data to verify that the code-to-code translation is being handled by the application properly. In many elements the "codeFromRepository" attribute is also accompanied by the "repositorySource" attribute. This is useful in cases where a credit liability or public record consists of data elements from multiple repository bureaus, and it is necessary to identify which bureau supplied the individual "code".

Payment pattern data is an example of how these different “code” attributes could supply the exact format needed by the loan company or bank using the XML Credit Report. A particular credit bureau vendor may be currently supplying a payment pattern formatted as: 114321111111. This payment pattern indicates that in the third month before the Payment Pattern Start Date, the account had a rating of “4” (90+ days late). In the fourth month its rating was “3” (60+ days late), in the fifth month its rating was “2” (30+ days late), and previous to that, its rating was “1” (Current). In this case the Payment Pattern Data, 114321111111, would appear in the “codeFromVendor” attribute.

The X12 Payment Pattern Code displays data either as Current (“C”), or displays the number of months past due at any particular month. Since it is an accepted standard, this is the default format in the XML Credit Report. The same payment pattern discussed in the previous paragraph, would be displayed as “CC321CCCCCCC”. This payment pattern indicates that in the third month before the Payment Pattern Start Date, the account had a rating of “3” (3 months late), in the fourth month the rating was “2” (2 months late), and in the fifth month its rating was “1” (1 month late). Previous to that, its ratings were all “C” (Current).

Both sets of data display the same information. But by using the “codeFromVendor” or “codeFromRepository” attributes, in addition to the default X12 Payment Pattern, the user of the credit report has the flexibility of choosing the coding format they are used to using.

Element and Attribute Entities

DOCUMENT ROUTING

The instant the XML Credit Report and XML Credit Report Request are ready for adoption, there is an immediate need for some type of XML data structure to handle the routing of requests and reports. I’m sure that this is also true for other vendors, banks and mortgage companies with multiple branches. The “BizTalk Framework” has a simple data structure that is similar to the X12 ISA envelope that contains the necessary information for automated routing of documents within a network. We could either use the entire Framework structure or a small portion of it that I have reprinted here:

Message routing can be discussed in more detail in our MBA XML Work Group meeting, I just wanted to introduce one possible solution. A summary of the BizTalk Framework is available at www.biztalk.org/addMsging2xml.asp.

CREDIT REPORT STRUCTURE

The remainder of this document is devoted to the elements and attributes that make up the XML Credit Report. The first element discussed is “CreditReport”, with is the main element from which all other elements are derived. The XML Credit Report structure is formatted below in an indented tree format. The root element, CreditReport, is at the first indentation level. The second indentation level includes the branch elements that are directly included in the CreditReport element. The third indentation level contains elements that are contained within the second level elements, and so on. The “Table of Contents” also displays the XML Credit Report structure in an indented tree format. (If you are viewing this document using a browser or word processor, you can use the underlined “hyperlinks” to navigate around the structure’s elements.)

Element Name: CreditReport
Element Type: Container Element (holds other elements)
Occurrences: Must appear once
Attribute(s): dtdVersion
Comment: "CreditReport" is the root element of this XML data format. This structure supports multiple credit report types: single-bureau infiles, merged infiles, and residential mortgage credit reports (RMCRs).

REPORT HEADER

· Element Name: ReportHeader

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: The Report Header contains elements that give the report number, date and time produced, the name of the credit bureau, and other information about the type of report and which repository bureau’s data were included.

Processor Report Number

· Element Name: ProcessorReportNum

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the credit report number assigned by the processing credit bureau.

Report Date-Time

· Element Name: ReportDateTime

· Element Type: Date-Time Element (CCYY-MM-DDTHH:MM:SS format)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the date and time that the credit report was generated by the processing credit bureau.

Report Processor

· Element Name: ReportProcessor

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: The Report Processor element contains the Loan File DTD’s “Entity” structure, which holds elements containing the processing credit bureau’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Report Type

· Element Name: ReportType (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): x12ProductServiceIDType, codeFromVendor

· Comment: This element contains a text description for the type of credit report (Merged Infile, RMCR, etc). The optional attribute is the ANSI X12 code for the report type. An additional attribute is available for a credit vendor code for the report type.

Repositories Returned

· Element Name: RepositoriesReturned

· Element Type: Empty Element (attributes only)

· Occurrences: Must appear once

· Attribute(s): equifax, experian, transunion

· Comment: The attributes of this element tell which repository bureaus data were included in the report.

Report Price

· Element Name: ReportPrice

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains price information for the credit report.

Amount

· Element Name: Amt

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This text element contains the actual price (no required format: 10, 10.00, $10, $10.00 are all acceptable).

Amount Qualifier

· Element Name: AmtQualifier

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12AmtQualifier

· Comment: This optional text element describes the amount. The optional attribute is the ANSI X12 code for the amount description.

REQUEST HEADER

· Element Name: RequestHeader (also used in other DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: The Request Header contains information originally sent with the initial request for the credit report and is “echoed” back with the credit report. Its elements include the request date and time, the name of the requester and /or loan originator, the loan number, the property address and other details about the type of services requested from the credit bureau.

Processor Request Number

· Element Name: ProcessorRequestNum

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the request number, if any, assigned by the processing credit bureau.

Request Date-Time

· Element Name: RequestDateTime

· Element Type: Date-Time Element (CCYY-MM-DDTHH:MM:SS format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the date and time that the credit report request was generated by the requester.

Request Submitter

· Element Name: RequestSubmitter

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: The Request Submitter element contains the Processor’s Account Number for the Requester, and the Loan File DTD’s “Entity” structure, which holds elements containing the Requester’s name, address, phone, contact name, etc.

Processor Account Number

· Element Name: ProcessorAcctNum (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the account number assigned by the credit report processor to the requester’s account.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Loan Originator

· Element Name: LoanOriginator

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element is used if the loan originator is different than the Requester. It contains the Processor’s Account Number for the Loan Originator, and the Loan File DTD’s “Entity” structure, which holds elements containing the Loan Originator’s name, address, phone, contact name, etc.

Processor Account Number

· Element Name: ProcessorAcctNum (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the account number assigned by the credit report processor to the loan originator’s account.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Bill To

· Element Name: BillTo

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element is used if the “bill to” name is different than the Requester. It contains the Processor’s Account Number for the “bill to” name, and the Loan File DTD’s “Entity” structure, which holds elements containing the Bill To’s name, address, phone, contact name, etc.

Processor Account Number

· Element Name: ProcessorAcctNum (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the account number assigned by the credit report processor to the Bill To’s account.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Property

· Element Name: Property

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: If this credit report is for a mortgage loan, home equity loan or refinance, this element holds the property address. The actual property address components are located in the Loan File DTD’s “Location” structure (which part of the “Entity” structure).

Location

· Element Name: Location

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains address, city, state and postal code elements. The full structure will be identical to that used in the XML Loan File DTD.

RequesterLoanFileID

· Element Name: RequesterLoanFileID

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the Loan number or other ID for the loan that is used by the requester.

Reference ID

· Element Name: ReferenceID (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): referenceType

· Comment: This optional repeating element can be used for any other reference numbers besides the Loan Number that the

· requester needs to have returned on the credit report. The "referenceType" attribute contains the type description (FHA Loan#, VA Loan#, Agency Loan#, Return File names, etc.).

Service Requested

· Element Name: ServiceRequested

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional repeating element identifies the type(s) of services desired by the requester.

Report Type

· Element Name: ReportType (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12ProductServiceIDType, codeFromVendor

Report Action

· Element Name: ReportAction

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12Action, codeFromVendor

· Comment: This element contains a text description for the type of action requested from the credit vendor – Add (new report), Change (update existing report), Reissue (copy of existing report). The optional attribute is the ANSI X12 code for the action desired. An additional attribute is available for a credit vendor code for the report action. If the action is Change or Reissue, the requester should supply the OriginalReportNum element (contained in ServiceRequested element).

Credit Report Merge Type

· Element Name: CreditReportMergeType

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): X12CreditReportMergeType

· Comment: This optional element contains a text description for the type of trade line merging (Blend, Pick and Choose, List and Stack), if the credit vendor supports selection of the merge type. The optional attribute is the ANSI X12 code for the merge type.

Original Report Number

· Element Name: OriginalReportNum

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element must be filled in with the original Processor's Report Number, when the "ReportAction" element is set to Change (X12ActionCode=2) or Reissue (X12ActionCode=I).

Repositories Requested

· Element Name: RepositoriesRequested

· Element Type: Empty Element (attributes only)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): equifax, experian, transunion

· Comment: The attributes of this optional element tell which repository bureaus data were requested for this report.

Other Service

· Element Name: OtherService

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional repeating element describes additional services requested from the credit vendor. The optional attributes are available for holding a repository and/or credit vendor code for the service

APPLICANT

· Element Name: Applicant (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once, may repeat

· Attribute(s): (none)

· Comment: The Applicant element contains information about the loan applicant such as name, social security number, date of birth, current and previous addresses, landlord information, employment information, etc. The elements contained within the Applicant element are not shown in this document at this time. This structure will be copied from the XML Loan File DTD.

CREDIT LIABILITY

· Element Name: CreditLiability

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): adverseData, consumerDispute, creditRecID, manualUpdate, ownerType

· Comment: This element is a container for the liability elements.

Account Number

· Element Name: AcctNum

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This is the account number assigned by the credit grantor to the applicant’s liability account.

Reference ID

· Element Name: ReferenceID (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): referenceType

· Comment: This optional repeating element can be used to hold a liability counter, a reference number that links credit report liability record and the corresponding liability record from the loan application, or any other reference number needed by the credit vendor or credit requester.

Account Ownership

· Element Name: AcctOwnership (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12TypeOfAcctOwnership, codeFromRepository, repositorySource, codeFromVendor

· Comment: This is element contains a text description for the type of account ownership (Individual, Joint, Joint Contractual, Maker, Participant, etc.). The optional attributes contain various codes for account ownership.

Credit Grantor

· Element Name: CreditGrantor

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the entity that originally opened a credit account for the applicant. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Credit Grantor’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Collection Agency

· Element Name: CollectionAgency

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: If the liability has been turned over to a collection agency, this element contains the Loan File DTD’s “Entity” structure, which holds elements containing the agency’s name, address, phone, contact name, etc. , and the “Credit Grantor” element will contain the name of the original credit grantor.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Account Type

· Element Name: AcctType

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12AcctType, codeFromRepository, repositorySource, codeFromVendor

· Comment: This is element contains a text description for the type of credit account (Credit Line, Mortgage, Installment, Revolving, Open). The optional attributes contain various codes for the account type.

Account Ratings

· Element Name: AcctRatings

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that describe the account’s rating, such as the current rating, highest delinquency rating, most recent delinquency rating, and the applicant’s recent payment pattern for the liability account.

Current Rating

· Element Name: CurrentRating

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12AcctRating, codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional element contains the text description for the current rating. The attributes contain various codes for the rating text.

Highest Delinquency Rating

· Element Name: HighestDelinqRating

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12AcctRating, codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional element contains the text description for the highest delinquency rating. The attributes contain various codes for the rating text.

Most Recent Delinquency Rating

· Element Name: MostRecentDelinqRating

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12AcctRating, codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional element contains the text description for the most recent delinquency rating. The attributes contain various codes for the rating text.

Payment Pattern

· Element Name: PaymentPattern

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): repositorySource, creditRecIDREF01, creditRecIDREF02, creditRecIDREF03, creditRecIDREF04, creditRecIDREF05

· Comment: This element contains payment pattern data elements. The “creditRecIDREF##” attributes identify the individual credit file that supplied the payment pattern. If the liability record supplied by the credit vendor processing the report is a “blend” or “merge” of data from several repository sources, the “repositorySource” attribute will be set to “MergedData”. For these “merged” liability records, credit vendor may sometimes supply multiple “PaymentPattern” data elements - the additional ones being the original payment patterns supplied with each credit variation file.

Payment Pattern Start Date

· Element Name: PaymentPatternStartDate

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element indicates the starting date of the first position in the “PaymentPatternData” element.

Payment Pattern Data

· Element Name: PaymentPatternData

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): codeFromRepository, codeFromVendor

· Comment: This element is a text string containing up to 84 months of account payment history. Each character represents one month's rating. The 1st character represents the rating for the "PaymentPatternStartDate". The 2nd character represents the rating for the month EARLIER than the start date. The 3rd character represents the rating for the next month earlier... and so on. The values below are from the X12 12 "Payment Pattern" Element:

C: Current

1: 30 days past due

2: 60 days past due

3: 90 days past due

4: 120 days past due

5: 150 or more days past due

6: 180 or more days past due

7: Making Payments Under Wage Earner Plan

8: Repossession

9: Bad Debt or Placed for Collection

N: No activity

X: No data received

The default rating codes used for this element are simple numbers that represent the number of months that the account was past at that point in time. In addition, "C" means that the account was "current", "N" represents "no activity", and "X" represents "no rating data" for that particular month. For example, if the "PaymentPatternStartDate" is July of 1999 and the "PaymentPatternData" string is "1121CCCC", this would indicate the following ratings:

Jul 1999 - 1 month past due

Jun 1999 - 1 month past due

May 1999 - 2 months past due

Apr 1999 - 1 month past due

Mar 1999 through Dec 1998 - Current

Loan Type

· Element Name: LoanType

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12LoanType, codeFromRepository, repositorySource, codeFromVendor

· Comment: This is element contains a text description for the type of loan (Auto, Student, FHA, VA, etc.). The optional attributes contain various codes for the loan type.

Liability Dates

· Element Name: LiabilityDates

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that hold various date fields related to the liability record, such as Date Reported, Date Opened, Date Paid, etc.

Date Reported

· Element Name: DateReported (also used in other elements)

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the liability data was reported by the credit grantor.

Date Opened

· Element Name: DateOpened

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date account was opened.

Date Closed

· Element Name: DateClosed

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the account was closed.

Date Paid

· Element Name: DatePaid (also used in other elements)

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the balance was paid to zero.

Date Last Activity

· Element Name: DateLastActivity

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date of last account activity (usually the last payment or charge).

Highest Delinquency Date

· Element Name: HighestDelinqDate

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the account was at its highest delinquency rating.

Most Recent Delinquency Date

· Element Name: MostRecentDelinqDate

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the most recent date the account was delinquent.

Liability Amounts

· Element Name: LiabilityAmts

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that hold various amount fields related to the liability record, such as Current Balance, Monthly Amount, Past Due Amount, etc.

Current Balance

· Element Name: CurrentBalance

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s current balance.

Monthly Payment

· Element Name: MonthlyPayment

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): estimated

· Comment: This optional element contains the account’s monthly payment amount.

Past Due Amount

· Element Name: PastDueAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s current past due amount.

Charge Off Amount

· Element Name: ChargeOffAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s charge off amount (usually an account in collection).

Credit Limit

· Element Name: CreditLimit

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s current credit limit.

High Balance Amount

· Element Name: HighBalanceAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s highest balance amount.

Original Principal Amount

· Element Name: OriginalPrincipalAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s original principal balance.

Balloon Payment Amount

· Element Name: BalloonPaymentAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s balloon payment amount (usually mortgages).

Highest Delinquency Amount

· Element Name: HighestDelinqAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s amount of highest delinquency.

Most Recent Delinquency Amount

· Element Name: MostRecentDelinqAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the account’s most recent delinquent amount.

Monthly Counts

· Element Name: MonthlyCounts

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that hold various monthly count fields, such as Months Remaining, Months Reviewed, # 30 Day Lates, # 60 Day Lates, etc.

Term Months

· Element Name: TermMonths

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the original loan term in months.

Months Remaining

· Element Name: MonthsRemaining

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the months remaining to be paid on the loan.

Months Reviewed

· Element Name: MonthsReviewed

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of months of account history included in the 30, 60, 90 day counts.

Late 30 Days

· Element Name: Late30Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 30 days.

Late 60 Days

· Element Name: Late60Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 60 days.

Late 90 Days

· Element Name: Late90Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 90 days.

Late 120 Days

· Element Name: Late120Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 120 days.

Late 150 Days

· Element Name: Late150Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 150 days.

Late 180 Days

· Element Name: Late180Days

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the number of times the account was delinquent 180 days.

Term

· Element Name: Term

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains a text description for the loan terms (for example, 360 months $400/month).

Collateral

· Element Name: Collateral

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains a text description of any collateral for the loan (for example, 97 Corvette).

Liability Comment

· Element Name: LiabilityComment

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): x12RatingRemarks, codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional repeating element contains a text comment about the liability account. Attributes are available to store repository bureau and/or credit vendor codes for the comment.

Credit Data Source

· Element Name: CreditDataSource (also used in other elements)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): repositorySource, creditRecIDREF01, creditRecIDREF02, creditRecIDREF03, creditRecIDREF04, creditRecIDREF05

· Comment: This optional repeating element contains elements and attributes describing the source of the credit data.

Subscriber Code

· Element Name: SubscriberCode

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the repository vendor’s Subscriber Code (sometimes also called Member ID) assigned to the entity reporting the credit data to the repository vendor.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the liability account.

Verified

· Element Name: Verified (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains an Verified information regarding the parent element record, such as the Verified Date and Verified By name. The full structure will be identical to that used in the XML Loan File DTD.

Original Liability

· Element Name: OriginalLiability (same structure as CreditLiability element)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): adverseData, consumerDispute, ownerType

· Comment: “OriginalLiability” has the same element structure as “CreditLiability”. It is used to store the original repository liability records that were “merged” or “blended” to create the parent “CreditLiability” record.

CREDIT PUBLIC RECORD

· Element Name: CreditPublicRec

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): adverseData, consumerDispute, creditRecID, manualUpdate, ownerType

· Comment: This element is a container for the public record data elements.

Public Record Type

· Element Name: PublicRecType

· Element Type: Text Element (holds data)

· Occurrences: Must appear once

· Attribute(s): x12CaseType, x12PublicRecObligation, codeFromRepository, repositorySource, codeFromVendor

· Comment: This is element contains a text description for the type of public record (Chapter 7 Bankruptcy, County Tax Lien, Foreclosure, etc.). The optional attributes contain various codes for the public record type.

Public Record Disposition

· Element Name: PublicRecDisposition

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12Disposition, codeFromRepository, repositorySource, codeFromVendor

· Comment: This is element contains a text description for the disposition or status of the public record (Filed, Satisfied, Released, etc.). The optional attributes contain various codes for the public record disposition.

Docket Number

· Element Name: DocketNum

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the court docket number for the public record.

Reference ID

· Element Name: ReferenceID (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): referenceType

· Comment: This optional repeating element can be used to hold a liability counter, a reference number that links credit report liability record and the corresponding public record from the loan application, or any other reference number needed by the credit vendor or credit requester.

Account Ownership

· Element Name: AcctOwnership (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12TypeOfAcctOwnership, codeFromRepository, repositorySource, codeFromVendor

Plaintiff

· Element Name: Plaintiff

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Plaintiff. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Plaintiff’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Defendant

· Element Name: Defendant

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Defendant. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Defendant’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Court

· Element Name: Court

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Court. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Court’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Attorney

· Element Name: Attorney

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Attorney. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Attorney’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Garnishee

· Element Name: Garnishee

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Garnishee. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Garnishee’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Alias

· Element Name: Alias

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the Alias. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Alias’ name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Public Record Dates

· Element Name: PublicRecDates

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that hold various date fields related to the public record, such as Date Filed, Date Reported, Date Paid, etc.

Date Filed

· Element Name: DateFiled

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains date the public record was filed.

Date Reported

· Element Name: DateReported (also used in other elements)

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the public record was reported.

Date Paid

· Element Name: DatePaid (also used in other elements)

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the date the balance was paid to zero.

Date Settled

· Element Name: DateSettled

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the settlement date.

Public Record Amounts

· Element Name: PublicRecAmts

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains other elements that hold various amount fields related to the public record, such as Legal Obligation Amount, Bankruptcy Assets, Bankruptcy Liabilities and Judgment Amount..

Legal Obligation Amount

· Element Name: LegalObligationAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): paymentFreq

· Comment: This optional element contains the amount the defendant is obligated to pay. The optional attribute defines the payment schedule (per week, per month, per year or lump sum).

Bankruptcy Assets Amount

· Element Name: BankruptcyAssetsAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the defendant’s assets at the time of bankruptcy.

Bankruptcy Liabilities Amount

· Element Name: BankruptcyLiabilitiesAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the defendant’s liabilities at the time of bankruptcy.

Judgment Amount

· Element Name: JudgmentAmt

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the judgment amount.

Public Record Comment

· Element Name: PublicRecComment

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional repeating element contains a text comment about the public record. Attributes are available to store repository bureau and/or credit vendor codes for the comment.

Credit Data Source

· Element Name: CreditDataSource (also used in other elements)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): repositorySource, creditRecIDREF01, creditRecIDREF02, creditRecIDREF03, creditRecIDREF04, creditRecIDREF05

· Comment: This optional repeating element contains elements and attributes describing the source of the credit data.

Subscriber Code

· Element Name: SubscriberCode

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the repository vendor’s Subscriber Code (sometimes also called Member ID) assigned to the entity reporting the credit data to the repository vendor.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the public record.

Verified

· Element Name: Verified (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This element contains an Verified information regarding the parent element record, such as Date Verified, Verified By Name, and Verified Comment. The full structure will be identical to that used in the XML Loan File DTD.

Original Public Record

· Element Name: OriginalPublicRec (same structure as PublicRec element)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): adverseData, consumerDispute, ownerType

· Comment: “OriginalPublicRec” has the same element structure as “PublicRec”. It is used to store the original repository public records that were “merged” or “blended” to create the parent “PublicRec” record.

CREDIT SCORE

· Element Name: CreditScore (also used in other DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): ownerType, scoreEval

· Comment: The "CreditScore" element contains elements and attributes that assign a "credit risk evaluation" to a credit applicant. The "ScoreModel" is the name of the algorithm model that was used to derive the "ScoreValue". A credit score will usually include one to four "ScoreComment"(s) or credit criteria, which affected the "ScoreValue".

Score Model

· Element Name: ScoreModel

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the name of the score algorithm model used to derive the credit score.

Score Value

· Element Name: ScoreValue

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the credit score. See repository bureau documentation for its meaning.

Score Comment

· Element Name: ScoreComment

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository

· Comment: This optional repeating element contains a text comment about a factor that affected the credit score. The “codeFromRepository” attribute contains the code for the comment.

Credit Data Source

· Element Name: CreditDataSource (also used in other elements)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): repositorySource, creditRecIDREF01, creditRecIDREF02, creditRecIDREF03, creditRecIDREF04, creditRecIDREF05

· Comment: This optional repeating element contains elements and attributes describing the source of the credit data.

Subscriber Code

· Element Name: SubscriberCode

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the repository vendor’s Subscriber Code (sometimes also called Member ID) assigned to the entity reporting the credit data to the repository vendor.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the credit score record.

CREDIT INQUIRY

· Element Name: CreditInquiry

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): creditRecID, ownerType

· Comment: This element is a container for the public record data elements.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

Reference ID

· Element Name: ReferenceID (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): referenceType

Account Ownership

· Element Name: AcctOwnership (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12TypeOfAcctOwnership, codeFromRepository, repositorySource, codeFromVendor

Date Of Inquiry

· Element Name: DateOfInquiry

· Element Type: Date Element (CCYY-MM-DD format)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This required element contains the date of the inquiry by the entity.

Inquiry Result

· Element Name: InquiryResult

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): x12InquiryResults, codeFromRepository, repositorySource, codeFromVendor

· Comment: This optional element contains the text description for the results of the credit inquiry listed. The attributes contain various codes for the results text.

Credit Data Source

· Element Name: CreditDataSource (also used in other elements)

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): repositorySource, creditRecIDREF01, creditRecIDREF02, creditRecIDREF03, creditRecIDREF04, creditRecIDREF05

· Comment: This optional repeating element contains elements and attributes describing the source of the credit data.

Subscriber Code

· Element Name: SubscriberCode

· Element Type: Text Element (holds data)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This optional element contains the repository vendor’s Subscriber Code (sometimes also called Member ID) assigned to the entity reporting the credit data to the repository vendor.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the credit score record.

CREDIT FILE VARIATION

· Element Name: CreditFileVariation

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): ownerType, creditRecID, repositorySource

· Comment: This element is a container for the public record data elements.

Applicant

· Element Name: Applicant (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: The Applicant element contains information from the repository bureau about the loan applicant such as name, social security number, date of birth, current and previous addresses, landlord information, employment information, etc. The elements contained within the Applicant element are not shown in this document at this time. This structure will be copied from the XML Loan File DTD.

Owning Credit Bureau

· Element Name: OwningCreditBureau

· Element Type: Container Element (holds other elements)

· Occurrences: Optional – May appear 0 or 1 time

· Attribute(s): (none)

· Comment: This is the container element for the credit bureau responsible for the credit data supplied with this “credit file variation”. It contains the Loan File DTD’s “Entity” structure, which holds elements containing the Owning Bureau’s name, address, phone, contact name, etc.

Entity

· Element Name: Entity (also used in other elements and DTDs)

· Element Type: Container Element (holds other elements)

· Occurrences: Must appear once

· Attribute(s): (none)

· Comment: This element contains an entity’s name, address, phone, contact name, etc. The full structure will be identical to that used in the XML Loan File DTD.

File Variation Note

· Element Name: Note

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): x12CreditFileVariation

· Comment: Each File Variation Note lists a “variation” between the applicant data sent with the credit request to the repository bureau, and the data returned in an individual credit file (i.e. Last Name, First Name, SSN, etc.). The attribute lists the X12 code value for the file variation.

Consumer Comment

· Element Name: ConsumerComment (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains “consumer comments” returned with this credit file variation from the repository bureau.

Credit Report Alert

· Element Name: CreditReportAlert (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository

· Comment: This optional repeating element contains “credit report alerts” returned with this credit file variation from the repository bureau. “Credit Report Alerts” include special messages about the credit file that need special attention or review such as, “Inquiry address is an answering service”, or “SSN has never been issued”. These messages generally come from Equifax’s “SAFESCAN”, Trans Union’s HAWK ALERT and Experian’s FACS+.

Error Note

· Element Name: ErrorNote (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository

· Comment: This optional repeating element contains error messages returned with this credit file variation from the repository bureau. These error messages generally indicate that there was a problem with the request data, or some other system or computer problem either at the repository bureau or the communications link with the repository bureau. Examples of “Error Notes” are “Invalid Subject Birth Date”, “Invalid Zip Code” or “This area of records temporarily unavailable”.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the credit file variation.

CREDIT REPORT SUMMARY

· Element Name: CreditReportSummary

· Element Type: Container Element (holds other elements)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This element is a container for the credit report summary data elements.

Consumer Comment

· Element Name: ConsumerComment (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains “consumer comments” filed with the credit vendor who processed this credit report. They may have been collected during a consumer interview.

Credit Report Alert

· Element Name: CreditReportAlert (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository

· Comment: This optional repeating element contains “credit report alerts” generated by the credit vendor who processed this credit report. “Credit Report Alerts” include special messages about the credit file that need special attention or review such as, “Inquiry address is an answering service”, or “SSN has never been issued”. These messages are generated as a result of the credit vendor’s own investigation.

Error Note

· Element Name: ErrorNote (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): codeFromRepository

· Comment: This optional repeating element contains error messages generated by the credit vendor who processed this credit report. These error messages generally indicate that there was a problem with the request data, or some other system or computer problem either at the repository bureau or the communications link with the repository bureau. Examples of “Error Notes” are “Invalid Subject Birth Date”, “Invalid Zip Code” or “Credit processing system is down for maintenance upgrade”.

Summary Note

· Element Name: SummaryNote (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains summary notes generated by the credit vendor who processed this credit report. These notes may consist of credit summary totals in a text format, PMI Aura formatted summary, or credit vendor disclaimers.

Note

· Element Name: Note (also used in other elements)

· Element Type: Text Element (holds data)

· Occurrences: Optional Repeating – May appear 0, 1 or any number of times

· Attribute(s): (none)

· Comment: This optional repeating element contains other miscellaneous comments about the credit report.

ATTRIBUTE LIST

Attribute Name	Used In Element	Data Type	Allowed Values	Default Value	Comment
adverseData	CreditLiability, CreditPublicRec	Enum	Yes, No	none	Declares whether or not the data reported with this record is considered adverse.
codeFromRepository	AcctOwnership (Liab, P/R Inq), AcctType, CreditReportAlert (FileVar), CurrentRating, Error Note (FileVar), HighestDelinqRating, InquiryResult, LoanType, LiabilityComment, MostRecentDelinqRating, OtherService, PaymentPatternData, PublicRecDisposition, PublicRecType, ScoreComment	String		none	This is the original code (for the element value) used by the repository bureau (Equifax, Experian or Trans Union) listed in the associated “repositorySource” attribute.
codeFromVendor	AcctOwnership (Liab, P/R Inq), AcctType, CurrentRating, HighestDelinqRating, InquiryResult, LoanType, LiabilityComment, MostRecentDelinqRating, OtherService, PaymentPatternData, PublicRecDisposition, PublicRecType, ReportAction, ReportType (RptHdr, Rqst)	String		none	This is the original code (for the element value) used by the credit vendor that processed the credit report.
consumerDispute	CreditLiability, CreditPublicRec	Enum	Yes, No	none	Declares whether or not the consumer has disputed data reported with this record.
creditRecID	CreditFileVariation, CreditInquiry, CreditLiability, CreditPublicRec	ID		none	Contains a unique ID for each Credit File Variation.
creditRecIDREF01	CreditDataSource (Liab, P/R, Score, Inq), PaymentPattern	IDRef		none	Contains a reference to a “creditRecID” attribute of a “CreditFileVariation” element.
creditRecIDREF02	CreditDataSource (Liab, P/R, Score, Inq), PaymentPattern	IDRef		none	Contains a reference to a “creditRecID” attribute of a “CreditFileVariation” element.
creditRecIDREF03	CreditDataSource (Liab, P/R, Score, Inq), PaymentPattern	IDRef		none	Contains a reference to a “creditRecID” attribute of a “CreditFileVariation” element.
creditRecIDREF04	CreditDataSource (Liab, P/R, Score, Inq), PaymentPattern	IDRef		none	Contains a reference to a “creditRecID” attribute of a “CreditFileVariation” element.
creditRecIDREF05	CreditDataSource (Liab, P/R, Score, Inq), PaymentPattern	IDRef		none	Contains a reference to a “creditRecID” attribute of a “CreditFileVariation” element.
dtdVersion	CreditReport	Enum	0.2	0.2	This REQUIRED attribute assigns a number to a specific version or release of the XML Credit Report structure. As new versions of the structure are released, the new version number will be added to the attributes “Allowed Values”, and will replace the “Default Value”.
Equifax	RepositoriesReturned, RepositoriesRequested	Enum	Yes, No	none	Was Equifax included? (Yes/No).
estimated	MonthlyPayment	Enum	Yes, No	none	Was the amount estimated? (Yes/No). “No” indicates the amount came from the credit grantor and was not calculated.
experian	RepositoriesReturned RepositoriesRequested	Enum	Yes, No	none	Was Experian (TRW) included? (Yes/No).
manualUpdate	CreditLiability, CreditPublicRec	Enum	Yes, No	none	This attribute indicates whether or not any information in the associated data record was updated manually. If set to "Yes", that indicates that the data fields were updated by the credit vendor after it was received from the repository bureau(s).
ownerType	CreditFileVariation, CreditInquiry, CreditLiability, CreditPublicRec, CreditScore	Enum	Borrower, Coborrower, Joint	none
paymentFreq	LegalObligationAmt	Enum	PerWeek, PerMonth, PerYear, LumpSum	none
referenceType	ReferenceID (Rqst, Liab, P/R Inq)	String		none	Describes type of information contained in the “ReferenceID” element.
repositorySource	AcctOwnership (Liab, P/R Inq), AcctType, CreditFileVariation, CreditDataSource (Liab, P/R, Score, Inq), CurrentRating, HighestDelinqRating, InquiryResult, LoanType, LiabilityComment, MostRecentDelinqRating, OtherService, PaymentPattern, PublicRecDisposition, PublicRecType	Enum	Equifax, Experian, TransUnion, MergedData, None, Other	none
scoreEval	CreditScore	Enum	Negative, Positive, NotReported, NotScored, Unscoreable	none
transUnion	RepositoriesReturned RepositoriesRequested	Enum	Yes, No	none	Was Trans Union included? (Yes/No).
x12AcctRating	CurrentRating, HighestDelinqRating, MostRecentDelinqRating	Enum	00, 01, 02, 03, 04, 05, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20	none	Values below are from the X12 263 "Rating Code" Element: 00: Not Used, Too New to Rate, or Unclassified 01: Current or Account Paid According to Terms 02: 30-59 Days Past Due 03: 60-89 Days Past Due 04: 90-119 Days Past Due 05: 120 Days or More Past Due 07: Making Payments Under Wage Earner Plan 08: Repossession 09: Bad Debt Placed for Collection 10: Currently Active 11: Currently Owing 12: Currently Past Due 13: Paid Anticipate 14: Paid Discount 15: Paid in Cash 16: Paid Prompt 17: Paid Slow 18: Placed for Collection Paid 19: Placed for Collection Partially Paid 20: Unfavorable Comments
x12AcctType	AcctType	Enum	C, I, M, O, R	none	Values below are from the X12 1189 "Type of Credit Account Code" Element: C: Credit Line I: Installment M: Mortgage O: Open R: Revolving
x12Action	ReportAction	Enum	1, 2, G, I, T, CV	none	Values below are from the X12 306 "Action Code" Element: 1: Add (New Report) 2: Change (Update - current version of previous Report) G: Cancel Entire Order/Item I: Reissue (Resend opy of original Report) T: Status Query CV: Convert the Report to the Type specified in ReportType Element
x12AmtQualifier	AmtQualifier	Enum	F7, FK, N, T3	none	Values below are from the X12 522 "Amount Qualifier Code" Element: F7: Sales Tax FK: Other Unlisted Amount N: Net T3: Total Submitted Charges
x12CaseType	PublicRecType	Enum	7, 9, 11, 12, 13		Values below are from the X12 1008 "Case Type Code" Element: 7: Bankruptcy Chapter 7 9: Bankruptcy Chapter 9 11: Bankruptcy Chapter 11 12: Bankruptcy Chapter 12 13: Bankruptcy Chapter 13
x12CreditFileVariation	FileVariationNote	Enum	01, 02, 03, 04, 05, 06, ZZ	none	Values below are from the X12 608 "Credit File Variation Code" Element: 01: Different Social Security Number 02: Different Last Name 03: Name Differences 04: Date of Birth Differences 05: Generation 06: Address ZZ: Mutually Defined
x12CreditReportMergeType	CreditReportMergeType	Enum	1, 2, 3, Z	none	Values below are from the X12 612 "Credit Report Merge Type Code" Element: 1: Blend 2: Pick and Choose 3: List and Stack Z: Mutually Defined
x12Disposition	PublicRecDisposition	Enum	01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, ZZ	none	Values below are from the X12 611 "Disposition Code" Element: 01: Satisfied 02: Unsatisfied 03: Released 04: Unreleased 05: Vacated 06: Settled 07: Distributed 08: Unknown 09: Dismissed 10: Discharged 11: Withdrawn 12: Appealed 13: Filed 14: Pending 15: Completed 18: Paid 19: Granted 20: Adjudicated 21: Non-adjudicated 22: Real Estate Sold 23: Paid - Not Satisfied 24: Rescinded 25: Converted 26: Cancelled ZZ: Mutually Defined
x12InquiryResults	InquiryResult	Enum	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11		Values below are from the X12 485 "Results Code" Element: 1: Declined 2: Open Discovered 3: Unknown 4: Did Not Inquire 5: Not a Lender 6: No Open Account 7: Reporting Agency Inquiry 8: Application Pending 9: Open, Account Number Not Issued 10: Account Closed 11: Open, Primary Account
x12LoanType	LoanType	Enum	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 90, 91, 92, 93	none	Values below are from the X12 1262 "Loan Type Code" Element: 1: Subsidized Federal Stafford 2: Federal Supplemental Loans for Students (SLS) 3: Federal PLUS Loan to Parents 4: Unsubsidized Federal Stafford 5: Federal Consolidated Loan 6: Residential Loan 7: Personal Loan 8: Automobile 9: Unsecured 10: Secured 11: Partially Secured 12: Home Improvement 13: FHA Home Improvement 14: Installment Sales Contract 15: Charge Account 16: Real Estate, Specific Type Unknown 17: Secured by Co-signer 18: Business 19: Recreational 20: Educational 21: Lease 22: Co-maker 23: Check Credit or Line of Credit 24: FHA Co-maker (Not Borrower) 25: Mobile Home 26: Credit Card 27: FHA Real Estate Mortgage 28: Note Loan 29: Note Loan with Co-maker 30: Household Good (Secured) 31: Household Goods and Other Collateral Auto 32: Veterans Administration Real Estate Mortgage 33: Conventional Real Estate Mortgage 34: Real Estate Mortgage without Other Collateral 35: Rental Agreement 36: Summary of Accounts with Same Status 37: Unknown Loan Type 38: Debt Counseling Service 39: Employment 40: Combined Credit Plan 41: Debit Card 42: Credit Line - Secured 43: Collection Attorney 44: Insurance Claims 45: Child Support 46: Government Unsecured Guarantee Loan 47: Government Secured Guarantee Loan 48: Government Secured Direct Loan 49: Government Grant 50: Government Overpayment 51: Government Fine 52: Government Fee for Service 53: Government Employee Advance 54: Government Miscellaneous Debt 55: Government Benefit 56: Returned Check 57: Installment Loan 58: Fully Amortized First 59: Balloon First 60: Subordinate Mortgage 61: Home Equity Line of Credit 62: Wrap Around 63: Tax 64: Mortgage 65: Rehabilitation 66: One to Four Servicing 67: Special Service 90: Other 91: Refinance 92: Sale 93: Wholesale
x12ProductServiceIDType	ReportType (RptHdr, Rqst)	Enum	01, 02, 04, 05, 06, 07, 08	none	Values below are from the X12 234 "Product / Service ID Code" Element: 01: Merged Infile (MIF) 02: Residential Mortgage Credit Report (RMCR) 04: MIF with selected Verifieds 05: RMCR - Foreign 06: Non-Traditional 07: RMCR with selected Verifieds 08: Reissue of Report >90 days old
x12PublicRecObligation	PublicRecType	Enum	01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, ZZ		Values below are from the X12 1185 "Public Record or Obligation Code" Element: 01: Foreclosure 02: Law Suit 03: Outstanding Judgment 04: Tax Lien 05: Support Debt 06: Bankruptcy 07: Garnishment 08: Repossession 09: Collection 10: Divorce Decree 11: Custody Agreement 12: Financing Statement (Secured Loan) 13: Lien 14: Non-responsibility 15: Financial Counseling 16: Fictitious Name 17: Notice of Default 18: Forcible Detainer 19: Unlawful Detainer 20: Other Public Record or Obligation Type ZZ: Mutually Defined
x12RatingRemarks	LiabilityComment	Enum	01, 02, 03, 04, 05, 06, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 24, 25, 26, 27, 33, 35, 36, 37, 38, 39, 40, 41, 42	none	Values below are from the X12 650 "Rating Remarks Code" Element: 01: Charge Off 02: Collection Account 03: Foreclosure 04: Involuntary Repossession 05: Repossession 06: Voluntary Repossession 08: Government Claim 09: Paid Account 10: Paid Charge-off 11: Paid Collectio 12: Paid Dealer 13: Paid Foreclosure 14: Paid Not as Agreed 15: Paid Repossession 16: Paid Satisfactory 17: Redeemed Repossession 18: Revolving Account – Current 19: Satisfactory 20: Satisfactory Revolving Account – Current 21: Too New to Rate 22: Unpaid Collection 24: Closed Not Paid 25: Insurance Claim 26: Partially Paid 27: Account Included in Bankruptcy 33: As Agreed 35: No Status 36: Not Paid as Agreed 37: Past Due 38: Settled 39: Unpaid 40: Card Lost 41: Account in Dispute 42: Bad Debt
x12TypeOfAcctOwnership	AcctOwnership (Liab, P/R Inq)	Enum	01, 02, 08, 09, 10, 12, 16, 18, 19, 20, 21	none	Values below are from the X12 1187 "Type Of Account Code" Element: 01: Sole (Individual) 02: Joint Ownership or Obligation in Severalty 08: Authorized User 09: On Behalf Of 10: Terminated 12: Undesignated 16: Joint Contractual Liability 18: Nonapplicant Spouse 19: Participant 20: Maker (With Co-maker) 21: Co-maker

TABLE OF CONTENTS

INTRODUCTION

REPORT HEADER

Processor Report Number

Report Date-Time

Report Processor

Entity

Report Type

Repositories Returned

Amount

Amount Qualifier

Request Submitter

Processor Account Number

Entity

Processor Account Number

Entity

Processor Account Number

Entity

Location

Reference ID

Service Requested

Report Type

Report Action

Credit Report Merge Type

Original Report Number

Repositories Requested

Other Service

APPLICANT

CREDIT LIABILITY

Account Number

Account Ownership

Entity

Entity

Account Type

Account Ratings

Current Rating

Highest Delinquency Rating

Most Recent Delinquency Rating

Payment Pattern

Payment Pattern Start Date

Payment Pattern Data

Loan Type

Date Reported

Date Opened

Date Closed

Date Paid

Date Last Activity

Highest Delinquency Date

Most Recent Delinquency Date

Liability Amounts

Current Balance

Monthly Payment

Past Due Amount

Charge Off Amount

Credit Limit

High Balance Amount

Original Principal Amount

Balloon Payment Amount

Highest Delinquency Amount

Most Recent Delinquency Amount

Term Months

Months Remaining

Months Reviewed

Late 30 Days

Late 60 Days

Late 90 Days

Late 120 Days

Late 150 Days

Late 180 Days

Collateral

Liability Comment

Credit Data Source

Subscriber Code

CREDIT PUBLIC RECORD

Public Record Type

Public Record Disposition

Reference ID

Account Ownership

Entity

Entity