US20040225596A1 - System and method for facilitating delivery of a loan to a secondary mortgage market purchaser - Google Patents

System and method for facilitating delivery of a loan to a secondary mortgage market purchaser Download PDF

Info

Publication number
US20040225596A1
US20040225596A1 US10/738,518 US73851803A US2004225596A1 US 20040225596 A1 US20040225596 A1 US 20040225596A1 US 73851803 A US73851803 A US 73851803A US 2004225596 A1 US2004225596 A1 US 2004225596A1
Authority
US
United States
Prior art keywords
loan
logic
data
delivery
underwriting
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/738,518
Inventor
John Kemper
David Coleman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fannie Mae Inc
Original Assignee
Fannie Mae Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fannie Mae Inc filed Critical Fannie Mae Inc
Priority to US10/738,518 priority Critical patent/US20040225596A1/en
Assigned to FANNIE MAE reassignment FANNIE MAE ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COLEMAN, DAVID A., KEMPER, JOHN L.
Publication of US20040225596A1 publication Critical patent/US20040225596A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283Price estimation or determination
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof

Definitions

  • This invention relates generally to computer systems and methods used to process data pertaining to financial assets, such as loans, securities, etc. and more particularly to facilitating delivery of a loan to a secondary mortgage market purchaser.
  • the lender can: (i) hold the loan as an investment in its portfolio; or (ii) sell the loan to investors in the “secondary mortgage market” (e.g., pension funds, insurance companies, securities dealers, financial institutions and various other investors) to replenish its supply of funds.
  • the loan may be sold alone, or in packages of other similar loans, for cash or in exchange for mortgage backed securities which provide lenders with a liquid asset to hold or sell to the secondary market.
  • lenders By choosing to sell its mortgage loans to the secondary mortgage market for cash, or by selling the mortgage backed securities, lenders get a new supply of funds to make more home mortgage loans, thereby assuring home buyers a continual supply of mortgage credit.
  • loans originated by a lender are typically underwritten before being closed or prior to delivery (i.e. sale) to a purchaser in the secondary mortgage market.
  • Underwriting provides a recommendation whether the loan meets the credit risk and eligibility requirements of a lender for the purposes of its portfolio or a secondary mortgage market purchaser based on a set of loan information provided by the lender.
  • the set of loan information may change between underwriting and closing and delivery of the loan (e.g., through continued negotiations between the borrower and lender).
  • the changes to the set of loan information may affect the underwriting decision, the decision whether to purchase the loan, as well as the price for the sale of the loan.
  • a purchaser is only able to determine differences between the set of loan information used for underwriting and the set of loan information for the delivered loan after the loan has been delivered and the sale transaction completed. If there are any yield adjustments due to differences in the set of loan information, the purchaser is faced with requesting such yield adjustments from the seller after the sale is complete, often after a significant lapse of time.
  • a method for facilitating delivery of a loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan and an identifier includes providing a delivery template to a seller of the loan to receive delivery data for the loan; retrieving the underwriting data associated with the identifier upon receiving a request from the seller including the identifier and populating the delivery template with the predetermined set of information.
  • a system for facilitating delivery of a loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan and an identifier includes means for providing a delivery template to a seller of the loan to receive delivery data for the loan, means for receiving a request from the seller including the identifier, means for retrieving the underwriting data associated with the identifier and means for populating the delivery template with the predetermined set of information.
  • a system for delivering a loan to a purchaser where the loan has a set of underwriting data provided by underwriting logic includes a user interface for providing a delivery template to the seller of the loan and for receiving delivery data for the loan and delivery logic, coupled to the user interface, for processing the delivery data for the loan.
  • the underwriting data includes a predetermined set of information relevant to the delivery of the loan and has an identifier generated by the underwriting logic.
  • the delivery logic retrieves the underwriting data associated with the identifier and populates the delivery template with the predetermined set of information.
  • FIG. 1 is a block diagram of a data processing system according to one preferred embodiment.
  • FIG. 2 is a block diagram showing user services logic of the system of FIG. 1 in greater detail.
  • FIGS. 3A and 3B are block diagrams showing underwriting logic, acquisition logic, servicer and investor reporting logic, and securitization logic of the system of FIG. 1 in greater detail.
  • FIG. 4 is a block diagram of the underwriting logic and delivery logic of the system shown FIGS. 1 and 3A.
  • FIG. 5 illustrates a comparison process for the comparison logic of FIG. 4.
  • FIG. 6 is a block diagram showing common services logic of FIG. 1 in greater detail.
  • the system 10 comprises a data processing system 12 , user systems 14 , bulk data systems 16 , and other data interfaces 18 .
  • the data processing system 12 further comprises user services logic 22 , a transaction exchange processor 24 , underwriting logic 26 , acquisition logic 28 , servicer and investor reporting logic 30 , securitization logic 32 , common services logic 34 , a data storage system 38 , and other data interfaces 18 .
  • logic is used in connection with some blocks and the term “processor” is used in connection with other blocks, these two terms are used interchangeably.
  • the term “processor” is used in the generic sense and is not meant to imply a separate discrete unit of processing hardware.
  • the data processing system 12 is configured for processing data pertaining to financial assets, such as loans and securities.
  • the data processing system 12 is configured to be used by a participant in the secondary mortgage market.
  • the participant is referred to as a “purchaser,” although it should be understood that the participant may participate in the secondary market in other, different, or additional ways (e.g., as a loan guarantor, as a loan securitizer, and so on).
  • the data processing system 12 is preferably useable to support various types of transactions which may be executed by such a purchaser in connection with one or more loans.
  • the purchaser may purchase loans from lenders or other loan originators as part of a cash execution.
  • the purchased loans may, for example, be held as investments in the purchaser's investment portfolio.
  • the purchaser may create mortgage backed securities (MBS) as part of an MBS execution, or create other financial instruments or assets that are collateralized by cash flows associated with individual loans, including both loans that have been purchased by the purchaser and other loans that have not been purchased by the purchaser.
  • MBS mortgage backed securities
  • the purchaser may acquire a pool of loans, securitize the pool of loans to create MBS that is then sold to investors, and hold the pool of loans in trust for the benefit of the investors.
  • the purchaser may also receive a fee for guaranteeing to holders of MBS or other financial instruments the repayment of the loans by borrowers.
  • the purchaser may also use loans to create other types of financial assets or instruments, for example, by purchasing loans and selling the financial instruments to investors, or by performing such services for other owners of loan assets.
  • the acquisition logic 28 is preferably useable to perform such operations as receiving information such as loan term, interest rate, principal owed, and other parameters regarding loans when loans are first purchased or otherwise acquired and entered into the data processing system 12 . In the case of cash executions, the acquisition logic 28 is also used to perform such operations as receiving commitments for the purchased loans.
  • the servicer and investor reporting logic 30 is used to process periodic loan data for loan accounting purposes and generate accounting output in connection with the purchased loans.
  • the terms “reporting logic” and “servicer and investor reporting logic” are used interchangeably and both refer to logic that is configured to perform loan accounting and generate accounting output (e.g., for purposes of investor reporting, for purposes of managing a loan portfolio, and so on) in connection with a plurality of loans.
  • the servicer and investor reporting logic 30 preferably performs such functions as receiving loan payment data on an ongoing basis from third party servicers.
  • the servicer and investor reporting logic 30 in the illustrated embodiment is not used for servicing loans directly but rather interfaces with a third party servicer.
  • the servicer and investor reporting logic 30 could also be configured to include additional logic for servicing loans, either as part of the servicer and investor reporting logic 30 or as part of another functional block.
  • the accounting output generated by the servicer and investor reporting logic 30 may include such things as accounting, tax, performance/valuation, and/or other relevant financial information for the loans retained in the portfolio or sold, in whole or in part.
  • the securitization logic 32 is used to generate financial assets.
  • financial asset generation logic and “securitization logic” are used interchangeably and refer to any logic that is used to generate/create financial assets.
  • financial asset is used to generically to refer to any asset that is backed by one or more cash flows, and includes such things as assets that are created entirely for internal data tracking purposes (e.g., in the case of packets which do not represent securities), as well as assets that have external significance (e.g., in the case of MBS or other security).
  • the securitization logic 32 may be used to generate financial assets such as MBS or assets that are tracked internally in situations where the owner/operator of the data processing system 12 purchases a pool of loans and holds the loans as an investment in its own portfolio.
  • the data processing system 12 may perform fewer or additional functions as compared to those described herein.
  • an entity that performs only some of the above-mentioned processes may use a computer system that contains only a subset of the functions described herein.
  • the data processing system 12 is used to support each of the business processes described above.
  • Access can include data flow into and out of system 12 .
  • a first access point into the data processing system 12 is the user services logic 22 which provides entry to the user system 14 .
  • a preferred implementation of the user services logic 22 is described in greater detail below in connection with FIG. 2.
  • the user systems 14 are assumed to be operated by human users that participate in some way in the above mentioned business processes.
  • the human user may be an employee of a lender or other loan originator that uploads loan information to the purchaser (or corrects, updates, and so on, information that has previously been provided) in connection with committing to deliver or actually delivering a group of loans to the purchaser, an employee of an owner of a portfolio of loans that uploads loan information in connection with a group of loans the owner wishes to have securitized by the purchaser, an employee of a servicer that uploads payment information regarding a group of loans serviced by the servicer, an employee of an institutional investor that downloads information regarding the financial performance or other data regarding investment instruments created and maintained by the purchaser, an employee of the purchaser itself, and so on.
  • a lender or other loan originator that uploads loan information to the purchaser (or corrects, updates, and so on, information that has previously been provided) in connection with committing to deliver or actually delivering a group of loans to the purchaser
  • an employee of an owner of a portfolio of loans that uploads loan information in connection with a group of loans the owner wishes to have securitized by the
  • a second access point into the data processing system 12 is the transaction exchange processor 24 which provides entry to the bulk data systems 16 .
  • the transaction exchange processor provides an alternative, bulk transfer mechanism for exchanging at least some of the transaction-related data mentioned above in connection with the user systems 14 , typically without intervention of a human operator. Such bulk data transfers may occur with lenders, servicers and so on.
  • the transaction exchange processor 24 receives/sends transactions, and prescreens/sorts/translates data is needed, and makes the transactions/data available for further processing in the data processing system 12 or outbound transmission.
  • a third access point into the data processing system 12 is through the data interfaces 18 .
  • the data interfaces 18 may be used to exchange other types of data between other computer systems and the data processing system 12 .
  • the data interfaces 18 may be used, to import or export data to other external computer systems (that is, computer systems not under the control of the purchaser) or other internal computer systems (e.g., computer systems that are under the control of the purchaser but that provide functionality that is not integrated into the data processing system 12 ).
  • other external computer systems that is, computer systems not under the control of the purchaser
  • other internal computer systems e.g., computer systems that are under the control of the purchaser but that provide functionality that is not integrated into the data processing system 12 .
  • the data processing system 12 is described in greater detail below in connection with FIGS. 2-6. As will become apparent from the discussion below, the preferred data processing system 12 exhibits a high level of data, service and time granularity. With respect to data granularity, the system 12 is capable of decomposing loans into a series of highly granular cash flows and tracking all of the cash flows from the point the cash flows enter the data processing system 12 (e.g., as part of a loan payment or other cash flow source) to the point the cash flows exit the data processing system 12 (e.g., as part of a payment on a financial instrument).
  • the data processing system 12 e.g., as part of a loan payment or other cash flow source
  • the decomposition of a particular loan into sub-loan cash flows may occur when the loan is first acquired, later when servicing activity begins on the loan, or at another time.
  • the allocation of the loan payment into individual cash flows may be performed by logic executed by the servicer, by the data processing system 12 , or by other logic.
  • all or nearly all of the cash flow sources associated with a particular loan can be identified and tracked.
  • the data processing system 12 not only decomposes and maps cash flows associated with such things as principal and borrower paid interest, but also sub-loan level cash flows arising in association with the borrower paid interest or fees associated with the loan such as servicing fees, guarantee fees, mortgage insurance, prepayment penalties, borrower-paid fees, servicer advances, servicer recoveries, and loss/default components, and provides other flexibility. Additional description regarding exemplary possible sources of cash flows is provided at the end of this section.
  • the data processing system 12 represents loans as a series of attributes and uses a business rules engine to process loan information. This dramatically simplifies the process of expanding the capabilities of the data processing system 12 to process data associated with any type of loan.
  • the capability to process a new type of loan may be added by adding an additional attribute to a list of attributes corresponding to the new product feature (or modifying existing attributes), by using the attribute to indicate the presence or absence (and/or other characteristics) of the new feature in a particular loan, and by modifying the rules engine to incorporate additional rules regarding the new loan feature. It is not necessary to build a completely new data processing system for the new type of loan. This makes it easier to offer new types of loans which are more optimally configured to meet the needs of individual borrowers. An exemplary set of attributes is described at the end of this section.
  • the data processing system 12 is capable of processing data using a much smaller time slice or update period than has been possible in the past.
  • systems have typically been constructed around the assumption that servicers provide monthly reports which summarize loan activity that occurred during the previous month.
  • the time slice for reporting has been one month and sub-monthly temporal data has been lost.
  • this information preferably includes information regarding the date the loan was acquired, the date or dates within each month or other period other period on which a payment or other transaction is expected, and/or the date the payment was received.
  • the time slice in the data processing system 12 is therefore one day (or less, if a smaller time slice such as AM/PM, hour, minutes, seconds, and so on, is used).
  • the temporal information is stored and maintained in databases which are synchronized/commonly accessible by the acquisition logic 28 , the servicer and investor reporting logic 30 , and the securitization logic 32 .
  • the acquisition logic 28 , the servicer and investor reporting logic 30 , and the securitization logic 32 each have access to this highly granular temporal information regarding loan acquisitions and payments.
  • the increased time granularity supports the above-mentioned capabilities to offer a wider array of loans to borrowers and a wider array of financial instruments to investors.
  • the increased time granularity facilitates offering loan products in which the borrower is expected to make bi-weekly payments, which may be attractive to borrowers that get paid bi-weekly instead of twice-monthly or monthly. This also facilitates handling loan products in which the date of a transaction is meaningful, such as daily simple interest loans. Further, because sub-loan cash flows can be processed using a one day time slice (or less), it is possible to create financial instruments based on cash flows that are processed on a per day basis.
  • each system has an up to date view of the data.
  • the data processing system 12 has the ability to accept payment and other transaction information from a servicer as such transactions occur (e.g., using daily, hourly, or near real-time updates) instead of or in addition to receiving end of the month summary transaction information from the servicer.
  • FIGS. 1-6 It should be apparent that it is also possible to construct data processing systems which do not incorporate the advantages described herein in connection with the data processing system 12 , or which also incorporate additional advantages not described herein. Further, it may also be noted that the separation of functionality shown in FIGS. 1-6 is necessarily to some extent conceptual, and it is also possible to provide the same functionality in other ways. Additionally, although numerous functions are described below, it may be noted that it may be desirable to provide fewer, additional, or different functions in a given data processing system depending on the application and what is needed.
  • the user services logic 22 includes electronic registration logic 50 , access and security logic 52 , user experience logic 54 , report request processing logic 62 , and a notification processor 64 .
  • the registration logic 50 is used to register individual users to be able to use the data processing system 12 . For example, an employee of a lender may be given a login name and password to access the data processing system 12 .
  • User registration preferably includes providing each user with an authorization profile that defines the extent and type of access the user is given to the data processing system 12 and the types of operations that the user may perform while accessing the data processing system 12 .
  • the access and security logic 52 cooperates with the electronic registration logic 50 to permit users to access the data processing system 12 in the manner authorized.
  • the user experience logic 54 provides a user interface to the data processing system 12 .
  • the user accesses the data processing system 12 through the Internet or an Intranet by using a personal/laptop computer or other suitable Internet-enabled device.
  • the data processing system 12 may be accessible to users by visiting the purchaser's web site (that is, the web site of the entity that owns/operates the data processing system 12 , and that is assumed to be in the business of purchasing, guaranteeing, and/or securitizing loans) and clicking on appropriate links located at the web site.
  • the user is able to access different web pages of the web site relating to the underwriting logic 26 , the acquisition logic 28 , the servicer and investor reporting logic 30 , and the securitization logic 32 .
  • the user may then perform functions in accordance with what is permitted by the user's authorization profile (which, in turn, is typically based on the user's employer and the user's job function for that employer).
  • an employee of a lender may be given authorization to access web pages associated with the acquisition logic 28 and commit the lender to deliver a quantity of loans on a future date (i.e., to engage in a forward commitment with the purchaser).
  • a future date i.e., to engage in a forward commitment with the purchaser.
  • the user experience logic 54 includes business application components 56 , reference data 58 , and user help logic 60 . These components provide implementation support to the above-described user interface.
  • the business application components 56 includes logic that assists directing a user to the correct web page.
  • the reference data 58 may include data regarding user preferences for the appearance of web pages to the user.
  • the reference data 58 may also provide general reference data and content that assists user interaction with the web site.
  • the reference data 58 may also include data regarding particular lenders, such as the year the lender was first approved to do business with the purchaser, contact information for the lender, and performance information such as statistics and transfer history for the lender.
  • the user help logic 60 provides other help or “How To” components.
  • the user services logic 22 also includes report request processing logic 62 and a notification processor 64 .
  • the report request processing logic 62 permits lenders and servicers to access the data processing system 12 and request reports generated from the data the lenders and servicers have provided the purchaser.
  • the reports may be redefined “canned” reports, or may be ad hoc reports defined by the user by drilling down into the data and/or defining data filters. the type of reporting generation capability available may be made dependent on the type of user.
  • the report request processing logic 62 may be used for incoming data in connection with lenders and servicers and/or for outgoing data in connection with investor reporting. Investor reporting may also be handled by other logic described below.
  • the notification processor 64 sends notifications/alerts to users.
  • the notification processor 64 may be used to send e-mail (or fax, automated telephone call, and so on) to a user associated with a servicer or lender indicating that data which has been submitted by the servicer or lender has been processed, and that the processed data is ready for review.
  • the notification processor 64 is useful in the context of exceptions processing, when the lender/servicer data is processed but the processing indicates that there may be an error in the lender's/servicer's data which requires review by a human operator.
  • the underwriting logic 26 is typically accessed by users that originate loans, such as lenders and brokers.
  • the underwriting logic 26 includes data capture logic 70 , underwriting logic 74 , and credit scoring logic 72 .
  • the data capture logic 70 is used to receive information to be used in loan underwriting and appraisal (e.g. information from a loan application and a credit report).
  • the information that is received for loan underwriting is a subset of the information that would be provided on a loan application.
  • the credit scoring logic 72 and the underwriting logic 74 cooperate to analyze the information to determine if the loan meets credit risk and eligibility requirements of the purchaser or of a lender for the purposes of its portfolio, and then issue a recommendation based on the assessment of the overall risk profile of the loan.
  • the credit scoring logic 72 generates a credit score of the loan applicant based on the loan applicant's credit history. For example, a credit report for the potential borrower may be obtained once the lender obtains authorization from the potential borrower.
  • Underwriting logic 74 combines the credit score with other information provided by the potential borrower to the lender to recommend whether to approve the loan. Such information may include, for example, one or more of the following: debt-to income ratios, appraisal value, income, borrower contribution, cash reserves of the borrower, loan-to-value ratio, loan purpose, loan term, loan type, property type, occupancy status and amount of subordinate financing, and other factors. Underwriting logic 74 stores the credit score and the other information and assigns a unique underwriting casefile ID to the lender and loan application for the particular borrower. The recommendation provided by the underwriting logic 74 indicates whether the loan meets the purchaser's credit risk and eligibility requirements.
  • the recommendation provides a message such as (1) “approved” or (2) “refer to help center” or like message regarding whether the loan meets the credit risk requirements.
  • Underwriting logic 74 may also provide a message such as (1) “eligible” or (2) “ineligible” regarding whether the loan product meets the purchaser's eligibility requirements.
  • the underwriting logic 74 also preferably indicates (i) minimum income and asset verification requirements, (ii) credit related documentation requirements, and (iii) the required level of property field work necessary to complete the processing of the loan file.
  • the underwriting logic 74 may produce the verification and approval requirements for referred loans as well as for loans recommended for approval.
  • the underwriting logic 74 may also provide the lender with information identifying problem areas with respect to the borrower's application and suggested areas for improving the borrower's chances for approval (e.g., lower loan amount or reduce debt).
  • the lender may refer the borrower to a help center to receive the benefit of such information and recommendations.
  • the recommendation provided by the underwriting logic 74 is stored with the associated data provided by the lender and borrower (hereinafter, the credit score, other information and the underwriting recommendation are referred to as “underwriting data”).
  • the underwriting data may be stored in, for example, a database.
  • a lender may resubmit a loan for underwriting (e.g., if property, loan or borrower information changes).
  • the underwriting data (including the underwriting recommendation and verification requirements) is updated to include the data from the most recent submission.
  • the information received and generated by underwriting logic 26 is preferably available to the other sub-components of the data processing system 12 as discussed in further detail below with respect to FIGS. 4 and 5.
  • the underwriting logic 26 may also be used to generate reports that provide information regarding the underwriting recommendation for a particular loan, information used in determining the recommendation (e.g., property, loan, and borrower information), and information summarizing key statistics from the credit report (e.g., borrower's open accounts, derogatory accounts and undisclosed accounts).
  • information used in determining the recommendation e.g., property, loan, and borrower information
  • information summarizing key statistics from the credit report e.g., borrower's open accounts, derogatory accounts and undisclosed accounts.
  • the acquisition logic 28 further includes cash committing logic 80 , deal management logic 82 , lender eligibility logic 84 , pricing logic 86 , delivery logic 88 , certification logic 90 , and custody logic 92 .
  • the cash committing logic 80 provides a facility for performing all cash commitment functions.
  • a master agreement/contract may be in place between the purchaser and the lender which defines overall terms of loan sales to the purchaser pursuant to particular commitments.
  • a cash commitment is an agreement (typically, governed by the overall master agreement) in which the mortgage purchaser agrees to buy mortgages from mortgage sellers (e.g., lenders) in exchange for a specified price in cash.
  • a cash commitment agreement specifies the type of mortgage(s) the seller plans to deliver, the amount of time the seller has to make a delivery, the price the mortgage purchaser will pay the seller for the loan(s), other pertinent loan terms, and, in some cases, loan level details pertaining to the mortgage.
  • the cash committing logic 80 provides a central point for approved lenders (or other approved sellers) and the purchaser to perform all cash commitment functions. These functions may include, for, example, making standard forward commitments, handling pair-off of commitments, extending commitments, over-delivering of a commitment, maintaining configurable parameters, updating contact information, updating commitment records, viewing and selecting from a seller's favorite product list, adding to and maintaining the seller's favorite product list, viewing contracts, fees, prices, yield adjustments, and so on.
  • the access and security logic 52 verifies the identity of the user (using a login ID and password) and allows the user to gain access to the cash committing logic 80 . Different types of users may be granted different levels of access to the cash commitment logic 80 (e.g., for different employees within a seller organization having different levels of authority to act on behalf of the seller).
  • the system 12 includes the ability to limit the different types of loans that a given seller may sell to a subset of the loans which the purchaser may purchase.
  • the different products may comprise loans of different terms, different interest rates and types of interest rates (fixed or variable), as well as a variety of other features or combinations of features that may be offered in connection with the particular mortgage products.
  • This information may be stored in the lender eligibility logic 84 , described below, and the cash committing logic 80 may interface with the lender eligibility logic 84 to limit commitment activity to only those products that the seller is eligible to sell. During the committing process, the seller selects the type of product the seller plans to deliver from a list of eligible products.
  • Sellers may be provided the ability to flag any eligible product as a “favorite,” and are able to select products from a favorites list when making commitments. Preferably, sellers are also provided with the option to assign their own marketing name for each eligible product in the seller's favorite list. In another embodiment, rather than selecting from a list of eligible products, sellers may be provided the ability to define a product they plan to deliver by defining the loan attributes.
  • the committing logic 80 provides sellers with the option to apply a commitment to a master agreement.
  • Information regarding master agreements is supplied by the deal management logic 82 and displayed in the cash committing logic 80 for a given seller.
  • the display may, for example, indicate valid master agreement numbers, the unfulfilled commitment amount in dollars for each master agreement, the expiration date for each master agreement, and/or other pertinent information.
  • the deal management logic 82 is used to store and track terms of the deals/contracts made between sellers of loans and the purchaser. When a seller contacts the purchaser to initiate negotiation of a new deal, an employee or other representative of the purchaser uses the deal management logic 82 to create a master agreement, MBS pool contract and all the associated variances.
  • the deal management logic 82 enables authorized users creating or modifying variances to identify editable variances and facilitates transforming “codeable” variances into business rules in the delivery logic.
  • the deal management logic 82 also facilitates communication of these variances to users responsible for analyzing them. Users responsible for analyzing variances are provided a link to the edit engine where they are able to add, modify, or delete edits based on their analyses.
  • the deal management logic 82 also integrates with the pricing logic 86 so that loan level yield adjustments that reflect negotiated variances may be entered and displayed in the generated master agreement.
  • the seller's specific adjustment tables (referencing master agreement and variance reference numbers) may also be stored in the deal management logic, or, more preferably, in the lender eligibility logic 84 .
  • the lender eligibility logic 84 is logic that maintains information regarding the eligibility of particular lenders to offer particular products made available by the purchaser.
  • the lender eligibility logic 84 allows users (via web interface) to maintain and update product or lender-specific parameters in connection with the committing logic 80 , the delivery logic 88 , the certification logic 90 , the custody logic 92 , and the servicer and investor reporting logic 30 .
  • the lender eligibility logic 84 may also be used to set pricing incentive adjustments, yield adjustments, fees and other parameters at the lender and product levels.
  • the pricing logic 86 is the logic used to generate pricing information and provide information to other logic in the data processing system 12 , including the underwriting logic 26 , the committing logic 80 , the delivery logic 88 , the certification logic 90 , the custody logic 92 , and the servicer and investor reporting logic 30 .
  • the pricing logic 86 may be accessed during delivery to determine the price to be paid for a particular loan, or after the loan is delivered to determine how changes/corrections in loan information affect pricing.
  • the pricing logic 86 takes into account pricing elements such as commitment/interest price (based on interest and the type of commitment), commitment calculations (e.g., for yield adjustments associated with pair-offs, over delivery, extensions), and credit adjustment price (based on loan level credit risk).
  • the pricing logic 86 may also be used for MBS pricing (i.e., pricing in situations where the loan is paid for using a mortgage backed security).
  • the pricing elements related to MBS includes the guarantee fee, the buy-up/buy-down amount and the credit adjustment amount.
  • the pricing logic 86 interacts with the delivery logic 88 (described in greater detail below) when a seller is unable to fulfill the terms of its original commitment to generate yield adjustments associated with pair-offs, over delivery, and extensions.
  • the pricing logic 86 acquires delivery and under delivery tolerance amounts from the lender eligibility logic 84 , processes data from a commitment inventory database to locate expired commitments and under deliveries, based on input from the delivery logic 88 .
  • the pricing logic 86 also processes data associated with the original commitment parameters to generate yield adjustments. Additionally, yield adjustments may also be assessed at the time of delivery for credit risk in connection with one or more loans that exceeds a pre-determined and agreed-upon level.
  • a certain level of credit risk is assumed when determining the cash price or MBS guarantee fee. Later, when loans are actually delivered, the true risk level is identified. If the cash price or MBS guarantee fee does not account for this actual level of risk, a yield adjustment is made.
  • the system allows the option of selecting either an upfront loan level yield adjustment at the time of delivery or a guarantee fee basis point adjustment to permit the payment to be made over time.
  • the pricing logic 86 also interacts with the servicer and investor reporting logic 30 when there are loan level changes during the servicing of the loan that result in a request for pricing.
  • the servicing logic 142 sends the pertinent data attributes needed for pricing to the pricing logic 86 and the pricing logic 86 returns pricing information for the loan in question.
  • the pricing logic 86 may also be used to access prices set forth in pricing grids that store pricing information as a function of various loan parameters and/or features, e.g., interest rate and remaining term in connection with a particular seller.
  • the pricing grids may be generated manually (e.g., in a spreadsheet which is provided to the pricing logic 86 ) or automatically.
  • the pricing logic 86 may also be used to generate reports regarding pricing information.
  • the delivery logic 88 is the logic used to process loans when loans are delivered to the purchaser in connection with a purchase.
  • the delivery logic 88 analyzes loan attributes, the associated deal/contract with the seller, and execution parameters to determine if the loan is acceptable for submission under the terms and conditions of the deal.
  • the delivery logic 88 also invokes the pricing logic 86 to determine the price and/or yield adjustment associated with accepting the loan.
  • the delivery logic 88 also allows sellers to set up pools in cases where the loans are pooled in MBS.
  • the delivery logic 88 receives electronic loan data (hereinafter referred to as “delivery data”) by way of the users services logic 22 or the transaction exchange processor 24 .
  • delivery data electronic loan data
  • the purchaser will generally also receive paper loan documents that support the electronic loan data received by the data processing system 12 .
  • the delivery logic 88 utilizes aspects of the underwriting logic 26 , the deal management logic 82 , and the pricing logic 86 .
  • Each loan that is delivered is checked against business rules and data format rules.
  • Business rules are based on the product, pool/piece/contract, pricing, commitment, and other factors. For example, a seller may inadvertently try to deliver a 15-yr loan in connection with a commitment for 30-yr loans, and the business rules provide a mechanism for identifying that the 15-yr loan can not be used to satisfy that commitment.
  • the delivery logic 88 uses the notification processor 64 to notify the seller when/if the data that is being delivered does not match the commitment.
  • the delivery logic 88 is also integrated with the underwriting logic 26 .
  • FIG. 4 shows a block diagram of the delivery logic and underwriting logic of the system of FIGS. 1 and 3A.
  • underwriting data including the underwriting recommendation) for a particular loan is assigned an underwriting casefile ID and may be stored in a database 406 .
  • the delivery loan data for a particular loan to be delivered may be assigned a unique loan ID and stored in a database 406 .
  • Delivery logic 88 and underwriting logic 26 preferably communicate to share data to perform various functions, such as (i) populate a loan delivery template of the delivery logic 88 , (ii) confirm that the loan being delivered meets underwriting criteria, and/or (iii) determine if the delivery data for a loan that was also underwritten using underwriting logic 26 is the same as the underwriting data provided for the loan.
  • the underwriting data transferred may include one or more of the following: borrower social security number, co-borrower social security number (if applicable), property address, loan amortization type, loan guarantor type, number of units, loan processing method, employment information, loan type, underwriting results, loan term, LTV, CLTV, borrower reserves, and so on.
  • the underwriting data may be used to populate a delivery template presented to a seller delivering the loan by, for example, a web interface.
  • the underwriting data is identified (e.g. italicized or shaded) so the seller can identify the data obtained from the underwriting logic 26 .
  • the seller therefore, does not have to reenter loan data previously entered during the underwriting process.
  • the seller can review the underwriting data to ensure that it is accurate.
  • the seller preferably, can edit or update the underwriting data, if necessary.
  • the underwriting data may be edited by way of a computer system with a user interface to receive inputs regarding the underwriting data.
  • a seller does not provide an underwriting casefile ID or if the loan being delivered was not underwritten using underwriting logic 26 , the seller will have to enter all of the loan data required for delivery of the loan.
  • the seller may enter the loan data using, for example, a keyboard or other input device in conjunction with a computer system.
  • delivery logic 88 may interact with underwriting logic 26 to confirm the loan being delivered meets the underwriting criteria of the purchaser.
  • Delivery logic 88 may transfer delivery data provided by the seller at delivery to the underwriting logic 26 .
  • Underwriting logic 26 will then process the delivery data relevant to providing an underwriting recommendation, as described above, to provide an underwriting recommendation.
  • Underwriting logic 26 then returns underwriting data (including the underwriting recommendation) to the delivery logic 88 .
  • the underwriting data and, in particular, the underwriting recommendation may be provided to the seller using notification processor 64 (FIG. 2).
  • the underwriting data may be used by the pricing engine 86 (FIG. 3A) to determine a price for the sale of the loan.
  • Delivery logic 88 also includes comparison logic 410 .
  • certain terms of the delivery data of a closed loan being delivered to the purchaser e.g., occupancy type, product type, amortization type, loan term, property type, loan purpose, property sales price, appraised value, etc.
  • the underwriting data provided to the underwriting logic 26 should match the underwriting data provided to the underwriting logic 26 . If certain material terms do not match there may be an impact on the underwriting decision and the price and/or price changes (e.g., credit related yield adjustments or fees) the seller will be charged.
  • material terms are determined using the business rules, i.e., business rules may be created which identify what terms are material.
  • comparison logic 410 permits the comparison of the underwriting data for a particular loan to the delivery data provided for the loan to determine any differences.
  • comparison logic 410 may be implemented as a separate system from the delivery logic 88 and the data processing system 12 .
  • comparison logic 410 may be configured to compare the underwriting data for a particular loan (as provided by underwriting logic 26 and database 406 ) to loan data provided by an external data source (i.e., a data source that is not related to the data processing system 12 ).
  • an external data source i.e., a data source that is not related to the data processing system 12 .
  • a loan sale transaction may occur between two lenders, e.g., a loan originator and a warehouse lender.
  • a lender may sell a loan it owns but did not originate.
  • the loan originator may use underwriting logic 26 to underwrite the loan and the warehouse lender (or purchaser) may wish to compare the loan data provided by the loan originator to the underwriting data before purchasing the loan.
  • FIG. 5 illustrates a comparison process for the comparison logic 410 .
  • the delivery data for the loan being delivered is provided to the delivery logic 88 .
  • delivery logic 88 receives electronic loan data from a seller by way of user services logic 22 (FIG. 1) or the transaction processor 24 (FIG. 1). If the loan does not have an underwriting casefile ID (decision 504 ), the delivery process proceeds as described with respect to FIG. 3A. Preferably, if the loan does not have an underwriting casefile ID (i.e., the loan was not underwritten using underwriting logic 26 ), the loan is submitted to underwriting logic 26 , as described above, to determine whether the loan meets the purchasers underwriting criteria.
  • underwriting casefile ID i.e., the loan was not underwritten using underwriting logic 26
  • the delivery logic 88 sends a request to the underwriting logic 26 to retrieve the underwriting data associated with the underwriting casefile ID at block 508 .
  • Underwriting logic 26 returns the underwriting data associated with the underwriting casefile ID to the delivery logic 88 .
  • the delivery logic 88 may directly access the underwriting data associated with the underwriting casefile ID in the database 406 .
  • the underwriting data and delivery data are then compared to determine any differences in a predetermined set of information (e.g., loan, borrower, and property information) at block 510 .
  • the delivery process proceeds as described herein with respect to FIG. 3A at block 514 . If the predetermined loan information from the underwriting data and the delivery data are different (decision 512 ), it is determined whether the differences are material to the underwriting decision or the price and/or any possible credit related adjustments for the loan (decision 516 ). As discussed above, whether a difference is material is preferably determined using the business rules. If the difference is material (i.e., the difference will impact the underwriting decision and price and/or credit related adjustments), delivery logic 88 invokes pricing logic 86 (FIG. 3A) to determine the price and/or price changes (e.g., any credit related yield adjustments or fees) at block 518 . Delivery logic 88 may also invoke underwriting logic 26 to underwrite the loan based on the delivery data provided by the seller.
  • the comparison results may be provided to the seller and/or the seller may be notified using the notification processor 64 (FIG. 2) when the predetermined set of information from the delivery data does not match the underwriting data and whether there is an impact on the underwriting decision and the price as well as any additional fees (e.g., credit related adjustments) that may be charged.
  • the seller has the option to edit the delivery data provided (e.g. if the seller made an error entering the delivery data).
  • the underwriting data may be edited by way of a computer system with a user interface to receive inputs regarding the delivery data. If the seller does not edit the delivery data (decision 522 ), the delivery process proceeds as described herein with respect to FIG. 3A at block 524 .
  • the process returns to block 510 and the edited delivery data is compared to the underwriting data. Also, the seller may decide not to deliver the loan based on the comparison results or the purchaser may decide not to purchase the loan based on the comparison results.
  • the seller preferably has the option to edit the delivery data (e.g. if the seller made an error entering the delivery data into the system). If the seller does not edit the delivery data (decision 526 ), the delivery process proceeds as described herein with respect to FIG. 3A at block 528 . If the seller does edit the delivery data (decision 526 ), the process returns to block 510 and the edited delivery data is compared to the underwriting data.
  • a lender may compare underwriting data for a loan with loan data provided by a broker from a loan origination system (hereinafter referred to as “loan origination data”).
  • Loans may be originated by a broker who, once the loans have closed, provides the loans to a lender for funding.
  • the lender can then either: (i) hold the loans as investments in its portfolio, or (ii) sell the loans to investors in the “secondary mortgage market” to replenish its supply of funds.
  • a lender may wish to evaluate its loan portfolio by comparing the loan data for loans already in the portfolio to underwriting data for the loans.
  • Such an evaluation may be performed as part of, for example, a decision to sell loans from the portfolio to the secondary market, a quality control process, due diligence, etc.
  • Other parties with an interest in a transaction involving a loan may also wish to evaluate the loan by comparing the current loan data to underwriting data for the loan.
  • Underwriting logic 26 may be used by the broker to underwrite a loan as described above.
  • the lender may wish to determine if the loan origination data (or a predetermined subset of the loan origination data) is the same as the underwriting data (or a predetermined subset of the underwriting data) for the loan before accepting the loan from the broker. It possible that the loan data used to underwrite the loan may change before the loan is provided to the lender (e.g., due to continued negotiations between the broker and the borrower).
  • the underwriting data for a loan identified by an underwriting casefile ID, may be accessed using, for example, user services logic 22 (FIGS. 1 and 2).
  • the lender may then compare the underwriting data to the loan origination data provided by the broker.
  • the broker may provide the loan origination data, for example, electronically or using physical documents. If there are differences between the underwriting data for the loan and the loan origination data for the loan, the lender may decide not to accept the loan from the broker.
  • a purchaser such as a wholesaler or warehouse lender, may compare underwriting data for a loan with loan data provided by another lender (or seller).
  • Loans originated by one lender may be sold to another lender, e.g. a wholesaler or warehouse lender.
  • a lender may also sell loans it owns but did not originate. the purchaser may wish to determine if the loan data submitted by the lender is the same as the underwriting data for the loan before accepting the loan.
  • the process for comparing the loan data and underwriting data is similar to that described above with respect to the broker/lender embodiment.
  • the delivery logic 88 allows the user to edit the delivery data for format/field edits and standard/custom edits necessary to deliver loans to the purchaser. Users have a real time view of updates to the delivery data in order to resolve data errors before the loan is purchased or securitized. For example, if the data indicates that a 15-yr loan is being used to satisfy a commitment for a 30-yr loan, the user may edit the data to indicate that the loan is a 30-yr loan (in a situation where the loan data as incorrectly entered and what was originally indicated as being a 15-yr loan is in fact a 30-yr loan).
  • the user may edit the data to instead apply the 15-yr loan to a different commitment for a 15-yr loan.
  • the user may edit the data to substitute a 30-yr loan for the 15-yr loan.
  • the delivery logic 88 also includes logic for address correction (detecting erroneous address information and correcting the address information) and geographic coding (to provide additional geographic information on the property, such as longitude and latitude, tract, legislative district, metropolitan statistical area number, and so on). By the end of the process, the delivery logic also generates a unique loan number for each of the loans for tracking purposes.
  • the certification logic 90 is logic that supports the process of ensuring that all loan documentation is complete and legally binding and that the paper documentation matches the electronic information delivered by the seller.
  • the certification logic 90 generates, stores and makes available to other aspects of the data processing system 12 information pertaining to which loans have been certified.
  • the certification logic 90 is also able to generate custom reports regarding certification data including reports on loans that have not been certified so that appropriate action may be taken (e.g., having the seller repurchase the loan).
  • the certification logic 90 facilitates data modification and facilitates data matching when loans are redelivered or resubmitted.
  • the certification logic 90 also generates repots to support management decisions with respect to certification activities.
  • the custody logic 92 is logic that is used to support the custody process, or the process whereby the purchaser stores the paper loan documents during the time from when the loans are purchased or securitized until they are released. Custody protects the physical evidence of investment in negotiable assets.
  • the custody logic 92 manages custodial profile/contact information, custodian/seller relationships, and seller/servicer profile/eligibility information related to custody activities.
  • the custody logic 92 also permits information to be retrieved regarding loan investors. If the market purchaser performs the custody function itself rather than having a third party act as custodian, the custody logic 92 also supports document management in connection with incoming and outgoing documents. In particular, the custody logic 92 tracks when loan documents are in the possession of the purchaser and otherwise manages and monitors the position of the physical loan documents.
  • the custody logic 92 also manages and calculates fees charged for custodial and certification services.
  • the acquisition logic 28 may also include other logic in addition to the logic described above.
  • the acquisition logic 28 may further include payable/receivable manager logic to track the billing of yield adjustments and fees generated by transactions in the committing logic 80 , the pricing logic 86 , the delivery logic 88 , the custody logic 92 , and certain aspects of the servicer and investor reporting logic 30 .
  • the payable/receivable manager logic may also be used to display the status (including payment status) of such yield adjustments and fees in a consolidated manner.
  • the servicer and investor reporting logic 30 includes loan process and compare (LPC) logic 100 , which monitors and verifies the activities of third party mortgage servicers on an ongoing basis.
  • LPC loan process and compare
  • the LPC logic 100 may be used to verify internally generated reporting information.
  • the LPC logic 100 performs such operations as receiving and validating reporting information pertaining to loan activity, loan delinquency information and unpaid balance comparison reported by the servicer, updating the records of the data processing system 12 regarding the status of all reported loans, and determining the remittance and disbursement amounts that are expected for the loans.
  • the servicer's data Prior to loan servicing, a comparison is performed of the servicer's data for loans being serviced with the purchaser's data for the same loans. Even if the purchaser's data has already been compared with lender data for the same group of loans, the servicer's data may for some reason be different. Accordingly, the purchaser may provide a predefined set of acquisition data to the servicer that the servicer can compare with the servicer 's data. At any time thereafter, the servicer may perform individual queries of the loan data stored on the purchasers data base via the user services logic 22 (web interface) and download the data for further comparison purposes. When exceptions are noted, the servicer can correct its data or submit a change request via the user interface to the attribute change processor (ACP) logic 122 , described below.
  • ACP attribute change processor
  • a loan activity processor 102 handles expected and scheduled servicing transactions including payments, rate changes, curtailments, and so on.
  • the activity processor 102 receives and validates loan transaction data, such as loan activity, unpaid balance comparison, and delinquency status updates.
  • the activity processor 102 also can be configured to check for duplicate transactions, validate servicer information, determine and validate the type of loan transaction, and validate that the loan activity is being reported in the correct reporting period.
  • the activity processor 102 also confirms that changes in unpaid balance and last paid installment are correct, derives expected interest remittance, derives expected principal remittance, and compares the derived amounts to the reported remittance amounts. After validation, the status of the loan is made available to the servicer through the user services logic 22 . The activity processor 102 also triggers the appropriate cash and accounting transactions in a book and tax accounting processor 146 . When loan activity is processed and does not match the purchasers expectations based on rules and calculations, exceptions are noted and communicated to users using the notification processor 64 .
  • the amortization/calculation processor 104 is used by the activity processor 102 to calculate loan level amounts, such as principal and interest due, servicing fees and other data pertinent to each loan.
  • Processor 104 may additionally be used to compute derived or decomposed cash flows, such as a guaranty fee or a servicing fee.
  • Business rules are used to identify scheduled and unscheduled principal, calculate fees, calculate remittance and disbursement amounts, calculate amounts to be disbursed to investors, amortization, and accruals. These calculations are used throughout the system 12 to perform functions such as collecting remittances from servicers, dispersing funds to investors and performing accounting activities. The results of processing are available through an interactive user interface to both personnel of the purchaser and personnel of the servicer for correction when transactions do not comply with business rules.
  • the trial balance processor 106 provides for validation of parameters such as servicer number, purchaser and servicers loan numbers, effective date, ending unpaid balance, note rate, pass through rate, principal and interest payment, last paid installment (LPI) date, pool number, accrued interest receivable balance, available line of credit, conversion date, reverse mortgage payment, net principal limit, taxes and insurance set asides, property charges set asides, repairs set asides, servicing fees set asides, scheduled payments, and so on. Any discrepancies are resolved and any system updates (loan attribute changes, data updates) are implemented. The LPC logic 100 then reprocesses the activity based on the corrected data.
  • LPI last paid installment
  • the LPC logic 100 may also be triggered with regard to a particular loan when the attribute change processor (ACP) logic 122 makes a change to attributes that affect loan processing or when a loan attribute triggers processing, such as note rate changes, payment changes and loan reporting.
  • the LPC logic 100 may also be triggered by borrower behavior (e.g., loan delinquencies status) at beginning and end of accounting periods.
  • the servicing event processor 108 identifies and handles business events that are not identified by the activity processor 102 . Examples of these events include identifying delinquent loans and identifying loans that are eligible for reclassification or substitution.
  • the delinquency status reporting processor 110 accepts delinquency reasons from the servicer for loans that have payments that are in arrears.
  • the attribute change processor (ACP) logic 122 processes loan or security level changes.
  • ACP logic 122 processes attribute changes regarding loans.
  • loans are characterized in the data processing system 12 by a series of attributes rather than by product codes.
  • Each mortgage product that is purchased is then represented by a series of attributes instead of or in addition to an overall product code.
  • New products may be created by creating new combinations of attributes, or by adding new attributes.
  • An exemplary list of possible attributes that may be used is provided at the end of this section.
  • ACP logic 122 processes attribute changes that occur after loans are brought into the data processing system 12 .
  • the ACP logic 122 processes attribute changes that are unexpected or are unscheduled whereas the LPC logic 100 handles attribute changes that are both expected and scheduled.
  • the ACP logic 122 also validates the attribute change request, assesses the financial impact of the change, updates the appropriate data and triggers the appropriate cash and accounting transactions.
  • Unexpected attribute changes are changes that are required due to new features or discrepancies between contract documentation and data captured by the acquisition logic 28 , this can include changes to loan data and/or changes in loan behavior.
  • Unscheduled attribute changes are changes that may occur based on contract documentation but the timeframe is unknown. For example, an unexpected attribute change would be a change for a daily simple interest cash loan that the purchaser has purchased without knowledge of a particular feature. After the purchase, the borrower exercises options under the feature and the servicer advances the next due date of the loan and submits a loan activity transaction record to the purchaser. Not knowing about the feature, the purchaser rejects the transaction since the loan record does not indicate the presence of the feature.
  • an unexpected and unscheduled attribute change would be the case where the lender submits an adjustable rate mortgage change request for a loan that the purchaser has set up as a fixed rate mortgage.
  • the request is processed as an unscheduled change because the purchaser's systems have never had an event scheduled to trigger the change.
  • An example of an unscheduled change is a fixed rate convertible loan which has the conversion option indicated in the terms of the note. It is anticipated that an attribute change will occur but the timing of the event is unknown and therefore unscheduled.
  • the two primary types of unexpected attributed changes are post purchase adjustments (data corrections) and modifications (attribute changes driven by a number of business requirements, such as product flexibility, delinquency management, and substitutions/reclassifications).
  • the ACP logic 122 receives attribute change requests which indicates current database values for the loan and the proposed changes.
  • the validation of the loan with the new values is then accomplished by applying the rules processor 180 (FIG. 6) to the ACP transaction.
  • the business rules engine is applied to determine whether the changes are allowable and any failed business rules are provided to an operator for further review.
  • the original terms of the contract are used to determine any pricing adjustments of the attribute change.
  • the system determines the difference between the current or adjusted price as applicable and the new price for the purchase adjustments.
  • a human operator reviews the requested change, the impact of the requested change, and any required hard copy documentation needed to justify the change.
  • the operator/business analyst either approves or rejects the change.
  • Rejected transactions may be modified and resubmitted. Approved adjustment transaction values are applied to the database and an audit trail history is maintained. If the result of the change request has an accounting impact, the ACP logic 122 also generates the appropriate transactions to trigger the accounting processor 146 .
  • the ACP logic 122 also includes loan conversion request processing logic 338 for handling loan conversion requests. Thus, when a loan conversion request is received, this logic tracks the request for the change, determines the allowability of the change based on business rules, and employs the remainder of the ACP logic 122 to make the change.
  • the securities aggregation and management (SAM) logic 130 receives the loan level cash flow information produced by the LPC logic 100 and aggregates this cash flow information to produce security level information.
  • the security level information is produced at each of the following levels: remittance/express date level within each piece/single pool; single pool level or piece level within each major pool; pseudo pool (pool-like reporting group) level; major header level for each major pool; choice pool level; strip level; mega pool level; and mega in mega (MIM) pool level.
  • the SAM logic 130 is also capable of processing and managing any grouping of loans, cash flows from loans, and other financial instruments.
  • the SAM logic 130 determines the loans in a given pool, aggregates cash flows based on the pool and loan level attributes for all the loans and then updates the system database.
  • the packet activity processor 132 has the flexibility to aggregate loan level cash flows at the most granular level to security level enabling the SAM logic to also manage specific cash flow strips (e.g., access yield strips, interest only strips).
  • the SAM logic 130 finalizes the relevant security information.
  • the SAM logic 130 uses a packet disclosure processor 134 to make final remittance level principal and interest, guaranty fee, and other draft amounts available to a cash processing logic 144 and to make security accounting data available to a book and tax accounting logic 146 .
  • the SAM logic 130 also calculates, at the various MBS security levels, disclosure data for investors and the payment distribution to investors.
  • the SAM logic 130 also includes packet modification request processing logic which is used to modify packets in generally the same manner that the attributes of loans are modified as described above in connection with the ACP logic 34 .
  • the operation of the SAM logic 130 , and in particular packets and the packet activity processor 132 is described in greater detail in connection with the packeting logic 154 .
  • the SAM logic 130 can be used to facilitate the provision of real-time data updating.
  • investors may be supplied with real-time analytic data.
  • the analytic data may include any data that allows investors to more accurately determine the value of their holdings, such as data concerning monthly loan payments, loan prepayments, loan pay-offs, and so on. For example, when a loan pays off, investors may be provided immediate access to this information rather than waiting until the next MBS reporting cycle.
  • the servicer and investor reporting logic 30 and the securitization logic 32 utilize the same data base (see FIG. 6).
  • the data used by the securitization logic 32 is always synchronized with the data used by the servicer and investor reporting logic 30 .
  • the servicer and investor reporting logic 30 and the securitization logic 32 may utilize different data bases that are synchronized on a weekly basis, on a daily basis, on a sub-daily basis, or in real time, depending on the frequency of update that is desired.
  • a servicing transfer logic 142 facilitates the process of transferring loans for the servicing rights of owned or securitized mortgages from one servicer to another or from one portfolio to another within the same servicer as of an effective date.
  • a servicing transfer may be initiated, for example, if a servicer decides to stop servicing loans for business reasons, if a servicer decides to transfer a certain group of loans to another branch or portfolio, if a servicer is involved in a merger or acquisition of the servicer necessitating a transfer to the surviving entity, or for other reasons.
  • the servicing logic 142 processes information regarding the old and new servicers and the loans that are subject to the change in servicing and updates loan record data for the respective affected loans.
  • the effective date of the change in servicing is also specified.
  • Information that is provided to the servicing transfer logic 142 as part of a servicing request includes the transferors servicer number, address and contact information, the transferees servicer number, address and contact information, unique loan numbers to be transferred, effective date, and other data. Additional steps, such as notifying the transferor of the termination and assessing transfer fees may also be performed.
  • the cash processor 144 provides a facility to allow servicers and other vendors to create and maintain bank account information.
  • the accounts are bank accounts established with the purchaser to facilitate loan transactions.
  • Servicers have the ability to create/select/update their account information in real time, including account numbers and remittance/disbursement information.
  • the information captured in this process allows the cash processor 144 to create and execute Automated Clearing House (ACH) transactions.
  • ACH Automated Clearing House
  • Historical records of servicers and vendors account and draft information is maintained to assist in resolving any issues that may arise.
  • the cash processor 144 retrieves remittance and disbursement information from other areas of the data processing system 12 .
  • the remittance and disbursement information includes effective date, loan number, dollar amount, remittance code, and granular level details.
  • the cash processor 144 performs a rollup of loan level details by servicer number as required.
  • the cash processor 144 also performs a rollup of loan level details by seller number whenever the seller is not the designated servicer.
  • the cash processor 144 triggers appropriate accounting transaction codes as needed that allow the book and tax accounting processor 146 to record applicable accounting entries.
  • the cash processor 144 creates cash transactions, for example, automated clearing house (ACH) transactions, outgoing check transactions, and so on.
  • the cash processor 144 begins this process after the cash processor 144 has completed the process of assessing and validating remittance and disbursement data.
  • the first step in creating a cash transaction is validating servicer/vendor bank account information.
  • an ACH transaction is created that debits or credits the appropriate custodial bank account
  • the book and tax accounting logic 146 manages accounting activities associated with the loans.
  • the accounting logic 146 provides a consistent methodology for the recording of accounting events related to mortgage business activities across the acquisition logic 28 and the servicer and investor reporting logic 30 into subsidiary ledgers for posting to a general ledger.
  • the book and tax accounting logic 146 supports the accounting activities related to the packaging of loan cash flows to the first level packet for the securitization logic 32 .
  • the book and tax accounting logic 146 supports the accounting activities related to forming securities or packets out of portfolio loan collateral.
  • the investment accounting for securities held in portfolio and for the payment distribution on mortgage derivatives could also be handled by the book and tax accounting logic 146 or, preferably, is handled by separate accounting logic 156 , described in greater detail below
  • the book and tax accounting logic 146 journalizes mortgage related business activity, maintains subsidiary ledgers, provides audit trails, provides data integrity and control within the subsidiary ledgers, facilitates timely reconciliations, provides flexibility to account for new products or changes depending on actual accounting methodologies, and provides information needed to perform financial analysis.
  • the book and tax accounting logic 146 utilizes an accounting matrix which is a two-dimensional structure comprised of accounting “families” and “family members.”
  • the families are groups of accounting relevant transaction and loan attributes, and the family members are the allowable values for each of the groups. All intersections of families and family members have a debit and credit account number associated with each of the intersections.
  • the accounting matrix uses business rules processor 180 to automatically interpret the transactions. As new products are introduced, the accounting matrix is modified to incorporate new family and/or family members to properly record the new business activity. Similarly, as products become obsolete, or as the requirement for breaking out activity on the corporate general ledger becomes less detailed, the accounting matrix can be modified to adapt to those changes as well.
  • a subsidiary ledger provides the capability to view the lowest level of business activity that created the entry in the subsidiary ledger to maintain an audit trail for the subsidiary ledger activity.
  • a system walk forward test of the subsidiary ledger balances is also performed to assure data integrity with the subsidiary ledger.
  • activity within the subsidiary ledgers is automatically summarized and posted to the general ledger
  • An automated reconciliation tool may be provided that generates the results of the reconciliation and, through a user interface, displays the results to an operator. Any reconciling items between the subsidiary and general ledgers may be analyzed and resolved by the operator. Through the operator interface, the operator updates the status of the reconciling items to indicate the results of the analysis. As reconciling items are resolved, the operator triggers the automated reconciliation facility to repeat the reconciliation and display the results.
  • the book and tax accounting logic 146 also provides information for financial and operational analysis. Information related to the status of the book and tax accounting logic is provided to operations through an accounting console.
  • the accounting console is a management and operational workflow tool that includes notifications and status information related to the book and tax accounting processes. It also provides summarized reports and the ability to view the detailed information supporting those reports.
  • the securitization logic 32 includes sifting/sorting logic 152 which accesses inventory, identifies collateral or asset attributes and sub-attributes, and categorizes data at its most granular level in both aggregating and segregating cash flows associated with mortgage assets.
  • the sifting/sorting logic 152 provides a user interactive application that allows users to define selection criteria (loan and/or atomic characteristics), prioritize them, evaluate results, and make decisions about market transactions and their related economics. By sifting and sorting through available inventories, cash flows may be qualified and quantified for optimal aggregation of targeted transactions, given relative market value.
  • the sifting/sorting logic 152 operates under a user maintainable library of business rules associated with mortgage instruments and respective cash flows.
  • An auto sift function is also provided to allow to batch processing of predefined inventory types. For example, a daily auto sift may be executed against “available for sale” loans to aggregate and pre-packet the loans for future transactions.
  • the purpose of the sifting/sorting logic 152 is to provide a mechanism by which users can examine the entire collateral universe and pair down to smaller groupings of collateral or assets within the universe.
  • Collateral refers to any cash flow derived from loans, pools, securities, commitments, and packets.
  • the purpose of sorting is to group the subset of collateral identified in the sifting process and organize it by a single or multiple attributes to further refine the pool of candidate collateral to be placed into a potential packet.
  • the sifting/sorting logic 152 supports the packeting logic 154 , described below.
  • the packeting logic 154 is used to create, maintain, and otherwise support packets.
  • a packet is an aggregation or packaging of cash flows that is treated as an entity separate and distinct from the incoming cash flows that support the packet and from the cash flows that result from the packet. Packets maintain the data integrity of the underlying assets as received by the LPC logic 100 and create an information chain that maps to a higher-order asset (e.g., an MBS or other financial instrument to be sold to an investor).
  • the source data for packets may be loan-level or packet-level information, and the packets themselves may represent actual securities or just a unit of reporting and remittance.
  • Packets permit the data processing system 12 to enable and support new transactions by providing a platform for sourcing, normalizing, and centralizing cash flow-related data and building the linkages between loan assets and securities or non-securitized assets. Packets provide greater flexibility in the transformation of cash flows from the primary mortgage/loan level to the secondary market and within the secondary market. Packets provide the flexibility-not only to create and sell securities to investors but also to support non-securitized forms of packaging to enable selling or retaining cash flows from individual loans. The ability to create and manipulate packets enables the creation of new types of financial instruments and new types of transactions within the secondary market.
  • the accounting logic 156 supports additional accounting functions for the securitization logic 32 that are not already supported by the book and tax accounting processor 146 .
  • the book and tax accounting processor 146 is responsible for performing maintenance accounting at the loan level (i.e., posting transactions), while the accounting logic 156 is responsible for the accounting logic associated with transformative accounting events.
  • Transformative accounting events include, for example, securitization events (in which a loan is to be construed to be sold). Other transformative events include a securitization event in which only a portion of the cash flows are sold, a sale event of a portfolio securities, and a sale event involving a whole loan.
  • the accounting logic 156 is responsible for ongoing maintenance in connection with the reconciliation of securities cash payables.
  • the accounting logic 156 performs such things as deriving the initial cost basis at the time of acquisition for every loan and inventory, maintaining the cost basis of each loan, tracking accounting intent for each loan, and performing market valuation for each loan.
  • the functionality of blocks 146 and 156 are shown as being conceptually separate, this functionality could also be combined.
  • the position monitor 158 allows monitoring of the purchaser's overall trade and investment position. Particularly, the position monitor 158 is an interactive tool that is usable to monitor positions of investors of whole loans and securities, and designate or redesignate inventory between trading accounts. The position monitor 158 is able to provide this information in near real time because the position monitor 158 either uses the same transactional database(s) as the servicer and investor reporting logic 30 and the securitization logic 32 or, preferably, uses a separate data base that is synchronized with these data bases. For both whole loans and securities, the position monitor 158 provides daily and month-to-date commitment/trade and delivery/settlement positions. The position monitor 158 also provides cumulative inventory positions held by the portfolio.
  • the position monitor 158 allows investors to manage inventory from an economic, risk management, and regulatory accounting and taxation perspective. It also allows investors to determine or designate what assets to buy, what assets to sell, and what assets to retain or hold for investment.
  • the portfolio manager 158 provides investors with a clear and concise view of their current net position of inventory.
  • the out of portfolio (OOP) pooling logic 160 permits the data processing system 12 to be used for pooling loans to create financial instruments in situations where the loans are owned by the entity that owns or operates the data processing system 12 or by an entity other than the entity that owns/operates the data processing system 12 .
  • the OOP pooling logic 160 provides the owner of the loans being pooled with the ability to select asset attributes and sub-attributes at a granular level, the ability to select loans to optimize chartered pool statistics, the ability to flexibly map incoming and outgoing cash flows, and the ability to use an on-screen display to manipulate collateral.
  • the out of portfolio pooling processor 160 also has the ability to collateralize asset cash flows as described above in connection with the packeting logic 154 .
  • the whole loan trading logic 162 provides a facility for engaging in whole loan trades to permit the owner or operator of the data processing system 12 to identify and sell loans out of its portfolio to other entities.
  • the whole loan trading logic 162 also provides logic for reporting to the servicer of a sold loan (1) that the loan has been sold and (2) the identity of the new owner of the loan, allowing the servicer to begin reporting payment information to the new owner.
  • the common services logic 34 includes work flow processor 170 which generates notifications about required actions and routes the notifications to users of the data processing system 12 according to pre-defined processing sequences for request approvals and exception report resolutions.
  • the work flow processor 170 also keeps track of status and actions related to work items.
  • the report processor 172 generates reports based on users' requests.
  • the report processor 172 allows data to be extracted from the data bases to prepare reports that can be sent out through the user services logic 22 .
  • the reports that are returned may be bulk transfers of data.
  • the report processor 172 supports generating the reports described above in connection with the acquisition logic 28 , the servicer and investor reporting logic 30 , and the securitization logic 32 .
  • the database and access control logic 174 provides database and user security administration and control for the databases in the data storage system 38 and functions available through system 12 .
  • the database access and control logic also maintains referential integrity, processes queries and updates, and performs all tasks related to access and control of the databases in the data storage system 38 .
  • the process controller/scheduler 176 triggers execution of processes based on time schedule and/or events received from application components.
  • the process controller/scheduler encapsulates information on processing interdependencies between different components in the data processing system 12 .
  • the audit logging logic 178 logs data that is needed for historical tracking of the activities of the data processing system 12 .
  • the purpose of the data logging is primarily to meet audit requirements in connection with the transactions processed by the data processing system 12 .
  • the business rules processor 180 is a rules engine that encapsulates business rules to permit the business rules to be applied to the loan data. Examples of the business rules applied by the rules processor 180 have been described throughout the discussion of the data processing system 12 .
  • a user interface is provided that allows the business rules to be modified and that allows new business rules to be added or obsolete business rules to be deleted.
  • the rules processor 180 maintains the business rules separate from the remainder of the application code that implements other aspects of the data processing system 12 . This allows the business rules to be modified/added/deleted without requiring revisions to the application code.
  • the rules processor 180 is provided as three separate rules processor, one for each of the acquisition logic 28 , the servicer and investor reporting logic 30 , and the securitization logic 32 , with separate user interfaces for each rules processor.
  • service granularity is achieved in part by representing loans as a series of data attributes.
  • the following is an example of a set of attributes that may be used to characterize loans: accounting class code; accounting close effective period; accounting reporting category code; actual UPB at acquisition; adjusted last paid installment date; adjusted unpaid principal balance; ceiling; change frequency; change method; conduit code; custodian code; downward cap; downward cap code; effective date; excess yield; excess yield adjustment; extended term; purchaser loan number; final step change; first PITI (principal, interest, taxes, insurance) due date; fixed interest rate; fixed pass-thru rate; fixed payment amount; floor; frequency of payment change; frequency of rate change; future feature code; index code; index lookback; interest rate; loan guaranty payment date; loan conversion date; loan guaranty date; loan payoff interest calculation code; loan rate effective date; loan to value ratio; LP control record; lender pass through (LPT) type code; maximum term; months payment control effective; months rate control effective; mortgage margin; mortgage
  • a cash flow may be any type of payment, whether of principal, interest, or fees.
  • Cash flow may also includes credit-related losses, which manifest themselves from the securities standpoint as negative investor payments (i.e., a reduction to positive cash flows).
  • Possible sources of cash flow may be associated with principal, interest, servicing fees, guarantee fees, mortgage insurance, prepayment penalties, borrower-paid fees, servicer advances, servicer recoveries, loss/default components, and REO activity.
  • individual cash flows that may be identified include the following: scheduled principal (amount payable based on scheduled amortization), actual principal (what was applied as principal), unscheduled principal (amount from borrower applied in excess of scheduled), advanced (amount not collected from borrower but remitted to investor), shortfall (underpayment from borrower, usually meaning less than full scheduled amount).
  • scheduled principal amount payable based on scheduled amortization
  • actual principal what was applied as principal
  • unscheduled principal amount from borrower applied in excess of scheduled
  • advanced amount not collected from borrower but remitted to investor
  • shortfall underpayment from borrower, usually meaning less than full scheduled amount
  • individual cash flows that may be identified include the following: scheduled Interest (amount payable), actual (what was applied), excess (interest collection in excess of amount payable), advanced (not collected from borrower but sent to investor), shortfall (underpayment from servicer), capitalized (negative amortization), other capitalized interest (delinquency), unrecoverable prepayment interest shortfall.
  • individual cash flows that may be identified include the following: gross servicing fee, core servicing fee (usually relates to tax), excess servicing fee, safe harbor (tax).
  • gross guarantee fee individual cash flows that may be identified include the following cash flows: gross guarantee fee (GF) (total charged to the lender), cash flows for internally tracking costs (e.g., costs associated with credit risk), base GF, GF variance, and other GF adjustments.
  • GF gross guarantee fee
  • MI mortgage insurance
  • individual cash flows that may be identified include the following: lender paid MI, borrower paid MI, portion of GF construed to be MI, back-end MI.
  • prepayment penalties individual cash flows that may be identified include the following: prepayment penalty, prepayment penalty (borrower-paid), yield maintenance fee (borrower-paid).
  • individual cash flows that may be identified include the following: borrower-paid fees, late payment fee, conversion/modification fee.
  • individual cash flows that may be identified include the following: advanced principal, advanced interest, advanced guaranty fee, servicing advances (usually relates to defaults, e.g., T&I).
  • servicer recoveries individual cash flows that may be identified include the following: recovered principal advances, recovered interest advances, recovered guaranty fee advances, recovered servicing advances.
  • cash flows that may be identified include the following: net realized loss (total amount payable to investors less all recoveries), foreclosure expenses, attorney fees, recoup of non-recoverable advances, loss due to modification, loss due to appraisal reduction, loss due to deficiency valuation, non-capitalized deferred interest (e.g. workout), interest paid on advances.
  • cash flows that may be identified include the following: foreclosure sale proceeds, rental income, insurance proceeds, tax expenses on REO, repair expenses on REO, sale/marketing expenses on REO, REO property maintenance expenses. It may be noted that some of the above cash flows are aggregate cash flows that can be further decomposed.
  • UPB unpaid principal balance
  • participation percentage including principal participation percentage, interest participation percentage, and servicing fee participation (basis points)
  • discount rate used to calculate yield maintenance or prepayment penalty

