Abstract: A planning engine for a financial planning system including at least one processor is provided. The at least one processor is programmed to receive user profile data and account data, assign an asset class weight to each of a plurality of asset classes associated with the account data, and retrieve an expected asset class return, an asset class standard deviation, and an asset class covariance. The processor is also programmed to generate a portfolio data object for each of the plurality of future years wherein the portfolio data object calculates (i) an expected portfolio return across the plurality of asset classes and (ii) a portfolio standard deviation across the plurality of asset classes. The processor is further configured to pass the portfolio data object to a monte carlo return object, receive, from the monte carlo return object, a matrix, and return an account projection derived from the matrix.

Abstract: A graphical user interface for a financial planning system includes at least one planning engine in communication with a database storing user profiles for a first and second plurality of users registered respectively for a first and second service level. An introductory page displays, to the first and second users, a top level menu and a comparison of an estimated retirement income amount to a user goal. The top level menu appears in a substantially identical format and location, and the first comparison appears in a substantially identical format and location, to the first and second users. The introductory page also displays, to the first and not the second users, an enrollment link operable to enable registration for the second service level. The introductory page further displays, to the second and not the first users, a dashboard link operable to open a dashboard page for the second level of services.

Abstract: A graphical user interface (GUI) includes a visual representation of projections over time for a user. The GUI calls a planning engine through an application programming interface (API) where calling the planning engine causes the planning engine to retrieve user profile data of the user, generate a predicted outcome for the user based on the user profile data, and return the predicted outcome to the GUI. In response to receiving the predicted outcome from the planning engine, the GUI updates updating the visual representation based on the predicted outcome. Certain implementations may include multiple planning engines, each with respective APIs, and/or reconfigurable planning engines.

Abstract: A graphical user interface for a financial planning system includes a dashboard page that includes an estimated income widget. The estimated income widget includes a comparison of an estimated retirement income amount to a user goal. The GUI is programmed to call at least one planning engine to generate the comparison based on a respective user profile. The GUI also includes an opportunity rules engine programmed to identify, based on the respective user profile and without calling the at least one planning engine, one of an ordered list of candidate modifications. The dashboard page further includes an opportunity area including (i) a message recommending the identified candidate modification, and (ii) an associated jump link to a page of the GUI enabling the respective user to execute the identified candidate modification.

Abstract: A graphical user interface (GUI) for a financial planning system includes at least one planning engine in communication with a database storing participant profiles for a plurality of participants each having a respective financial account. A dashboard page displays, to an advisor, an account-snapshot widget, a recommended-estimated-income widget, and a current-estimated-income widget. The GUI is programmed to call the at least one planning engine to generate (i) recommended values for the at least one investment composition field and the savings-rate field, based on first values for a salary field, an expected-time-of-retirement field, and a participant goal field, and (ii) a first comparison, based on the recommended values for the at least one investment composition field and the savings-rate field and the first values for the expected-time-of-retirement field and the participant goal field.

Abstract: A graphical user interface for a financial planning system includes at least one planning engine in communication with a database storing user profiles for a first and second plurality of users registered respectively for a first and second service level. An introductory page displays, to the first and second users, a top level menu and a comparison of an estimated retirement income amount to a user goal. The top level menu appears in a substantially identical format and location, and the first comparison appears in a substantially identical format and location, to the first and second users. The introductory page also displays, to the first and not the second users, an enrollment link operable to enable registration for the second service level. The introductory page further displays, to the second and not the first users, a dashboard link operable to open a dashboard page for the second level of services.

Abstract: A graphical user interface for a financial planning system generates and displays a list of savings-option selectors by determining projected retirement incomes for a first savings rate based on an assumed savings type being tax-deferred and non-tax-deferred, and in response to the projected retirement income being higher for the assumed savings type being other than the actual type, including a change-type selector enabling the user to maintain the first savings-rate and update the savings type. The GUI further determines a goal-based savings rate and type that enables the user to meet a user goal, and in response to the goal-based values differing from the actual values, includes a goal-based selector enabling the user to update to the goal-based savings rate and type. The GUI displays the list of savings-option selectors on a savings rate page of the GUI.

Abstract: A graphical user interface (GUI) for a financial planning system includes at least one planning engine in communication with a database storing participant profiles for a plurality of participants each having a respective financial account. A dashboard page displays, to an advisor, an account-snapshot widget, a recommended-estimated-income widget, and a current-estimated-income widget. The GUI is programmed to call the at least one planning engine to generate (i) recommended values for the at least one investment composition field and the savings-rate field, based on first values for a salary field, an expected-time-of-retirement field, and a participant goal field, and (ii) a first comparison, based on the recommended values for the at least one investment composition field and the savings-rate field and the first values for the expected-time-of-retirement field and the participant goal field.

Abstract: A graphical user interface for a financial planning system includes a retirement summary page that includes a current plan tab and a plan model tab. The current plan tab includes an income graph including, for each year of retirement, guaranteed and variable income in a two-color bar graph. Values on the income graph are generated based on income factors associated with a user profile. The plan model tab includes a link selectable to display a page that enables the user to select a model projected income factor that differs from a corresponding income factor. The plan model tab further includes a model income graph including, for each year of retirement, a model guaranteed and variable income in another two-color bar-graph. Values on the model income graph are generated based on the at least one model projected income factor substituted for the corresponding income factors.

Abstract: A graphical user interface for a financial planning system includes a dashboard page that includes an estimated income widget. The estimated income widget includes a comparison of an estimated retirement income amount to a user goal. The GUI is programmed to call at least one planning engine to generate the comparison based on a respective user profile. The GUI also includes an opportunity rules engine programmed to identify, based on the respective user profile and without calling the at least one planning engine, one of an ordered list of candidate modifications. The dashboard page further includes an opportunity area including (i) a message recommending the identified candidate modification, and (ii) an associated jump link to a page of the GUI enabling the respective user to execute the identified candidate modification.