RECOMMENDATIONS

SUMMARY

[0001 ] Embodiments of the present invention are directed to computerized systems, methods and articles for determining and providing tax

recommendations for a taxpayer to a user, and more particularly to systems, methods and articles for determining and providing tax recommendation for a taxpayer to a user utilizing a tax preparation system.

[0002] The embodiments of the present invention may be implemented on and/or utilizing a tax return preparation system, or components thereof, comprising a tax preparation software application executing on a computing device. The tax return preparation system may operate on a new construct in which tax rules and the calculations based thereon are established in declarative data-structures, namely, completeness graph(s) and tax calculation graph(s). The tax calculation graph(s) comprise a plurality of nodes including input nodes, functional nodes, and function nodes which represent the tax operation used to perform a tax calculation in accordance with the applicable tax code and/or tax rules. The tax calculation graph(s) are also configured with a plurality of calculation paths wherein each calculation path connects a plurality of nodes which are data dependent such that a node is connected to another node if the node depends on the other node. Use of these data-structures permits the user interface to be loosely connected or even divorced from the tax calculation engine and the data used in the tax calculations. As used herein, the terms "engine," "module," and "element" are structural terms referring to a respective software application installed on a suitable hardware implementation, as would be known by those of ordinary skill in the art. These terms are not used as "nonce" words for the purpose of mean-plus-function claim elements. Tax calculations are dynamically calculated based on tax-related data that is input from a user, derived from sourced data, or estimated. A smart tax logic agent running on a set of rules can review current run time data and evaluate missing tax data necessary to prepare and complete a tax return. The tax logic agent proposes suggested questions to be asked to a user to fill in missing blanks. This process can be continued until completeness of all tax topics has occurred. A completed tax return (e.g., a printed tax return or an electronic tax return) can then be electronically prepared and filed (electronically and/or in paper form) with respect to the relevant taxing jurisdictions.

[0003] In another aspect of the tax return preparation system, the system is configured to operate the computing device to establish a connection to a data store configured to store user-specific tax data therein. The computing device executes a tax calculation engine configured to read and write tax calculation data to and from the shared data store, the tax calculation engine using one or more of the tax calculation graphs specific to particular tax topics. The computing device executes a tax logic agent, the tax logic agent reading from the shared data store and a plurality of decision tables collectively representing a completion graph for computing tax liability or a portion thereof, the tax logic agent outputting one or more suggestions for missing tax data based on an entry in one of the plurality of decision tables. The computing device executes a user interface manager configured to receive the one or more suggestions and present to a user one or more questions based on the one or more suggestions via a user interface, wherein a user response to the one or more questions is input to the shared data store. The user interface manager is configured to generate and display a question screen to the user. The question screen includes a question for the user requesting tax data for a taxpayer and is also configured to receive the tax data from the user in the form of input from the user. The user interface manager which receives the suggestion(s) selects one or more suggested questions to be presented to a user. Alternatively, the user interface manager may ignore the suggestion(s) and present a different question or prompt to the user.

[0004] In the event that all tax topics are covered, the tax logic agent, instead of outputting one or more suggestions for missing tax data may output a "done" instruction to the user interface manager. The computing device may then prepare a tax return for the taxpayer based on the data in the shared data store. The tax return may be a conventional paper-based return or, alternatively, the tax return may be an electronic tax return which can then be e-filed.

[0005] In one embodiment of the present invention, the tax preparation system is further configured to determine tax recommendations for the taxpayer. The present invention does not include any strategy for reducing, avoiding, or deferring tax liability, but instead provides tax recommendations to a user which the user may or may not implement. As such, the invention only provides advice and does not in any way limit the use of any tax strategy by any taxpayer or tax advisor. Indeed, any taxpayer or tax advisor would be free to use any of the tax recommendations provided by the present invention.

[0006] The tax preparation software application further comprises a

recommendation engine. The recommendation engine is configured to analyze a tax calculation graph calculated based on tax data for a taxpayer and determine one or more tax variables which can affect the tax result (e.g., total tax owed, the amount of tax payment remaining, or refund) of the taxpayer. For example, the recommendation engine may analyze the tax calculation graph by traversing the calculation paths of the tax calculation graph and identify input nodes on the graph which can affect the tax result of the taxpayer. As an example, the recommendation engine may determine that the taxpayer may reduce its taxes owed by increasing retirement contributions, and identify a retirement

contribution input node (e.g., 401 (k) contribution) as a tax variable which can affect the tax result of the taxpayer.

[0007] The recommendation engine is further configured to analyze the identified tax variables to determine whether each tax variable is a taxpayer controllable variable. As an example, some tax variables are impossible or impracticable for a taxpayer to control, such as age, birth date, social security number, or disabilities. The recommendation engine may utilize a controllability model relating each tax variable to a level of tax payer controllability to determine whether a tax variable is controllable by the taxpayer, such as a heuristic graph or chart. For instance, the controllability model may be generated by human analysis, computer analysis of data, or a combination of both.

[0008] The recommendation engine is also configured to execute the tax calculation engine to calculate the calculation graph by varying the taxpayer controllable variables to determine an effect on the tax result. This may be done by varying one taxpayer controllable variable up and down around a known or estimated value while keeping the other variables constant, and determining the affect on the tax result. This can be repeated for each taxpayer controllable variable.

[0009] In another aspect of the present invention, the system may be configured to allow the user to select the taxpayer controllable variables of interest and/or predict how much each such tax variable will change. The system is configured to display to the user the taxpayer controllable variables determined by analyzing the calculated tax calculation graph and requests the user to select one or more of the taxpayer controllable variables. The system may also prompt the user to provide a change estimate or prediction of how much each taxpayer controller variables will change. The system receives the selections and/or estimates from the user. The recommendation engine then utilizes only the taxpayer controllable variables selected by the user in executing the tax calculation engine to calculate the tax calculation graph by varying the taxpayer controllable variables to determine an effect on the tax result by varying the taxpayer controllable variables. If provided, the recommendation engine also utilizes the change estimates in determining the effect on the tax result. [0010] In another aspect, the tax preparation system is configured to provide the tax recommendations to a user. The tax preparation system is configured to generate a tax recommendation item for each of the tax recommendations. Each of the tax recommendation items includes its respective tax recommendation, meta data, a recommendation excerpt, and a confidence score indicating a measure of how likely the tax recommendation is to be implemented by to the taxpayer.

[001 1 ] The recommendation engine then provides the tax recommendation items to the interface manager. The user interface manager may further comprises a recommendation processing element. The recommendation processing element generates a user interface presentation using the

recommendation items. The system then displays the user interface

presentation to the user.

[0012] In still another aspect, the tax preparation system may be configured to provide recurring, updated recommendations to the user, such as when the tax situation of the taxpayer changes and/or when the tax rules change. The tax preparation system further comprises a recommendation service for providing the recurring, updated recommendations to the user and/or a recommendation database for storing the tax recommendations. After determining the one or more tax recommendations and generating the tax recommendation items for each tax recommendation, as described above, the recommendation engine provides the tax recommendation items to the tax recommendation database which stores the tax recommendation items. Then, the recommendation service accesses the tax recommendations from the recommendation database and generates a user interface presentation. The recommendation service then dispatches the tax recommendations to the user, such as by displaying the user interface presentation to the user. In additional aspects, the tax preparation system updates the tax recommendations based upon receiving updated tax data regarding the taxpayer and/or new tax rules. For example, the system may receive feedback regarding the taxpayer implementing one or more of the tax recommendations previously provided to the user. The recommendation engine then determines updated tax recommendations and generates updated tax recommendation items for each updated tax recommendation based on the updated tax data and/or new tax rules.

[0013] In still another aspect, the system, including the user interface manager and/or the recommendation service, may also be configured to provide the tax recommendations to the user in a manner in which the user can adjust the values for the taxpayer controllable variables and obtain the tax result for the adjusted values. The system provide the tax recommendations to the user in the form of one or more adjustable input value controls in which each input value control is configured to allow the user to adjust an input value for a respective taxpayer controllable variable. Then, the recommendation engine receives the adjusted input value for one or more of the taxpayer controllable variables based on the user adjusting the one or more input value controls. The tax calculation engine calculates the tax calculation graph using the adjusted values for the taxpayer controllable variables resulting in a modified tax results and the system provides the modified tax result to the user.

[0014] Another embodiment of the present invention is directed to computer- implemented methods for providing tax recommendations for a taxpayer. For example, the method may include, a tax preparation system, same or similar to that described above, executing the recommendation engine to determine one or more tax recommendations and generating a tax recommendation item for each tax recommendation. The recommendation engine provides the tax

recommendation items to the user interface manager. The user interface manager processes the tax recommendation items and generates a user interface presentation for displaying the recommendations to the user. The tax preparation system then displays the user interface presentation to the user.

[0015] In additional aspects of the present invention, the computer- implemented method may also include any of the additional aspects described herein for the system for providing tax recommendations for a taxpayer.

[0016] Another embodiment of the present invention is directed to an article of manufacture comprising a non-transitory computer readable medium embodying instructions executable by a computer to execute a process according to any of the method embodiments of the present invention for providing tax

recommendations for a taxpayer. For instance, the non-transitory computer readable medium embodying instructions executable by a computer may be configured to execute a process comprising: a tax preparation system, same or similar to that described above, executing the recommendation engine to determine one or more tax recommendations and generating a tax recommendation item for each tax recommendation. The recommendation engine provides the tax recommendation items to the user interface manager. The user interface manager processes the tax recommendation items and generates a user interface presentation for displaying the recommendations to the user. The tax preparation system then displays the user interface

presentation to the user.

[0017] In additional aspects, the article of manufacture may be further configured according to the additional aspects described herein for the system and/or method for determining tax recommendations for a taxpayer.

[0018] It is understood that the steps of the methods and processes of the present invention are not required to be performed in the order as shown in the figures or as described, but can be performed in any order that accomplishes the intended purpose of the methods and processes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG. 1 schematically illustrates how tax legislation/tax rules are parsed and represented by a completeness graph and a tax calculation graph.

[0020] FIG. 2 illustrates an example of a simplified version of a completeness graph related to a qualifying child for purposes of determining deductions for federal income tax purposes.

[0021 ] FIG. 3 illustrates another illustration of a completeness graph. [0022] FIG. 4 illustrates a decision table based on or derived from the completeness graph of FIG. 3.

[0023] FIG. 5 illustrates another embodiment of a decision table that incorporates statistical data.

[0024] FIG. 6A illustrates an example of a tax calculation graph according to one embodiment.

[0025] FIG. 6B illustrates an example of a calculation graph that relates to the determination and calculation of a shared responsibility penalty under the Affordable Care Act according to one embodiment.

[0026] FIG. 7 schematically illustrates a tax preparation system for calculating taxes using rules and calculations based on declarative data structures, and for performing a tax recommendation function, according to one embodiment.

[0027] FIG. 8 is a flow chart of a method for determining tax

recommendations for a taxpayer using a the tax preparation system having a tax recommendation engine.

[0028] FIG. 9 illustrates a controllability model according to one embodiment.

[0029] FIG. 10 illustrates a display for providing tax recommendations using slider input value controls for adjusting the values of user controllable variables according to one embodiment.

[0030] FIG. 1 1 is a flow chart of a method for preparing an electronic tax return and determining tax recommendations according to one embodiment.

[0031 ] FIG. 12 illustrates the implementation of tax preparation software on various computing devices. [0032] FIG. 13 illustrates generally the components of a computing device that may be utilized to execute the software for automatically calculating or determining tax liability, performing an estimated tax payments function, and/or preparing a tax return based thereon, according to the embodiments of the invention.

[0033] FIG. 14 is a flow chart of a method for computing and generating a controllability model, according to one embodiment.

[0034] FIG. 15 is a schematic diagram of a tax recommendation system or subsystem for providing tax recommendations to a user, according to one embodiment.

[0035] FIG. 16 is a flow chart of a method for providing tax recommendations to a user, according to one embodiment.

[0036] FIG. 17 is a flow chart of a method for providing tax recommendations using the system of FIG. 15, according to one embodiment.

DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS

[0037] Embodiments of the present invention are directed to systems, methods and articles of manufacture for determining tax recommendations for a taxpayer by using a tax calculation graph to identify tax variables that a taxpayer can control and modify. The tax preparation system of the present invention comprises a recommendation engine configured to analyze a tax calculation graph which is calculated using tax data of the taxpayer. The recommendation engine determines tax variables (e.g., input nodes) in the tax calculation graph which can affect the tax result (e.g., total tax liability, the amount of tax payment remaining, or refund amount). The recommendation engine analyzes these tax variables to determine which of them can be reasonably controlled by the taxpayer using a controllability model which relates tax variables to a level of user controllability. The recommendation engine then executes a tax calculation engine to calculate the tax calculation graph by varying the taxpayer controllable variables to determine how varying the user controllable variables affects the tax result. The recommendation engine then analyzes the affect on the tax result and determines one or more tax recommendation for the taxpayer. As one example, the recommendation engine may determine that the taxpayer can increase a 401 (k) retirement contribution and decrease the total tax liability, and therefore, may recommend that the taxpayer increase the 401 (k) contribution from a current value to an increased value.

[0038] Tax preparation is a time-consuming and laborious process. It is estimated that individuals and businesses spend around 6.1 billion hours per year complying with the filing requirements of the United States federal Internal Revenue Code. Tax return preparation software has been commercially available to assist taxpayers in preparing their tax returns. Tax return

preparation software is typically run on a computing device such as a computer, laptop, tablet, or mobile computing device such as a Smartphone. Traditionally, a user has walked through a set of rigidly defined user interface interview screens that selectively ask questions that are relevant to a particular tax topic or data field needed to calculate a taxpayer's tax liability. [0039] In contrast to the rigidly defined user interface screens used in prior iterations of tax preparation software, the present design provides tax preparation software 100 that runs on computing devices 102, 103 (see FIG. 12) and operates on a new construct in which tax rules and the calculations based thereon are established in declarative data-structures, namely, completeness graph(s) and tax calculation graph(s). Completeness graphs 12 (see e.g. FIGS. 1 -3) and tax calculation graphs 14 (see e.g. FIGS. 6A-6B) are data structures in the form of trees having nodes and interconnections between the nodes indicating interdependencies. Completeness graphs 12 identify each of the conditions (e.g. questions, criteria, conditions) which may be required to be satisfied to complete a particular tax topic or a complete tax return, and also identifies when all conditions have been satisfied to complete a particular tax topic or, a complete, file-able tax return. The tax calculation graphs 14

semantically describe data dependent nodes, including input nodes, functional nodes, functions, and tax operations, that perform tax calculations or operations in accordance with tax code or tax rules. Examples of these data structures are described in U.S. Patent Application Nos. 14/097,057 and 14/448,886, both of which are incorporated by reference as if set forth fully herein.

[0040] Use of these data-structures permits the user interface to be loosely connected or even detached from the tax calculation engine and the data used in the tax calculations. Tax calculations are dynamically calculated based on tax data derived from sourced data, estimates, user input, or even intermediate tax calculations that are then utilized for additional tax calculations. A smart tax logic agent running on a set of rules can review current run time data and evaluate missing data fields and propose suggested questions to be asked to a user to fill in missing blanks. This process can be continued until completeness of all tax topics has occurred. An electronic return can then be prepared and filed with respect to the relevant taxing jurisdictions.

[0041 ] FIG. 1 illustrates graphically how tax legislation/tax rules 10 are broken down into a completeness graph 12 and a tax calculation graph 14. In one aspect of the invention, tax legislation or rules 10 are parsed or broken into various topics. For example, there may be nearly one hundred topics that need to be covered for completing a federal tax return. When one considers both federal and state tax returns, there can be well over one hundred tax topics that need to be covered. When tax legislation or tax rules 10 are broken into various topics or sub-topics, in one embodiment of the invention, each particular topic (e.g., topics A, B) may each have their own dedicated completeness graph 12A, 12B and tax calculation graph 14A, 14B as seen in FIG. 1 .

[0042] Note that in FIG. 1 , the completeness graph 12 and the tax calculation graph 14 are interdependent as illustrated by dashed line 16. That is to say, some elements contained within the completeness graph 12 are needed to perform actual tax calculations using the tax calculation graph 14. Likewise, aspects within the tax calculation graph 14 may be needed as part of the completion graph 12. Taken collectively, the completeness graph 12 and the tax calculation graph 14 represent data structures that capture all the conditions necessary to complete the computations that are required to complete a tax return that can be filed. The completeness graph 12, for example, determines when all conditions have been satisfied such that a "fileable" tax return can be prepared with the existing data. The completeness graph 12 is used to determine, for example, that no additional data input is needed to prepare and ultimately print or file a tax return. The completeness graph 12 is used to determine when a particular schema contains sufficient information such that a tax return can be prepared and filed. Individual combinations of completeness graphs 12 and tax calculation graphs 14 that relate to one or more topics can be used to complete the computations required for some sub-calculation. In the context of a tax setting, for example, a sub-selection of topical completeness graphs 12 and tax calculation graphs 14 can be used for intermediate tax results such as Adjusted Gross Income (AGI) or Taxable Income (Tl), itemized deductions, tax credits, and the like.

[0043] The completeness graph 12 and the tax calculation graph 14 represent data structures that can be constructed in the form of a tree. FIG. 2 illustrates a completeness graph 12 in the form of a tree with nodes 20 and arcs 22

representing a basic or general version of a completeness graph 12 for the topic of determining whether a child qualifies as a dependent for federal income tax purposes. A more complete flow chart-based representation of questions related to determining a "qualified child" may be found in U.S. Patent Application No. 14/097,057, which is incorporated by reference herein. Each node 20 contains a condition that in this example is expressed as a Boolean expression that can be answered in the affirmative or negative. The arcs 22 that connect each node 20 illustrate the dependencies between nodes 20. The combination of arcs 22 in the completeness graph 12 illustrates the various pathways to completion. A single arc 22 or combination of arcs 22 that result in a determination of "Done" represent a pathway to completion. As seen in FIG. 2, there are several pathways to completion. For example, one pathway to completion is where an affirmative (True) answer is given to the question of whether you or a spouse can be claimed on someone else's tax return. If such a condition is true, your child is not a qualifying dependent because under IRS rules you cannot claim any dependents if someone else can claim you as a dependent. In another example, if you had a child and that child did not live with you for more than 6 months of the year, then your child is not a qualifying dependent. Again, this is a separate IRS requirement for a qualified dependent.

[0044] As one can imagine given the complexities and nuances of the tax code, many tax topics may contain completeness graphs 12 that have many nodes with a large number of pathways to completion. However, many branches or lines within the completeness graph 12 can be ignored, for example, when certain questions internal to the completeness graph 12 are answered that eliminate other nodes 20 and arcs 22 within the completeness graph 12. The dependent logic expressed by the completeness graph 12 allows one to minimize subsequent questions based on answers given to prior questions. This allows a minimum question set that can be generated and that can be presented to a user as explained herein. [0045] FIG. 3 illustrates another example of a completeness graph 12 that includes a beginning node 20a (Node A), intermediate nodes 20b-g (Nodes B-G) and a termination node 20y (Node "Yes" or "Done"). Each of the beginning node 20a and intermediate nodes 20a-g represents a question. Inter-node

connections or arcs 22 represent response options. In the illustrated

embodiment, each inter-node connection 22 represents an answer or response option in binary form (Y/N), for instance, a response to a Boolean expression. It will be understood, however, that embodiments are not so limited, and that a binary response form is provided as a non-limiting example. In the illustrated example, certain nodes, such as nodes A, B and E, have two response options 22, whereas other nodes, such as nodes D, G and F, have one response option 22.

[0046] As explained herein, the directed graph or completion graph 12 that is illustrated in FIG. 3 can be traversed through all possible paths from the start node 20a to the termination node 20y. By navigating various paths through the completion graph 12 in a recursive manner, the system can determine each path from the beginning node 20a to the termination node 20y. The completion graph 12 along with the pathways to completion through the graph can be converted into a different data structure or format. In the illustrated embodiment shown in FIG. 4, this different data structure or format is in the form of a decision table 30. In the illustrated example, the decision table 30 includes rows 32 (five rows 32a-e are illustrated) based on the paths through the completion graph 12. In the illustrated embodiment, the columns 34a-g of the completion graph represent expressions for each of the questions (represented as nodes A-G in FIG. 3) and answers derived from completion paths through the completion graph 12 and column 34h indicates a conclusion, determination, result or goal 34h concerning a tax topic or situation, e.g., "Yes - your child is a qualifying child" or "No - your child is not a qualifying child."

[0047] Referring to FIG. 4, each row 32 of the decision table 30 represents a tax rule. The decision table 30, for example, may be associated with a federal tax rule or a state tax rule. In some instances, for example, a state tax rule may include the same decision table 30 as the federal tax rule. The decision table 30 can be used, as explained herein, to drive a personalized interview process for the user of tax preparation software 100. In particular, the decision table 30 is used to select a question or questions to present to a user during an interview process. In this particular example, in the context of the completion graph from FIG. 3 converted into the decision table 30 of FIG. 4, if the first question presented to the user during an interview process is question "A" and the user answers "Yes" rows 32c-e may be eliminated from consideration given that no pathway to completion is possible. The tax rule associated with these columns cannot be satisfied given the input of "Yes" in question "A." Note that those cell entries denoted by "?" represent those answers to a particular question in a node that are irrelevant to the particular pathway to completion. Thus, for example, referring to row 34a, when an answer to Q _A is "Y" and a path is completed through the completion graph 12 by answering Question C as "N" then answers to the other questions in Nodes B and D-F are "?" since they are not needed to be answered given that particular path.

[0048] After an initial question has been presented and rows are eliminated as a result of the selection, next, a collection of candidate questions from the remaining available rows 32a and 32b is determined. From this universe of candidate questions from the remaining rows, a candidate question is selected. In this case, the candidate questions are questions Q _c and Q _G in columns 34c, 34g, respectively. One of these questions is selected and the process repeats until either the goal 34h is reached or there is an empty candidate list.

[0049] FIG. 5 illustrates another embodiment of a decision table 30. In this embodiment, the decision table 30 includes additional statistical data 36 associated with each rule (e.g., rules R Re). For example, the statistical data 36 may represent a percentage or the like in which a particular demographic or category of user(s) satisfies this particular path to completion. The statistical data 36 may be mined from existing or current year tax filings. The statistical data 36 may be obtained from a proprietary source of data such as tax filing data owned by Intuit, Inc. The statistical data 36 may be third party data that can be purchased or leased for use. For example, the statistical data 36 may be obtained from a government taxing authority or the like (e.g., IRS). In one aspect, the statistical data 36 does not necessarily relate specifically to the individual or individuals preparing the particular tax return. For example, the statistical data 36 may be obtained based on a number of tax filers which is then classified into one or more classifications. For example, statistical data 36 can be organized with respect to age, type of tax filing (e.g., joint, separate, married filing separately), income range (gross, AGI, or TI), deduction type, geographic location, and the like).

[0050] FIG. 5 illustrates two such columns 38a, 38b in the decision table 30 that contain statistical data 36 in the form of percentages. For example, column 38a (STAT1 ) may contain a percentage value that indicates taxpayers under the age of thirty-five where Rule _! is satisfied. Column 38b (STAT2) may contain a percentage value that indicates taxpayers over the age of thirty-five where Rule _! is satisfied. Any number of additional columns 38 could be added to the decision table 30 and the statistics do not have to relate to an age threshold or grouping. The statistical data 36 may be used, as explained in more detail below, by the tax preparation software 100 to determine which of the candidate questions (Q _A -QG) should be asked to a taxpayer. The statistical data 36 may be compared to one or more known taxpayer data fields (e.g., age, income level, tax filing status, geographic location, or the like) such that the question that is presented to the user is most likely to lead to a path to completion. Candidate questions may also be excluded or grouped together and then presented to the user to efficiently minimize tax interview questions during the data acquisition process. For example, questions that are likely to be answered in the negative can be grouped together and presented to the user in a grouping and asked in the negative - for example, "we think these question do not apply to you, please confirm that this is correct." This enables the elimination of many pathways to completion that can optimize additional data requests of the taxpayer. [0051 ] FIGS. 6A and 6B illustrate two examples of tax calculation graphs 14. The tax calculation graph 14 semantically describes data dependent tax operations that are used to perform a tax calculation in accordance with the tax code or tax rules 10. The tax calculation graphs 14 in FIGS. 6A and 6B are a simplified view of data dependent tax operations that are used to determine the taxes Due (taxDue) based on various sources of income, deductions,

exemptions, and credits. The tax calculation graph 14 is a type of directed graph (which may be composed of a plurality of directed graphs) and, in most situations relevant to tax calculations, is a directed acyclic graph that encodes the data dependencies amongst tax concepts or topics.

[0052] In FIG. 6A, various nodes 24 are leaf or input nodes. Examples of leaf nodes 24 in this particular example include data obtained from W-2 forms, data obtained from 1099-INT forms, data obtained from other investment income (INV), filing status, and number of dependents. Typically, though not exclusively, leaf nodes 24 are populated with user inputs. That is to say the user (e.g. a taxpayer) will enter this information from a user interface as described herein. In other embodiments, however, the leaf nodes 24 may be populated with information that is automatically obtained by the tax preparation software 100. For example, in some embodiments, tax documents may be imaged or scanned with relevant data being automatically extracted using Object Character

Recognition (OCR) techniques. In other embodiments, prior tax returns may be used by the tax preparation software 100 to extract information (e.g., name, potential dependents, address, and social security number) which can then be used to populate the leaf nodes 24. Online resources such as financial services websites or other user-specific websites can be crawled and scanned to scrape or otherwise download tax related information that can be automatically populated into leaf nodes 24. Additional third party information sources such as credit bureaus, government databases, and the like can also be used by the tax preparation software 100 to obtain information that can then be populated in to respective leaf nodes 24.

[0053] In still other embodiments, values for leaf nodes 24 may be derived or otherwise calculated. For example, while the number of dependents may be manually entered by a taxpayer, those dependents may not all be "qualifying" dependents for tax purposes. In such instances, the actual number of "qualified" dependents may be derived or calculated by the tax preparation software 100. In still other embodiments, values for leaf nodes 24 may be estimated as described herein.

[0054] Still other internal nodes, referred to as functional nodes 26, semantically represent a tax concept and may be calculated or otherwise determined using a function node 28 (also referred to as a "function 28"). The functional node 26 and the associated function 28 define a particular tax operation 29. For example, as seen in FIG. 6A, tax operation 29 refers to total wage income and is the result of the accumulator function 28 summing all W-2 income from leaf nodes 24. The functional node 26 may include a number in some instances. In other instances, the functional node 26 may include a response to a Boolean expression such as "true" or "false." The functional nodes 26 may also be constant values in some instances. Some or all of these functional nodes 26 may be labeled as "tax concepts" or "tax topics." The combination of a functional node 26 and its associated function 28 relate to a specific tax operation 29 as part of the tax topic.

[0055] Interconnected functional node 26 containing data dependent tax concepts or topics are associated with a discrete set of functions 28 that are used to capture domain specific patterns and semantic abstractions used in the tax calculation. The discrete set of functions 28 that are associated with any particular functional node may be commonly re-occurring operations for functions that are used throughout the process of calculating tax liability. For instance, examples of such commonly reoccurring functions 28 include copy, capping, thresholding, accumulation or adding, look-up operations, phase out calculations, comparison calculations, exemptions, exclusions, and the like.

[0056] In one embodiment, the entire set of functions 28 that is used to compute or calculate a tax liability is stored within a data store 30 which in some instances may be a database. The various functions 28 that are used to semantically describe data connections between functional nodes 26 can be called upon by the tax preparation software 100 for performing tax calculations. Utilizing these common functions 28 greatly improves the efficiency of the tax preparation software 100 and can be used by a programmer to more easily track and follow the complex nature of the ever-evolving tax code. The common functions 28 also enable easier updating of the tax preparation software 100 because as tax laws and regulations change, fewer changes need to be made to the software code as compared to prior hard-wired approaches.

[0057] Importantly, the tax calculation graph 14 and the associated functional nodes 26 and function nodes 28 can be tagged and later be used or called upon to intelligently explain to the user the reasoning behind why a particular tax result changed or did not change between a first set of tax data and a second set of tax data having one or more different values, as explained in more detail below. The functions 28 can be de-coupled from a specific narrow definition and instead be associated with one or more explanations. Examples of common functions 28 found in tax legislation and tax rules include the concepts of "caps" or

"exemptions" that are found in various portions of the tax code. One example of a "cap" is the portion of the U.S. tax code that limits the ability of a joint filer to deduct more than $3,000 of net capital losses in any single tax year. There are many other instances of such caps. An example of an "exemption" is one that relates to early distributions from retirement plans. For most retirement plans, early distributions from qualified retirement plans prior to reaching the age of fifty nine and one-half (59 ½) require a 10% penalty. This penalty can be avoided, however, if an exemption applies such as the total and permanent disability of the participant. Other exemptions also apply. Such exemptions are found throughout various aspects of the tax code and tax regulations.

[0058] In some embodiments, the function node 28 may include any number of mathematical or other operations. Examples of functions 28 include

summation, subtraction, multiplication, division, and look-ups of tables or values from a database 30 or library as is illustrated in FIG. 6A. It should be understood that the functional node 26 within completion graph 12 and the tax calculation graph 14 may be shared in some instances. For example, AGI is a re-occurring tax concept that occurs in many places in the tax code. AGI is used not only for the mathematical computation of taxes but is also used, for example, to determine eligibility of certain tax deductions and credits. Thus, the AGI node is common to both the completion graph 12 and the tax calculation graph 14.

[0059] FIG. 6B illustrates an example of a tax calculation graph 14 that is used to calculate the amount of penalty under the Affordable Care Act (ACA). Under the ACA, taxpayers are required to have minimum essential health coverage for each month of the year, qualify for an exemption, or make a shared responsibility penalty payment when filing his or her federal tax return. FIG. 6B illustrates a flowchart illustration of a process used to calculate a taxpayer's shared responsibility payment under the ACA (referred to herein as an ACA penalty). FIG. 6B illustrates, for example, various leaf nodes 24a-24j used as part of this calculation to determine the ACA penalty. Leaf nodes 24a-24f are used to calculate the modified adjusted gross income (ACA MAGI) as well as the applicable ACA poverty level. One can see how the accumulator function 28a is used to generate the ACA MAGI in this example by adding foreign income 14a, AGI 24b, and tax exempt interest 24c. Likewise, a look-up function 28b can be used to determine the applicable ACA poverty level based on the taxpayer's zip code 24d, filing status 24e, and number of dependents 24f. The ACA MAGI and the ACA poverty level are then subject to a thresholding function 28c to determine whether the ACA poverty level exemption applies. Under the ACA, if a taxpayer cannot afford basic coverage because the minimum amount one must pay for the premiums exceeds a percentage of household income (i.e., 8%), one is exempt from obtaining minimum essential coverage.

[0060] Still referring to FIG. 6B, a taxpayer may be exempt from the requirement to obtain minimum essential coverage by obtaining a different statutory exemption. These exemptions include: religious conscience, health care sharing ministry, a member of Indian tribe, short coverage gap (less than 3 consecutive months), hardship, affordability (already mentioned above), incarceration, and not lawfully present. A true/false Boolean function 28d may be used to determine whether an Exemption Certificate Number (ECN) has been obtained from the taxpayer certifying that one of the statutory exemptions has been satisfied. Another threshold function 28e is applied to determine whether one of the statutory exemptions is satisfied (e.g., affordability or others). If at least one of these statutory conditions is met then the taxpayer is exempt from the ACA shared responsibility payment penalty.

[0061 ] As seen in FIG. 6B, if a taxpayer has obtained minimal essential coverage during the year, there is still the possibility that a penalty may be owed because under the ACA, if there is a gap in coverage for a covered member of the family of more than three (3) months, at least some penalty amount is owed. Function 28f (at least one condition true) is used to determine if there was minimum essential coverage during the year for any period. Function 28g (gap>3 months) is used to determine the gap in coverage in order to gaps in coverage that exceed the 3 month statutory requirement. The gap in coverage penalty, however, may be pro-rated based on the length of the gap in coverage as indicated in FIG. 6B.

[0062] In the event there is a penalty, the ACA requires that the penalty be the greater of a percentage of income, net of specified deductions, or a specified penalty that is applied per individual or family. For example, for the 2015 year, the percentage is 2.0 percent and increases to 2.5 percent in subsequent years. FIG. 6B illustrates the use of a subtraction function 28g that utilizes the AGI node 24b to arrive at a taxable income value. A look-up function 28h is used to obtain the applicable tax rate (e.g., 2.0% for 2015) and is used to calculate the income- based ACA penalty.

[0063] In order to determine the non-income or "fixed" penalty, an

accumulator function 28i is used to determine the penalty. In this example, the calculation pertains to a family wherein the penalty includes a fixed amount for a child ($162.50 per child in 2015) and a fixed amount per adult ($325.00 per adult). Under the ACA, there is a maximum cap of this fixed penalty. For example, in 2015, the maximum family penalty is $975. As seen in FIG. 6B, a cap function 28j is used to determine the minimum cap. Another function 28k that is referred to as "at least minimum cap" is used to determine the greater of the fixed penalty or the income-based penalty. If the income-based penalty is higher than the fixed amount then that value is used, otherwise the fixed penalty amount is used. Still referring to FIG. 6B, another cap function 28I is used to determine whether the penalty has exceeded another cap that is part of the ACA law. Under the ACA, the overall penalty is capped at the national average premium for a bronze level insurance plan. The cap function 281 is used to ensure that the calculated penalty (i.e., the income based penalty) does not exceed this amount. After application of the cap function 281, the ACA penalty amount is determined.

[0064] As seen in FIG. 6B, there are a variety of different functions 28 that are employed as part of the process used to calculate any applicable penalty under the ACA. In some instances, a common function (e.g., cap functions 28j and 281) is found in multiple locations within the tax calculation graph 14. It should be understood that the functions 28 illustrated in FIG. 6B are illustrative as other functions may be used beyond those specifically illustrated in the drawings.

[0065] FIG. 7 schematically illustrates a tax return preparation system 40 for calculating taxes using rules and calculations based on declarative data structures according to one embodiment. The system 40 includes a shared data store 42 that contains therein a schema 44 or canonical model representative to the data fields utilized or otherwise required to complete a tax return. The shared data store 42 may be a repository, file, or database that is used to contain the tax-related data fields. The shared data store 42 is accessible by a computing device 102, 103 as described herein (e.g., FIG. 12). The shared data store 42 may be located on the computing device 102, 103 running the tax preparation software 100 or it may be located remotely, for example, in cloud environment on another, remotely located computer. The schema 44 may include, for example, a schema based on the Modernized e-File (MeF) system developed by the Internal Revenue Service. The MeF is a web-based system that allows electronic filing of tax returns through the Internet. MeF uses extensible markup language (XML) format that is used when identifying, storing, and transmitting data. For example, each line or data element on a tax return is given an XML name tag as well as every instance of supporting data. Tax preparation software 100 uses XML schemas and business rules to electronically prepare and transmit tax returns to tax reporting agencies. Transmitters use the Internet to transmit electronic tax return data to the IRS MeF system. The IRS validates the transmitted files against the XML schemas and Business Rules in the MeF schema 44.

[0066] The schema 44 may be a modified version of the MeF schema used by the IRS. For example, the schema 44 may be an extended or expanded version (designated MeF++) of the MeF model established by government authorities that utilizes additional fields. While the particular MeF schema 44 is discussed herein the invention is not so limited. MeF and MeF+++ are only examples of tax agency standards for electronic filing of tax returns, and the present invention is not limited to any particular standard. Accordingly, any references to MeF or MeF++ in the specification or drawings includes any suitable standard for electronic filing of tax returns.

[0067] There may be many different schemas 44 depending on the different tax jurisdiction. For example, Country A may have a tax schema 44 that varies from Country B. Different regions or states within a single country may even have different schemas 44. The systems and methods described herein are not limited to a particular schema 44 implementation. The schema 44 may contain all the data fields required to prepare and file a tax return with a government taxing authority. This may include, for example, all fields required for any tax forms, schedules, and the like. Data may include text, numbers, and a response to a Boolean expression (e.g., True/False or Yes/No). As explained in more detail, the shared data store 42 may, at any one time, have a particular instance 46 of the MeF schema 44 (for MeF++ schema) stored therein at any particular time. For example, FIG. 7 illustrates several instances 46 of the MeF schema 44 (labeled as MeF-ι, MeF ₂ , MeF _N ). These instances 46 may be updated as additional data is input into the shared data store 42.

[0068] As seen in FIG. 7, the shared data store 42 may import data from one or more data sources 48. A number of data sources 48 may be used to import or otherwise transfer tax related data to the shared data store 42. This may occur through a user interface control 80 as described herein or, alternatively, data importation may occur directly to the shared data store 42 (not illustrated in FIG. 7). The tax related data may include personal identification data such as a name, address, or taxpayer ID. Tax data may also relate to, for example, details regarding a taxpayer's employer(s) during a preceding tax year. This may include, employer name, employer federal ID, dates of employment, and the like. Tax related day may include residential history data (e.g., location of residence(s) in tax reporting period (state, county, city, etc.) as well as type of housing (e.g., rental unit or purchased home). Tax related information may also include dependent-related information such as the number of family members in a household including children. Tax related information may pertain to sources of income, including both earned and unearned income as well. Tax related information also include information that pertains to tax deductions or tax credits. Tax related information may also pertain to medical insurance information. For example, under the new ACA many taxpayers may obtain health insurance through a state or federal marketplace. Such a marketplace may have

information stored or accessible that is used in connection with preparing a tax return. Tax information related to premiums paid, coverage information, subsidy amounts (if any), and enrolled individuals can be automatically imported into the shared data store 42.

[0069] For example, user input 48a is one type of data source 48. User input 48a may take a number of different forms. For example, user input 48a may be generated by a user using, for example, an input device such as keyboard, mouse, touchscreen display, voice input (e.g., voice to text feature), photograph or image, or the like to enter information manually into the tax preparation software 100. For example, as illustrated in FIG. 7, user interface manager 82 contains an import module 89 that may be used to select what data sources 48 are automatically searched for tax related data. Import module 89 may be used as a permission manager that includes, for example, user account numbers and related passwords. The Ul control 80 enables what sources 48 of data are searched or otherwise analyzed for tax related data. For example, a user may select prior year tax returns 48b to be searched but not online resources 48c. The tax data may flow through the Ul control 80 directly as illustrated in FIG. 7 or, alternatively, the tax data may be routed directly to the shared data store 42. The import module 89 may also present prompts or questions to the user via a user interface presentation 84 generated by the user interface manager 82. For example, a question may ask the user to confirm the accuracy of the data. For instance, the user may be asked to click a button, graphic, icon, box or the like to confirm the accuracy of the data prior to or after the data being directed to the shared data store 42. Conversely, the interface manager 82 may assume the accuracy of the data and ask the user to click a button, graphic, icon, box or the like for data that is not accurate. The user may also be given the option of whether or not to import the data from the data sources 48.

[0070] User input 48a may also include some form of automatic data gathering. For example, a user may scan or take a photographic image of a tax document (e.g., W-2 or 1099) that is then processed by the tax preparation software 100 to extract relevant data fields that are then automatically transferred and stored within the data store 42. OCR techniques along with pre-stored templates of tax reporting forms may be called upon to extract relevant data from the scanned or photographic images whereupon the data is then transferred to the shared data store 42.

[0071 ] Another example of a data source 48 is a prior year tax return 48b. A prior year tax return 48b that is stored electronically can be searched and data is copied and transferred to the shared data store 42. The prior year tax return 48b may be in a proprietary format (e.g., .txt, .pdf) or an open source format. The prior year tax return 48b may also be in a paper or hardcopy format that can be scanned or imaged whereby data is extracted and transferred to the shared data store 42. In another embodiment, a prior year tax return 48b may be obtained by accessing a government database (e.g., IRS records).

[0072] An additional example of a data source 48 is an online resource 48c. An online resource 48c may include, for example, websites for the taxpayer(s) that contain tax-related information. For example, financial service providers such as banks, credit unions, brokerages, investment advisors typically provide online access for their customers to view holdings, balances, and transactions. Financial service providers also typically provide year-end tax documents to their customers such as, for instance, 1099-INT (interest income), 1099-DIV (dividend income), 1099-B (brokerage proceeds), 1098 (mortgage interest) forms. The data contained on these tax forms may be captured and transferred electronically to the shared data store 42.

[0073] Of course, there are additional examples of online resources 48c beyond financial service providers. For example, many taxpayers may have social media or similar accounts. These include, by way of illustration and not limitation, Facebook, Linked-ln, Twitter, and the like. User's may post or store personal information on these properties that may have tax implications. For example, a user's Linked-ln account may indicate that a person changed jobs during a tax year. Likewise, a posting on Facebook about a new home may suggest that a person has purchased a home, moved to a new location, changed jobs; all of which may have possible tax ramifications. This information is then acquired and transferred to the shared data store 42, which can be used to drive or shape the interview process described herein. For instance, using the example above, a person may be asked a question whether or not she changed jobs during the year (e.g., "It looks like you changed jobs during the past year, is this correct?". Additional follow-up questions can then be presented to the user.

[0074] Still referring to FIG. 7, another data source 48 includes sources of third party information 48d that may be accessed and retrieved. For example, credit reporting bureaus contain a rich source of data that may implicate one or more tax items. For example, credit reporting bureaus may show that a taxpayer has taken out a student loan or home mortgage loan that may be the source of possible tax deductions for the taxpayer. Other examples of sources of third party information 48d include government databases. For example, the state department of motor vehicles may contain information relevant to tax portion of vehicle registration fees which can be deductible in some instances. Other government databases that may be accessed include the IRS (e.g., IRS tax return transcripts), and state taxing authorities. Third party resources 48d may also include one of the state-based health insurance exchanges or the federal health insurance exchange (e.g., www.healthcare.gov).

[0075] Referring briefly to FIG. 12, the tax preparation software 100 including the system 40 of FIG. 7 is executed by the computing device 102, 103. Referring back to FIG. 7, the tax return preparation software 100 executed by the

computing device 102, 103 includes a tax calculation engine 50 that computes one or more tax calculations based on the tax calculation graph(s) 14 and the available data at any given instance within the schema 44 in the shared data store 42. The tax calculation engine 50 may calculate a final tax due amount (i.e. tax liability), a final refund amount, or one or more intermediary calculations (e.g., taxable income, AGI, earned income, un-earned income, total deductions, total credits, alternative minimum tax (AMT) and the like). The tax calculation engine 50 utilizes the one or more calculation graphs 14 as described previously in the context of FIGS. 1 , 6A and 6B. In one embodiment, a series of different calculation graphs 14 are used for respective tax topics. These different calculation graphs 14 may be coupled together or otherwise compiled as a composite calculation graph 14 to obtain an amount of taxes due or a refund amount based on the information contained in the shared data store 42. The tax calculation engine 50 reads the most current or up to date information contained within the shared data store 42 and then performs tax calculations. Updated tax calculation values are then written back to the shared data store 42. As the updated tax calculation values are written back, new instances 46 of the canonical model 46 are created. The tax calculations performed by the tax calculation engine 50 may include the calculation of an overall tax liability or refund due. The tax calculations may also include intermediate calculations used to determine an overall tax liability or refund due (e.g., AGI calculation). Tax calculations include, for example, the ACA penalty that is described in FIG. 6B as one illustrative example.

[0076] Still referring to FIG. 7, the system 40 includes a tax logic agent (TLA) 60. The TLA 60 operates in conjunction with the shared data store 42 whereby updated tax data represented by instances 46 are read to the TLA 60. The TLA 60 contains run time data 62 that is read from the shared data store 42. The run time data 62 represents the instantiated representation of the canonical tax schema 44 at runtime. The TLA 60 may contain therein a rule engine 64 that utilizes a fact cache to generate either non-binding suggestions 66 for additional question(s) to present to a user or "Done" instructions 68 which indicate that completeness has occurred and additional input is not needed. The rule engine 64 may operate in the form of a Drools expert engine. Other declarative rules engines 64 may be utilized and a Drools expert rule engine 64 is provided as one example of how embodiments may be implemented. The TLA 60 may be implemented as a dedicated module contained within the tax preparation software 100.

[0077] As seen in FIG. 7, the TLA 60 uses the decision tables 30 to analyze the run time data 62 and determine whether a tax return is complete. Each decision table 30 created for each topic or sub-topic is scanned or otherwise analyzed to determine completeness for each particular topic or sub-topic. In the event that completeness has been determined with respect to each decision table 30, then the rule engine 64 outputs a "done" instruction 68 to the Ul control 80. If the rule engine 64 does not output a "done" instruction 68 that means there are one or more topics or sub-topics that are not complete, in which case, as explained in more detail below, the Ul control 80 presents interview questions to a user for answer. The TLA 60 identifies a decision table 30 corresponding to one of the non-complete topics or sub-topics and, using the rule engine 64, identifies one or more non-binding suggestions 66 to present to the Ul control 80. The non-binding suggestions 66 may include a listing or compilation of one or more questions (e.g., Q1 -Q5 as seen in FIG. 7) from the decision table 30. In some instances, the listing or compilation of questions may be ranked in order by rank. The ranking or listing may be weighted in order of importance, relevancy, confidence level, or the like. For example, a top ranked question may be a question that, based on the remaining rows (e.g., R1 -R5) in a decision will most likely lead to a path to completion. As part of this ranking process, statistical information such as the STAT1 , STAT2 percentages as illustrated in FIG. 5 may be used to augment or aid this ranking process. Questions may also be presented that are most likely to increase the confidence level of the calculated tax liability or refund amount. In this regard, for example, those questions that resolve data fields associated with low confidence values may, in some embodiments, be ranked higher.

[0078] The following pseudo code generally expresses how a rule engine 64 functions utilizing a fact cache based on the runtime canonical data 62 or the instantiated representation of the canonical tax schema 46 at runtime and generating non-binding suggestions 66 provided as an input a Ul control 80. As described in U.S. Application No. 14/097,057 previously incorporated herein by reference, data such as required inputs can be stored to a fact cache so that the needed inputs can be recalled at a later time, and to determine what is already known about variables, factors or requirements of various rules:

Rule engine (64)/ Tax Logic Agent (TLA) (60)

// initialization process

Load_Tax_Knowledge_Base; Create_Fact_Cache; While (new_data_from_application) lnsert_data_into_fact_cache;

collection = Execute_Tax_Rules; // collection is all the fired rules and corresponding conditions

suggestions = Generate_suggestions (collection);

send_to_application(suggestions);

[0079] The TLA 60 may also receive or otherwise incorporate information from a statistical/ life knowledge module 70. The statistical/life knowledge module 70 contains statistical or probabilistic data related to the taxpayer. For example, statistical/ life knowledge module 70 may indicate that taxpayers residing within a particular zip code are more likely to be homeowners than renters. More specifically, the statistical/life knowledge module may comprise tax correlation data regarding a plurality of tax matter correlations. Each of the tax matter correlations quantifies a correlation between a taxpayer attribute and a tax related aspect. For instance, a taxpayer attribute could be taxpayer age which may be correlated to a tax related aspect such as having dependents, or a taxpayer attribute might be taxpayer age which may be correlated to

homeownership or other relevant tax related aspect. The tax correlation data also quantifies the correlations, such as by a probability of the correlation. For instance, the correlation between the taxpayer attribute and the tax related aspect may be a certain percentage probability, such as 10%, 20%, 30%, 40%, 50%, 60%, or any percentage from 0% to 100%. Alternatively, the quantification can be a binary value, such as relevant or not relevant. In other words, for a given taxpayer attribute, it may be determined that a tax related aspect is relevant or completely not relevant when a taxpayer has the given taxpayer attribute. As an example, if the taxpayer attribute is that the taxpayer is married, the correlation may indicate that spouse information is relevant and will be required.

[0080] The TLA 60 may use this knowledge to weight particular topics or questions related to these topics. For example, in the example given above, questions about home mortgage interest may be promoted or otherwise given a higher weight. The statistical knowledge may apply in other ways as well. For example, tax forms often require a taxpayer to list his or her profession. These professions may be associated with transactions that may affect tax liability. For instance, a taxpayer may list his or her occupation as "teacher." The statistic/life knowledge module 70 may contain data that shows that a large percentage of teachers have retirement accounts and in particular 403(b) retirement accounts. This information may then be used by the TLA 60 when generating its

suggestions 66. For example, rather than asking generically about retirement accounts, the suggestion 66 can be tailored directly to a question about 403(b) retirement accounts.

[0081 ] The data that is contained within the statistic/life knowledge module 70 may be obtained by analyzing aggregate tax data of a large body of taxpayers. For example, entities having access to tax filings may be able to mine their own proprietary data to establish connections and links between various taxpayer characteristics and tax topics. This information may be contained in a database or other repository that is accessed by the statistic/life knowledge module 70. This information may be periodically refreshed or updated to reflect the most up- to-date relationships. Generally, the data contained in the statistic/life knowledge module 70 is not specific to a particular tax payer but is rather generalized to characteristics shared across a number of tax payers although in other embodiments, the data may be more specific to an individual taxpayer.

[0082] Still referring to FIG. 7, the Ul controller 80 encompasses a user interface manager 82 and a user interface presentation or user interface 84. The user interface presentation 84 is controlled by the interface manager 82 and may manifest itself, typically, on a visual screen or display 104 that is presented on a computing device 102 (seen, for example, in FIG. 12). The computing device 102 may include the display of a computer, laptop, tablet, mobile phone (e.g., Smartphone), or the like. Different user interface presentations 84 may be invoked using a Ul generator 85 depending, for example, on the type of display or screen 104 that is utilized by the computing device. For example, an interview screen with many questions or a significant amount of text may be appropriate for a computer, laptop, or tablet screen but such as presentation may be inappropriate for a mobile computing device such as a mobile phone or

Smartphone. In this regard, different interface presentations 84 may be prepared for different types of computing devices 102. The nature of the interface presentation 84 may not only be tied to a particular computing device 102 but different users may be given different interface presentations 84. For example, a taxpayer that is over the age of 60 may be presented with an interview screen that has larger text or different visual cues than a younger user.

[0083] The user interface manager 82, as explained previously, receives non- binding suggestions from the TLA 60. The non-binding suggestions may include a single question or multiple questions that are suggested to be displayed to the taxpayer via the user interface presentation 84. The user interface manager 82, in one aspect of the invention, contains a suggestion resolution element 88, which is responsible for resolving how to respond to the incoming non-binding suggestions 66. For this purpose, the suggestion resolution element 88 may be programmed or configured internally. Alternatively, the suggestion resolution element 88 may access external interaction configuration files. Additional details regarding configuration files and their use may be found in U.S. Patent

Application No. 14/206,834, which is incorporated by reference herein.

[0084] Configuration files specify whether, when and/or how non-binding suggestions are processed. For example, a configuration file may specify a particular priority or sequence of processing non-binding suggestions 66 such as now or immediate, in the current user interface presentation 84 (e.g., interview screen), in the next user interface presentation 84, in a subsequent user interface presentation 84, in a random sequence (e.g., as determined by a random number or sequence generator). As another example, this may involve classifying non-binding suggestions as being ignored. A configuration file may also specify content (e.g., text) of the user interface presentation 84 that is to be generated based at least in part upon a non-binding suggestion 66. [0085] A user interface presentation 84 may comprise pre-programmed interview screens that can be selected and provided to the generator element 85 for providing the resulting user interface presentation 84 or content or sequence of user interface presentations 84 to the user. User interface presentations 84 may also include interview screen templates, which are blank or partially completed interview screens that can be utilized by the generation element 85 to construct a final user interface presentation 84 on the fly during runtime.

[0086] As seen in FIG. 7, the Ul controller 80 interfaces with the shared data store 42 such that data that is entered by a user in response to the user interface presentation 84 can then be transferred or copied to the shared data store 42. The new or updated data is then reflected in the updated instantiated

representation of the schema 44. Typically, although not exclusively, in response to a user interface presentation 84 that is generated (e.g., interview screen), a user inputs data to the tax preparation software 100 using an input device that is associated with the computing device. For example, a taxpayer may use a mouse, finger tap, keyboard, stylus, voice entry, or the like to respond to questions. The taxpayer may also be asked not only to respond to questions but also to include dollar amounts, check or un-check boxes, select one or more options from a pull down menu, select radio buttons, or the like. Free form text entry may also be requested from the taxpayer. For example, with regard to donated goods, the taxpayer may be prompted to explain what the donated goods are and describe the same in sufficient detail to satisfy requirements set by a particular taxing authority. [0087] Still referring to FIG. 7, in one aspect, the TLA 60 outputs a current tax result 65 which can be reflected on a display 104 of a computing device 102, 103. For example, the current tax result 65 may illustrate a tax due amount or a refund amount. The current tax results 65 may also illustrate various other intermediate calculations or operations used to calculate tax liability. For example, AGI or Tl may be illustrated. Deductions (either itemized or standard) may be listed along with personal exemptions. Penalty or tax credits may also be displayed on the computing device 102, 103. This information may be displayed contemporaneously with other information, such as user input information, or user interview questions or prompts or even narrative

explanations.

[0088] The TLA 60 also outputs a tax data that is used to generate the actual tax return (either electronic return or paper return). The return itself can be prepared by the TLA 60 or at the direction of the TLA 60 using, for example, the services engine 90 that is configured to perform a number of tasks or services for the taxpayer. The services engine 90 is operatively coupled to the TLA 60 and is configured to perform a number of tasks or services for the taxpayer. For example, the services engine 90 can include a printing option 92. The printing option 92 may be used to print a copy of a tax return, tax return data, summaries of tax data, reports, tax forms and schedules, and the like. The services engine 90 may also electronically file 94 or e-file a tax return with a tax authority (e.g., federal or state tax authority). Whether a paper or electronic return is filed, data from the shared data store 42 required for particular tax forms, schedules, and the like is transferred over into the desired format. With respect to e-filed tax returns, the tax return may be filed using the MeF web-based system that allows electronic filing of tax returns through the Internet. Of course, other e-filing systems may also be used other than those that rely on the MeF standard. The services engine 90 may also make one or more recommendations 96 based on the run-time data 62 contained in the TLA 60. For instance, the services engine 90 may identify that a taxpayer has incurred penalties for underpayment of estimates taxes and may recommend to the taxpayer to increase his or her withholdings or estimated tax payments for the following tax year. As another example, the services engine 90 may find that a person did not contribute to a retirement plan and may recommend 96 that a taxpayer open an Individual Retirement Account (IRA) or look into contributions in an employer-sponsored retirement plan. The services engine 90 may also include a calculator 98 that can be used to calculate various intermediate calculations used as part of the overall tax calculation algorithm. For example, the calculator 98 can isolate earned income, investment income, deductions, credits, and the like. The calculator 98 can also be used to estimate tax liability based on certain changed assumptions (e.g., how would my taxes change if I was married and filed a joint return?). The calculator 98 may also be used to compare and analyze differences between previous tax years.

[0089] By using calculation graphs 14 to drive tax calculations and tax operations, it is possible to determine interdependencies of the nodes (including tax operations, functional nodes and function nodes) and the year-over-year calculation graphs 14 can be used to readily identify differences and report the same to a user. Differences can be found using commonly used graph isomorphism algorithms over the two respective calculation graphs 14.

[0090] As shown in FIG. 7, the tax preparation system 40 also includes a recommendation engine 210 for determining tax recommendations for a taxpayer. The recommendation engine 210 may operate within the tax preparation software 100, or it may be a separate software application operating independent of the tax preparation software 100, or it may be a separate software program operatively coupled with the tax preparation software 100. As generally described above, the recommendation engine 210 is configured to execute a tax recommendation function which analyzes a calculated tax calculation graph 14, and determines tax recommendations which the taxpayer may implement for a current or future tax year.

[0091 ] The tax preparation system 40 may be configured in various ways to allow a user to utilize the tax recommendation functionality. As some examples, for a web-based tax preparation system 40 in which a user accesses and uses the system 40 through the Internet using a web browser, the user may utilize the tax recommendation function by logging in to the system and then selecting a tax recommendation function. In another way, the tax preparation system 40 may be configured to send an email or other electronic communication to the user asking if the user wants to obtain tax recommendations for the current tax year or a future tax year. The tax recommendation function may also be accessed using text messages, such as SMS or MMS, similar to email. The tax recommendation function may also be configured as a mobile device application, in which the user executes the application on a mobile device such as a smartphone, and the application interfaces with the tax preparation system 40 to utilize the tax estimate function. Accordingly, the tax preparation system 40 is configured with interfaces for any of the various modes of utilizing the tax recommendation function.

[0092] Referring to Fig. 8, in one embodiment, a method 220 for determining a tax recommendation for a taxpayer is shown. At step 222, in order to enable the tax recommendation functionality, the tax preparation system 40 accesses tax data for a taxpayer by any of the methods and data sources 48 as described herein. The system 40 stores the tax data in the shared data store 42. At step 224, the system 40 executes the tax calculation engine 50 to calculate one or more tax calculation graphs 14 using the tax data as described herein.

[0093] At step 226, the system 40 then executes the recommendation engine 210. The recommendation engine 210 is configured to analyze the calculated tax calculation graph(s) 14 to determine one or more tax variables 212 which can affect the tax result of the tax calculation, such as the total tax owed by the taxpayer, the amount of tax payment owed after applying payments previously made, or the tax refund due to the taxpayer. The recommendation engine 210 is configured to traverse the calculation paths of the tax calculation graph(s) 14 to identify nodes (e.g., input nodes 24, function nodes 26 and/or functional nodes 28) on the tax calculation graph(s) 14 which if modified could affect the tax result of the taxpayer. These identified input nodes 24 constitute tax variables 212 which can affect the tax result of the tax calculation.

[0094] The recommendation engine 210 may identify the tax variables 212 by any suitable method. For example, the recommendation engine 210 may traverse the calculation paths of the tax calculation graph(s) 14 and modify a single node and then determine whether modifying the single node affects the tax result. This can be recursively repeated for each of the nodes of the tax calculation graph(s) 14. In the case that is it known that certain nodes are interconnected by a relationship or function such that multiple nodes need to be modified in order to affect the tax result, the recommendation engine 210 may be configured to modify the multiple nodes together to determine whether such nodes are tax variables 212 which can affect the tax result.

[0095] At step 230, the recommendation engine 210 is further configured to analyze the identified tax variables 212 to determine which of the tax variables 212 is controllable by the taxpayer, referred to as taxpayer controllable variables 214. As used herein, the term "controllable" with respect to taxpayer controllable variables 214 means the tax variable is reasonably controllable by the taxpayer based on a controllability model 216, as described below. For instance, some tax variables are more controllable by the taxpayer, such as retirement account contributions, capital gains and losses, and retirement account withdrawals. On the other hand, some tax variables are impracticable or even impossible to control by the taxpayer, such as age, address, and income, or may be

undesirable to modify, such as marital status, income, self-employment status, and the like. These examples are only illustrative and are not intended to be limitations on the tax variables and their controllability.

[0096] The recommendation engine 210 utilizes a controllability model 216 to determine which of the tax variables 212 is a taxpayer controllable variable 214. The controllability model 216 may be a chart, formula, table or other model which relates each tax variables to a level of controllability by a taxpayer. As an example, tax variables like retirement account contributions, capital gains and losses, and retirement account withdrawals may be given a high level of controllability, while tax variables like age, address, income, number of children, and number of dependents may be given a low level of controllability. The level of controllability may vary from a high level indicating controllable by all or most taxpayers to a low level indicating impossible for a taxpayer to control, and various levels in-between. Alternatively, the controllability model may simply be binary by assigning each tax variable as either controllable or not controllable. FIG. 9 is a graphic representation of a controllability model 216 in which the X- axis lists the tax variables and the Y-axis indicates the level of controllability by the taxpayer. The controllability model 216 may be a heuristic model developed and modified from empirical data, such as from a database of tax return data, a model based on analysis of each tax variable, or a combination thereof.

[0097] The controllability model 216 may be generated by, and/or based upon, human analysis, computer analysis of data, or a combination of both. For example, in one embodiment, a controllability modeling module may compute and generate a controllability model using the schema of the system 40 and a database of tax data using the method 400 as shown in the flow chart of Fig. 14. The method 400 may utilize tax data tax data compiled from previously filed tax returns. The controllability modeling module may be a component of the system 40, or it may be a separate and distinct software program. At step 402 of method 400, the controllability modeling module identifies all of the tax concepts that are user inputs, such as by analyzing the calculation graphs 14 and identifying all input nodes 24, which are all of the possible tax variables 212. At step 404, the controllability modeling module collects a data set of tax data for multiple tax years, which may include millions of data profiles (e.g., previously filed tax returns or tax data for previously filed tax returns) for each tax year. At step 406, for each user input, the module computes how likely the tax variable is changed for a taxpayer from a first tax year to the next tax year, such as a ratio of the data profiles having a change in a tax variable from a first tax year to the next tax year over the total number of data profiles for a number of years of tax data.

[0098] In one embodiment, the controllability modeling module may determine the ratio by analyzing the data set for the value of a particular tax variable 212 for each of the data profiles and the change in the tax variable 212 for each tax profile from a first tax year to the next tax year. The change may be analyzed for a particular number of tax years, or for all tax years for which data is available, depending on the characteristics of the user input. Then, the module determines how many of the data profiles have a the change in the tax

variable 212 from a first tax year to the next tax year. The module then determines the ratio by dividing the number of data profiles having a change in the tax variable by the total number of relevant data profiles. The total number of relevant data profiles may be all of the data profiles analyzed for the particular tax variable. Alternatively, the total number of relevant data profiles may only include those data profiles having a threshold value for the tax variable or the change in the tax variable.

[0099] The operation of the controllability modeling module will now be described for the controllability of the tax variable 212 for the "number of dependents" using a hypothetical example. Assume a data set of data profiles having 5 years of tax data for 30 million taxpayers, resulting in 150 million data profiles. For each taxpayer, the controllability modeling module determines the number of changes of the value for the number of dependents from one tax year to the next tax year for each of the five tax years. For instance, for a particular taxpayer, the number of dependents changes from 0 to 1 from tax year 1 to tax year 2, and changes from 1 to 2 from tax year 3 to tax year 4. This results in 2 changes in the tax variable over 5 years. This is repeated for each of the taxpayers (30 million taxpayers in this example). Then, the controllability value for the controllability model 216 is calculated as the total sum of the number of changes divided by the total number of data profiles (150 million in this example). If a threshold is utilized, the denominator for the controllability value is the number of data profiles which have a change in the number of dependents which meets the threshold (or depending on the type of threshold, data profiles of only those taxpayers which meet the threshold). [00100] Alternatively, or in addition to the process described above, the recommendation engine 210 may determine the taxpayer controllable variables 214 by asking the user to identify which of the tax variables 212 is a taxpayer controllable variable 214. The recommendation engine 216 may provide a list of the tax variables 212 to the user, and then the user may select which of the tax variables 212 are taxpayer controllable. The recommendation engine 210 receives the user's selections and identifies (determines) the selected tax variables 212 as taxpayer controllable variables 214.

[00101 ] At step 232, the recommendation engine 210 then determines an effect of the taxpayer controllable variables 214 on the tax result. The

recommendation engine 210 determines the effect of the taxpayer controllable variables by executing the tax calculation engine to calculate the tax calculation graph by varying the taxpayer controllable variables 214 and determining the effect on the tax result. In one method, the recommendation engine 210 varies one taxpayer controllable 214 up and down around a known or estimated value while keeping the other variables constant, and then calculating the tax calculation graph(s) 14 to determine the effect on the tax result. The

recommendation engine 210 may vary each taxpayer controllable variable 214 according to an adjustability model 218. The adjustability model 218 provides the recommendation engine 210 with the varying values for each of the taxpayer controllable variables 214 to be input into the tax calculation graph(s) 14 to determine the effect on the tax result. The adjustability model 218 relates a distribution range for each of the tax variables 212 to the tax data for the taxpayer and/or typical, average or mean values based on tax data from tax returns for a large sampling of taxpayers. For example, if the taxpayer has a known value for a particular tax variable, the adjustability model 218 will output to the recommendation engine 210 a range of values for each of the taxpayer controllable variables 214 about the known value such that the range includes the most common sampling of values for the tax variable based upon the tax returns for a large sampling of taxpayers. Many of the tax variables will have a bell curve of values from the large sampling of taxpayers, such that the range can be determined by including one, two, three or other number of standard deviations about the known value for the taxpayer. For tax variables in which the taxpayer does not have a known value, the adjustability model 218 provides a range about an average or median value for the tax variable based on the sampling of taxpayers. In addition, the range and number of varying values used for estimated values may be much larger than for known values. For instance, the adustability model 218 may provide 10-20 or more values in a range for a tax variable having a known value for the taxpayer, and 100-300 or more values in a range for a taxpayer controllable variable 214 based on an estimate for taxpayer. The process of step 232 using the adustability model 218 may also be utilized in step 230 for determining which of the tax variables 212 is a user controllable tax variable 214. In other words, the recommendation engine 210 can determine the effect on the tax result in varying the tax variables 212 using the adjustability model 218 to determine which of the tax variables 212 is a user controllable tax variable 214. For example, the recommendation engine 210 can require that the tax variable have a threshold potential effect on the tax result in order to determine that a tax variable 212 is user controllable tax variable

[00102] At step 234, the recommendation engine 210 may further determine the taxpayer controllable variables 214 by allowing the user to select the taxpayer controllable variables 214 of interest from the taxpayer controllable variables 214 determined as described above. The system 40 provides the taxpayer controllable variables 214 to the user by displaying them to the user, such as in a list, table, etc. The system 40 may provide the taxpayer controllable variables 214 to the user by utilizing the Ul control 80 (or components thereof), as described above. The system 40 requests the user to select one or more of the taxpayer controllable variables 214. The user selects the desired taxpayer controllable variables 214, and the system 40 receives the user's selection of one or more of the taxpayer controllable variables 214. This step 234 can be executed before or after determining the effect of the taxpayer controllable variables 214 on the tax result at step 232. If step 234 is executed before step 232, then step 232 is performed using only the user selected taxpayer

controllable variables 214. If step 234 is executed after step 232, then the user may have the benefit of narrowing the taxpayer controllable variables 214 before the recommendation engine 210 determines the tax recommendations, as described below. At step 234, the system may also prompt the user to provide a change estimate or prediction of how much each taxpayer controller variable will change. The system receives the selections and/or estimates from the user. The recommendation engine then utilizes only the taxpayer controllable variables selected by the user in executing the tax calculation engine to calculate the tax calculation graph by varying the taxpayer controllable variables to determine an effect on the tax result by varying the taxpayer controllable variables. If provided, the recommendation engine also utilizes the change estimates in determining the effect on the tax result, as described above for step 232.

[00103] Still referring to Fig. 8, at step 236, the recommendation engine 210 determines one or more tax recommendations for the taxpayer. The

recommendation engine 210 may determine the tax recommendations by utilizing the determined effect on the tax result of each of the taxpayer

controllable variables 214 at step 232 and identifying which of the taxpayer controllable variables 214 have the desirable effect on the tax result, such as reducing the total tax owed, reducing the tax payment remaining, and/or increasing the tax refund for the taxpayer. The recommendation engine 210 also determines the range of effect on the tax result over the range used to determine the effect on the tax result in step 232.

[00104] The recommendation engine 210 may also generate a tax

recommendation item for each tax recommendation, in which the tax

recommendation item includes additional data and/or information in addition to the tax recommendation. For example, the tax recommendation item may include meta data, a recommendation excerpt and a confidence score indicating a measure of how likely the tax recommendation is to be implemented by the taxpayer. The meta data may include such data as a recommendation scenario identification (e.g., an identification number or code), the names of the models used to generate the recommendation, additional explanation of the recommendation, hyperlinks to IRS documents or pages of the tax preparation application, etc.).

[00105] The confidence score indicates a measure of how likely the tax recommendation is to be implemented by the taxpayer, i.e., how likely the taxpayer will implement the particular tax recommendation. The confidence score is in general determined by a recommendation generation algorithm, and depending on the mathematical model the algorithm applies, there are many ways of determining a confidence score. For example, one simplistic way of determining the confidence score could be based on some expert crafted rules, so that these score are determined by experts in the tax field. The confidence score may be in relative terms, such as low, medium, and high, and so on, or numerical scores, such as on a scale of 0 to 1 , with 0 being zero percent confidence and 1 being 100% confidence. A more sophisticated system may utilize an algorithm to determine the confidence score. For example, a taxpayer's tax situation can be clustered with other similar taxpayers, and then it is determined how likely a particular recommendation is taken by that collection of taxpayers. For example, assume the algorithm uses zip-code, age, profession, and AGI as the parameters to cluster the taxpayers. Then, the taxpayer being analyzed may be assigned to a cluster of say 50,000 samples, where each sample represents a tax return. If the recommendation engine 210 is analyzing a tax variable 212 for increasing the taxpayer's charitable donation, the algorithm statistically collects the distribution of charitable donations from all the other taxpayers in the cluster. Assuming the result is represented by a probability distribution function ("PDF") "f," and the taxpayer's donation is an amount "X," then by checking X against f, the algorithm obtains a relative measure of the confidence score of the recommendation to modify the taxpayer's charitable donation. For instance, if X is on the far right end of the curve (i.e. F(X) is almost 1 ), the confidence score is low because the taxpayer is already making a charitable donation at the high end of the distribution of similar taxpayers. This indicates that recommending the taxpayer to donate more may not be an appealing idea. Contrastingly, if X is located on the far left side (i.e. F(X) is close to 0), the confidence score is high because the taxpayer has a charitable donation that is on the low end of the distribution of similarly situated taxpayers. This indicates that recommending the taxpayer to increase charitable donations is more likely a good idea, and the confidence score is high. Based on these relationships, the algorithm can be used to generate a confidence score for a tax recommendation. In a practical system, the aforementioned PDF can be approximated with one or more Gaussian distributions each with a mean and a variance. Such approximations will make the above computation more intensive during the modeling phase, but much more straightforward during runtime, since the system can leverage the confidence interval which can be derived from the mean and the variance.