Abstract

A method for facilitating delivery of a loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan and an identifier includes providing a delivery template to a seller of the loan to receive delivery data for the loan; retrieving the underwriting data associated with the identifier upon receiving a request from the seller including the identifier and populating the delivery template with the predetermined set of information.

Description

    PRIORITY
  • This application claims the benefit of U.S. [0001] Provisional Application 60/436,977, filed Dec. 30, 2002, hereby incorporated by reference in its entirety.
  • FIELD OF THE INVENTION
  • This invention relates generally to computer systems and methods used to process data pertaining to financial assets, such as loans, securities, etc. and more particularly to facilitating delivery of a loan to a secondary mortgage market purchaser. [0002]
  • DESCRIPTION OF RELATED ART
  • The purchase of a home is typically the largest investment that a person makes. Because of the amount of money required to purchase a home, most home buyers do not have sufficient assets to purchase a home outright on a cash basis. In addition, buyers who have already purchased a home may wish to refinance their home. Therefore, potential homebuyers consult lenders such as banks, credit unions, mortgage companies, savings and loan institutions, state and local housing finance agencies, and so on, to obtain the funds necessary to purchase or refinance their homes. These lenders offer mortgage products to potential home buyers. The lenders who make (originate and fund) mortgage loans directly to home buyers comprise the “primary mortgage market.”[0003]
  • When a mortgage is made in the primary mortgage market, the lender can: (i) hold the loan as an investment in its portfolio; or (ii) sell the loan to investors in the “secondary mortgage market” (e.g., pension funds, insurance companies, securities dealers, financial institutions and various other investors) to replenish its supply of funds. The loan may be sold alone, or in packages of other similar loans, for cash or in exchange for mortgage backed securities which provide lenders with a liquid asset to hold or sell to the secondary market. By choosing to sell its mortgage loans to the secondary mortgage market for cash, or by selling the mortgage backed securities, lenders get a new supply of funds to make more home mortgage loans, thereby assuring home buyers a continual supply of mortgage credit. [0004]
  • Loans originated by a lender (or alternatively a broker) are typically underwritten before being closed or prior to delivery (i.e. sale) to a purchaser in the secondary mortgage market. Underwriting provides a recommendation whether the loan meets the credit risk and eligibility requirements of a lender for the purposes of its portfolio or a secondary mortgage market purchaser based on a set of loan information provided by the lender. Often, however, the set of loan information may change between underwriting and closing and delivery of the loan (e.g., through continued negotiations between the borrower and lender). The changes to the set of loan information may affect the underwriting decision, the decision whether to purchase the loan, as well as the price for the sale of the loan. Typically, however, a purchaser is only able to determine differences between the set of loan information used for underwriting and the set of loan information for the delivered loan after the loan has been delivered and the sale transaction completed. If there are any yield adjustments due to differences in the set of loan information, the purchaser is faced with requesting such yield adjustments from the seller after the sale is complete, often after a significant lapse of time. [0005]
  • Therefore, a need exists for a system and method that provides access to underwriting data at delivery. In addition, a need exists for a system and method that facilitates the comparison of underwriting data for a loan and delivery data for the loan at the time of delivery, before the sale transaction is complete. [0006]
  • In addition, while the sale of loans to the secondary mortgage market in exchange for cash or MBS has worked to increase home ownership rates, these rates could further be improved if new types of investment instruments or assets and new types of mortgage products could be provided. Efforts to offer new types of investment instruments and new types of loan products have been hampered by the fact that current data processing systems for processing loan information (including information on both the borrower side and on the investor side of the process) are not sufficiently efficient and flexible. Modifying the data processing system to support a new type of loan product or a new type of investment instrument is very difficult and expensive. In many cases, inherent limitations in the architecture of such data processing systems make certain types of new loan products or new investment instruments impossible to offer as a practical matter. [0007]
  • SUMMARY OF THE INVENTION
  • In accordance with one aspect of the invention, a method for facilitating delivery of a loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan and an identifier includes providing a delivery template to a seller of the loan to receive delivery data for the loan; retrieving the underwriting data associated with the identifier upon receiving a request from the seller including the identifier and populating the delivery template with the predetermined set of information. [0008]
  • In accordance with another aspect of the invention, a system for facilitating delivery of a loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan and an identifier includes means for providing a delivery template to a seller of the loan to receive delivery data for the loan, means for receiving a request from the seller including the identifier, means for retrieving the underwriting data associated with the identifier and means for populating the delivery template with the predetermined set of information. [0009]
  • In accordance with yet another aspect of the invention, a system for delivering a loan to a purchaser where the loan has a set of underwriting data provided by underwriting logic includes a user interface for providing a delivery template to the seller of the loan and for receiving delivery data for the loan and delivery logic, coupled to the user interface, for processing the delivery data for the loan. The underwriting data includes a predetermined set of information relevant to the delivery of the loan and has an identifier generated by the underwriting logic. Upon receiving a request from the seller that includes the identifier via the user interface, the delivery logic retrieves the underwriting data associated with the identifier and populates the delivery template with the predetermined set of information. [0010]
  • Other features and advantages of the present invention will become apparent to those skilled in the art from the following detailed description and accompanying drawings. It should be understood, however, that the detailed description and specific examples, while indicating preferred embodiments of the present invention, are given by way of illustration and not limitation. Many modifications and changes within the scope of the present invention may be made without departing from the spirit thereof, and the invention includes all such modifications.[0011]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of a data processing system according to one preferred embodiment. [0012]
  • FIG. 2 is a block diagram showing user services logic of the system of FIG. 1 in greater detail. [0013]
  • FIGS. 3A and 3B are block diagrams showing underwriting logic, acquisition logic, servicer and investor reporting logic, and securitization logic of the system of FIG. 1 in greater detail. [0014]
  • FIG. 4 is a block diagram of the underwriting logic and delivery logic of the system shown FIGS. 1 and 3A. [0015]
  • FIG. 5 illustrates a comparison process for the comparison logic of FIG. 4. [0016]
  • FIG. 6 is a block diagram showing common services logic of FIG. 1 in greater detail.[0017]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Referring now to FIG. 1, a [0018] computer system 10 for processing data pertaining to financial assets is shown. As shown in FIG. 1, the system 10 comprises a data processing system 12, user systems 14, bulk data systems 16, and other data interfaces 18. The data processing system 12 further comprises user services logic 22, a transaction exchange processor 24, underwriting logic 26, acquisition logic 28, servicer and investor reporting logic 30, securitization logic 32, common services logic 34, a data storage system 38, and other data interfaces 18. Herein, although the term “logic” is used in connection with some blocks and the term “processor” is used in connection with other blocks, these two terms are used interchangeably. The term “processor” is used in the generic sense and is not meant to imply a separate discrete unit of processing hardware.
  • The [0019] data processing system 12 is configured for processing data pertaining to financial assets, such as loans and securities. In one embodiment, the data processing system 12 is configured to be used by a participant in the secondary mortgage market. Herein, for convenience, the participant is referred to as a “purchaser,” although it should be understood that the participant may participate in the secondary market in other, different, or additional ways (e.g., as a loan guarantor, as a loan securitizer, and so on).
  • The [0020] data processing system 12 is preferably useable to support various types of transactions which may be executed by such a purchaser in connection with one or more loans. For example, the purchaser may purchase loans from lenders or other loan originators as part of a cash execution. The purchased loans may, for example, be held as investments in the purchaser's investment portfolio. Alternatively, the purchaser may create mortgage backed securities (MBS) as part of an MBS execution, or create other financial instruments or assets that are collateralized by cash flows associated with individual loans, including both loans that have been purchased by the purchaser and other loans that have not been purchased by the purchaser. For example, in the case of MBS, the purchaser may acquire a pool of loans, securitize the pool of loans to create MBS that is then sold to investors, and hold the pool of loans in trust for the benefit of the investors. The purchaser may also receive a fee for guaranteeing to holders of MBS or other financial instruments the repayment of the loans by borrowers. The purchaser may also use loans to create other types of financial assets or instruments, for example, by purchasing loans and selling the financial instruments to investors, or by performing such services for other owners of loan assets.
  • The [0021] acquisition logic 28 is preferably useable to perform such operations as receiving information such as loan term, interest rate, principal owed, and other parameters regarding loans when loans are first purchased or otherwise acquired and entered into the data processing system 12. In the case of cash executions, the acquisition logic 28 is also used to perform such operations as receiving commitments for the purchased loans.
  • The servicer and [0022] investor reporting logic 30 is used to process periodic loan data for loan accounting purposes and generate accounting output in connection with the purchased loans. Herein, the terms “reporting logic” and “servicer and investor reporting logic” are used interchangeably and both refer to logic that is configured to perform loan accounting and generate accounting output (e.g., for purposes of investor reporting, for purposes of managing a loan portfolio, and so on) in connection with a plurality of loans. The servicer and investor reporting logic 30 preferably performs such functions as receiving loan payment data on an ongoing basis from third party servicers. In this regard, it may be noted that the servicer and investor reporting logic 30 in the illustrated embodiment is not used for servicing loans directly but rather interfaces with a third party servicer. Of course, the servicer and investor reporting logic 30 could also be configured to include additional logic for servicing loans, either as part of the servicer and investor reporting logic 30 or as part of another functional block. The accounting output generated by the servicer and investor reporting logic 30 may include such things as accounting, tax, performance/valuation, and/or other relevant financial information for the loans retained in the portfolio or sold, in whole or in part.
  • The [0023] securitization logic 32 is used to generate financial assets. Herein, the terms “financial asset generation logic” and “securitization logic” are used interchangeably and refer to any logic that is used to generate/create financial assets. Herein, the term “financial asset” is used to generically to refer to any asset that is backed by one or more cash flows, and includes such things as assets that are created entirely for internal data tracking purposes (e.g., in the case of packets which do not represent securities), as well as assets that have external significance (e.g., in the case of MBS or other security). The securitization logic 32 may be used to generate financial assets such as MBS or assets that are tracked internally in situations where the owner/operator of the data processing system 12 purchases a pool of loans and holds the loans as an investment in its own portfolio.
  • It will be appreciated that the [0024] data processing system 12 may perform fewer or additional functions as compared to those described herein. For example, an entity that performs only some of the above-mentioned processes may use a computer system that contains only a subset of the functions described herein. Herein, it will be assumed that the data processing system 12 is used to support each of the business processes described above.
  • Generally speaking, in the illustrated embodiment, there are three access points for external systems into the [0025] data processing system 12. Access can include data flow into and out of system 12. A first access point into the data processing system 12 is the user services logic 22 which provides entry to the user system 14. A preferred implementation of the user services logic 22 is described in greater detail below in connection with FIG. 2. For purposes of explanation, the user systems 14 are assumed to be operated by human users that participate in some way in the above mentioned business processes. For example, the human user may be an employee of a lender or other loan originator that uploads loan information to the purchaser (or corrects, updates, and so on, information that has previously been provided) in connection with committing to deliver or actually delivering a group of loans to the purchaser, an employee of an owner of a portfolio of loans that uploads loan information in connection with a group of loans the owner wishes to have securitized by the purchaser, an employee of a servicer that uploads payment information regarding a group of loans serviced by the servicer, an employee of an institutional investor that downloads information regarding the financial performance or other data regarding investment instruments created and maintained by the purchaser, an employee of the purchaser itself, and so on.
  • A second access point into the [0026] data processing system 12 is the transaction exchange processor 24 which provides entry to the bulk data systems 16. The transaction exchange processor provides an alternative, bulk transfer mechanism for exchanging at least some of the transaction-related data mentioned above in connection with the user systems 14, typically without intervention of a human operator. Such bulk data transfers may occur with lenders, servicers and so on. The transaction exchange processor 24 receives/sends transactions, and prescreens/sorts/translates data is needed, and makes the transactions/data available for further processing in the data processing system 12 or outbound transmission. A third access point into the data processing system 12 is through the data interfaces 18. The data interfaces 18 may be used to exchange other types of data between other computer systems and the data processing system 12. For example, the data interfaces 18 may be used, to import or export data to other external computer systems (that is, computer systems not under the control of the purchaser) or other internal computer systems (e.g., computer systems that are under the control of the purchaser but that provide functionality that is not integrated into the data processing system 12).
  • The [0027] data processing system 12 is described in greater detail below in connection with FIGS. 2-6. As will become apparent from the discussion below, the preferred data processing system 12 exhibits a high level of data, service and time granularity. With respect to data granularity, the system 12 is capable of decomposing loans into a series of highly granular cash flows and tracking all of the cash flows from the point the cash flows enter the data processing system 12 (e.g., as part of a loan payment or other cash flow source) to the point the cash flows exit the data processing system 12 (e.g., as part of a payment on a financial instrument). The decomposition of a particular loan into sub-loan cash flows may occur when the loan is first acquired, later when servicing activity begins on the loan, or at another time. When loan payments are received, the allocation of the loan payment into individual cash flows may be performed by logic executed by the servicer, by the data processing system 12, or by other logic. Ideally, all or nearly all of the cash flow sources associated with a particular loan can be identified and tracked. Additionally, it is also possible to aggregate cash flows from a borrower perspective or other entity perspective. For example, a series of loans (e.g., all to the same borrower) may be aggregated into a higher order cash flow and then the aggregation of the loans may be decomposed. It is also possible to add cash flows to existing loans, for example, so that a new cash flow (e.g., for a new line of credit) may be established without having to set up a new loan. This provides additional flexibility to modify a borrower's loan over time. Thus, the data processing system 12 not only decomposes and maps cash flows associated with such things as principal and borrower paid interest, but also sub-loan level cash flows arising in association with the borrower paid interest or fees associated with the loan such as servicing fees, guarantee fees, mortgage insurance, prepayment penalties, borrower-paid fees, servicer advances, servicer recoveries, and loss/default components, and provides other flexibility. Additional description regarding exemplary possible sources of cash flows is provided at the end of this section. The decomposition and mapping of cash flows dramatically increases the number of different types of financial instruments that may be created, because it makes it possible to create financial instruments based on these other cash flows. In turn, this makes it possible to create financial instruments that are more optimally configured to meet the needs of the owner of the financial instrument.
  • With respect to service granularity, the [0028] data processing system 12 represents loans as a series of attributes and uses a business rules engine to process loan information. This dramatically simplifies the process of expanding the capabilities of the data processing system 12 to process data associated with any type of loan. The capability to process a new type of loan may be added by adding an additional attribute to a list of attributes corresponding to the new product feature (or modifying existing attributes), by using the attribute to indicate the presence or absence (and/or other characteristics) of the new feature in a particular loan, and by modifying the rules engine to incorporate additional rules regarding the new loan feature. It is not necessary to build a completely new data processing system for the new type of loan. This makes it easier to offer new types of loans which are more optimally configured to meet the needs of individual borrowers. An exemplary set of attributes is described at the end of this section.
  • With respect to time granularity, the [0029] data processing system 12 is capable of processing data using a much smaller time slice or update period than has been possible in the past. In the past, systems have typically been constructed around the assumption that servicers provide monthly reports which summarize loan activity that occurred during the previous month. The time slice for reporting has been one month and sub-monthly temporal data has been lost. In the data processing system 12, when information regarding new loans is received by the acquisition logic 28 and/or when information regarding loan payments is received by the servicer and investor reporting logic 30, this information preferably includes information regarding the date the loan was acquired, the date or dates within each month or other period other period on which a payment or other transaction is expected, and/or the date the payment was received. The time slice in the data processing system 12 is therefore one day (or less, if a smaller time slice such as AM/PM, hour, minutes, seconds, and so on, is used). The temporal information is stored and maintained in databases which are synchronized/commonly accessible by the acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32. As a result, the acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32 each have access to this highly granular temporal information regarding loan acquisitions and payments. The increased time granularity supports the above-mentioned capabilities to offer a wider array of loans to borrowers and a wider array of financial instruments to investors. For example, the increased time granularity facilitates offering loan products in which the borrower is expected to make bi-weekly payments, which may be attractive to borrowers that get paid bi-weekly instead of twice-monthly or monthly. This also facilitates handling loan products in which the date of a transaction is meaningful, such as daily simple interest loans. Further, because sub-loan cash flows can be processed using a one day time slice (or less), it is possible to create financial instruments based on cash flows that are processed on a per day basis.
  • Another benefit of the [0030] acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32 being provided on a common platform and having access to common/synchronized databases is that each system has an up to date view of the data. The data processing system 12 has the ability to accept payment and other transaction information from a servicer as such transactions occur (e.g., using daily, hourly, or near real-time updates) instead of or in addition to receiving end of the month summary transaction information from the servicer. Once the data is received, it is accessible throughout the data processing system 12. For example, it is not necessary to limit the data updates for the securitization logic to a once-per month basis at the end of a servicing cycle. Therefore, an up to date view of the data is available throughout the data processing system 12.
  • It should be apparent that it is also possible to construct data processing systems which do not incorporate the advantages described herein in connection with the [0031] data processing system 12, or which also incorporate additional advantages not described herein. Further, it may also be noted that the separation of functionality shown in FIGS. 1-6 is necessarily to some extent conceptual, and it is also possible to provide the same functionality in other ways. Additionally, although numerous functions are described below, it may be noted that it may be desirable to provide fewer, additional, or different functions in a given data processing system depending on the application and what is needed.
  • Referring now to FIG. 2, a preferred implementation of the [0032] user services logic 22 and its sub-components thereof will now be described. The user services logic 22 includes electronic registration logic 50, access and security logic 52, user experience logic 54, report request processing logic 62, and a notification processor 64. The registration logic 50 is used to register individual users to be able to use the data processing system 12. For example, an employee of a lender may be given a login name and password to access the data processing system 12. User registration preferably includes providing each user with an authorization profile that defines the extent and type of access the user is given to the data processing system 12 and the types of operations that the user may perform while accessing the data processing system 12. The access and security logic 52 cooperates with the electronic registration logic 50 to permit users to access the data processing system 12 in the manner authorized.
  • The [0033] user experience logic 54 provides a user interface to the data processing system 12. Preferably, the user accesses the data processing system 12 through the Internet or an Intranet by using a personal/laptop computer or other suitable Internet-enabled device. For example, the data processing system 12 may be accessible to users by visiting the purchaser's web site (that is, the web site of the entity that owns/operates the data processing system 12, and that is assumed to be in the business of purchasing, guaranteeing, and/or securitizing loans) and clicking on appropriate links located at the web site. Depending on the authorizations the user has been given in the registration logic 50, the user is able to access different web pages of the web site relating to the underwriting logic 26, the acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32. For example, there may be one or more web pages relating to acquisitions that may be accessed by lenders, one or more pages relating to servicing that may be accessed by servicers, and so on. The user may then perform functions in accordance with what is permitted by the user's authorization profile (which, in turn, is typically based on the user's employer and the user's job function for that employer). For example, an employee of a lender may be given authorization to access web pages associated with the acquisition logic 28 and commit the lender to deliver a quantity of loans on a future date (i.e., to engage in a forward commitment with the purchaser). The types of operations that different users may perform is described in greater detail in connection with FIGS. 3A-3B and 4-6 below.
  • The [0034] user experience logic 54 includes business application components 56, reference data 58, and user help logic 60. These components provide implementation support to the above-described user interface. The business application components 56 includes logic that assists directing a user to the correct web page. The reference data 58 may include data regarding user preferences for the appearance of web pages to the user. The reference data 58 may also provide general reference data and content that assists user interaction with the web site. The reference data 58 may also include data regarding particular lenders, such as the year the lender was first approved to do business with the purchaser, contact information for the lender, and performance information such as statistics and transfer history for the lender. The user help logic 60 provides other help or “How To” components.
  • The [0035] user services logic 22 also includes report request processing logic 62 and a notification processor 64. The report request processing logic 62 permits lenders and servicers to access the data processing system 12 and request reports generated from the data the lenders and servicers have provided the purchaser. The reports may be redefined “canned” reports, or may be ad hoc reports defined by the user by drilling down into the data and/or defining data filters. the type of reporting generation capability available may be made dependent on the type of user. The report request processing logic 62 may be used for incoming data in connection with lenders and servicers and/or for outgoing data in connection with investor reporting. Investor reporting may also be handled by other logic described below.
  • The [0036] notification processor 64 sends notifications/alerts to users. For example, the notification processor 64 may be used to send e-mail (or fax, automated telephone call, and so on) to a user associated with a servicer or lender indicating that data which has been submitted by the servicer or lender has been processed, and that the processed data is ready for review. The notification processor 64 is useful in the context of exceptions processing, when the lender/servicer data is processed but the processing indicates that there may be an error in the lender's/servicer's data which requires review by a human operator.
  • Referring now to FIG. 3A, a preferred implementation of the [0037] underwriting logic 26 and sub-components thereof will now be described. The underwriting logic 26 is typically accessed by users that originate loans, such as lenders and brokers. The underwriting logic 26 includes data capture logic 70, underwriting logic 74, and credit scoring logic 72. The data capture logic 70 is used to receive information to be used in loan underwriting and appraisal (e.g. information from a loan application and a credit report). Typically, the information that is received for loan underwriting is a subset of the information that would be provided on a loan application.
  • The [0038] credit scoring logic 72 and the underwriting logic 74 cooperate to analyze the information to determine if the loan meets credit risk and eligibility requirements of the purchaser or of a lender for the purposes of its portfolio, and then issue a recommendation based on the assessment of the overall risk profile of the loan. The credit scoring logic 72 generates a credit score of the loan applicant based on the loan applicant's credit history. For example, a credit report for the potential borrower may be obtained once the lender obtains authorization from the potential borrower.
  • Underwriting [0039] logic 74 combines the credit score with other information provided by the potential borrower to the lender to recommend whether to approve the loan. Such information may include, for example, one or more of the following: debt-to income ratios, appraisal value, income, borrower contribution, cash reserves of the borrower, loan-to-value ratio, loan purpose, loan term, loan type, property type, occupancy status and amount of subordinate financing, and other factors. Underwriting logic 74 stores the credit score and the other information and assigns a unique underwriting casefile ID to the lender and loan application for the particular borrower. The recommendation provided by the underwriting logic 74 indicates whether the loan meets the purchaser's credit risk and eligibility requirements. Preferably, the recommendation provides a message such as (1) “approved” or (2) “refer to help center” or like message regarding whether the loan meets the credit risk requirements. Underwriting logic 74 may also provide a message such as (1) “eligible” or (2) “ineligible” regarding whether the loan product meets the purchaser's eligibility requirements. For each loan, the underwriting logic 74 also preferably indicates (i) minimum income and asset verification requirements, (ii) credit related documentation requirements, and (iii) the required level of property field work necessary to complete the processing of the loan file. The underwriting logic 74 may produce the verification and approval requirements for referred loans as well as for loans recommended for approval.
  • If a loan submitted to the [0040] underwriting logic 74 receives a recommendation of “refer”, the underwriting logic 74 may also provide the lender with information identifying problem areas with respect to the borrower's application and suggested areas for improving the borrower's chances for approval (e.g., lower loan amount or reduce debt). In addition, the lender may refer the borrower to a help center to receive the benefit of such information and recommendations.
  • The recommendation provided by the [0041] underwriting logic 74 is stored with the associated data provided by the lender and borrower (hereinafter, the credit score, other information and the underwriting recommendation are referred to as “underwriting data”). The underwriting data may be stored in, for example, a database. A lender may resubmit a loan for underwriting (e.g., if property, loan or borrower information changes). Each time a loan is resubmitted to the underwriting logic 26, the underwriting data (including the underwriting recommendation and verification requirements) is updated to include the data from the most recent submission. The information received and generated by underwriting logic 26 is preferably available to the other sub-components of the data processing system 12 as discussed in further detail below with respect to FIGS. 4 and 5.
  • The [0042] underwriting logic 26 may also be used to generate reports that provide information regarding the underwriting recommendation for a particular loan, information used in determining the recommendation (e.g., property, loan, and borrower information), and information summarizing key statistics from the credit report (e.g., borrower's open accounts, derogatory accounts and undisclosed accounts).
  • Still referring to FIG. 3A, a preferred implementation of the [0043] acquisition logic 28 and sub-components thereof will now be described. The acquisition logic 28 further includes cash committing logic 80, deal management logic 82, lender eligibility logic 84, pricing logic 86, delivery logic 88, certification logic 90, and custody logic 92.
  • The [0044] cash committing logic 80 provides a facility for performing all cash commitment functions. Typically, a master agreement/contract may be in place between the purchaser and the lender which defines overall terms of loan sales to the purchaser pursuant to particular commitments. A cash commitment is an agreement (typically, governed by the overall master agreement) in which the mortgage purchaser agrees to buy mortgages from mortgage sellers (e.g., lenders) in exchange for a specified price in cash. Typically, a cash commitment agreement specifies the type of mortgage(s) the seller plans to deliver, the amount of time the seller has to make a delivery, the price the mortgage purchaser will pay the seller for the loan(s), other pertinent loan terms, and, in some cases, loan level details pertaining to the mortgage.
  • The [0045] cash committing logic 80 provides a central point for approved lenders (or other approved sellers) and the purchaser to perform all cash commitment functions. These functions may include, for, example, making standard forward commitments, handling pair-off of commitments, extending commitments, over-delivering of a commitment, maintaining configurable parameters, updating contact information, updating commitment records, viewing and selecting from a seller's favorite product list, adding to and maintaining the seller's favorite product list, viewing contracts, fees, prices, yield adjustments, and so on. As previously described, the access and security logic 52 verifies the identity of the user (using a login ID and password) and allows the user to gain access to the cash committing logic 80. Different types of users may be granted different levels of access to the cash commitment logic 80 (e.g., for different employees within a seller organization having different levels of authority to act on behalf of the seller).
  • In the preferred embodiment, the [0046] system 12 includes the ability to limit the different types of loans that a given seller may sell to a subset of the loans which the purchaser may purchase. The different products may comprise loans of different terms, different interest rates and types of interest rates (fixed or variable), as well as a variety of other features or combinations of features that may be offered in connection with the particular mortgage products. This information may be stored in the lender eligibility logic 84, described below, and the cash committing logic 80 may interface with the lender eligibility logic 84 to limit commitment activity to only those products that the seller is eligible to sell. During the committing process, the seller selects the type of product the seller plans to deliver from a list of eligible products. Sellers may be provided the ability to flag any eligible product as a “favorite,” and are able to select products from a favorites list when making commitments. Preferably, sellers are also provided with the option to assign their own marketing name for each eligible product in the seller's favorite list. In another embodiment, rather than selecting from a list of eligible products, sellers may be provided the ability to define a product they plan to deliver by defining the loan attributes.
  • The committing [0047] logic 80 provides sellers with the option to apply a commitment to a master agreement. Information regarding master agreements is supplied by the deal management logic 82 and displayed in the cash committing logic 80 for a given seller. The display may, for example, indicate valid master agreement numbers, the unfulfilled commitment amount in dollars for each master agreement, the expiration date for each master agreement, and/or other pertinent information.
  • The [0048] deal management logic 82 is used to store and track terms of the deals/contracts made between sellers of loans and the purchaser. When a seller contacts the purchaser to initiate negotiation of a new deal, an employee or other representative of the purchaser uses the deal management logic 82 to create a master agreement, MBS pool contract and all the associated variances.
  • During the master agreement negotiation process, all terms and stipulations of the agreement are entered into the [0049] deal management logic 82. The deal management logic 82 enables authorized users creating or modifying variances to identify editable variances and facilitates transforming “codeable” variances into business rules in the delivery logic. The deal management logic 82 also facilitates communication of these variances to users responsible for analyzing them. Users responsible for analyzing variances are provided a link to the edit engine where they are able to add, modify, or delete edits based on their analyses.
  • The [0050] deal management logic 82 also integrates with the pricing logic 86 so that loan level yield adjustments that reflect negotiated variances may be entered and displayed in the generated master agreement. The seller's specific adjustment tables (referencing master agreement and variance reference numbers) may also be stored in the deal management logic, or, more preferably, in the lender eligibility logic 84.
  • The [0051] lender eligibility logic 84 is logic that maintains information regarding the eligibility of particular lenders to offer particular products made available by the purchaser. The lender eligibility logic 84 allows users (via web interface) to maintain and update product or lender-specific parameters in connection with the committing logic 80, the delivery logic 88, the certification logic 90, the custody logic 92, and the servicer and investor reporting logic 30. The lender eligibility logic 84 may also be used to set pricing incentive adjustments, yield adjustments, fees and other parameters at the lender and product levels.
  • The [0052] pricing logic 86 is the logic used to generate pricing information and provide information to other logic in the data processing system 12, including the underwriting logic 26, the committing logic 80, the delivery logic 88, the certification logic 90, the custody logic 92, and the servicer and investor reporting logic 30. For example, the pricing logic 86 may be accessed during delivery to determine the price to be paid for a particular loan, or after the loan is delivered to determine how changes/corrections in loan information affect pricing. The pricing logic 86 takes into account pricing elements such as commitment/interest price (based on interest and the type of commitment), commitment calculations (e.g., for yield adjustments associated with pair-offs, over delivery, extensions), and credit adjustment price (based on loan level credit risk). In addition to cash pricing (i.e., pricing in situations where the loan is paid in cash), the pricing logic 86 may also be used for MBS pricing (i.e., pricing in situations where the loan is paid for using a mortgage backed security). The pricing elements related to MBS includes the guarantee fee, the buy-up/buy-down amount and the credit adjustment amount.
  • The [0053] pricing logic 86 interacts with the delivery logic 88 (described in greater detail below) when a seller is unable to fulfill the terms of its original commitment to generate yield adjustments associated with pair-offs, over delivery, and extensions. The pricing logic 86 acquires delivery and under delivery tolerance amounts from the lender eligibility logic 84, processes data from a commitment inventory database to locate expired commitments and under deliveries, based on input from the delivery logic 88. The pricing logic 86 also processes data associated with the original commitment parameters to generate yield adjustments. Additionally, yield adjustments may also be assessed at the time of delivery for credit risk in connection with one or more loans that exceeds a pre-determined and agreed-upon level. In particular, at the time a cash commitment or MBS deal is made, a certain level of credit risk is assumed when determining the cash price or MBS guarantee fee. Later, when loans are actually delivered, the true risk level is identified. If the cash price or MBS guarantee fee does not account for this actual level of risk, a yield adjustment is made. The system allows the option of selecting either an upfront loan level yield adjustment at the time of delivery or a guarantee fee basis point adjustment to permit the payment to be made over time.
  • The [0054] pricing logic 86 also interacts with the servicer and investor reporting logic 30 when there are loan level changes during the servicing of the loan that result in a request for pricing. The servicing logic 142 sends the pertinent data attributes needed for pricing to the pricing logic 86 and the pricing logic 86 returns pricing information for the loan in question.
  • The [0055] pricing logic 86 may also be used to access prices set forth in pricing grids that store pricing information as a function of various loan parameters and/or features, e.g., interest rate and remaining term in connection with a particular seller. The pricing grids may be generated manually (e.g., in a spreadsheet which is provided to the pricing logic 86) or automatically. The pricing logic 86 may also be used to generate reports regarding pricing information.
  • The [0056] delivery logic 88 is the logic used to process loans when loans are delivered to the purchaser in connection with a purchase. The delivery logic 88 analyzes loan attributes, the associated deal/contract with the seller, and execution parameters to determine if the loan is acceptable for submission under the terms and conditions of the deal. The delivery logic 88 also invokes the pricing logic 86 to determine the price and/or yield adjustment associated with accepting the loan. The delivery logic 88 also allows sellers to set up pools in cases where the loans are pooled in MBS.
  • The [0057] delivery logic 88 receives electronic loan data (hereinafter referred to as “delivery data”) by way of the users services logic 22 or the transaction exchange processor 24. The purchaser will generally also receive paper loan documents that support the electronic loan data received by the data processing system 12.
  • The [0058] delivery logic 88 utilizes aspects of the underwriting logic 26, the deal management logic 82, and the pricing logic 86. Each loan that is delivered is checked against business rules and data format rules. Business rules are based on the product, pool/piece/contract, pricing, commitment, and other factors. For example, a seller may inadvertently try to deliver a 15-yr loan in connection with a commitment for 30-yr loans, and the business rules provide a mechanism for identifying that the 15-yr loan can not be used to satisfy that commitment. The delivery logic 88 uses the notification processor 64 to notify the seller when/if the data that is being delivered does not match the commitment.
  • The [0059] delivery logic 88 is also integrated with the underwriting logic 26. FIG. 4 shows a block diagram of the delivery logic and underwriting logic of the system of FIGS. 1 and 3A. As discussed above, underwriting data including the underwriting recommendation) for a particular loan is assigned an underwriting casefile ID and may be stored in a database 406. The delivery loan data for a particular loan to be delivered may be assigned a unique loan ID and stored in a database 406. Delivery logic 88 and underwriting logic 26 preferably communicate to share data to perform various functions, such as (i) populate a loan delivery template of the delivery logic 88, (ii) confirm that the loan being delivered meets underwriting criteria, and/or (iii) determine if the delivery data for a loan that was also underwritten using underwriting logic 26 is the same as the underwriting data provided for the loan.
  • When a seller is entering delivery data for a loan being delivered via [0060] delivery logic 88, much of the information required is the same as the information required by underwriting logic 26. As discussed above, the information received for loan underwriting is typically a subset of the information that would be provided on a loan application. If the loan was underwritten using underwriting logic 26, a seller may provide an underwriting casefile ID to the delivery logic 88. Delivery logic 88 may then send a request to the underwriting logic 26 to transfer the current underwriting data associated with the underwriting casefile ID in the database 406 to the delivery logic 88. In an alternative embodiment, the delivery logic 88 may directly access the underwriting data associated with the underwriting casefile ID in the database 406. The underwriting data transferred may include one or more of the following: borrower social security number, co-borrower social security number (if applicable), property address, loan amortization type, loan guarantor type, number of units, loan processing method, employment information, loan type, underwriting results, loan term, LTV, CLTV, borrower reserves, and so on.
  • The underwriting data may be used to populate a delivery template presented to a seller delivering the loan by, for example, a web interface. Preferably, the underwriting data is identified (e.g. italicized or shaded) so the seller can identify the data obtained from the [0061] underwriting logic 26. The seller, therefore, does not have to reenter loan data previously entered during the underwriting process. In addition, the seller can review the underwriting data to ensure that it is accurate. The seller, preferably, can edit or update the underwriting data, if necessary. For example, the underwriting data may be edited by way of a computer system with a user interface to receive inputs regarding the underwriting data. If a seller does not provide an underwriting casefile ID or if the loan being delivered was not underwritten using underwriting logic 26, the seller will have to enter all of the loan data required for delivery of the loan. The seller may enter the loan data using, for example, a keyboard or other input device in conjunction with a computer system.
  • If a loan being delivered was not previously underwritten using [0062] underwriting logic 26, delivery logic 88 may interact with underwriting logic 26 to confirm the loan being delivered meets the underwriting criteria of the purchaser. Delivery logic 88 may transfer delivery data provided by the seller at delivery to the underwriting logic 26. Underwriting logic 26 will then process the delivery data relevant to providing an underwriting recommendation, as described above, to provide an underwriting recommendation. Underwriting logic 26 then returns underwriting data (including the underwriting recommendation) to the delivery logic 88. The underwriting data and, in particular, the underwriting recommendation, may be provided to the seller using notification processor 64 (FIG. 2). In addition, the underwriting data may be used by the pricing engine 86 (FIG. 3A) to determine a price for the sale of the loan.
  • [0063] Delivery logic 88 also includes comparison logic 410. Generally, certain terms of the delivery data of a closed loan being delivered to the purchaser (e.g., occupancy type, product type, amortization type, loan term, property type, loan purpose, property sales price, appraised value, etc.) should match the underwriting data provided to the underwriting logic 26. If certain material terms do not match there may be an impact on the underwriting decision and the price and/or price changes (e.g., credit related yield adjustments or fees) the seller will be charged. Preferably, material terms are determined using the business rules, i.e., business rules may be created which identify what terms are material. Accordingly, comparison logic 410 permits the comparison of the underwriting data for a particular loan to the delivery data provided for the loan to determine any differences.
  • In an alternative embodiment, [0064] comparison logic 410 may be implemented as a separate system from the delivery logic 88 and the data processing system 12., Accordingly, comparison logic 410 may be configured to compare the underwriting data for a particular loan (as provided by underwriting logic 26 and database 406) to loan data provided by an external data source (i.e., a data source that is not related to the data processing system 12). For example, a loan sale transaction may occur between two lenders, e.g., a loan originator and a warehouse lender. Alternatively, a lender may sell a loan it owns but did not originate. the loan originator may use underwriting logic 26 to underwrite the loan and the warehouse lender (or purchaser) may wish to compare the loan data provided by the loan originator to the underwriting data before purchasing the loan.
  • FIG. 5 illustrates a comparison process for the [0065] comparison logic 410. At block 510, the delivery data for the loan being delivered is provided to the delivery logic 88. As mentioned above, delivery logic 88 receives electronic loan data from a seller by way of user services logic 22 (FIG. 1) or the transaction processor 24 (FIG. 1). If the loan does not have an underwriting casefile ID (decision 504), the delivery process proceeds as described with respect to FIG. 3A. Preferably, if the loan does not have an underwriting casefile ID (i.e., the loan was not underwritten using underwriting logic 26), the loan is submitted to underwriting logic 26, as described above, to determine whether the loan meets the purchasers underwriting criteria.
  • If the loan has an underwriting casefile ID (decision [0066] 504), the delivery logic 88 sends a request to the underwriting logic 26 to retrieve the underwriting data associated with the underwriting casefile ID at block 508. Underwriting logic 26 returns the underwriting data associated with the underwriting casefile ID to the delivery logic 88. As mentioned above, in an alternative embodiment, the delivery logic 88 may directly access the underwriting data associated with the underwriting casefile ID in the database 406. The underwriting data and delivery data are then compared to determine any differences in a predetermined set of information (e.g., loan, borrower, and property information) at block 510. If the predetermined set of loan information of the underwriting data and the delivery data are the same (decision 512), the delivery process proceeds as described herein with respect to FIG. 3A at block 514. If the predetermined loan information from the underwriting data and the delivery data are different (decision 512), it is determined whether the differences are material to the underwriting decision or the price and/or any possible credit related adjustments for the loan (decision 516). As discussed above, whether a difference is material is preferably determined using the business rules. If the difference is material (i.e., the difference will impact the underwriting decision and price and/or credit related adjustments), delivery logic 88 invokes pricing logic 86 (FIG. 3A) to determine the price and/or price changes (e.g., any credit related yield adjustments or fees) at block 518. Delivery logic 88 may also invoke underwriting logic 26 to underwrite the loan based on the delivery data provided by the seller.
  • At [0067] block 520, the comparison results may be provided to the seller and/or the seller may be notified using the notification processor 64 (FIG. 2) when the predetermined set of information from the delivery data does not match the underwriting data and whether there is an impact on the underwriting decision and the price as well as any additional fees (e.g., credit related adjustments) that may be charged. Preferably, the seller has the option to edit the delivery data provided (e.g. if the seller made an error entering the delivery data). For example, the underwriting data may be edited by way of a computer system with a user interface to receive inputs regarding the delivery data. If the seller does not edit the delivery data (decision 522), the delivery process proceeds as described herein with respect to FIG. 3A at block 524. If the seller does edit the delivery data (decision 522), the process returns to block 510 and the edited delivery data is compared to the underwriting data. Also, the seller may decide not to deliver the loan based on the comparison results or the purchaser may decide not to purchase the loan based on the comparison results.
  • If the difference between the delivery data and the underwriting data are not material (decision [0068] 516), the seller preferably has the option to edit the delivery data (e.g. if the seller made an error entering the delivery data into the system). If the seller does not edit the delivery data (decision 526), the delivery process proceeds as described herein with respect to FIG. 3A at block 528. If the seller does edit the delivery data (decision 526), the process returns to block 510 and the edited delivery data is compared to the underwriting data.
  • In another embodiment, a lender may compare underwriting data for a loan with loan data provided by a broker from a loan origination system (hereinafter referred to as “loan origination data”). Loans may be originated by a broker who, once the loans have closed, provides the loans to a lender for funding. As described above, the lender can then either: (i) hold the loans as investments in its portfolio, or (ii) sell the loans to investors in the “secondary mortgage market” to replenish its supply of funds. Alternatively, a lender may wish to evaluate its loan portfolio by comparing the loan data for loans already in the portfolio to underwriting data for the loans. Such an evaluation may be performed as part of, for example, a decision to sell loans from the portfolio to the secondary market, a quality control process, due diligence, etc. Other parties with an interest in a transaction involving a loan may also wish to evaluate the loan by comparing the current loan data to underwriting data for the loan. [0069]
  • Underwriting [0070] logic 26 may be used by the broker to underwrite a loan as described above. When a loan is submitted to the lender by a broker, including the loan origination data, the lender may wish to determine if the loan origination data (or a predetermined subset of the loan origination data) is the same as the underwriting data (or a predetermined subset of the underwriting data) for the loan before accepting the loan from the broker. It possible that the loan data used to underwrite the loan may change before the loan is provided to the lender (e.g., due to continued negotiations between the broker and the borrower). The underwriting data for a loan, identified by an underwriting casefile ID, may be accessed using, for example, user services logic 22 (FIGS. 1 and 2). The lender may then compare the underwriting data to the loan origination data provided by the broker. The broker may provide the loan origination data, for example, electronically or using physical documents. If there are differences between the underwriting data for the loan and the loan origination data for the loan, the lender may decide not to accept the loan from the broker.
  • In yet another embodiment, a purchaser such as a wholesaler or warehouse lender, may compare underwriting data for a loan with loan data provided by another lender (or seller). Loans originated by one lender may be sold to another lender, e.g. a wholesaler or warehouse lender. Alternatively, a lender may also sell loans it owns but did not originate. the purchaser may wish to determine if the loan data submitted by the lender is the same as the underwriting data for the loan before accepting the loan. The process for comparing the loan data and underwriting data is similar to that described above with respect to the broker/lender embodiment. [0071]
  • Returning to FIG. 3A, the [0072] delivery logic 88 allows the user to edit the delivery data for format/field edits and standard/custom edits necessary to deliver loans to the purchaser. Users have a real time view of updates to the delivery data in order to resolve data errors before the loan is purchased or securitized. For example, if the data indicates that a 15-yr loan is being used to satisfy a commitment for a 30-yr loan, the user may edit the data to indicate that the loan is a 30-yr loan (in a situation where the loan data as incorrectly entered and what was originally indicated as being a 15-yr loan is in fact a 30-yr loan). Alternatively, the user may edit the data to instead apply the 15-yr loan to a different commitment for a 15-yr loan. As a further alternative, the user may edit the data to substitute a 30-yr loan for the 15-yr loan. The delivery logic 88 also includes logic for address correction (detecting erroneous address information and correcting the address information) and geographic coding (to provide additional geographic information on the property, such as longitude and latitude, tract, congressional district, metropolitan statistical area number, and so on). By the end of the process, the delivery logic also generates a unique loan number for each of the loans for tracking purposes.
  • The [0073] certification logic 90 is logic that supports the process of ensuring that all loan documentation is complete and legally binding and that the paper documentation matches the electronic information delivered by the seller. The certification logic 90 generates, stores and makes available to other aspects of the data processing system 12 information pertaining to which loans have been certified. The certification logic 90 is also able to generate custom reports regarding certification data including reports on loans that have not been certified so that appropriate action may be taken (e.g., having the seller repurchase the loan). The certification logic 90 facilitates data modification and facilitates data matching when loans are redelivered or resubmitted. The certification logic 90 also generates repots to support management decisions with respect to certification activities.
  • The [0074] custody logic 92 is logic that is used to support the custody process, or the process whereby the purchaser stores the paper loan documents during the time from when the loans are purchased or securitized until they are released. Custody protects the physical evidence of investment in negotiable assets. The custody logic 92 manages custodial profile/contact information, custodian/seller relationships, and seller/servicer profile/eligibility information related to custody activities. The custody logic 92 also permits information to be retrieved regarding loan investors. If the market purchaser performs the custody function itself rather than having a third party act as custodian, the custody logic 92 also supports document management in connection with incoming and outgoing documents. In particular, the custody logic 92 tracks when loan documents are in the possession of the purchaser and otherwise manages and monitors the position of the physical loan documents. The custody logic 92 also manages and calculates fees charged for custodial and certification services.
  • The [0075] acquisition logic 28 may also include other logic in addition to the logic described above. For example, the acquisition logic 28 may further include payable/receivable manager logic to track the billing of yield adjustments and fees generated by transactions in the committing logic 80, the pricing logic 86, the delivery logic 88, the custody logic 92, and certain aspects of the servicer and investor reporting logic 30. The payable/receivable manager logic may also be used to display the status (including payment status) of such yield adjustments and fees in a consolidated manner.
  • Referring now to FIG. 3B, a preferred implementation of the servicer and [0076] investor reporting logic 30 will now be described in greater detail. The servicer and investor reporting logic 30 includes loan process and compare (LPC) logic 100, which monitors and verifies the activities of third party mortgage servicers on an ongoing basis. Alternatively, if servicing is performed internally by the owner of the data processing system 12 and is included as part of the servicer and investor reporting logic 30 or as part of another functional block of the data processing system 12, the LPC logic 100 may be used to verify internally generated reporting information. Thus, the LPC logic 100 performs such operations as receiving and validating reporting information pertaining to loan activity, loan delinquency information and unpaid balance comparison reported by the servicer, updating the records of the data processing system 12 regarding the status of all reported loans, and determining the remittance and disbursement amounts that are expected for the loans.
  • As an initial matter, prior to loan servicing, a comparison is performed of the servicer's data for loans being serviced with the purchaser's data for the same loans. Even if the purchaser's data has already been compared with lender data for the same group of loans, the servicer's data may for some reason be different. Accordingly, the purchaser may provide a predefined set of acquisition data to the servicer that the servicer can compare with the servicer 's data. At any time thereafter, the servicer may perform individual queries of the loan data stored on the purchasers data base via the user services logic [0077] 22 (web interface) and download the data for further comparison purposes. When exceptions are noted, the servicer can correct its data or submit a change request via the user interface to the attribute change processor (ACP) logic 122, described below.
  • During the life of the loan, when loan activity occurs (e.g., when the borrower makes loan payments), the [0078] LPC logic 100 is executed with regard to a particular loan when a servicer reports transactions to the purchaser. A loan activity processor 102 handles expected and scheduled servicing transactions including payments, rate changes, curtailments, and so on. The activity processor 102 receives and validates loan transaction data, such as loan activity, unpaid balance comparison, and delinquency status updates. The activity processor 102 also can be configured to check for duplicate transactions, validate servicer information, determine and validate the type of loan transaction, and validate that the loan activity is being reported in the correct reporting period. The activity processor 102 also confirms that changes in unpaid balance and last paid installment are correct, derives expected interest remittance, derives expected principal remittance, and compares the derived amounts to the reported remittance amounts. After validation, the status of the loan is made available to the servicer through the user services logic 22. The activity processor 102 also triggers the appropriate cash and accounting transactions in a book and tax accounting processor 146. When loan activity is processed and does not match the purchasers expectations based on rules and calculations, exceptions are noted and communicated to users using the notification processor 64.
  • The amortization/[0079] calculation processor 104 is used by the activity processor 102 to calculate loan level amounts, such as principal and interest due, servicing fees and other data pertinent to each loan. Processor 104 may additionally be used to compute derived or decomposed cash flows, such as a guaranty fee or a servicing fee. Business rules are used to identify scheduled and unscheduled principal, calculate fees, calculate remittance and disbursement amounts, calculate amounts to be disbursed to investors, amortization, and accruals. These calculations are used throughout the system 12 to perform functions such as collecting remittances from servicers, dispersing funds to investors and performing accounting activities. The results of processing are available through an interactive user interface to both personnel of the purchaser and personnel of the servicer for correction when transactions do not comply with business rules.
  • The [0080] trial balance processor 106 provides for validation of parameters such as servicer number, purchaser and servicers loan numbers, effective date, ending unpaid balance, note rate, pass through rate, principal and interest payment, last paid installment (LPI) date, pool number, accrued interest receivable balance, available line of credit, conversion date, reverse mortgage payment, net principal limit, taxes and insurance set asides, property charges set asides, repairs set asides, servicing fees set asides, scheduled payments, and so on. Any discrepancies are resolved and any system updates (loan attribute changes, data updates) are implemented. The LPC logic 100 then reprocesses the activity based on the corrected data.
  • In addition to borrower payments, the [0081] LPC logic 100 may also be triggered with regard to a particular loan when the attribute change processor (ACP) logic 122 makes a change to attributes that affect loan processing or when a loan attribute triggers processing, such as note rate changes, payment changes and loan reporting. The LPC logic 100 may also be triggered by borrower behavior (e.g., loan delinquencies status) at beginning and end of accounting periods.
  • The [0082] servicing event processor 108 identifies and handles business events that are not identified by the activity processor 102. Examples of these events include identifying delinquent loans and identifying loans that are eligible for reclassification or substitution. The delinquency status reporting processor 110 accepts delinquency reasons from the servicer for loans that have payments that are in arrears.
  • The attribute change processor (ACP) [0083] logic 122 processes loan or security level changes. ACP logic 122 processes attribute changes regarding loans. As previously described, in the preferred embodiments, loans are characterized in the data processing system 12 by a series of attributes rather than by product codes. Each mortgage product that is purchased is then represented by a series of attributes instead of or in addition to an overall product code. New products may be created by creating new combinations of attributes, or by adding new attributes. An exemplary list of possible attributes that may be used is provided at the end of this section.
  • [0084] ACP logic 122 processes attribute changes that occur after loans are brought into the data processing system 12. In particular, after loans are brought into the data processing system 12, the ACP logic 122 processes attribute changes that are unexpected or are unscheduled whereas the LPC logic 100 handles attribute changes that are both expected and scheduled. The ACP logic 122 also validates the attribute change request, assesses the financial impact of the change, updates the appropriate data and triggers the appropriate cash and accounting transactions.
  • Unexpected attribute changes are changes that are required due to new features or discrepancies between contract documentation and data captured by the [0085] acquisition logic 28, this can include changes to loan data and/or changes in loan behavior. Unscheduled attribute changes are changes that may occur based on contract documentation but the timeframe is unknown. For example, an unexpected attribute change would be a change for a daily simple interest cash loan that the purchaser has purchased without knowledge of a particular feature. After the purchase, the borrower exercises options under the feature and the servicer advances the next due date of the loan and submits a loan activity transaction record to the purchaser. Not knowing about the feature, the purchaser rejects the transaction since the loan record does not indicate the presence of the feature. After assessing the exception and evaluating the change, the servicer submits an attribute change request to add this feature and keep the loan in the purchaser's portfolio or in the security, pending confirmation of continued loan eligibility. An example of an unexpected and unscheduled attribute change would be the case where the lender submits an adjustable rate mortgage change request for a loan that the purchaser has set up as a fixed rate mortgage. The request is processed as an unscheduled change because the purchaser's systems have never had an event scheduled to trigger the change. An example of an unscheduled change is a fixed rate convertible loan which has the conversion option indicated in the terms of the note. It is anticipated that an attribute change will occur but the timing of the event is unknown and therefore unscheduled. The two primary types of unexpected attributed changes are post purchase adjustments (data corrections) and modifications (attribute changes driven by a number of business requirements, such as product flexibility, delinquency management, and substitutions/reclassifications).
  • In operation, the [0086] ACP logic 122 receives attribute change requests which indicates current database values for the loan and the proposed changes. The validation of the loan with the new values is then accomplished by applying the rules processor 180 (FIG. 6) to the ACP transaction. The business rules engine is applied to determine whether the changes are allowable and any failed business rules are provided to an operator for further review. Next, the original terms of the contract are used to determine any pricing adjustments of the attribute change. The system determines the difference between the current or adjusted price as applicable and the new price for the purchase adjustments. Next, a human operator reviews the requested change, the impact of the requested change, and any required hard copy documentation needed to justify the change. The operator/business analyst either approves or rejects the change. Rejected transactions may be modified and resubmitted. Approved adjustment transaction values are applied to the database and an audit trail history is maintained. If the result of the change request has an accounting impact, the ACP logic 122 also generates the appropriate transactions to trigger the accounting processor 146.
  • The [0087] ACP logic 122 also includes loan conversion request processing logic 338 for handling loan conversion requests. Thus, when a loan conversion request is received, this logic tracks the request for the change, determines the allowability of the change based on business rules, and employs the remainder of the ACP logic 122 to make the change.
  • The securities aggregation and management (SAM) [0088] logic 130 receives the loan level cash flow information produced by the LPC logic 100 and aggregates this cash flow information to produce security level information. The security level information is produced at each of the following levels: remittance/express date level within each piece/single pool; single pool level or piece level within each major pool; pseudo pool (pool-like reporting group) level; major header level for each major pool; choice pool level; strip level; mega pool level; and mega in mega (MIM) pool level. In addition to securities, the SAM logic 130 is also capable of processing and managing any grouping of loans, cash flows from loans, and other financial instruments. Using a packet activity processor 132, the SAM logic 130 determines the loans in a given pool, aggregates cash flows based on the pool and loan level attributes for all the loans and then updates the system database. The packet activity processor 132 has the flexibility to aggregate loan level cash flows at the most granular level to security level enabling the SAM logic to also manage specific cash flow strips (e.g., access yield strips, interest only strips). At the end of appropriate processing periods, the SAM logic 130 finalizes the relevant security information. The SAM logic 130 then uses a packet disclosure processor 134 to make final remittance level principal and interest, guaranty fee, and other draft amounts available to a cash processing logic 144 and to make security accounting data available to a book and tax accounting logic 146. The SAM logic 130 also calculates, at the various MBS security levels, disclosure data for investors and the payment distribution to investors. The SAM logic 130 also includes packet modification request processing logic which is used to modify packets in generally the same manner that the attributes of loans are modified as described above in connection with the ACP logic 34. The operation of the SAM logic 130, and in particular packets and the packet activity processor 132, is described in greater detail in connection with the packeting logic 154.
  • Further, the [0089] SAM logic 130 can be used to facilitate the provision of real-time data updating. For example, investors may be supplied with real-time analytic data. the analytic data may include any data that allows investors to more accurately determine the value of their holdings, such as data concerning monthly loan payments, loan prepayments, loan pay-offs, and so on. For example, when a loan pays off, investors may be provided immediate access to this information rather than waiting until the next MBS reporting cycle.
  • In the illustrated embodiment, the servicer and [0090] investor reporting logic 30 and the securitization logic 32 utilize the same data base (see FIG. 6). As a result, the data used by the securitization logic 32 is always synchronized with the data used by the servicer and investor reporting logic 30. Thus, it is not necessary for the securitization logic 32 to wait until the end of a periodic (e.g., monthly) reporting cycle to receive updated data, but rather the securitization logic 32 always has access to up-to-date loan information. In another embodiment, the servicer and investor reporting logic 30 and the securitization logic 32 may utilize different data bases that are synchronized on a weekly basis, on a daily basis, on a sub-daily basis, or in real time, depending on the frequency of update that is desired.
  • A [0091] servicing transfer logic 142 facilitates the process of transferring loans for the servicing rights of owned or securitized mortgages from one servicer to another or from one portfolio to another within the same servicer as of an effective date. A servicing transfer may be initiated, for example, if a servicer decides to stop servicing loans for business reasons, if a servicer decides to transfer a certain group of loans to another branch or portfolio, if a servicer is involved in a merger or acquisition of the servicer necessitating a transfer to the surviving entity, or for other reasons. The servicing logic 142 processes information regarding the old and new servicers and the loans that are subject to the change in servicing and updates loan record data for the respective affected loans. The effective date of the change in servicing is also specified. Information that is provided to the servicing transfer logic 142 as part of a servicing request includes the transferors servicer number, address and contact information, the transferees servicer number, address and contact information, unique loan numbers to be transferred, effective date, and other data. Additional steps, such as notifying the transferor of the termination and assessing transfer fees may also be performed.
  • The [0092] cash processor 144 provides a facility to allow servicers and other vendors to create and maintain bank account information. The accounts are bank accounts established with the purchaser to facilitate loan transactions. Servicers have the ability to create/select/update their account information in real time, including account numbers and remittance/disbursement information. The information captured in this process allows the cash processor 144 to create and execute Automated Clearing House (ACH) transactions. Historical records of servicers and vendors account and draft information is maintained to assist in resolving any issues that may arise.
  • Additionally, the [0093] cash processor 144 retrieves remittance and disbursement information from other areas of the data processing system 12. The remittance and disbursement information includes effective date, loan number, dollar amount, remittance code, and granular level details. The cash processor 144 performs a rollup of loan level details by servicer number as required. The cash processor 144 also performs a rollup of loan level details by seller number whenever the seller is not the designated servicer. The cash processor 144 triggers appropriate accounting transaction codes as needed that allow the book and tax accounting processor 146 to record applicable accounting entries.
  • Finally, the [0094] cash processor 144 creates cash transactions, for example, automated clearing house (ACH) transactions, outgoing check transactions, and so on. The cash processor 144 begins this process after the cash processor 144 has completed the process of assessing and validating remittance and disbursement data. The first step in creating a cash transaction is validating servicer/vendor bank account information. Ultimately, an ACH transaction is created that debits or credits the appropriate custodial bank account
  • The book and [0095] tax accounting logic 146 manages accounting activities associated with the loans. The accounting logic 146 provides a consistent methodology for the recording of accounting events related to mortgage business activities across the acquisition logic 28 and the servicer and investor reporting logic 30 into subsidiary ledgers for posting to a general ledger. The book and tax accounting logic 146 supports the accounting activities related to the packaging of loan cash flows to the first level packet for the securitization logic 32. In addition, the book and tax accounting logic 146 supports the accounting activities related to forming securities or packets out of portfolio loan collateral. The investment accounting for securities held in portfolio and for the payment distribution on mortgage derivatives could also be handled by the book and tax accounting logic 146 or, preferably, is handled by separate accounting logic 156, described in greater detail below
  • The book and [0096] tax accounting logic 146 journalizes mortgage related business activity, maintains subsidiary ledgers, provides audit trails, provides data integrity and control within the subsidiary ledgers, facilitates timely reconciliations, provides flexibility to account for new products or changes depending on actual accounting methodologies, and provides information needed to perform financial analysis. In one embodiment, the book and tax accounting logic 146 utilizes an accounting matrix which is a two-dimensional structure comprised of accounting “families” and “family members.” The families are groups of accounting relevant transaction and loan attributes, and the family members are the allowable values for each of the groups. All intersections of families and family members have a debit and credit account number associated with each of the intersections. When the journal entry is created, the appropriate debit and credit account numbers are first assigned to each of the transactions as they are processed. The accounting matrix uses business rules processor 180 to automatically interpret the transactions. As new products are introduced, the accounting matrix is modified to incorporate new family and/or family members to properly record the new business activity. Similarly, as products become obsolete, or as the requirement for breaking out activity on the corporate general ledger becomes less detailed, the accounting matrix can be modified to adapt to those changes as well.
  • As business activities are processed, they are recorded/journalized in a subsidiary ledger according to the debit and credit account numbers assigned from the accounting matrix. This occurs by translating business activities into family and family member transactions that can be interpreted by the matrix. A subsidiary ledger provides the capability to view the lowest level of business activity that created the entry in the subsidiary ledger to maintain an audit trail for the subsidiary ledger activity. As activity is recorded, a system walk forward test of the subsidiary ledger balances is also performed to assure data integrity with the subsidiary ledger. At the end of accounting cycles, activity within the subsidiary ledgers is automatically summarized and posted to the general ledger [0097]
  • At the end of the accounting cycle, reconciliation is performed between the subsidiary ledger activity and balances, and the general ledger activity and balances using an automated reconciliation tool. An automated reconciliation tool may be provided that generates the results of the reconciliation and, through a user interface, displays the results to an operator. Any reconciling items between the subsidiary and general ledgers may be analyzed and resolved by the operator. Through the operator interface, the operator updates the status of the reconciling items to indicate the results of the analysis. As reconciling items are resolved, the operator triggers the automated reconciliation facility to repeat the reconciliation and display the results. [0098]
  • The book and [0099] tax accounting logic 146 also provides information for financial and operational analysis. Information related to the status of the book and tax accounting logic is provided to operations through an accounting console. The accounting console is a management and operational workflow tool that includes notifications and status information related to the book and tax accounting processes. It also provides summarized reports and the ability to view the detailed information supporting those reports.
  • A preferred implementation of the [0100] securitization logic 32 and sub-components thereof will now be described. The securitization logic 32 includes sifting/sorting logic 152 which accesses inventory, identifies collateral or asset attributes and sub-attributes, and categorizes data at its most granular level in both aggregating and segregating cash flows associated with mortgage assets. The sifting/sorting logic 152 provides a user interactive application that allows users to define selection criteria (loan and/or atomic characteristics), prioritize them, evaluate results, and make decisions about market transactions and their related economics. By sifting and sorting through available inventories, cash flows may be qualified and quantified for optimal aggregation of targeted transactions, given relative market value. The sifting/sorting logic 152 operates under a user maintainable library of business rules associated with mortgage instruments and respective cash flows. An auto sift function is also provided to allow to batch processing of predefined inventory types. For example, a daily auto sift may be executed against “available for sale” loans to aggregate and pre-packet the loans for future transactions.
  • The purpose of the sifting/[0101] sorting logic 152 is to provide a mechanism by which users can examine the entire collateral universe and pair down to smaller groupings of collateral or assets within the universe. Collateral refers to any cash flow derived from loans, pools, securities, commitments, and packets. The purpose of sorting is to group the subset of collateral identified in the sifting process and organize it by a single or multiple attributes to further refine the pool of candidate collateral to be placed into a potential packet. The sifting/sorting logic 152 supports the packeting logic 154, described below.
  • The [0102] packeting logic 154 is used to create, maintain, and otherwise support packets. A packet is an aggregation or packaging of cash flows that is treated as an entity separate and distinct from the incoming cash flows that support the packet and from the cash flows that result from the packet. Packets maintain the data integrity of the underlying assets as received by the LPC logic 100 and create an information chain that maps to a higher-order asset (e.g., an MBS or other financial instrument to be sold to an investor). The source data for packets may be loan-level or packet-level information, and the packets themselves may represent actual securities or just a unit of reporting and remittance.
  • Packets permit the [0103] data processing system 12 to enable and support new transactions by providing a platform for sourcing, normalizing, and centralizing cash flow-related data and building the linkages between loan assets and securities or non-securitized assets. Packets provide greater flexibility in the transformation of cash flows from the primary mortgage/loan level to the secondary market and within the secondary market. Packets provide the flexibility-not only to create and sell securities to investors but also to support non-securitized forms of packaging to enable selling or retaining cash flows from individual loans. The ability to create and manipulate packets enables the creation of new types of financial instruments and new types of transactions within the secondary market.
  • The [0104] accounting logic 156 supports additional accounting functions for the securitization logic 32 that are not already supported by the book and tax accounting processor 146. In general, the book and tax accounting processor 146 is responsible for performing maintenance accounting at the loan level (i.e., posting transactions), while the accounting logic 156 is responsible for the accounting logic associated with transformative accounting events. Transformative accounting events include, for example, securitization events (in which a loan is to be construed to be sold). Other transformative events include a securitization event in which only a portion of the cash flows are sold, a sale event of a portfolio securities, and a sale event involving a whole loan. In addition, the accounting logic 156 is responsible for ongoing maintenance in connection with the reconciliation of securities cash payables. The accounting logic 156 performs such things as deriving the initial cost basis at the time of acquisition for every loan and inventory, maintaining the cost basis of each loan, tracking accounting intent for each loan, and performing market valuation for each loan. Of course, although the functionality of blocks 146 and 156 are shown as being conceptually separate, this functionality could also be combined.
  • The position monitor [0105] 158 allows monitoring of the purchaser's overall trade and investment position. Particularly, the position monitor 158 is an interactive tool that is usable to monitor positions of investors of whole loans and securities, and designate or redesignate inventory between trading accounts. The position monitor 158 is able to provide this information in near real time because the position monitor 158 either uses the same transactional database(s) as the servicer and investor reporting logic 30 and the securitization logic 32 or, preferably, uses a separate data base that is synchronized with these data bases. For both whole loans and securities, the position monitor 158 provides daily and month-to-date commitment/trade and delivery/settlement positions. The position monitor 158 also provides cumulative inventory positions held by the portfolio. The position monitor 158 allows investors to manage inventory from an economic, risk management, and regulatory accounting and taxation perspective. It also allows investors to determine or designate what assets to buy, what assets to sell, and what assets to retain or hold for investment. The portfolio manager 158 provides investors with a clear and concise view of their current net position of inventory.
  • The out of portfolio (OOP) pooling [0106] logic 160 permits the data processing system 12 to be used for pooling loans to create financial instruments in situations where the loans are owned by the entity that owns or operates the data processing system 12 or by an entity other than the entity that owns/operates the data processing system 12. The OOP pooling logic 160 provides the owner of the loans being pooled with the ability to select asset attributes and sub-attributes at a granular level, the ability to select loans to optimize chartered pool statistics, the ability to flexibly map incoming and outgoing cash flows, and the ability to use an on-screen display to manipulate collateral. The out of portfolio pooling processor 160 also has the ability to collateralize asset cash flows as described above in connection with the packeting logic 154.
  • The whole [0107] loan trading logic 162 provides a facility for engaging in whole loan trades to permit the owner or operator of the data processing system 12 to identify and sell loans out of its portfolio to other entities. The whole loan trading logic 162 also provides logic for reporting to the servicer of a sold loan (1) that the loan has been sold and (2) the identity of the new owner of the loan, allowing the servicer to begin reporting payment information to the new owner.
  • Referring to FIG. 6, the [0108] common services logic 34 includes work flow processor 170 which generates notifications about required actions and routes the notifications to users of the data processing system 12 according to pre-defined processing sequences for request approvals and exception report resolutions. The work flow processor 170 also keeps track of status and actions related to work items.
  • The [0109] report processor 172 generates reports based on users' requests. The report processor 172 allows data to be extracted from the data bases to prepare reports that can be sent out through the user services logic 22. The reports that are returned may be bulk transfers of data. The report processor 172 supports generating the reports described above in connection with the acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32.
  • The database and [0110] access control logic 174 provides database and user security administration and control for the databases in the data storage system 38 and functions available through system 12. The database access and control logic also maintains referential integrity, processes queries and updates, and performs all tasks related to access and control of the databases in the data storage system 38.
  • The process controller/[0111] scheduler 176 triggers execution of processes based on time schedule and/or events received from application components. The process controller/scheduler encapsulates information on processing interdependencies between different components in the data processing system 12.
  • The [0112] audit logging logic 178 logs data that is needed for historical tracking of the activities of the data processing system 12. The purpose of the data logging is primarily to meet audit requirements in connection with the transactions processed by the data processing system 12.
  • The business rules [0113] processor 180 is a rules engine that encapsulates business rules to permit the business rules to be applied to the loan data. Examples of the business rules applied by the rules processor 180 have been described throughout the discussion of the data processing system 12. A user interface is provided that allows the business rules to be modified and that allows new business rules to be added or obsolete business rules to be deleted. The rules processor 180 maintains the business rules separate from the remainder of the application code that implements other aspects of the data processing system 12. This allows the business rules to be modified/added/deleted without requiring revisions to the application code. The ability to modify or add business rules quickly facilitates the introduction of new types of loan products and investment instruments, because the data processing system 12 may be easily modified to implement any special data processing required for the implementation of the new loan products/investment instruments. Preferably, the rules processor 180 is provided as three separate rules processor, one for each of the acquisition logic 28, the servicer and investor reporting logic 30, and the securitization logic 32, with separate user interfaces for each rules processor.
  • As previously indicated, service granularity is achieved in part by representing loans as a series of data attributes. The following is an example of a set of attributes that may be used to characterize loans: accounting class code; accounting close effective period; accounting reporting category code; actual UPB at acquisition; adjusted last paid installment date; adjusted unpaid principal balance; ceiling; change frequency; change method; conduit code; custodian code; downward cap; downward cap code; effective date; excess yield; excess yield adjustment; extended term; purchaser loan number; final step change; first PITI (principal, interest, taxes, insurance) due date; fixed interest rate; fixed pass-thru rate; fixed payment amount; floor; frequency of payment change; frequency of rate change; future feature code; index code; index lookback; interest rate; loan guaranty payment date; loan conversion date; loan guaranty date; loan payoff interest calculation code; loan rate effective date; loan to value ratio; LP control record; lender pass through (LPT) type code; maximum term; months payment control effective; months rate control effective; mortgage margin; mortgage term; net interest adjustment; new payment amount; next control record; next scheduled payment change date; next scheduled rate change date; number of months in effect; other fees collected adjustment; pass-thru rate; payment change amount/percentage; payment change method code; payment control record; payment type code; principal adjustment; processing status code; product code; rate change method code; rate change percent; rate control record; rate conversion status code; rate rounding method; rate type code; reclassification date; remittance day code; required change index; required margin; secured unpaid principal balance; servicing fee; servicing fee adjustment; servicing fee type; servicing remittance option; unpaid principal balance; upward cap; upward cap code. In addition to the above-mentioned attributes, additional attributes may be used in connection with particular types of specialty loan products. [0114]
  • As previously indicated, data granularity is achieved at least in part by decomposing loan assets into a series of cash flows. A cash flow may be any type of payment, whether of principal, interest, or fees. Cash flow may also includes credit-related losses, which manifest themselves from the securities standpoint as negative investor payments (i.e., a reduction to positive cash flows). Possible sources of cash flow may be associated with principal, interest, servicing fees, guarantee fees, mortgage insurance, prepayment penalties, borrower-paid fees, servicer advances, servicer recoveries, loss/default components, and REO activity. For principal, individual cash flows that may be identified include the following: scheduled principal (amount payable based on scheduled amortization), actual principal (what was applied as principal), unscheduled principal (amount from borrower applied in excess of scheduled), advanced (amount not collected from borrower but remitted to investor), shortfall (underpayment from borrower, usually meaning less than full scheduled amount). For interest, individual cash flows that may be identified include the following: scheduled Interest (amount payable), actual (what was applied), excess (interest collection in excess of amount payable), advanced (not collected from borrower but sent to investor), shortfall (underpayment from servicer), capitalized (negative amortization), other capitalized interest (delinquency), unrecoverable prepayment interest shortfall. For servicing fees, individual cash flows that may be identified include the following: gross servicing fee, core servicing fee (usually relates to tax), excess servicing fee, safe harbor (tax). For guarantee fees, individual cash flows that may be identified include the following cash flows: gross guarantee fee (GF) (total charged to the lender), cash flows for internally tracking costs (e.g., costs associated with credit risk), base GF, GF variance, and other GF adjustments. For mortgage insurance (MI), individual cash flows that may be identified include the following: lender paid MI, borrower paid MI, portion of GF construed to be MI, back-end MI. For prepayment penalties, individual cash flows that may be identified include the following: prepayment penalty, prepayment penalty (borrower-paid), yield maintenance fee (borrower-paid). For borrower-paid fees, individual cash flows that may be identified include the following: borrower-paid fees, late payment fee, conversion/modification fee. For seller advances, individual cash flows that may be identified include the following: advanced principal, advanced interest, advanced guaranty fee, servicing advances (usually relates to defaults, e.g., T&I). For servicer recoveries, individual cash flows that may be identified include the following: recovered principal advances, recovered interest advances, recovered guaranty fee advances, recovered servicing advances. For default activity, cash flows that may be identified include the following: net realized loss (total amount payable to investors less all recoveries), foreclosure expenses, attorney fees, recoup of non-recoverable advances, loss due to modification, loss due to appraisal reduction, loss due to deficiency valuation, non-capitalized deferred interest (e.g. workout), interest paid on advances. For REO activity, cash flows that may be identified include the following: foreclosure sale proceeds, rental income, insurance proceeds, tax expenses on REO, repair expenses on REO, sale/marketing expenses on REO, REO property maintenance expenses. It may be noted that some of the above cash flows are aggregate cash flows that can be further decomposed. Other cash flow pertinent information that may be tracked includes unpaid principal balance (UPB) (including scheduled UPB and actual UPB), participation percentage (including principal participation percentage, interest participation percentage, and servicing fee participation (basis points)), discount rate (used to calculate yield maintenance or prepayment penalty), appraised balance, foreclosure sale date, and REO sale date. [0115]
  • Many other changes and modifications may be made to the present invention without departing from the spirit thereof. For example; each of the features described above may also be implemented in systems or logic that are configured differently than the [0116] data processing system 12 and/or that include different, fewer or more functions than the functions included in the data processing system 12. The scope of these and other changes will become apparent from the appended claims.

