Patent Application
20080010176
Solutions for bonus depreciation records and proposals have been invented. Any number of bonus depreciation transactions can be manually entered against an asset/depreciation book without having any specific bonus depreciation records defined. Manually entered bonus transactions are taken into consideration when calculating additional bonuses through a bonus depreciation proposal process or when doing a depreciation proposal.
A variety of illustrative features and implementations are described herein that help illustrate the inventive subject matter, although that subject matter is broader than can be described herein in complete detail, and is not limited to the particular illustrative examples provided herein.
A user may enter or modify depreciation bonuses as independent transactions, with or without reference to particular assets at the time the depreciation bonuses are set up or modified. The bonus depreciations defined by the user may be stored and may be made available over a network or other distributed utility, for application across a large organization or organizations, including for assets that are entered much later in time and in different locations. This enables flexibility for a user to prepare depreciation solution systems at a time or place independently of entering records for assets or of using proposed bonus depreciations for the assets. It also enables the flexibility to respond quickly and with a generalized solution to changes in tax laws that define the bonus depreciations, which may be frequent, irregular, and unpredictable.
For example, bonus depreciation transactions may be recorded by a tax attorney, and assets may be recorded by a logistics manager in a different department of the organization, months or years after the tax attorney recorded the bonus depreciations, and in a very distant physical location. However, system 10 will compare the newly recorded assets against the recorded user-defined bonus depreciations, select bonus depreciations applicable to the assets, and make proposals for the bonus depreciations to be used in association with those assets, according to the present illustrative embodiment. Those proposals might be made to a third user separated in time and space from the first two users—for example, an accountant in another department, preparing a tax analysis or tax filing for the organization. As another alternative, the bonus depreciation records may be entered manually by an outsourced or specialized tax management service, which share their results by agreement with separate organizations.
The system is also generalized to enable bonus depreciations to be defined with reference to any currency and any jurisdiction's tax laws. Bonus depreciations may also be defined according to a variety of forms; for example, some bonus depreciations may be in the form of a flat amount, while other bonus depreciations may be in the form of a percentage of a value associated with applicable assets. Different bonus depreciations may be applicable to the same assets, and the system enables the flexibility to apply those multiple bonus depreciations, using a prioritization of the bonus depreciations, which is described further below.
One or more bonus depreciations may be applied to an asset, and subtracted from its basis, prior to subtracting an additional regular depreciation, for example. System 10 may include interfaces or forms for a user to enter defining values or parameters, such as basis values, bonus depreciations, and regular depreciations, that are received by a computing device, for example. Bonus depreciations and other data determined by system 10 may be provided on a user output device such as a monitor, or may be incorporated into forms for tax filings, for example. System 10 may function as part of a larger system for generalized tax solutions.
Bonus depreciations are generally taken during the first reporting period that an asset is acquired or placed into service, prior to taking normal depreciation. According to the present illustrative embodiment, system 10 will take that into account by using a default that applies bonus depreciations prior to normal depreciation, and does not apply bonus depreciations to an asset for which depreciation has previously been taken. Another option may be used for applying bonus depreciations to an asset for which normal depreciation has previously been taken. This is sometimes called extraordinary depreciation, but may be applied as another application of user-defined bonus depreciations where the applicable jurisdiction provides for their use.
As depicted in
A user may also define a GroupBonus object 13, defining an asset group, or a BookBonus object 17, defining an accounting book, in this illustrative embodiment. The GroupBonus object 13 is associated with the AssetGroup object 15 and may be used for defaulting bonus depreciation values from Bonus objects 11, AssetGroup objects 15, and/or BookBonus objects 17 associated with the GroupBonus object 13, for example.
GroupBonus objects 13 and BookBonus objects 17 may be used to define asset groups and accounting books, respectively, and bonus depreciations applicable to generalized sets of assets associated with those asset groups and/or accounting books, as in step 24 of method 20 in
AssetGroup object 15 may be used to define a certain type of asset, which has defining characteristics to meet eligibility requirements of a certain bonus depreciation or are otherwise of interest in applying bonus depreciations. For example, one AssetGroup object 15 may be applied to all of the buildings owned by an organization; another AssetGroup object 15 may be applied to all the office furniture owned by the organization; yet another AssetGroup object 15 may be applied to all the motor vehicles owned by the organization, and so forth, in this illustrative embodiment.
Then, one of the AssetGroup objects 15 may be assigned one or more bonus depreciations defined by a user. With the assignment of that one user-defined bonus depreciation to the AssetGroup object 15, and thereby to a particular asset group, corresponding user-defined bonus depreciations can be proposed for or applied to all the assets associated with that asset group. When new assets are entered by the same user or other users associated with the organization, the new assets can be checked for whether they belong to an asset group corresponding to a particular AssetGroup object 15, and if so, the corresponding bonus depreciation or depreciations may automatically be proposed for or applied to those assets as a default, in this illustrative embodiment. Options may also be provided that the user may select to modify or discard the proposed or applied default bonus depreciations for particular assets, without affecting the default bonus depreciations applied to the other assets in that asset group, as in step 26 of method 20 in
Bonus depreciation records can also be associated with a BookBonus object 17, which can be used to apply default bonus depreciations to AssetBook objects 19, associated with assets listed in a particular accounting book. For example, one organization might keep different accounting books with reference to different tax jurisdictions to which it is subject, and among which its assets are distributed. This might involve different accounting books for assets in different countries, or for the accounting for the same assets with reference to state and federal taxes, or for the same assets with reference to an alternative minimum tax (AMT) accounting, for example. As with the asset groups, a user may use a BookBonus object 17 to assign a blanket default bonus depreciation to the particular corresponding accounting book group, and may thereafter modify or discard bonus depreciations proposed for or applied to a particular asset, without disturbing the default bonus depreciations applied to the other assets in the accounting book group.
There are therefore several different ways in which a user may define bonus depreciations for different assets. It may often be the case that two or more different bonus depreciations may apply to the same asset. If the bonus depreciations are of mixed type, for example between flat amounts and percentages, then the order of priority in which the bonus depreciations are applied becomes a non-trivial concern.
As depicted in
In some cases, the priority of order in which bonus depreciations should be applied may be specified by the applicable tax law. In this case, the Priority attributes may be defined to reflect that specification, and ensure that it is carried out in practice, across all assets to which it is applicable as their records are received. In other cases, the priority of order in which bonus depreciations are to be applied may not be specified. In this case, system 10 may calculate which possible prioritization of the user-defined bonus depreciations maximizes the value for the bonus depreciations for the selected asset, and propose or apply the prioritization that yields the maximum bonus depreciations.
For example, an asset group may have two bonus depreciations applicable to it, where one bonus depreciation consists of a flat amount and the other bonus depreciation consists of a percentage. System 10 may then apply the bonus depreciation consisting of the percentage first, and thereafter apply the bonus depreciation consisting of the flat amount, thereby maximizing the total bonus depreciation applied to those assets, because the percentage depreciation is then applied against the full original basis, rather than against the amount reduced by prior application of the flat amount depreciation.
ProposalEngine object 31 may receive a notice to generate AssetBonusTransaction objects 35, corresponding to asset bonus depreciation transactions, to be applied to assets associated with an AssetBook object, for example. The ProposalEngine object 31 may then call the BonusProposalEngine 33, which is associated with a BookBonus object 17, in this illustrative embodiment, and may use the BookBonus object 17 and its own internal rules to calculate the value of each bonus depreciation that may be proposed for the assets under consideration. The BonusProposalEngine object 33 then returns the bonus amount to the ProposalEngine object 31, which then creates an AssetBonusTransaction object 35 that specifically defines the value of the bonus depreciation to be proposed for a corresponding asset.
The system may compare the records of the assets with the asset groups (which may include assets grouped by accounting book, in this example) to select matching bonus depreciations associated with matching asset groups. The system may then propose usage of the matching bonus depreciations with the assets.
The system may subsequently receive records of additional assets with an asset type matching an asset type for one of the before-mentioned assets. The system may then propose that the user-defined bonus depreciations indicated for the before-mentioned assets be applied to the additional asset. A user may accept the new bonus proposal, by default in some implementations, or with modifications. The system may then respond to this acceptance of the proposed bonus depreciations by calculating values for the bonus depreciations for the additional asset.
An example of the use of a bonus depreciation proposal system is provided as follows, according to another illustrative embodiment. In an illustrative tax situation, a user is subject to United States federal tax law, which specifies two different bonus depreciations for federal tax purposes in a given fiscal year.
In this particular example, a user uses an illustrative embodiment to generate a total bonus depreciation amount for a particular commercial building that was first put into service during the fiscal year, with a basis of $550,000. One bonus depreciation is encoded in section 179 of the U.S. Internal Revenue Code for the given year, and specifies a bonus depreciation for qualified property, and provides a flat amount bonus depreciation of $50,000 as applied to this building.
The other applicable bonus depreciation is included in a temporary Recovery Opportunity Act applicable only to the given fiscal year, targeted toward certain asset losses due to a major natural disaster that occurred earlier that year, in the area where the building is located. The damage to the building is such that it qualifies for a 50% bonus depreciation, cumulatively with the section 179 bonus depreciation.
The user may define bonus depreciations corresponding to these applicable authorizations. The user may also create an asset group called Buildings, to which these bonus depreciations are indicated to be applicable. The user may then add this particular building to the Buildings asset group. Near the end of the fiscal year, the user runs the depreciation transaction proposals for a Federal Tax depreciation book, to prepare for related tax filings.
According to one example, the Recovery Opportunity Act specifies that its bonus depreciation can only be applied after any applicable section 179 bonus depreciation. In this case, the system calculates the applicable bonus depreciations for the asset in question, assigning them the prioritization specified by statute, of the section 179 flat amount bonus depreciation first, followed by the percentage bonus depreciation at 50%. After the flat $50,000 is deducted from the basis for the first bonus depreciation, the 50% is applied to the difference of $500,000, for a second bonus depreciation of $250,000, and a sum total bonus depreciation of $300,000. The system proposes this priority of bonus depreciations with this total, which the user may accept, discard, or modify. With the bonus depreciations now exhausted, the system records the building's basis for normal depreciations at $250,000.
In another example, the facts may be the same except that the applicable law does not specify the order of priority in which the two bonus depreciations are to be calculated. In this case, the system may evaluate the available bonus depreciations and propose a set of bonus depreciations with an order of prioritization that maximizes the total bonus depreciation. In this case, the system assigns an earlier priority to the percentage bonus depreciation, and a later priority to the flat amount bonus depreciation. The system therefore calculates the bonus depreciations as $275,000, as 50% of the basis of $550,000, plus the flat amount of $50,000, for a total of $325,000, or a ten percent premium over the total calculated with the reverse order of prioritization.
The system also provides safeguards to ensure that other considerations are taken into account in calculating the bonus depreciations. For example, the system may check whether the calculated value for the bonus depreciation for a selected asset is greater than the value or basis of the selected asset. If it is, then the system resets the value of the bonus depreciation of the selected asset equal to the value of the selected asset, so that the entire value of the asset may be depreciated, but the bonus depreciation cannot actually be greater than the basis of the asset being depreciated.
Various embodiments may run on or be associated with a wide variety of hardware and computing environment elements and systems. For example, a medium readable by a computing device may include executable instructions that configure a computing device to run applications, perform methods, and provide systems associated with different embodiments. Some illustrative features of exemplary embodiments such as are described above may be executed on computing devices such as computer 110 or mobile computing device 201, such as depicted in
Embodiments are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with various embodiments include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, telephony systems, distributed computing environments that include any of the above systems or devices, and the like.
Embodiments may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Various embodiments may be implemented as instructions that are executable by a computing device, which can be embodied on any form of computer readable media discussed below. Various additional embodiments may be implemented as data structures or databases that may be accessed by various computing devices, and that may influence the function of such computing devices. Some embodiments are designed to be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
With reference to
Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 110 through input devices such as a keyboard 162, a microphone 163, and a pointing device 161, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195.
The computer 110 may be operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110. The logical connections depicted in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
Memory 204 is implemented as non-volatile electronic memory such as random access memory (RAM) with a battery back-up module (not shown) such that information stored in memory 204 is not lost when the general power to mobile device 200 is shut down. A portion of memory 204 is illustratively allocated as addressable memory for program execution, while another portion of memory 204 is illustratively used for storage, such as to simulate storage on a disk drive.
Memory 204 includes an operating system 212, application programs 214 as well as an object store 216. During operation, operating system 212 is illustratively executed by processor 202 from memory 204. Operating system 212, in one illustrative embodiment, is a WINDOWS® CE brand operating system commercially available from Microsoft Corporation. Operating system 212 is illustratively designed for mobile devices, and implements database features that can be utilized by applications 214 through a set of exposed application programming interfaces and methods. The objects in object store 216 are maintained by applications 214 and operating system 212, at least partially in response to calls to the exposed application programming interfaces and methods.
Communication interface 208 represents numerous devices and technologies that allow mobile device 200 to send and receive information. The devices include wired and wireless modems, satellite receivers and broadcast tuners to name a few. Mobile device 200 can also be directly connected to a computer to exchange data therewith. In such cases, communication interface 208 can be an infrared transceiver or a serial or parallel communication connection, all of which are capable of transmitting streaming information.
Input/output components 206 include a variety of input devices such as a touch-sensitive screen, buttons, rollers, and a microphone as well as a variety of output devices including an audio generator, a vibrating device, and a display. The devices listed above are by way of example and need not all be present on mobile device 200. In addition, other input/output devices may be attached to or found with mobile device 200.
Mobile computing system 200 also includes network 220. Mobile computing device 201 is illustratively in wireless communication with network 220—which may be the Internet, a wide area network, or a local area network, for example—by sending and receiving electromagnetic signals 299 of a suitable protocol between communication interface 208 and wireless interface 222. Wireless interface 222 may be a wireless hub or cellular antenna, for example, or any other signal interface. Wireless interface 222 in turn provides access via network 220 to a wide array of additional computing resources, illustratively represented by computing resources 224 and 226. Naturally, any number of computing devices in any locations may be in communicative connection with network 220. Computing device 201 is enabled to make use of executable instructions stored on the media of memory component 204, such as executable instructions that configure a computing device to provide solutions for bonus depreciation records and proposals. For example, according to one illustrative embodiment, the executable instructions may enable mobile computing device 201 to receive bonus depreciation transactions, receive records of assets, calculate depreciation values, and propose depreciation values for the assets via a user output, for example.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
