Abstract:
A method and system for integrating and managing information, documents, and compliance among financial professionals, financial professional clients, and financial professional supervisors. The method and system of the invention considers all information necessary for a financial professional to run their business and includes information relevant to the client and supervisor. This information includes full information management, electronic file management, compliance management, broker/dealer oversight, portfolio management, calendar management, and communications management. This information is presented to the financial professional, client, and supervisor in distinct yet integrated modules. Additionally, the method and system of the present invention offers tools for the financial professional, client, and supervisor that are relevant to their respective needs.

Description:
FIELD OF THE INVENTION 
     The present invention relates to a method for integrating and managing information, documents, and compliance for the management and supervision of a financial professional&#39;s practice, and more particularly, to methods for management of a financial professional&#39;s practice, clients, contacts, investment management, filing, compliance, and regulatory requirements by financial professionals, financial professional clients, and financial professional supervisors. 
     DESCRIPTION OF BACKGROUND ART 
     The continued emergence of a fully networked economy is inevitable due to: (1) computer software and hardware becoming increasingly powerful and less expensive; (2) communication and network technologies becoming increasingly powerful and less expensive; and (3) the proliferation of the Internet and other networking related technologies. 
     The use of computer software, hardware and networking technologies in the management of financial services has also expanded in recent years. In particular, financial service firms are continuing to integrate these technologies into their businesses in order to provide an automated approach for personal asset and wealth management and to improve their efficiency in providing financial advice and other services to their clients. 
     As a result of the advances in technologies and applications of these technologies to business tasks, a dramatically expanded use of electronic commerce (e-commerce) has also occurred. Entirely new paradigms for e-commerce have evolved or emerged from traditional non e-commerce businesses and business models. In particular, e-commerce through the Internet, is widely credited with introducing tremendous efficiencies in commercial transactions. This expanded use of the Internet has also dramatically altered the vendor/customer relationship. 
     For example, in the financial services industry, the ability of an organization to provide enhanced customer service through the use of advanced technology and e-commerce can be a valuable competitive advantage. Financial professionals may be hampered in their ability to service a client fully if they are only able to retrieve limited client and financial information due to limited integration of computer hardware, software, networking and e-commerce resources. Therefore, more efficient methods for managing assets and financial advising and more powerful support tools for wealth management and the management of the financial practitioner&#39;s business will require computer hardware/software platforms that overcome past limitations in what is now a highly technological financial arena. 
     SUMMARY OF THE INVENTION 
     The present invention is directed at overcoming the foregoing and other difficulties encountered in the background art. In particular, the present invention is a method and system for facilitating service and analysis of the needs of financial planning professionals and their clients as well as supervisors and regulatory agents responsible for overseeing financial professionals. 
     The embodiments of the present invention provide many aspects that are not believed to be supplied by the background art. For example, integrated calendar and scheduling functionality is not discussed in the art. 
     Additionally, integrated email functionality is not discussed in the art. An embodiment of the invention allows the users to access their email. Users have the ability to both send and receive email from the invention. Further, the invention automatically files all incoming and outgoing email in the appropriate location with the appropriate tags and the appropriate retention period. Sophisticated logic and intelligence rules are used to aid in the reduction and elimination of unwanted emails (e.g. unsolicited advertisements). 
     Further, an embodiment of the invention known as the “Timeline” is not discussed in the art. The timeline is a graphical representation of all events and actions that have occurred displayed in a chronological fashion. Users have the ability to define the length and specific dates within the timeline. For example, the timeline may be used for a client to show things such as journals, account transactions, calendar events, life events (e.g. retirement dates), personal and professional events, and other events that occur within the scope of the invention. 
     Embodiments of the present invention provide a financial professional or other end user (“FP”) with computer screens or other electronic visual display or audio generating device that present information regarding the FP&#39;s business, clients, contacts, companies, investments, model portfolios, and electronic/digital filing. 
     Business information would specifically include, but not be limited to: compliance tracking and management (with regard to corporate or firm rules, federal and state statutes, or any other rule, law, or statute that the FP would be bound by); oversight of all tasks or projects as defined by the FP or the FP&#39;s staff; forecasting of income the FP&#39;s firm can expect to generate based on outstanding advisory fees, assets under management, commissions, and commission trails; pending investment recommendations made to clients; calendar functionality; email management and audit tracking and management (related to regulatory, internal, or other audits of the FP&#39;s practice). 
     Client information would specifically include, but not be limited to: personal and professional details; journaling capabilities (whereby the FP can manage and track notes and details of the event in which the note is regarding); oversight of all tasks or projects as defined by the FP or the FP&#39;s staff; advisory fee tracking; clients&#39; advisor (other than the FP) relationship management; asset, insurance, liability, and cash flow tracking and management; investment check (written by or for the client) tracking; estate document and entity tracking and management; portfolio management, investment performance reporting, and asset under management tracking and management. 
     Contact information would specifically include, but not be limited to: personal and professional details; journaling capabilities; and professional relationships tracking and management. Company information would specifically include, but not be limited to: company locations; company employees and contacts; company benefit plan details; journaling capabilities; and investments managed by the company (for those companies that actually do manage investments). 
     Investment, insurance, and debt products (“PRODUCT”) information would specifically include, but not be limited to: PRODUCT allocation; PRODUCT research tracking and management; PRODUCT comparison capabilities; PRODUCT owner tracking; PRODUCT history; PRODUCT transactions; PRODUCT performance reporting; and commissions and trails tracking and management. 
     Model Portfolio information would specifically include, but not be limited to: model portfolio creation and management; weighted asset allocation calculations; consolidation and calculation of allocation information; consolidation and calculation of equity style information; and client portfolio illustration. 
     Electronic filing would specifically include, but not be limited to: digital documents and files that may be uploaded by an end user, uploaded via an automated process, captured (e.g. email may be captured), or otherwise added to the system; the process and method by which files are converted to a standard format (e.g. PDF/A); the process and method of assigning specific identifiers to each file for identification and retrieval purposes as well as for proper retention; the capabilities to create and manage file retention periods and assignments; the process and method of storing the file in a manner acceptable to be considered compliant with statues, rules, and regulations (e.g. non-erasable and non-alterable on a WORM format); the process and method of storing files in a manner whereby the ability to destroy files after all appropriate retention periods have been satisfied without destroying files that have not satisfied their relative retention requirements is retained; and the ability to retrieve files. Further, the client as well as the FP&#39;s supervisors and regulatory agents responsible for oversight of the FP may be offered access to the same, similar or related data via a Web browser or other interface. 
     Further, the method and system of the present invention provides databases that are maintained and updated for access by a FP or other end users; generates reports; runs summaries and provides projections, analysis, and recommendations for advisement. 
     Furthermore, the method and system of the present invention provides financial services and analysis capabilities that allow an advisor to individually manage a multitude of separate and distinct customer accounts for a fraction of the cost of more expensive background art financial advising systems. Specifically, the method and system of the present invention takes a client&#39;s personal and business profile into account in comparing and selecting financial instruments (e.g., stocks, corporate and municipal bonds, mutual funds, certificates of deposit, government securities, money markets, etc.) for investment and wealth management. 
     In one aspect of the invention, a computer-based method for integrating and managing information, documents, and compliance comprises accessing client data wherein the client data comprises an associated account portfolio and a client profile; retrieving integrated data from a database wherein the integrated data is related to the client data and is compiled from at least one of a plurality of sources; analyzing the retrieved integrated data in accordance with the client profile; enriching the analyzed retrieved integrated data by graphically displaying at least one of performance data, accuracy data, pricing data, benchmark data and historical data associated with the associated account portfolio; communicating the analyzed retrieved integrated data between at least the client and at least an advisor to enable the client and the advisor to collaborate on the analyzed retrieved integrated data; and displaying the analyzed retrieved integrated data based on display specifications which comprise at least one of client defined display specifications and default display specifications. 
     In another aspect of the invention, a system for integrating and managing information, documents, and compliance comprises means for accessing client data wherein the client data comprises an associated account portfolio and a client profile; means for retrieving integrated data from a database wherein the integrated data is related to the client data and is compiled from at least one of a plurality of sources; means for analyzing the retrieved integrated data in accordance with the client profile; means for enriching the analyzed retrieved integrated data by graphically displaying at least one of performance data, accuracy data, pricing data, benchmark data and historical data associated with the associated account portfolio; means for communicating the analyzed retrieved integrated data between at least the client and at least an advisor to enable the client and the advisor to collaborate on the analyzed retrieved integrated data; and means for displaying the analyzed retrieved integrated data based on display specifications which comprise at least one of client defined display specifications and default display specifications. 
     In yet another aspect of the invention, an embodiment that is computer-implemented further comprises a computer-readable medium containing software code that, when executed by a computer, causes the computer to implement method for integrating and managing information, documents, and compliance among financial professionals, financial professional&#39;s clients, and financial professional&#39;s supervisors comprising: providing a user interface for allowing the graphical selection, display and representation of information and commands related to data associated with a financial professional&#39;s practice; accessing the data associated with the financial professional&#39;s practice; retrieving integrated data from one or multiple databases wherein the integrated data is related to the financial professional&#39;s practice data and is compiled from at least one of a plurality of sources; and analyzing the retrieved integrated data by applying at least one of a plurality of operational applications, wherein the plurality of operational applications comprises a filing application, an audit application, a compliance application, a management application and a portfolio application and wherein the selective application of at least one of the plurality of operational applications allows a user of the method to analyze the retrieved integrated data in a manner consistent with their personal style of information management. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1.0  is an exemplary screen shot of a HOME page and NAVIGATION in accordance with an embodiment of the invention. 
         FIG. 2.2  is an exemplary screen shot of a Business Projects Summary page in accordance with an embodiment of the invention. 
       FIG.  2 . 2 . 1  is an exemplary screen shot of a Project Detail page in accordance with an embodiment of the invention. 
       FIG.  2 . 2 . 2  is an exemplary screen shot of a Project Templates page in accordance with an embodiment of the invention. 
         FIG. 2.3  is an exemplary screen shot of a Business Income Forecasting page in accordance with an embodiment of the invention. 
       FIG.  2 . 3 . 1  is an exemplary screen shot of an Assets Under Management and Commission Schedules page in accordance with an embodiment of the invention. 
         FIG. 2.4  is an exemplary screen shot of a Pending Recommendations page in accordance with an embodiment of the invention. 
         FIG. 2.5  is an exemplary screen shot of a Compliance Overview page in accordance with an embodiment of the invention. 
         FIG. 3.1  is an exemplary screen shot of a Client Personal Information in accordance with an embodiment of the invention. 
         FIG. 3.2  is an exemplary screen shot of a Client Professional Information page in accordance with an embodiment of the invention. 
         FIG. 3.3A  is an exemplary screen shot of a Client Journal (Overview) in accordance with an embodiment of the invention. 
         FIG. 3.3B  is an exemplary screen shot of a Client Journal (Specific Journal View) page in accordance with an embodiment of the invention. 
         FIG. 3.3C  is an exemplary screen shot of a Client Journal (Zoom View) page in accordance with an embodiment of the invention. 
         FIG. 3.4  is an exemplary screen shot of a Client Specific Projects page in accordance with an embodiment of the invention. 
         FIG. 3.5  is an exemplary screen shot of a Fees page in accordance with an embodiment of the invention. 
         FIG. 3.6  is an exemplary screen shot of a Client Advisors page in accordance with an embodiment of the invention. 
         FIG. 3.7  is an exemplary screen shot of a Client Administration page in accordance with an embodiment of the invention. 
       FIG.  3 . 7 . 1  is an exemplary screen shot of a Client Administration (Permissions View) in accordance with an embodiment of the invention. 
         FIG. 3.8A  is an exemplary screen shot of a Client Wealth Overview (Current Allocation Detail) page in accordance with an embodiment of the invention. 
         FIG. 3.8B  is an exemplary screen shot of a Client Wealth Overview (Group and Style Detail) page in accordance with an embodiment of the invention. 
         FIG. 3.8C  is an exemplary screen shot of a Client Wealth Overview (Target Allocation Detail) page in accordance with an embodiment of the invention. 
         FIG. 3.8D  is an exemplary screen shot of a Client Wealth Overview (Allocation Balance Detail) page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 2  is an exemplary screen shot of a Client Asset Overview page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 2 . 1  is an exemplary screen shot of a Client Asset Details page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 2 . 2  is an exemplary screen shot of a Client Asset Allocation page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 2 . 3  is an exemplary screen shot of a Client Asset Holdings and Grants page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 2 . 4  is an exemplary screen shot of a Client Asset History page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 3  is an exemplary screen shot of a Client Insurance Overview page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 4  is an exemplary screen shot of a Client Investment Checks page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 5  is an exemplary screen shot of a Client Liabilities page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 6  is an exemplary screen shot of a Client Cash Flow page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 7  is an exemplary screen shot of a Client Estate page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 8  is an exemplary screen shot of a Client Assets Under Management (AUM) Overview page in accordance with an embodiment of the invention. 
       FIG.  3 . 8 . 9  is an exemplary screen shot of an Aggregation page in accordance with an embodiment of the invention. 
         FIG. 3.9  is an exemplary screen shot of a Contact page in accordance with an embodiment of the invention. 
         FIG. 4.1  is an exemplary screen shot of a Company Detail page in accordance with an embodiment of the invention. 
         FIG. 4.2  is an exemplary screen shot of a Company Benefit Plan Detail page in accordance with an embodiment of the invention. 
         FIG. 4.3  is an exemplary screen shot of a Company Journal page in accordance with an embodiment of the invention. 
         FIG. 5.1  is an exemplary screen shot of a Product Overview and Research page in accordance with an embodiment of the invention. 
         FIG. 5.2  is an exemplary screen shot of a Product Allocation page in accordance with an embodiment of the invention. 
         FIG. 5.3  is an exemplary screen shot of a Product Owners and Revenue page in accordance with an embodiment of the invention. 
         FIG. 6.1  is an exemplary screen shot of a Model Portfolio page in accordance with an embodiment of the invention. 
         FIG. 7.1  is an exemplary screen shot of an Administration page in accordance with an embodiment of the invention. 
         FIG. 8.1  is an exemplary screen shot of a Reports page in accordance with an embodiment of the invention. 
         FIG. 9.1A  is an exemplary screen shot of a File Upload Center page in accordance with an embodiment of the invention. 
         FIG. 9.1B  is an exemplary screen shot of a File Upload Center (Edit Detail View) page in accordance with an embodiment of the invention. 
       FIG.  9 . 1 . 1  is an exemplary screen shot of a Files Being Tagged page in accordance with an embodiment of the invention. 
         FIG. 9.2  is an exemplary screen shot of a File Retention Period page in accordance with an embodiment of the invention. 
         FIG. 9.3  is an exemplary screen shot of a File Search page in accordance with an embodiment of the invention. 
         FIG. 9.4  is an exemplary screen shot of a File Tags page in accordance with an embodiment of the invention. 
         FIG. 9.5  is an exemplary screen shot of a Files Not Yet Tagged page in accordance with an embodiment of the invention. 
         FIG. 10  is an exemplary screen shot of a Supervisor Home page in accordance with an embodiment of the invention. 
         FIG. 10.1  is an exemplary screen shot of a Supervisor Audit (Practice Selection) page in accordance with an embodiment of the invention. 
       FIG.  10 . 1 . 1  is an exemplary screen shot of a Supervisor Audit (Home) page in accordance with an embodiment of the invention. 
       FIG.  10 . 1 . 2  is an exemplary screen shot of a Supervisor Audit (Client Specific) page in accordance with an embodiment of the invention. 
         FIG. 11.1  is an exemplary screen shot of a Client Module (Home) page in accordance with an embodiment of the invention. 
         FIG. 11.2  is an exemplary screen shot of a Client Module (Account Detail) page in accordance with an embodiment of the invention. 
         FIG. 11.3  is an exemplary screen shot of a Client Module (Files) page in accordance with an embodiment of the invention. 
         FIG. 12  is an exemplary illustration of non-limiting examples of the user types and their connection to the three modules within an embodiment of the invention. 
         FIG. 13.1  is an exemplary illustration of the Filing Process (Adding) in accordance with an embodiment of the invention. 
         FIG. 13.2  is an exemplary illustration of the Filing Process (Retrieving) in accordance with an embodiment of the invention. 
         FIG. 13.3  is an exemplary illustration of the File Location Structure in accordance with an embodiment of the invention. 
         FIG. 14  is an exemplary illustration of the interconnection of the three modules (Advisor, Client, and Supervisor) and the various compliance embodiments of the invention. 
         FIG. 15  is an exemplary illustration of the interconnection relationships between the various functions of the embodiments of the invention. 
         FIG. 16  is an exemplary System Level Technical Diagram of an embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The present invention provides a computer-based method and system for improved information management for FP&#39;s, FP clients, and FP supervisors. In particular, the method and system integrates various data and information management tools and databases as well as the underlying data and information that require management. Preferably, the present invention is implemented as a combination of software and hardware elements comprising an input device, display monitor, a graphical user interface (GUI), at least one communications device for connection to the internet and remote databases such as a modem, and at least one processing unit of a design adapted to perform the method of the invention. 
     According to an embodiment of the present invention, the invention comprises at least one integrated database that includes or interfaces with relational databases or other types of databases which utilize Sybase or other data storage or query formats, platforms or resources such as OLAP (On Line Analytical Processing), SQL (Standard Query Language); and include a storage area network (SAN). The databases of the present invention may be housed locally or remotely, for instance, in a secure, scalable facility. For security and reliability, redundancy may be employed in the integrated database. 
     The present invention includes a data repository and may host various other applications to provide a consolidated view of information and information management solutions regarding FPs, clients, and supervisors. In addition, the present invention allows the user to customize and analyze the information in a manner consistent with their personal style of information management. The elements that make up the present invention are further discussed in the following paragraphs. 
       FIG. 1.0  is an exemplary computer display screen shot of a HOME page in accordance with an embodiment of the invention. In particular, the HOME page view displays consolidated information gathered from various sources throughout the present invention as well as from outside sources. These consolidated views allow users to quickly access information likely to be currently relevant. As shown in  FIG. 1.0 , the NAVIGATION HEADINGS  110 - 128  allow the user to select different pages and views within the invention. 
     Clicking on each of the navigation headings  110 - 128  shown in  FIG. 1.0  with a mouse or pointer, for example leads to additional screens or views for sub-categories of the heading that provide additional information and selection options for the user. Exemplary screenshots for these subcategories are further discussed below. 
       FIG. 2.2  is an exemplary screen shot of a Business Projects Summary page in accordance with an embodiment of the invention. The projects listed on this page include all projects for a FP&#39;s practice as well as all sub-steps of the projects that the current user is responsible for. These projects include, but are not limited to, projects linked to clients as well as projects not linked to any particular client. Additional action buttons of the Business Projects Summary page, as shown in  FIG. 2.2  include, but are not limited to: “Create new project,”  210 , “Show completed projects,”  212  and “View Templates”  214 , for example. Details of a project can be seen by clicking on a particular project or project sub-step. Additionally, users can filter the information currently displayed by using the “Apply this filter”  216  action button. 
     FIG.  2 . 2 . 1  is an exemplary screen shot of a Project Detail page in accordance with an embodiment of the invention. Additional action buttons of this page, as shown in the “Project”  200  section in FIG.  2 . 2 . 1  include, but are not limited to: “Add a new project”  218 , “Delete the entire project”  220 , “Return to all projects”  222  and “Save this project as a template”  224 . Action buttons in the “Project Step”  226  section of FIG.  2 . 2 . 1  include, but are not limited to: “Edit this step&#39;s members”  228  , “Save this step”  230 , “Add a sub-step to this step”  232 , and “Delete this step”  234 . All the details of a particular project are found on this page. By selecting an individual step (e.g., as shown in FIG.  2 . 2 . 1 : “Send Fact Finder”, “One Week Follow-up”, etc.) from the list on the left side of FIG.  2 . 2 . 1 , further details of that step can be shown on the right side. Each project, as displayed visually in a “tree” structure on the left, can have any number of steps, each of which can have any number of sub-steps, which in turn can have sub-steps, and so on, without limit. Further details of the operation of the Project Detail page are outlined in FIG.  2 . 2 . 1 . 
     The Project Detail page allows users to assign responsibility of project steps to one or multiple individuals including, but not limited to, a specific client, client advisor, user of the system, the FP, a member of the FP&#39;s staff, or the FP&#39;s supervisor or auditor. In addition, project creation and expansion can also occur on this page. FP&#39;s can create multi-tiered projects. Each tier, or step, of the project can be assigned to people who are responsible for the completion of that step. An embodiment of the invention notifies each person as to any status changes via, for example: internal systems, e-mail, and active alerts. Additionally, each project step and sub-step relationship maintains appropriate “parent/child” rules (e.g. a parent step cannot be completed until each child step is completed). As discussed below, projects can also be saved as templates for future projects. 
     FIG.  2 . 2 . 2  is an exemplary screen shot of a Project Templates page in accordance with an embodiment of the invention. Action buttons of the Project Templates page, as shown in FIG.  2 . 2 . 2  include, but are not limited to: “Load this template”  236 , “Delete this template”  238  and “Return to all projects”  240 . Loading a template will create a new project based on the template selected. Further details of the operation of the Project Templates page are outlined in FIG.  2 . 2 . 2 . 
       FIG. 2.3  is an exemplary screen shot of a Business Income Forecasting page in accordance with an embodiment of the invention. Revenue forecasting for the FP&#39;s practice is calculated using values gathered from fees the FP charges clients, from user created asset under management (“AUM”) schedules, and from user defined commission and trail schedules. AUM and commission and trail schedules can be assigned to specific accounts. The values from these accounts are used with the specifically assigned schedules to produce revenue projections. Additionally, upfront commissions can be marked as having been paid so they are not double-counted in projections. Also, logic rules are used to calculate when future revenues can be expected. Further, users can input market growth factors to simulate how different market conditions would affect future income. 
     FIG.  2 . 3 . 1  is an exemplary screen shot of a Assets Under Management and Commission Schedules page in accordance with an embodiment of the invention. Users have the ability to create custom Asset Under Management (“AUM”) schedules as well as Commission and Trail schedules. AUM schedules include account breakpoint tiers that can be assigned basis points. Users can create single or multiple tier AUM schedules. Multi-tier schedules can be calculated in a graduated or flat manner. The gradual manner takes into account any lower breakpoint and the corresponding basis point. The flat manner only takes the current tier&#39;s basis points into account. 
     Commission and Trail schedules are calculated in a similar manner to AUM schedules. However, commissions are investment product based and the user therefore must assign commissions and trails to individual products. The commission calculation also takes into account upfront commissions as well as subsequent payouts, or trails. The user identifies what month after a client&#39;s purchase that the trail starts and ends. The user also assigns basis points to each trail tier. Commissions may have multiple trail tiers. 
     The AUM and Commission and Trail schedules can be assigned to individual accounts and are used in the projection of a FP&#39;s future income as is shown in  FIG. 2.3 . 
       FIG. 2.4  is an exemplary screen shot of a Pending Recommendations page in accordance with an embodiment of the invention. This page lists the outstanding recommendations made to clients as well as a total value of all outstanding recommendations  242 . 
       FIG. 2.5  is an exemplary screen shot of a Compliance Overview page in accordance with an embodiment of the invention. This page is a summary view of various compliance issues throughout the invention. This includes, but is not limited to, displaying relevant contact records, relevant files, and summaries on items such as outstanding audit items (in relation to an audit conducted through the Supervisory Module)  244 , compliance items  246 , continuing education  248 , and compliance meetings  250 . These items can be accessed in detail by clicking on the relevant item, thereby generating a response from the system. Additionally, the invention alerts the user through various means when the status of any item changes (e.g. the user receives an email when a new compliance issue is added). Further details of the operation and features of the Compliance Overview page are outlined in  FIG. 2.5 . 
       FIG. 3.1  is an exemplary screen shot of a Client Personal Information page in accordance with an embodiment of the invention. Personal information about the client can be stored, accessed or displayed. Non-limiting examples of this information include, but are not limited to: client pictures, multiple addresses, detailed dependant information, nick names and birthdates. 
       FIG. 3.2  is an exemplary screen shot of a Client Professional Information Setup page in accordance with an embodiment of the invention. Professional information about the client can be stored, accessed or displayed. Non-limiting examples of this information include, but are not limited to: occupation, work phone, email, and other professional associations. 
       FIG. 3.3A  is an exemplary screen shot of a Client Journal (Overview) page in accordance with an embodiment of the invention. This page displays summary journal information for a specific client. This page also allows the user to create new journals, edit journal categories, and filter the journals currently being displayed. Selecting any displayed journal summary will load that specific journal into a new view as illustrated in  FIG. 3.3B . 
       FIG. 3.3B  is an exemplary screen shot of a Client Journal (Specific Journal View) page in accordance with an embodiment of the invention. Users have the ability to view journals, create new journals, edit existing journals, and delete journals. Exemplary entries in a journal include, but are not limited to, time and date information identified by the user, event description, event attendees, categories, subject, and journal notes. Additionally, the invention automatically identifies which user entered each journal note and when the note was entered (this information cannot be altered by the user). Further, once a journal note has been saved, the user does not have the ability to alter journal notes. This allows the user to identify without question when a specific journal note was written, who wrote it, and what was included in that note. Further, the journal is accessible from each contact&#39;s journal page that has been identified as an event attendee. Furthermore, specific digital files of the invention may also be linked to a specific journal. Selecting a specific existing journal note will load that specific note into a new view as illustrated in  FIG. 3.3C . 
       FIG. 3.3C  is an exemplary screen shot of a Client Journal (Zoom View) page in accordance with an embodiment of the invention. 
       FIG. 3.4  is an exemplary screen shot of a Client Specific Projects page in accordance with an embodiment of the invention. This page is similar in function to the Business Project Summary as identified previously in  FIG. 2.2 . The primary difference is that the projects identified in  FIG. 3.4  are related to a specific client. 
       FIG. 3.5  is an exemplary screen shot of a Fee page in accordance with an embodiment of the invention. The Fee page functions include, but are not limited to: fee general information; specific details regarding past fees invoiced to the client; comparisons of the current client to other clients; a method for automatically calculating fees based on user-defined rules; and a method for automatically generating invoices for clients. 
       FIG. 3.6  is an exemplary screen shot of a Client Advisors page in accordance with an embodiment of the invention. The Client Advisors page provides a list of all of the client&#39;s advisors. FP&#39;s can link any number of contacts as an Advisor to any client. Non-limiting examples of the types of advisor information that can be stored, accessed or displayed include attorneys, accountants, doctors, and other FP&#39;s. 
       FIG. 3.7  is an exemplary screen shot of a Client Administration page in accordance with an embodiment of the invention. In Client Administration  3 . 7 , users can set up an emergency login username and login password that they carry on their person in the event of a medical or other emergency. Clients of the FP will be able to designate specific digital files (e.g., living wills, medical allergies, etc) to be viewed by anyone logging in using their emergency login username and login password. Further details of the operation of the Client Administration page are outlined in  FIG. 3.7 . 
     FIG.  3 . 7 . 1  is an exemplary screen shot of a Client Administration (Permission View) page in accordance with an embodiment of the invention. Users can view the status and details of the specific client&#39;s activity within the Client Module. Additionally, users have the ability to view the Client Module as the client would see it. Users also have the ability to designate specific files to be visible to the client through the Client Module. These files can be grouped into folders that are defined at the client level. Further, users have the ability to reset a client password  310 , unlock a client account  312 , and remove a client&#39;s access rights to the Client Module  314 . 
       FIG. 3.8A  is an exemplary screen shot of a Client Wealth Overview page in accordance with an embodiment of the invention. The Client Wealth Overview page is a consolidation of information regarding a specific client&#39;s wealth including, but not limited to: a list of all balance sheet accounts related to the client; a list of all accounts in process for the client; net worth summaries for the client, their dependents, and estate entities within their control; insurance summaries; and graphical and numeric representations related to their asset allocation. Additionally, users can view consolidated information regarding portfolio holdings. Further, users can view account performance information. Users also have the ability to print several related reports from this page. These reports include, but are not limited to: balance sheets (for accounting, dependents, and outside of estate); portfolio accounts; accounts in process; portfolio holdings; portfolio holdings overlap; portfolio performance; account performance; portfolio allocation; and portfolio balance. 
       FIG. 3.8B  is an exemplary screen shot of a Client Wealth Overview (Group and Style Detail) page in accordance with an embodiment of the invention. This page is identical in function to  FIG. 3.8A  with the exception of displaying the current portfolio allocation group and the equity style breakdown. 
       FIG. 3.8C  is an exemplary screen shot of a Client Wealth Overview (Target Allocation Detail) page in accordance with an embodiment of the invention. This page is identical in function to  FIG. 3.8A  with the exception of adding functionality whereby the user can designate an investment model as the target portfolio for the current client. 
       FIG. 3.8D  is an exemplary screen shot of a Client Wealth Overview (Allocation Balance Detail) page in accordance with an embodiment of the invention. This page is identical in function to  FIG. 3.8A  with the exception of displaying differences in allocation between the current allocation and the target allocation. 
     FIG.  3 . 8 . 2  is an exemplary screen shot of a Client Asset Overview page in accordance with an embodiment of the invention. Further details of the operation of the Client Asset Overview page are shown in FIG.  3 . 8 . 2 . 
     FIG.  3 . 8 . 2 . 1  is an exemplary screen shot of a Client Asset Detail page in accordance with an embodiment of the invention. Detailed account information is displayed on this page. This information is gathered from manual data entry as we all as from various outside sources. Additionally, users have the ability to designate specific commission or asset under management models. The invention can calculate expected income for the FP based on these models and underlying value and transactional data. Users also have the ability to identify accounts not managed by the FP. Clients are made aware of this status in the Client Module. Further details of the operation of the Client Asset Details page are shown in FIG.  3 . 8 . 2 . 1 . 
     FIG.  3 . 8 . 2 . 2  is an exemplary screen shot of a Client Asset Allocation page in accordance with an embodiment of the invention. This page provides the users with the ability to graphically display the allocation of assets as well as the allocation group and equity style. Users can manually enter allocation information, gather it through an external source, or use the allocation of a linked product. Further details of the operation of the Client Asset Overview page are shown in FIG.  3 . 8 . 2 . 2 . 
     In Client Asset Allocation, FP&#39;s can evaluate risks associated with each investment/asset and to identify situations where a client&#39;s investment strategy varies from the client&#39;s risk profile. 
     FIG.  3 . 8 . 2 . 3  is an exemplary screen shot of a Client Asset Holdings and Grants page in accordance with an embodiment of the invention. Account holding information may be entered manually or may be populated from external sources. The invention uses the information to calculate taxable gains or losses and the percent of the account represented by each individual holding. Further details of the operation of the Client Asset Holdings and Grants page are shown in FIG.  3 . 8 . 2 . 3 . 
     FIG.  3 . 8 . 2 . 4  is an exemplary screen shot of a Client Asset History page in accordance with an embodiment of the invention. The capabilities of this page allow the user to track account values manually or have these values automatically populated by external sources. Further details of the operation of the Client Asset History page are shown in FIG.  3 . 8 . 2 . 4 . 
     FIG.  3 . 8 . 3  is an exemplary screen shot of a Client Insurance Overview page in accordance with an embodiment of the invention. Further details of the content of the Client Insurance Detail page are shown in FIG.  3 . 8 . 3 . 
     Additionally, users can track insurance details, allocation, holdings, history, and transactions in a manner similar to assets as shown in FIG.  3 . 8 . 2 . 
     FIG.  3 . 8 . 4  is an exemplary screen shot of a Client Investment Checks page in accordance with an embodiment of the invention. Users can track checks written by clients. Further, the source and destination of the funds can be tracked as well. Users can track any check received or written from any account. Users may also link an image of the referenced check to the record. Further details of the operation of these pages are shown in FIG.  3 . 8 . 4 . 
     FIG.  3 . 8 . 5  is an exemplary screen shot of a Client Liabilities page in accordance with an embodiment of the invention. This page allows users to track details of a client&#39;s debt. Further details of the operation of these pages are shown in FIG.  3 . 8 . 5 . 
     Additionally, users can track liability details, secured assets, history, and transactions in a manner similar to assets as shown in FIG.  3 . 8 . 2 . 
     FIG.  3 . 8 . 6  is an exemplary screen shot of a Client Cash Flow page in accordance with an embodiment of the invention. Detailed information on income and expenses can be tracked on this page. 
     Additionally, the invention can calculate future cash flow projections using a combination of the cash flow data, account information specifics, client specifics (e.g. retirement date), and projection assumptions. The user has the ability to input assumptions to improve projection accuracy (e.g. growth rates, tax information). Further details of the operation of these pages are shown in FIG.  3 . 8 . 7 . 
     FIG.  3 . 8 . 7  is an exemplary screen shot of a Client Estate page in accordance with an embodiment of the invention. Users can store detailed information regarding a client&#39;s estate documents and entities. Additionally, users are notified when it is time for certain documents to be reviewed again. Further, estate entities can be the owner for specific accounts. This allows the proper identification of account ownership as well as the creation of proper balance sheets and other documents. Further details of the operation of these pages are shown in FIG.  3 . 8 . 7 . 
     FIG.  3 . 8 . 8  is an exemplary Client Assets Under Management (AUM) Overview screen. This page provides the capability to graphically display AUM income charts in relation to the selected client as compared to an average of all other clients. Additionally, this page lists all accounts with AUM schedules assigned to them. Further, this page displays projected income received by the FP based on this client&#39;s AUM schedules. Furthermore, calculations for each individual account may be displayed by selecting one of the displayed accounts. Users can select to have calculations completed based in each individual asset, or by grouping individual assets according to AUM schedule as to take advantage of AUM schedule tier breakpoints. Further details of the operation of these pages are shown in FIG.  3 . 8 . 8 . 1 . 
     FIG.  3 . 8 . 9  is an exemplary screen shot of an Aggregation page in accordance with an embodiment of the invention. In Aggregation  3 . 8 . 9 , users can aggregate the following, but is not limited to, account values, cost basis, dates, account numbers, transactions, specific details on holdings, performance related information, asset allocation, equity style, of clients&#39; assets, liabilities, insurance policies, reward points, etc. through third party (e.g. Yodlee Inc.) and proprietary services. This information is updated automatically. 
     Additionally, users have the ability to create local accounts based on the aggregated information. Once an account is created from, or linked to, a local account, all relevant aggregated information regarding the account will remain updated from the various aggregation sources. 
       FIG. 3.9  is an exemplary screen shot of a Contact page in accordance with an embodiment of the invention. Users have the ability to load people who are not clients. These types of people include, but are not limited to; business contacts; personal contacts; and client dependents. The information regarding these people is displayed on a page similar to the one shown in  FIG. 3.9 . 
     Additionally, users have the ability to journal to any contact with similar functions to the journaling capabilities for clients. Users also have the ability to file directly to contacts in a similar manner to the filing to clients 
     Further, users have the ability to “upgrade” contact records to client records. Doing so would give the upgraded contact all functionality available for clients. Further details of the operation of these pages are shown in  FIG. 3.9 . 
       FIG. 4.1  is an exemplary screen shot of a Company Detail page in accordance with an embodiment of the invention. In addition to keeping specific details on the company such as any number of locations and their addresses and phone numbers, this page displays all employees and contacts of the company. Employees are cross referenced with all clients and contacts and will populate for any company of which the contact or client is an employee of 
       FIG. 4.2  is an exemplary screen shot of a Company Benefit Plan Detail page in accordance with an embodiment of the invention. Users can store, access, print, or display details of any number of company plans including, but not limited to the information regarding the benefit: at retirement; early retirement; termination; disability; and death. In addition, users can link this information directly to supporting digital files. 
       FIG. 4.3  is an exemplary screen shot of a Company Journal page in accordance with an embodiment of the invention. Users have similar journal functionality, as discussed above, for any company for clients and contacts. 
       FIG. 5.1  is an exemplary screen shot of a Product Overview and Research page in accordance with an embodiment of the invention. In addition to storing details regarding the specific product, users have the ability to add any number of research notes. The invention automatically records the user who entered each note as well as when the note was created. Once created, the notes cannot be altered. 
     Additionally, the user can compare each product to any number of additional products. Further, broker/dealers have the ability to populate product information as well as underlying research data. Users who are affiliated with the broker/dealer would be able to access these product records. 
       FIG. 5.2  is an exemplary screen shot of a Product Allocation page in accordance with an embodiment of the invention. Users have the ability to manually enter an allocation for a product or populate allocation information from external sources. 
       FIG. 5.3  is an exemplary screen shot of a Product Owners and Revenue page in accordance with an embodiment of the invention. This page provides the capability to graphically display commission and trail income charts in relation to the selected product as compared to an average of all other products. Additionally, this page lists all accounts with commission and trail schedules assigned to them. Further, this page displays projected income received by the FP based on this products commission schedules. Furthermore, calculations for each individual account may be displayed by selecting one of the displayed accounts. Further details of the operation of these pages are shown in  FIG. 5.3 . 
       FIG. 6.1  is an exemplary screen shot of a Model Portfolio page in accordance with an embodiment of the invention. Users can create and track investment models by adding any number of products and assign a weighted model percentage to each. The weighted percentage represents how much of the model is represented by that product. Further, the embodiments of the invention calculate the weighted asset allocation of each product in the model and present a resulting asset allocation and allocation grouping breakdown for that particular model. The source of each underlying allocation is pulled from each respective product&#39;s allocation. These models can be used as a target allocation for individual client portfolio&#39;s to be compared against as shown in  FIG. 3.8C . 
       FIG. 7.1  is an exemplary screen shot of an Administration page in accordance with an embodiment of the invention. Users designated as an “Advisor” have the ability to assign permissions to other users. Permissions include the ability to access the system, view various pages, and the ability to add, edit, or delete various types of information. Users also have the ability to give permissions for users in additional installations of invention access to specific records with specific permissions. 
     Additionally, users have the ability to manage their practice&#39;s branding as seen in the Client Module. This involves custom graphics and text that can be changed by the user at any time. 
     Further, users have the ability to set their preferences within the system (e.g. receiving automated email alerts from the system). 
       FIG. 8.1  is an exemplary screen shot of a Reports page in accordance with an embodiment of the invention. Users have the ability to create pre-defined and custom reports. These reports can be displayed in several file formats including, but not limited to, PDF, spreadsheet, rich text, and html. 
       FIG. 9.1A  and  FIG. 9.1B  are exemplary screen shots of a File Upload Center Setup page in accordance with an embodiment of the invention. The list of “Items not yet tagged” shown on these pages are files that have been uploaded but have not completed the filing (a.k.a. “tagging”) process for this particular location. Files can be uploaded by the user or automatically uploaded via a pre-defined relationship. Users can edit specific file properties before completing the filing process by tagging them. 
     Files are location based meaning they are assigned to specific items such as, but not limited to, specific people, companies, products, the advisor&#39;s practice, and calendar dates. The screen shots show in  FIG. 9.1A  and  FIG. 9.1B  are representative of an upload center for a specific location. Further details of the operation of this page are shown in  FIG. 9.1A  and  FIG. 9.1B . 
     Furthermore, FPs can store, access and display digital files can be stored in a non-erasable and unalterable format for a length of predetermined time. Storing a document in compliant vs. standard storage format is an election that can be made by the FP. The present invention uses the FPs chosen file methods/styles; dates; pre-defined and user defined keywords or tags, as defined above; and other methods to identify and ease the retrieval and display of stored files. 
     Moreover, files can also be linked to specific items within the present invention for “location based” retrieval later. (e.g., a statement for a particular client&#39;s investment can be linked to that exact investment. When viewing that investment in the client&#39;s asset view, the FP can click “Filing” and see all related documents to that particular asset.) Different versions of the same file/document can be created so that a FP can make changes to a document, but retain the original document in an unaltered state to comply with laws, regulations, and rules. 
     FIG.  9 . 1 . 1  is an exemplary screen shot of a File Being Tagged page in accordance with an embodiment of the invention. The tagging process is the final step for the user in the filing process. The user may assign tags to a single or multiple files at once. Tags are user defined identifiers to aid in proper storage, retrieval, and retention of files. Users may assign any number of tags to each file. 
     Additionally, users may also tag a file with any number of balance sheet accounts (if tagging a client file) that are, or have been, under control of that client. 
     Further, users may create tag groups that consist of multiple tags. These tag groups may be loaded in a future tagging session assisting consistent use of file tags. 
     Furthermore, tags may be assigned a specific retention period (see  FIG. 9.2 ). If a user tags a file with tag that has been assigned a retention period, the invention will keep the file in a non-alterable and non-erasable state until the end of the retention period. An embodiment of the invention allows for multiple tags using multiple retention periods. The invention uses all tags and retention periods within each file to continually calculate the minimum retention date (“MRD”). This date is the earliest date a file can be altered or destroyed (erased). 
     Additionally, an embodiment of the invention allows the users to re-file (e.g. move a file to a different location and assign new tags) files that have been previously filed incorrectly. To ensure users do not “cheat” the retention compliance system, the invention retains a complete filing history for each file which includes any previous MRD. When calculating a current MRD for a file, the invention also takes into account any previous MRD for the file and ensures that the current MRD cannot occur before any historical MRD. 
     Further, once a file has been tagged, it is automatically copied and converted to the current ISO standard for long term digital document preservation (e.g. PDF/A-1a) and is copied to a write once read many (“WORM”) media format. The user also retains the original file format accessible on non-WORM media. Files that are stored in WORM media are arranged on media that is specific to its corresponding MRD. This enables the proper files to be destroyed en-masse after their MRD&#39;s have been met. Further details of the operation of this page are outlined in FIG.  9 . 1 . 1 . 
       FIG. 9.2  is an exemplary screen shot of a File Retention Period Setup page in accordance with an embodiment of the invention. Users have the ability to create retention periods. These periods are lengths of time measured in years and months for a specific event. These events include, but are not limited to, a document date, an account opening, an account closing, a termination of a relationship, and any user defined event. Additionally, users can assign tags to specific retention periods. Further details of the operation of this page are outlined in  FIG. 9.2 . 
       FIG. 9.3  is an exemplary screen shot of a File Search page in accordance with an embodiment of the invention. File searches can be conducted by searches of specific fields including, but not limited to, upload date ranges, document date ranges, file author, file tag, file name, and MRD. Additionally, files may be searched by utilizing a visual representation of file tags as shown on the left of  FIG. 9.3 . Selecting individual tags will filter the search results list (as shown on the right of  FIG. 9.3 ) to display the files found within that tag. Files that have been assigned specific balance sheet account tags will have the ability to be displayed by selecting that specific account tag. Files will appear within every tag that it has been assigned. 
     Additionally, selecting a specific file will display the file details (as seen on the lower right of  FIG. 9.3 ). File details include, but are not limited to, the file ID, file name, file cabinet, file folder, file author, file details, upload date, document date, MRD, filing history, and file tag and retention period details. 
     Users have the option to open or re-file an file. Files that have an MRD that is later than the current date cannot delete or alter the file. Further details of the operation of this page are outlined in  FIG. 9.3 . 
       FIG. 9.4  is an exemplary screen shot of a File Tags page in accordance with an embodiment of the invention. Users have the ability to create and modify file tags. File tags can be assigned to appear in one or more filing cabinets during their respective tagging process. These filing cabinets include, but are not limited to, people, companies, products, the FP&#39;s business, and specific dates. 
     Further, users have the ability to create tag groups. These groups can be assigned a name and any number of filing tags. These tag groups are used during the filing process to assist in tagging consistency. Further details of the operation of this page are outlined in  FIG. 9.4 . 
       FIG. 9.5  is an exemplary screen shot of a Files Not Yet Tagged page in accordance with an embodiment of the invention. This page consolidates all files that have not yet completed the tagging process. Clicking on an untagged file will allow the user to properly complete the filing process by adding appropriate tags. Users also have the ability within this page to upload files to multiple locations. Further details of the operation of this page are outlined in  FIG. 9.5 . 
       FIG. 10  is an exemplary screen shot of a Supervisor Home page in accordance with an embodiment of the invention. This page displays all open audits being conducted by the current supervisor user. Additionally, supervisor users have the ability to, but not limited to, audit an advisor, oversee an advisor, find files, and manage their settings. 
     Auditing an advisor allows a supervisor to conduct comprehensive audits on specific advisors and advisor groups. 
     Overseeing an advisor allows a supervisor to view advisor and advisor group details in much the same way as they would for an audit. However, an embodiment of the invention does not automatically track the actions of the supervisor. Additionally, the supervisor does not have the ability to create “Action Items” for the underlying advisor. This section is designed to facilitate a less official audit than an actual and official audit. 
     Finding files allows supervisors to search for files using a variety of search methods. The file search does not have to be advisor or advisor group specific. For example, the supervisor could search for all files with the “Complaint” tag that had been uploaded in the last quarter of the previous year. 
     Throughout the supervisory module, the supervisor has capabilities including, but not limited to, creating notes, marking items for follow-up, marking items as suspicious, marking items as deficient, marking items as illegal, marking items as questionable, marking items as unacceptable, notifying other supervisors of specific items, notifying FP&#39;s of specific items, extending the MRD of any file, viewing any file, and copying files. 
       FIG. 10.1  is an exemplary screen shot of a Supervisor Audit (Practice Selection) page in accordance with an embodiment of the invention. This page allows supervisors to select a specific advisor or advisor group. After selecting an advisor or advisor group, the supervisor is presented with details on the advisor group as well as any audits. 
     Additionally, the supervisor has the option to load an existing audit, or to create a new audit. Further details of the operation of this page are outlined in  FIG. 10.1 . 
     FIG.  10 . 1 . 1  is an exemplary screen shot of a Supervisor Audit (Home) page in accordance with an embodiment of the invention. This page displays the audit creation notes (as shown in the upper left hand corner of FIG.  10 . 1 . 1 ). 
     Further, all actions that have occurred with each audit are automatically recorded and displayed for review. 
     Additionally, the supervisor has the ability to perform several functions. These include, but are not limited to, creating action items, audit specific clients, audit specific products, audit business files of the advisor, audit files that have been grouped by date, and audit files on companies the advisor has stored. 
     Creating action items allows the supervisor to make requests or notifications to the underlying advisor. The advisor is automatically notified of such requests and notifications through various means (e.g. automated emails and notifications within the Advisor Module). The advisor has the option to respond to each action item within the Compliance section of the Advisor Module (see  FIG. 2.5 ). The supervisor is automatically notified of any response made by the advisor to each action item. The supervisor has the ability to mark these responses that identify if the response satisfies the original request or requires more input from the advisor. An embodiment from the invention will notify the advisor of any follow-up actions that are required. 
     Auditing a client allows the supervisor to view details on any number of specific clients of the FP. These details include, but are not limited to, client financial information, client employment details, client age, client files, journals written regarding the client, and client accounts. Further details of the operation of this page are outlined in FIG.  10 . 1 . 2 . 
     Auditing product information allows the supervisor to view details on any number of products input by the FP. These details include, but are not limited to, product use status, client accounts that are invested in the product, product research, comparable products, and product files. 
     Auditing business files allows the supervisor to view files and file details on the files that have been filed under the FP&#39;s business. These details include, but are not limited to, the file ID, file name, file cabinet, file folder, file author, file details, upload date, who filed the document, document date, MRD, filing history, and file tag and retention period details. 
     Auditing files grouped by date allows the supervisor to view files and file details on the files that have been filed under a specific date. These details include, but are not limited to, the file ID, file name, file cabinet, file folder, file author, file details, upload date, who filed the document, document date, MRD, filing history, and file tag and retention period details. 
     Auditing files on other companies allows the supervisor to view files and file details on the files that have been filed under specific companies other than the FP&#39;s company. These details include, but are not limited to, the file ID, file name, file cabinet, file folder, file author, file details, upload date, who filed the document, document date, MRD, filing history, and file tag and retention period details. 
     Further, the supervisor has the ability to extend the MRD of any file they choose. An embodiment of the invention records these changes and adds them to the file history. 
     FIG.  10 . 1 . 2  is an exemplary screen shot of a Supervisor Audit (Specific Client) page in accordance with an embodiment of the invention. This page allows a supervisor to conduct an audit on a specific client within a specific FP&#39;s practice. Client details as well as a list of all audit items specific to the selected client in the current audit are displayed (see the lower half of FIG.  10 . 1 . 2 ). Additionally, the supervisor has the ability to conduct several actions including, but not limited to, creating an action item specifically regarding the currently selected client, viewing the selected client&#39;s files and the file details, viewing journals written by the FP regarding the selected client, and viewing the selected client&#39;s accounts. 
       FIG. 11.1  is an exemplary screen shot of a Client Module (Home) page in accordance with an embodiment of the invention. The Client Portal is accessed by clients of the FP. The page represented in  FIG. 11.1  displays an overview of information for the client. This page displays, but is not limited to, the following items: net worth calculations; insurance totals; current account listings and values; account location chart; account aggregation identifiers; unmanaged account identifier; an image selected by the FP; text and text headings as selected by the FP; and buttons to other areas of the Client Module. 
       FIG. 11.2  is an exemplary screen shot of a Client Module (Account Detail) page in accordance with an embodiment of the invention. Client users are presented with a similar page by clicking in a specific account. This page view displays, but is not limited to: basic account statement information; account history; account allocation; account holdings; account transactions; account performance; account aggregation status. Additionally, clients can link directly to the underlying institution&#39;s online presence (e.g. web site). 
       FIG. 11.3  is an exemplary screen shot of a Client Module (Files) page in accordance with an embodiment of the invention. Client users have the ability to view files that the FP has designated as visible to the client. FP&#39;s have the ability to create custom folders on the client levels. Only folders with files in them are visible. Clients can view file details as well as open any file. 
     Additionally, clients have the ability to create “Emergency logins” and designate specific files to be viewable by such emergency logins. Clients are provided with a “wallet card” template that allows them to carry the emergency login credentials along with instructions on their person. This emergency login could then, for example, be carried in the wallet of the client. In the event of an emergency, for example, one in which the client is incapacitated and hospitalized, emergency personnel could find and use the emergency login to access files. These files could include such things as medical directives, living testaments, religious instructions, etc. 
       FIG. 12  is an exemplary illustration of non-limiting examples of the user types and their connection to the three modules in accordance with an embodiment of the invention. Various user types have inherent permissions to the various modules in an embodiment of the invention. All modules share portions of the data of the invention. 
       FIG. 13.1  is an exemplary illustration of the Filing Process (Adding) in accordance with an embodiment of the invention. This flow chart identifies the process by which Files or File Data Files are added to an embodiment of the invention. An embodiment of the invention allows files to be uploaded by users or by external sources which may be automated. Additionally, the invention allows the manual or automatic upload of “File Data”. File Data is the data that would be found within a specific file (e.g. account statement data). Each File Data file that is uploaded would have a corresponding File Generation Template. This template allows an embodiment of the invention to generate files (e.g. account statements) based on the combination of the File Data and the corresponding templates. Further details of the operation of this page are outlined in  FIG. 13.1 . As is depicted therein, the filing process begins with a user, external source, or automated process uploading or otherwise transfers files. This process is depicted as step  410 . Once the files are uploaded, file metadata is stored in a database (step  412 ) and the file or raw file data type is stored separate from metadata (step  414 ). Once this process has been completed, a determination is then made as to whether the file is an automated file type. This determination is depicted as step  416 . If the answer is yes, a determination is then made as to whether the file is a true file or raw file data (step  418 ). 
     If the file is a true file, then in accordance with step  420 , the proper file location, tags and retention periods based on meta-data are automatically assigned. The files are then copied then converted to the ISO standard for long term preservation of electronic documents (currently PDF/A) in accordance with step  430 , and then moved to the appropriate WORM media in accordance with step  432 , at which point the filing is complete as depicted by step  434 . Returning to step  418 , if it is determined that the file is not a true file, but rather comprises raw file data, then in accordance with step  422 , file data is automatically assigned along with the proper location, tags and retention periods. The file data is then moved to WORM media as depicted by step  426 , and the filing is then completed as depicted in step  434 . 
     Returning now to step  416 , if it is determined that the file is not an automated file, then the user assigns the proper file location and tags in accordance with step  424 , after which retention periods are automatically assigned as shown in step  428 . Steps  430 ,  432  and  434  are then performed as detailed above. 
       FIG. 13.2  is an exemplary illustration of the Filing Process (Retrieving) in accordance with an embodiment of the invention. This flow chart identifies the process by which files are retrieved from an embodiment of the invention. Further details of the operation of this page are outlined in  FIG. 13.2 . As is depicted therein, the retrieving filing process is initiated as depicted in step  440  by the user searching metadata for a specific file. The file identified by step  440  is then selected for retrieval in accordance with step  442 . At this stage, a determination is made as to whether the user requires a file stored on WORM media in accordance with step  444 . If the answer is yes, then a determination is made as to whether the file is a true file as opposed to raw file data is depicted in step  446 . If the answer is yes, then a matching file on WORM media is downloaded as depicted in step  448 , thus completing the retrieval process as depicted in step  458 . 
     Returning to step  446 , if the file is not a true file, then a file data file type is matched with the appropriate file generation template in accordance with step  452 . A file is then generated from a combination of file data and file generation templates in accordance with step  454  and the file is downloaded to the user as depicted in step  456  thereby completing the retrieval process according to step  458 . Returning now to step  444 , if the answer is no, then a matching file on non WORM media is downloaded to the user as depicted in step  450 , thereby completing the retrieval process as depicted in step  458 . 
       FIG. 13.3  is an exemplary illustration of the File Location Structure in accordance with an embodiment of the invention. Files are stored and identified in a location hierarchy. This hierarchy consists of filing cabinets that contain file folders that contain file tags. Each subset is specific to the parent set. For example, the folders for the filing cabinet “People” are individuals within the database. The file tags for the individual people folders are specific to people. 
     Additionally, while subsets are dependent on their parent step, they do not have to be mutually exclusive. For example, the tag “Correspondence” may be used for the People filing cabinet as well as the Company and Grouped By Date filing cabinets. Further details of the operation of this page are outlined in  FIG. 13.3 . 
       FIG. 14  is an exemplary illustration of several compliance specific relationships and connections among the advisor module, client module, and supervisory module in accordance with an embodiment of the invention. The invention is designed to aid in compliance with laws, statutes, rules, and regulations specific to the FP industry. 
       FIG. 15  is an exemplary illustration of the interconnection relationships between the various functions of the embodiments of the invention. 
       FIG. 16  is an exemplary high level technical diagram of the present invention. The system of the present invention provides various services, modules, functions, and access to information. Users of the various modules  510 - 514  (as shown in  FIG. 12 ) may interface with the User Interface  518  which in turn interfaces with the Application Layer  520  through the Internet. Access to additional information may be available through databases that include, but are not limited to a file database  526 ; a records database  528 ; and other databases  530 . Additionally, access to information may be available through additional various storage methods such as hard disk drives  524  and WORM (Write Once Read Many) drives. Data for these databases may be stored and gathered by various methods, such as automated techniques  532  (e.g. web crawlers, web spiders, etc.) or manual techniques (e.g., data entry of users). Further, information may be stored and gathered via External Services  522  (e.g. third party aggregation services). Information for the system may be stored in a single database or separate databases. 
     The foregoing description illustrates and describes the present invention. Additionally, the disclosure shows and describes only the preferred embodiments of the invention, but as mentioned above, it is to be understood that the invention is capable of use in various other combinations, modifications, and environments and is capable of changes or modifications within the scope of the inventive concept as expressed herein, commensurate with the above teachings and/or skill or knowledge of the relevant art. The embodiments described hereinabove are further intended to explain best modes known of practicing the invention and to enable others skilled in the art to utilize the invention in such or other embodiments and with the various modifications required by the particular applications or uses of the invention. Accordingly, the description is not intended to limit the invention to the form or application disclosed herein. Also, it is intended that the appended claims be construed to include alternative embodiments. 
     It will, of course, be understood that, although particular embodiments have just been described, the claimed subject matter is not limited in scope to a particular embodiment or implementation. For example, one embodiment may be in hardware, such as implemented to operate on a device or combination of devices, for example, whereas another embodiment may be in software. Likewise, an embodiment may be implemented in firmware, or as any combination of hardware, software, and/or firmware, for example. Likewise, although claimed subject matter is not limited in scope in this respect, one embodiment may comprise one or more articles, such as a storage medium or storage media. This storage media, such as, one or more CD-ROMs and/or disks, for example, may have stored thereon instructions, that when executed by a system, such as a computer system, computing platform, or other system, for example, may result in an embodiment of a method in accordance with claimed subject matter being executed, such as one of the embodiments previously described, for example. As one potential example, a computing platform may include one or more processing units or processors, one or more input/output devices, such as a display, a keyboard and/or a mouse, and/or one or more memories, such as static random access memory, dynamic random access memory, flash memory, and/or a hard drive. For example, a display may be employed to display one or more queries, such as those that may be interrelated, and or one or more tree expressions, although, again, claimed subject matter is not limited in scope to this example. 
     In the preceding description, various aspects of claimed subject matter have been described. For purposes of explanation, specific numbers, systems and/or configurations were set forth to provide a thorough understanding of claimed subject matter. However, it should be apparent to one skilled in the art having the benefit of this disclosure that claimed subject matter may be practiced without the specific details. In other instances, well known features were omitted and/or simplified so as not to obscure the claimed subject matter. While certain features have been illustrated and/or described herein, many modifications, substitutions, changes and/or equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and/or changes as fall within the true spirit of claimed subject matter.