Claims (15)

What is claimed is:
1. A method for facilitating delivery of a loan to a purchaser, the loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan, the underwriting data having an identifier, the method comprising:
providing a delivery template to a seller of the loan to receive delivery data for the loan;
upon receiving a request from the seller including the identifier, retrieving the underwriting data associated with the identifier; and
populating the delivery template with the predetermined set of information.
2. A method according to claim 1, further comprising receiving delivery data from the seller via the delivery template.
3. A method according to claim 2, further comprising determining a price for the loan based on the predetermined set of information and the delivery data received from the seller.
4. A method according to claim 1, further comprising editing the underwriting data for the loan.
5. A method according to claim 1, wherein the predetermined set of information includes a borrower identifier, occupancy type, product type, amortization type, loan term, property type, loan purpose, property sales price and appraised value.
6. A system for facilitating delivery of a loan to a purchaser, the loan having a set of underwriting data including a predetermined set of information relevant to the delivery of the loan, the underwriting data having an identifier, the system comprising:
means for providing a delivery template to a seller of the loan to receive delivery data for the loan;
means for receiving a request from the seller including the identifier;
means for retrieving the underwriting data associated with the identifier; and
means for populating the delivery template with the predetermined set of information.
7. A system according to claim 6, further comprising means for receiving delivery data from the seller via the delivery template.
8. A system according to claim 7, further comprising means for determining a price for the loan based on the predetermined set of information and the delivery data received from the seller.
9. A system according to claim 6, further comprising means for editing the underwriting data for the loan.
10. A system according to claim 6, wherein the predetermined set of information includes a borrower identifier, occupancy type, product type, amortization type, loan term, property type, loan purpose, property sales price and appraised value.
11. A system for delivering a loan to a purchaser, the loan having a set of underwriting data provided by underwriting logic, the underwriting data including a predetermined set of information relevant to the delivery of the loan and having an identifier generated by the underwriting logic, the system comprising:
a user interface for providing a delivery template to the seller of the loan and for receiving delivery data for the loan;
delivery logic, coupled to the user interface, for processing the delivery data for the loan;
wherein, upon receiving a request from the seller that includes the identifier via the user interface, the delivery logic retrieves the underwriting data associated with the identifier and populates the delivery template with the predetermined set of information.
12. A system according to claim 11, wherein retrieving the underwriting data includes sending a request to the underwriting logic.
13. A system according to claim 11, further comprising pricing logic coupled to the delivery logic for determining a price for the loan based on the predetermined set of information and the delivery data provided by the seller.
14. A system according to claim 11, wherein user interface permits the seller to edit the underwriting data.
15. A system according to claim 11, wherein the predetermined set of information includes a borrower identifier, occupancy type, product type, amortization type, loan term, property type, loan purpose, property sales price and appraised value.
US10/738,518 2002-12-30 2003-12-17 System and method for facilitating delivery of a loan to a secondary mortgage market purchaser Abandoned US20040225596A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/738,518 US20040225596A1 (en) 2002-12-30 2003-12-17 System and method for facilitating delivery of a loan to a secondary mortgage market purchaser

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US43697702P 2002-12-30 2002-12-30
US10/738,518 US20040225596A1 (en) 2002-12-30 2003-12-17 System and method for facilitating delivery of a loan to a secondary mortgage market purchaser

Publications (1)

Publication Number Publication Date
US20040225596A1 true US20040225596A1 (en) 2004-11-11

Family

ID=32713117

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/737,298 Expired - Lifetime US7747519B2 (en) 2002-12-30 2003-12-16 System and method for verifying loan data at delivery
US10/738,518 Abandoned US20040225596A1 (en) 2002-12-30 2003-12-17 System and method for facilitating delivery of a loan to a secondary mortgage market purchaser
US12/825,169 Expired - Lifetime US8024265B2 (en) 2002-12-30 2010-06-28 System and method for verifying loan data at delivery

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/737,298 Expired - Lifetime US7747519B2 (en) 2002-12-30 2003-12-16 System and method for verifying loan data at delivery

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/825,169 Expired - Lifetime US8024265B2 (en) 2002-12-30 2010-06-28 System and method for verifying loan data at delivery

Country Status (3)

Country Link
US (3) US7747519B2 (en)
AU (2) AU2003295807A1 (en)
WO (2) WO2004061561A2 (en)

Cited By (78)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050102225A1 (en) * 2002-12-30 2005-05-12 Dror Oppenheimer System and method for processing data pertaining to financial assets
US20050131787A1 (en) * 2003-12-16 2005-06-16 Monteleone Leonard C. System and method for trading of mortgage backed securities
US20050203839A1 (en) * 2004-12-03 2005-09-15 Phoenix Analytic Services, Inc. Method for Transferring Mortgage Servicing Rights
US20050216394A1 (en) * 2003-12-16 2005-09-29 Monteleone Leonard C Computer-based system and method for confirming failed trades of securities
US20060004651A1 (en) * 2004-07-02 2006-01-05 Corr Jonathan H Loan origination software system for processing mortgage loans over a distributed network
US20060036465A1 (en) * 2004-08-13 2006-02-16 O'donnell Lee F Online interactive interface and automated processing for loan origination and underwriting
US20070050287A1 (en) * 2005-08-26 2007-03-01 Capozza Dennis R Method for structuring a new loan
US20070255641A1 (en) * 2006-04-28 2007-11-01 Harrington Kevin F Computer interface for trading bonds
US20090037321A1 (en) * 2007-08-02 2009-02-05 Bank Of America Corporation System and method for processing loan applications
US20090083076A1 (en) * 2003-09-19 2009-03-26 Hashim Safaa H Techniques for ensuring data security among participants in a web-centric insurance management system
US20090240609A1 (en) * 2008-03-19 2009-09-24 Soogyung Cho System and method for tracking and analyzing loans involved in asset-backed securities
US7620578B1 (en) 2006-05-01 2009-11-17 Jpmorgan Chase Bank, N.A. Volatility derivative financial product
US20090299621A1 (en) * 2004-01-29 2009-12-03 Xanavi Informatics Corporation Automobile navigation apparatus
US7680731B1 (en) 2000-06-07 2010-03-16 Jpmorgan Chase Bank, N.A. System and method for executing deposit transactions over the internet
US7693782B1 (en) 2004-08-03 2010-04-06 Fannie Mae Method and system for evaluating a loan
US7702580B1 (en) 2000-06-13 2010-04-20 Fannie Mae System and method for mortgage loan pricing, sale and funding
US7716107B1 (en) 2006-02-03 2010-05-11 Jpmorgan Chase Bank, N.A. Earnings derivative financial product
US7742981B2 (en) 2002-12-30 2010-06-22 Fannie Mae Mortgage loan commitment system and method
US7747519B2 (en) 2002-12-30 2010-06-29 Fannie Mae System and method for verifying loan data at delivery
US7770184B2 (en) 2003-06-06 2010-08-03 Jp Morgan Chase Bank Integrated trading platform architecture
US7783565B1 (en) * 2006-11-08 2010-08-24 Fannie Mae Method and system for assessing repurchase risk
US7809633B2 (en) 2002-12-30 2010-10-05 Fannie Mae System and method for pricing loans in the secondary mortgage market
US7818238B1 (en) 2005-10-11 2010-10-19 Jpmorgan Chase Bank, N.A. Upside forward with early funding provision
US7827096B1 (en) 2006-11-03 2010-11-02 Jp Morgan Chase Bank, N.A. Special maturity ASR recalculated timing
US7860787B2 (en) 2002-12-30 2010-12-28 Fannie Mae System and method for modifying attribute data pertaining to financial assets in a data processing system
US7890407B2 (en) 2000-11-03 2011-02-15 Jpmorgan Chase Bank, N.A. System and method for estimating conduit liquidity requirements in asset backed commercial paper
US7908242B1 (en) 2005-04-11 2011-03-15 Experian Information Solutions, Inc. Systems and methods for optimizing database queries
US7912865B2 (en) 2006-09-26 2011-03-22 Experian Marketing Solutions, Inc. System and method for linking multiple entities in a business database
US20110137788A1 (en) * 2009-12-04 2011-06-09 Merkle Robert A Systems and methods for evaluating the ability of borrowers to repay loans
US7966234B1 (en) 1999-05-17 2011-06-21 Jpmorgan Chase Bank. N.A. Structured finance performance analytics system
US7970688B2 (en) 2003-07-29 2011-06-28 Jp Morgan Chase Bank Method for pricing a trade
US7991689B1 (en) 2008-07-23 2011-08-02 Experian Information Solutions, Inc. Systems and methods for detecting bust out fraud using credit data
US8024264B2 (en) 2007-04-12 2011-09-20 Experian Marketing Solutions, Inc. Systems and methods for determining thin-file records and determining thin-file risk levels
US8065211B2 (en) 2002-12-30 2011-11-22 Fannie Mae System and method for creating and tracking agreements for selling loans to a secondary market purchaser
US8090639B2 (en) 2004-08-06 2012-01-03 Jpmorgan Chase Bank, N.A. Method and system for creating and marketing employee stock option mirror image warrants
US8117117B2 (en) 2002-08-15 2012-02-14 Ellie Mae, Inc. Loan origination system interface for online loan application processing
US8175889B1 (en) 2005-04-06 2012-05-08 Experian Information Solutions, Inc. Systems and methods for tracking changes of address based on service disconnect/connect data
US20120116944A1 (en) * 2010-11-05 2012-05-10 Dicarlo Dean System and Method of Electronic Exchange for Residential Mortgages
US8244628B1 (en) 2000-06-13 2012-08-14 Fannie Mae Computerized systems and methods for facilitating the flow of capital through the housing finance industry
US8301574B2 (en) 2007-09-17 2012-10-30 Experian Marketing Solutions, Inc. Multimedia engagement study
US8352354B2 (en) 2010-02-23 2013-01-08 Jpmorgan Chase Bank, N.A. System and method for optimizing order execution
US8364518B1 (en) 2009-07-08 2013-01-29 Experian Ltd. Systems and methods for forecasting household economics
US8364579B2 (en) 2002-06-14 2013-01-29 Ellie Mae, Inc. Online system for fulfilling loan applications from loan originators
US8364588B2 (en) 2007-05-25 2013-01-29 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US8392334B2 (en) 2006-08-17 2013-03-05 Experian Information Solutions, Inc. System and method for providing a score for a used vehicle
US8423450B2 (en) 2002-12-30 2013-04-16 Fannie Mae System and method for processing data pertaining to financial assets
US8423447B2 (en) 2004-03-31 2013-04-16 Jp Morgan Chase Bank System and method for allocating nominal and cash amounts to trades in a netted trade
US8463697B1 (en) 2007-01-10 2013-06-11 Liberty Home Equity Solutions, Inc. Method and system for providing a loan using equity in a new home
US8515861B2 (en) 2002-12-30 2013-08-20 Fannie Mae System and method for facilitating sale of a loan to a secondary market purchaser
US8548886B1 (en) 2002-05-31 2013-10-01 Jpmorgan Chase Bank, N.A. Account opening system, method and computer program product
US8600798B1 (en) 2007-09-21 2013-12-03 Ellie Mae, Inc. Loan screening
US8606666B1 (en) 2007-01-31 2013-12-10 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US8626560B1 (en) 2009-06-30 2014-01-07 Experian Information Solutions, Inc. System and method for evaluating vehicle purchase loyalty
US8639616B1 (en) 2010-10-01 2014-01-28 Experian Information Solutions, Inc. Business to contact linkage system
US8666879B1 (en) * 2002-12-30 2014-03-04 Fannie Mae Method and system for pricing forward commitments for mortgage loans and for buying committed loans
US8688569B1 (en) * 2005-03-23 2014-04-01 Jpmorgan Chase Bank, N.A. System and method for post closing and custody services
US8725613B1 (en) 2010-04-27 2014-05-13 Experian Information Solutions, Inc. Systems and methods for early account score and notification
US8738514B2 (en) 2010-02-18 2014-05-27 Jpmorgan Chase Bank, N.A. System and method for providing borrow coverage services to short sell securities
US8775299B2 (en) 2011-07-12 2014-07-08 Experian Information Solutions, Inc. Systems and methods for large-scale credit data processing
US8954459B1 (en) 2008-06-26 2015-02-10 Experian Marketing Solutions, Inc. Systems and methods for providing an integrated identifier
US9147042B1 (en) 2010-11-22 2015-09-29 Experian Information Solutions, Inc. Systems and methods for data verification
US9152727B1 (en) 2010-08-23 2015-10-06 Experian Marketing Solutions, Inc. Systems and methods for processing consumer information for targeted marketing applications
US20160078534A1 (en) * 2014-09-15 2016-03-17 The Toronto-Dominion Bank Method and network for transferring a loan
US9342783B1 (en) 2007-03-30 2016-05-17 Consumerinfo.Com, Inc. Systems and methods for data verification
US9483606B1 (en) 2011-07-08 2016-11-01 Consumerinfo.Com, Inc. Lifescore
US9529851B1 (en) 2013-12-02 2016-12-27 Experian Information Solutions, Inc. Server architecture for electronic data quality processing
US9563916B1 (en) 2006-10-05 2017-02-07 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US9576030B1 (en) 2014-05-07 2017-02-21 Consumerinfo.Com, Inc. Keeping up with the joneses
US9690820B1 (en) 2007-09-27 2017-06-27 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US9697263B1 (en) 2013-03-04 2017-07-04 Experian Information Solutions, Inc. Consumer data request fulfillment system
US9853959B1 (en) 2012-05-07 2017-12-26 Consumerinfo.Com, Inc. Storage and maintenance of personal data
US10102536B1 (en) 2013-11-15 2018-10-16 Experian Information Solutions, Inc. Micro-geographic aggregation system
US10242019B1 (en) 2014-12-19 2019-03-26 Experian Information Solutions, Inc. User behavior segmentation using latent topic detection
US10262362B1 (en) 2014-02-14 2019-04-16 Experian Information Solutions, Inc. Automatic generation of code for attributes
US10678894B2 (en) 2016-08-24 2020-06-09 Experian Information Solutions, Inc. Disambiguation and authentication of device users
US10963434B1 (en) 2018-09-07 2021-03-30 Experian Information Solutions, Inc. Data architecture for supporting multiple search models
US11227001B2 (en) 2017-01-31 2022-01-18 Experian Information Solutions, Inc. Massive scale heterogeneous data ingestion and user resolution
US11880377B1 (en) 2021-03-26 2024-01-23 Experian Information Solutions, Inc. Systems and methods for entity resolution

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060106690A1 (en) * 2004-10-29 2006-05-18 American International Group, Inc. Lender evaluation system
US20080281734A1 (en) * 2005-07-11 2008-11-13 Appone Services, Inc. System and method for integrated credit application and tax refund estimation
US7860766B2 (en) * 2005-09-12 2010-12-28 Terant Enterprises Inc. Closing funds management system
US7711636B2 (en) 2006-03-10 2010-05-04 Experian Information Solutions, Inc. Systems and methods for analyzing data
CA2646773A1 (en) * 2007-12-13 2009-06-13 Mrre Inc. Method of and system for web-based managing and reporting mortgage transactions
US8244611B2 (en) * 2007-12-19 2012-08-14 Metabank Private label promotion card system, program product, and associated computer-implemented methods
US8818887B2 (en) 2007-12-21 2014-08-26 Metabank Computer-implemented methods, program product, and system for micro-loan product management
US8069085B2 (en) 2007-12-21 2011-11-29 Metabank System, program product, and associated methods to autodraw for micro-credit attached to a prepaid card
US8583515B2 (en) 2007-12-21 2013-11-12 Metabank Transfer account systems, computer program products, and associated computer-implemented methods
US8589295B2 (en) 2007-12-21 2013-11-19 Metabank Transfer account systems, computer program products, and associated computer-implemented methods
WO2009105653A1 (en) * 2008-02-20 2009-08-27 Metabank Methods to advance loan proceeds on prepaid cards, associatated systems and computer program products
US10515405B2 (en) 2008-03-03 2019-12-24 Metabank Person-to-person lending program product, system, and associated computer-implemented methods
WO2009117518A1 (en) * 2008-03-19 2009-09-24 Experian Information Solutions, Inc. System and method for tracking and analyzing loans involved in asset-backed securities
WO2009124264A1 (en) 2008-04-04 2009-10-08 Metabank System, program product, and method for debit card and checking account autodraw
WO2009124270A1 (en) 2008-04-04 2009-10-08 Metabank System, program product, and associated methods to autodraw for micro-credit attached to a prepaid card
WO2009140520A1 (en) 2008-05-14 2009-11-19 Metabank A pre-paid card transaction computer to load a loan on a pre-paid card
US11227331B2 (en) 2008-05-14 2022-01-18 Metabank System, program product, and computer-implemented method for loading a loan on an existing pre-paid card
US8538879B2 (en) 2008-05-14 2013-09-17 Metabank System, program product, and computer-implemented method for loading a loan on an existing pre-paid card
US9256904B1 (en) 2008-08-14 2016-02-09 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US8403211B2 (en) 2008-09-04 2013-03-26 Metabank System, program product and methods for retail activation and reload associated with partial authorization transactions
WO2010028266A1 (en) 2008-09-04 2010-03-11 Metabank System, program product and methods for retail activation and reload associated with partial authorization transactions
US7594821B1 (en) 2008-09-17 2009-09-29 Yazaki North America, Inc. Sealing gap formed by assembled connector parts
US8024242B2 (en) 2008-09-04 2011-09-20 Metabank System, method, and program product for foreign currency travel account
US8371502B1 (en) 2008-10-28 2013-02-12 Metabank Shopping center gift card offer fulfillment machine, program product, and associated methods
US8108977B1 (en) 2008-10-31 2012-02-07 Metabank Machine, methods, and program product for electronic order entry
US9213965B1 (en) 2008-11-26 2015-12-15 Metabank Machine, methods, and program product for electronic inventory tracking
US8090649B2 (en) 2008-12-18 2012-01-03 Metabank Computerized extension of credit to existing demand deposit accounts, prepaid cards and lines of credit based on expected tax refund proceeds, associated systems and computer program products
US8175962B2 (en) 2008-12-18 2012-05-08 Metabank Computerized extension of credit to existing demand deposit accounts, prepaid cards and lines of credit based on expected tax refund proceeds, associated systems and computer program products
US8286863B1 (en) 2009-02-04 2012-10-16 Metabank System and computer program product to issue a retail prepaid card including a user-designed external face using a chit and related computer implemented methods
US20110082737A1 (en) 2009-09-28 2011-04-07 Crowe Andrew B Computer-implemented methods, computer program products, and systems for management and control of a loyalty rewards network
US9652802B1 (en) 2010-03-24 2017-05-16 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US8515863B1 (en) 2010-09-01 2013-08-20 Federal Home Loan Mortgage Corporation Systems and methods for measuring data quality over time
US8930262B1 (en) 2010-11-02 2015-01-06 Experian Technology Ltd. Systems and methods of assisted strategy design
US20120246060A1 (en) * 2011-03-25 2012-09-27 LoanHD, Inc. Loan management, real-time monitoring, analytics, and data refresh system and method
US8635277B2 (en) 2011-03-29 2014-01-21 Amazon Technologies, Inc. Mediated lending of digital items
US8799363B2 (en) * 2011-03-29 2014-08-05 Amazon Technologies, Inc. Lending digital items to identified recipients
US20120254066A1 (en) * 2011-03-31 2012-10-04 Neuberger Berman Fixed Income Llc Methods and apparatus for valuing mortgage loan portfolios
US9558519B1 (en) 2011-04-29 2017-01-31 Consumerinfo.Com, Inc. Exposing reporting cycle information
US10296878B1 (en) 2011-06-28 2019-05-21 Amazon Technologies, Inc. Platform for providing generic e-content
US20130132291A1 (en) * 2011-11-22 2013-05-23 Bank Of America Assessing agreement compliance
US20130179331A1 (en) * 2012-01-05 2013-07-11 Denali Alaskan Federal Credit Union Method and system for internal analysis of loan instruments
US10255598B1 (en) 2012-12-06 2019-04-09 Consumerinfo.Com, Inc. Credit card account data extraction
US20140279399A1 (en) * 2013-03-14 2014-09-18 Capital One Financial Corporation System and method for matching vendors and clients
US20140279393A1 (en) * 2013-03-15 2014-09-18 Fiserv, Inc. Electronic loan processing, management and quality assessment
US11263693B1 (en) * 2013-10-17 2022-03-01 Fannie Mae Central risk pricing system and method
US20150348186A1 (en) * 2014-05-27 2015-12-03 C1 Bank System and method for dynamic customer acquisition probability and risk-adjusted return-on-equity analysis
US9928268B2 (en) * 2014-07-29 2018-03-27 Mark Besch System and method for verifying the contents of forms relative to a separate dataset
US10757154B1 (en) 2015-11-24 2020-08-25 Experian Information Solutions, Inc. Real-time event-based notification system
US11361268B1 (en) * 2016-08-31 2022-06-14 Fannie Mae Business rules management system
US10735183B1 (en) 2017-06-30 2020-08-04 Experian Information Solutions, Inc. Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network
US11620403B2 (en) 2019-01-11 2023-04-04 Experian Information Solutions, Inc. Systems and methods for secure data aggregation and computation
US10679286B1 (en) * 2019-05-17 2020-06-09 Capital One Services, Llc Systems and methods for intelligent income verification to improve loan contract funding
EP4035115A4 (en) * 2019-09-26 2023-07-26 Sliwka, Lukasz Jakub Distributed ledger lending systems having a smart contract architecture and methods therefor
US11579955B1 (en) 2019-12-27 2023-02-14 Federal Home Loan Mortgage Corporation (Freddie Mac) Database and file management for data validation and authentication

Citations (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3316395A (en) * 1963-05-23 1967-04-25 Credit Corp Comp Credit risk computer
US4876648A (en) * 1988-01-12 1989-10-24 Lloyd Clarke B System and method for implementing and administering a mortgage plan
US5239462A (en) * 1992-02-25 1993-08-24 Creative Solutions Groups, Inc. Method and apparatus for automatically determining the approval status of a potential borrower
US5323315A (en) * 1991-08-02 1994-06-21 Vintek, Inc. Computer system for monitoring the status of individual items of personal property which serve as collateral for securing financing
US5414621A (en) * 1992-03-06 1995-05-09 Hough; John R. System and method for computing a comparative value of real estate
US5537315A (en) * 1994-03-23 1996-07-16 Mitcham; Martin K. Method and apparatus for issuing insurance from kiosk
US5563783A (en) * 1992-05-13 1996-10-08 The Trustees Of Columbia University In The City Of New York Method and system for securities pool allocation
US5611052A (en) * 1993-11-01 1997-03-11 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5615268A (en) * 1995-01-17 1997-03-25 Document Authentication Systems, Inc. System and method for electronic transmission storage and retrieval of authenticated documents
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5765144A (en) * 1996-06-24 1998-06-09 Merrill Lynch & Co., Inc. System for selecting liability products and preparing applications therefor
US5797133A (en) * 1994-08-31 1998-08-18 Strategic Solutions Group, Inc Method for automatically determining the approval status of a potential borrower
US5870721A (en) * 1993-08-27 1999-02-09 Affinity Technology Group, Inc. System and method for real time loan approval
US5878403A (en) * 1995-09-12 1999-03-02 Cmsi Computer implemented automated credit application analysis and decision routing system
US5878404A (en) * 1996-10-08 1999-03-02 Mechanics Savings Bank System and method for managing the amortization of a loan
US5930775A (en) * 1997-01-14 1999-07-27 Freddie Mac Method and apparatus for determining an optimal investment plan for distressed residential real estate loans
US5930776A (en) * 1993-11-01 1999-07-27 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5940812A (en) * 1997-08-19 1999-08-17 Loanmarket Resources, L.L.C. Apparatus and method for automatically matching a best available loan to a potential borrower via global telecommunications network
US5940811A (en) * 1993-08-27 1999-08-17 Affinity Technology Group, Inc. Closed loop financial transaction method and apparatus
US5966700A (en) * 1997-12-23 1999-10-12 Federal Home Loan Bank Of Chicago Management system for risk sharing of mortgage pools
US5966699A (en) * 1996-10-11 1999-10-12 Zandi; Richard System and method for conducting loan auction over computer network
US5970464A (en) * 1997-09-10 1999-10-19 International Business Machines Corporation Data mining based underwriting profitability analysis
US5974372A (en) * 1996-02-12 1999-10-26 Dst Systems, Inc. Graphical user interface (GUI) language translator
US6014645A (en) * 1996-04-19 2000-01-11 Block Financial Corporation Real-time financial card application system
US6021202A (en) * 1996-12-20 2000-02-01 Financial Services Technology Consortium Method and system for processing electronic documents
US6035288A (en) * 1998-06-29 2000-03-07 Cendant Publishing, Inc. Interactive computer-implemented system and method for negotiating sale of goods and/or services
US6044362A (en) * 1997-09-08 2000-03-28 Neely; R. Alan Electronic invoicing and payment system
US6070151A (en) * 1993-04-22 2000-05-30 Fibonacci Corporation System for the creation and collateralization of real estate mortgage investment conduit securities
US6076070A (en) * 1998-07-23 2000-06-13 Cendant Publishing, Inc. Apparatus and method for on-line price comparison of competitor's goods and/or services over a computer network
US6088686A (en) * 1995-12-12 2000-07-11 Citibank, N.A. System and method to performing on-line credit reviews and approvals
US6112190A (en) * 1997-08-19 2000-08-29 Citibank, N.A. Method and system for commercial credit analysis
US6119103A (en) * 1997-05-27 2000-09-12 Visa International Service Association Financial risk prediction systems and methods therefor
US6125349A (en) * 1997-10-01 2000-09-26 At&T Corp. Method and apparatus using digital credentials and other electronic certificates for electronic transactions
US6202053B1 (en) * 1998-01-23 2001-03-13 First Usa Bank, Na Method and apparatus for generating segmentation scorecards for evaluating credit risk of bank card applicants
US6226624B1 (en) * 1997-10-24 2001-05-01 Craig J. Watson System and method for pre-authorization of individual account remote transactions
US6233566B1 (en) * 1998-12-31 2001-05-15 Ultraprise Corporation System, method and computer program product for online financial products trading
US6289319B1 (en) * 1984-05-24 2001-09-11 Lawrence B. Lockwood Automatic business and financial transaction processing system
US20020029154A1 (en) * 2000-09-07 2002-03-07 Hnc Software, Inc. Mechanism and method for dynamic question handling through an electronic interface
US20020029194A1 (en) * 2000-09-07 2002-03-07 Richard Lewis System and method of managing financial transactions over an electronic network
US20020032635A1 (en) * 2000-01-06 2002-03-14 Stewart Harris Systems and methods for monitoring credit of trading couterparties
US20020035520A1 (en) * 2000-08-02 2002-03-21 Weiss Allan N. Property rating and ranking system and method
US20020038318A1 (en) * 2000-09-22 2002-03-28 Cochran Jeffrey M. System and method for managing transferable records
US6367013B1 (en) * 1995-01-17 2002-04-02 Eoriginal Inc. System and method for electronic transmission, storage, and retrieval of authenticated electronic original documents
US20020040339A1 (en) * 2000-10-02 2002-04-04 Dhar Kuldeep K. Automated loan processing system and method
US20020052835A1 (en) * 2000-04-28 2002-05-02 Toscano Paul James On line loan process
US20020052815A1 (en) * 1999-12-30 2002-05-02 Johnson Christopher Donald Methods and apparatus for automated underwriting of segmentable portfolio assets
US6385594B1 (en) * 1998-05-08 2002-05-07 Lendingtree, Inc. Method and computer network for co-ordinating a loan over the internet
US20020059137A1 (en) * 2000-06-27 2002-05-16 Freeman Douglas K. Online mortgate application processing and tracking system
US6401070B1 (en) * 1996-10-11 2002-06-04 Freddie Mac System and method for providing house price forecasts based on repeat sales model
US6405181B2 (en) * 1998-11-03 2002-06-11 Nextcard, Inc. Method and apparatus for real time on line credit approval
US20020077968A1 (en) * 2000-12-14 2002-06-20 International Business Machines Corporation Data sampling with priority to conforming component ratios
US20020087389A1 (en) * 2000-08-28 2002-07-04 Michael Sklarz Value your home
US20020087364A1 (en) * 2000-11-07 2002-07-04 Lerner Andrew S. System and method for enabling real time underwriting of insurance policies
US20020091550A1 (en) * 2000-06-29 2002-07-11 White Mitchell Franklin System and method for real-time rating, underwriting and policy issuance
US20020091630A1 (en) * 2001-01-10 2002-07-11 Akiyoshi Inoue Loan intermediary processing system and method thereof
US20020099650A1 (en) * 2000-11-15 2002-07-25 Cole James A. Method for automatically processing a financial loan application and the system thereof
US6430539B1 (en) * 1999-05-06 2002-08-06 Hnc Software Predictive modeling of consumer financial behavior
US20020111901A1 (en) * 2001-01-24 2002-08-15 Whitney Patrick G. Loan servicing system
US20020111835A1 (en) * 2000-11-06 2002-08-15 Hele John C. R. Underwriting insurance
US6438526B1 (en) * 1998-09-09 2002-08-20 Frederick T. Dykes System and method for transmitting and processing loan data
US20020138414A1 (en) * 2001-03-26 2002-09-26 Baker Charles Pitman Method and system and article of manufacture for a rules based automated loan approval system
US6505176B2 (en) * 1998-06-12 2003-01-07 First American Credit Management Solutions, Inc. Workflow management system for an automated credit application system
US6513018B1 (en) * 1994-05-05 2003-01-28 Fair, Isaac And Company, Inc. Method and apparatus for scoring the likelihood of a desired performance result
US20030023610A1 (en) * 2001-07-27 2003-01-30 Bove Stephen B. Online real and personal property management system and method
US20030028478A1 (en) * 2001-08-01 2003-02-06 Kinney James Michael System and method for originating turbocharged ("Turbo TM") loans
US20030033241A1 (en) * 2001-08-08 2003-02-13 Adi Harari Methods and systems for automated loan origination, processing and approval
US20030033242A1 (en) * 2000-06-03 2003-02-13 Joan Lynch System and method for automated process of deal structuring
US20030036996A1 (en) * 2001-08-16 2003-02-20 Lazerson Jeffrey M. Credit/financing process
US20030036994A1 (en) * 2001-04-12 2003-02-20 Brad Witzig Automated mortgage lender processing system
US20030036995A1 (en) * 2001-08-16 2003-02-20 Lazerson Jeffrey M. Credit/financing process
US20030046223A1 (en) * 2001-02-22 2003-03-06 Stuart Crawford Method and apparatus for explaining credit scores
US6532450B1 (en) * 1998-12-09 2003-03-11 American Management Systems, Inc. Financial management system including an offset payment process
US20030065614A1 (en) * 2001-10-01 2003-04-03 Sweeney Joan M. Method and system for rules based underwriting
US20030093366A1 (en) * 2001-11-13 2003-05-15 Halper Steven C. Automated loan risk assessment system and method
US20030110249A1 (en) * 2001-06-08 2003-06-12 Bryan Buus System and method for monitoring key performance indicators in a business
US6584467B1 (en) * 1995-12-08 2003-06-24 Allstate Insurance Company Method and apparatus for obtaining data from vendors in real time
US6594635B1 (en) * 1998-10-24 2003-07-15 Marketcore.Com, Inc. Data processing system for providing an efficient market for insurance and reinsurance
US20030144949A1 (en) * 2002-01-25 2003-07-31 Ed Blanch Web-based mortgage broker application
US6609109B1 (en) * 1995-10-12 2003-08-19 Freddie Mac Method for combining house price forecasts
US20030167191A1 (en) * 2002-02-25 2003-09-04 Slabonik Elizabeth Ann System and method for underwriting review in an insurance system
US20030172025A1 (en) * 2002-02-08 2003-09-11 Gallina Mike A. Computerized system and method for qualifying mortgage loan clients
US20030177032A1 (en) * 2001-12-31 2003-09-18 Bonissone Piero Patrone System for summerizing information for insurance underwriting suitable for use by an automated system
US20030182159A1 (en) * 2001-12-31 2003-09-25 Bonissone Piero Patrone Process for summarizing information for insurance underwriting suitable for use by an automated system
US20040002915A1 (en) * 1998-07-22 2004-01-01 Mcdonald Russell W. Mortgage loan data processing system and method for a loan broker
US20040019517A1 (en) * 2002-07-26 2004-01-29 Fidelity National Information Solutions, Inc. Method of establishing an insurable value estimate for a real estate property
US20040030649A1 (en) * 2002-05-06 2004-02-12 Chris Nelson System and method of application processing
US20040030616A1 (en) * 2000-02-25 2004-02-12 Andrew Florance System and method for collection, distribution, and use of information in connection with commercial real estate
US20040034592A1 (en) * 2002-08-15 2004-02-19 Limin Hu Loan origination system interface for online loan application processing
US20040049445A1 (en) * 2002-09-10 2004-03-11 Nanda Kishore Financial services automation
US20040049439A1 (en) * 2002-09-06 2004-03-11 David Johnston Interactive electronic bill payment system
US20040059653A1 (en) * 2002-09-24 2004-03-25 Fidelity National Financial, Inc. System and method for rendering automated real property title decisions
US20040064402A1 (en) * 2002-09-27 2004-04-01 Wells Fargo Home Mortgage, Inc. Method of refinancing a mortgage loan and a closing package for same
US20040107161A1 (en) * 2002-08-13 2004-06-03 International Business Machines Corporation System, method and computer program for managing credit decisions
US20040122717A1 (en) * 2002-10-21 2004-06-24 James Hancock Claim submission system and method
US6988082B1 (en) * 2000-06-13 2006-01-17 Fannie Mae Computerized systems and methods for facilitating the flow of capital through the housing finance industry
US7089503B1 (en) * 2001-04-04 2006-08-08 Fannie Mae Mortgage loan customization system and process

Family Cites Families (101)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5644726A (en) 1989-05-25 1997-07-01 Oppenheimer; Robert H. Method and system implementing a mortgage partnership
US5262941A (en) 1990-03-30 1993-11-16 Itt Corporation Expert credit recommendation method and system
US5274547A (en) 1991-01-03 1993-12-28 Credco Of Washington, Inc. System for generating and transmitting credit reports
US5689649A (en) 1991-03-01 1997-11-18 Altman; Robert System for operation of a combination mortgage, equity load and savings plan
US5361201A (en) 1992-10-19 1994-11-01 Hnc, Inc. Real estate appraisal using predictive modeling
US5696907A (en) 1995-02-27 1997-12-09 General Electric Company System and method for performing risk and credit analysis of financial service applications
US5699527A (en) 1995-05-01 1997-12-16 Davidson; David Edward Method and system for processing loan
US6144948A (en) 1997-06-23 2000-11-07 Walker Digital, Llc Instant credit card marketing system for reservations for future services
US5995947A (en) 1997-09-12 1999-11-30 Imx Mortgage Exchange Interactive mortgage and loan information and real-time trading system
US6304860B1 (en) 1997-10-03 2001-10-16 Joseph B. Martin, Jr. Automated debt payment system and method using ATM network
WO1999048036A1 (en) 1998-03-20 1999-09-23 Iq Financial Systems, Inc. System, method, and computer program product for assessing risk within a predefined market
US6311169B2 (en) 1998-06-11 2001-10-30 Consumer Credit Associates, Inc. On-line consumer credit data reporting system
WO2000021011A2 (en) 1998-10-02 2000-04-13 Indymac, Inc. System and method for processing loans
US20030018558A1 (en) 1998-12-31 2003-01-23 Heffner Reid R. System, method and computer program product for online financial products trading
US6324526B1 (en) 1999-01-15 2001-11-27 D'agostino John System and method for performing secure credit card purchases
US6778968B1 (en) 1999-03-17 2004-08-17 Vialogy Corp. Method and system for facilitating opportunistic transactions using auto-probes
AUPP962599A0 (en) 1999-04-07 1999-04-29 Liberty Financial Pty Ltd Application apparatus and method
US6860187B2 (en) 1999-04-07 2005-03-01 Metal Storm Limited Projectile launching apparatus and methods for fire fighting
US6609112B1 (en) * 1999-05-20 2003-08-19 Dovebid, Inc. System and method for providing proxy-based online Dutch auction services
WO2000075833A2 (en) 1999-06-07 2000-12-14 Loan Trader.Com Method and business model for matching mortgage lenders and borrowers
US7395239B1 (en) 1999-07-19 2008-07-01 American Business Financial System and method for automatically processing loan applications
WO2001016845A1 (en) 1999-08-31 2001-03-08 Insurance Technology Services Of America, Inc. Method and apparatus for network-based automated insurance transaction processing
WO2001018718A1 (en) 1999-09-09 2001-03-15 Taylor Hugh Gibbs Jr System and method for evaluating credit risks
EP1242941A1 (en) 1999-10-08 2002-09-25 Mohammed Karkukly A system and method facilitating mortgage banking and related real estate services
AU1448401A (en) 1999-10-29 2001-05-14 Donald Dipietro Method for dynamic provision of credit information
WO2001039079A1 (en) 1999-11-23 2001-05-31 Gelco Corporation Method and system for generating automated quotes and for credit processing and scoring
CA2393540A1 (en) 1999-12-03 2001-06-07 Homestore.Com, Inc. Method and system for processing a mortgage application
US20010032177A1 (en) 1999-12-29 2001-10-18 Starkman Hartley C. Methods and systems for a re-marketing model for loans
US7003484B2 (en) 1999-12-30 2006-02-21 Ge Capital Commercial Finance, Inc. Methods and systems for efficiently sampling portfolios for optimal underwriting
JP2004501418A (en) 2000-02-22 2004-01-15 イーキューイー インターナショナル インコーポレイテッド Comprehensive risk assessment system and autonomous method of underwriting using the system
EP1259921A1 (en) 2000-02-22 2002-11-27 Eqe International, Inc. Multi-level comprehensive risk assessment system for insurance underwriting
US7085735B1 (en) 2000-02-23 2006-08-01 Iclosings.Com, Inc. System and method for conducting the closing of a real estate sale over a computerized network
US7752124B2 (en) 2000-03-03 2010-07-06 Mavent Holdings, Inc. System and method for automated loan compliance assessment
US7107241B1 (en) 2000-03-10 2006-09-12 Lenders Residential Asset Company Llc System and method for processing a secured collateral loan
US20010037287A1 (en) 2000-03-14 2001-11-01 Broadbent David F. Method and apparatus for an advanced speech recognition portal for a mortgage loan management system
US20010047326A1 (en) 2000-03-14 2001-11-29 Broadbent David F. Interface system for a mortgage loan originator compliance engine
US6904412B1 (en) 2000-03-14 2005-06-07 Everbank Method and apparatus for a mortgage loan originator compliance engine
US6985886B1 (en) 2000-03-14 2006-01-10 Everbank Method and apparatus for a mortgage loan management system
US6671673B1 (en) 2000-03-24 2003-12-30 International Business Machines Corporation Method for integrated supply chain and financial management
US8145556B2 (en) 2000-04-10 2012-03-27 Tealdi Daniel A Online mortgage approval and settlement system and method therefor
AU2001253332A1 (en) 2000-04-14 2001-10-30 Livecapital, Inc. Online credit services brokering
US20010032178A1 (en) 2000-04-18 2001-10-18 Lloyd Adams Network based loan approval and document origination system
US8660939B2 (en) 2000-05-17 2014-02-25 Timothy D. Allen Method for mortgage customer retention
US6618730B1 (en) 2000-06-16 2003-09-09 Ge Capital Commercial Finance, Inc. Methods and systems for managing workflow
JP2002007701A (en) 2000-06-21 2002-01-11 Dainippon Printing Co Ltd Loan application system
US7146337B1 (en) 2000-09-13 2006-12-05 Precept Corporation System and method for originating loans
WO2002008855A2 (en) 2000-07-21 2002-01-31 Precept Corporation System and method for originating loans
EP1316044A4 (en) 2000-08-10 2006-02-08 Debt Exchange Inc Systems and methods for trading and originating financial products using a computer network
US7165092B2 (en) 2000-08-14 2007-01-16 Imagitas, Inc. System and method for sharing information among provider systems
US20050015321A1 (en) 2000-08-30 2005-01-20 Susanne Vindekilde System and method for listing offerings of commercial paper and other interests
AU2001292648A1 (en) 2000-09-11 2002-03-26 Michael L. Flynn Method and apparatus for producing reduced risk loans
US20020107818A1 (en) 2000-10-12 2002-08-08 Mcewen Scott Allen System and method for expression-based pricing
AU2002239352A1 (en) 2000-11-24 2002-07-24 Principia Partners, Llc Accounting system for the dynamic state of the portfolio reporting
US20020082984A1 (en) * 2000-12-26 2002-06-27 Paul Zappier Automated method for loan settlement
JP2002259696A (en) 2001-03-06 2002-09-13 Bank Of Tokyo-Mitsubishi Ltd Loan applying method, loan application receiving method, loan applying device, loan application receiving device, and recording medium
US7958024B2 (en) 2001-03-15 2011-06-07 Versata Development Group, Inc. Method and apparatus for processing sales transaction data
US20020138413A1 (en) * 2001-03-26 2002-09-26 Creamer David E. Commercial mortgage closing process
JP2002288426A (en) 2001-03-26 2002-10-04 Fukui Ginko Ltd Automatic investigation management system for housing loan
US20020152165A1 (en) 2001-04-12 2002-10-17 International Business Machines Corporation Method and apparatus for bill payments at an automatic teller machine
US20020152170A1 (en) 2001-04-12 2002-10-17 International Business Machines Corporation Method and apparatus for processing checks at an automatic teller machine for electronic transfer
US20020152155A1 (en) * 2001-04-13 2002-10-17 Greenwood James E. Method for automated and integrated lending process
US20020188556A1 (en) 2001-05-02 2002-12-12 James Colica System and method for monitoring and analyzing exposure data
US20030220879A1 (en) 2001-11-21 2003-11-27 Gaughan Breen P. System and method for electronic document processing
US7899688B2 (en) 2001-12-31 2011-03-01 Genworth Financial, Inc. Process for optimization of insurance underwriting suitable for use by an automated system
US8793146B2 (en) 2001-12-31 2014-07-29 Genworth Holdings, Inc. System for rule-based insurance underwriting suitable for use by an automated system
US7844477B2 (en) 2001-12-31 2010-11-30 Genworth Financial, Inc. Process for rule-based insurance underwriting suitable for use by an automated system
US7844476B2 (en) 2001-12-31 2010-11-30 Genworth Financial, Inc. Process for case-based insurance underwriting suitable for use by an automated system
US7630910B2 (en) 2001-12-31 2009-12-08 Genworth Financial, Inc. System for case-based insurance underwriting suitable for use by an automated system
US7895062B2 (en) 2001-12-31 2011-02-22 Genworth Financial, Inc. System for optimization of insurance underwriting suitable for use by an automated system
US8005693B2 (en) 2001-12-31 2011-08-23 Genworth Financial, Inc. Process for determining a confidence factor for insurance underwriting suitable for use by an automated system
AU2003304166A1 (en) 2002-01-25 2005-01-21 Seurat Company Data integration system and method for presenting 3600 customer views
JP2003223559A (en) 2002-01-31 2003-08-08 Good Loan Kk Housing loan contract system and method
US20060074793A1 (en) * 2002-02-22 2006-04-06 Hibbert Errington W Transaction management system
US6651884B2 (en) 2002-03-26 2003-11-25 First Data Corporation System for ranking card reissue transactions
US20030225662A1 (en) 2002-04-01 2003-12-04 Horan James P. Managed asset platform system and method
US20030208385A1 (en) 2002-05-03 2003-11-06 Ing North America Insurance Corporation System and method for underwriting insurance
US7146367B2 (en) 2002-05-14 2006-12-05 Advectis, Inc. Document management system and method
US20030229553A1 (en) 2002-06-07 2003-12-11 Phanporn Kongyingyong Automated online underwriting
US7444302B2 (en) 2002-06-14 2008-10-28 Ellie Mae, Inc. Online system for fulfilling loan applications from loan originators
US20040181435A9 (en) 2002-06-14 2004-09-16 Reinsurance Group Of America Corporation Computerized system and method of performing insurability analysis
US9805417B2 (en) 2002-06-19 2017-10-31 Trading Technologies International, Inc. System and method for automated trading
US20040083164A1 (en) * 2002-07-08 2004-04-29 Schwartz Dennis P. System and method for generating residential loan documents from multiple and diverse databases
JP4158611B2 (en) * 2002-09-06 2008-10-01 株式会社日立製作所 Projection-type image display device
US20040138996A1 (en) 2002-10-18 2004-07-15 Daniel Bettenburg System and method for evaluating secondary market options for loans
US20040128170A1 (en) 2002-12-19 2004-07-01 Mackethan Edwin Robeson Method for intergrating insurance quotation, payment and issuance to mortgage loan origination process
US20040128230A1 (en) 2002-12-30 2004-07-01 Fannie Mae System and method for modifying attribute data pertaining to financial assets in a data processing system
US20050102226A1 (en) 2002-12-30 2005-05-12 Dror Oppenheimer System and method of accounting for mortgage related transactions
US7885889B2 (en) 2002-12-30 2011-02-08 Fannie Mae System and method for processing data pertaining to financial assets
WO2004061748A1 (en) 2002-12-30 2004-07-22 Fannie Mae System and method for defining loan products
US7593889B2 (en) 2002-12-30 2009-09-22 Fannie Mae System and method for processing data pertaining to financial assets
US7742981B2 (en) 2002-12-30 2010-06-22 Fannie Mae Mortgage loan commitment system and method
WO2004061561A2 (en) 2002-12-30 2004-07-22 Fannie Mae System and method for facilitating delivery of a loan to a secondary mortgage market purchaser
WO2004061557A2 (en) 2002-12-30 2004-07-22 Fannie Mae System and method for creating and tracking agreements for selling loans to a secondary market purchaser
AU2003294347A1 (en) 2002-12-30 2004-07-29 Fannie Mae System and method for processing data pertaining to financial assets
AU2003297295A1 (en) 2002-12-30 2004-07-29 Fannie Mae System and method of processing data pertaining to financial assets
AU2003291140A1 (en) 2002-12-30 2004-07-29 Fannie Mae System and method for facilitating sale of a loan to a secondary market purchaser
WO2004061564A2 (en) 2002-12-30 2004-07-22 Fannie Mae System and method for pricing loans in the secondary mortgage market
US20050080722A1 (en) 2002-12-30 2005-04-14 Kemper John L. Online system for delivery of loans to a secondary market purchaser
US20040199458A1 (en) 2003-04-07 2004-10-07 Thinh Ho System and method for on-line mortgage services
US20040267595A1 (en) 2003-06-30 2004-12-30 Idcocumentd, Llc. Worker and document management system
US20050108063A1 (en) 2003-11-05 2005-05-19 Madill Robert P.Jr. Systems and methods for assessing the potential for fraud in business transactions

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3316395A (en) * 1963-05-23 1967-04-25 Credit Corp Comp Credit risk computer
US6289319B1 (en) * 1984-05-24 2001-09-11 Lawrence B. Lockwood Automatic business and financial transaction processing system
US4876648A (en) * 1988-01-12 1989-10-24 Lloyd Clarke B System and method for implementing and administering a mortgage plan
US5323315A (en) * 1991-08-02 1994-06-21 Vintek, Inc. Computer system for monitoring the status of individual items of personal property which serve as collateral for securing financing
US5239462A (en) * 1992-02-25 1993-08-24 Creative Solutions Groups, Inc. Method and apparatus for automatically determining the approval status of a potential borrower
US5414621A (en) * 1992-03-06 1995-05-09 Hough; John R. System and method for computing a comparative value of real estate
US5563783A (en) * 1992-05-13 1996-10-08 The Trustees Of Columbia University In The City Of New York Method and system for securities pool allocation
US6070151A (en) * 1993-04-22 2000-05-30 Fibonacci Corporation System for the creation and collateralization of real estate mortgage investment conduit securities
US6105007A (en) * 1993-08-27 2000-08-15 Affinity Technology Group, Inc. Automatic financial account processing system
US5870721A (en) * 1993-08-27 1999-02-09 Affinity Technology Group, Inc. System and method for real time loan approval
US5940811A (en) * 1993-08-27 1999-08-17 Affinity Technology Group, Inc. Closed loop financial transaction method and apparatus
US5611052A (en) * 1993-11-01 1997-03-11 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US6029149A (en) * 1993-11-01 2000-02-22 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5930776A (en) * 1993-11-01 1999-07-27 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5537315A (en) * 1994-03-23 1996-07-16 Mitcham; Martin K. Method and apparatus for issuing insurance from kiosk
US6513018B1 (en) * 1994-05-05 2003-01-28 Fair, Isaac And Company, Inc. Method and apparatus for scoring the likelihood of a desired performance result
US5797133A (en) * 1994-08-31 1998-08-18 Strategic Solutions Group, Inc Method for automatically determining the approval status of a potential borrower
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5615268A (en) * 1995-01-17 1997-03-25 Document Authentication Systems, Inc. System and method for electronic transmission storage and retrieval of authenticated documents
US6367013B1 (en) * 1995-01-17 2002-04-02 Eoriginal Inc. System and method for electronic transmission, storage, and retrieval of authenticated electronic original documents
US5878403A (en) * 1995-09-12 1999-03-02 Cmsi Computer implemented automated credit application analysis and decision routing system
US6609109B1 (en) * 1995-10-12 2003-08-19 Freddie Mac Method for combining house price forecasts
US6584467B1 (en) * 1995-12-08 2003-06-24 Allstate Insurance Company Method and apparatus for obtaining data from vendors in real time
US6088686A (en) * 1995-12-12 2000-07-11 Citibank, N.A. System and method to performing on-line credit reviews and approvals
US5974372A (en) * 1996-02-12 1999-10-26 Dst Systems, Inc. Graphical user interface (GUI) language translator
US6014645A (en) * 1996-04-19 2000-01-11 Block Financial Corporation Real-time financial card application system
US5765144A (en) * 1996-06-24 1998-06-09 Merrill Lynch & Co., Inc. System for selecting liability products and preparing applications therefor
US5878404A (en) * 1996-10-08 1999-03-02 Mechanics Savings Bank System and method for managing the amortization of a loan
US6401070B1 (en) * 1996-10-11 2002-06-04 Freddie Mac System and method for providing house price forecasts based on repeat sales model
US5966699A (en) * 1996-10-11 1999-10-12 Zandi; Richard System and method for conducting loan auction over computer network
US6021202A (en) * 1996-12-20 2000-02-01 Financial Services Technology Consortium Method and system for processing electronic documents
US5930775A (en) * 1997-01-14 1999-07-27 Freddie Mac Method and apparatus for determining an optimal investment plan for distressed residential real estate loans
US6119103A (en) * 1997-05-27 2000-09-12 Visa International Service Association Financial risk prediction systems and methods therefor
US5940812A (en) * 1997-08-19 1999-08-17 Loanmarket Resources, L.L.C. Apparatus and method for automatically matching a best available loan to a potential borrower via global telecommunications network
US6112190A (en) * 1997-08-19 2000-08-29 Citibank, N.A. Method and system for commercial credit analysis
US6044362A (en) * 1997-09-08 2000-03-28 Neely; R. Alan Electronic invoicing and payment system
US5970464A (en) * 1997-09-10 1999-10-19 International Business Machines Corporation Data mining based underwriting profitability analysis
US6125349A (en) * 1997-10-01 2000-09-26 At&T Corp. Method and apparatus using digital credentials and other electronic certificates for electronic transactions
US6226624B1 (en) * 1997-10-24 2001-05-01 Craig J. Watson System and method for pre-authorization of individual account remote transactions
US5966700A (en) * 1997-12-23 1999-10-12 Federal Home Loan Bank Of Chicago Management system for risk sharing of mortgage pools
US6202053B1 (en) * 1998-01-23 2001-03-13 First Usa Bank, Na Method and apparatus for generating segmentation scorecards for evaluating credit risk of bank card applicants
US6385594B1 (en) * 1998-05-08 2002-05-07 Lendingtree, Inc. Method and computer network for co-ordinating a loan over the internet
US6611816B2 (en) * 1998-05-08 2003-08-26 Lendingtree, Inc. Method and computer network for co-ordinating a loan over the Internet
US6505176B2 (en) * 1998-06-12 2003-01-07 First American Credit Management Solutions, Inc. Workflow management system for an automated credit application system
US6035288A (en) * 1998-06-29 2000-03-07 Cendant Publishing, Inc. Interactive computer-implemented system and method for negotiating sale of goods and/or services
US20040002915A1 (en) * 1998-07-22 2004-01-01 Mcdonald Russell W. Mortgage loan data processing system and method for a loan broker
US6076070A (en) * 1998-07-23 2000-06-13 Cendant Publishing, Inc. Apparatus and method for on-line price comparison of competitor's goods and/or services over a computer network
US6438526B1 (en) * 1998-09-09 2002-08-20 Frederick T. Dykes System and method for transmitting and processing loan data
US6594635B1 (en) * 1998-10-24 2003-07-15 Marketcore.Com, Inc. Data processing system for providing an efficient market for insurance and reinsurance
US6405181B2 (en) * 1998-11-03 2002-06-11 Nextcard, Inc. Method and apparatus for real time on line credit approval
US6532450B1 (en) * 1998-12-09 2003-03-11 American Management Systems, Inc. Financial management system including an offset payment process
US6233566B1 (en) * 1998-12-31 2001-05-15 Ultraprise Corporation System, method and computer program product for online financial products trading
US6430539B1 (en) * 1999-05-06 2002-08-06 Hnc Software Predictive modeling of consumer financial behavior
US20020052815A1 (en) * 1999-12-30 2002-05-02 Johnson Christopher Donald Methods and apparatus for automated underwriting of segmentable portfolio assets
US20020032635A1 (en) * 2000-01-06 2002-03-14 Stewart Harris Systems and methods for monitoring credit of trading couterparties
US20040030616A1 (en) * 2000-02-25 2004-02-12 Andrew Florance System and method for collection, distribution, and use of information in connection with commercial real estate
US20020052835A1 (en) * 2000-04-28 2002-05-02 Toscano Paul James On line loan process
US20030033242A1 (en) * 2000-06-03 2003-02-13 Joan Lynch System and method for automated process of deal structuring
US6988082B1 (en) * 2000-06-13 2006-01-17 Fannie Mae Computerized systems and methods for facilitating the flow of capital through the housing finance industry
US20020059137A1 (en) * 2000-06-27 2002-05-16 Freeman Douglas K. Online mortgate application processing and tracking system
US20020091550A1 (en) * 2000-06-29 2002-07-11 White Mitchell Franklin System and method for real-time rating, underwriting and policy issuance
US20020035520A1 (en) * 2000-08-02 2002-03-21 Weiss Allan N. Property rating and ranking system and method
US20020087389A1 (en) * 2000-08-28 2002-07-04 Michael Sklarz Value your home
US20020029194A1 (en) * 2000-09-07 2002-03-07 Richard Lewis System and method of managing financial transactions over an electronic network
US20020029154A1 (en) * 2000-09-07 2002-03-07 Hnc Software, Inc. Mechanism and method for dynamic question handling through an electronic interface
US20020038318A1 (en) * 2000-09-22 2002-03-28 Cochran Jeffrey M. System and method for managing transferable records
US20020040339A1 (en) * 2000-10-02 2002-04-04 Dhar Kuldeep K. Automated loan processing system and method
US20020111835A1 (en) * 2000-11-06 2002-08-15 Hele John C. R. Underwriting insurance
US20020087364A1 (en) * 2000-11-07 2002-07-04 Lerner Andrew S. System and method for enabling real time underwriting of insurance policies
US20020099650A1 (en) * 2000-11-15 2002-07-25 Cole James A. Method for automatically processing a financial loan application and the system thereof
US20020077968A1 (en) * 2000-12-14 2002-06-20 International Business Machines Corporation Data sampling with priority to conforming component ratios
US20020091630A1 (en) * 2001-01-10 2002-07-11 Akiyoshi Inoue Loan intermediary processing system and method thereof
US20020111901A1 (en) * 2001-01-24 2002-08-15 Whitney Patrick G. Loan servicing system
US20030046223A1 (en) * 2001-02-22 2003-03-06 Stuart Crawford Method and apparatus for explaining credit scores
US20020138414A1 (en) * 2001-03-26 2002-09-26 Baker Charles Pitman Method and system and article of manufacture for a rules based automated loan approval system
US7089503B1 (en) * 2001-04-04 2006-08-08 Fannie Mae Mortgage loan customization system and process
US20030036994A1 (en) * 2001-04-12 2003-02-20 Brad Witzig Automated mortgage lender processing system
US20030110249A1 (en) * 2001-06-08 2003-06-12 Bryan Buus System and method for monitoring key performance indicators in a business
US20030023610A1 (en) * 2001-07-27 2003-01-30 Bove Stephen B. Online real and personal property management system and method
US20030028478A1 (en) * 2001-08-01 2003-02-06 Kinney James Michael System and method for originating turbocharged ("Turbo TM") loans
US20030033241A1 (en) * 2001-08-08 2003-02-13 Adi Harari Methods and systems for automated loan origination, processing and approval
US20030036995A1 (en) * 2001-08-16 2003-02-20 Lazerson Jeffrey M. Credit/financing process
US20030036996A1 (en) * 2001-08-16 2003-02-20 Lazerson Jeffrey M. Credit/financing process
US20030065614A1 (en) * 2001-10-01 2003-04-03 Sweeney Joan M. Method and system for rules based underwriting
US20030093366A1 (en) * 2001-11-13 2003-05-15 Halper Steven C. Automated loan risk assessment system and method
US20030177032A1 (en) * 2001-12-31 2003-09-18 Bonissone Piero Patrone System for summerizing information for insurance underwriting suitable for use by an automated system
US20030182159A1 (en) * 2001-12-31 2003-09-25 Bonissone Piero Patrone Process for summarizing information for insurance underwriting suitable for use by an automated system
US20030144949A1 (en) * 2002-01-25 2003-07-31 Ed Blanch Web-based mortgage broker application
US20030172025A1 (en) * 2002-02-08 2003-09-11 Gallina Mike A. Computerized system and method for qualifying mortgage loan clients
US20030167191A1 (en) * 2002-02-25 2003-09-04 Slabonik Elizabeth Ann System and method for underwriting review in an insurance system
US20040030649A1 (en) * 2002-05-06 2004-02-12 Chris Nelson System and method of application processing
US20040019517A1 (en) * 2002-07-26 2004-01-29 Fidelity National Information Solutions, Inc. Method of establishing an insurable value estimate for a real estate property
US20040107161A1 (en) * 2002-08-13 2004-06-03 International Business Machines Corporation System, method and computer program for managing credit decisions
US20040034592A1 (en) * 2002-08-15 2004-02-19 Limin Hu Loan origination system interface for online loan application processing
US20040049439A1 (en) * 2002-09-06 2004-03-11 David Johnston Interactive electronic bill payment system
US20040049445A1 (en) * 2002-09-10 2004-03-11 Nanda Kishore Financial services automation
US20040059653A1 (en) * 2002-09-24 2004-03-25 Fidelity National Financial, Inc. System and method for rendering automated real property title decisions
US20040064402A1 (en) * 2002-09-27 2004-04-01 Wells Fargo Home Mortgage, Inc. Method of refinancing a mortgage loan and a closing package for same
US20040122717A1 (en) * 2002-10-21 2004-06-24 James Hancock Claim submission system and method

Cited By (142)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7966234B1 (en) 1999-05-17 2011-06-21 Jpmorgan Chase Bank. N.A. Structured finance performance analytics system
US7680731B1 (en) 2000-06-07 2010-03-16 Jpmorgan Chase Bank, N.A. System and method for executing deposit transactions over the internet
US7680732B1 (en) 2000-06-07 2010-03-16 Jpmorgan Chase Bank, N.A. System and method for executing deposit transactions over the internet
US7702580B1 (en) 2000-06-13 2010-04-20 Fannie Mae System and method for mortgage loan pricing, sale and funding
US8244628B1 (en) 2000-06-13 2012-08-14 Fannie Mae Computerized systems and methods for facilitating the flow of capital through the housing finance industry
US7890407B2 (en) 2000-11-03 2011-02-15 Jpmorgan Chase Bank, N.A. System and method for estimating conduit liquidity requirements in asset backed commercial paper
US8548886B1 (en) 2002-05-31 2013-10-01 Jpmorgan Chase Bank, N.A. Account opening system, method and computer program product
US8364579B2 (en) 2002-06-14 2013-01-29 Ellie Mae, Inc. Online system for fulfilling loan applications from loan originators
US8117117B2 (en) 2002-08-15 2012-02-14 Ellie Mae, Inc. Loan origination system interface for online loan application processing
US8666879B1 (en) * 2002-12-30 2014-03-04 Fannie Mae Method and system for pricing forward commitments for mortgage loans and for buying committed loans
US7809633B2 (en) 2002-12-30 2010-10-05 Fannie Mae System and method for pricing loans in the secondary mortgage market
US8024265B2 (en) 2002-12-30 2011-09-20 Fannie Mae System and method for verifying loan data at delivery
US9928546B2 (en) 2002-12-30 2018-03-27 Fannie Mae System and method for processing data pertaining to financial assets
US20050102225A1 (en) * 2002-12-30 2005-05-12 Dror Oppenheimer System and method for processing data pertaining to financial assets
US7979346B2 (en) 2002-12-30 2011-07-12 Fannie Mae System and method for pricing loans in the secondary mortgage market
US7860787B2 (en) 2002-12-30 2010-12-28 Fannie Mae System and method for modifying attribute data pertaining to financial assets in a data processing system
US8060440B2 (en) 2002-12-30 2011-11-15 Fannie Mae System and method for modifying attribute data pertaining to financial assets in a data processing system
US8065211B2 (en) 2002-12-30 2011-11-22 Fannie Mae System and method for creating and tracking agreements for selling loans to a secondary market purchaser
US8032450B2 (en) 2002-12-30 2011-10-04 Fannie Mae Loan commitment system and method
US8423450B2 (en) 2002-12-30 2013-04-16 Fannie Mae System and method for processing data pertaining to financial assets
US8515861B2 (en) 2002-12-30 2013-08-20 Fannie Mae System and method for facilitating sale of a loan to a secondary market purchaser
US7742981B2 (en) 2002-12-30 2010-06-22 Fannie Mae Mortgage loan commitment system and method
US7747519B2 (en) 2002-12-30 2010-06-29 Fannie Mae System and method for verifying loan data at delivery
US7885889B2 (en) 2002-12-30 2011-02-08 Fannie Mae System and method for processing data pertaining to financial assets
US7770184B2 (en) 2003-06-06 2010-08-03 Jp Morgan Chase Bank Integrated trading platform architecture
US7970688B2 (en) 2003-07-29 2011-06-28 Jp Morgan Chase Bank Method for pricing a trade
US9916624B2 (en) 2003-09-19 2018-03-13 Oracle International Corporation Techniques for arranging views and navigating in a web-centric insurance management system
US8463624B2 (en) 2003-09-19 2013-06-11 Oracle International Corporation Techniques for ensuring data security among participants in a web-centric insurance management system
US20090083076A1 (en) * 2003-09-19 2009-03-26 Hashim Safaa H Techniques for ensuring data security among participants in a web-centric insurance management system
US20090083077A1 (en) * 2003-09-19 2009-03-26 Hashim Safaa H Techniques for arranging views and navigating in a web-centric insurance management system
US20090089101A1 (en) * 2003-09-19 2009-04-02 Hashim Safaa H Techniques for underwriting insurance policies using web-centric insurance management system
US20050131787A1 (en) * 2003-12-16 2005-06-16 Monteleone Leonard C. System and method for trading of mortgage backed securities
US20050216394A1 (en) * 2003-12-16 2005-09-29 Monteleone Leonard C Computer-based system and method for confirming failed trades of securities
US20050222943A1 (en) * 2003-12-16 2005-10-06 Monteleone Leonard C System and method for processing failed trades of mortgage backed securities
US20090299621A1 (en) * 2004-01-29 2009-12-03 Xanavi Informatics Corporation Automobile navigation apparatus
US8423447B2 (en) 2004-03-31 2013-04-16 Jp Morgan Chase Bank System and method for allocating nominal and cash amounts to trades in a netted trade
US9143514B2 (en) 2004-07-02 2015-09-22 Ellie Mae, Inc. Enterprise security management system using hierarchical organization and multiple ownership structure
US20060004651A1 (en) * 2004-07-02 2006-01-05 Corr Jonathan H Loan origination software system for processing mortgage loans over a distributed network
US8990254B2 (en) * 2004-07-02 2015-03-24 Ellie Mae, Inc. Loan origination software system for processing mortgage loans over a distributed network
US9313209B2 (en) * 2004-07-02 2016-04-12 Ellie Mae, Inc. Loan origination software system for processing mortgage loans over a distributed network
US8762357B2 (en) 2004-07-02 2014-06-24 Ellie Mae. Inc. Enterprise security management system using hierarchical organization and multiple ownership structure
US20150262292A1 (en) * 2004-07-02 2015-09-17 Ellie Mae, Inc. Loan origination software system for processing mortgage loans over a distributed network
US8126920B2 (en) 2004-07-02 2012-02-28 Ellie Mae, Inc. Enterprise security management system using hierarchical organization and multiple ownership structure
US7693782B1 (en) 2004-08-03 2010-04-06 Fannie Mae Method and system for evaluating a loan
US8090639B2 (en) 2004-08-06 2012-01-03 Jpmorgan Chase Bank, N.A. Method and system for creating and marketing employee stock option mirror image warrants
US20060036465A1 (en) * 2004-08-13 2006-02-16 O'donnell Lee F Online interactive interface and automated processing for loan origination and underwriting
US20050203839A1 (en) * 2004-12-03 2005-09-15 Phoenix Analytic Services, Inc. Method for Transferring Mortgage Servicing Rights
US8688569B1 (en) * 2005-03-23 2014-04-01 Jpmorgan Chase Bank, N.A. System and method for post closing and custody services
US8175889B1 (en) 2005-04-06 2012-05-08 Experian Information Solutions, Inc. Systems and methods for tracking changes of address based on service disconnect/connect data
US8065264B1 (en) 2005-04-11 2011-11-22 Experian Information Solutions, Inc. Systems and methods for optimizing database queries
US7908242B1 (en) 2005-04-11 2011-03-15 Experian Information Solutions, Inc. Systems and methods for optimizing database queries
US8583593B1 (en) 2005-04-11 2013-11-12 Experian Information Solutions, Inc. Systems and methods for optimizing database queries
US20070050287A1 (en) * 2005-08-26 2007-03-01 Capozza Dennis R Method for structuring a new loan
US7818238B1 (en) 2005-10-11 2010-10-19 Jpmorgan Chase Bank, N.A. Upside forward with early funding provision
US8412607B2 (en) 2006-02-03 2013-04-02 Jpmorgan Chase Bank, National Association Price earnings derivative financial product
US8280794B1 (en) 2006-02-03 2012-10-02 Jpmorgan Chase Bank, National Association Price earnings derivative financial product
US7716107B1 (en) 2006-02-03 2010-05-11 Jpmorgan Chase Bank, N.A. Earnings derivative financial product
US20070255641A1 (en) * 2006-04-28 2007-11-01 Harrington Kevin F Computer interface for trading bonds
US7620578B1 (en) 2006-05-01 2009-11-17 Jpmorgan Chase Bank, N.A. Volatility derivative financial product
US8392334B2 (en) 2006-08-17 2013-03-05 Experian Information Solutions, Inc. System and method for providing a score for a used vehicle
US11257126B2 (en) 2006-08-17 2022-02-22 Experian Information Solutions, Inc. System and method for providing a score for a used vehicle
US10380654B2 (en) 2006-08-17 2019-08-13 Experian Information Solutions, Inc. System and method for providing a score for a used vehicle
US7912865B2 (en) 2006-09-26 2011-03-22 Experian Marketing Solutions, Inc. System and method for linking multiple entities in a business database
US9563916B1 (en) 2006-10-05 2017-02-07 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US11631129B1 (en) 2006-10-05 2023-04-18 Experian Information Solutions, Inc System and method for generating a finance attribute from tradeline data
US10121194B1 (en) 2006-10-05 2018-11-06 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US10963961B1 (en) 2006-10-05 2021-03-30 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US7827096B1 (en) 2006-11-03 2010-11-02 Jp Morgan Chase Bank, N.A. Special maturity ASR recalculated timing
US7885892B1 (en) * 2006-11-08 2011-02-08 Fannie Mae Method and system for assessing repurchase risk
US7783565B1 (en) * 2006-11-08 2010-08-24 Fannie Mae Method and system for assessing repurchase risk
US8463697B1 (en) 2007-01-10 2013-06-11 Liberty Home Equity Solutions, Inc. Method and system for providing a loan using equity in a new home
US10078868B1 (en) 2007-01-31 2018-09-18 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US10891691B2 (en) 2007-01-31 2021-01-12 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US11443373B2 (en) 2007-01-31 2022-09-13 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US8606666B1 (en) 2007-01-31 2013-12-10 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US10402901B2 (en) 2007-01-31 2019-09-03 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US10650449B2 (en) 2007-01-31 2020-05-12 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US9619579B1 (en) 2007-01-31 2017-04-11 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US11908005B2 (en) 2007-01-31 2024-02-20 Experian Information Solutions, Inc. System and method for providing an aggregation tool
US9342783B1 (en) 2007-03-30 2016-05-17 Consumerinfo.Com, Inc. Systems and methods for data verification
US11308170B2 (en) 2007-03-30 2022-04-19 Consumerinfo.Com, Inc. Systems and methods for data verification
US10437895B2 (en) 2007-03-30 2019-10-08 Consumerinfo.Com, Inc. Systems and methods for data verification
US8024264B2 (en) 2007-04-12 2011-09-20 Experian Marketing Solutions, Inc. Systems and methods for determining thin-file records and determining thin-file risk levels
US8738515B2 (en) 2007-04-12 2014-05-27 Experian Marketing Solutions, Inc. Systems and methods for determining thin-file records and determining thin-file risk levels
US8271378B2 (en) 2007-04-12 2012-09-18 Experian Marketing Solutions, Inc. Systems and methods for determining thin-file records and determining thin-file risk levels
US8364588B2 (en) 2007-05-25 2013-01-29 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US9251541B2 (en) 2007-05-25 2016-02-02 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US20090037321A1 (en) * 2007-08-02 2009-02-05 Bank Of America Corporation System and method for processing loan applications
US7761356B2 (en) * 2007-08-02 2010-07-20 Bank Of America Corporation System and method for processing loan applications
US8301574B2 (en) 2007-09-17 2012-10-30 Experian Marketing Solutions, Inc. Multimedia engagement study
US8600798B1 (en) 2007-09-21 2013-12-03 Ellie Mae, Inc. Loan screening
US10528545B1 (en) 2007-09-27 2020-01-07 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US11347715B2 (en) 2007-09-27 2022-05-31 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US9690820B1 (en) 2007-09-27 2017-06-27 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US20090240609A1 (en) * 2008-03-19 2009-09-24 Soogyung Cho System and method for tracking and analyzing loans involved in asset-backed securities
US10075446B2 (en) 2008-06-26 2018-09-11 Experian Marketing Solutions, Inc. Systems and methods for providing an integrated identifier
US11157872B2 (en) 2008-06-26 2021-10-26 Experian Marketing Solutions, Llc Systems and methods for providing an integrated identifier
US11769112B2 (en) 2008-06-26 2023-09-26 Experian Marketing Solutions, Llc Systems and methods for providing an integrated identifier
US8954459B1 (en) 2008-06-26 2015-02-10 Experian Marketing Solutions, Inc. Systems and methods for providing an integrated identifier
US8001042B1 (en) 2008-07-23 2011-08-16 Experian Information Solutions, Inc. Systems and methods for detecting bust out fraud using credit data
US7991689B1 (en) 2008-07-23 2011-08-02 Experian Information Solutions, Inc. Systems and methods for detecting bust out fraud using credit data
US8626560B1 (en) 2009-06-30 2014-01-07 Experian Information Solutions, Inc. System and method for evaluating vehicle purchase loyalty
US8364518B1 (en) 2009-07-08 2013-01-29 Experian Ltd. Systems and methods for forecasting household economics
US8706615B2 (en) * 2009-12-04 2014-04-22 Robert A. Merkle Systems and methods for evaluating the ability of borrowers to repay loans
US20110137788A1 (en) * 2009-12-04 2011-06-09 Merkle Robert A Systems and methods for evaluating the ability of borrowers to repay loans
US8738514B2 (en) 2010-02-18 2014-05-27 Jpmorgan Chase Bank, N.A. System and method for providing borrow coverage services to short sell securities
US8352354B2 (en) 2010-02-23 2013-01-08 Jpmorgan Chase Bank, N.A. System and method for optimizing order execution
US8725613B1 (en) 2010-04-27 2014-05-13 Experian Information Solutions, Inc. Systems and methods for early account score and notification
US9152727B1 (en) 2010-08-23 2015-10-06 Experian Marketing Solutions, Inc. Systems and methods for processing consumer information for targeted marketing applications
US8639616B1 (en) 2010-10-01 2014-01-28 Experian Information Solutions, Inc. Business to contact linkage system
US20120116944A1 (en) * 2010-11-05 2012-05-10 Dicarlo Dean System and Method of Electronic Exchange for Residential Mortgages
US9147042B1 (en) 2010-11-22 2015-09-29 Experian Information Solutions, Inc. Systems and methods for data verification
US9684905B1 (en) 2010-11-22 2017-06-20 Experian Information Solutions, Inc. Systems and methods for data verification
US10176233B1 (en) 2011-07-08 2019-01-08 Consumerinfo.Com, Inc. Lifescore
US11665253B1 (en) 2011-07-08 2023-05-30 Consumerinfo.Com, Inc. LifeScore
US9483606B1 (en) 2011-07-08 2016-11-01 Consumerinfo.Com, Inc. Lifescore
US10798197B2 (en) 2011-07-08 2020-10-06 Consumerinfo.Com, Inc. Lifescore
US8775299B2 (en) 2011-07-12 2014-07-08 Experian Information Solutions, Inc. Systems and methods for large-scale credit data processing
US9853959B1 (en) 2012-05-07 2017-12-26 Consumerinfo.Com, Inc. Storage and maintenance of personal data
US11356430B1 (en) 2012-05-07 2022-06-07 Consumerinfo.Com, Inc. Storage and maintenance of personal data
US9697263B1 (en) 2013-03-04 2017-07-04 Experian Information Solutions, Inc. Consumer data request fulfillment system
US10580025B2 (en) 2013-11-15 2020-03-03 Experian Information Solutions, Inc. Micro-geographic aggregation system
US10102536B1 (en) 2013-11-15 2018-10-16 Experian Information Solutions, Inc. Micro-geographic aggregation system
US9529851B1 (en) 2013-12-02 2016-12-27 Experian Information Solutions, Inc. Server architecture for electronic data quality processing
US11847693B1 (en) 2014-02-14 2023-12-19 Experian Information Solutions, Inc. Automatic generation of code for attributes
US11107158B1 (en) 2014-02-14 2021-08-31 Experian Information Solutions, Inc. Automatic generation of code for attributes
US10262362B1 (en) 2014-02-14 2019-04-16 Experian Information Solutions, Inc. Automatic generation of code for attributes
US9576030B1 (en) 2014-05-07 2017-02-21 Consumerinfo.Com, Inc. Keeping up with the joneses
US10936629B2 (en) 2014-05-07 2021-03-02 Consumerinfo.Com, Inc. Keeping up with the joneses
US11620314B1 (en) 2014-05-07 2023-04-04 Consumerinfo.Com, Inc. User rating based on comparing groups
US10019508B1 (en) 2014-05-07 2018-07-10 Consumerinfo.Com, Inc. Keeping up with the joneses
US20160078534A1 (en) * 2014-09-15 2016-03-17 The Toronto-Dominion Bank Method and network for transferring a loan
US10445152B1 (en) 2014-12-19 2019-10-15 Experian Information Solutions, Inc. Systems and methods for dynamic report generation based on automatic modeling of complex data structures
US10242019B1 (en) 2014-12-19 2019-03-26 Experian Information Solutions, Inc. User behavior segmentation using latent topic detection
US11010345B1 (en) 2014-12-19 2021-05-18 Experian Information Solutions, Inc. User behavior segmentation using latent topic detection
US11550886B2 (en) 2016-08-24 2023-01-10 Experian Information Solutions, Inc. Disambiguation and authentication of device users
US10678894B2 (en) 2016-08-24 2020-06-09 Experian Information Solutions, Inc. Disambiguation and authentication of device users
US11227001B2 (en) 2017-01-31 2022-01-18 Experian Information Solutions, Inc. Massive scale heterogeneous data ingestion and user resolution
US11681733B2 (en) 2017-01-31 2023-06-20 Experian Information Solutions, Inc. Massive scale heterogeneous data ingestion and user resolution
US11734234B1 (en) 2018-09-07 2023-08-22 Experian Information Solutions, Inc. Data architecture for supporting multiple search models
US10963434B1 (en) 2018-09-07 2021-03-30 Experian Information Solutions, Inc. Data architecture for supporting multiple search models
US11880377B1 (en) 2021-03-26 2024-01-23 Experian Information Solutions, Inc. Systems and methods for entity resolution

Also Published As

Publication number Publication date
US7747519B2 (en) 2010-06-29
AU2003295807A1 (en) 2004-07-29
WO2004061561A2 (en) 2004-07-22
WO2004061566A8 (en) 2004-11-18
US8024265B2 (en) 2011-09-20
AU2003295787A1 (en) 2004-07-29
AU2003295787A8 (en) 2004-07-29
US20100268641A1 (en) 2010-10-21
WO2004061561A3 (en) 2005-02-24
WO2004061566A2 (en) 2004-07-22
US20040215554A1 (en) 2004-10-28
WO2004061566A3 (en) 2005-01-06
AU2003295807A8 (en) 2004-07-29

Similar Documents

Publication Publication Date Title
US8024265B2 (en) System and method for verifying loan data at delivery
US8515861B2 (en) System and method for facilitating sale of a loan to a secondary market purchaser
US7979346B2 (en) System and method for pricing loans in the secondary mortgage market
US8065211B2 (en) System and method for creating and tracking agreements for selling loans to a secondary market purchaser
US7593889B2 (en) System and method for processing data pertaining to financial assets
US8060440B2 (en) System and method for modifying attribute data pertaining to financial assets in a data processing system
US9928546B2 (en) System and method for processing data pertaining to financial assets
US8032450B2 (en) Loan commitment system and method
US20050080722A1 (en) Online system for delivery of loans to a secondary market purchaser
US20050102225A1 (en) System and method for processing data pertaining to financial assets
US20040220873A1 (en) System and method for defining loan products
US20040225595A1 (en) System and method for processing data pertaining to financial assets

Legal Events

Date Code Title Description
AS Assignment

Owner name: FANNIE MAE, DISTRICT OF COLUMBIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KEMPER, JOHN L.;COLEMAN, DAVID A.;REEL/FRAME:014846/0931;SIGNING DATES FROM 20040226 TO 20040608

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION