Abstract:
A method for managing business information by a first business entity using a server system is provided. The server system is coupled to a centralized database and at least one client system. The method includes receiving at the server system business information relating to at least one second business entity from the client system, storing the business information received at the server system in the centralized database, tracking the business information stored in the centralized database, updating the centralized database periodically with newly received business information to maintain the business information, and providing the business information in response to an inquiry.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    This invention relates generally to managing risk management information and, more particularly, to network-based methods and systems for managing risk management information.  
           [0002]    Businesses engaging in complex deals, such as commercial financing, mergers, acquisitions and real estate transactions, generally conduct a due diligence analysis to access the financial strength, operational characteristics of a business, collateral and/or business value, management strength, industry dynamics, and the proposed structure of the transaction and the party or parties involved in the deal. The due diligence analysis facilitates the financing business to better evaluate and manage the risk associated with the deal after the transaction closes.  
           [0003]    During a due diligence analysis, information, known as risk management (RM) information, is gathered from many sources. RM information is often complex and relates to various relevant areas of the overall transaction. Therefore, a number of different members of a due diligence team may need to know the same RM information in evaluating the deal. Internal deal teams typically manually and individually collect data as part of the due diligence analysis. The efforts are often duplicated, and as such, the data may be entered multiple times on multiple different systems throughout the financing business. For example, in a transaction involving the lending on accounts receivable and inventory to secure a formula based loan to a business, both an underwriting team and a legal team may be involved. The underwriting team may be focused on (i) what the collateral is, the value of the collateral, and how the collateral is valued, (ii) the financial strength and operation of the business, (iii) the management strength, (iv) the overall structure of the transaction, and (v) other factors relating to the business, industry, and collateral involved in the deal. The legal team may be focused on (i) the location of the collateral, (ii) the structure of the transaction, (iii) an understanding of the legal entities involved, and (iv) other legal factors surrounding the business, industry and collateral involved in the deal. During the due diligence analysis, both the underwriting and the legal teams will collect certain RM information to be evaluated. Although the underwriting team and the legal team may have different concerns when evaluating the RM information, much of the RM information being evaluated is the same.  
           [0004]    Individual collection of RM information by various internal deal teams increases the risk of overlapping data collection and decreases time efficiency. Further, individual reporting by internal teams to other internal teams or external teams increases the risk of providing inconsistent or incomplete data during the documentation process, which may result in increased cycle time and costs. For example, in the collateral transaction described above, external legal counsel may request information relating to the location of the collateral from the borrower. The underwriting team may also request information from the borrower regarding the location of the collateral. Because the information is collected both manually and individually, the underwriting team may have no knowledge that the data had been previously collected by the legal team. Consequently, documentation cycle time and costs are increased. Additionally, because various deal teams may collect the RM information, the RM information may not be centralized for future monitoring and management.  
         BRIEF DESCRIPTION OF THE INVENTION  
         [0005]    In one aspect, a method for managing business information by a first business entity using a server system is provided. The server system is coupled to a centralized database and at least one client system. The method includes receiving at the server system business information relating to at least one second business entity from the client system, storing the business information received at the server system in the centralized database, tracking the business information stored in the centralized database, updating the centralized database periodically with newly received business information to maintain the business information, and providing the business information in response to an inquiry.  
           [0006]    In another aspect, a method for managing risk management (RM) information for a first business entity using a web-based system is provided. The system employs a server system coupled to a centralized database and at least one client system. The RM information includes at least one of business information, accounts payable, accounts receivable, an availability analysis, a covenant compliance, coverage ratios, financial statements, financial statement and availability projections, a capital structure, income statements, an inventory, a leverage analysis, a loan profile, collateral, guarantors, machinery and equipment, real estate, a liquidation value, amortization information, a capital raising history, an equity valuation, and other documents and information relating to the financial condition of at least one second business entity. The method includes receiving at the server system RM information relating to at least one second business entity from a user through the client system, storing RM information received at the server system in the centralized database, and tracking RM information including compiling data reports, exporting RM information, and linking documents to at least one of the second business entities. The method also includes updating the centralized database with RM information including adding and deleting information to revise existing RM information, and providing RM information in response to an inquiry, including downloading requested information from the server system and displaying requested information on the client system, the inquiry including utilizing at least one pull-down lists, check boxes, radio buttons, and hypertext links. The method also includes notifying a user through an electronic message of the results of a review of RM information, including findings and recommendations relating to the RM information, and providing a report of the review results by transmitting an electronic report to the managerial user system, which includes a summary of the review of RM information, and an internal deal team&#39;s findings and recommendations such that managerial oversight of the RM information and electronic data interchange between a user, the first business entity, and the second business entity are facilitated.  
           [0007]    In another aspect, a network based system for managing business information by a first business entity is provided. The system includes a client system comprising a browser, a centralized database for storing information, and a server system configured to be coupled to the client system and the database. The server system is further configured to receive business information relating to at least one second business entity from the client system, store the business information in the centralized database, track the business information, update the centralized database periodically with newly received business information to maintain the business information, provide said business information in response to an inquiry by a user, and notify users electronically of a review of the business information by a deal team, including said deal team&#39;s findings and recommendations relating to the review of said business information.  
           [0008]    In another aspect, a computer program embodied on a computer readable medium for managing risk management (RM) information by a first business entity analyzing at least one second business entity is provided. The program includes a code segment that receives RM information and then maintains a database by adding, deleting and updating RM information, provides users with access to RM information, generates data reports based on RM information for at least one of each second business entity and a selected group of second business entities, and compiles a plurality of data reports that includes at least one of business information, accounts payable, accounts receivable, an availability analysis, a covenant compliance, coverage ratios, financial statements, financial statement and availability projections, a capital structure, income statements, an inventory, a leverage analysis, a loan profile, collateral, guarantors, machinery and equipment, real estate, a liquidation value, amortization information, a capital raising history, an equity valuation, and other documents and information relating to the financial condition of each second business entity. The code segment also compiles a plurality of data reports that includes a selected subset of at least one of business information, accounts payable, accounts receivable, the availability analysis, the covenant compliance, coverage ratios, financial statements, financial statement and availability projections, the capital structure, income statements, the inventory, the leverage analysis, the loan profile, collateral, guarantors, machinery and equipment, real estate, the liquidation value, amortization information, the capital raising history, the equity valuation, and other documents and information relating to the financial condition of each second business entity, and compiles a plurality of data reports that includes at least one of business information, accounts payable, accounts receivable, the availability analysis, the covenant compliance, coverage ratios, financial statements, financial statement and availability projections, the capital structure, income statements, the inventory, the leverage analysis, the loan profile, collateral, guarantors, machinery and equipment, real estate, the liquidation value, amortization information, the capital raising history, the equity valuation, and other documents and information relating to the financial condition of the selected group of second business entities. The code segment also compiles a plurality of data reports that includes a selected subset of at least one of business information, accounts payable, accounts receivable, the availability analysis, the covenant compliance, coverage ratios, financial statements, financial statement and availability projections, the capital structure, income statements, the inventory, the leverage analysis, the loan profile, collateral, guarantors, machinery and equipment, real estate, the liquidation value, amortization information, the capital raising history, the equity valuation, and other documents and information relating to the financial condition of the selected group of second business entities. The code segment also exports RM information relating to at least one second business entity by a user from the database to at least one other computer program for review, exports RM information relating to the selected group of second business entities selected by a user from the database to at least one other computer program for review, links documents to at least one second business entity such that a user can access said documents during a review of the second business entity, links documents to the selected group of second business entities such that a user can access the documents during a review of the second business entities, notifies a user of a review of RM information by a deal team member, and provides a report comprising a summary of the review of RM information, including the deal team&#39;s findings and recommendations.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]    [0009]FIG. 1 is a simplified block diagram of a Risk Management Coordination System (RMCS) in accordance with one embodiment of the present invention.  
         [0010]    [0010]FIG. 2 is an expanded version block diagram of an example embodiment of a server architecture of the RMCS.  
         [0011]    [0011]FIG. 3 shows a configuration of a database within the database server of the server system including other related server components.  
         [0012]    [0012]FIG. 4 is a flowchart of the processes employed by RMCS to facilitate use.  
         [0013]    [0013]FIG. 5 is an example embodiment of a user interface displaying a login page of a RMCS.  
         [0014]    [0014]FIG. 6 is an example embodiment of a user interface displaying a home page of an account section in a RMCS.  
         [0015]    [0015]FIG. 7 is an example embodiment of a user interface displaying account payable trends for an account in a RMCS.  
         [0016]    [0016]FIG. 8 is an example embodiment of a user interface displaying account receivable trends for an account in a RMCS.  
         [0017]    [0017]FIG. 9 is an example embodiment of a user interface displaying availability trends for an account in a RMCS.  
         [0018]    [0018]FIG. 10 is an example embodiment of a user interface displaying covenant compliance for an account in a RMCS.  
         [0019]    [0019]FIG. 11 is an example embodiment of a user interface displaying coverage ratios for an account in a RMCS.  
         [0020]    [0020]FIG. 12 is an example embodiment of a user interface displaying income statement trends for an account in a RMCS.  
         [0021]    [0021]FIG. 13 is an example embodiment of a user interface displaying inventory trends for an account in a RMCS.  
         [0022]    [0022]FIG. 14 is an example embodiment of a user interface displaying total leverage and senior leverage over time for an account in a RMCS.  
         [0023]    [0023]FIG. 15 is an example embodiment of a user interface displaying risk measures for an account in a RMCS.  
         [0024]    [0024]FIGS. 16A through 16C display an example embodiment of a user interface displaying asset based portfolio management reports for an account in a RMCS.  
         [0025]    [0025]FIG. 17 is an example embodiment of a user interface displaying a collateral availability summary for an account in a RMCS.  
         [0026]    [0026]FIG. 18 is an example embodiment of a user interface displaying collateral security and guarantors information for an account in a RMCS.  
         [0027]    [0027]FIG. 19 is an example embodiment of a user interface displaying collateral performance commentary information for an account in a RMCS.  
         [0028]    [0028]FIG. 20 is an example embodiment of a user interface displaying account receivable ineligibles information for an account in a RMCS.  
         [0029]    [0029]FIG. 21 is an example embodiment of a user interface displaying account receivable ineligibles information for an account in a RMCS.  
         [0030]    [0030]FIG. 22 is an example embodiment of a user interface displaying account payable concentration information for an account in a RMCS.  
         [0031]    [0031]FIG. 23 is an example embodiment of a user interface displaying account payable aging information for an account in a RMCS.  
         [0032]    [0032]FIG. 24 is an example embodiment of a user interface displaying account receivable aging information for an account in a RMCS.  
         [0033]    [0033]FIG. 25 is an example embodiment of a user interface displaying account receivable concentration information for an account in a RMCS.  
         [0034]    [0034]FIG. 26 is an example embodiment of a user interface displaying account receivable sales and receivables statistics information for an account in a RMCS.  
         [0035]    [0035]FIG. 27 is an example embodiment of a user interface displaying account receivable verification information for an account in a RMCS.  
         [0036]    [0036]FIG. 28 is an example embodiment of a user interface displaying inventory appraisal information for an account in a RMCS.  
         [0037]    [0037]FIG. 29 is an example embodiment of a user interface displaying inventory composition information for an account in a RMCS.  
         [0038]    [0038]FIG. 30 is an example embodiment of a user interface displaying inventory by product information for an account in a RMCS.  
         [0039]    [0039]FIG. 31 is an example embodiment of a user interface displaying inventory gross margin information for an account in a RMCS.  
         [0040]    [0040]FIG. 32 is an example embodiment of a user interface displaying inventory by location information for an account in a RMCS.  
         [0041]    [0041]FIG. 33 is an example embodiment of a user interface displaying machinery and equipment appraisal information for an account in a RMCS.  
         [0042]    [0042]FIG. 34 is an example embodiment of a user interface displaying real estate appraisal information for an account in a RMCS.  
         [0043]    [0043]FIG. 35 is an example embodiment of a user interface displaying audits information for an account in a RMCS.  
         [0044]    [0044]FIG. 36 is an example embodiment of a user interface displaying miscellaneous collateral information for an account in a RMCS.  
         [0045]    [0045]FIG. 37 is an example embodiment of a user interface displaying capital structure and CF Business Exposure for an account in a RMCS.  
         [0046]    [0046]FIG. 38 is an example embodiment of a user interface displaying financial covenants information for an account in a RMCS.  
         [0047]    [0047]FIGS. 39A through 39C display an example embodiment of a user interface displaying financial statements information for an account in a RMCS.  
         [0048]    [0048]FIG. 40 is an example embodiment of a user interface displaying a financial performance summary for an account in a RMCS.  
         [0049]    [0049]FIGS. 41A and 41B show an example embodiment of a user interface displaying an account retention plan for an account in a RMCS.  
         [0050]    [0050]FIG. 42 is an example embodiment of a user interface displaying buy, sell, hold recommendations for an account in a RMCS.  
         [0051]    [0051]FIG. 43 is an example embodiment of a user interface displaying investment trading statistics information for an account in a RMCS.  
         [0052]    [0052]FIGS. 44A and 44B display an example embodiment of a user interface displaying a cash flow loan analysis for an account in a RMCS.  
         [0053]    [0053]FIGS. 45A and 45B show an example embodiment of a user interface displaying liquidation value information for an account in a RMCS.  
         [0054]    [0054]FIG. 46 is an example embodiment of a user interface displaying a watchlist strategy for an account in a RMCS.  
         [0055]    [0055]FIG. 47 is an example embodiment of a user interface displaying an amortization schedule for an account in a RMCS.  
         [0056]    [0056]FIG. 48 is another example embodiment of a user interface displaying fee structure information for an account in a RMCS.  
         [0057]    [0057]FIG. 49 is an example embodiment of a user interface displaying capital raising history information for an account in a RMCS.  
         [0058]    [0058]FIG. 50 is an example embodiment of a user interface displaying key milestones and number of months of cash remaining for an account in a RMCS.  
         [0059]    [0059]FIG. 51 is an example embodiment of a user interface displaying equity valuation and exit strategy for an account in a RMCS.  
         [0060]    [0060]FIG. 52 is an example embodiment of a user interface displaying CF Business share of other equity instruments information for an account in a RMCS.  
         [0061]    [0061]FIG. 53 is an example embodiment of a user interface displaying background commentary information for an account in a RMCS.  
         [0062]    [0062]FIG. 54 is an example embodiment of a user interface displaying recent events and loan activity for an account in a RMCS.  
         [0063]    [0063]FIG. 55 is an example embodiment of a user interface displaying risk ratings for an account in a RMCS.  
         [0064]    [0064]FIG. 56 is an example embodiment of a user interface displaying deal team information for an account in a RMCS.  
         [0065]    [0065]FIG. 57 is an example embodiment of a user interface displaying alerts for accounts in a RMCS.  
         [0066]    [0066]FIG. 58, is an example embodiment of a user interface displaying general setup information for an account in a RMCS.  
         [0067]    [0067]FIG. 59 is an example embodiment of a user interface displaying capital structure setup information for an account in a RMCS.  
         [0068]    [0068]FIG. 60 is an example embodiment of a user interface displaying collateral setup information for an account in a RMCS.  
         [0069]    [0069]FIG. 61 is an example embodiment of a user interface displaying covenant setup information for an account in a RMCS.  
         [0070]    [0070]FIG. 62 is an example embodiment of a user interface displaying equity setup information and CF Business activity and history for an account in a RMCS.  
         [0071]    [0071]FIG. 63 is an example embodiment of a user interface displaying a portfolio home page in a RMCS.  
         [0072]    [0072]FIG. 64 is an example embodiment of a user interface displaying availability information for a portfolio in a RMCS.  
         [0073]    [0073]FIG. 65 is an example embodiment of a user interface displaying availability trends for a portfolio in a RMCS.  
         [0074]    [0074]FIG. 66 is an example embodiment of a user interface displaying buy, sell, hold reporting for a portfolio in a RMCS.  
         [0075]    [0075]FIG. 67 is an example embodiment of a user interface displaying customer map/unmap details for a portfolio in a RMCS.  
         [0076]    [0076]FIG. 68 is an example embodiment of a user interface displaying deal team setup information for an account in a RMCS.  
         [0077]    [0077]FIG. 69 is an example embodiment of a user interface displaying industry concentration trends for a portfolio in a RMCS.  
         [0078]    [0078]FIG. 70 is an example embodiment of a user interface displaying a comparison of industry concentration trends at different times for a portfolio in a RMCS.  
         [0079]    [0079]FIG. 71 is an example embodiment of a user interface displaying loan coverage information for a portfolio in a RMCS.  
         [0080]    [0080]FIG. 72 is an example embodiment of a user interface displaying near term deal maturities for a portfolio in a RMCS.  
         [0081]    [0081]FIG. 73 is an example embodiment of a user interface displaying frequently viewed control reports within a portfolio in a RMCS.  
         [0082]    [0082]FIG. 74 is an example embodiment of a user interface displaying risk classification for a portfolio in a RMCS.  
         [0083]    [0083]FIG. 75 is an example embodiment of a user interface displaying risk classification for a portfolio in a RMCS.  
         [0084]    [0084]FIG. 76 is an example embodiment of a user interface displaying alert details for a portfolio in a RMCS.  
         [0085]    [0085]FIG. 77 is an example embodiment of a user interface displaying alerts by account for a portfolio in a RMCS.  
         [0086]    [0086]FIG. 78 is an example embodiment of a user interface displaying alerts by type for a portfolio in a RMCS.  
         [0087]    [0087]FIG. 79 is an example embodiment of a user interface displaying an administrative home page in a RMCS.  
         [0088]    [0088]FIG. 80 is an example embodiment of a user interface displaying a tools home page in a RMCS.  
         [0089]    [0089]FIG. 81 is an example embodiment of a user interface displaying a communication home page in a RMCS.  
         [0090]    [0090]FIG. 82 is an example embodiment of a user interface displaying a help home page in a RMCS.  
         [0091]    [0091]FIG. 83 is an example embodiment of a user interface displaying a covenant summary report page in a RMCS. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0092]    Example embodiments of systems and processes that facilitate integrated network-based electronic reporting and workflow process management related to a Risk Management Coordination System (RMCS) are described below in detail. A technical effect of the systems and processes described herein include at least one of facilitating an electronic submission of information using a client system, automating extraction of information, and web-based reporting for internal and external system users. The RMCS allows a business engaging in complex deals, such as commercial financing, mergers, acquisitions and real estate transactions, to collect, manage, store and disseminate risk management (RM) information among internal deal teams and selected outside deal teams to facilitate a more accurate and efficient analysis of the risks associated with a deal and to facilitate management of workload and personnel. The RMCS also allows a business engaging in complex deals to manage customer relationships, manage specific legal information, manage and create an electronic deal file, manage and create an electronic account manager journal, train personnel, and provide predictive measures based on history, industry trends and economic data.  
         [0093]    In the example embodiment, the RMCS collects, tracks, displays, and disseminates real time Risk Management (RM) information, which is information relating to a business entity being analyzed (“Analyzed Business”) by another business engaging in complex deals, such as commercial financing, mergers, acquisitions and real estate transactions (“Commercial Finance Business” or “CF Business”). RM information includes at least one of business information, accounts payable, accounts receivable, covenant compliance, financial statements, capital structure, income statements, inventory, leverage, loan profile, collateral, guarantors, machinery and equipment, real estate, liquidation value, and other documents and information relating to the financial condition of the Analyzed Business.  
         [0094]    The RMCS enables the CF Business to input RM information on a single occasion and into a single computer workstation that may be located at various locations. In addition, the RMCS permits the various internal deal teams within the CF Business to share RM information when conducting a due diligence analysis and to continue account management on the Analyzed Business. The RMCS also enables the CF Business to provide RM information to outside deal teams, like outside legal counsel, during the due diligence analysis. The RMCS also enables a user to monitor a plurality of accounts included in a portfolio, and monitor a plurality of portfolios. Additionally, the RMCS enables a deal team leader to manage a workload of an account manager as well as enabling a senior risk officer to manage a workload of team leaders. The RMCS further permits the CF Business to devote more time to analyzing RM information and conducting a due diligence analysis, and less time entering, checking and reporting data.  
         [0095]    RM information relating to the Analyzed Business is received by the RMCS which stores the RM information in a database, updates the database with RM information received, tracks, the RM information received, provides RM information in response to an inquiry, allows selected outside deal teams to review and comment on RM information, and provides a report to at least one managerial user within the CF Business summarizing the review of RM information for an Analyzed Business.  
         [0096]    In the RMCS, RM information is stored in the database. The network based RMCS provides convenient access to RM information, including at least one of business information, accounts payable, accounts receivable, availability analysis, covenant compliance, coverage ratios, financial statements, financial statement and availability projections, capital structure, income statements, inventory, leverage, loan profile, collateral, guarantors, machinery and equipment, real estate, liquidation value, amortization, capital raising history, equity valuation, and other documents and information relating to the financial condition of the Analyzed Business. A user must be authorized to gain access into the RMCS. In the example embodiment, once the RMCS home page is accessed, the user will be able to choose from a list of Analyzed Businesses, also known as accounts, for which the user is responsible, is listed on the deal team, or has been granted access by other users. Once the user selects the account to be reviewed, the user can review RM information relating to the Analyzed Business associated with that account. In an example embodiment, only an authorized user can access the RM information. In addition, the example embodiment enables a user to monitor and view RM information for a plurality of accounts which comprise a portfolio.  
         [0097]    In one embodiment, the system is a computer program embodied on a computer readable medium implemented utilizing Java® and Structured Query Language (SQL) with a client user interface front-end for administration and a web interface for standard user input and reports. (Java is a registered trademark of Sun Microsystems, Inc., Palo Alto, Calif.). In an example embodiment, the system is web enabled and is run on a business-entity&#39;s intranet. In yet another embodiment, the system is fully accessed by individuals having an authorized access outside the firewall of the business-entity through the Internet. In a further example embodiment, the system is being run in a Windows® NT environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Wash.). The application is flexible and designed to run in various different environments without compromising any major functionality.  
         [0098]    The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process also can be used in combination with other assembly packages and processes.  
         [0099]    [0099]FIG. 1 is a simplified block diagram of a Risk Management Coordination System (RMCS)  10  including a server system  12 , and a plurality of client sub-systems, also referred to as client systems  14 , connected to server system  12 . In one embodiment, client systems  14  are computers including a web browser, such that server system  12  is accessible to client systems  14  via the Internet. Client systems  14  are interconnected to the Internet through many interfaces including a network, such as a local area network (LAN) or a wide area network (WAN), dial-in-connections, cable modems and special high-speed ISDN lines. Client systems  14  could be any device capable of interconnecting to the Internet including a web-based phone, personal digital assistant (PDA), or other web-based connectable equipment. A database server  16  is connected to a database  20  containing information on a variety of matters, as described below in greater detail. In one embodiment, centralized database  20  is stored on server system  12  and can be accessed by potential users at one of client systems  14  by logging onto server system  12  through one of client systems  14 . In an alternative embodiment database  20  is stored remotely from server system  12  and may be non-centralized.  
         [0100]    [0100]FIG. 2 is an expanded version block diagram of an example embodiment of a server architecture of a RMCS  22 . Components in system  22 , identical to components of system  10  (shown in FIG. 1), are identified in FIG. 2 using the same reference numerals as used in FIG. 1. System  22  includes server system  12  and client systems  14 . Server system  12  further includes database server  16 , an application server  24 , a web server  26 , a fax server  28 , a directory server  30 , and a mail server  32 . A disk storage unit  34  is coupled to database server  16  and directory server  30 . Servers  16 ,  24 ,  26 ,  28 ,  30 , and  32  are coupled in a local area network (LAN)  36 . In addition, a system administrator&#39;s workstation  38 , a user workstation  40 , and a supervisor&#39;s workstation  42  are coupled to LAN  36 . Alternatively, workstations  38 ,  40 , and  42  are coupled to LAN  36  via an Internet link or are connected through an Intranet.  
         [0101]    Each workstation,  38 ,  40 , and  42  is a personal computer having a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations  38 ,  40 , and  42 , such functions can be performed at one of many personal computers coupled to LAN  36 . Workstations  38 ,  40 , and  42  are illustrated as being associated with separate functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to LAN  36 . In an example embodiment, client system  14  includes workstation  40  which can be used by an internal deal team user or a designated outside deal team user to review RM information relating to an Analyzed Business.  
         [0102]    Server system  12  is configured to be communicatively coupled to various individuals, including employees  44  and to third parties, e.g., designated outside deal team users,  46  via an ISP Internet connection  48 . The communication in the example embodiment is illustrated as being performed via the Internet, however, any other wide area network (WAN) type communication can be utilized in other embodiments, i.e., the systems and processes are not limited to being practiced via the Internet. In addition, and rather than WAN  50 , local area network  36  could be used in place of WAN  50 .  
         [0103]    In the example embodiment, any authorized individual having a workstation  54  can access RMCS  22 . At least one of the client systems includes a manager workstation  56  located at a remote location. Workstations  54  and  56  are personal computers having a web browser. Also, workstations  54  and  56  are configured to communicate with server system  12 . Furthermore, fax server  28  communicates with remotely located client systems, including a client system  56  via a telephone link. Fax server  28  is configured to communicate with other client systems  38 ,  40 , and  42  as well.  
         [0104]    [0104]FIG. 3 shows a configuration of database  20  within database server  16  of server system  12  shown in FIG. 1. Database  20  is coupled to several separate computer software components within server system  12 , which perform specific tasks. In the example embodiment, server system  12  includes a collection component  64  for collecting data from users in database  20 , a tracking component  66  for tracking data, and a displaying component  68  to display information. Tracking component  66  tracks and cross-references data, including modifying existing data.  
         [0105]    Server system  12  also includes a receiving component  70  to receive a specific query from client system  14 , and an accessing component  72  to access database  20  within data storage device  34 . Receiving component  70  is programmed to receive a query from one of a plurality of users. Server system  12  further includes a processing component  76  for searching and processing received queries against database  20  containing a variety of information collected by collection component  64 . An information fulfillment component  78  located in server system  12  enables the requested information to be downloaded to the plurality of users in response to the requests received by receiving component  70 . Information fulfillment component  78  downloads the information after the information is retrieved from database  20  by a retrieving component  80 . Retrieving component  80  retrieves, downloads and sends information to client system  14  based on a query received from client system  14 .  
         [0106]    Retrieving component  80  also includes a display component  84  that is configured to download information to be displayed on a client system&#39;s graphical user interface, and a printing component  86  that is configured to print information. Retrieving component  80  generates reports requested by the user through client system  14  in a pre-determined format. System  10  is flexible to provide other alternative types of reports and is not constrained to the options set forth above.  
         [0107]    Server system  12  also includes a notifying component  88  and a providing component  90 . Notifying component  88  electronically transmits a message to client system  14  based on information inputted into server system  12 , notifying a user of the status of the review of RM information by the deal team. Providing component  90  electronically provides a report to manager workstation  56  (shown in FIG. 2) summarizing the review of the RM information by the deal team, including the deal team&#39;s findings and recommendations relating to whether the CF Business should take risk mitigation action with respect to the deal, and, if so, what type of action is recommended.  
         [0108]    In one embodiment, collection component  64 , tracking component  66 , displaying component  68 , receiving component  70 , processing component  76 , information fulfillment component  78 , retrieving component  80 , display component  84 , printing component  86 , notifying component  88 , and providing component  90  are computer programs embodied on computer readable medium.  
         [0109]    Database  20  is divided into an Accounts Section  92 , a Portfolio Section  94 , an Admin Section  96 , a Tools Section  98 , a Communication Section  100 , a Help Section  102 , and a Logoff Section  104 . Accounts Section  92  illustrates RM information  106  for each individual account, which are also known as the Analyzed Businesses, within RMCS  10  (shown in FIG. 1). To facilitate searching, Accounts Section  92  is sub-divided into a Home Section  108 , an Analysis Section  110 , a Reporting Section  112 , a Data Section  114 , an Alerts Section  116 , a Setup Section  118 , and a Customer Preview Section  120 .  
         [0110]    RM information  106  includes at least one of the following for each Analyzed Business: business information  122 , accounts payable  124 , accounts receivable  126 , availability analysis  128 , covenant compliance  130 , coverage ratios  132 , financial statements  134 , financial statement and availability projections  135 , a capital structure  136 , income statements  138 , an inventory  140 , leverage  142 , a loan profile  144 , collateral  146 , guarantors  148 , machinery and equipment  150 , real estate  152 , a liquidation value  154 , amortization  156 , a capital raising history  158 , an equity valuation  160 , and other documents and information  162  relating to the financial condition of the Analyzed Business&#39;.  
         [0111]    Portfolio Section  94  illustrates RM information  106  on an aggregate basis for a plurality of accounts (or Analyzed Businesses) within a portfolio and inputted in RMCS  10 . To facilitate searching, Portfolio Section  94  is sub-divided into a Home Section  164 , an Analysis Section  166 , a Reporting Section  168 , and an Alerts Section  170 .  
         [0112]    Admin Section  96  enables the user to access RM information  106 , and delegate accounts to various other users, including internal deal team users and outside deal team users.  
         [0113]    Tools Section  98  enables the user to access RM information  106  and provides a user with links to other commercial finance resources.  
         [0114]    Communication Section  100  enables the user to access RM information  106  and provides useful links to historical and current communications (e.g., e-mails, correspondence, memos, etc.) from users within the CF Business.  
         [0115]    Help Section  102  displays additional information links relating to RMCS  10  (shown in FIG. 1). In the example embodiment, Help Section  102  includes a user guide link, a glossary of defined terms link, a frequently asked questions link, a quick reference card link, and a feedback link.  
         [0116]    Logoff Section  104  permits a user to logoff of RMCS  10  (shown in FIG. 1).  
         [0117]    System  10  accumulates a variety of confidential data and has different access levels to control and monitor the security of and access to system  10 . Authorization for access is assigned by system administrators on a need to know basis. In one embodiment, access is provided based on job functions. In yet another embodiment, system  10  provides access based on business-entity. The administration/editing capabilities within system  10  are also restricted to ensure that only authorized individuals have access to modify or edit the data existing in the system. System  10  manages and controls access to system data and information.  
         [0118]    The architectures of system  10  as well as various components of system  10  are exemplary only. Other architectures are possible and can be utilized in connection with practicing the processes described below.  
         [0119]    [0119]FIG. 4 is a flowchart  200  illustrating example processes utilized by system  10 . The technical effect of RMCS  10  is achieved by a user first accessing  210  a user interface, such as a home page  220 , of the web site through client system  14  (shown in FIG. 1). In one embodiment, client system  14 , as well as server system  12 , are protected from access by unauthorized individuals. The user logs-in  230  to system  10  using a password (not shown) and an employee user login for security. The technical effect is further achieved through client system  14 , which is configured to receive  232  an electronic notice indicating that a review of RM information  106  (shown in FIG. 3) has occurred, and whether any comments or findings were made relating to the review.  
         [0120]    Client system  14  also displays  240  options available to the user through links, check boxes, or pull-down lists. Once the user selects  244  an option (in one embodiment, relating to a facility within the business entity) from the available links, the request is transmitted  248  to server system  12 . Transmitting  248  the request is accomplished, in one embodiment, either by click of a mouse or by a voice command. Once server system  12  (shown in FIG. 1) receives  252  the request, server system  12  accesses  256  database  20  (shown in FIG. 1). System  10  determines  260  if additional. narrowing options are available. In one embodiment, additional narrowing options relate to at least one of the Analyzed Business and RM information  106 , and include check boxes, hyperlinks, buttons, and pull-down lists. If additional narrowing options are available  264 , system  10  displays  240  the options relating to the prior option selected by the user on client system  14 . The user selects  244  the desired option and transmits the request  248 . Server system  12  receives the request  252  and accesses  256  database  20 . When system  10  determines that additional options  260  are not available  268 , system  10  retrieves  272  requested information from database  20 . The requested information is downloaded  276  and provided  280  to client system  14  from server  12 . Client system  14  transmits a report  282  from a user to manager workstation  56  (shown in FIG. 2) summarizing the review of RM information  106  by a deal team, including the deal team&#39;s comments and findings. The user can continue to search  284  database  20  for other information or exit  290  from system  10 .  
         [0121]    [0121]FIG. 5 is an example embodiment of a user interface  300  displaying a login page of RMCS  10  (shown in FIG. 1). User interface  300  illustrates a User Name field  302  and a Password field  304 . All users must have a user name and password to log-on to RMCS  10 . In an example embodiment, user interface  300  also shows an “Enter” button  306 , which the user must select after entering an appropriate user name in User Name field  302  and password in Password field  304 . Although buttons are shown in the example embodiment, pull-down lists, check boxes, and other means for inputting this information could also be used. User interface  300  is the entry point for anyone trying to access RMCS  10  and database  20  (shown in FIG. 1) via the web. After entering the requested information and selecting Submit button  306 , the user enters RMCS  10 .  
         [0122]    User interface  300  also displays hyperlinks Forgot Password  308 , Modify Account  310 , and Not Registered  312 . By selecting Forgot Password  308  hyperlink, a screen is displayed prompting the user to input information. By inputting the requested information, RMCS  10  provides the user with their assigned password. Similarly, by selecting Modify Account  310  hyperlink, a user is prompted by a screen to input information that will change the user&#39;s current password.  
         [0123]    [0123]FIG. 6 is an example embodiment of a user interface  320  displaying a home page of RMCS  10  (shown in FIG. 1), which is displayed after a user has logged onto RMCS  10 . User interface  320  displays a summary of RM information  106  (shown in FIG. 3) for all accounts  322 , or Analyzed Businesses, for which the user is responsible, is listed on a deal team, or has been assigned to by other users. In an example embodiment, user interface  320  illustrates a plurality of menu tabs including at least one of Accounts  324 , Portfolio  326 , Admin  328 , Tools  330 , Communication  332 , Help  334 , and Logoff  336 . Although tabs are shown in the example embodiment, pull-down lists, check boxes, and other means for inputting this information could also be used. These menu tabs enable the user to navigate RMCS  10 .  
         [0124]    In the example embodiment, user interface  320  also displays sub-menu tabs located below the menu tabs. The sub-menu tabs include at least one of Home  338 , Analysis  340 , Reporting  342 , Data  344 , Alerts  346 , Setup  348 , and Customer Preview  350 . The sub-menu tabs further enable the user to navigate RMCS  10 . In the example embodiment, user interface  320  is displayed when Accounts  324  and Home  338  are selected or upon logging into the system.  
         [0125]    When menu tab Accounts  324  and sub-menu tab Home  338  are selected, user interface  320  displays a summary of RM information  106  in tabular form for each accounts  322  for which the user is responsible, is listed on a deal team, or has been assigned to by other users. In the example embodiment, the table includes at least the following column headers: Account Name  352 , Alerts  354 , Risk Class  356 , Commercial Finance (CF)-Commitment  358 , CF Outstandings (CF O/S)  360 , $ Excess Avail  362 , % Excess Avail  364 , Fixed Charge Coverage Over The Last Twelve Months (FCC LTM)  366 , Cash Burn LTM  368 , Sr. Debt  370 , Tot. Debt  372 , KMV  374 , Last Audit  376 , SIC  378 , and Account Manager (AM)  380 . KMV is a third party credit valuation tool. SIC is a code that identifies an industry that the business operates within. An Account Manager is a person within the CF Business that manages the account and underwrites the original transaction. In the example embodiment, each column is sortable by ascending or descending order. Additionally, each column header is a link, when selected, displays another screen that provides additional information relating to the selected column header.  
         [0126]    FCC LTM  366  and Cash Burn LTM  368  also include pull-down boxes that may be selected by the user. In the example embodiment, the options included in these pull-down boxes are LTM (shown in FIG. 6), L 9 M (Last Nine Months), L 6 M (Last Six Months), L 3 M (Last Three Months), and L 1 M (Last One Month).  
         [0127]    [0127]FIG. 7 is an example embodiment of a user interface  400  displaying account payable trends for selected account  322  (shown in FIG. 6), which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects AP Trends within a navigation bar  401  located along the left side of user interface  400 .  
         [0128]    In the example embodiment, navigation bar  401  can be hidden to provide a larger screen view by clicking an “X” in the upper right hand corner of navigation bar  401 . Once navigation bar  401  is hidden, a user can unhide navigation bar  401  by clicking on a Show Menu icon located below and to the left of Account tab  324 . Navigation bar  401  may be displayed or hidden on most user interfaces included within RMCS  10  (shown in FIG. 1). For exemplary purposes, navigation bar  401  is shown both displayed and hidden in the user interfaces included within the present patent application.  
         [0129]    User interface  400  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  400  illustrates an account field  402  showing selected account  322  or the Analyzed Business. User interface  400  also illustrates Accounts Payable (AP) Trends field  404 , a Frequency field  406 , e.g., monthly, quarterly, and annual, a From date field  408 , a To date field  410 , and a Go button  412 .  
         [0130]    In the example embodiment, the graphs displayed on user interface  400  are displayed automatically using RM information  106  which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when dates are inputted into From date field  408  and To date field  410 , a Frequency  406  is selected, and Go button  412  is selected. Additionally, once the graphs are generated, a user can (i) click on a View Full Screen button to enlarge the corresponding graph to occupy the full screen, or (ii) click on a Show Data Table button to view the actual tabular data that is used to generate the specific graph. To change the display, the user selects different time intervals and/or dates. The graphs may include at least one of Accounts Payable and Accrued Liabilities  414 , Net Working Capital  416 , and Accounts Payable to Inventory  418 .  
         [0131]    [0131]FIG. 8 is an example embodiment of a user interface  440  displaying account receivable trends for selected account  322  (shown in FIG. 6), which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects AR Trends within navigation bar  401 . User interface  440  displays at least one of graphical and tabular analyses of selected account  322  for a selected period of time. In the example embodiment, user interface  440  displays an Accounts Receivable (AR) Components pull-down list  442 , a Frequency pull-down list  444 , a Number of Periods pull-down list  446 , and a Go button  448 .  
         [0132]    In the example embodiment, the graphs displayed on user interface  440  are displayed automatically using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user after the time period is inputted by the user. Additionally, once the graphs are generated, a user can (i) click on a View Full Screen button to enlarge the corresponding graph to occupy the full screen, or (ii) click on a Show Data Table button to view the actual tabular data that is used to generate the specific graph. The graphs are then shown over a monthly, quarterly, annually frequency based on what is inputted into Frequency field  444 . The graphs are generated after Go button  448  is selected. To change the display, the user selects different time intervals and/or dates. The graphs may include at least one of A/R Availability Trends  450 , A/R Turnover  452 , and Sales Dilution  454 .  
         [0133]    [0133]FIG. 9 is an example embodiment of a user interface  480  displaying an availability analysis for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Availability Trends within navigation bar  401 . User interface  480  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  480  illustrates an account field  482  showing selected account  322  or the Analyzed Business. User interface  480  also displays an Analysis Period field  484 , a To date field  486 , a From date field  488 , and a Go button  490 . In the example embodiment, Analysis Period field  484  includes 15 days, 30 days, 45 days, 60 days, and 90 days.  
         [0134]    In the example embodiment, the graphs illustrated on user interface  480  are displayed automatically using RM information  106  (shown in FIG. 3) stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when dates are inputted into To date field  486  and From date field  488 , an Analysis Period  484  is selected, and Go button  490  is selected. To change the display, the user selects different time intervals and/or dates, and selects Go button  490 . The graphs may include at least one of a Daily Excess Availability Chart  492 , a Monthly Excess Availability Chart  493 , an Effective Advance Rate Chart  494 , and an Availability Composition Chart  496 . Each graph also provides a View Full Screen button  498  which enables the user to enlarge the corresponding graph, and a Show Data Table button  500  which enables the user to display the data table that corresponds to that particular graph.  
         [0135]    [0135]FIG. 10 is an example embodiment of a user interface  520  displaying covenant compliance for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Covenant Compliance within navigation bar  401 . User interface  520  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  520  displays an Account field  522  showing selected account  322 , which is also known as the Analyzed Business. User interface  520  also includes a From date field  524 , a To date field  526 , and a Go button  528 .  
         [0136]    In the example embodiment, the graphs displayed on user interface  520  display financial covenant compliance for account  322  or the Analyzed Business. The graphs are automatically displayed using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when dates are inputted into From date field  524  and To date field  526 , and Go button  528  is selected. To change the display, the user selects different dates, and selects Go button  528 . In the example embodiment, the graphs displayed on user interface  520  may include at least one of Net Worth  530 , Non-Financed Capex  532 , and FCC  534 . Each graph displayed on user interface  520  also includes a View Full Screen button  536 , and a Show Data Table button  538 . Additionally, user interface  520  displays a reduced Data Table  540  that corresponds with at least one of the displayed graphs. When a user selects reduced Data Table  540 , a full screen data table is displayed.  
         [0137]    [0137]FIG. 11 is an example embodiment of a user interface  560  displaying coverage ratios for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Coverage Ratios within navigation bar  401 . User interface  560  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  560  includes an Account Name field  562  showing selected account  322 , which is also known as the Analyzed Business. User interface  560  also illustrates a Ratio &amp; Basis for Ratio data scroll field  564 , a Financials pull-down field  566 , a Based on pull-down field  570 , a Beginning Date field  574 , an Ending Date field  576 , and a Go button  578 .  
         [0138]    In the example embodiment, the graphs illustrated on user interface  560  are displayed automatically using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when data is inputted into Ratio &amp; Basis for Ratio data scroll field  564 , Financials pull-down field  566 , Based on pull-down field  570 , Beginning Date field  574 , Ending Date field  576 , and Go button  578  is selected. To change the display, the user inputs different data into the various fields and selects Go button  578 . In the example embodiment, the user can select from at least one of the following ratios: Operating Cash Flow (OCF)/Total Interest  580 , OCF/Senior Cash Interest  582 , OCF/Senior Cash Interest (Maintenance Capex)  584 , and OCF/Senior Cash Interest (Non-Financed Capex)  586 . Capex is defined as Capital Expenditures. EBITDA, which is shown in Based on pull-down field  570 , is defined as Earnings Before Interest, Taxes, Depreciation, and Amortization. Each graph displayed on user interface  560  also includes a View Full Screen button  588 , and a Show Data Table button  590 .  
         [0139]    [0139]FIG. 12 is an example embodiment of a user interface  600  displaying financial statement trends for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Income Statement Trends within navigation bar  401 . User interface  600  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  600  displays an Account Name field  602  showing selected account  322 , also known as the Analyzed Business. User interface  600  also illustrates a Frequency field  606 , e.g., monthly, quarterly, and annual, a From date field  608 , a To date field  610 , and a Go button  612 .  
         [0140]    In the example embodiment, the graphs illustrated on user interface  600  display an income statement performance for account  322 . The graphs are automatically displayed on user interface  600  using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when data is inputted into Frequency field  606 , From date field  608 , To date field  610 , and Go button  612  is selected. To change the display, the user inputs different data into the various fields and selects Go button  612 . In the example embodiment, the graphs that may be generated by the user and displayed on user interface  600  include at least one of Revenues  614 , Earnings Before Interest, Taxes, Depreciation and Amortization (EBITDA)  616 , Gross Margin Trend  618 , and EBITDA Margin Trend  620 . Each graph displayed on user interface  600  also includes a View Full Screen button  622 , and a Show Data Table button  624 .  
         [0141]    [0141]FIG. 13 is an example embodiment of a user interface  640  displaying inventory trends for selected account  322  (shown in FIG. 6), which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Inventory Trends within navigation bar  401  (not shown in FIG. 13). User interface  640  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  640  displays an ABLE ID pull-down field  641 , an Inventory Component pull-down field  642 , a Frequency pull-down field  644 , e.g., monthly, quarterly, and annual, a # of Periods pull-down field  646 , and a Go button  648 .  
         [0142]    ABLE is a known and commercially available software program manufactured by Computer and Software Enterprises, Inc., San Luis Obispo, Calif. ABLE stands for Asset Based Lending Environment (“ABLE”) and is a collateral and accounting subledger system. Although ABLE is shown in the example embodiment, RMCS  10  does not require ABLE as it sub-ledger system. Rather, RMCS  10  can utilize and interface with a plurality of known and commercially available sub-ledger systems. Another example of a known and commercially available sub-ledger system that can interface with RMCS  10  includes AE Business Solutions, Madison, Wisconsin. For convenience purposes, the example embodiment discussed herein will include the ABLE sub-ledger system.  
         [0143]    In the example embodiment, the graphs illustrated on user interface  640  display inventory trends for account  322 , also known as the Analyzed Business. The graphs are automatically displayed on user interface  640  using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when data is inputted into ABLE ID pull-down field  641 , Inventory Component pull-down field  642 , Frequency pull-down field  644 , # of periods pull-down field  646 , and Go button  648  is selected. To change the display, the user inputs different data into the various fields and selects Go button  648 . In the example embodiment, the graphs that may be generated by the user and displayed on user interface  640  include at least one of Inventory Availability Trend  650 , and Inventory Balance and Turnover  652 . Each graph displayed on user interface  640  also includes a View Full Screen button  654 , and a Show Data Table button  656 .  
         [0144]    [0144]FIG. 14 is an example embodiment of a user interface  660  displaying total leverage and senior leverage over time for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Leverage Trends within navigation bar  401 . User interface  660  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  660  displays an Account Name field  662  showing selected account  322 , also known as the Analyzed Business. User interface  660  also displays a Frequency pull-down field  668 , e.g., monthly, quarterly, and annual, a From date field  670 , and a To date field  672 .  
         [0145]    In the example embodiment, the graphs illustrated on user interface  660  display total leverage and senior leverage over time for account  322 . The graphs are automatically displayed on user interface  660  using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when data is inputted into Frequency pull-down field  668 , From date field  670 , and To date field  672 . To change the display, the user inputs different data into the various fields. In the example embodiment, the graphs that may be generated by the user and displayed on user interface  660  include at least one of Total Debt to EBITDA  674 , and Senior Debt to EBITDA  676 .  
         [0146]    [0146]FIG. 15 is an example embodiment of a user interface  700  displaying risk measures such as KMV, S&amp;P, Moody&#39;s, and other measures utilized by the business entity to classify risk including at least one of Risk Classification, Risk+, and GlobalNet, over time for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Analysis  340  are selected by a user or after the user selects Risk Measures within navigation bar  401 . KMV is a risk rating system that provides a default rate indicator on a business entity. S&amp;P is a Standard &amp; Poors risk rating system. Moody&#39;s and Risk+ are also risk rating systems. GlobalNet is a tool used to track and aggregate the CF Business&#39; entire exposure by both business and product as they relate to the specific deal. User interface  700  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  700  displays an Account Name field  702  showing selected account  322 , also known as the Analyzed Business. User interface  700  also displays a Frequency pull-down field  708 , e.g., monthly, quarterly, and annual, a From date field  710 , a To date field  712 , and a Go button  713 .  
         [0147]    In the example embodiment, the graphs illustrated on user interface  700  display risk measures over time for account  322 . The graphs are automatically displayed on user interface  700  using RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The graphs are generated by the user when data is inputted into Frequency field  708 , From date field  710 , To date field  712 , and Go button  713  is selected. To change the display, the user inputs different data into the various fields. In the example embodiment, the graphs that may be generated by the user and displayed on user interface  700  include at least one of KMV/S&amp;P  714 , Risk Classification  716 , Risk+  718 , GlobalNet  720 , and Stock Price  722 . Each graph displayed on user interface  700  also includes a View Full Screen button  724 , and a Show Data Table button  726 .  
         [0148]    [0148]FIGS. 16A through 16C display an example embodiment of a user interface  740  displaying account specific reports referred to as Portfolio Management Reports (PMR) for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Reporting  342  are selected by a user. User interface  740  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  740  may display for selected account  322  a summary of current loan balances, an amount of collateral, a resulting availability of credit, an effective advance rate, letters of credit, and other information relating to credit. User interface  740  may also display for selected account  322  a summary of loan balances, a monthly trend of changes in collateral balances, and an amount of collateral availability.  
         [0149]    User interface  740  displays an account specific report used by management within the CF Business to monitor each account  322 , also known as the Analyzed Business. User interface  740  displays a report based on RM information  106  (shown in FIG. 3) which is stored in RMCS  10  (shown in FIG. 1). The standard report includes at least one of asset-based accounts, cash-flow accounts, equity accounts, Bank Loan Group (BLG) accounts, and WatchList account.  
         [0150]    In the example embodiment, user interface  740  displays an Account Name pull-down field  742  showing selected account  322 . User interface  740  also displays a Summary Information Section, a Background Section, a Recent Events and Loan Activities Section, a Guarantors/Security Section, a Capital Structure Section, a Fee Structure Section, a Financial Performance Section, a Balance Sheet Section, a Financial Commentary Section, a Borrowing Base Section, a Covenants Section, a Collateral Information Section, a Trading Statistics Section, and a Liquidation Value Section. User interface  740  also displays an As of Date data field  744 , a Report Date label  748 , a Risk Classification field  750 , a Go button  752 , a Top button  754 , a Bottom button  755 , a Background button  756 , a Capital Structure button  758 , a Financials button  760 , a Covenants button  761 , a Collateral button  762 , and a Trading Statistics button  764 .  
         [0151]    User interface  740  also displays a History of Entries link  768 , which enables a user to identify when a financial record was last saved within RMCS  10 . After a user selects History of Entries link  768 , a calendar is displayed (not shown in FIG. 16) that highlights the last time a specific financial record was saved within RMCS  10 .  
         [0152]    [0152]FIG. 17 is an example embodiment of a user interface  780  displaying collateral availability for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. The data may be viewed by the user through Data Section  344  and the Setup Section  348  of RMCS  10  (shown in FIG. 1). The navigation bar located along the left side of user interface  780  is shown hidden in FIG. 17. In the example embodiment, Data Section  344  is divided into a plurality of categories including at least one of Collateral, Financial Statements and Capital Structure, Strategy, Deal Structure, Equity, Company, and Contacts, which are displayed within the navigation bar. User interface  780  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  780  displays for selected account  322  a summary of collateral data such as availability, appraisals, agings, and concentrations. User interface  780  may also illustrate for selected account  322  a summary of collateral data broken down into categories including Secured  782 , Unsecured  784 , and Combined  786 .  
         [0153]    In the example embodiment, user interface  780  displays an Account Name field  788  showing selected account  322 , also known as the Analyzed Business. User interface  780  also displays an ABLE ID pull-down field  790 , a currency pull-down field  792 , a Date field  794 , a Go button  796 , and a Save button  798 . In the example embodiment, ABLE ID pull-down field  790  displays those subaccounts that are linked to the selected account  322 . User interface  780  also displays a History of Entries link  799 , which enables a user to identify when a financial record was last saved within RMCS  10 .  
         [0154]    [0154]FIG. 18 is an example embodiment of a user interface  820  displaying collateral security and guarantors information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Collateral Overview &amp; Guarantors from a navigation bar (not shown) located on the left side of user interface  820 . The data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  820  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  820  displays for selected account  322  a summary of collateral security and guarantors. User interface  820  may also display for selected account  322  a summary of security  822 , security details,  824 , description of collateral  826 , description of boot collateral  828 , and guarantors  830 . In the example embodiment, user interface  820  displays an Account Name field  832  showing selected account  322 , which is also known as the Analyzed Business. User interface  820  also displays a Date field  834 , a Save button  836 , a Cancel button  838 , a Delete button  840 , an Add button  842 , and an Edit button  844 . User interface  820  also displays a History of Entries link  846 , which enables a user to identify when a financial record was last saved within RMCS  10 .  
         [0155]    [0155]FIG. 19 is an example embodiment of a user interface  850  displaying collateral performance commentary information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Collateral Performance Commentary from a navigation bar (not shown) located on the left side of user interface  850 . User interface  850  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  850  displays for selected account  322  a summary of collateral performance commentary.  
         [0156]    [0156]FIG. 20 is an example embodiment of a user interface  852  displaying accounts receivable (A/R) ineligibles information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Ineligibles from a navigation bar located on the left side of user interface  852 . User interface  852  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  852  displays for selected account  322  a summary of A/R ineligibles.  
         [0157]    [0157]FIG. 21 is an example embodiment of a user interface  853  displaying A/R ineligibles information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Ineligibles Monthly Trends from a navigation bar located on the left side of user interface  853 . User interface  853  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  853  displays for selected account  322  a summary of A/R ineligibles with a monthly trend report.  
         [0158]    [0158]FIG. 22 is an example embodiment of a user interface  854  displaying accounts payable (A/P) concentration information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/P Concentration from a navigation bar located on the left side of user interface  854 . User interface  854  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  854  displays for selected account  322  a summary of A/P concentration.  
         [0159]    [0159]FIG. 23 is an example embodiment of a user interface  855  displaying A/P aging information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/P Aging from a navigation bar located on the left side of user interface  855 . User interface  855  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  855  displays for selected account  322  a summary of A/P aging.  
         [0160]    [0160]FIG. 24 is an example embodiment of a user interface  856  displaying A/R aging information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Aging from a navigation bar located on the left side of user interface  856 . User interface  856  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  856  displays for selected account  322  a summary of A/R aging.  
         [0161]    [0161]FIG. 25 is an example embodiment of a user interface  857  displaying A/R concentration information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Concentration from a navigation bar located on the left side of user interface  857 . User interface  857  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  857  displays for selected account  322  a summary of A/R concentration.  
         [0162]    [0162]FIG. 26, is an example embodiment of a user interface  858  displaying A/R sales and receivables statistics for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Sales &amp; Receivables Statistics from a navigation bar located on the left side of user interface  858 . User interface  858  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  858  displays for selected account  322  a summary of A/R sales and receivable statistics.  
         [0163]    [0163]FIG. 27 is an example embodiment of a user interface  859  displaying A/R verification information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects A/R Verification from a navigation bar located on the left side of user interface  859 . User interface  859  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  859  displays for selected account  322  a summary of A/R verifications.  
         [0164]    [0164]FIG. 28 is an example embodiment of a user interface  860  displaying detailed information relating to inventory appraisals for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Inventory Appraisal from a navigation bar (not shown) located on the left side of user interface  860 . User interface  860  is included in the Collateral category of Data Section  344 . Data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  860  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  860  displays for selected account  322  a summary of inventory appraisals for account  322 . In the example embodiment, user interface  860  displays an Account Name field  862  showing selected account  322 , which is also known as the Analyzed Business. User interface  860  also includes a Date field  866 , a History of Entries link  867 , a Go button  868 , an Add Item button  870 , a Delete button  872 , a Save button  874 , and a Cancel button  876 .  
         [0165]    [0165]FIG. 29 is an example embodiment of a user interface  880  displaying detailed information relating to inventory composition for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Inventory Composition from a navigation bar located on the left side of user interface  880 . User interface  880  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  880  displays a summary of inventory composition for account  322 .  
         [0166]    [0166]FIG. 30 is an example embodiment of a user interface  882  displaying detailed information relating to inventory by product for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Inventory By Product from a navigation bar located on the left side of user interface  882 . User interface  882  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  882  displays a summary of inventory by product for account  322 .  
         [0167]    [0167]FIG. 31 is an example embodiment of a user interface  884  displaying detailed information relating to inventory gross margin for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Inventory Gross Margin from a navigation bar located on the left side of user interface  884 . User interface  884  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  884  displays a summary of inventory gross margin for account  322 .  
         [0168]    [0168]FIG. 32 is an example embodiment of a user interface  886  displaying detailed information relating to inventory by location for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Inventory By Location from a navigation bar located on the left side of user interface  886 . User interface  886  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  886  displays a summary of inventory by location for account  322 .  
         [0169]    [0169]FIG. 33 is an example embodiment of a user interface  888  displaying detailed information relating to machinery and equipment (M&amp;E) appraisals for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects M&amp;E Appraisal from a navigation bar located on the left side of user interface  888 . User interface  888  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  888  displays a summary of inventory by location for account  322 .  
         [0170]    [0170]FIG. 34 is an example embodiment of a user interface  890  displaying detailed information relating to real estate appraisals for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Real Estate Appraisal from a navigation bar located on the left side of user interface  890 . User interface  890  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  890  displays a summary of inventory by location for account  322 .  
         [0171]    [0171]FIG. 35 is an example embodiment of a user interface  892  displaying detailed information relating to audits for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Audits from a navigation bar located on the left side of user interface  892 . User interface  892  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  892  displays a summary of audits for account  322 .  
         [0172]    [0172]FIG. 36 is an example embodiment of a user interface  894  displaying detailed information relating to miscellaneous collateral matters for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Miscellaneous Collateral Matters from a navigation bar located on the left side of user interface  894 . User interface  894  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  894  displays a summary of miscellaneous collateral matters for account  322 .  
         [0173]    [0173]FIG. 37 is an example embodiment of a user interface  900  displaying capital structure and CF Business exposure by business and product information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Capital Structure and GECC Exposure from a navigation bar located on the left side of user interface  900  (navigation bar shown in FIG. 36). User interface  900  is included in the Financial Statements and Capital Structure category of Data Section  344 . Data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  900  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  900  illustrates for selected account  322  capital structure, the CF Business capital exposure, and the GlobalNet exposure within the CF Business. In the example embodiment, user interface  900  illustrates an Account Name field  902  showing selected account  322 , which is also known as the Analyzed Business. User interface  900  also displays a Date field  904 , a History of Entries link  905 , a Save button  906 , a Cancel button  908 , a View button  910 , an Add button  912 , an Edit button  914 , and a Delete button  916 .  
         [0174]    In the example embodiment, user interface  900  also includes a column having a reference “Per ABLE/ALCAR”. As stated above, ABLE is a known and commercially available software program manufactured by Computer and Software Enterprises, Inc., San Luis Obispo, Calif. ABLE stands for Asset Based Lending Environment (“ABLE”) and is a collateral and accounting subledger system. Alcar® is a computer software application that enables a user to project or model a financial situation of a business entity based on actual, historical financial information for the business entity. Alcar® also enables a user to compare the “actual” financial information for a company to “expected” financial information and/or “historical” financial information. (Alcar is a registered trademark of The Alcar Group Inc., Skokie, Ill. 60077.)  
         [0175]    [0175]FIG. 38 is an example embodiment of a user interface  940  displaying a financial covenant compliance history for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. User interface  940  is included in the Financial Statements and Capital Structure category of Data Section  344 . Data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  940  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  940  displays for selected account  322  a Financial Covenants section  942 , an Edit Covenant Periods section  944 , and a General Covenant Commentary section  946 . In the example embodiment, user interface  940  displays an Account Name field  948  showing selected account  322 , which is also. known as the Analyzed Business. User interface  940  also displays a Date of Most Recent Covenant Compliance Certificate field  950 , a Covenant Name pull-down field  952 , a Save button  954 , a Cancel button  956 , a Go button  958 , and a History of Entries link  960 .  
         [0176]    [0176]FIGS. 39A through 39C display an example embodiment of a user interface  980  displaying a balance sheet, income statement and cash flow information for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user or after a user selects Financial Statements from a navigation bar (not shown) located on the left side of user interface  980 . User interface  980  is included in the Financial Statements and Capital Structure category of Data Section  344 . Data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  980  displays at least one of graphical and tabular analyses of selected account  322 , and provides data fields for financial information for account  322  to be inputted into RMCS  10 . In the example embodiment, user interface  980  displays for selected account  322  an Assets section  982 , a Liabilities and Shareholder Equity section  984 , an Income Statement section  986 , a Cash Flow section  988 , and an Other section  990 . In the example embodiment, user interface  980  displays an Account Name pull-down field  992  showing selected account  322 , which is also known as the Analyzed Business. User interface  980  also displays a Reporting Period pull-down field  994 , a Scenario pull-down field  996 , a Save button  998 , a Cancel button  1000 , a Go button  1002 , and an Add button  1004 .  
         [0177]    In the example embodiment, the financial information, including balance sheet, income statement and cash flow information, displayed on user interface  980  is enter into RMCS  10  through Alcar®. More specifically, financial information is entered into Alcar®, and is then download from Alcar® to RMCS  10 . As stated above, Alcar® is a computer software application that enables a user to project or model a financial situation of a business entity based on actual, historical financial information for the business entity. Alcar® also enables a user to compare the “actual” financial information for a company to “expected” financial information and/or “historical” financial information.  
         [0178]    [0178]FIG. 40 is an example embodiment of a user interface  1020  displaying a summary of an income statement, debt service ratios, and a cash position for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. User interface  1020  is included in the Financial Statements and Capital Structure category of Data Section  344 . Data may be viewed by a user through Data Section  344  and Setup Section  348  of RMCS  10  (shown in FIG. 1). User interface  1020  displays at least one of graphical and tabular analyses of selected account  322 . In the example embodiment, user interface  1020  displays an Account Name pull-down field  1022  showing selected account  322 , which is also known as the Analyzed Business. User interface  1020  also displays a Scenario pull-down field  1024 , a Year pull-down field  1026 , a Save Commentary button  1028 , and a Financial Commentary section  1030  where financial commentary is inputted for selected account  322 .  
         [0179]    FIGS.  41 - 46  are example embodiments of user interfaces illustrating the Strategy category of Data Section  344 . The Strategy category of Data Section  344  displays actions taken by an account manager for the CF Business to either retain or exit selected account  322  as well as a tool to assess and/or evaluate an economic viability of different business options.  
         [0180]    [0180]FIGS. 41A and 41B show an example embodiment of user interface  1040  displaying an account retention plan for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. The account retention plan is a tool used by management of.CF Business to improve the retention of valued accounts and expand CF Business product offerings as well as tap into the valued account vendors, customers and peers to source new business for the CF Business. In the example embodiment, user interface  1040  has a section illustrating whether the CF Business is attempting to retain the account or exit the credit. In addition, user interface  1040  illustrates a strategy of the CF Business for retaining the account.  
         [0181]    [0181]FIG. 42 is an example embodiment of user interface  1050  illustrating recommendations on buying, selling, or holding specific capital structure tranches for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. The term “tranche” as used herein is not limited to foreign notes but also includes assets and financial instrument groupings regardless of country or jurisdiction. User interface  1050  enables a user to add comments supporting various recommendations and strategy. In the example embodiment, data will only be inputted into user interface  1050  for debt deals that have a secondary market for the paper.  
         [0182]    [0182]FIG. 43 is an example embodiment of user interface  1060  displaying trading prices for debt and equity tranches, details the prior market transactions, for example Bank Loan Group (BLG) Transactions, for selected account  322 . User interface  1060  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, BLG Transactions section should be completed for all BLG accounts. Additionally, any accounts that have had secondary market transactions should complete the BLG Transactions section on user interface  1060 . RMCS  10  (shown in FIG. 1) also tracks prior market transactions for other groups other than BLG.  
         [0183]    [0183]FIGS. 44A and 44B display an example embodiment of user interface  1070  displaying company valuations based on a sale of the company as a going concern for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, data relating to asset-based deals is entered through user interface  1070 .  
         [0184]    [0184]FIGS. 45A and 45B show an example embodiment of user interface  1080  displaying company valuation based on a liquidation of the company&#39;s assets for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, for each asset, net recovery is calculated by multiplying an appropriate value by the recovery percent. Liquidation and collection expenses are then deducted. All of the net recovery items are added to calculate the gross collateral proceeds. Additionally, expenses are captured in the liquidation analysis and are broken down as follows: A/R Collection Expenses, Liquidation Expenses, and Additional Expenses.  
         [0185]    [0185]FIG. 46 is an example embodiment of user interface  1090  displaying a strategy being used by an account manager for selected account  322  on a Watchlist Strategy  1092 . User interface  1090  is accessed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user.  
         [0186]    FIGS.  47 - 48  are example embodiments of user interfaces illustrating the Deal Structure category of Data Section  344 . The Deal Structure category of Data Section  344  illustrates scheduled debt payments and actual payments received for all tranches of debt for selected account  322 , and illustrates a negotiated fee structure for each borrower.  
         [0187]    [0187]FIG. 47 is an example embodiment of user interface  1100  that displays an amortization schedule for all tranches of company debt for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, if a company has debt with regularly scheduled amortization payments or a one-time bullet payment, such payments may be entered in RMCS  10  (shown in FIG. 1) through user interface  1100 .  
         [0188]    [0188]FIG. 48 is an example embodiment of user interface  1120  displaying a negotiated fee structure for each transaction for selected account  322 . User interface  1120  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, fees that may be displayed on user interface  1120  include at least one of agency fees, audit fees, success fees, and legal fees.  
         [0189]    FIGS.  49 - 52  are example embodiments of user interfaces illustrating the Equity category of Data Section  344 . The Equity category of Data Section  344  illustrates whether the CF Business has an equity interest in selected account  322 .  
         [0190]    [0190]FIG. 49 is an example embodiment of user interface  1140  displaying a summary of information relating to a company&#39;s investors and capital raising history for equity deals for selected account  322 . User interface  1140  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, data will only be inputted into user interface  1140  for deals in which the CF Business has an equity interest.  
         [0191]    [0191]FIG. 50 is an example embodiment of user interface  1150  that displays a company&#39;s progress on meeting milestones and illustrates how much cash the company has to meet future obligations for selected account  322 . User interface  1150  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by the user. In the example embodiment, data will only be inputted into user interface  1150  for deals in which the CF Business has an equity interest.  
         [0192]    [0192]FIG. 51 is an example embodiment of user interface  1160  that displays estimated valuation of common equity, the CF Business&#39;s ownership percentage, and strategy to maximize value and exit investment for selected account  322 . User interface  1160  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user.  
         [0193]    [0193]FIG. 52 is an example embodiment of user interface  1170  that calculates valuation and pre-tax gain for equity instruments other than common stock and maintains characteristics for each equity instrument for selected account  322 . User interface is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, user interface  1170  is utilized if an equity investment other than common stock is held. On an equity setup page, the user will note the types of equity investments that the CF Business has made in the Analyzed Business, the cost basis, and the share or rights held. If the equity instrument is something other than common stock, the information is than further used in user interface  1170 . In the example embodiment, data must be inputted into at least one of Dividend Rate field, Dividend Type field, Redemption Value field, Number of Warrants in the Money field, and Conversion Cost of Warrants field on user interface  1170 .  
         [0194]    FIGS.  53 - 55  are example embodiments of user interfaces displaying the Company category of Data Section  344 . The Company category of Data Section  344  illustrates general information regarding the CF Business&#39; relationship with the Analyzed Business, current events impacting the Analyzed Business, and how the Analyzed Business is rated by external agencies and by internal resources.  
         [0195]    [0195]FIG. 53 is an example embodiment of user interface  1180  that displays general background information about the Analyzed Business, also referred to as selected account  322 , and its relationship with the CF Business. User interface  1180  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, information displayed on user interface  1180  provides a general overview of the Analyzed Business and describes the nature of the relationship with the borrower.  
         [0196]    [0196]FIG. 54 is an example embodiment of user interface  1190  that tracks recent events affecting the selected account  322 , which is also known as the Analyzed Business, and records loan activity. User interface  1190  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user.  
         [0197]    [0197]FIG. 55 is an example embodiment of user interface  1200  that displays internal and external risk ratings of the Analyzed Business, also referred to as selected account  322 . User interface  1200  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, all deals will have an internal auto calculation of credit risk rating as well as facility risk rating, which are each based upon a predetermined criteria. These risk ratings are displayed on user interface  1200 .  
         [0198]    [0198]FIG. 56 is an example embodiment of user interface  1210  that displays the Contacts category of Data Section  344 . The Contacts category of Data Section  344  displays the names of those persons involved with selected account  322 , also known as the Deal Team. User interface  1210  is displayed after menu tab Accounts  324  and sub-menu tab Data  344  are selected by a user. In the example embodiment, user interface  1210  includes those persons on the deal team for the CF Business that are involved in selected account  322 , and each persons role on the deal team. In alternative embodiments, user interface  1210  will also include persons outside of the CF Business that are also involved in selected account  322 .  
         [0199]    [0199]FIG. 57 is an example embodiment of a user interface  1220  displaying a summary of outstanding alerts for all accounts illustrated on user interface  320  (shown on FIG. 6). User interface  1220  is displayed after menu tab Accounts  324  and sub-menu tab Alerts  346  are selected by a user. In the example embodiment, user interface  1220  displays at least two alerts including: Informative Alerts and Action Alerts. An Informative Alert is an alert sent to an account manager within the CF Business to notify the account manager of possible changes in the overall deal that include, but are not limited to, the credit structure, collateral performance, risk ratings, and financial performance of the Analyzed Business. An Action Alert is an alert that requires action. An Action Alert is sent to the account manager to notify the account manager that the user has been instructed to take some action. Additionally, in the example embodiment, user interface  1220  permits the alerts to be escalated to a series of upper management layers within the CF Business such that, after a specified period of time or when an informative alert has exceeded a certain threshold, an alert will automatically be sent to the various layers of upper management based on the severity of the alert. Also, in the example embodiment, user interface  1220  displays whether an action alert has been resolved or when an informative alert has been acknowledged by an account manager. An action alert may be resolved when the necessary information is received by the CF Business and RMCS  10  (shown in FIG. 1) is updated with respect to the information received. An informative alert may be resolved when the account manager acknowledges the alert. Additionally, with respect to either type of alert, the account manager can record comments that can be tracked over time and senior management can review, add, delete, and evaluate such comments to more senior management or refer them back to the account manger for further follow up.  
         [0200]    FIGS.  58 - 62  are example embodiments of user interfaces that prompt the user to input information to setup an account, also known as the Analyzed Business, in RMCS  10  (shown in FIG. 1). In the example embodiment and as explained below, these user interfaces drive numerous calculations and decisions made by RMCS  10 .  
         [0201]    [0201]FIG. 58 is an example embodiment of user interface  1240  that displays a screen to be filled out by a user when starting an account setup process. User interface  1240  also displays general information about the account. User interface  1240  is displayed after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. User interface  1240  also includes a navigation bar (not shown) along the left side of user interface  1240  that is common to Setup Section  348 .  
         [0202]    [0202]FIG. 59 is an example embodiment of user interface  1260  that displays a screen for setting up an Analyzed Business&#39;s capital structure. User interface  1260  is displayed after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. Actual capital structure amounts are input into RMCS  10  (shown in FIG. 1) through user interface  900  (shown in FIG. 37) over time as actual financial results are reported. User interface  1260  also includes an ABLE &amp; ALCAR Component Map button that enables a user to map information stored within at least one of ABLE, Alcar®, and RMCS  10  (shown in FIG. 1). In the example embodiment, after a user clicks the ABLE &amp; ALCAR Component Map button, a pop-up screen is displayed (not shown in FIG. 59) that enables the user to link information stored in at least one of ABLE, Alcar®, and RMCS  10  such that the information may be accessed, displayed, and utilized by RMCS  10 .  
         [0203]    [0203]FIG. 60 is an example embodiment of user interface  1280  that displays a screen for setting up an identification of each sub-ledger component by a collateral group. User interface  1280  is displayed after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. In the example embodiment, the subledger system shown is ABLE, a known and commercially available software program. Although ABLE is shown in the example embodiment, RMCS  10  does not require ABLE as it sub-ledger system. Rather, RMCS  10  can utilize and interface with a plurality of known and commercially available sub-ledger systems.  
         [0204]    [0204]FIG. 61 is an example embodiment of user interface  1300  that illustrates the covenants for a loan for a selected account  322  User interface  1300  is displayed after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. In the example embodiment, all covenants should be setup in RMCS  10  (shown in FIG. 1) during the initial setup process. Actual covenant levels are input into RMCS  10  through user interface  940  (shown in FIG. 38) over time as the actual financial results are reported.  
         [0205]    [0205]FIG. 62 is an-example embodiment of user interface  1310  that displays a screen to be completed for deals involving equity investments for selected account  322 . User interface  1310  is displayed after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. In the example embodiment, user interface  1310  enables a user to track all transactions involving at least one of common stock, non-convertible preferred stock, convertible preferred stock, a Limited Liability Corporation (LLC), a Limited Partnership (LP) interest, warrants, and options. User interface  1310  does not have to be completed for equity funds.  
         [0206]    [0206]FIG. 63 is an example embodiment of a user interface  1320  displaying a home page of RMCS  10  (shown in FIG. 1) after a user has logged onto RMCS  10 , and selected menu tab Portfolio  326  and sub-menu tab Home  338 . User interface  1320  illustrates a summary of RM information  106  (shown in FIG. 3) for all accounts  322  (shown in FIG. 6), or Analyzed Businesses, within the Commercial Finance Business Unit for which the user is responsible as an account manager or a manager of account managers (i.e., a Team Leader) or other upper management. As such, the most senior management of the CF Business have access to an entire account portfolio of the organization. In an example embodiment, for team leaders, user interface  1320  displays all accounts for all of the account managers that the team leader manages. For portfolio mangers or above, user interface  1320  displays all accounts associated with the team leaders they manage. In the example embodiment, user interface  1320  also displays sub-menu tabs located below menu tab Portfolio  326 . The sub-menu tabs include at least one of Home  338 , Analysis/Report  340 , and Alerts  346 . The sub-menu tabs further enable the user to navigate RMCS  10 .  
         [0207]    When menu tab Portfolio  326  and sub-menu tab Home  338  are selected, user interface  1320  displays a summary of RM information  106  in tabular form for each accounts  322  for which the user is responsible. In the example embodiment, the table includes at least the following column headers: No. of Alerts  1322 , Avg. Age of Alerts  1324 , CF Commit Amount  1326 , CF Outstanding Amount  1328 , # Accounts Overadvance  1330 , # Watchlist  1332 , $ Outstanding Watchlist  1334 , % of $ of Watchlist  1336 , Total # Accounts  1338 , #&lt;5% Avail  1340 , $&lt;5% Avail  1342 , # Amendments (not shown), and # Default Accounts  1346  (not shown). In the example embodiment, each column is sortable by ascending or descending order. Additionally, each column header is a link, when selected, displays another screen that provides additional information relating to the selected column header. In the example embodiment, user interface  1320  also displays a Business Unit data box  1347 , a Business Segment data box  1348 , a Region data box  1350 , a SIC data box  1354 ,-and a Go button  1356 .  
         [0208]    These data boxes (e.g., Business Unit data box  1347 , Business Segment data box  1348 , Region data box  1350 , and SIC data box  1354 ) are “filters” that allow the user to drill down on information displayed on user interface  1320 . As discussed below, these filters are also displayed on numerous other user interfaces with RMCS  10  so that a user may drill down on information displayed on the particular user interface.  
         [0209]    RMCS  10  allows a business engaging in complex deals, such as commercial financing, mergers, acquisitions and real estate transactions, to collect, manage, store and disseminate RM information among internal deal teams and selected outside deal teams to facilitate a more accurate and efficient analysis of the risks associated with a deal and to facilitate management of workload and personnel. In one embodiment, RMCS  10  also includes a unit of measure assigned to each deal within RMCS  10  wherein the unit of measure, referred to herein as a deal workload factor, represents an amount of work a user may be required to devote to a deal and is based on at least one of a type of the deal, risks associated with the deal, and a progress status of the deal. As a deal is assigned to a user within RMCS  10 , the deal workload factor assigned to that deal is also assigned to the user. In one embodiment, RMCS  10  totals the workload amount for each user, based on each deal assigned to that user, and displays it to a predesignated party within RMCS  10 . The predesignated party may designate a maximum workload amount that may be assigned to any one user. The workload of each user may then be managed by RMCS  10 .  
         [0210]    [0210]FIG. 64 is an example embodiment of a user interface  1380  displaying an analysis of availability for a portfolio, which is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user or after Availability is selected from a navigation bar (not shown in FIG. 64) located along the left side of user interface  1380 . User interface  1380  displays a graphical or tabular analyses of availability for the selected Business Segment Name pull-down list. The analysis enables the user to assess liquidity trends being experienced across the portfolio. In the example embodiment, user interface  1380  displays a Period pull-down field  1382 , a Start Date data field  1384 , an End Date field  1386 , a Display. Graph In pull-down field  1388 , and a Frequency pull-down field  1390 . User interface  1380  also displays the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter. Additional filters are also displayed on user interface  1380  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter.  
         [0211]    User interface  1380  displays financial information in at least one of tabular and graphical form. In the example embodiment, a pie chart is displayed. The financial information supporting the pie chart may also be displayed by clicking on the pie chart or by clicking a particular piece of the pie chart. Additionally, in the example embodiment, tabular illustrations of the financial information are also active such that a user may click on a link included within a tabular illustration to drill down on the financial information supporting that specific entry.  
         [0212]    [0212]FIG. 65 is an example embodiment of a user interface  1400  that also displays an analysis of availability for a portfolio, which is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. User interface  1400  displays at least one of graphical and tabular analyses of availability for the portfolio. The analysis enables the user to assess liquidity trends being experienced across a selected portfolio. User interface  1400  also includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1400  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. The filters enable the user to control the information displayed on user interface  1400 .  
         [0213]    [0213]FIG. 66 is an example embodiment of a user interface  1410  displaying a summary of buy, sell, and hold recommendations made in the portfolio of a -selected Business Unit, Business Segment, and Region. User interface  1410  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. The analysis enables the user to review buy, sell, hold recommendations across a selected portfolio. User interface  1410  also includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1410  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. The filters enable the user to control the information displayed on user interface  1410 .  
         [0214]    [0214]FIG. 67 is an example embodiment of a user interface  1420  displaying a customer map-unmap details page after menu tab Accounts  324  and sub-menu tab Setup  348  are selected by a user. User interface  1420  displays the mapping of an entry between RMCS  10  (shown in FIG. 1) and Alcar®.  
         [0215]    [0215]FIG. 68 is an example embodiment of a user interface  1430  displaying a deal team setup page. The deal team is also displayed on user interface  1210  (shown in FIG. 56). User interface  1430  enables a user to setup a deal team for a particular deal involving selected account  322  including the setting up of the role of each person on the deal team.  
         [0216]    [0216]FIG. 69 is an example embodiment of a user interface  1440  displaying a breakdown of a portfolio by industry concentration. User interface  1440  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. User interface  1440  also includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1440  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. The analysis enables the user to access industry concentrations for the entire portfolio and display them in at least one of graphical and tabular form. In the example embodiment, a pie chart is displayed. The financial information supporting the pie chart may also be displayed by clicking on the pie chart or by clicking a particular piece of the pie chart. Additionally, tabular illustrations of financial information (not shown) are also active such that a user may click on a link included within a tabular illustration to drill down on the financial information supporting that specific entry.  
         [0217]    [0217]FIG. 70 is an example embodiment of a user interface  1450  that displays an industry concentration comparison of a portfolio at two different points in time. User interface  1450  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. The financial information supporting the pie charts may also be displayed by clicking on the pie charts or by clicking a particular piece of the pie charts. Additionally, the tabular illustrations are also active such that a user may click on a link included within a tabular illustration to drill down on the financial information supporting that specific entry.  
         [0218]    [0218]FIG. 71 is an example embodiment of a user interface  1460  displaying a portfolio stratified by liquidation values for a Business Unit, Business Segment, and Region. User interface  1460  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis  340  are selected by a user. In the example embodiment, user interface  1460  includes a Deal Class pull-down field  1462 , which includes Asset Based (shown in FIG. 71), Equity, and Cash Flow as well as ALL. In addition, a pie chart illustrating Loan Coverage Multiples (LCM) of the example portfolio is displayed. The user can then click on the pie chart to drill down to a list of accounts, then to an account, and then to a PMR. User interface  1460  includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1440  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. User interface  1460  allows the user to display the information in at least one of tabular and graphical form.  
         [0219]    [0219]FIG. 72 is an example embodiment of a user interface  1470  displaying a list of accounts in a portfolio by maturity date for a Business Unit, Business Segment and Region. User interface  1470  enables a user to quickly identify which accounts need to be focused on to prevent unwanted portfolio run-off. User interface  1470  displays the accounts that are scheduled to mature within the time horizon selected. In the example embodiment, if an account has multiple maturity dates, the earliest maturity date will be displayed. User interface  1470  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. In addition, a user may click on the account to drill down to the Account Retention Plan shown in FIGS. 41A and 41B.  
         [0220]    [0220]FIG. 73 is an example embodiment of a user interface  1480  that displays frequently viewed control reports by Business Unit, Business Segment, and Region. User interface  1480  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. User interface  1480  includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter, and a Region filter, that enable a user to control the information displayed.  
         [0221]    [0221]FIG. 74 is an example embodiment of a user interface  1490  that illustrates a graphical display of a portfolio by risk classification by a Business Unit, Business Segment, and Region. User interface  1490  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. User interface  1490  includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1490  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. User interface  1490  enables the user to display risk classifications for an entire portfolio, and display them in at least one of graphical and tabular form. In the example embodiment, a pie chart is displayed. The financial information supporting the pie chart may also be displayed by clicking on the pie chart or by clicking a particular piece of the pie chart. Additionally, tabular illustrations of financial information (not shown) are also active such that a user may click on a link included within a tabular illustration to drill down on the financial information supporting that specific entry.  
         [0222]    [0222]FIG. 75 is another example embodiment of a user interface  1500  that illustrates a graphical display of a portfolio by risk classification for a Business Unit, Business Segment, and Region. User interface  1500  is displayed after menu tab Portfolio  326  and sub-menu tab Analysis/Report  340  are selected by a user. User interface  1500  includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed. Additional filters are also displayed on user interface  1500  including a Deal Class filter, a Participation Type filter, a Risk Classification filter, a Customers filter, and a To Exclude filter. User interface  1500  enables the user to display risk classifications for an entire portfolio, and display them in at least one of graphical and tabular form. In the example embodiment, an area graph is displayed. In the example embodiment, a user may click on an entry included within the data table to drill down on the financial information supporting the selected entry. In at least one other embodiment, a user may click on the area graph or a particular portion of the area graph to further display the supporting information.  
         [0223]    [0223]FIG. 76 is an example embodiment of a user interface  1560  displaying a summary of outstanding alerts for all accounts illustrated on user interface  320  (shown on FIG. 6). User interface  1560  is displayed after menu tab Portfolio  326  and sub-menu tab Alerts  346  are selected by a user. In the example embodiment, user interface  1560  illustrates at least two alerts including: Informative Alerts and Action Alerts. An Informative Alert is an alert sent to an account manager within the CF Business to notify the account manager of possible changes in the overall deal that include, but are not limited to, the credit structure, collateral performance, risk ratings, and financial performance of the Analyzed Business. An Action Alert is an alert that requires action. An Action Alert is sent to the account manager to notify the account manager that the user has been instructed to take some action. Additionally, in the example embodiment, user interface  1560  permits the alerts to be escalated to a series of upper management layers within the CF Business such that, after a specified period of time or when an informative alert has exceeded a certain threshold, an alert will automatically be sent to the various layers of upper management based on the severity of the alert. Also, in the example embodiment, user interface  1560  illustrates whether an action alert has been resolved or when an informative alert has been acknowledged by an account manager. An action alert may be resolved when the necessary information is received by the CF Business and RMCS  10  (shown in FIG. 1) is updated with respect to the information received. An informative alert may be resolved when the account manager acknowledges the alert. Additionally, with respect to either type of alert, the account manager can record comments that can be tracked over time and senior management can review, add, delete, and evaluate such comments to more senior management or refer them back to the account manger for further follow up. In the example embodiment, user interface  1560  displays an Alert Detail pull-down field  1562 , which includes at least one of Alert Detail, Alerts by Account, and Alerts by Type, and an Alert Status pull-down field  1564 . User interface  1560  includes the filters at the top of the page, including a Business Unit filter, a Business Segment filter and a Region filter, that enable a user to control the information displayed.  
         [0224]    [0224]FIG. 77 is an example embodiment of a user interface  1570  displaying a summary of outstanding alerts by account. User interface  1570  is displayed after menu tab Portfolio  326  and sub-menu tab Alerts  346  are selected by a user, and after Alerts by Account is inputted into Alert Detail pull-down field  1562  (shown in FIG. 76).  
         [0225]    [0225]FIG. 78 is an example embodiment of a user interface  1580  displaying a summary of outstanding alerts by type for a Business Unit, Business Segment, and Region. User interface  1580  is displayed after menu tab Portfolio  326  and sub-menu tab Alerts  346  are selected by a user, and after Alerts by Type is inputted into Alert Detail pull-down field  1562  (shown in FIG. 76).  
         [0226]    [0226]FIG. 79 is an example embodiment of a user interface  1590  displaying a home page of RMCS  10  (shown in FIG. 1) after a user has logged onto RMCS  10  and selected menu tab Admin  328 . User interface  1590  enables a user to delegate an account to another user. The account may be delegated to another user when: the account manager requests someone to cover the account while the account manager is outside of the office or unavailable for a period of time, or the person who provides coverage is not part of the deal team. In the example embodiment, a team leader and an account manager will receive an electronic message from RMSC  10  when an account is delegated so that the team leader can monitor the activity on the account.  
         [0227]    In an example embodiment, user interface  1590  illustrates a plurality of menu tabs including at least one of Accounts  324 , Portfolio  326 , Admin  328 , Tools  330 , Communication  332 , Help  334 , and Logoff  336 . Although tabs are shown in the example embodiment, pull-down lists, check boxes, and other means for inputting this information could also be used. These menu tabs enable the user to navigate RMCS  10 . In addition, user interface  1590  also illustrates an Account Owner pull-down field for All Accounts  1592 , a Delegate pull-down field for All Accounts  1594 , an Account Owner pull-down field for Specific Accounts  1596 , and a Delegate pull-down field for Specific Accounts  1598 .  
         [0228]    [0228]FIG. 80 is an example embodiment of a user interface  1600  displaying a home page of RMCS  10  (shown in FIG. 1) after a user has logged onto RMCS  10  and selected menu tab Tools  330 . User interface  1600  includes a plurality of links that may be utilized by the user including at least one of Web ABLE, Work Flow, Policy 6.0, Industry Experts, Customer Feedback Center, Intra Links, Trade Finance, and E-Board Room. The links provided are those that are typically used in underwriting and commercial finance. Additional links may be provided as required by users of the system. The links listed herein are for example purposes.  
         [0229]    [0229]FIG. 81 is an example embodiment of a user interface  1610  displaying a home page of RMCS  10  (shown in FIG. 1) after a user has logged onto RMCS  10  and selected menu tab Communication  332 . User interface  1610  displays a summary of communications from risk leaders and from a system administrator.  
         [0230]    [0230]FIG. 82 is an example embodiment of a user interface  1620  displaying a home page of RMCS  10  (shown in FIG. 1) after a user has logged onto RMCS  10  and selected menu tab Help  334 . User interface  1620  displays additional information relating to RMCS  10 . In the example embodiment, user interface  1620  includes a user guide link.  1622 , a glossary of defined terms link  1624 , a frequently asked questions link  1626 , a site map link  1628 , and a feedback link  1630 .  
         [0231]    [0231]FIG. 83 is an example embodiment of a user interface  1640  displaying a covenant summary report for selected account  322 , which is displayed after menu tab Accounts  324  and sub-menu tab Reporting  342  are selected by a user. User interface  1640  displays a chart for a selected account that includes at least one of the following column headers: covenant, covenant calculation date, company calculation, CF Business calculation, covenant level, in compliance, compliance formula, amended, and comment.  
         [0232]    RMCS therefore better enables a business engaging in complex deals, such as commercial financing, mergers, acquisitions and real estate transactions, to collect, manage, store and disseminate RM information among internal deal teams and selected outside deal teams so as to facilitate a more accurate and efficient analysis of the risks associated with a deal and to facilitate management of workload and personnel. More specifically, RMCS enables the CF Business to input RM information on a single occasion and into a single computer workstation that may be located at various locations, permits the various internal deal teams within the CF Business to share RM information when conducting a due diligence analysis and to continue account management of the Analyzed Business, and enables the CF Business to provide RM information to outside deal teams, like outside legal counsel, during the due diligence analysis. The RMCS also enables a user to monitor a plurality of accounts included in a portfolio, and monitor a plurality of portfolios. Additionally, the RMCS enables a deal team leader to manage a workload of an account manager as well as enabling a senior risk officer to manage a workload of team leaders. The RMCS therefore permits the CF Business to devote more time to analyzing RM information and conducting the due diligence analysis, and less time entering, checking and reporting data.  
         [0233]    While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.