[00106] In another aspect, at step 238 the system 40 requests and receives from the user a target tax result for the taxpayer. For example, the target tax result may be a specific total tax owed, a specific total remaining tax payment or specific tax refund. This step 238 may be performed at any point in the method 220, but if the target tax result is used in step 236 to determine the tax

recommendation, then step 238 must be performed at least prior to step 238. The target tax result may be utilized by the recommendation engine 210 to determine the tax recommendations. The recommendation engine 210 analyzes the user controllable variables 214 and determines values and/or ranges of values for the user controllable variables 214 to obtain the target tax result, or at least come closest to the target tax result. In the case of multiple user controllable variables 214, there may be a target range for each of the user controllable variables which obtains the target tax result. Accordingly, in the case of multiple user controllable variables 214, the recommendation engine 210 may perform a multi-variant analysis. The recommendation engine 210 may determine a midpoint value within a target range for each of the user controllable variables which obtains the target tax result. As described in more detail below, the system 40 may then allow the user to adjust the values of each of the user controllable variables 214 within the target range, and when one of the values is adjusted, the values of the other user controllable variables 214 adjusts accordingly to obtain the target tax result.

[00107] At step 240, the recommendation engine 210 (and/or system 40) provides the tax recommendations to the user. In one embodiment, the system 40 may provide the tax recommendations to the user by utilizing the Ul control 80 (or components thereof) (see Fig. 7), or in another embodiment described below, by utilizing a recommendation service 21 1 (see Fig. 15). [00108] For instance, Fig. 16 shows a method 260 for providing the tax recommendations to the user using the user interface manager 82. In this embodiment, the user interface manager 82 includes a recommendation processing module 250 (see Fig. 7). The system 40 provides the tax

recommendations to a user by providing the tax recommendations determined at step 236 to the recommendation processing module 250 of the user interface manager 82 of the Ul control 80. At step 262, the recommendation processing module 250 accesses or receives the tax recommendation items from the recommendation engine 210. At step 264, the recommendation processing module 250 processes the tax recommendation items and generates an appropriate user interface presentation 84 for displaying the tax

recommendations to the user. At step 270, the system 40 then displays the user interface presentation 84 to the user.

[00109] In additional features, the recommendation processing module 250 may perform one or more processes on the tax recommendation items in order to generate the user interface presentation. At step 266, the recommendation processing module 250 sorts the tax recommendations by confidence score, such as from lowest confidence score to highest confidence score, or vice versa. In addition, at step 267, the recommendation processing module 250 may filter out tax recommendations having a confidence score below a threshold value. This can reduce the number of tax recommendations provided to the user by ignoring tax recommendations which have a low confidence score, i.e. they are not likely to be implemented by the taxpayer. At step 268, the recommendation processing module 250 may also integrate one or more of hyperlinks, images and explanations of the tax recommendations into the user interface presentation 84. For example, at step 242 of method 220, the system 40 may generate explanations which provide one or more of a description of the tax

recommendation, how it applies to the taxpayer, and how it can improve the taxpayer's tax return.

[001 10] In another embodiment, FIG. 17 shows a method 288 in which the tax recommendations are provided to the user in a year round recurring, updating process which updates the tax recommendations based on updates to a taxpayer's tax data profile and/or updates to a tax knowledge base based on changes in the tax laws and tax codes. Referring now to FIG. 15, a schematic diagram of a tax recommendation system 252 (or subsystem 252) for providing recurring, updated tax recommendations is shown. The tax recommendation system 252 may be a stand-alone system which is operably coupled to the tax preparation system 40, or it may be a subsystem of the tax preparation system 40 which utilizes the common components shown in Fig. 7 (in which same or like components have the same reference number). For example, as shown in Fig. 7, the recommendation service 282, recommendation database 280, and tax knowledge base 284 may be components of the tax preparation system 40. Still, in other embodiments (e.g., see FIG. 15), the recommendation service 282, recommendation database 280 and/or tax knowledge base 284 may be components separate from the system 40, but in operable communication with the system 40 through appropriate communication networking. The recommendation database 280 and the recommendation service 282 are in operable communication such as through a communication network.

[001 1 1 ] Referring to FIGS. 15 and 17, at step 289, the recommendation engine 210 provides the tax recommendations items to the recommendation database 280. The recommendation database 280 stores the tax

recommendations. At step 290, the recommendation service 282 accesses the tax recommendation items from the recommendation database 280. Then, at step 291 , the recommendation service 282 processes the tax recommendation items for dispatching to the user. At step 295, the recommendation service dispatches the tax recommendations to the user 286. Similar to the

recommendation processing module 250 of the user interface manager 82, the recommendation service 282 may be configured to generate an appropriate user interface presentation 84 for displaying the tax recommendations to the user. The recommendation service 282 is configured to dispatch the tax

recommendations to the user by any suitable means, such as via email, text message, mobile application, an alert or reminder regarding the tax

recommendations or deadlines regarding the tax recommendations.

[001 12] At step 296, the tax knowledge base 284 receives updated tax rules and the system 40 updates the tax calculation graph(s) 14 and other

components, such as the completion graph(s) 12 to reflect the updated tax rules. The updated tax rules may be received from any suitable source, such as the relevant tax agency, a tax law update service, or other source. At step 297, the system 40 also receives updated taxpayer tax data, such as updates to the taxpayer's tax situation, and/or feedback regarding the taxpayer implementing one or more of the tax recommendations. The updated taxpayer tax data may be received and/or accessed from any suitable source, such as a user inputting the data using the system 40, the system 40 automatically accessing the updated taxpayer tax data from a database having taxpayer tax data, such as databases for financial accounts of the taxpayer, a personal finance management application, or other suitable source.

[001 13] At step 298, the recommendation engine 210 determines updated tax recommendations and generates updated tax recommendation items for each updated tax recommendation based at least in part on the updated tax rules and/or updated taxpayer tax data, such as feedback regarding the taxpayer implementing one or more of the tax recommendations.

[001 14] At step 299, the recommendation service 282 provides the updated tax recommendations to the user, same or similar to step 294.

[001 15] Similar to the recommendation processing module 250, the

recommendation service 282 may perform one or more processes on the tax recommendation items in order to provide the tax recommendations to the user and/or generate the user interface presentation 84. At step 291 , the

recommendation service 282 sorts the tax recommendations by confidence score, such as from lowest confidence score to highest confidence score, or vice versa. In addition, at step 292, the recommendation service 282 may filter out tax recommendations having a confidence score below a threshold value. This can reduce the number of tax recommendations provided to the user by ignoring tax recommendations which have a low confidence score, i.e. they are not likely to be implemented by the taxpayer. At step 293, the recommendation

processing module 250 may also integrate one or more of hyperlinks, images and explanations of the tax recommendations into the user interface presentation 84. The explanations may be generated at step 242 of method 220. The explanations provide one or more of a description of the tax recommendation, how it applies to the taxpayer, and how it can improve the taxpayer's tax return.

[001 16] In any of the embodiments for providing the tax recommendations to the user as described above, the tax recommendations may be provided to the user in the form of adjustable input value controls 21 1 (see FIG. 10). The input value controls 21 1 identify the taxpayer controllable tax variable 214, a

recommended value 213 for the taxpayer controllable tax variable 214, and a control for adjusting the input value for the taxpayer controllable tax variable. As shown in Fig. 10, the input value control 21 1 may be a slider 21 1 which the user can slide left or right (or up or down, depending on the desired configuration) to adjust the input value for the respective taxpayer controllable variable 214. In the case of target tax result as described, when one of the sliders 21 1 is adjusted to adjust the input value for one of the taxpayer controllable variables 214, the values and sliders 21 1 for one or more of the other taxpayer controllable variables 214 may also adjust to obtain the target tax result 215. The sliders 21 1 may also have a selectable lock 217 to lock the slider 21 1 from adjusting when one of the other sliders 21 1 is adjusted. This way, the user can set one or more of the values for the taxpayer controllable variables 214 on the sliders 21 1 and the recommendation engine 210 will only vary the unlocked taxpayer controllable variables 214 to obtain the target tax result 215.

[001 17] In additional aspects, the tax preparation system 40 may also be configured to assist the user (e.g. taxpayer) in implementing the tax

recommendations. As an example, if a recommendation includes modifying the taxpayer's tax withholding or estimated tax payments, the system 40 asks the user whether the user to schedule revised estimated tax payments to be made from a financial account of the taxpayer at a financial institution, or complete and submit a new form for withholding tax (e.g. form W-4 for U.S. federal withholding tax). When the user selects to schedule estimated tax payment(s) from a financial institution, the system 40 requests the financial account information for making the payment(s), and the date(s) for the payment(s). The system 40 then processes the scheduled estimated tax payments, by any suitable means, such as ACH payments, or other electronic payment system. When the user selects to submit a new withholding form, the system 40 may compute and complete a withholding form for the taxpayer. The system 40 may use the tax

recommendation, as well as any required tax data from the shared data store to compute any schedules and/or worksheets for preparing a withholding form. The system 40 fills in the withholding form and provides it to the user for submission by the taxpayer (usually to the employer or payroll service) or the system may obtain information for submitting the form and submit the withholding form on behalf of the taxpayer. [001 18] Encapsulating the tax code and regulations within calculation graphs 14 results in much improved testability and maintainability of the tax preparation software 100. Software programming errors ("bugs") can be identified more easily when the calculation graphs 14 are used because such bugs can be traced more easily. In addition, updates to the calculation graphs 14 can be readily performed with less effort when tax code or regulations change.

[001 19] Referring now to FIG. 1 1 , a flow chart showing one illustrative method for preparing a tax return and/or obtaining tax recommendations using the tax preparation system 40, according to one embodiment of the invention. In operation of the system 40 to prepare a tax return and/or obtain tax

recommendations, at step 1000, a user initiates the tax preparation software 100 on a computing device 102, 103 as seen, for example, in FIG. 12. The tax preparation software 100 may reside on the actual computing device 102 that the user interfaces with or, alternatively, the tax preparation software 100 may reside on a remote computing device 103 such as a server or the like as illustrated. In such instances, the computing device 102 that is utilized by the user or tax payer communicates via the remote computing device 103 using an application 106 contained on the computing device 102. The tax preparation software 100 may also be run using conventional Internet browser software. Communication between the computing device 102 and the remote computing device 103 may occur over a wide area network such as the Internet. Communication may also occur over a private communication network (e.g., mobile phone network). [00120] At step 1 100, the tax preparation system executes the tax preparation software 100 to gather and/or import tax related information from one or more data sources 48. Tax data may also be input manually with user input 48a.

[00121 ] At step 1200, the tax calculation engine 50 computes one or more tax calculation graphs dynamically based on the then available data at any given instance within the schema 44 in the shared data store 42. In some instances, estimates or educated guesses may be made for missing data. Details regarding how such estimates or educated guesses are done maybe found in U.S. Patent Application No. 14/448,986 which is incorporated by reference as if set forth fully herein.

[00122] At step 1300, the tax logic agent 60 reads the run time data 62 which represents the instantiated representation of the canonical tax schema 44 at runtime.

[00123] At step 1400, the tax logic agent 60 then utilizes the decision tables 30 (or modified completeness model(s) or modified decision table(s)) to generate and send non-binding suggestions 66 to the Ul control 80. Alternatively, at step 1500, the tax logic agent 60 may determine that completeness has been achieved across the tax topics in which case a done instruction may be delivered to the Ul control.

[00124] If not done, at step 1600, the process continues whereby the user interface manager 82 will then process the suggestion(s) 66 using the suggestion resolution element 88 for resolving of how to respond to the incoming non- binding suggestions 66. At step 1700, the user interface manager 82 then generates a user interface presentation 84 to the user whereby the user is presented with one or more prompts. The prompts may include questions, affirmations, confirmations, declaratory statements, and the like. The prompts are displayed on a screen 104 of the computing device 102 whereby the user can then respond to the same by using one or more input devices associated with the computing device 102 (e.g., keyboard, mouse, finger, stylus, voice recognition, etc.).

[00125] At step 1800, the response or responses that are given by the user of the tax preparation software 100 are then written back to the shared data store 42 to thereby update all appropriate fields of the schema 44. The process then continues with operation 1200 and proceeds as explained above until a completeness state has been reached and a done instruction is sent to the Ul control 80.

[00126] The tax preparation system 40 may at any time execute the tax recommendation function, when initiated as described above. When initiated, the system 40 executes the method 220 as described above

[00127] FIG. 13 generally illustrates components of a computing device 102, 103 that may be utilized to execute the software for automatically calculating or determining tax liability and preparing an electronic or paper return based thereon, as well as performing the tax recommendation method 220. The components of the computing device 102 include a memory 300, program instructions 302, a processor or controller 304 to execute program instructions 302, a network or communications interface 306, e.g., for communications with a network or interconnect 308 between such components. The computing device 102, 103 may include a server, a personal computer, laptop, tablet, mobile phone, or other portable electronic device. The memory 300 may be or include one or more of cache, RAM, ROM, SRAM, DRAM, RDRAM, EEPROM and other types of volatile or non-volatile memory capable of storing data. The processor unit 304 may be or include multiple processors, a single threaded processor, a multi-threaded processor, a multi-core processor, or other type of processor capable of processing data. Depending on the particular system component (e.g., whether the component is a computer or a hand held mobile

communications device), the interconnect 308 may include a system bus, LDT, PCI, ISA, or other types of buses, and the communications or network interface may, for example, be an Ethernet interface, a Frame Relay interface, or other interface. The interface 306 may be configured to enable a system component to communicate with other system components across a network which may be a wireless or various other networks. It should be noted that one or more components of the computing device 102, 103 may be located remotely and accessed via a network. Accordingly, the system configuration illustrated in FIG. 13 is provided to generally illustrate how embodiments may be configured and implemented.

[00128] The described embodiments of the present invention, including the functions performed by the system 40 and its components, including the tax recommendation engine 210, may also be embodied in, or readable from, a computer-readable medium or carrier, e.g., one or more of the fixed and/or removable data storage data devices and/or data communications devices connected to a computer. Carriers may be, for example, magnetic storage medium, optical storage medium and magneto-optical storage medium.

Examples of carriers include, but are not limited to, a floppy diskette, a memory stick or a flash drive, CD-R, CD-RW, CD-ROM, DVD-R, DVD-RW, or other carrier now known or later developed capable of storing data. The processor 304 performs steps or executes program instructions 302 within memory 300 and/or embodied on the carrier to implement method embodiments.

[00129] Embodiments, however, are not so limited and implementation of embodiments may vary depending on the platform utilized. Accordingly, embodiments are intended to exemplify alternatives, modifications, and equivalents that may fall within the scope of the claims.