The present disclosure relates to techniques for collecting income-tax information from a user.
Existing income-tax programs that facilitate income-tax preparation typically operate by collecting income-tax information either directly or indirectly from users. For example, a user may provide the income-tax information from forms (such as a W-2 form) by typing it in manually. Alternatively, the user may provide credential information (such as a user name and password) that allows the income-tax information to be downloaded from a payroll company's server. However, this indirect collection technique is not available for many users.
Manually providing income-tax information is a time-consuming and laborious process. Furthermore, because users don't know which data on a given form is relevant, they often provide all the information on the form, which results in wasted effort. In addition, manually provided income-tax information often contains errors that can cause mistakes in users' income-tax returns. However, requiring users to validate all of the data they have provided (such as all of the fields in a W-2 form) is also a time-consuming and laborious process, and the user may not detect all of the errors.
As a consequence, manual entry of income-tax information can adversely impact the user experience, and can result in mistakes in users' income-tax returns. Consequently, manual entry can reduce: customer satisfaction, customer retention, and sales of the income-tax programs.
The disclosed embodiments relate to a computer system that receives income-tax information. During operation, the computer system receives an image of a document from a user. Then, the computer system extracts income-tax information from fields in the document, and determines a subset of the income-tax information which is relevant to an income-tax return of the user based on predefined information for different types of income-tax returns. Next, the computer system provides the subset of the income-tax information to the user for validation. The computer system also receives feedback from the user about the subset of the income-tax information.
Note that the document may include a summary of the income-tax information of the user during a time interval. For example, the document may include a W-2 form. Furthermore, the image may include a photograph of the document, such as an image that is captured using an imaging device on a portable electronic device (e.g., a cellular telephone).
In some embodiments, extracting the income-tax information involves optical character recognition (OCR). Additionally, providing the subset of the income-tax information may involve providing the subset of the income-tax information in a format that is suitable for presentation on a display, such as that of the portable electronic device.
The feedback may include the user's acceptance of the subset of the income-tax information and/or a correction of an error in the subset of the income-tax information. After receiving the feedback, the computer system may populate fields in the income-tax return of the user based on the subset of the income-tax information.
Another embodiment provides a method that includes at least some of the operations performed by the computer system.
Another embodiment provides a computer-program product for use with the computer system. This computer-program product includes instructions for at least some of the operations performed by the computer system.
Table 1 provides relevance criteria for the income-tax information in the fields in a W-2 form in accordance with an embodiment of the present disclosure.
Note that like reference numerals refer to corresponding parts throughout the drawings. Moreover, multiple instances of the same part are designated by a common prefix separated from an instance number by a dash.
Embodiments of a computer system, a technique for receiving income-tax information, and a computer-program product (e.g., software) for use with the computer system are described. This collection technique allows a user (such as a taxpayer) to provide income-tax information by submitting an image of a document, such as an income-tax summary or form. After receiving the image, the income-tax information is extracted from the document, and a subset of the income-tax information that is relevant to the user is determined. This subset of the income-tax information is then provided to the user for validation, and the user subsequently provides feedback about the subset of the income-tax information, such as acceptance of the subset or correction of any errors. Furthermore, after receiving the user feedback, fields in an income-tax return of the user may be populated using the subset of the income-tax information.
By facilitating collection of the subset of the income-tax information, this technique may make it easier for users to accurately and efficiently complete their income-tax returns. For example, the users may only have to validate the subset of the income-tax information (as opposed to all of the income-tax information). When included in income-tax software, this capability may: reduce mistakes in income-tax returns, increase sales, improve customer satisfaction and/or increase customer retention.
In the discussion that follows, the users may include a variety of entities, such as: an individual, an organization, a business and/or a government agency. Furthermore, a ‘business’ should be understood to include: for-profit corporations, non-profit corporations, organizations, groups of individuals, sole proprietors, government agencies, partnerships, limited liability corporations, etc.
Note that in the discussion that follows an image of a document is used to submit or provide the income-tax information. However, in other embodiments the income-tax information can be provided using a wide variety of formats and techniques, including: user-entered text or alpha-numeric characters, voice, video and/or data in a computer-readable electronic format (such as an electronic data stream).
We now describe embodiments of the collection technique.
Then, the computer system extracts income-tax information from fields in the document (operation 112), and determines a subset of the income-tax information which is relevant to an income-tax return of the user based on predefined information for different types of income-tax returns (operation 114).
For example, extracting the income-tax information may involve optical character recognition (OCR).
Next, the computer system provides the subset of the income-tax information to the user for validation (operation 116), and receives feedback from the user about the subset of the income-tax information (operation 118). Note that providing the subset of the income-tax information may involve providing the subset of the income-tax information in a format that is suitable for presentation on a display, such as that of the portable electronic device. Furthermore, the feedback may include the user's acceptance of the subset of the income-tax information and/or a correction of one or more errors in the subset of the income-tax information.
After receiving the feedback, the computer system may optionally populate fields in the income-tax return of the user based on the subset of the income-tax information (operation 120).
In an exemplary embodiment, the collection technique is implemented using an electronic device (such as a client computer or the portable electronic device) and at least one server computer, which communicate through a network, such as the Internet (i.e., using a client-server architecture). This is illustrated in
Next, server computer 212 provides the subset of the income-tax information to electronic device 210 for validation (operation 224). After electronic device 210 receives the subset of the income-tax information (operation 226), the user provides feedback to electronic device 210 (operation 228). This feedback is, in turn, provided by electronic device 210 to server computer 212 (operation 230).
After receiving the feedback (operation 232), server computer 212 may optionally correct any identified errors in the subset of the income-tax information (operation 234) and/or may optionally populate fields in the income-tax return of the user based on the subset of the income-tax information (operation 236).
In some embodiments of method 100 (
In an exemplary embodiment, a user uploads a picture or a scanned image of an income-tax document (such as a W-2 form or, more generally, any income-tax-related document) to a computer or a server that is operated by a provider of the income-tax software. However, in some embodiments the user provides the original document to the provider of the income-tax software, and the information in this document is subsequently scanned in. After receiving the image, the income-tax information in the income-tax document is obtained, for example by using an OCR engine (such as FlexiCapture OCR software from ABBYY Software House, Inc. of Moscow, Russia).
Furthermore, the user's tax situation or circumstance is assessed based on the income-tax information and/or based on answers to questions from the income-tax program that are provided by the user (such as the user's income level, etc.) so that the user can be assigned to a particular income-tax category or type of income-tax return (including the associated income-tax return forms). For example, the user may be a simple income-tax filer who will use the 1040EZ form, if: the user's income level is currently less than $80,000 for single filers (or $100,000 for married filers) so that they most likely will not be itemizing their deductions; and/or they did not hit the Social Security tax limit ($105,000 in 2009) or the sum of individual local/state tax limits (such as the current $90,669 State Disability Insurance limit in California).
Based on this classification, an income-tax analysis engine determines a subset of the income-tax information in the income-tax document that is relevant to the user's income-tax return (and the 1040EZ form). For example, Table 1 summarizes relevance criteria for the income-tax information in the fields in a W-2 form for a general tax return (including that for the 1040EZ) form for a particular user (who has a given income level and demographic group) based on current income-tax law. In particular, Table 1 delineates the fields in the W-2 form that are: required, conditionally required, or not required at all for accurate and compliant income-tax calculations. Note that validation of some fields may be required if they are read using OCR, such as: Box 7, Box 8, Box 9, Box 10, Box 11, Boxes 12a-12d and Box 14.
The income-tax analysis engine may then present the subset of the income-tax information to the user for review. In this way, the user is not forced to evaluate all the fields in the W-2 form, which: reduces the review time and effort, simplifies the overall process (because the user no longer has to understand which fields are important for their income-tax return), and focuses the user's attention on the relevant income-tax information (which may increase the likelihood that the user identifies any errors that occurred during processing, such as during the OCR). After reviewing the subset of the income-tax information, the user can provide feedback, such as validation (i.e., that the subset of the income-tax information is correct) and/or correction of any errors.
In some embodiments, the user provides the picture of the income-tax return using a camera in a cellular telephone. In addition, the subset of the income-tax information may be presented to the user for review using a user interface that is displayed on the cellular telephone (and, more generally, on a display on an electronic device, such as a computer). This is shown in
We now describe embodiments of the computer system and its use.
In some embodiments, at least a portion of the income-tax software may be an application tool (such as an income-tax application tool) that is embedded in the web page (and which executes in a virtual environment of the web browser). In an illustrative embodiment, the income-tax application tool is a software package written in: JavaScript™ (a trademark of Oracle Corporation), e.g., the income-tax application tool includes programs or procedures containing JavaScript instructions, ECMAScript (the specification for which is published by the European Computer Manufacturers Association International), VBScript™ (a trademark of Microsoft Corporation) or any other client-side scripting language.
In other words, the embedded income-tax application tool may include programs or procedures containing: JavaScript, ECMAScript instructions, VBScript instructions, or instructions in another programming language suitable for rendering by the web browser or another client application (such as on computer 410). Thus, the income-tax application tool may be provided to the user via a client-server architecture.
As discussed previously, the user may provide an image of the income-tax document to server 414 via network 412, for example, the user may upload a picture of the income-tax document from computer 410. Then, an extraction engine or module 416 (such as an OCR engine) may extract the income-tax information from the image, and an analysis engine or module 418 may determine the subset of the income-tax information based on: the user's tax circumstances, predefined information for the associated income-tax return forms (which are associated with different types of income-tax returns), and/or the income-tax information in the income-tax document. Next, server 414 may provide the subset of the income-tax information back to the computer 410 via network 412 for review and either validation or correction by the user. Once the subset of the income-tax information has been validated, it may be used to populate fields in an income-tax return of the user.
Note that the information in computer system 400 (such as the information about the user's tax circumstances and the predefined information for the income-tax return forms) may be stored at one or more locations in computer system 400 (i.e., locally or remotely). Moreover, because this information may be sensitive in nature, it may be encrypted. For example, stored information and/or information communicated via network 412 may be encrypted.
Memory 524 in computer system 500 may include volatile memory and/or non-volatile memory. More specifically, memory 524 may include: ROM, RAM, EPROM, EEPROM, flash memory, one or more smart cards, one or more magnetic disc storage devices, and/or one or more optical storage devices. Memory 524 may store an operating system 526 that includes procedures (or a set of instructions) for handling various basic system services for performing hardware-dependent tasks. Memory 524 may also store procedures (or a set of instructions) in a communication module 528. These communication procedures may be used for communicating with one or more computers and/or servers, including computers and/or servers that are remotely located with respect to computer system 500.
Memory 524 may also include multiple program modules (or sets of instructions), including: income-tax software 530 (or a set of instructions), extraction module 416 (or a set of instructions), analysis module 418 (or a set of instructions), review module 532 (or a set of instructions), encryption module 550 (or a set of instructions), financial software 552 (or a set of instructions) and/or e-file service 554 (or a set of instructions). Note that one or more of these program modules (or sets of instructions) may constitute a computer-program mechanism.
During method 100 (
Next, review module 532 may communicate subset of the income-tax information 538 to the user for review. In response, the user may provide feedback 546, such as validation of subset of the income-tax information 538 and/or correction of any identified errors. After validation and/or correction of any errors, subset of the income-tax information 538 may be used to populate fields in the user's income-tax return 548. In some embodiments, e-file service 554 subsequently files the user's income-tax return 548 after it is completed by the user.
Furthermore, because the information about the user's income-tax information may be sensitive in nature, in some embodiments at least some of the information stored in memory 524 and/or at least some of the information communicated using communication module 528 is encrypted using encryption module 550. Additionally, in some embodiments one or more of the modules in memory 524 may be included in financial software 552.
Instructions in the various modules in memory 524 may be implemented in: a high-level procedural language, an object-oriented programming language, and/or in an assembly or machine language. Note that the programming language may be compiled or interpreted, e.g., configurable or configured, to be executed by the one or more processors 510.
Although computer system 500 is illustrated as having a number of discrete items,
Computers and servers in computer systems 400 (
In exemplary embodiments, the financial-software application (i.e., financial software 552) includes: Quicken™ and/or TurboTax™ (from Intuit, Inc., of Mountain View, Calif.), Microsoft Money™ (from Microsoft Corporation, of Redmond, Wash.), SplashMoney™ (from SplashData, Inc., of Los Gatos, Calif.), Mvelopes™ (from In2M, Inc., of Draper, Utah), and/or open-source applications such as Gnucash™, PLCash™, Budget™ (from Snowmint Creative Solutions, LLC, of St. Paul, Minn.), and/or other planning software capable of processing financial information.
Moreover, the financial-software application may include software such as: QuickBooks™ (from Intuit, Inc., of Mountain View, Calif.), Peachtree™ (from The Sage Group PLC, of Newcastle Upon Tyne, the United Kingdom), Peachtree Complete™ (from The Sage Group PLC, of Newcastle Upon Tyne, the United Kingdom), MYOB Business Essentials™ (from MYOB US, Inc., of Rockaway, N.J.), NetSuite Small Business Accounting™ (from NetSuite, Inc., of San Mateo, Calif.), Cougar Mountain™ (from Cougar Mountain Software, of Boise, Id.), Microsoft Office Accounting™ (from Microsoft Corporation, of Redmond, Wash.), Simply Accounting™ (from The Sage Group PLC, of Newcastle Upon Tyne, the United Kingdom), CYMA IV Accounting™ (from CYMA Systems, Inc., of Tempe, Ariz.), DacEasy™ (from Sage Software SB, Inc., of Lawrenceville, Ga.), Microsoft Money™ (from Microsoft Corporation, of Redmond, Wash.), Tally.ERP (from Tally Solutions, Ltd., of Bangalore, India) and/or other payroll or accounting software capable of processing payroll information.
User interface 300 (
While the preceding embodiments illustrate the use of the collection technique with income-tax information (and, more generally, financial information), this technique may be used with a wide variety of information in a diverse group of applications (and associated forms), including: loan information for use in a loan form, insurance information for use in an insurance form, immigration information for use in an immigration form, etc. Thus, if information for use in a form is extracted using OCR or an automated-data-input technique, knowledge about predefined information in this form (such as the format of the form) and/or the circumstances of a given user may be used restrict or limit the amount of information that is subsequently verified by this user.
The foregoing description is intended to enable any person skilled in the art to make and use the disclosure, and is provided in the context of a I-cular application and its requirements. Moreover, the foregoing descriptions of embodiments of the present disclosure have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present disclosure to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Additionally, the discussion of the preceding embodiments is not intended to limit the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.