US20050137953A1 - Asset planning and tracking - Google Patents
Asset planning and tracking Download PDFInfo
- Publication number
- US20050137953A1 US20050137953A1 US10/740,159 US74015903A US2005137953A1 US 20050137953 A1 US20050137953 A1 US 20050137953A1 US 74015903 A US74015903 A US 74015903A US 2005137953 A1 US2005137953 A1 US 2005137953A1
- Authority
- US
- United States
- Prior art keywords
- user
- retirement
- resources
- excess
- transaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/06—Asset management; Financial planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
Definitions
- This invention relates to automated financial management of a person's resources.
- the invention features a computer-implemented method that includes receiving information about transactions that occurred in one or more accounts of a user during a period and determining if the user has excess resources based on the received information. If it is determined that the user has excess resources, then a suggested transaction for disposing of at least a portion of the excess resources is generated.
- Embodiments may include one or more of the following features.
- the computer-implemented method may include receiving information indicating the user's preferences for disposing of excess resources then generating the suggested transaction based on information received about the user's preferences.
- the method may also include computing a periodic savings goal based on the received information and determining if the user has met the periodic savings goal.
- the method may determine if the user has excess resources by netting debit transactions and credit transactions recorded in the user accounts during the period
- the method may also include transmitting a message, such as an e-mail message or an SMS/SMTP message, to the user that contains the suggested transaction.
- the method may include receiving an indication back from the user to execute the suggested transaction and executing the transaction.
- the invention features a computer-implemented method that includes receiving information about transactions that occurred in one or more accounts of a user during a period, determining if the transactions indicate that a savings plan of the user has been exceeded based on the information received and generating a suggested transaction if the savings plan of the user has been exceeded.
- Embodiments may include one or more of the following features.
- the method may include receiving information indicating the user's preferences for disposing excess resources and then generating a suggested transaction based on the information received about the user's preferences.
- the method may further include transmitting a message to the user or posting a web page to a server that contains the suggested transaction.
- the method may further include receiving information indicating the user's desire to execute the suggested transaction and executing the suggested transaction.
- the method may also include computing a periodic savings goal based on information received by the user or an operator on behalf of a user indicating the user's desire to save a certain amount of resources by a certain future date.
- Another aspect of the invention features a computer-implemented method that includes determining if a user has consumed resources budgeted for a period based on information received about transaction that occurred in one or more of the user's accounts during the period and generating a suggested transaction for disposing at least a portion of the excess resources if the user has not consumed the resources budgeted for the period.
- Embodiments may include one or more of the following features.
- the method may include receiving information indicating the user's preferences for disposing of excess resources and then generating a suggested transaction based on the information received indicating the user's preferences.
- the method may further include transmitting a message to the user or posting a web page to a server that contains the suggested transaction.
- the method may further include receiving information indicating the user's desire to execute the suggested transaction and executing the suggested transaction.
- Another aspect of the invention features a system that includes a setup module configured to receive information indicating a user's preferences for disposal of excess resources, a storage device configured to store the user's preferences, an aggregation module configured to periodically retrieve transaction information about one or more accounts, and an execution module configured to determine if the user has excess resources during a period and, if the user has excess resources, then generate a suggested transaction for disposal of the excess income.
- a setup module configured to receive information indicating a user's preferences for disposal of excess resources
- a storage device configured to store the user's preferences
- an aggregation module configured to periodically retrieve transaction information about one or more accounts
- an execution module configured to determine if the user has excess resources during a period and, if the user has excess resources, then generate a suggested transaction for disposal of the excess income.
- Embodiments may include one or more of the following features.
- the system may also include a message generation module configured to form a message that includes the suggested transaction.
- the financial plan may be a spending plan (budget) or a savings plan (e.g., a retirement savings plan).
- the setup module may also be configured to compute a periodic savings plan based on information received that indicates the user's desire to save a certain amount of resources by a certain future date.
- the execution module may also be configured to execute the suggested transaction in response to information indicating the user's desire to complete the suggested transaction.
- Another aspect of the invention features a computer-implemented method that includes using information about transactions that occurred in one or more accounts of a user to determine whether the user's financial situation matches a planned financial situation and automatically suggesting a transaction in an account based on the determination.
- Embodiments may include one or more of the following features.
- the planned financial situation may be a savings plan, such as a retirement savings plan, or a spending plan, such as a retirement budget.
- the method may also include receiving information about transactions that occurred in one or more accounts and receiving information indicating the user's preferences for disposal of excess resources.
- FIGS. 1-2 are a block diagrams of an account management system.
- FIG. 3 is a block diagram of a retirement planning system.
- FIG. 4 is a flow chart illustrating a user activation session.
- FIGS. 5A-5E are flow charts illustrating operation of a retirement planning system.
- an account management system 10 is in communication with several financial institutions 12 , 13 , 14 and several user terminals 15 , 16 , 17 using the Internet.
- the system 10 is also in communication with several operator terminals 18 , 19 over an intranet.
- the operator of an operator terminals 18 , 19 may be a customer service representative who may assist the user in configuring the system, but may not provide financial advice to the user, or a licensed broker or financial advisor who may provide financial advice to the user while assisting the user in configuring the account management system for the particular user.
- the operator may provide other services related or even unrelated to the accounts being managed.
- the operator has access to a telephone and facsimile machine (not shown) to facilitate communication with a user.
- the account management system 10 includes a network server 20 that manages network traffic between the account management system 10 and the users 15 , 16 , 17 , financial institutions 12 , 13 , 14 and operators 18 , 19 .
- the network server 20 is in communication using a local area network 21 with an aggregation system 22 , a rules engine system 23 , a bill pay system 25 , a money transfer system 24 , and a retirement planning system 26 .
- the aggregation system 22 is configured to periodically (e.g., once per day) retrieve and store personal financial data for each user in a database 27 .
- the personal financial data database 27 includes account information from each of the user's accounts regardless of which financial institution maintains the account. For example, if a user maintains a checking account at Bank of AmericaTM, a money market account at Fidelity InvestmentsTM, and a mortgage account at FannieMaeTM, the database 27 will include account information about all three accounts.
- the account information stored within the database is a complete record of all transactions on the account.
- a “personal financial account” or an “account” as used in this description includes any asset account, such as checking, savings, brokerage, money market, 401(k)s, IRAs, whole life insurance policies, annuities, or the like, as well as any liability account, such as mortgages, car loans, student loans, personal loans, utility accounts, home equity lines, or the like.
- the term “financial institution” as used in this description refers to any individual, company, corporation, partnership, government entity, or any other entity that maintains a personal financial account, and includes such entities as banks, brokerage companies, mutual fund companies, life insurance companies, mortgage companies, loan service companies, utility companies, and companies that manage pensions or 401(k) account.
- the aggregation system 22 may be any known aggregation system, such as the Yodlee iFinityTM system, that periodically retrieves and stores account data from the various financial institutions each user maintains an asset or liability account.
- the rules system 23 includes a rules setup module 28 , a rules database 29 , and a rules engine 30 .
- the rules setup module 28 is a software program that prompts the user for information to set up rules that specify how the system 10 is to manage the user's accounts.
- the rules set up by each user are stored in the rules database 29 and are accessed by the rules engine 30 to automatically manage the user's accounts.
- An example of a rules system that may be used in the account management system is described in a co-pending application titled “Financial Account Management” to Steve Elterich and John McDonough filed on the same date as this disclosure, and which is herein incorporated by reference.
- the money transfer system 24 is configured to permit a user to transfer money between accounts and may be any system known in the art for facilitating electronic money transfers between accounts, such as the Fidelity Money LineTM system.
- the bill payment system 25 is configured to permit a user to pay bills on-line by “writing” an electronic check.
- the bill payment system 25 may be any on-line bill payment system known in the art, such as the Fidelity Bill Pay SM system.
- the retirement planning system 26 is configured to operate in different ways depending upon whether the user is retired. If the user is not retired, the retirement planning system 26 is configured to project the amount of money a user must save per period (e.g., per month) in order to meet his retirement goal and tracks the user's progress toward the retirement goal. If the user is retired (and is drawing upon his or her retirement assets), then the retirement planning system is configured to analyze and provide the user with information about the consumption of the user's retirement assets.
- the retirement planning system 26 includes a setup module 32 that receives input from a user 34 , a retirement planning database 36 that stores retirement data (e.g., retirement goals, projected retirement date, and an estimated rate of return) for each user of the system, a retirement planning engine 38 that analyzes the user's periodic (e.g., monthly) transactions and a message generator 40 that produces messages to the user or an operator.
- retirement data e.g., retirement goals, projected retirement date, and an estimated rate of return
- a retirement planning engine 38 that analyzes the user's periodic (e.g., monthly) transactions
- a message generator 40 that produces messages to the user or an operator.
- the user In order for retirement planning system 26 to track and analyze a user's retirement assets, the user first configures the system 26 during an activation session.
- a user e.g., user 1 shown in FIG. 1
- the setup module 32 prompts the user to enter personal information about the user such as the user's name, age, mailing address, e-mail address, martial status, current income, or other personal information (block 404 ).
- the setup module extracts the personal information stored about the user from the other system and prompts the user to confirm the accuracy of the data.
- the setup module also prompts the user to complete an electronic investor's profile questionnaire (IPQ) form to obtain information regarding the user's investment preferences and risk tolerance.
- IPQ electronic investor's profile questionnaire
- Retirement data is data about the user's financial retirement plan such as the user's projected retirement age, financial retirement goals, current retirement assets and accounts, and an expected rate of return for the user's portfolio of retirement assets.
- the setup module prompts the user to indicate whether the user is retired and is drawing upon his or her retirement assets or whether the user is not retired and is saving for retirement. If the user indicates that he or she is not retired, then the setup module prompts the user to complete an electronic investor's retirement questionnaire (IRQ) form, which asks the user to provide the following retirement data:
- IRQ electronic investor's retirement questionnaire
- the setup module prompts the user for the following information:
- the setup module 32 projects a rate of return for a user based on the user's current portfolio of retirement investments and asks the user to confirm or change the projected rate of return.
- the setup module also permits the user to specify a projected inflation rate.
- the retirement planning system 26 has a preprogrammed inflation rate (e.g., 3% per year).
- the setup module 32 After the setup module 32 receives the user's retirement data, it then prompts the user for information regarding the user's accounts, including all asset and liability accounts (block 408 ). If the user has previously registered accounts with the account management system 10 , the setup module may query and extract a list of the user's accounts from the personal financial data database 27 and ask the user if the assets list is accurate and complete or whether the user would like to add or delete assets from the list.
- the setup module 32 After the setup module 32 receives data regarding the user's accounts, the setup module asks a non-retired user if the user would like the system to automatically save for the user's retirement (decision block 410 ). If the user is not retired, then decision block 410 is skipped and the setup module proceeds directly to block 414 described below. If the non-retired user indicates a desire for the system to automatically save for the user's retirement, the setup module prompts the user for information that enables the system to automatically save for the user's retirement (block 412 ). In this regard, the setup module prompts the user for information about the amount and source or sources of funds from which the user desires the system to fund the user's retirement savings account.
- the user may have a paycheck deposited in a checking account each month and may indicate a desire to have the system automatically transfer a portion of each paycheck (expressed in terms of an absolute dollar amount or a percentage of the paycheck) into an IRA account or other account earmarked for retirement.
- the setup module would recommend a periodic amount the user must save in a tax-deferred or taxable account in order to meet the user's retirement goals based on the retirement and account data provided by the user.
- the setup module After the setup module has obtained information sufficient to automatically save for a non-retired user's retirement or if a user has indicated a desire not to have the system automatically save funds for the user's retirement, the setup module prompts the user for information that indicates the user's preferences for how to use excess monthly income (block 414 ). In this regard, the setup module asks the user a series of questions about how the user would spend extra amounts of money at the end of a month.
- the system asks a non-retired user what the user would do if he or she had $500 left over at the end of the month after paying off all monthly bills and saving for retirement and provides the user with a series of choices such as, spend the money, save the money, pay off debt with the money or some combination of the above.
- the system asks a retired user what the user would do if he or she had $500 of extra retirement income after paying off all monthly bills and provides the user with the same series of choices, i.e., spend the money, save the money, pay off dept or some combination of above.
- the system then provides the user with a comprehensive list of items and asks the user to rate how likely it would be for the user to spend the money on the listed items.
- the setup module may provide the user with a list of items and ask the user to rate each item on a scale.
- the setup module prompts the user for information regarding preferred vendors for various products or services and preferred manufacturers of various products. For example, if the user indicates that he or she would like to spend excess income on electronics products, the system may obtain additional information from the user indicating that the user prefers “name-brand” electronics products such as BoseTM, SonyTM, NikonTM, or Hewlett-PackardTM over other manufacturers' products.
- the system may obtain additional information from the user indicating that the user prefers a specific local jeweler over other jewelers. Similarly, if a user indicates a desire to spend excess income on travel, the system may obtain the user's preferences about locations and airlines.
- the setup module provides the user with a comprehensive list of savings goals for the money (e.g., put the money towards the user's retirement savings, child's or grandchild's education, the purchase of a vacation home, automobile or boat, or a “rainy day” fund) and asks the user to rate how likely it would be for the user to save the funds towards the listed goals. For any savings goals that the user indicates a high likelihood of putting money towards, the setup module asks the user to identify the time horizon for the particular goal. Additionally, if the user has also registered his or her accounts with the account management system 10 , then the setup module queries and extracts the user's asset accounts from the personal financial data database 27 (shown in FIGS. 2-3 ) and asks the user to correlate savings goals, if any, with the user's asset accounts.
- a comprehensive list of savings goals for the money e.g., put the money towards the user's retirement savings, child's or grandchild's education, the purchase of a vacation home, automobile or boat, or a
- the setup module provides the user with a list of debts (e.g., mortgage, car loan, credit card, student loans, personal loan, etc.) and asks the user to rate how likely it would be for the user to put the money towards the listed debt.
- debts e.g., mortgage, car loan, credit card, student loans, personal loan, etc.
- the setup module queries and extracts the user's liability accounts from the personal financial data database 27 and asks the user to rate how likely it would be for the user to pay off each of the user's liability accounts.
- the setup module is also configured to recommend to the user to prioritize paying off debts with higher interest rates.
- the setup module prompts the user for information indicating what portion of the excess the user would spend, save or pay off debt. Then the setup module prompts the user for information indicating how the user would spend the money, the savings goal of the money, or what debts the user would pay down in the manner described above. In this way, the setup module builds a profile of the user and, if the retirement planning system detects excess funds at the end of a period (e.g., at the end of a month), the system 26 can notify the user of the excess and suggest various ways in which the user may use the funds based on the user profile.
- the setup module prompts the user for information regarding the user's preferences for receiving a periodic statement (block 416 ).
- the setup module may ask the user to indicate whether the user would like monthly, quarterly, bi-annually or annual statements showing the user's progress towards his or her retirement goals.
- the message generator 40 (shown in FIG. 3 ) is configured to send messages in many formats, e.g., paper, SMS, SMTP, facsimile, Universal Resource Locator (URL), to many endpoints, e.g., mail, network printer, SMS/SMTP device, e-mail, or webpage.
- the setup module is also configured to prompt the user for information indicating the user's preference as to how the user would like to receive periodic statements.
- the setup module After obtaining the user's preference on how often the user would like to obtain a periodic statement, the setup module computes the amount a non-retired user must put towards his or her retirement assets per period (e.g., per month) in order to meet the user's retirement goals based on the retirement and account data supplied by the user (block 418 ). Alternatively, for a retired user, the setup module computes a periodic retirement budget based on the user's assets (retirement and non-retirement), the user's life expectancy, the expected rate of return, and the projected inflation rate (block 418 ). In either case, the setup module will display this figure to the user and ask the user if he or she would like to change any of the underlying data (e.g., the user's retirement goals, expected rate of return).
- the setup module will display this figure to the user and ask the user if he or she would like to change any of the underlying data (e.g., the user's retirement goals, expected rate of return).
- the setup module After collecting the above information from the user, the setup module creates and stores a record of the user's personal information, account information, retirement data and preferences in the retirement database (block 420 ). After the user's record of information has been created in the retirement database, the retirement planning engine 38 is able to track and analyze the user's progress towards his or her retirement goals. If the user wants to change any of the information contained in the retirement database, the user may initiate an update session, which causes the setup module to present the user with the previously entered information and ask the user to indicate how he or she would like to modify the data. Once the user makes the desired modifications, the setup module stores the new information in the user's record of information stored in the retirement planning database 36 .
- Information transferred between the user and the setup module 32 can be interfaced through an operator 18 , 19 (e.g., a customer service representative, a licensed broker or a licensed financial advisor) during an activation session or an update session.
- a licensed broker or financial advisor can engage the user in a discussion about the user's retirement goals and financial resources and obtain information from the user through a telephone call or a face-to-face meeting and enter the appropriate information into the setup module 32 .
- a customer service representative can be contacted by the user in order to assist the user with setting up the retirement planning system 26 .
- FIG. 5 Operation of the retirement planning system shown in FIGS. 1-3 is illustrated in FIG. 5 .
- the retirement planning engine 38 (shown in FIG. 3 ) will periodically (e.g., once a month, once a quarter, once a year, etc.) query the personal financial data database 27 to obtain data indicating all transactions (i.e., debits and credits) on every user account that were recorded during the period (block 502 ).
- the retirement planning engine 38 determines whether the user is retired by looking up the user's retirement data stored in the retirement planning database 36 (decision block 504 ).
- the retirement planning engine 38 computes the net amount deposited into non-retirement and retirement accounts during the period (blocks 506 and 508 ).
- the retirement engine determines which accounts are retirement accounts based on information stored about each account in the retirement planning database 36 that was provided by the user in the activation session (or a subsequent update session).
- the retirement planning engine 38 determines if a user is retired by scanning the user's transaction history for a deposit to a 401(k) account, or an IRA account. If there is a recent deposit (e.g., within the period) in one of these accounts, then the retirement planning engine 38 presumes that the user is not retired.
- the retirement planning engine scans that user's transaction history for a payroll deposit. If there is a payroll deposit, then the retirement planning engine 38 presumes that the user is not retired. If there is no payroll deposit, then the retirement planning engine 38 presumes that the user is retired if the user is age 55 or older. Otherwise, the retirement planning engine 38 presumes that the user is not retired, but is unemployed or otherwise not receiving a regular payroll deposit.
- the retirement planning engine After computing the net amount deposited into non-retirement and retirement account during the period, the retirement planning engine checks to ensure that the deposits into the retirement accounts comport with current state and federal tax laws (block 509 ). In this regard, the retirement planning engine may access the retirement database to determine if the user is eligible to contribute to an IRA given the user's age and current income level. Similarly, the retirement planning engine may track the aggregate amount the user has deposited into tax deferred retirement accounts (e.g., an IRA, Roth IRA or a 401(k) account) to ensure that the user has not deposited more than the maximum contribution amount prescribed by law. If the retirement planning engine determines that the user has reached the maximum limits a tax deferred savings account, the planning engine automatically deposits the funds into to a taxable account.
- tax deferred retirement accounts e.g., an IRA, Roth IRA or a 401(k) account
- the system determines whether the user has met his or her retirement savings goal for the period (decision block 510 ). As previously described, the user's savings goal for the period is determined based on the user's retirement data and account data obtained during the setup session (or a subsequent update session).
- the retirement planning engine 38 determines that the user has not met his or her periodic retirement savings goal, the retirement planning engine 38 then computes the amount which the user is under the periodic goal (block 512 on FIG. 5B ).
- the retirement engine 38 retrieves information from the retirement planning database 36 that indicates the aggregate amount by which the user has underfunded or overfunded the user's retirement accounts as of the previous period. For example, a user may be scheduled to have an aggregate of $4,000 saved for retirement after four months (e.g., scheduled to save $1,000 per month), but may have been able to save an average of $1,100 per month, leaving the user's retirement savings plan overfunded by $400 after the fourth month. If this first period the retirement planning engine 38 has tracked the user's retirement savings plan, then the amount by which the user is under or over the periodic goal is recorded in the retirement planning database 36 as the aggregated shortage/overage amount.
- the retirement planning engine 38 After retrieving the user's aggregate shortage/overage from the previous period, the retirement planning engine 38 computes a new aggregate shortage/overage based on the shortage of the current period (block 516 ). To continue with the above example, if the user has underfunded his or her retirement accounts by $300 for the period, the user's aggregate overage will be reduced from $400 to $100. After computing the new aggregate shortage/overage, the retirement planning engine 38 updates the retirement planning database 36 with this new amount.
- the retirement planning engine 38 determines whether the user has excess income for the period by netting the debits and credits recorded in the user's non-retirement accounts for the period (decision block 518 ). If the retirement planning engine 38 determines that the user does not have excess income for the period (and thus no source from which to fund the shortage in retirement savings for the period), the retirement planning engine 38 transmits to the message generator 40 an indication that the user does not have excess income for the period along with the amount the user has saved for retirement for the period, the amount by which the user was short of the user's periodic retirement savings goal, the total aggregate amount of retirement savings, and the amount the user is over or under the user's aggregate retirement savings goal. The message generator 40 assembles this information in a statement that is sent to the user (block 520 ).
- the retirement planning engine 38 determines if the excess income for the period is less than or equal to the amount needed to reach the user's periodic retirement savings goal (decision block 522 ).
- the retirement planning engine 38 determines that the excess income is less than or equal to the amount needed to reach the periodic retirement savings goal, the retirement planning engine 38 causes the statement generator 40 (shown in FIG. 3 ) to generate an interactive statement recommending that the excess income be applied towards the periodic goal (block 524 ).
- An interactive statement is an electronic message that allows the user to submit a response back to the system.
- An interactive statement may be in the form of an electronic mail message sent to a user's electronic mailbox, an SMS or SMTP message sent to a user's text-messaging device, or a webpage posted to a website that may be accessed by the user.
- the interactive statement generated by the statement generator 40 may be an e-mail message that includes the amount the user has saved for retirement for the period, the amount by which the user was short of the user's periodic retirement savings goal, the total aggregate amount of retirement savings, the amount the user is over or under the user's aggregate retirement savings goal, and the amount of excess income for the period.
- the interactive statement may further include a recommendation to apply the excess income towards the user's periodic retirement savings goal and may provide a hyperlink that the user may click on if the user wants the retirement planning system to transfer the excess income to one or more retirement savings accounts.
- the retirement planning engine 38 then transfers the excess income to one or more of the user's retirement accounts (block 526 ). For example, if the user clicks on a hyperlink to a website in an e-mail indicating that the user would like the system to transfer excess income to one or more retirement accounts, the user may be taken to a secure website that asks the user to input the amount of the excess income the user would like transferred as well as an identification of which retirement account or accounts the user would like the funds to be transferred.
- the website may include a list of each of the user's retirement accounts, how much the user has contributed to each account in over a tax year, and information about the maximum amount, if any, that may be contributed to the retirement accounts in a tax year (e.g., contributions to an IRA account in a tax year are currently capped by law and are not available to persons with adjusted gross income over a specified amount).
- the retirement planning engine 38 transfers the funds accordingly and sends the user a confirmation message.
- the retirement planning engine 38 determines that the excess income is greater than the amount needed to reach the periodic retirement savings goal, the retirement planning engine 38 queries the retirement planning database 36 to retrieve information about the user's spending preferences (block 528 ). Next, the retirement planning engine 38 builds a list of recommendations for spending the excess income above the periodic retirement savings goal based on the information about the user's spending preference retrieved from the retirement planning database 36 (block 530 ) For example, the user may have indicated in an activation or update session that the user would like to use excess income purchase jewelry and to save for a vacation home. The user may have also indicated in the activation or update session a particular account that the user has earmarked for a vacation home. In this example, the retirement planning engine 38 builds a list of the following recommendations:
- the retirement planning engine 38 transmits the list to the statement generator 40 , which incorporates the list into an interactive statement that is sent to the user (block 532 ).
- the interactive statement also notifies the user that the user has excess income and recommends that the user apply the excess income to first meet the periodic retirement savings goal and then use the surplus on one or more of the items on the recommendation list.
- the user may provide information back to the retirement planning system through the interactive message in order to have the system execute any desired transactions (block 530 ). For example, suppose the user provides information back to the system commanding the system to use the excess income to meet the user's periodic retirement goal, purchase gold earrings at jeweler “A” and apply the remainder to the account earmarked for a vacation home.
- the retirement planning engine 38 electronically transfers a portion of the excess income sufficient to meet the user's periodic saving goal from one or more of the user's non-retirement accounts to one or more of the user's retirement accounts.
- the system also automatically purchase the gold earrings by either transferring finds directly to the jeweler, or preferably, charging the earrings on a charge account held by the user (e.g., a Visa or a Mastercard account) and then transferring the purchase amount to the charge account.
- a charge account held by the user e.g., a Visa or a Mastercard account
- the user is able to take advantage of the purchase protections and benefits (e.g., frequently flyer miles) afforded by the charge account.
- the system 26 may hold the purchase funds in an interest bearing account and then transfer the purchase funds to the charge account on the payment due date for the charge account.
- the system 26 also transfers the remaining excess income into the account earmarked for a vacation home.
- the retirement planning engine 38 determines whether there is an aggregate shortage in the user's retirement savings plan (decision block 536 in FIG. 5C ).
- the retirement planning engine 38 determines that there is not an aggregate shortage in the user's retirement savings plan (i.e., the user is at or above the current savings goal for the user's retirement savings plan)
- the retirement engine queries the retirement planning database 36 to obtain the user's spending preferences (block 538 ), builds a list of spending recommendations (block 540 ), prompts the message generator to generate an interactive statement with spending recommendations (block 542 ), and executes any transactions commanded by user in response to the interactive statement (block 544 ), as previously described with respect to blocks 528 , 530 , 532 and 534 .
- the retirement planning engine 38 determines if the excess income is less than or equal to the amount needed to satisfy the shortage (decision block 546 ). If the amount is less than or equal to the amount needed to make up the shortage, then the retirement planning engine 38 prompts the statement generator 40 to generate an interactive statement recommending that the excess income be applied towards the user's retirement savings (block 548 ). If the user responds back to the interactive statement, the system executes any transactions commanded by the user (block 550 ).
- the retirement planning engine 38 determines that the excess income is greater than the amount needed to make up the aggregate shortage in the user's retirement saving plan, the retirement engine then queries the retirement planning database 36 to obtain the user's spending preferences (block 552 ), builds a list of spending recommendations (block 554 ), prompts the message generator to generate an interactive statement with spending recommendations (block 556 ), and executes any transactions commanded by user in response to the interactive statement (block 558 ), as previously described with respect to blocks 528 , 530 , 532 and 534 .
- the retirement planning engine 38 determines, based on the user's retirement information, that the user is retired, the retirement planning engine 38 determines if the user has income above the user's retirement budget (decision block 560 ).
- the user's retirement budget is the periodic income stream needed to have the after-tax amount desired by the user for the period.
- the retirement engine queries the retirement planning database 36 to obtain the user's spending preferences (block 562 shown in FIG. 5D ), builds a list of spending recommendations (block 564 ), prompts the message generator to generate an interactive statement with spending recommendations (block 566 ), and then executes any transactions commanded by user in response to the interactive statement (block 568 ), as previously described with respect to blocks 528 , 530 , 532 and 534 . If the user does not spend excess income, the retirement planning engine 38 recomputes the user's projected retirement assets.
- the retirement planning engine 38 determines that the user does not have income above the user's retirement budget (decision block 560 in FIG. 5A ). If the retirement engine then determines if the user has spent more than the user's retirement budget (decision block 570 in FIG. 5E ). If the user has not spent more than the budgeted amount (i.e., the user has spent exactly the budgeted amount), the statement generator 40 generates a periodic statement showing the projected user's retirement assets (block 572 ). If the user has spent more than the budgeted amount, then the retirement planning engine 38 recomputes the user's projected retirement assets (block 574 ) and the statement generator 40 generate a periodic statement showing a projection of the user's retirement assets (block 576 ).
- the retirement planning system is also configured to allow a user to view the user's current progress towards his or her periodic or overall retirement goal at any time by accessing this information over a secure Internet website.
- the system is also configured to allow a customer service representative, broker or financial advisor to access this information on-line (e.g., through the Internet or an intranet). In this way, a broker or financial advisor is able get a picture of the user's financial resources and spending habits and work to formulate a savings and investment plan tailored for the individual user.
- the message generator is configured to monitor Internet messaging services, such as America On-LineTM instant messaging or YahooTM messenger, for a user to sign on under a handle they provide during the activation session or a subsequent update session.
- Internet messaging services such as America On-LineTM instant messaging or YahooTM messenger
- the message generator determines that a user has logged on to the messaging service, the message generator opens a chat session with the user to provide the user with automated reminders about saving for retirement, messages about the user's savings for the current period or in the aggregate, or other information relating to the user's retirement planning.
- an asset planning and tracking system e.g., retirement planning system 26 shown in FIGS. 2-3
- may plans for and tracks progress towards any savings goal e.g., a house renovation project, a wedding reception, purchase of a second home, a child's college education, or a vacation
- any savings goal e.g., a house renovation project, a wedding reception, purchase of a second home, a child's college education, or a vacation
- an asset planning and tracking system may track other “assets” than financial assets such as frequent flyer miles.
- a frequently flyer tracking system may track a user's frequent flyer miles against a goal (e.g., sufficient miles for roundtrip tickets to Hawaii for a family of four in five years) and may periodically apprise the user of his progress towards the goal and make recommendations as to how to use excess miles.
- a goal e.g., sufficient miles for roundtrip tickets to Hawaii for a family of four in five years
Abstract
Description
- This invention relates to automated financial management of a person's resources.
- People sometimes save part of their income toward a goal, such as saving for retirement or a child's college education, and later (upon retirement or the start of college) periodically withdraw part of the saved money.
- In one aspect, the invention features a computer-implemented method that includes receiving information about transactions that occurred in one or more accounts of a user during a period and determining if the user has excess resources based on the received information. If it is determined that the user has excess resources, then a suggested transaction for disposing of at least a portion of the excess resources is generated.
- Embodiments may include one or more of the following features. The computer-implemented method may include receiving information indicating the user's preferences for disposing of excess resources then generating the suggested transaction based on information received about the user's preferences. The method may also include computing a periodic savings goal based on the received information and determining if the user has met the periodic savings goal. The method may determine if the user has excess resources by netting debit transactions and credit transactions recorded in the user accounts during the period The method may also include transmitting a message, such as an e-mail message or an SMS/SMTP message, to the user that contains the suggested transaction. Similarly, the method may include receiving an indication back from the user to execute the suggested transaction and executing the transaction.
- In another aspect, the invention features a computer-implemented method that includes receiving information about transactions that occurred in one or more accounts of a user during a period, determining if the transactions indicate that a savings plan of the user has been exceeded based on the information received and generating a suggested transaction if the savings plan of the user has been exceeded.
- Embodiments may include one or more of the following features. The method may include receiving information indicating the user's preferences for disposing excess resources and then generating a suggested transaction based on the information received about the user's preferences. The method may further include transmitting a message to the user or posting a web page to a server that contains the suggested transaction. The method may further include receiving information indicating the user's desire to execute the suggested transaction and executing the suggested transaction.
- The method may also include computing a periodic savings goal based on information received by the user or an operator on behalf of a user indicating the user's desire to save a certain amount of resources by a certain future date.
- Another aspect of the invention features a computer-implemented method that includes determining if a user has consumed resources budgeted for a period based on information received about transaction that occurred in one or more of the user's accounts during the period and generating a suggested transaction for disposing at least a portion of the excess resources if the user has not consumed the resources budgeted for the period.
- Embodiments may include one or more of the following features. The method may include receiving information indicating the user's preferences for disposing of excess resources and then generating a suggested transaction based on the information received indicating the user's preferences. The method may further include transmitting a message to the user or posting a web page to a server that contains the suggested transaction. The method may further include receiving information indicating the user's desire to execute the suggested transaction and executing the suggested transaction.
- Another aspect of the invention features a system that includes a setup module configured to receive information indicating a user's preferences for disposal of excess resources, a storage device configured to store the user's preferences, an aggregation module configured to periodically retrieve transaction information about one or more accounts, and an execution module configured to determine if the user has excess resources during a period and, if the user has excess resources, then generate a suggested transaction for disposal of the excess income.
- Embodiments may include one or more of the following features. The system may also include a message generation module configured to form a message that includes the suggested transaction. The financial plan may be a spending plan (budget) or a savings plan (e.g., a retirement savings plan).
- The setup module may also be configured to compute a periodic savings plan based on information received that indicates the user's desire to save a certain amount of resources by a certain future date. The execution module may also be configured to execute the suggested transaction in response to information indicating the user's desire to complete the suggested transaction.
- Another aspect of the invention features a computer-implemented method that includes using information about transactions that occurred in one or more accounts of a user to determine whether the user's financial situation matches a planned financial situation and automatically suggesting a transaction in an account based on the determination.
- Embodiments may include one or more of the following features. The planned financial situation may be a savings plan, such as a retirement savings plan, or a spending plan, such as a retirement budget.
- The method may also include receiving information about transactions that occurred in one or more accounts and receiving information indicating the user's preferences for disposal of excess resources.
- Other features and advantages of the invention will be apparent from the description and from the claims.
-
FIGS. 1-2 are a block diagrams of an account management system. -
FIG. 3 is a block diagram of a retirement planning system. -
FIG. 4 is a flow chart illustrating a user activation session. -
FIGS. 5A-5E are flow charts illustrating operation of a retirement planning system. - As shown in
FIG. 1 , anaccount management system 10 is in communication with severalfinancial institutions several user terminals system 10 is also in communication withseveral operator terminals operator terminals operator terminals - As shown in
FIG. 2 , theaccount management system 10 includes anetwork server 20 that manages network traffic between theaccount management system 10 and theusers financial institutions operators network server 20 is in communication using alocal area network 21 with anaggregation system 22, arules engine system 23, abill pay system 25, amoney transfer system 24, and aretirement planning system 26. - The
aggregation system 22 is configured to periodically (e.g., once per day) retrieve and store personal financial data for each user in adatabase 27. For each user; the personalfinancial data database 27 includes account information from each of the user's accounts regardless of which financial institution maintains the account. For example, if a user maintains a checking account at Bank of America™, a money market account at Fidelity Investments™, and a mortgage account at FannieMae™, thedatabase 27 will include account information about all three accounts. In a preferred embodiment, the account information stored within the database is a complete record of all transactions on the account. A “personal financial account” or an “account” as used in this description includes any asset account, such as checking, savings, brokerage, money market, 401(k)s, IRAs, whole life insurance policies, annuities, or the like, as well as any liability account, such as mortgages, car loans, student loans, personal loans, utility accounts, home equity lines, or the like. The term “financial institution” as used in this description refers to any individual, company, corporation, partnership, government entity, or any other entity that maintains a personal financial account, and includes such entities as banks, brokerage companies, mutual fund companies, life insurance companies, mortgage companies, loan service companies, utility companies, and companies that manage pensions or 401(k) account. - To limit the capacity needed for the database, other implementations may configure the database to include a record of all transactions on an account for a certain time period (e.g., all transactions within the past three months). In another configuration, the database simply maintains the current balance of the account. The
aggregation system 22 may be any known aggregation system, such as the Yodlee iFinity™ system, that periodically retrieves and stores account data from the various financial institutions each user maintains an asset or liability account. - The
rules system 23 includes arules setup module 28, arules database 29, and arules engine 30. Therules setup module 28 is a software program that prompts the user for information to set up rules that specify how thesystem 10 is to manage the user's accounts. The rules set up by each user are stored in therules database 29 and are accessed by therules engine 30 to automatically manage the user's accounts. An example of a rules system that may be used in the account management system is described in a co-pending application titled “Financial Account Management” to Steve Elterich and John McDonough filed on the same date as this disclosure, and which is herein incorporated by reference. - The
money transfer system 24 is configured to permit a user to transfer money between accounts and may be any system known in the art for facilitating electronic money transfers between accounts, such as the Fidelity Money Line™ system. Thebill payment system 25 is configured to permit a user to pay bills on-line by “writing” an electronic check. Thebill payment system 25 may be any on-line bill payment system known in the art, such as the Fidelity Bill PaySM system. - As will be explained in more detail below, the
retirement planning system 26 is configured to operate in different ways depending upon whether the user is retired. If the user is not retired, theretirement planning system 26 is configured to project the amount of money a user must save per period (e.g., per month) in order to meet his retirement goal and tracks the user's progress toward the retirement goal. If the user is retired (and is drawing upon his or her retirement assets), then the retirement planning system is configured to analyze and provide the user with information about the consumption of the user's retirement assets. - Referring to
FIG. 3 , theretirement planning system 26 includes asetup module 32 that receives input from a user 34, aretirement planning database 36 that stores retirement data (e.g., retirement goals, projected retirement date, and an estimated rate of return) for each user of the system, aretirement planning engine 38 that analyzes the user's periodic (e.g., monthly) transactions and amessage generator 40 that produces messages to the user or an operator. - In order for
retirement planning system 26 to track and analyze a user's retirement assets, the user first configures thesystem 26 during an activation session. - For example, as shown in
FIG. 4 , a user (e.g.,user 1 shown inFIG. 1 ) initially establishes communication with theretirement planning system 26 using the Internet and indicates a desire to activate theretirement management system 26 by, for example, clicking on a button in a graphical user interface (block 402). In response, thesetup module 32 prompts the user to enter personal information about the user such as the user's name, age, mailing address, e-mail address, martial status, current income, or other personal information (block 404). If the user has already registered with another system associated with the retirement planning system, e.g., theaccount management system 10, the setup module extracts the personal information stored about the user from the other system and prompts the user to confirm the accuracy of the data. The setup module also prompts the user to complete an electronic investor's profile questionnaire (IPQ) form to obtain information regarding the user's investment preferences and risk tolerance. - After the setup module obtains personal information about the user, the process prompts the user for retirement data (block 406). Retirement data is data about the user's financial retirement plan such as the user's projected retirement age, financial retirement goals, current retirement assets and accounts, and an expected rate of return for the user's portfolio of retirement assets. In one implementation, the setup module prompts the user to indicate whether the user is retired and is drawing upon his or her retirement assets or whether the user is not retired and is saving for retirement. If the user indicates that he or she is not retired, then the setup module prompts the user to complete an electronic investor's retirement questionnaire (IRQ) form, which asks the user to provide the following retirement data:
-
- a. the user's projected retirement age;
- b. the amount of monthly after-tax income (expressed in current dollars) the user desires to have available after retirement;
- c. a list of the user's current retirement assets (e.g., 401(k) accounts, IRAs, annuities, whole life insurance policies that are intended to be cashed out at retirement, and other accounts or assets earmarked for retirement); and
- d. an expected rate of return for the user's retirement assets.
- If the user indicates that he or she is retired, then the setup module prompts the user for the following information:
-
- a. the age at which the user retired;
- b. the user's current age;
- c. a list of the user's current retirement assets and income sources; and
- d. an expected rate of return for the user's retirement assets.
If the user has previously registered accounts with theaccount management system 10, the setup module queries and extracts a list of the user's asset accounts and asks the user to indicate which asset accounts are earmarked for retirement (for a non-retired user ) or being used for retirement (for a retired user). The setup module also asks the user whether the user has any additional assets (e.g., fully-owned real estate, jewelry or valuable collections) that the user plans to consume during retirement.
- With respect to the expected rate of return (items d above), the
setup module 32 projects a rate of return for a user based on the user's current portfolio of retirement investments and asks the user to confirm or change the projected rate of return. - In one implementation, the setup module also permits the user to specify a projected inflation rate. In another implementation, the
retirement planning system 26 has a preprogrammed inflation rate (e.g., 3% per year). - After the
setup module 32 receives the user's retirement data, it then prompts the user for information regarding the user's accounts, including all asset and liability accounts (block 408). If the user has previously registered accounts with theaccount management system 10, the setup module may query and extract a list of the user's accounts from the personalfinancial data database 27 and ask the user if the assets list is accurate and complete or whether the user would like to add or delete assets from the list. - After the
setup module 32 receives data regarding the user's accounts, the setup module asks a non-retired user if the user would like the system to automatically save for the user's retirement (decision block 410). If the user is not retired, thendecision block 410 is skipped and the setup module proceeds directly to block 414 described below. If the non-retired user indicates a desire for the system to automatically save for the user's retirement, the setup module prompts the user for information that enables the system to automatically save for the user's retirement (block 412). In this regard, the setup module prompts the user for information about the amount and source or sources of funds from which the user desires the system to fund the user's retirement savings account. For example, the user may have a paycheck deposited in a checking account each month and may indicate a desire to have the system automatically transfer a portion of each paycheck (expressed in terms of an absolute dollar amount or a percentage of the paycheck) into an IRA account or other account earmarked for retirement. The setup module would recommend a periodic amount the user must save in a tax-deferred or taxable account in order to meet the user's retirement goals based on the retirement and account data provided by the user. - After the setup module has obtained information sufficient to automatically save for a non-retired user's retirement or if a user has indicated a desire not to have the system automatically save funds for the user's retirement, the setup module prompts the user for information that indicates the user's preferences for how to use excess monthly income (block 414). In this regard, the setup module asks the user a series of questions about how the user would spend extra amounts of money at the end of a month.
- In one implementation, the system asks a non-retired user what the user would do if he or she had $500 left over at the end of the month after paying off all monthly bills and saving for retirement and provides the user with a series of choices such as, spend the money, save the money, pay off debt with the money or some combination of the above. Similarly, the system asks a retired user what the user would do if he or she had $500 of extra retirement income after paying off all monthly bills and provides the user with the same series of choices, i.e., spend the money, save the money, pay off dept or some combination of above.
- If the user chooses to spend the money, the system then provides the user with a comprehensive list of items and asks the user to rate how likely it would be for the user to spend the money on the listed items. For example, the setup module may provide the user with a list of items and ask the user to rate each item on a scale. Additionally, the setup module prompts the user for information regarding preferred vendors for various products or services and preferred manufacturers of various products. For example, if the user indicates that he or she would like to spend excess income on electronics products, the system may obtain additional information from the user indicating that the user prefers “name-brand” electronics products such as Bose™, Sony™, Nikon™, or Hewlett-Packard™ over other manufacturers' products. If a user indicates a desire to spend excess income of jewelry, the system may obtain additional information from the user indicating that the user prefers a specific local jeweler over other jewelers. Similarly, if a user indicates a desire to spend excess income on travel, the system may obtain the user's preferences about locations and airlines.
- If the user indicates that he or she would save the money, then the setup module provides the user with a comprehensive list of savings goals for the money (e.g., put the money towards the user's retirement savings, child's or grandchild's education, the purchase of a vacation home, automobile or boat, or a “rainy day” fund) and asks the user to rate how likely it would be for the user to save the funds towards the listed goals. For any savings goals that the user indicates a high likelihood of putting money towards, the setup module asks the user to identify the time horizon for the particular goal. Additionally, if the user has also registered his or her accounts with the
account management system 10, then the setup module queries and extracts the user's asset accounts from the personal financial data database 27 (shown inFIGS. 2-3 ) and asks the user to correlate savings goals, if any, with the user's asset accounts. - Similarly, if the user indicates that he or she would pay off debt, the setup module provides the user with a list of debts (e.g., mortgage, car loan, credit card, student loans, personal loan, etc.) and asks the user to rate how likely it would be for the user to put the money towards the listed debt. If the user has also registered his or her accounts with the
account management system 10, then the setup module queries and extracts the user's liability accounts from the personalfinancial data database 27 and asks the user to rate how likely it would be for the user to pay off each of the user's liability accounts. The setup module is also configured to recommend to the user to prioritize paying off debts with higher interest rates. - If the user indicates that he or she would likely use the excess funds in some combination of spending, saving or paying off debt, the setup module prompts the user for information indicating what portion of the excess the user would spend, save or pay off debt. Then the setup module prompts the user for information indicating how the user would spend the money, the savings goal of the money, or what debts the user would pay down in the manner described above. In this way, the setup module builds a profile of the user and, if the retirement planning system detects excess funds at the end of a period (e.g., at the end of a month), the
system 26 can notify the user of the excess and suggest various ways in which the user may use the funds based on the user profile. - Referring back to
FIG. 4 , after the setup module collects information about the user's preferences for using extra income, the setup module prompts the user for information regarding the user's preferences for receiving a periodic statement (block 416). In this regard, the setup module may ask the user to indicate whether the user would like monthly, quarterly, bi-annually or annual statements showing the user's progress towards his or her retirement goals. The message generator 40 (shown inFIG. 3 ) is configured to send messages in many formats, e.g., paper, SMS, SMTP, facsimile, Universal Resource Locator (URL), to many endpoints, e.g., mail, network printer, SMS/SMTP device, e-mail, or webpage. Accordingly, the setup module is also configured to prompt the user for information indicating the user's preference as to how the user would like to receive periodic statements. - After obtaining the user's preference on how often the user would like to obtain a periodic statement, the setup module computes the amount a non-retired user must put towards his or her retirement assets per period (e.g., per month) in order to meet the user's retirement goals based on the retirement and account data supplied by the user (block 418). Alternatively, for a retired user, the setup module computes a periodic retirement budget based on the user's assets (retirement and non-retirement), the user's life expectancy, the expected rate of return, and the projected inflation rate (block 418). In either case, the setup module will display this figure to the user and ask the user if he or she would like to change any of the underlying data (e.g., the user's retirement goals, expected rate of return).
- After collecting the above information from the user, the setup module creates and stores a record of the user's personal information, account information, retirement data and preferences in the retirement database (block 420). After the user's record of information has been created in the retirement database, the
retirement planning engine 38 is able to track and analyze the user's progress towards his or her retirement goals. If the user wants to change any of the information contained in the retirement database, the user may initiate an update session, which causes the setup module to present the user with the previously entered information and ask the user to indicate how he or she would like to modify the data. Once the user makes the desired modifications, the setup module stores the new information in the user's record of information stored in theretirement planning database 36. - Information transferred between the user and the
setup module 32 can be interfaced through anoperator 18, 19 (e.g., a customer service representative, a licensed broker or a licensed financial advisor) during an activation session or an update session. For example, a licensed broker or financial advisor can engage the user in a discussion about the user's retirement goals and financial resources and obtain information from the user through a telephone call or a face-to-face meeting and enter the appropriate information into thesetup module 32. Similarly, a customer service representative can be contacted by the user in order to assist the user with setting up theretirement planning system 26. - Operation of the retirement planning system shown in
FIGS. 1-3 is illustrated inFIG. 5 . - As shown in
FIG. 5 , after a user has activated thesystem 10, the retirement planning engine 38 (shown inFIG. 3 ) will periodically (e.g., once a month, once a quarter, once a year, etc.) query the personalfinancial data database 27 to obtain data indicating all transactions (i.e., debits and credits) on every user account that were recorded during the period (block 502). - After obtaining data indicating the transactions that were recorded over the period, the
retirement planning engine 38 determines whether the user is retired by looking up the user's retirement data stored in the retirement planning database 36 (decision block 504). - If the retirement data indicates that the user is not retired, the
retirement planning engine 38 computes the net amount deposited into non-retirement and retirement accounts during the period (blocks 506 and 508). The retirement engine determines which accounts are retirement accounts based on information stored about each account in theretirement planning database 36 that was provided by the user in the activation session (or a subsequent update session). In another implementation, theretirement planning engine 38 determines if a user is retired by scanning the user's transaction history for a deposit to a 401(k) account, or an IRA account. If there is a recent deposit (e.g., within the period) in one of these accounts, then theretirement planning engine 38 presumes that the user is not retired. If there is not a deposit, then the retirement planning engine scans that user's transaction history for a payroll deposit. If there is a payroll deposit, then theretirement planning engine 38 presumes that the user is not retired. If there is no payroll deposit, then theretirement planning engine 38 presumes that the user is retired if the user is age 55 or older. Otherwise, theretirement planning engine 38 presumes that the user is not retired, but is unemployed or otherwise not receiving a regular payroll deposit. - After computing the net amount deposited into non-retirement and retirement account during the period, the retirement planning engine checks to ensure that the deposits into the retirement accounts comport with current state and federal tax laws (block 509). In this regard, the retirement planning engine may access the retirement database to determine if the user is eligible to contribute to an IRA given the user's age and current income level. Similarly, the retirement planning engine may track the aggregate amount the user has deposited into tax deferred retirement accounts (e.g., an IRA, Roth IRA or a 401(k) account) to ensure that the user has not deposited more than the maximum contribution amount prescribed by law. If the retirement planning engine determines that the user has reached the maximum limits a tax deferred savings account, the planning engine automatically deposits the funds into to a taxable account.
- After computing the amount that was deposited into non-retirement and retirement accounts during the period, the system determines whether the user has met his or her retirement savings goal for the period (decision block 510). As previously described, the user's savings goal for the period is determined based on the user's retirement data and account data obtained during the setup session (or a subsequent update session).
- If the
retirement planning engine 38 determines that the user has not met his or her periodic retirement savings goal, theretirement planning engine 38 then computes the amount which the user is under the periodic goal (block 512 onFIG. 5B ). - The
retirement engine 38 then retrieves information from theretirement planning database 36 that indicates the aggregate amount by which the user has underfunded or overfunded the user's retirement accounts as of the previous period. For example, a user may be scheduled to have an aggregate of $4,000 saved for retirement after four months (e.g., scheduled to save $1,000 per month), but may have been able to save an average of $1,100 per month, leaving the user's retirement savings plan overfunded by $400 after the fourth month. If this first period theretirement planning engine 38 has tracked the user's retirement savings plan, then the amount by which the user is under or over the periodic goal is recorded in theretirement planning database 36 as the aggregated shortage/overage amount. - After retrieving the user's aggregate shortage/overage from the previous period, the
retirement planning engine 38 computes a new aggregate shortage/overage based on the shortage of the current period (block 516). To continue with the above example, if the user has underfunded his or her retirement accounts by $300 for the period, the user's aggregate overage will be reduced from $400 to $100. After computing the new aggregate shortage/overage, theretirement planning engine 38 updates theretirement planning database 36 with this new amount. - The
retirement planning engine 38 determines whether the user has excess income for the period by netting the debits and credits recorded in the user's non-retirement accounts for the period (decision block 518). If theretirement planning engine 38 determines that the user does not have excess income for the period (and thus no source from which to fund the shortage in retirement savings for the period), theretirement planning engine 38 transmits to themessage generator 40 an indication that the user does not have excess income for the period along with the amount the user has saved for retirement for the period, the amount by which the user was short of the user's periodic retirement savings goal, the total aggregate amount of retirement savings, and the amount the user is over or under the user's aggregate retirement savings goal. Themessage generator 40 assembles this information in a statement that is sent to the user (block 520). - If the
retirement planning engine 38 determines that the user has excess income for the period, theretirement planning engine 38 determines if the excess income for the period is less than or equal to the amount needed to reach the user's periodic retirement savings goal (decision block 522). - If the
retirement planning engine 38 determines that the excess income is less than or equal to the amount needed to reach the periodic retirement savings goal, theretirement planning engine 38 causes the statement generator 40 (shown inFIG. 3 ) to generate an interactive statement recommending that the excess income be applied towards the periodic goal (block 524). An interactive statement is an electronic message that allows the user to submit a response back to the system. An interactive statement may be in the form of an electronic mail message sent to a user's electronic mailbox, an SMS or SMTP message sent to a user's text-messaging device, or a webpage posted to a website that may be accessed by the user. In one implementation, the interactive statement generated by thestatement generator 40 may be an e-mail message that includes the amount the user has saved for retirement for the period, the amount by which the user was short of the user's periodic retirement savings goal, the total aggregate amount of retirement savings, the amount the user is over or under the user's aggregate retirement savings goal, and the amount of excess income for the period. The interactive statement may further include a recommendation to apply the excess income towards the user's periodic retirement savings goal and may provide a hyperlink that the user may click on if the user wants the retirement planning system to transfer the excess income to one or more retirement savings accounts. - If the user indicates that the user would like the system to transfer excess income to one or more retirement savings account, the
retirement planning engine 38 then transfers the excess income to one or more of the user's retirement accounts (block 526). For example, if the user clicks on a hyperlink to a website in an e-mail indicating that the user would like the system to transfer excess income to one or more retirement accounts, the user may be taken to a secure website that asks the user to input the amount of the excess income the user would like transferred as well as an identification of which retirement account or accounts the user would like the funds to be transferred. The website may include a list of each of the user's retirement accounts, how much the user has contributed to each account in over a tax year, and information about the maximum amount, if any, that may be contributed to the retirement accounts in a tax year (e.g., contributions to an IRA account in a tax year are currently capped by law and are not available to persons with adjusted gross income over a specified amount). After the user provides the information about the amount of the excess income to be transferred and the target accounts, theretirement planning engine 38 transfers the funds accordingly and sends the user a confirmation message. - Referring back to decision block 522 in
FIG. 5B , if theretirement planning engine 38 determines that the excess income is greater than the amount needed to reach the periodic retirement savings goal, theretirement planning engine 38 queries theretirement planning database 36 to retrieve information about the user's spending preferences (block 528). Next, theretirement planning engine 38 builds a list of recommendations for spending the excess income above the periodic retirement savings goal based on the information about the user's spending preference retrieved from the retirement planning database 36 (block 530) For example, the user may have indicated in an activation or update session that the user would like to use excess income purchase jewelry and to save for a vacation home. The user may have also indicated in the activation or update session a particular account that the user has earmarked for a vacation home. In this example, theretirement planning engine 38 builds a list of the following recommendations: -
- a. transfer excess income above the amount needed to meet periodic retirement savings goal to the account earmarked for a vacation home purchase;
- b. use excess income to purchase a pair of gold earrings on sale at recommended merchant “A”;
- c. use excess income to purchase a silver necklace on sale at recommended merchant “B”;
- d. use excess income to purchase a gold bracelet on sale at recommend merchant “C”.
Theretirement planning engine 38 builds the list of items for sale from a list of preferred vendors by querying product information provided over the Internet by the vendors according to the amount of excess income any user preference information stored in theretirement planning database 36. For example, theretirement planning system 26 may have extensive information about a user's preference and may have information that indicates not only does the user have a preference to spend excess income on jewelry, but also that the user prefers sterling silver jewelry. The list of recommended vendors for a particular product market may be preprogrammed into the system by a system programmer or it may be specified by the user during an activation or update session.
- After building a list of recommendations, the
retirement planning engine 38 transmits the list to thestatement generator 40, which incorporates the list into an interactive statement that is sent to the user (block 532). In addition to information about the user's retirement savings (e.g., amount the user has saved for retirement for the period, the amount by which the user was short of the user's periodic retirement savings goal, the total aggregate amount of retirement savings, and the amount the user is over or under the user's aggregate retirement savings goal), the interactive statement also notifies the user that the user has excess income and recommends that the user apply the excess income to first meet the periodic retirement savings goal and then use the surplus on one or more of the items on the recommendation list. - As explained above, the user may provide information back to the retirement planning system through the interactive message in order to have the system execute any desired transactions (block 530). For example, suppose the user provides information back to the system commanding the system to use the excess income to meet the user's periodic retirement goal, purchase gold earrings at jeweler “A” and apply the remainder to the account earmarked for a vacation home. In response to receiving this information back from the user, the
retirement planning engine 38 electronically transfers a portion of the excess income sufficient to meet the user's periodic saving goal from one or more of the user's non-retirement accounts to one or more of the user's retirement accounts. The system also automatically purchase the gold earrings by either transferring finds directly to the jeweler, or preferably, charging the earrings on a charge account held by the user (e.g., a Visa or a Mastercard account) and then transferring the purchase amount to the charge account. By making the purchase through a charge account like Visa or Mastercard, the user is able to take advantage of the purchase protections and benefits (e.g., frequently flyer miles) afforded by the charge account. Additionally, if the user does not maintain a balance on the charge account (and thus is not charged interest on purchases), thesystem 26 may hold the purchase funds in an interest bearing account and then transfer the purchase funds to the charge account on the payment due date for the charge account. Thesystem 26 also transfers the remaining excess income into the account earmarked for a vacation home. - Referring back to decision block 510 in
FIG. 5A , if theretirement planning engine 38 determines that the user has met his or her retirement savings goal for the period, theretirement planning engine 38 determines whether there is an aggregate shortage in the user's retirement savings plan (decision block 536 inFIG. 5C ). - If the
retirement planning engine 38 determines that there is not an aggregate shortage in the user's retirement savings plan (i.e., the user is at or above the current savings goal for the user's retirement savings plan), the retirement engine queries theretirement planning database 36 to obtain the user's spending preferences (block 538), builds a list of spending recommendations (block 540), prompts the message generator to generate an interactive statement with spending recommendations (block 542), and executes any transactions commanded by user in response to the interactive statement (block 544), as previously described with respect toblocks - If the
retirement planning engine 38 determines that there is an aggregate shortage in the user's retirement savings plan, theretirement planning engine 38 determines if the excess income is less than or equal to the amount needed to satisfy the shortage (decision block 546). If the amount is less than or equal to the amount needed to make up the shortage, then theretirement planning engine 38 prompts thestatement generator 40 to generate an interactive statement recommending that the excess income be applied towards the user's retirement savings (block 548). If the user responds back to the interactive statement, the system executes any transactions commanded by the user (block 550). - If the
retirement planning engine 38 determines that the excess income is greater than the amount needed to make up the aggregate shortage in the user's retirement saving plan, the retirement engine then queries theretirement planning database 36 to obtain the user's spending preferences (block 552), builds a list of spending recommendations (block 554), prompts the message generator to generate an interactive statement with spending recommendations (block 556), and executes any transactions commanded by user in response to the interactive statement (block 558), as previously described with respect toblocks - Referring back to decision block 504 in
FIG. 5A , if theretirement planning engine 38 determines, based on the user's retirement information, that the user is retired, theretirement planning engine 38 determines if the user has income above the user's retirement budget (decision block 560). As described above, the user's retirement budget is the periodic income stream needed to have the after-tax amount desired by the user for the period. - If the user has income above the user's retirement budget, the retirement engine queries the
retirement planning database 36 to obtain the user's spending preferences (block 562 shown inFIG. 5D ), builds a list of spending recommendations (block 564), prompts the message generator to generate an interactive statement with spending recommendations (block 566), and then executes any transactions commanded by user in response to the interactive statement (block 568), as previously described with respect toblocks retirement planning engine 38 recomputes the user's projected retirement assets. - If the
retirement planning engine 38 determines that the user does not have income above the user's retirement budget (decision block 560 inFIG. 5A ), the retirement engine then determines if the user has spent more than the user's retirement budget (decision block 570 inFIG. 5E ). If the user has not spent more than the budgeted amount (i.e., the user has spent exactly the budgeted amount), thestatement generator 40 generates a periodic statement showing the projected user's retirement assets (block 572). If the user has spent more than the budgeted amount, then theretirement planning engine 38 recomputes the user's projected retirement assets (block 574) and thestatement generator 40 generate a periodic statement showing a projection of the user's retirement assets (block 576). - In one implementation, the retirement planning system is also configured to allow a user to view the user's current progress towards his or her periodic or overall retirement goal at any time by accessing this information over a secure Internet website. The system is also configured to allow a customer service representative, broker or financial advisor to access this information on-line (e.g., through the Internet or an intranet). In this way, a broker or financial advisor is able get a picture of the user's financial resources and spending habits and work to formulate a savings and investment plan tailored for the individual user.
- In another implementation, the message generator is configured to monitor Internet messaging services, such as America On-Line™ instant messaging or Yahoo™ messenger, for a user to sign on under a handle they provide during the activation session or a subsequent update session. When the message generator determines that a user has logged on to the messaging service, the message generator opens a chat session with the user to provide the user with automated reminders about saving for retirement, messages about the user's savings for the current period or in the aggregate, or other information relating to the user's retirement planning.
- Other embodiments are within the scope of the following claims. For example, an asset planning and tracking system, e.g.,
retirement planning system 26 shown inFIGS. 2-3 , may plans for and tracks progress towards any savings goal (e.g., a house renovation project, a wedding reception, purchase of a second home, a child's college education, or a vacation) and analyzes consumption once the user begins drawing upon the assets. Additionally, an asset planning and tracking system may track other “assets” than financial assets such as frequent flyer miles. In this implementation, a frequently flyer tracking system may track a user's frequent flyer miles against a goal (e.g., sufficient miles for roundtrip tickets to Hawaii for a family of four in five years) and may periodically apprise the user of his progress towards the goal and make recommendations as to how to use excess miles.
Claims (42)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/740,159 US8527382B2 (en) | 2003-12-17 | 2003-12-17 | Asset planning and tracking |
EP04814655A EP1695283A2 (en) | 2003-12-17 | 2004-12-17 | Asset planning and tracking |
PCT/US2004/042502 WO2005059799A2 (en) | 2003-12-17 | 2004-12-17 | Asset planning and tracking |
CNA2004800376404A CN1894717A (en) | 2003-12-17 | 2004-12-17 | Asset planning and tracking |
US13/961,580 US8676687B2 (en) | 2003-12-17 | 2013-08-07 | Asset planning and tracking |
US14/155,115 US20140129402A1 (en) | 2003-12-17 | 2014-01-14 | Asset planning and tracking |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/740,159 US8527382B2 (en) | 2003-12-17 | 2003-12-17 | Asset planning and tracking |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/961,580 Continuation US8676687B2 (en) | 2003-12-17 | 2013-08-07 | Asset planning and tracking |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050137953A1 true US20050137953A1 (en) | 2005-06-23 |
US8527382B2 US8527382B2 (en) | 2013-09-03 |
Family
ID=34677807
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/740,159 Active 2031-07-29 US8527382B2 (en) | 2003-12-17 | 2003-12-17 | Asset planning and tracking |
US13/961,580 Expired - Lifetime US8676687B2 (en) | 2003-12-17 | 2013-08-07 | Asset planning and tracking |
US14/155,115 Abandoned US20140129402A1 (en) | 2003-12-17 | 2014-01-14 | Asset planning and tracking |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/961,580 Expired - Lifetime US8676687B2 (en) | 2003-12-17 | 2013-08-07 | Asset planning and tracking |
US14/155,115 Abandoned US20140129402A1 (en) | 2003-12-17 | 2014-01-14 | Asset planning and tracking |
Country Status (4)
Country | Link |
---|---|
US (3) | US8527382B2 (en) |
EP (1) | EP1695283A2 (en) |
CN (1) | CN1894717A (en) |
WO (1) | WO2005059799A2 (en) |
Cited By (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060020533A1 (en) * | 2004-07-23 | 2006-01-26 | Lee Stephon D | Computer-implemented program for budgeting and saving |
US20060080200A1 (en) * | 2000-04-07 | 2006-04-13 | Ashton David M | System and method for benefit plan administration |
US20060136595A1 (en) * | 1998-12-08 | 2006-06-22 | Ramakrishna Satyavolu | Network-based verification and fraud-prevention system |
US20070061237A1 (en) * | 2005-09-15 | 2007-03-15 | Robert Merton | Graphical user interface for retirement income planning |
US20070198382A1 (en) * | 2006-02-17 | 2007-08-23 | Ferrari Michael R | Method of saving for a time delayed purchase |
US20090063198A1 (en) * | 2007-08-29 | 2009-03-05 | Yung-Sung Chien | Investment insurance auctioning method and system thereof |
US20090063332A1 (en) * | 2007-08-29 | 2009-03-05 | Wachovia Corporation | Flexible automatic savings programs |
US20090192947A1 (en) * | 2008-01-24 | 2009-07-30 | Fmr Llc | Generating a Savings Plan |
WO2009131471A1 (en) * | 2008-04-22 | 2009-10-29 | Aliveware Limited | Practice manager |
WO2009132285A1 (en) * | 2008-04-24 | 2009-10-29 | Kiboo Licensing, Llc | Financial lifestyle navigator and banking system |
US20090271287A1 (en) * | 2008-04-24 | 2009-10-29 | KIBOO LICENSING, LLC a Delaware limited liability company | Financial lifestyle navigator and banking system |
US7617138B1 (en) | 2004-05-28 | 2009-11-10 | Towers Perrin Forster & Crosby, Inc. | Estimating financial valuation of benefit plans |
US20100094740A1 (en) * | 2008-10-14 | 2010-04-15 | Cashlocale.Com Inc. | Financial planning and plan execution |
US20100121780A1 (en) * | 2008-05-05 | 2010-05-13 | Ian Sheridan | System and method for generating a transactionable multimedia financial planning statement |
US20100138341A1 (en) * | 2008-12-02 | 2010-06-03 | Leah Solomon | Method and system for saving money with a group of mobile devices |
US7835963B1 (en) | 2008-03-12 | 2010-11-16 | United Services Automobile Association (Usaa) | Systems and methods for retirement asset distribution |
US20100306126A1 (en) * | 2009-05-29 | 2010-12-02 | Ameriprise Financial, Inc. | Management of goals and recommendations |
US7895102B1 (en) * | 2008-02-29 | 2011-02-22 | United Services Automobile Association (Usaa) | Systems and methods for financial plan benchmarking |
US20110106691A1 (en) * | 2009-06-03 | 2011-05-05 | Clark D Sean | Systems and methods for tracking financial information |
US20110112985A1 (en) * | 2009-11-06 | 2011-05-12 | Kocmond Peter George | Method and system for generating a financial plan score |
US8165939B1 (en) | 2007-04-23 | 2012-04-24 | Reass Richard M | Method of settling a real estate transaction and system implementing the method |
US8200554B1 (en) * | 2008-12-18 | 2012-06-12 | Intuit Inc. | Graduated automatic savings |
US8296206B1 (en) * | 2010-04-30 | 2012-10-23 | Intuit Inc. | Method and system for providing intelligent targeted budgeting using financial transaction data from similarly situated individuals |
US8341057B1 (en) | 2007-06-22 | 2012-12-25 | Capital One Financial Corporation | System and method of analyzing and monitoring a customer's financial condition |
US8380623B1 (en) | 2008-02-08 | 2013-02-19 | The Pnc Financial Services Group, Inc. | Systems and methods for enabling financial savings |
US8620788B2 (en) * | 2012-03-09 | 2013-12-31 | Hartford Fire Insurance Company | System and method for dynamic financial account management |
US8630877B1 (en) * | 2009-07-17 | 2014-01-14 | United Services Automobile Association (Usaa) | Systems and methods for retirement gap insurance |
US8639622B1 (en) | 2009-08-31 | 2014-01-28 | Wells Fargo Bank, N.A. | Budget management system and method |
US8671054B2 (en) * | 2012-05-18 | 2014-03-11 | Jpmorgan Chase Bank, N.A. | Dynamic management and netting of transactions using executable rules |
US20140188674A1 (en) * | 2013-01-03 | 2014-07-03 | Debt Lean, SL | Method, system and computer program for providing multilateral debt netting and payment services for enterprises |
US20160350860A1 (en) * | 2015-05-27 | 2016-12-01 | Bank Of America Corporation | Modifying an estimated financial plan |
US20180040062A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | Resource tracking and utilization system |
US20180040072A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | System for analyzing historical events to determine potential catalysts and automatically generating and implementing mitigation |
US20180240190A1 (en) * | 2017-02-17 | 2018-08-23 | Katie Lynn Schumacher | Delayed reward savings system |
US20180341378A1 (en) * | 2015-11-25 | 2018-11-29 | Supered Pty Ltd. | Computer-implemented frameworks and methodologies configured to enable delivery of content and/or user interface functionality based on monitoring of activity in a user interface environment and/or control access to services delivered in an online environment responsive to operation of a risk assessment protocol |
US10249003B2 (en) | 2015-03-20 | 2019-04-02 | Bank Of America Corporation | System for sharing retirement scores between social groups of customers |
US10334026B2 (en) | 2016-08-08 | 2019-06-25 | Bank Of America Corporation | Resource assignment system |
US11748821B1 (en) * | 2016-07-28 | 2023-09-05 | United Services Automobile Association (Usaa) | Systems and methods for managing and reducing spending |
US11861689B1 (en) | 2007-11-28 | 2024-01-02 | Wells Fargo Bank, N.A. | Systems for data management and financial budgeting |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100250420A1 (en) * | 2009-03-30 | 2010-09-30 | Bank Of America Corporation | Systems and methods for budget guardrails |
CN102708467A (en) * | 2012-05-22 | 2012-10-03 | 苏州奇可思信息科技有限公司 | Personal financial management system |
US20140258179A1 (en) * | 2013-03-11 | 2014-09-11 | Bank Of America Corporation | Open retirement account |
CA2865617C (en) | 2013-09-30 | 2020-07-14 | The Toronto-Dominion Bank | Systems and methods for administering investment portfolios based on transaction data |
US9424572B2 (en) | 2014-03-04 | 2016-08-23 | Bank Of America Corporation | Online banking digital wallet management |
US20150379488A1 (en) * | 2014-06-27 | 2015-12-31 | Clear Path Financial | Automated proactive electronic resource allocation processing system |
US10210583B2 (en) | 2015-01-19 | 2019-02-19 | Elena A. Colquitt | Integrated automated bill and budget reconciliation, cash flow allocation and payment software system |
US10032223B2 (en) | 2015-03-20 | 2018-07-24 | Bank Of America Corporation | System for account linking and future event integration into retirement score calculation |
US9830660B2 (en) | 2015-03-20 | 2017-11-28 | Bank Of America Corporation | System for augmenting a retirement score with health information |
US10019760B2 (en) | 2015-03-20 | 2018-07-10 | Bank Of America Corporation | System for utilizing a retirement score to receive benefits |
US20160350864A1 (en) * | 2015-05-27 | 2016-12-01 | Bank Of America Corporation | Goal guarantee system |
US10013714B2 (en) | 2015-09-11 | 2018-07-03 | Bank Of America Corporation | System for simulation and implementation of dynamic state-dependent resource reconfiguration |
US10249002B2 (en) | 2015-09-11 | 2019-04-02 | Bank Of America Corporation | System for dynamic visualization of individualized consumption across shared resource allocation structure |
US10127551B2 (en) | 2015-09-11 | 2018-11-13 | Bank Of America Corporation | System for modeling and implementing event-responsive resource allocation structures |
WO2017173021A1 (en) * | 2016-03-30 | 2017-10-05 | Mastercard International Incorporated | Method and system for digital money management for a payment account |
US20170323272A1 (en) | 2016-05-09 | 2017-11-09 | Bank Of America Corporation | System environment for user-specific program aggregation and non-collocated third party system extraction and deployment |
US10915959B2 (en) * | 2016-10-18 | 2021-02-09 | Jpmorgan Chase Bank, N.A. | System and method for spend management and investment of funds |
US10825104B1 (en) | 2017-02-16 | 2020-11-03 | Intuit Inc. | Method and system for integrating invoice related financial transaction data into a personal financial management and bill payment system and using the payment source to more accurately identify and categorize tax related financial transactions using the payment method |
US10524165B2 (en) | 2017-06-22 | 2019-12-31 | Bank Of America Corporation | Dynamic utilization of alternative resources based on token association |
US10313480B2 (en) | 2017-06-22 | 2019-06-04 | Bank Of America Corporation | Data transmission between networked resources |
US10511692B2 (en) | 2017-06-22 | 2019-12-17 | Bank Of America Corporation | Data transmission to a networked resource based on contextual information |
US20190066067A1 (en) * | 2017-08-29 | 2019-02-28 | Walmart Apollo, Llc | System and method for collaborative sharing of digital currency |
CN108090749A (en) * | 2018-02-08 | 2018-05-29 | 陈丽娜 | A kind of financial consultant's intelligent management |
US11748814B2 (en) | 2018-05-21 | 2023-09-05 | Empower Annuity Insurance Company Of America | Planning engine for a financial planning system |
US20190355055A1 (en) | 2018-05-21 | 2019-11-21 | Great-West Life & Annuity Insurance Company | Graphical user interface including dynamic generation of savings option selectors for a financial planning system |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5947526A (en) * | 1997-04-15 | 1999-09-07 | Budget Master, Llc | Personal financial tracking system and method |
US6631358B1 (en) * | 1999-11-11 | 2003-10-07 | John W. L. Ogilvie | Promoting savings by facilitating incremental commitments made with credit card and other consumer-initiated transactions |
US20040054610A1 (en) * | 2001-11-28 | 2004-03-18 | Monetaire | Monetaire wealth management platform |
US20040254835A1 (en) * | 2000-11-06 | 2004-12-16 | American Express Travel Related Services Company, Inc. | Pay yourself first budgeting |
US20040267651A1 (en) * | 2001-07-31 | 2004-12-30 | American Express Travel Related Services Company, Inc. | Portfolio integration module for providing financial planning and advice |
US20090055327A1 (en) * | 1997-12-02 | 2009-02-26 | Financial Engines, Inc. | Financial goal planning and analysis system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4588192A (en) | 1983-09-15 | 1986-05-13 | Pedro Laborde | Financial futures game |
FR2605431B1 (en) | 1986-10-16 | 1988-12-02 | France Etat | ELECTRONIC PAYMENT METHOD USING A MEMORY CARD |
US6430542B1 (en) | 1998-08-26 | 2002-08-06 | American Express Financial Corporation | Computer-implemented program for financial planning and advice system |
-
2003
- 2003-12-17 US US10/740,159 patent/US8527382B2/en active Active
-
2004
- 2004-12-17 EP EP04814655A patent/EP1695283A2/en not_active Withdrawn
- 2004-12-17 WO PCT/US2004/042502 patent/WO2005059799A2/en active Application Filing
- 2004-12-17 CN CNA2004800376404A patent/CN1894717A/en active Pending
-
2013
- 2013-08-07 US US13/961,580 patent/US8676687B2/en not_active Expired - Lifetime
-
2014
- 2014-01-14 US US14/155,115 patent/US20140129402A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5947526A (en) * | 1997-04-15 | 1999-09-07 | Budget Master, Llc | Personal financial tracking system and method |
US20090055327A1 (en) * | 1997-12-02 | 2009-02-26 | Financial Engines, Inc. | Financial goal planning and analysis system |
US6631358B1 (en) * | 1999-11-11 | 2003-10-07 | John W. L. Ogilvie | Promoting savings by facilitating incremental commitments made with credit card and other consumer-initiated transactions |
US20040254835A1 (en) * | 2000-11-06 | 2004-12-16 | American Express Travel Related Services Company, Inc. | Pay yourself first budgeting |
US20040267651A1 (en) * | 2001-07-31 | 2004-12-30 | American Express Travel Related Services Company, Inc. | Portfolio integration module for providing financial planning and advice |
US20040054610A1 (en) * | 2001-11-28 | 2004-03-18 | Monetaire | Monetaire wealth management platform |
Cited By (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060136595A1 (en) * | 1998-12-08 | 2006-06-22 | Ramakrishna Satyavolu | Network-based verification and fraud-prevention system |
US20060080200A1 (en) * | 2000-04-07 | 2006-04-13 | Ashton David M | System and method for benefit plan administration |
US7617138B1 (en) | 2004-05-28 | 2009-11-10 | Towers Perrin Forster & Crosby, Inc. | Estimating financial valuation of benefit plans |
US20060020533A1 (en) * | 2004-07-23 | 2006-01-26 | Lee Stephon D | Computer-implemented program for budgeting and saving |
US20070061237A1 (en) * | 2005-09-15 | 2007-03-15 | Robert Merton | Graphical user interface for retirement income planning |
WO2007035528A2 (en) * | 2005-09-15 | 2007-03-29 | Integrated Finance Limited | Graphical user interface for retirement income planning |
WO2007035528A3 (en) * | 2005-09-15 | 2007-11-01 | Integrated Finance Ltd | Graphical user interface for retirement income planning |
US7711619B2 (en) | 2005-09-15 | 2010-05-04 | Integrated Finance Limited | Graphical user interface for retirement income planning |
US20070198382A1 (en) * | 2006-02-17 | 2007-08-23 | Ferrari Michael R | Method of saving for a time delayed purchase |
US8165939B1 (en) | 2007-04-23 | 2012-04-24 | Reass Richard M | Method of settling a real estate transaction and system implementing the method |
US8341057B1 (en) | 2007-06-22 | 2012-12-25 | Capital One Financial Corporation | System and method of analyzing and monitoring a customer's financial condition |
US8086475B2 (en) * | 2007-08-29 | 2011-12-27 | Shacom.Com Inc. | Investment insurance auctioning method and system thereof |
US20090063332A1 (en) * | 2007-08-29 | 2009-03-05 | Wachovia Corporation | Flexible automatic savings programs |
US20090063198A1 (en) * | 2007-08-29 | 2009-03-05 | Yung-Sung Chien | Investment insurance auctioning method and system thereof |
US11861689B1 (en) | 2007-11-28 | 2024-01-02 | Wells Fargo Bank, N.A. | Systems for data management and financial budgeting |
US20090192947A1 (en) * | 2008-01-24 | 2009-07-30 | Fmr Llc | Generating a Savings Plan |
US8380623B1 (en) | 2008-02-08 | 2013-02-19 | The Pnc Financial Services Group, Inc. | Systems and methods for enabling financial savings |
US10282780B1 (en) | 2008-02-08 | 2019-05-07 | The Pnc Financial Services Group, Inc. | Systems and methods for scheduling and tracking account activity |
US8423452B1 (en) | 2008-02-08 | 2013-04-16 | The Pnc Financial Services Group, Inc. | Systems and methods for scheduling and tracking bank account activity |
US7895102B1 (en) * | 2008-02-29 | 2011-02-22 | United Services Automobile Association (Usaa) | Systems and methods for financial plan benchmarking |
US7835963B1 (en) | 2008-03-12 | 2010-11-16 | United Services Automobile Association (Usaa) | Systems and methods for retirement asset distribution |
US8751345B1 (en) | 2008-03-12 | 2014-06-10 | United Services Automobile Association (Usaa) | Systems and methods for retirement asset distribution |
US8015090B1 (en) * | 2008-03-12 | 2011-09-06 | United Services Automobile Association (Usaa) | Systems and methods for retirement asset distribution |
WO2009131471A1 (en) * | 2008-04-22 | 2009-10-29 | Aliveware Limited | Practice manager |
US20090271287A1 (en) * | 2008-04-24 | 2009-10-29 | KIBOO LICENSING, LLC a Delaware limited liability company | Financial lifestyle navigator and banking system |
WO2009132285A1 (en) * | 2008-04-24 | 2009-10-29 | Kiboo Licensing, Llc | Financial lifestyle navigator and banking system |
US20100121780A1 (en) * | 2008-05-05 | 2010-05-13 | Ian Sheridan | System and method for generating a transactionable multimedia financial planning statement |
US8200562B2 (en) | 2008-05-05 | 2012-06-12 | Massachusetts Mutual Life Insurance Company | System and method for generating a transactionable multimedia financial planning statement |
US20100094740A1 (en) * | 2008-10-14 | 2010-04-15 | Cashlocale.Com Inc. | Financial planning and plan execution |
US8478691B2 (en) | 2008-12-02 | 2013-07-02 | Savingshero, LLC | Method and system for impulse savings |
US20100138341A1 (en) * | 2008-12-02 | 2010-06-03 | Leah Solomon | Method and system for saving money with a group of mobile devices |
US8090656B2 (en) | 2008-12-02 | 2012-01-03 | Leah Solomon | Method and system for saving money with a group of mobile devices |
US8200554B1 (en) * | 2008-12-18 | 2012-06-12 | Intuit Inc. | Graduated automatic savings |
US20100306126A1 (en) * | 2009-05-29 | 2010-12-02 | Ameriprise Financial, Inc. | Management of goals and recommendations |
US20120197818A1 (en) * | 2009-05-29 | 2012-08-02 | Ameriprise Financial, Inc. | Management of goals and recommendations |
US8190502B2 (en) * | 2009-05-29 | 2012-05-29 | Ameriprise Financial, Inc. | Management of goals and recommendations |
US10249001B2 (en) * | 2009-05-29 | 2019-04-02 | Ameriprise, Financial, Inc. | Management of goals and recommendations |
US8635142B2 (en) * | 2009-05-29 | 2014-01-21 | Ameriprise Financial, Inc. | Management of goals and recommendations |
US20140108298A1 (en) * | 2009-05-29 | 2014-04-17 | Ameriprise Financial Center | Management of Goals and Recommendations |
US20110106691A1 (en) * | 2009-06-03 | 2011-05-05 | Clark D Sean | Systems and methods for tracking financial information |
US8630877B1 (en) * | 2009-07-17 | 2014-01-14 | United Services Automobile Association (Usaa) | Systems and methods for retirement gap insurance |
US8639622B1 (en) | 2009-08-31 | 2014-01-28 | Wells Fargo Bank, N.A. | Budget management system and method |
US8719132B1 (en) | 2009-08-31 | 2014-05-06 | Wells Fargo Bank, N.A. | Financial management system and method with debt management |
US11250390B1 (en) | 2009-08-31 | 2022-02-15 | Wells Fargo Bank, N.A. | Financial management system and method with customizable user interface |
US10810660B1 (en) * | 2009-08-31 | 2020-10-20 | Wells Fargo Bank, N.A. | Financial management system and method with retirement planning |
US10460379B1 (en) | 2009-08-31 | 2019-10-29 | Wells Fargo Bank, N.A. | Financial management system and method with customizable user interface |
US20110112985A1 (en) * | 2009-11-06 | 2011-05-12 | Kocmond Peter George | Method and system for generating a financial plan score |
US8296206B1 (en) * | 2010-04-30 | 2012-10-23 | Intuit Inc. | Method and system for providing intelligent targeted budgeting using financial transaction data from similarly situated individuals |
US8620788B2 (en) * | 2012-03-09 | 2013-12-31 | Hartford Fire Insurance Company | System and method for dynamic financial account management |
US8909552B2 (en) * | 2012-05-18 | 2014-12-09 | Jpmorgan Chase Bank, N.A. | Dynamic management and netting of transactions using executable rules |
US20150066714A1 (en) * | 2012-05-18 | 2015-03-05 | Jpmorgan Chase Bank, N.A. | Dynamic management and netting of transactions using executable rules |
US8671054B2 (en) * | 2012-05-18 | 2014-03-11 | Jpmorgan Chase Bank, N.A. | Dynamic management and netting of transactions using executable rules |
US20140136404A1 (en) * | 2012-05-18 | 2014-05-15 | Jpmorgan Chase Bank, N.A. | Dynamic Management and Netting of Transactions Using Executable Rules |
US20140188674A1 (en) * | 2013-01-03 | 2014-07-03 | Debt Lean, SL | Method, system and computer program for providing multilateral debt netting and payment services for enterprises |
US10643283B2 (en) | 2015-03-20 | 2020-05-05 | Bank Of America Corporation | System for sharing retirement scores between social groups of customers |
US10249003B2 (en) | 2015-03-20 | 2019-04-02 | Bank Of America Corporation | System for sharing retirement scores between social groups of customers |
US20160350860A1 (en) * | 2015-05-27 | 2016-12-01 | Bank Of America Corporation | Modifying an estimated financial plan |
US20180341378A1 (en) * | 2015-11-25 | 2018-11-29 | Supered Pty Ltd. | Computer-implemented frameworks and methodologies configured to enable delivery of content and/or user interface functionality based on monitoring of activity in a user interface environment and/or control access to services delivered in an online environment responsive to operation of a risk assessment protocol |
US11748821B1 (en) * | 2016-07-28 | 2023-09-05 | United Services Automobile Association (Usaa) | Systems and methods for managing and reducing spending |
US20180040072A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | System for analyzing historical events to determine potential catalysts and automatically generating and implementing mitigation |
US10438296B2 (en) * | 2016-08-08 | 2019-10-08 | Bank Of America Corporation | System for analyzing historical events to determine potential catalysts and automatically generating and implementing mitigation |
US20180040062A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | Resource tracking and utilization system |
US10334026B2 (en) | 2016-08-08 | 2019-06-25 | Bank Of America Corporation | Resource assignment system |
US20180240190A1 (en) * | 2017-02-17 | 2018-08-23 | Katie Lynn Schumacher | Delayed reward savings system |
Also Published As
Publication number | Publication date |
---|---|
CN1894717A (en) | 2007-01-10 |
WO2005059799A2 (en) | 2005-06-30 |
WO2005059799A3 (en) | 2006-05-18 |
US20140129402A1 (en) | 2014-05-08 |
US8676687B2 (en) | 2014-03-18 |
US20130325751A1 (en) | 2013-12-05 |
US8527382B2 (en) | 2013-09-03 |
EP1695283A2 (en) | 2006-08-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8676687B2 (en) | Asset planning and tracking | |
AU689690B2 (en) | Computer system for managing client financial accounts with overdraft protection | |
US8812379B2 (en) | Method and system balancing net savings, resources and claims into retirement | |
US7165044B1 (en) | Investment portfolio tracking system and method | |
US7877320B1 (en) | System and method for tracking and facilitating analysis of variance and recourse transactions | |
US7383218B1 (en) | Method and system for integrating investment advice with financial account statement information | |
AU716769B1 (en) | Application apparatus and method | |
US20050154662A1 (en) | Asset allocation, rebalancing, and investment management system | |
US20080270304A1 (en) | Funds transfer system and method | |
US20070038544A1 (en) | Method and apparatus for financial investment advice available to a host of users over a public network | |
US20070005461A1 (en) | Business tax organizing method and system | |
US20040148248A1 (en) | Secondary transfers of restricted interests | |
JP2002507015A (en) | Method and apparatus for enabling individuals or small investors to cost effectively build and manage portfolios of securities or other assets or liabilities | |
US8438108B1 (en) | System and method for transferring mortgage loan servicing rights | |
US20090248555A1 (en) | System and Method for Third Party Payment Processing of Credit Cards | |
EP1234266A2 (en) | Method and apparatus for aggregated securities brokerage service | |
US20050091133A1 (en) | A System and method for creating a capitalization table of a company | |
JP2002329074A (en) | Derivative dealing processing method and its system | |
JP2007048013A (en) | Privately placed bond fund operation processor and private placed bond fund operation processing method, and privately placed bond fund operation processing program | |
US20230124577A1 (en) | Automated exchange for services using service time units | |
US7716105B1 (en) | Brokerage management system and method | |
WO2005048049A2 (en) | Asset allocation, rebalancing, and investment management system | |
Melka | Determinants of Diffusion of Online Payment Systems in Addis Ababa | |
Kyaw | INFLUENCING FACTORS ON CUSTOMER PERCEPTION OF INTERNET BANKING | |
Njagi | Innovations Brought About by International Trade in the Service Industry in Kenya (a Case Study of Banking Sector) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FMR CORP., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCDONOUGH, JOHN;ELTERICH, STEVE;REEL/FRAME:015319/0925 Effective date: 20040116 |
|
AS | Assignment |
Owner name: FMR LLC, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:FMR CORP.;REEL/FRAME:021221/0180 Effective date: 20070927 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |