USH1830H - System for use-tax determination - Google Patents

System for use-tax determination Download PDF

Info

Publication number
USH1830H
USH1830H US08/877,785 US87778597A USH1830H US H1830 H USH1830 H US H1830H US 87778597 A US87778597 A US 87778597A US H1830 H USH1830 H US H1830H
Authority
US
United States
Prior art keywords
tax
data
computer
data elements
logic
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US08/877,785
Inventor
Rosalyn A. Petrimoulx
Tamara Marie Wellington
Nancy Lou Huey Kanter
Maria Dalia Montague
David Joseph Burgie
Patrick A. Carey
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dow Chemical Co
Original Assignee
Dow Chemical Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dow Chemical Co filed Critical Dow Chemical Co
Priority to US08/877,785 priority Critical patent/USH1830H/en
Application granted granted Critical
Publication of USH1830H publication Critical patent/USH1830H/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • This invention relates to computer-implemented tax preparation and tax submission accounting. Specifically, this invention is directed to providing a system which enables use-tax accrual and determination.
  • Sales taxes and use-taxes need to be defined and paid by business enterprises in the course of their operations.
  • proper and efficient fulfillment of this requirement by a business enterprise executing multiple-location operations requires substantial expenditure of effort, resources, and time as a plurality of tax situations respective to different jurisdictional entities such as states, counties, cities, towns, and townships compel ongoing attention.
  • jurisdictional entities have effective tax rates respective to the purpose for which items and services are acquired; in this regard, jurisdictions extend certain implicit "use-tax" incentives to influence and encourage certain types of activities (e.g. investment in projects which enhance environmental quality, expansion of the business enterprise base of the jurisdiction by encouraging industrial processing within that jurisdiction, and cooperative support with the jurisdiction of socially beneficial initiatives).
  • CLR/ Fast-Tax CLR Fast-Tax Corporation of Carrollton, Texas
  • a product having both a file showing current tax rate information and a computer-implemented program for determining a proper allocation of taxes to different relevant jurisdictions respective to a location e.g.
  • Cost Object is a datalogical accounting entity which functions as a logical identifier for an accounting domain and can also be virtually used to reference the accounting domain with which it is affiliated.
  • a cost object has a relationship to an accounting domain which is similar to the relationship of a person to the name (or a portion of the name) by which they are identified.
  • a cost object or combination of cost objects assist accounting personnel in defining a meaningful and useful detailed purpose for a transaction or set of transactions.
  • the set of cost objects used in an accounting system ultimately must enable account specificity which is of sufficient detail to enable achievement of all reporting obligations and needs in the business enterprise.
  • Order Type is an accounting cost object which is referenced in conjunction with an account used to collect costs for "short term items" or for accounting entities useful to a business enterprise which have two key attributes of (a) an initiating moment of time and (b) an (at least presumed) ending moment of time.
  • Examples of Order Types are (1) an addition to a building or remodeling of a plant used to make a product; (2) a set of costs connected to a batch (also known as a lot) of manufactured material which has a set of attributes (e.g.
  • test results or records relating to manufacturing conditions helping to distinguish it as a separate entity for record-keeping purposes
  • a Project or Project Account is an Order Type accounting cost object which is frequently distinguished from other Order Types because it is affiliated with a defined amount of capital which can be depreciated in the tax reports of a business enterprise.
  • Cost Center is an accounting cost object which references an ongoing account used to collect costs for accounting entities useful to a business enterprise which does not have an (at least presumed) ending moment of time as an attribute. Cost Centers tend to reflect the standing, ongoing, and established accounting groupings (and their internally affiliated equipment, personnel, purchases, sales, and the like) which characterize the business enterprise. Although Cost Centers do indeed have an "end point" in verity, the definition of when that end point will occur is not usually identified; Cost Centers, therefore, do not necessarily have an "end point” in theory.
  • a Cost Center is distinguished from an Order Type by a presumption and intent on the part of personnel in the business enterprise respecting permanence; since this presumption and intent has implications for tax and securities reporting and, thereby, for auditing, it is useful for the different types of accounts to be supported in a computer system such as that related to the present invention.
  • Cost Element is an accounting cost object which is an identifier used to categorize a type of spending. Examples of Cost Elements are salaries, materials and supplies, raw materials, labor and services, payments to a utility company, and the like. Cost Elements are used to distinguish what type of needed item or service a business enterprise has acquired or the purpose for which the business enterprise may have acquired the particular item or service; since the type of item or service or purpose for acquisition has implications for tax and securities reporting and, thereby, for auditing, it is useful for the different identifiers to be supported in a computer system such as that related to the present invention.
  • An example, in this regard, of an item acquired for a distinct purpose respective to taxes would be of a pump used for an environmental purpose; since certain tax jurisdictions encourage the expenditure of resources toward the enhancement of the environment through the granting of a tax benefit for money spent toward that purpose, a Cost Element is attached to this particular expenditure by the accounting system to help in designating its special tax status.
  • Accounting group registry A fundamental accounting cost object which uniquely distinguishes the tax, accounting, and business enterprise relevance of money related to a particular transaction or other event for purposes of reporting, accounting, and archival.
  • Order Types (and Projects or Project Accounts), Cost Centers, and Cost Elements are all general accounting cost objects which are useful in building efficient data schema within large business enterprises; but a particular transaction is usually reported-for, accounted-for, and archived using a combination of these general accounting cost objects; the combinatorial result is an accounting group registry for the transaction or summary of transactions having the same combination of identifying cost objects.
  • the Cost Element is appended as a "suffix" to a particular Cost Center in reporting, accounting, and archiving a particular transaction or summary of transactions; so the combination of a particular Cost Center and its Cost Element suffix define the relevant accounting group registry.
  • the Cost Element is appended as a prefix to Project Account (an "Order Type") in reporting, accounting, and archiving a particular transaction or summary of transactions, so the combination of the particular Project Account and its Cost Element prefix define the accounting group registry.
  • Tax rate data element An item of data which is used in the determination of taxes.
  • Tax Rate A type of tax rate data element which defines a percentage or an otherwise relative amount which is applied to the value of a transaction to define a jurisdiction's tax.
  • Taxable Percentage A type of tax rate data element which defines the proportion of a transaction which is subject to a Tax Rate.
  • a taxable percentage can be useful in the operation of a jurisdiction insofar as an "incentive" can be created by defining a taxable percentage respective to established tax rates without changing the tax rate (per se) to achieve the incentive. In this manner, the incentive can be defined to a proper sophistication without burdening the tax rate definition per se with complexities respective to the incentive.
  • the present invention provides an apparatus for determining accrued use-taxes, the apparatus having a computer; transaction record acquisition logic in the computer for acquiring transaction information characterizing purchases of goods and services and, then, for generating transaction records; use-tax accrual logic in the computer linked to the transaction records; and tax rate acquisition logic in the computer for (firstly) acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes for a plurality of state jurisdictions, and (secondly) for generating a data schema linked to the use-tax accrual logic having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to the tax jurisdiction codes.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further acquires data descriptive of excluded accounting group registries and the data schema further comprises fourth data elements descriptive of excluded accounting group registries.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has the first, second, third, and fourth data elements arranged in tables in the data schema.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has data alignment logic in the computer which is used to assure that the cost objects and other data elements described above are interactively harmonious and mutually comprehensive.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has transaction record extraction logic in the computer used to read the transaction records and to build simplified transaction records respective to the transaction records.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has tax rate update logic in the computer linked to the data schema and to the tax rate database for periodically acquiring new tax information from the tax rate database to replace respective third data elements.
  • the present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has sales tax crediting logic in the computer linked to the sales tax payment record and to the data schema such that the paid sales taxes can be credited to the accrued use-taxes.
  • the present invention also provides a method for determining accrued use-taxes from transaction records holding data elements which characterize purchases of goods and services which has the steps of providing a computer; acquiring transaction information characterizing purchases of goods and services; generating transaction records in the computer from the transaction information; acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes from at least one external tax information source having that information and data for a plurality of state jurisdictions; generating (in the computer) a data schema having first data elements descriptive of the inclusive accounting group registries, second data elements descriptive of the tax jurisdiction codes, and third data elements descriptive of the tax information respective to the tax jurisdiction codes; and accessing (in the computer) the data schema to acquire the first, second, and third data elements; accessing in the computer the transaction records to acquire the data elements which characterize purchases of goods and services; and using the data elements which characterize purchases of goods and services and using the first, second, and third data elements to determine the accrued use-taxes in the computer.
  • the present invention also provides a method such as that described above having the steps of (1) acquiring data elements descriptive of Order Type, excluded accounting group registries, and excluded cost objects; and (2) generating, in the data schema in the computer, fourth data elements descriptive of excluded accounting group registries.
  • the present invention also provides a method such as that described above having the step of aligning the data elements so that they are interactively harmonious and mutually comprehensive.
  • the present invention also provides a method such as that described above having the steps of building simplified transaction records respective to the transaction records in the computer and determining the accrued use-taxes from the simplified transaction records.
  • the present invention also provides a method such as that described above having the steps of periodically acquiring new tax information from the tax rate database to replace respective third data elements.
  • the present invention also provides a method such as that described above having the step of crediting the paid sales taxes to the accrued use-taxes.
  • the present invention provides computer-implemented logic and a method for generating an amended tax report enabling corrections to be filed to harmonize previously-filed tax reports respective to the findings of an auditor or other entity reviewing the filed tax reports for the business enterprise.
  • FIG. 1 presents the tax accrual system overview of the present invention.
  • FIG. 2 presents details of a transaction activity preparation system.
  • FIG. 3 shows details of a tax rate acquisition system.
  • FIG. 4 outlines a general overview of the tax accrual process.
  • FIG. 5 depicts details which are related to cost center accounting executed by the accrual logical engine in the present invention.
  • FIG. 6 depicts details which are related to order type and project accounting executed by the accrual logical engine in the present invention.
  • FIG. 7 depicts detail related to adjusting use-taxes to reflect the impact of related sales taxes.
  • FIG. 8 shows an embodiment of a general purpose computer system for use in implementing the present invention.
  • the present invention is enabled through use of a machine which is a special purpose computer created by combining a general purpose computer with computer program code directed to the particular function of accrued use-tax determination. Details related to the description of a general purpose computer are discussed with respect to FIG. 8.
  • the computer program code (resident within the computer) directed to the particular function of accrued use-tax determination provides at least one "component part" of the machine.
  • the computer program code may be in the form of, without limitation, inter-linked modules, routines and subroutines, program objects, and/or installed interactive processes.
  • computer program code may be at least partially expressed in hardwired circuitry reminiscent of traditional hardwired gate arrangements which execute simplified logical scenarios without need for computers capable of executing sequential instructions in conjunction with a clock pulse. It is useful to reference the computer program code collectively in execution with the general purpose computer as "logic", with the logic being further subdivided to include logical engines, logical data schema, and logical linkages.
  • logical engines reference descriptively useful virtual functional elements within the logic which read data, write data, calculate data, and perform decision operations related to data
  • logical data schema reference descriptively useful virtual functional elements within the logic which store and hold data in a systematic and methodical manner for convenient access in electronic or other form.
  • a logical data schema is, therefore, a collection, assembly, and compilation of data in a methodical way for use in the computer.
  • Logical linkages function to define descriptively useful virtual functional data pipelines between logical engines and logical data schema; in this regard, a logical linkage facilitates data communication (communication in a datalogical context) between other logical entities.
  • a link or connection in computer processing therefore, usually has both a physical attachment and a logical linkage dimension which enables information to be meaningfully exchanged across the physical attachment.
  • a logical engine executes a useful process (useful data work) on data
  • a logical data schema holds data in a usefully organized way in an appropriately elegant structural arrangement
  • a logical linkage provides an acceptably secure and robust communication path between different logical engines and/or logical data schema for the transfer of data between any two of those logical entities.
  • a first logical data schema linked to a first logical engine which outputs via a second linkage to a second logical data schema can be paralleled to a first tank which has a pipeline to a pump which outputs via a second pipeline to a second tank.
  • the "tank to pipeline to pump to second pipeline to second tank” arrangement executes to transfer a liquid such as water even as the "first logical data schema linked to a first logical engine which outputs via a second linkage to a second logical data schema” arrangement executes to transfer data.
  • a reference to logical engines, logical linkages, and/or logical data schema presumes and incorporates the apparent physical means enabling the logical dimension to be achieved; the reference and focus on the logic helps in distinguishing the aspects of the special purpose computer which is the subject of the present invention from a general purpose computer or other type of special purpose computer.
  • FIG. 1 presents Tax Accrual System Logic Overview 101.
  • Business Enterprise Database 103 is a general data schema holding individual entries (records of events including orders, sales, acquisitions, receipts, purchases, inventory changes, and the like) in the ongoing process of a business enterprises entities' activities.
  • Business Enterprise Database 103 receives data from Business Enterprise Function Programs 105 and may also be a source of data for other programs (computer executed logical processes relating to orders, sales, acquisitions, receipts, purchases, inventory changes, and the like used in the general operations executed to read, calculate or reorganize, and write data) which are used in the ongoing process of a business enterprise's activities.
  • Some programs in Business Enterprise Function Programs 105 function to transfer certain records in Business Enterprise Database 103 into accounting entries which have relevance in the characterization of operations respective to cost control, corporate performance reporting, and tax return preparation; these programs may also define accounting entries without a need for reference to Business Enterprise Database 103.
  • the output from the programs in Business Enterprise Function Programs 105 functioning to define accounting entries is, however, stored in a database type of data schema defined herein as Accounting Balance Data 107.
  • the general relationships between Business Enterprise Database 103, Business Enterprise Function Programs 105, and Accounting Balance Data 107 are very common in most business enterprises which have evolved to a size prompting general integration of their business enterprise computing activities and should be generally apparent.
  • Accounting Balance Data 107 is fairly extensive, and the information therein can be updated or changed at any moment in time.
  • a first step in achieving this is to have a program in Business Enterprise Function Programs 105 which periodically runs to generate a conveniently sized listing of entries respective to a certain need; and, in the preferred embodiment of the present invention, such a program is used to periodically read records in Accounting Balance Data 107 to generate an Transaction Activity Log 203 (shown in FIG. 2) within Transaction Activity Preparation System 109. Details of Transaction Activity Preparation System 109 will be further discussed respective to FIG. 2.
  • Transaction Activity Preparation System 109 is read and referenced by Accrual Logical Engine 117 which also reads and references information from Reference Tables 115; Accrual Logical Engine 117 then performs a process further described respective to FIGS. 5 and 6 to generate tax accrual data values, and Accrual Logical Engine 117 then writes selected tax accrual data values into Accounting Balance Data b 107.
  • a set of tables are held within a data schema defined herein as Reference Tables 115, which holds tax information in the form of tax data respective to the tax jurisdiction codes in the form of data elements descriptive of the tax information.
  • Reference Tables 115 These tables, their affiliated data elements, logical identifiers, data element definitions, and exemplary formats are shown in the following paragraphs.
  • Reference Tables 115 are updated and changed by Tax Rate Acquisition System 113 (Further discussed with respect to FIG. 3) and by Table Loading Logical Engine 121; Tax Rate Acquisition System 113 acquires tax rate information from Tax Rate Information Source 111 (also further discussed with respect to FIG. 3).
  • Table Loading Logical Engine 121 is substantially a straightforward data schema interface logical engine which enables a human to use Monitor and Report Interface 123 (a standard terminal or workstation interface) to access and read both Accounting Balance Data 107 and Reference Tables 115 data and then make specific database entries to modify the data in Reference Tables 115 as the human references some external sources of tax data and other tax information; it should be noted that some of the external sources of information are publications from the jurisdictions themselves, which define the tax rates and tax information related to taxable percentages in their reports and records related to jurisdictional rule making.
  • Table Loading Logical Engine 121 has some embedded subprograms which activate automatically to access both Accounting Balance Data 107 and Reference Tables 115 data and then make specific database entries into Reference Tables 115 to update certain fields in Reference Tables 115 in a manner which should generally be apparent.
  • the level of access protection given to an individual operating Monitor and Report Interface 123 in accessing and modifying specific database entries is preferably more restrictive and specific than the protection given to individuals using Monitor and Report Interface 125 (for the Reversal Logical Engine 119), Monitor and Report Interface 127 (for the Reference Tables 115), and Monitor and Report Interface 129 (for the Accrual Logical Engine 117); for these last three interfaces do not have the same ability to fundamentally alter the information in Reference Tables 115 without any limitation to the scope of the modifications being implemented.
  • Monitor and Report Interfaces (125, 127, and 129) generally function to facilitate logic and provide output either (a) to print reports (when operated in conjunction with printing hardware or with a screen display), (b) to enable well defined processes to be initiated (via a keyboard and screen display), or (c) to enable examination and, optionally, alteration of specific predefined data fields.
  • a feature in the present invention respective to the portion of the database identified by cost elements "Rerun #1” thru “Rerun #6" in the Cost Object Inclusion And Taxable Percentage Table (Table 5) enables corrected filings after a tax report has been defined and the information in Accounting Balance Data 107 has been "finalized".
  • judgments on the part of personnel within the business enterprise are subject to auditing and review; in some cases, certain of those judgments by personnel within the business enterprise respecting tax rates are occasionally challenged and/or corrected through the process of auditing and review conducted subsequent to the filing of a tax report.
  • a correction pursuant to the auditing and review process
  • a corrected tax report must be generated.
  • corrective reports can be output by the tax accrual system logic where the Accrual Logical Engine 117 reprocesses the information contained in the archived copy of the Transaction Activity Log 203 (or derived transaction information) and, referencing the selecting indicator, uses the Tax # (from the original report) and Rerun # data elements to define a corrective report.
  • the present invention provides logic, data, and a method for generating an amended tax report which enables corrections to be filed reconciling previously-filed tax reports respective to the findings of an auditor or other entity reviewing filed tax reports for the business enterprise.
  • Tax Accrual System Logic Overview 101 also shows Reversal Logical Engine 119 which also reads and references information from Reference Tables 115 and Accounting Balance Data 107, executes a process further described respective to FIG. 7 which reduces the tax liability to reflect taxes which have already been paid, and then writes accrual data values into Accounting Balance Data 107 as debits and credits.
  • FIG. 2 presents further Details of Transaction Activity Preparation System 109 as Transaction Activity Preparation System Detail 201.
  • a program in Business Enterprise Function Programs 105 runs at a convenient time to periodically read records in Accounting Balance Data 107 and generate a conveniently sized Transaction Activity Log 203 within Transaction Activity Preparation System 109.
  • the data schema of one embodiment of Transaction Activity Log 203 has field definitions as indicated in Table 9.
  • Transaction Activity Log 203 The data of Transaction Activity Log 203 is read by Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207.
  • Transaction Activity Log 203 The data of Transaction Activity Log 203 is still fairly extensive (see discussion of Business Enterprise Function Programs 105 and Transaction Activity Preparation System 109 respective to FIG. 1), and the information therein can be updated or changed at any moment in time by Business Enterprise Function Programs 105.
  • Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207 establish a defined set of data from Transaction Activity Log 203 (at essentially a moment in time) at such times when Transaction Activity Log 203 is best accessed in a prompt manner so that all users of this file can have optimal response and stability of the collected data in the file.
  • Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207 (a) parse and selectively extract data necessary to define tax accrual from Transaction Activity Log 203 and (b) write output to one of two respective data schema: Cost Center Transaction Data 209 and Order Type Transaction Data 211.
  • Cost Center data relates to an ongoing account type which collects costs for established accounts within the accounting system
  • Order Type data relates to a limited-term account type which collects costs for accounts which are appropriate to Order Types identified as more short-term in potential duration than the ongoing accounts within the accounting system.
  • the records in the Transaction Activity Log 203 have somewhat different active fields, and, in the preferred embodiment, it was considered more convenient to open files and handle the data in the context of the two categories by use of processes deployed in the generally parallel design depicted instead of via a single unified process that would discriminate records by field layout; other embodiments for solving this need include a single logical engine having two subroutines respective to the different record types, unified record types, and the like, as should be apparent. Process details for reading records from Transaction Activity Log 203, parsing the record, selecting data for the accrual process, and writing data as output into one of the Cost Center Transaction Data 209 and Order Type Transaction Data 211 data schema should be apparent.
  • Cost Center Transaction Data 209 and Order Type Transaction Data 211 data schema therefore, hold tax accrual source information for use by Accrual Logical Engine 117 in a stable and fixed form for a particular instance of tax accrual determination; in this regard, a "snapshot" of transaction activity for a period of time is created and can be preserved.
  • Tax Rate Acquisition System Detail 301 shows other parts of Tax Rate Acquisition System 113 as it acquires tax rate information from Tax Rate Information Source 111 for updating and changing of Reference Tables 115.
  • Tax Rate Information Source 111 can be a database in a computer-implemented system accessible via a network linkage (such as via the Internet), it can be a set of data available in a data schema available on a computer readable disk, or it could be a data file which is periodically updated by a human (via a system and method not shown, but which should be apparent).
  • the information in Tax Rate Information Source 111 changes periodically as different jurisdictions modify their respective tax provisions.
  • the information in Tax Rate Information Source 111 is, therefore, a summary of this detailed information in conveniently available form.
  • One source of such a set of data is Fast-Tax Rate File which is available from CLR Fast-Tax Corporation located in Carrollton, Tex.
  • Tax Rate Acquisition Logical Engine 307 reads the information from Tax Rate Information Source 111 either automatically or as prompted by a human via Monitor and Report Interface 309 to obtain a recent set of tax rate data elements. Tax Rate Acquisition Logical Engine 307 selects a subset of the information from Tax Rate Information Source 111 of interest to the particular business enterprise and writes the newly acquired tax information to New Tax Rate Database 305 to hold an unchanging and business-enterprise-relevant subset of the information. Tax Rate Uploading Logical Engine 303 reads the data in New Tax Rate Database 305 and updates appropriate tables in Reference Tables 115.
  • Monitor and Report Interface 309 for the Tax Rate Acquisition Logical Engine 307
  • Monitor and Report Interface 311 for the Tax Rate Uploading Logical Engine 303
  • FIG. 4 shows a general overview of the larger General Tax Accrual Process 401.
  • a first Transaction Collection Step 403 needs to occur on a periodic basis so that all accounting transactions for a period of time are collected together to serve as inputs to the general tax accrual process.
  • a second general Liability Account Debiting Step 405 sales taxes which have already been paid (a requirement in some jurisdictions) need to be figured and retained as liability debits to decrease the use-tax which will be paid.
  • use-taxes can be defined for all transactions as liability credits (Note that a liability credit will generate an increase in the tax that will need to be paid to an outside jurisdiction, while a liability debit is a decrease in the tax that will need to be paid to the outside jurisdiction).
  • Accrual Logical Engine Cost Center Process 501 is shown in FIG. 5 and Accrual Logical Engine Order Type Cost Process 601 is shown in FIG. 6. These two processes are logically executed by the computer in series as a unified entity (connected at Initiate Order Type Portion Step 521) by Accrual Logical Engine 117 to perform a process generating tax accrual data values and writing selected tax accrual data values into Accounting Balance Data 107.
  • FIG. 5 shows initiation of the Accrual Logical Engine Cost Center Process 501 with Start Step 503 where Accrual Logical Engine 117 opens Accounting Balance Data 107, Reference Tables 115, and Cost Center Transaction Data 209 for access.
  • Accrual Logical Engine 117 reads a first (or new) record from Cost Center Transaction Data 209, and parses the Cost Center field. Referencing information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115, Accrual Logical Engine 117 executes Relevant Cost Center Decision Step 507 by comparing the Cost Center for the record with the included Cost Centers to decide if this record should proceed to Extract Cost Element Step 508 or to Last Cost Center Transaction Decision Step 519.
  • Accrual Logical Engine 117 proceeds to extract the Cost Element in Extract Cost Element Step 508.
  • Accrual Logical Engine 117 then proceeds to Relevant Cost Element Decision Step 509, references information in Table 4 (Cost Element Inclusion Table) in Reference Tables 115, and compares the Cost Element for the record with the included Cost Elements in that table to decide if this record should proceed to Step 519 or to (Cost Center) Taxable Percentage Definition Step 511.
  • Accrual Logical Engine 117 proceeds to Step 511, references information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115 to acquire the relevant taxable percentage, and holds this percentage in its logic.
  • Accrual Logical Engine 117 proceeds to (Cost Center) Postal Delivery Code Identification Step 513, references information in Table 6 (Tax Jurisdiction Code Table) in Reference Tables 115 to acquire the tax jurisdiction code, and holds this code in its logic.
  • the described embodiment uses the U.S. Postal Zone Improvement Plan (ZIP) code relevant to this Cost Center.
  • ZIP U.S. Postal Zone Improvement Plan
  • the Cost Centers are always defined to have relevance only within a unique one and only one particular state, so there is no need to execute Step 513 prior to Step 511.
  • Accrual Logical Engine 117 executes Step 513 prior to Step 511.
  • a geopolitical demographic allocation file is used to enable allocation.
  • Accrual Logical Engine 117 next executes (Cost Center) Tax Rate Definition Step 515 by referencing information in Table 7 (Tax Rate Table) in Reference Tables 115 to acquire the tax rate relevant to the tax jurisdiction and holds this rate in its logic. Then, Accrual Logical Engine 117 proceeds to (Cost Center) Tax Computation and Storage Step 517 where the amount of expenditure respective to the Cost Element, the taxable percentage, and the tax rate are multiplied together to define the tax; the tax is then entered as a tax liability into the proper jurisdictional account in Accounting Balance Data 107 in conjunction with reference to information in Table 8 (Tax Cost Element Table).
  • Accrual Logical Engine 117 proceeds to Last Cost Center Transaction Decision Step 519 and ascertains if the last Cost Center record has been processed. Note that alternative routes to Step 519 are via Relevant Cost Center Decision Step 507 or Relevant Cost Element Decision Step 509 as previously discussed. Accrual Logical Engine 117 terminates Step 519 to Initiate Order Type Portion Step 521 if the last Cost Center record has been processed or to Read Cost Center Transaction Step 505 to acquire the next Cost Center transaction record if the last Cost Center record has not been processed.
  • FIG. 6 shows continuation of the unified process (connected at Initiate Order Type Portion Step 521) executed by Accrual Logical Engine 117 to generate tax accrual data values and write selected tax accrual data values into Accounting Balance Data 107.
  • Accrual Logical Engine 117 continues the process begun with Accrual Logical Engine Cost Center Process 501 with Initiate Order Type Portion Step 521 where Accrual Logical Engine 117 opens Order Type Transaction Data 211 for access.
  • In Read New Order Type Transaction Step 621 Accrual Logical Engine 117 reads a first record from Order Type Transaction Data 211 and parses the relevant Order Type field.
  • Accrual Logical Engine 117 executes Relevant Order Type Decision Step 603 by comparing the Order Type for the record with the included Order Types (in this case the "Project Number") to decide if this record should proceed to Extract (Order Type) Cost Element Step 605 or to Last Order Type Transaction Decision Step 617. If a match is identified, and the Order Type is thereby to be included, Accrual Logical Engine 117 proceeds to extract the relevant Cost Element in Extract (Order Type) Cost Element Step 605.
  • Order Type inclusion is established in Step 603 where an Order Type is always affiliated with a Cost Center and the inclusion decision proceeds by, firstly, identifying the affiliated Cost Center respective to the Order Type and, secondly, comparing the affiliated Cost Center to the included Cost Centers in Table 5.
  • Accrual Logical Engine 117 then proceeds to Relevant (Order Type) Cost Element Decision Step 607, references information in Table 4 (Cost Element Inclusion Table) in Reference Tables 115, and compares the related Cost Element for the record with the included Order Type Cost Elements in that table to decide if this record should proceed to Last Order Type Transaction Decision Step 617 or to (Order Type) Taxable Percentage Definition Step 609.
  • Accrual Logical Engine 117 proceeds to Step 609, references information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115 to acquire the relevant taxable percentage, and holds this percentage in its logic.
  • Accrual Logical Engine 117 proceeds to (Order Type) Postal Delivery Code Identification Step 611, references information in Table 6 (Tax Jurisdiction Code Table) in Reference Tables 115 to acquire the tax jurisdiction code, and holds this code in its logic.
  • the described embodiment uses the U.S. Postal Zone Improvement Plan (ZIP) code relevant to this Order Type.
  • ZIP U.S. Postal Zone Improvement Plan
  • Order Type accounts are defined to have relevance uniquely within one and only one state, so there is no need to execute Step 611 prior to Step 609.
  • Accrual Logical Engine 117 executes Step 611 prior to Step 609.
  • a geopolitical demographic allocation file is used to enable allocation.
  • Accrual Logical Engine 117 next executes (Order Type) Tax Rate Definition Step 613 by referencing information in Table 7 (Tax Rate Table) in Reference Tables 115 to acquire the tax rate relevant to the tax jurisdiction and holds this rate in its logic. Then, Accrual Logical Engine 117 proceeds to (Order Type) Tax Computation and Storage Step 615 where the amount of expenditure respective to the Cost Element, the taxable percentage, and the tax rate are multiplied together to define the tax; the tax is then entered as a tax liability into the proper jurisdictional account in Accounting Balance Data 107.
  • assurance that the Cost Object data elements are interactively harmonious and mutually comprehensive can be achieved by executing a comparison of the Cost Center against both an inclusion table such as Table 4 (Cost Element Inclusion Table) and an exclusion table such as Table 2 (Cost Center and Order Type Exclusion Table) when executing (e.g.) Relevant Cost Center Decision Step 507 and thereby comparing the Cost Center for the record with an included Cost Center reference and an excluded Cost Center reference to decide if this record should proceed to Extract Cost Element Step 508 or to Last Cost Center Transaction Decision Step 519.
  • an inclusion table such as Table 4 (Cost Element Inclusion Table) and an exclusion table such as Table 2 (Cost Center and Order Type Exclusion Table)
  • references to Table 4 and Table 3 (Cost Element Exclusion Table) in Reference Tables 115 and comparison of the Cost Element for the record with the included and excluded Cost Elements in those tables; references to Table 5 (Cost Object Inclusion And Taxable Percentage Table), Table 1 (Order Type Inclusion Table), and Table 2 (Cost Center and Order Type Exclusion Table) in Relevant Order Type Decision Step 603 and comparison of the Order Type for the record with the included and excluded Order Types in those tables; and references to Table 4 and Table 3 in Extract (Order Type) Cost Element Step 605 and comparison of the Cost Element for the record with the included and excluded Cost Elements in those tables help in establishing a data schema cross-check as the personnel using the present invention establish two separate types of tables indicating (as a first paradigm of inclusion) what is to be included and (as a second paradigm of exclusion) what is not to be excluded so that the computer executed logic can confirm both paradigms against the cost objects being processed
  • the "inclusion” check could be executed first in one embodiment, or the "exclusion” check could be performed first in another embodiment.
  • Another embodiment uses a less definite “exclusion” only check with default inclusion (the benefit being a smaller and less costly data schema size); yet another embodiment uses the less definite "exclusion” check with general default inclusion but with the addition of a limited set of additional specific inclusion checks for those data objects of special importance to the business enterprise.
  • the exclusion and inclusion data entries can be further compared to a master list to help establish that "all cost objects are present and accounted-for" and that no cost object is both included and excluded; as should be apparent, if a cost object has a reason to be both included and excluded, the cost object may not be properly detailed for the larger goals of the accounting needs of the business enterprise and an indication is thereby established that a further set of fundamental cost objects respective to that "dichotomously designated" cost object is needed.
  • Accrual Logical Engine 117 proceeds to Last Order Type Transaction Decision Step 617 and ascertains if the last Order Type record has been processed. Note that alternative routes to Step 617 are via Relevant Order Type Decision Step 603 or Relevant (Order Type) Cost Element Decision Step 607 as previously discussed.
  • Accrual Logical Engine 117 terminates Step 617 to End Step 619 if the last Order Type record has been processed or to Read Order Type Transaction Step 621 to acquire the next Order Type transaction record if the last Order Type record has not been processed.
  • End Step 619 Accrual Logical Engine 117 closes all open files and generates a report to Monitor and Report Interface 129 (reporting interface logic for the Accrual Logical Engine 117).
  • Reversal Logical Engine 119 executes Reversal Logical Engine Process 701 to decrease the tax liability in a particular jurisdiction by debiting the liability with taxes which have already been paid as sales taxes at the time when the business enterprise acquired goods or services.
  • the payment of sales tax in some jurisdictions must take place at the time of sale and must be collected by the seller; whereas, in other jurisdictions, the payment of sales tax in some jurisdictions may be accrued in an account by the purchaser for a period of time of sale and then paid as a part of a single payment (as a "use-tax"). Since jurisdictions extend certain tax benefits during certain times to influence and encourage certain types of activities (e.g.
  • Reversal Logical Engine 119 is the logical engine within the present invention which executes logic to achieve that resolving feature.
  • Two main account types facilitate these operations: an "enumerated liability account” type of account holding a listing of records respective to individual purchases of goods and services, and an “accrual liability account” type of account holding a single value which represents the appropriate cumulative impact of all entries and considerations in a respective "enumerated liability account”.
  • the enumerated liability accounts are also organized by individual ZIP code; in the following discussion, the set of enumerated liability accounts will be treated as one extended enumerated liability account.
  • FIG. 7 shows initiation of Reversal Logical Engine Process 701 with Start Step 703 where Reversal Logical Engine 119 opens Accounting Balance Data 107 and Reference Tables 115 for access.
  • Start Step 703 terminates to Read Enumerated Liability Account Record Step 705 where a record in the enumerated liability account is read.
  • (Reversal) Postal Delivery Code Extraction Step 707 the location indicators in the enumerated liability account record are used in conjunction with information in the Tax Rate Table (Table 7) and the Tax Jurisdiction Code Table (Table 6) in Reference Tables 115 to identify the postal delivery code respective to the destination of the transaction in the enumerated liability account record.
  • Enumerated Liability Account Debiting and Accrual Liability Account Crediting Step 713 the allocated enumerated liability account is credited for the amount of the transaction and the accrual liability account is debited for the amount of the transaction (which had been previously paid to the jurisdictional tax authority).
  • Reversal Logical Engine 119 executes Last Enumerated Liability Account Record Decision Step 715 to determine if the logic should progress to End Step 717 or to Read Enumerated Liability Account Record Step 705 for reading the next enumerated liability account record.
  • Last Enumerated Liability Account Record Decision Step 715 is to transfer the logic to End Step 717, Reversal Logical Engine 119 closes all open files and generates a report to Monitor and Report Interface 125 (for the Reversal Logical Engine 119).
  • a program in Business Enterprise Function Programs 105 executes to allocate the taxes defined by use of the present invention to different relevant jurisdictions respective to a location respective to each enumerated liability account and accrual liability account (e.g., a business enterprise in an urban location interacts with a city jurisdictional entity, a county jurisdictional entity, and a state jurisdictional entity).
  • An example of such a program is in the CLR Fast-Tax product previously identified in this specification.
  • the present invention is, therefore, enabled through use of a machine which is a special purpose computer created by combining a general purpose computer with computer program code directed to the particular function of accrued use-tax determination (alternatively termed, e.g., accrued use-tax determination software, accrued use-tax determination computer program, accrued use-tax software, accrued use-tax determination program, and/or accrued use-tax determination computer-implemented logic) so that, when connected to an electrical power source, powered by electricity, and activated to execute the computer program code (software), the special purpose computer executes the particular function of accrued use-tax determination pursuant to the instructions from the computer program code.
  • the general purpose computer has electrically activated components denoted as a central processing unit (CPU), at least one physical memory connected to the CPU, an input keyboard connected to the CPU, an output display (which can include, without limitation, a printer, printing terminal where output is printed on paper, cathode ray tube monitor, and/or flat panel monitor) connected to the CPU, a computer clock pulse generator within the CPU for providing periodic signals which assist in latching and interconnecting internal circuits in the CPU and in synchronizing operations of the CPU in real-time, and a connection to electrical power for energizing all of the electrically activated components of the computer.
  • CPU central processing unit
  • the CPU has electrically activated components denoted as a central processing unit (CPU), at least one physical memory connected to the CPU, an input keyboard connected to the CPU, an output display (which can include, without limitation, a printer, printing terminal where output is printed on paper, cathode ray tube monitor, and/or flat panel monitor) connected to the CPU, a computer clock pulse generator within the CPU
  • the CPU further has control circuits, a bus, and specific computer circuits for either temporarily holding data (e.g., a register or an accumulator), for executing fundamental data processing operations (e.g., an addition circuit and/or a boolean logical operation circuit), or for executing types of instructions (e.g.
  • an arithmetic logical unit or ALU combining arithmetic and logical operations into an essentially unified sub-circuit
  • the specific computer circuits are connected in communication to the control bus and, in some cases, to each other through latching circuits which can individually be in either a conducting (communicating) or non-conducting (non-communicating) configuration; the collective configurations of all the latching circuits at a particular moment define a particular state of the central processor; and the state of the central processor is respectively modified and changed from the individual instructions of the computer program code as they are successively accessed in the central processing unit in conjunction with the output of the clock pulse generator.
  • the general purpose computer also has computer program code in the form of a commercially available operating system which functions as a computer program code platform for enabling the execution of the special purpose computer program code directed to the particular function of accrued use-tax determination.
  • the present invention is implemented by and through partial use of a computer which has been programmed to perform the accrued use-tax determination; the general purpose computer functions as a medium for realizing the functionality provided by the computer program code's functionality.
  • the preferred embodiment is deployed on an IBM 9021-9X2 or an IBM 9021-982 mainframe computer using the MVS operating system available from IBM, Old Orchard Road, Armonk, N.Y., 10504, and the SAP-R2 application system platform available from SAP America, Inc., 625 North Governor Printz Blvd., Essington, Pa. 19029.
  • some communication linkages within an extended form of the special purpose computer may be implemented by electrical, optical, or radio-frequency signal communication interfaces and communication media which collectively use electrically-powered transmitter and receiver components which are directly or indirectly linked to at least one central processing unit.
  • a set of networked or otherwise linked general purpose computers collectively function to execute the computer program code.
  • FIG. 8 shows an embodiment of a general purpose computer 801 for use in implementing the present invention with a mainframe computer 803 being linked via a network 805 to a desktop workstation 807.
  • the mainframe computer 803 and desktop workstation 807 each have a respective CPU 809 and CPU 811.
  • the mainframe computer 803 and desktop workstation 807 each also have respective logic 813 and logic 815 interactive with the respective CPUs 809 & 811.
  • the logic 813 includes the operating system for the mainframe computer 803 and the accrued use-tax determination computer-implemented logic of the present invention discussed with respect to FIGS. 1 through 7.
  • the logic 815 of the desktop workstation includes the operating system for the desktop computer 803 and a terminal emulator which functions with the monitor 817 for enabling human interface to the logic 813 of the mainframe computer 803.
  • the preferred embodiment of the desktop workstation is deployed on an IBM 330-P75 Personal Computer having a Windows 95 operating system available from Microsoft Corporation, 1-T Microsoft Way, Redmond, Wash., 98052, and an "IRMA for the Mainframe" 3.0.0 terminal emulator available from Digital Communications Associates, Inc., 1000 Alderman Drive, Alpharetta, Ga. 30202-4199.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

This invention relates to computer-implemented tax preparation and tax submission accounting, and the invention is directed to providing a system which enables use-tax accrual and determination. The described computer system has transaction record acquisition logic for acquiring transaction information characterizing purchases of goods and services and for generating transaction records; use-tax accrual logic; and tax rate acquisition logic for acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes from an external tax information source. The invention also provides data alignment logic used to assure that data elements used in tax determination are interactively harmonious and mutually comprehensive. The invention also provides (1) update logic for periodically acquiring new tax information from a tax rate database to keep tax rate information in a current and relevant condition and (2) sales tax crediting logic in the computer so that paid sales taxes can be credited to accrued use-taxes.

Description

FIELD OF THE INVENTION
This invention relates to computer-implemented tax preparation and tax submission accounting. Specifically, this invention is directed to providing a system which enables use-tax accrual and determination.
BACKGROUND OF THE INVENTION
Sales taxes and use-taxes need to be defined and paid by business enterprises in the course of their operations. In a nation such as the United States of America, proper and efficient fulfillment of this requirement by a business enterprise executing multiple-location operations requires substantial expenditure of effort, resources, and time as a plurality of tax situations respective to different jurisdictional entities such as states, counties, cities, towns, and townships compel ongoing attention. Furthermore, many of these different jurisdictional entities have effective tax rates respective to the purpose for which items and services are acquired; in this regard, jurisdictions extend certain implicit "use-tax" incentives to influence and encourage certain types of activities (e.g. investment in projects which enhance environmental quality, expansion of the business enterprise base of the jurisdiction by encouraging industrial processing within that jurisdiction, and cooperative support with the jurisdiction of socially beneficial initiatives). Additionally, effective tax rates respective to these "use-taxes" can, at times, be different respective to certain goods and services since the jurisdiction may either define the rates only for a certain limited time, or, in the normal course of rate setting, change the rate. A further complication in tax management is that payment of sales tax in some jurisdictions must take place at the time of sale and must be collected by the seller, whereas, in other jurisdictions, the payment of sales tax may be accrued in an account by the purchaser for a period of time and then paid as a part of a single payment "use-tax". An additional complication in tax management occurs when an article is purchased in one jurisdiction and then transported into another jurisdiction for use (or when the cumulative value of a set of such articles purchased with a defined period of time and so transported exceeds a certain value threshold). These complexities have prompted developments in tools and methods which assist in maintaining up-to-date information and in computing taxes. One example of a product offered in this regard is CLR/ Fast-Tax (CLR Fast-Tax Corporation of Carrollton, Texas), a product having both a file showing current tax rate information and a computer-implemented program for determining a proper allocation of taxes to different relevant jurisdictions respective to a location (e.g. a business enterprise in an urban location usually must interact with a city jurisdictional entity, a county jurisdictional entity, and a state jurisdictional entity, as well as with the federal jurisdictional entity since each of the city, county, and state entities has authority respective to that location). Another system for handling taxes is described in U.S. Pat. No. 5,335,169 issued on Aug. 2, 1994 to Malcolm K. L. Chong entitled "System for Tracking Multiple Rate Assessments On Transactions" for tracking and reporting taxable, non-taxable, and tax exempt sales transactions which are subject to a number of taxing jurisdictions for companies selling goods; it should be noted, however, that the patent to Chong seems to be specific to the needs of a selling party and does not fully deal with needs of purchasing parties. In this regard, sales taxes (the interest of the selling party in a transaction) and use-taxes (the interest of the purchasing party in a transaction) are different (although, in many situations, they appear to result in the same amount of tax being paid), so companies purchasing and using goods need a system which is directed to handling use-tax issues and detail. What is needed, therefore, is a system and a method providing use-tax preparation and submission accounting; the present invention provides such a system and method.
OBJECT OF THE INVENTION
It is a principle object of the present invention to provide a machine for use-tax determination.
It is a further object of the present invention to provide a machine for use-tax determination which is based upon a generally available computer having commercially available operating system logic and special logic specific to use-tax determination.
It is yet a further object of the present invention to provide a machine for use-tax determination which has: (A) transaction record acquisition logic for (1) acquiring transaction information characterizing purchases of goods and services and (2) generating transaction records; (B) use-tax accrual logic; and (C) tax rate acquisition logic for (1) acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes for a plurality of state jurisdictions, and (2) generating a data schema with data elements descriptive of the inclusive accounting group registries, tax jurisdiction codes, and tax information.
It is yet a further object of the present invention to provide a machine for use-tax determination having data alignment logic used to assure that the data elements indicated above are interactively harmonious and mutually comprehensive.
It is yet a further object of the present invention to provide a machine for use-tax determination having special logic which reads primary transaction records and builds derived simplified transaction records to help manage optimum access to the computing environment.
It is yet a further object of the present invention to provide a machine for use-tax determination which has tax rate update logic for periodically acquiring new tax information from a tax rate database to keep tax rate information current and relevant.
It is an additional object of the present invention to provide a machine for use-tax determination which has sales tax crediting logic in the computer so that paid sales taxes can be deducted from accrued use-taxes.
As a process and method, it is an object of the present invention to provide a method for use-tax determination using a generally available computer having (1) commercially available operating system logic and (2) special logic for use-tax determination.
It is a further object of the present invention to provide a computer-implemented method for use-tax determination which aligns the data elements used in the use-tax determination so that they are interactively harmonious and mutually comprehensive.
It is a yet a further object of the present invention to provide a computer-implemented method for use-tax determination which builds simplified transaction records respective to the transaction records in the computer and determines the accrued use-taxes in the computer from the simplified transaction records to help manage optimum access to the computing environment in a business enterprise.
It is yet a further object of the present invention to provide a computer-implemented method for use-tax determination which credits paid sales taxes to accrued use-taxes.
GLOSSARY OF TERMS
A glossary is herewith presented to help clarify some key terms used in discussing the present invention.
Cost Object: A cost object is a datalogical accounting entity which functions as a logical identifier for an accounting domain and can also be virtually used to reference the accounting domain with which it is affiliated. In this regard, a cost object has a relationship to an accounting domain which is similar to the relationship of a person to the name (or a portion of the name) by which they are identified. A cost object or combination of cost objects assist accounting personnel in defining a meaningful and useful detailed purpose for a transaction or set of transactions. The set of cost objects used in an accounting system ultimately must enable account specificity which is of sufficient detail to enable achievement of all reporting obligations and needs in the business enterprise.
Order Type: An Order Type is an accounting cost object which is referenced in conjunction with an account used to collect costs for "short term items" or for accounting entities useful to a business enterprise which have two key attributes of (a) an initiating moment of time and (b) an (at least presumed) ending moment of time. Examples of Order Types are (1) an addition to a building or remodeling of a plant used to make a product; (2) a set of costs connected to a batch (also known as a lot) of manufactured material which has a set of attributes (e.g. test results or records relating to manufacturing conditions) helping to distinguish it as a separate entity for record-keeping purposes; (3) a set of costs connected to a batch (also known as a lot) of acquired material which has a set of attributes (test results) helping to distinguish it as its own entity for record-keeping purposes; or (4) a set of costs made to a particular outside business enterprise entity for services rendered over a period of time.
Project: A Project or Project Account is an Order Type accounting cost object which is frequently distinguished from other Order Types because it is affiliated with a defined amount of capital which can be depreciated in the tax reports of a business enterprise.
Cost Center: A Cost Center is an accounting cost object which references an ongoing account used to collect costs for accounting entities useful to a business enterprise which does not have an (at least presumed) ending moment of time as an attribute. Cost Centers tend to reflect the standing, ongoing, and established accounting groupings (and their internally affiliated equipment, personnel, purchases, sales, and the like) which characterize the business enterprise. Although Cost Centers do indeed have an "end point" in verity, the definition of when that end point will occur is not usually identified; Cost Centers, therefore, do not necessarily have an "end point" in theory. A Cost Center is distinguished from an Order Type by a presumption and intent on the part of personnel in the business enterprise respecting permanence; since this presumption and intent has implications for tax and securities reporting and, thereby, for auditing, it is useful for the different types of accounts to be supported in a computer system such as that related to the present invention.
Cost Element: A Cost Element is an accounting cost object which is an identifier used to categorize a type of spending. Examples of Cost Elements are salaries, materials and supplies, raw materials, labor and services, payments to a utility company, and the like. Cost Elements are used to distinguish what type of needed item or service a business enterprise has acquired or the purpose for which the business enterprise may have acquired the particular item or service; since the type of item or service or purpose for acquisition has implications for tax and securities reporting and, thereby, for auditing, it is useful for the different identifiers to be supported in a computer system such as that related to the present invention. An example, in this regard, of an item acquired for a distinct purpose respective to taxes would be of a pump used for an environmental purpose; since certain tax jurisdictions encourage the expenditure of resources toward the enhancement of the environment through the granting of a tax benefit for money spent toward that purpose, a Cost Element is attached to this particular expenditure by the accounting system to help in designating its special tax status.
Accounting group registry: A fundamental accounting cost object which uniquely distinguishes the tax, accounting, and business enterprise relevance of money related to a particular transaction or other event for purposes of reporting, accounting, and archival. Order Types (and Projects or Project Accounts), Cost Centers, and Cost Elements are all general accounting cost objects which are useful in building efficient data schema within large business enterprises; but a particular transaction is usually reported-for, accounted-for, and archived using a combination of these general accounting cost objects; the combinatorial result is an accounting group registry for the transaction or summary of transactions having the same combination of identifying cost objects. As an example, in some business enterprises, the Cost Element is appended as a "suffix" to a particular Cost Center in reporting, accounting, and archiving a particular transaction or summary of transactions; so the combination of a particular Cost Center and its Cost Element suffix define the relevant accounting group registry. As another example, the Cost Element is appended as a prefix to Project Account (an "Order Type") in reporting, accounting, and archiving a particular transaction or summary of transactions, so the combination of the particular Project Account and its Cost Element prefix define the accounting group registry. In a very small business enterprise, it may indeed be practical to give a non-combinatorial unique accounting location (accounting group registry with an affiliated unique logical identifier reference) to each transaction, but, as an example in a large business enterprise, the existence of 1000 Cost Centers and 1000 Cost Elements would define at least 1,000,000 (1000 times 1000) general accounting cost objects if such unique identifiers were used. In practice therefore, a necessary accounting group registry is usually achieved via a combination of cost object datalogical types, since it costs much less to maintain 2000 cost objects (e.g. 1000 Cost Centers and Object Types +1000 Cost Elements) instead of the comparable 1,000,000 accounting group registry cost objects which would be required if the accounting system in a business enterprise could not support the combination of identifiers in its accounting system. The present invention will be described in detail using the general accounting cost objects which help to most efficiently achieve the system described; however, the invention also relates to the fundamental accounting group registry verity which is essentially defined by the combination of the relevant cost objects related to each described transaction.
Tax rate data element: An item of data which is used in the determination of taxes.
Tax Rate: A type of tax rate data element which defines a percentage or an otherwise relative amount which is applied to the value of a transaction to define a jurisdiction's tax.
Taxable Percentage: A type of tax rate data element which defines the proportion of a transaction which is subject to a Tax Rate. A taxable percentage can be useful in the operation of a jurisdiction insofar as an "incentive" can be created by defining a taxable percentage respective to established tax rates without changing the tax rate (per se) to achieve the incentive. In this manner, the incentive can be defined to a proper sophistication without burdening the tax rate definition per se with complexities respective to the incentive.
SUMMARY OF THE INVENTION
To achieve the foregoing objectives, the present invention provides an apparatus for determining accrued use-taxes, the apparatus having a computer; transaction record acquisition logic in the computer for acquiring transaction information characterizing purchases of goods and services and, then, for generating transaction records; use-tax accrual logic in the computer linked to the transaction records; and tax rate acquisition logic in the computer for (firstly) acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes for a plurality of state jurisdictions, and (secondly) for generating a data schema linked to the use-tax accrual logic having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to the tax jurisdiction codes.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further acquires data descriptive of excluded accounting group registries and the data schema further comprises fourth data elements descriptive of excluded accounting group registries.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has the first, second, third, and fourth data elements arranged in tables in the data schema.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has data alignment logic in the computer which is used to assure that the cost objects and other data elements described above are interactively harmonious and mutually comprehensive.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has transaction record extraction logic in the computer used to read the transaction records and to build simplified transaction records respective to the transaction records.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has tax rate update logic in the computer linked to the data schema and to the tax rate database for periodically acquiring new tax information from the tax rate database to replace respective third data elements.
The present invention also provides an apparatus such as that described above where the tax rate acquisition logic further has sales tax crediting logic in the computer linked to the sales tax payment record and to the data schema such that the paid sales taxes can be credited to the accrued use-taxes.
The present invention also provides a method for determining accrued use-taxes from transaction records holding data elements which characterize purchases of goods and services which has the steps of providing a computer; acquiring transaction information characterizing purchases of goods and services; generating transaction records in the computer from the transaction information; acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to the tax jurisdiction codes from at least one external tax information source having that information and data for a plurality of state jurisdictions; generating (in the computer) a data schema having first data elements descriptive of the inclusive accounting group registries, second data elements descriptive of the tax jurisdiction codes, and third data elements descriptive of the tax information respective to the tax jurisdiction codes; and accessing (in the computer) the data schema to acquire the first, second, and third data elements; accessing in the computer the transaction records to acquire the data elements which characterize purchases of goods and services; and using the data elements which characterize purchases of goods and services and using the first, second, and third data elements to determine the accrued use-taxes in the computer.
The present invention also provides a method such as that described above having the steps of (1) acquiring data elements descriptive of Order Type, excluded accounting group registries, and excluded cost objects; and (2) generating, in the data schema in the computer, fourth data elements descriptive of excluded accounting group registries.
The present invention also provides a method such as that described above having the step of aligning the data elements so that they are interactively harmonious and mutually comprehensive.
The present invention also provides a method such as that described above having the steps of building simplified transaction records respective to the transaction records in the computer and determining the accrued use-taxes from the simplified transaction records.
The present invention also provides a method such as that described above having the steps of periodically acquiring new tax information from the tax rate database to replace respective third data elements.
The present invention also provides a method such as that described above having the step of crediting the paid sales taxes to the accrued use-taxes.
Finally, the present invention provides computer-implemented logic and a method for generating an amended tax report enabling corrections to be filed to harmonize previously-filed tax reports respective to the findings of an auditor or other entity reviewing the filed tax reports for the business enterprise.
BRIEF DESCRIPTION OF THE DRAWING
FIG. 1 presents the tax accrual system overview of the present invention.
FIG. 2 presents details of a transaction activity preparation system.
FIG. 3 shows details of a tax rate acquisition system.
FIG. 4 outlines a general overview of the tax accrual process.
FIG. 5 depicts details which are related to cost center accounting executed by the accrual logical engine in the present invention.
FIG. 6 depicts details which are related to order type and project accounting executed by the accrual logical engine in the present invention.
FIG. 7 depicts detail related to adjusting use-taxes to reflect the impact of related sales taxes.
FIG. 8 shows an embodiment of a general purpose computer system for use in implementing the present invention.
DETAILED DESCRIPTION OF THE INVENTION
The present invention is enabled through use of a machine which is a special purpose computer created by combining a general purpose computer with computer program code directed to the particular function of accrued use-tax determination. Details related to the description of a general purpose computer are discussed with respect to FIG. 8. The computer program code (resident within the computer) directed to the particular function of accrued use-tax determination provides at least one "component part" of the machine. The computer program code may be in the form of, without limitation, inter-linked modules, routines and subroutines, program objects, and/or installed interactive processes. In some emergent computer designs, enabled by modern application specific integrated circuitry (ASIC) technology, computer program code may be at least partially expressed in hardwired circuitry reminiscent of traditional hardwired gate arrangements which execute simplified logical scenarios without need for computers capable of executing sequential instructions in conjunction with a clock pulse. It is useful to reference the computer program code collectively in execution with the general purpose computer as "logic", with the logic being further subdivided to include logical engines, logical data schema, and logical linkages. In this regard, logical engines reference descriptively useful virtual functional elements within the logic which read data, write data, calculate data, and perform decision operations related to data; and logical data schema reference descriptively useful virtual functional elements within the logic which store and hold data in a systematic and methodical manner for convenient access in electronic or other form. A logical data schema is, therefore, a collection, assembly, and compilation of data in a methodical way for use in the computer. Logical linkages function to define descriptively useful virtual functional data pipelines between logical engines and logical data schema; in this regard, a logical linkage facilitates data communication (communication in a datalogical context) between other logical entities. A link or connection in computer processing, therefore, usually has both a physical attachment and a logical linkage dimension which enables information to be meaningfully exchanged across the physical attachment. A logical engine executes a useful process (useful data work) on data, a logical data schema holds data in a usefully organized way in an appropriately elegant structural arrangement, and a logical linkage provides an acceptably secure and robust communication path between different logical engines and/or logical data schema for the transfer of data between any two of those logical entities. As a comparative metaphor, a first logical data schema linked to a first logical engine which outputs via a second linkage to a second logical data schema can be paralleled to a first tank which has a pipeline to a pump which outputs via a second pipeline to a second tank. The "tank to pipeline to pump to second pipeline to second tank" arrangement executes to transfer a liquid such as water even as the "first logical data schema linked to a first logical engine which outputs via a second linkage to a second logical data schema" arrangement executes to transfer data. In respect to the foregoing, it is important to recognize that a reference to logical engines, logical linkages, and/or logical data schema presumes and incorporates the apparent physical means enabling the logical dimension to be achieved; the reference and focus on the logic helps in distinguishing the aspects of the special purpose computer which is the subject of the present invention from a general purpose computer or other type of special purpose computer.
The Figures of this detailed description will define structural relationships between key modules and components within the computer program code and other aspects of the invention which enable the functionality of the machine of the present invention to be realized; in this regard, the machine ultimately is constructed out of a combination of hardware and software.
FIG. 1 presents Tax Accrual System Logic Overview 101. Business Enterprise Database 103 is a general data schema holding individual entries (records of events including orders, sales, acquisitions, receipts, purchases, inventory changes, and the like) in the ongoing process of a business enterprises entities' activities. Business Enterprise Database 103 receives data from Business Enterprise Function Programs 105 and may also be a source of data for other programs (computer executed logical processes relating to orders, sales, acquisitions, receipts, purchases, inventory changes, and the like used in the general operations executed to read, calculate or reorganize, and write data) which are used in the ongoing process of a business enterprise's activities. Some programs in Business Enterprise Function Programs 105 function to transfer certain records in Business Enterprise Database 103 into accounting entries which have relevance in the characterization of operations respective to cost control, corporate performance reporting, and tax return preparation; these programs may also define accounting entries without a need for reference to Business Enterprise Database 103. The output from the programs in Business Enterprise Function Programs 105 functioning to define accounting entries is, however, stored in a database type of data schema defined herein as Accounting Balance Data 107. The general relationships between Business Enterprise Database 103, Business Enterprise Function Programs 105, and Accounting Balance Data 107 are very common in most business enterprises which have evolved to a size prompting general integration of their business enterprise computing activities and should be generally apparent.
Usually, the amount of information in Accounting Balance Data 107 is fairly extensive, and the information therein can be updated or changed at any moment in time. In a system such as the present invention, there is a need to establish a defined set of data from Accounting Balance Data 107 at essentially a moment in time, and there is also frequently a need to manage the times when the file is accessed by a user (person or process) when a substantial number of records need to be individually read so that general access to the file is managed to be as prompt as possible for all users. A first step in achieving this is to have a program in Business Enterprise Function Programs 105 which periodically runs to generate a conveniently sized listing of entries respective to a certain need; and, in the preferred embodiment of the present invention, such a program is used to periodically read records in Accounting Balance Data 107 to generate an Transaction Activity Log 203 (shown in FIG. 2) within Transaction Activity Preparation System 109. Details of Transaction Activity Preparation System 109 will be further discussed respective to FIG. 2.
Transaction Activity Preparation System 109 is read and referenced by Accrual Logical Engine 117 which also reads and references information from Reference Tables 115; Accrual Logical Engine 117 then performs a process further described respective to FIGS. 5 and 6 to generate tax accrual data values, and Accrual Logical Engine 117 then writes selected tax accrual data values into Accounting Balance Data b 107.
A set of tables are held within a data schema defined herein as Reference Tables 115, which holds tax information in the form of tax data respective to the tax jurisdiction codes in the form of data elements descriptive of the tax information. These tables, their affiliated data elements, logical identifiers, data element definitions, and exemplary formats are shown in the following paragraphs.
              TABLE 1                                                     
______________________________________                                    
Order Type Inclusion                                                      
The following table is an embodiment of an Order Type Inclusion Table.    
It                                                                        
shows all of the general Order Types that will be included in the         
use-tax                                                                   
accrual calculation.                                                      
______________________________________                                    
Order Type Inclusion Table                                                
Order   Type                                                              
Type    Indic        From Date                                            
                                 To Date                                  
FA      PO          01/01/1996                                            
                                12/31/2099                                
FB      PO          01/01/1996                                            
                                12/31/2099                                
FP      PO           01/01/1996                                           
                                12/31/2099                                
ID      IN          01/01/1996                                            
                                12/31/2099                                
IE      IN          01/01/1996                                            
                                12/31/2099                                
IK      IN          01/01/1996                                            
                                12/31/2099                                
IP      IN          01/01/1996                                            
                                12/31/2099                                
IR      IN          01/01/1996                                            
                                12/31/2099                                
______________________________________                                    
Field Name                                                                
         Description           Example                                    
______________________________________                                    
Order Type                                                                
         A two digit character that identifies a                          
                                 FA, FB                                   
             specific type of limited-term account.                       
Type Indic                                                                
         A two digit character that identifies an Order                   
                                PO, IN                                    
             Type to the use-tax accrual system.                          
From Date                                                                 
          This is the starting date that the record is                    
                                01/01/1996                                
             valid.                                                       
To Date     This is the expiration date of the record.                    
                                12/31/2099                                
______________________________________                                    

              TABLE 2                                                     
______________________________________                                    
Cost Center and Order Type Exclusion Table                                
The following table is an embodiment of a Cost Center and Order Type      
Exclusion Table. It shows all of the Cost Centers and Order Types that    
will be excluded in the use-tax accrual calculation.                      
______________________________________                                    
Cost Center Exclusion Table                                               
                     From     To                                          
Co   Pl      From     Cost Center                                         
                              Cost Center                                 
                                         To                               
mp   nt      Date     (Order Type)                                        
                               (Order Type)                               
                                        Date                              
______________________________________                                    
12   AP      01/01/1996                                                   
                      MFG1     MFG1           12/31/2099                  
12   AP      01/01/1996                                                   
                      MFG2     MFG2           12/31/2099                  
12   AP      01/01/1997                                                   
                       PRG1    PRG1           12/31/1997                  
______________________________________                                    
Field Name                                                                
         Description          Example                                     
______________________________________                                    
Comp             Each company, legal entitiy, has a two                   
                                12, 01                                    
                 digit numeric character assigned.                        
Plnt             Each plant, process-section of the                       
                                AP, YM                                    
                 company has a two digit                                  
                 alpha/numeric character assigned.                        
From Date                                                                 
                This is the starting date that the                        
                                01/01/1996                                
                 record is valid.                                         
From Cost                                                                 
              This is the starting Cost Center or                         
                                MFG1, MFG2                                
Center          Order Type of the record. Cost                            
(Order Type)                                                              
                 Center is an ongoing account used to                     
                 collect costs. Order Type is a limited-                  
                 term account used to collect costs. A                    
                 plant could have several Cost Centers                    
                 and/or Order Types.                                      
To Cost Center                                                            
          This is the ending Cost Center of the                           
                                MFG1, MFG2                                
(Order Type)                                                              
              record. Cost Center is an ongoing                           
                                PRG1                                      
                 account used to collect costs. Order                     
                 Type is a limited-term account used                      
                 to collect costs. A plant could have                     
                 several Cost Centers and/or Order                        
                 Types.                                                   
To Date         This is the expiration date of the                        
                                12/31/2099                                
                              record.                                     
______________________________________                                    

              TABLE 3                                                     
______________________________________                                    
Cost Element Exclusion Table                                              
The following table is an embodiment of a Cost Element Exclusion Table.   
It shows all of the Cost Elements that will be excluded from the use-tax  
accrual calculation.                                                      
______________________________________                                    
Cost Element Exclusion Table                                              
Co  Pl               From     To                                          
mp   nt    From Date   Cost Element                                       
                                Cost Element                              
                                        To Date                           
______________________________________                                    
12   01    01/01/1996                                                     
                      600396         600396                               
                                             12/31/2099                   
12   01    01/01/1996                                                     
                      605999         605999                               
                                             12/31/2099                   
12   01    01/01/1996                                                     
                      620002         620003                               
                                             12/31/2099                   
12   01    01/01/1996                                                     
                      621097         621097                               
                                              12/31/2099                  
12   01    01/01/1996                                                     
                      621098         621098                               
                                             12/31/2099                   
12   01    01/01/1996                                                     
                      623000         623097                               
                                             12/31/2099                   
12   01    01/01/1996                                                     
                      641097         641097                               
                                             12/31/2099                   
______________________________________                                    
Field Name                                                                
         Description         Example                                      
______________________________________                                    
Comp           Each company, legal entity, has a                          
                                    12, 01                                
               two digit numeric character                                
               assigned.                                                  
Plnt           Each plant, process-section of the                         
                                   01, YM, S1                             
               company, has a two digit                                   
               alpha/numeric character assigned.                          
From Date                                                                 
              This is the starting date that the                          
                                   01/01/1996                             
               record is valid.                                           
From Cost                                                                 
           This is the starting Cost Element of                           
                                 600396, 600599                           
Element        the record.  Cost Elements are used                        
               to categorize the type of spending,                        
               e.g. salaries, materials and supplies.                     
To Cost      This is the ending Cost Element of                           
                                   600396, 600599                         
Element        the record.  Cost Elements are used                        
               to categorize the type of spending,                        
               e.g. salaries, materials and supplies.                     
To Date       This is the expiration date of the                          
                                   12/31/2099                             
               record.                                                    
______________________________________                                    

              TABLE 4                                                     
______________________________________                                    
The following table is an embodiment of a Cost Element Inclusion Table.   
It assigns an indicator to each Cost Element included in the use-tax      
accrual                                                                   
calculation.                                                              
______________________________________                                    
Cost Element Inclusion Table                                              
             From      Cost Element                                       
                                 Labor/                                   
                                       To                                 
Comp  Plant  Date      From  To    Utility                                
                                          Date                            
______________________________________                                    
12                 01/01/1996                                             
                         600000                                           
                               620000                                     
                                     M       12/31/2099                   
12                 01/01/1996                                             
                         630000                                           
                               635000                                     
                                     L       12/31/2099                   
12                 01/01/1996                                             
                         640000                                           
                               650000                                     
                                     U         12/31/2099                 
12    AP         01/01/1996                                               
                         600000                                           
                               620000                                     
                                     M       12/31/2099                   
12        AP     01/01/1996                                               
                         630000                                           
                               635000                                     
                                     L          12/31/2099                
______________________________________                                    
Field Name                                                                
        Description           Example                                     
______________________________________                                    
Comp         Each company, legal entity, has a two                        
                               12, 01                                     
             digit numeric character assigned.                            
Plant        Each plant, process-section of the                           
                                01, YM, S1                                
             company, has a two digit                                     
             alpha/numeric character assigned.                            
From Date                                                                 
            This is the starting date that the record                     
                               01/01/1996                                 
             is valid.                                                    
From Cost                                                                 
                 This is the starting Cost Element of the                 
                               600000, 630000                             
Element      record. Cost Elements are used to                            
             categorize the type of spending, e.g.                        
             salaries, materials and supplies, labor,                     
             and utilities.                                               
To Cost            This is the ending Cost Element of the                 
                               620000, 635000                             
Element      record. Cost Elements are used to                            
             categorize the type of spending, e.g.                        
             salaries, materials and supplies, labor,                     
             and utilities.                                               
Labor/Utility                                                             
            This two digit aplhabetical character                         
                               M, L, U, O, US                             
             assigns an indicator type to each Cost                       
             Element.                                                     
To Date     This is the expiration date of the                            
                                12/31/2099                                
             record.                                                      
______________________________________                                    

                                  TABLE 5                                 
__________________________________________________________________________
Cost Object Inclusion and Taxable Percentage Table                        
The following table is an embodiment of a Cost Object Inclusion and       
Taxable                                                                   
Percentage Table.  It shows the tax percentage respective to taxes by     
Cost Element                                                              
type (material, labor, utility, and the like) for each Order Type and     
Cost Center.                                                              
__________________________________________________________________________
Cost Object Inclusion and Taxable Percentage Table                        
                            C   Tax#1                                     
                                     thru                                 
                                         Tax#6                            
Co                                                                        
   Pl                                                                     
      Order Type                                                          
           Cost                                                           
                 From                                                     
                     Update                                               
                          R                                               
                               DO                                         
                                 Rerun1                                   
                                     thru                                 
                                          Rerun6                          
mp                                                                        
  nt                                                                      
    Number                                                                
          Centr                                                           
              Date  Year                                                  
                        TO                                                
                          St                                              
                            T I Ty % Ty                                   
                                       % Ty %                             
__________________________________________________________________________
12                                                                        
   01                                                                     
      A.089.0.0                                                           
                 01/01/1995                                               
                      1995                                                
                            IN                                            
                              P                                           
                                  M                                       
                                     50                                   
                                         65                               
                                          U   80                          
                                  US                                      
                                    90                                    
                                         75                               
                                              0                           
                                  M                                       
                                     0                                    
                                       0L                                 
                                           U                              
                                              0                           
                                  US                                      
                                    0                                     
                                       0O                                 
                                              0                           
12                                                                        
   AP                                                                     
           MFG3                                                           
                 01/01/1995                                               
                     1996                                                 
                           IN                                             
                              C                                           
                               Y                                          
                                 M   50                                   
                                       70                                 
                                          U   20                          
                                  US                                      
                                    30                                    
                                       40                                 
                                              0                           
                                  M                                       
                                     0                                    
                                       0L                                 
                                           U                              
                                              0                           
                                  US                                      
                                    0                                     
                                         0                                
                                               0                          
__________________________________________________________________________
Field Name      Description         Example                               
__________________________________________________________________________
Comp                           Each company, legal entity, has a          
                                       12, 01                             
                               digit numeric character assigned.          
Plnt                           Each plant, process-section of             
                                       AP, YM, S1                         
                               company, has a two digit                   
                               alpha/numeric character assigned.          
Order Type             Order Type is a limited-term account               
                                       A.089.0.0                          
Number                  used to collect costs for limited-term            
                        items, e.g. addition to a building,               
                        remodeling of a plant                             
Cost Centr             Cost Center is an ongoing account                  
                                       MFG3                               
(Cost Center)          to collect costs.  A plant could have              
                        several Cost Centers.                             
From Date              This is the starting date that the                 
                                      01/01/1996                          
                        is valid.                                         
Update Year            The year the record was updated.                   
                                        1995                              
RTO                     The two digit alphabetical character              
                                       IN, MI, TX                         
                        assigned to a regional tax office.                
                        Regional tax office is the office that            
                        handles a specific area of the country.           
State                   Two digit alphabetical character                  
                                        IN, OH, TX                        
                        assigned to a state.                              
COT                     Each record has a C or P                          
                                         C, P                             
(Cost Objective Type:                                                     
                      assigned whether it is a Cost                       
Cost Center or Order                                                      
                      Center or Order Type.                               
Type)                                                                     
DI                      Each record may be assigned a                     
                                        Y                                 
(deletion indicator)                                                      
                      deletion indicator when it is no                    
                        longer valid.                                     
Tax #1 thru Tax #6                                                        
                  Each indicator type, L, M, U,                           
                                        M 50%                             
                        US, O has a taxable percent                       
                                        L 100%                            
                        assigned.                                         
Rerun #1 thru Rerun                                                       
                     This has the same field format                       
                                        M 50% L                           
#6                      as the above field. It can be                     
                                        100%                              
                        used for changing the                             
                        percentages and rerunning the                     
                        system.                                           
__________________________________________________________________________

              TABLE 6                                                     
______________________________________                                    
Tax Jurisdiction Code Table                                               
The following table is an embodiment of a Tax Jurisdiction Code Table.    
It shows the tax jurisdiction for each Order Type and Cost                
______________________________________                                    
Center.                                                                   
Tax Jurisdiction Code Table                                               
Co  Pl    Order Type Cost        Date  T   R   Tax Jur                    
mp   nt    Number        Center                                           
                              St  From    Y                               
                                            TO  Code                      
______________________________________                                    
12   01    A.089.0.0          IN            INP                           
                                               41500                      
12   AP                     MFG1                                          
                              IN            INC                           
                                               41500                      
12   AP                     PINEPOW                                       
                              IN            INC                           
                                               78657                      
______________________________________                                    
Field Name Description         Example                                    
______________________________________                                    
Comp                      Each company, legal entity, has                 
                                  12, 01                                  
                          two digit numeric character                     
                                       assigned.                          
Plnt                      Each plant, process-section of                  
                                          AP, YM, S1                      
                          the company, has a two digit                    
                          alpha/numeric character                         
                                       assigned.                          
Order Type Number                                                         
                 Order Type is a used to collect                          
                                          A.089.0.0                       
                   cost for limited-term accounts,                        
                   e.g. addition to a building or                         
                   remodeling of a plant                                  
Cost Center                                                               
                  Cost Center is an ongoing                               
                                          Hani                            
                           account used to collect costs.                 
                   A plant could have several Cost                        
                                       Centers.                           
St                 Two digit alphabetical character                       
                                   IN, OH, TX                             
(State)           assigned to a state.                                    
Date From         This is the starting date that the                      
                                        01/01/1996                        
                   record is valid.                                       
TY                 Each record has a C or P                               
                                    C, P                                  
(Type)             assigned whether it is a Cost                          
                                       Center or Order Type.              
RTO                The two digit alphabetical                             
                                          IN, MI, TX                      
                   character assigned to a regional                       
                   tax office. Regional tax office                        
                   is the office that handles a                           
                       specific area of the country.                      
Tax Jur Code                                                              
                           Tax jurisdiction code which                    
                                   78657                                  
                   determines the tax rate. In this                       
                   instance the postal zip code is                        
                   used as a tax jurisdiction code.                       
______________________________________                                    

              TABLE 7                                                     
______________________________________                                    
Tax Rate Table                                                            
The following table is an embodiment of a tax rate table. It shows all    
of                                                                        
the tax rates by tax jurisdiction code.                                   
______________________________________                                    
Tax Rate (by Jurisdiction) Table                                          
Tax Jur  State  From                 Tax                                  
Code       Abbr   Date       Description                                  
                                       Rate                               
______________________________________                                    
41500      IN     01/01/1996                                              
                            INDIANA        5.0000                         
76523      CA     01/01/1996                                              
                            CALIFORNIA                                    
                                        4.5000                            
77440      TX     01/01/1996                                              
                            TEXAS           6.2500                        
78657      IN     01/01/1996                                              
                            INDIANA        7.0000                         
78955      IN     01/01/1996                                              
                            INDIANA        7.0000                         
85205       IN    01/01/1996                                              
                              INDIANA                                     
                                           7.0000                         
______________________________________                                    
Field Name Description        Example                                     
______________________________________                                    
Tax Jur Code                                                              
               Tax jurisdiction which determines                          
                                 76523, 77440                             
(Tax Jurisdiction                                                         
             the tax rate. In this instance the                           
Code)           postal code is used as a tax                              
                jurisdiction code.                                        
State Abbr     Two Digit alphabetical state                               
                                 IN, CA                                   
                abbreviation.                                             
From Date      This is the starting date that the                         
                                 01/01/1996                               
                record is valid.                                          
Description                                                               
               Description of the tax jurisdiction.                       
                                Indiana,                                  
                                     California                           
Tax Rate       Use-tax rate which is applicable                           
                                 5.0000, 4.0000                           
                for the tax jurisdiction on the                           
                record.                                                   
______________________________________                                    

              TABLE 8                                                     
______________________________________                                    
Tax Cost Element Table                                                    
The following table is an embodiment of a Tax Cost Element Table. It      
assigns the Cost Elements included in the use-tax accrual calculation     
respective to a Cost Element.  In some respects, this is a convenience    
table                                                                     
helping to enable the mapping of some tax accruals into a summary tax     
category for convenient auditing.                                         
______________________________________                                    
9TYP Tax Cost Element Table                                               
Co       Cost Element   Tax Cost Element                                  
mp       From       To      To Charge                                     
______________________________________                                    
12        600000     606097 663068                                        
12        613000     614097 663008                                        
12        620022     620032 663058                                        
12        630000     630006 663008                                        
12        630012     630012 663058                                        
12        640015     640015 663058                                        
12        640036     640037   663058                                      
______________________________________                                    
Field Name                                                                
        Description          Example                                      
______________________________________                                    
Comp          Each company, legal entity, has                             
                              12, 01                                      
              a two digit numeric charater                                
              assigned.                                                   
From Cost                                                                 
           This is the starting Cost Element of                           
                             600000, 630000                               
Element       the record. Cost Elements are used                          
              to categorize the type of spending,                         
              e.g. salaries, materials and supplies.                      
To Cost      This is the ending  Cost Element                               
                              620000, 635000                              
Element       of the record. Cost Elements are                            
              used to categorize the type of                              
              spending, e.g. salaries, materials                          
              and supplies.                                               
Tax Cost                                                                  
           Tax Cost Element specifically                                  
                              663008, 663068                              
Element           set up to collect use-taxes.                            
To Charge                                                                 
______________________________________
Reference Tables 115 are updated and changed by Tax Rate Acquisition System 113 (Further discussed with respect to FIG. 3) and by Table Loading Logical Engine 121; Tax Rate Acquisition System 113 acquires tax rate information from Tax Rate Information Source 111 (also further discussed with respect to FIG. 3). Table Loading Logical Engine 121 is substantially a straightforward data schema interface logical engine which enables a human to use Monitor and Report Interface 123 (a standard terminal or workstation interface) to access and read both Accounting Balance Data 107 and Reference Tables 115 data and then make specific database entries to modify the data in Reference Tables 115 as the human references some external sources of tax data and other tax information; it should be noted that some of the external sources of information are publications from the jurisdictions themselves, which define the tax rates and tax information related to taxable percentages in their reports and records related to jurisdictional rule making. This human intervention is performed occasionally; although, in another embodiment, Table Loading Logical Engine 121 has some embedded subprograms which activate automatically to access both Accounting Balance Data 107 and Reference Tables 115 data and then make specific database entries into Reference Tables 115 to update certain fields in Reference Tables 115 in a manner which should generally be apparent. It should be noted that the level of access protection given to an individual operating Monitor and Report Interface 123 in accessing and modifying specific database entries (within Reference Tables 115) is preferably more restrictive and specific than the protection given to individuals using Monitor and Report Interface 125 (for the Reversal Logical Engine 119), Monitor and Report Interface 127 (for the Reference Tables 115), and Monitor and Report Interface 129 (for the Accrual Logical Engine 117); for these last three interfaces do not have the same ability to fundamentally alter the information in Reference Tables 115 without any limitation to the scope of the modifications being implemented. These Monitor and Report Interfaces (125, 127, and 129) generally function to facilitate logic and provide output either (a) to print reports (when operated in conjunction with printing hardware or with a screen display), (b) to enable well defined processes to be initiated (via a keyboard and screen display), or (c) to enable examination and, optionally, alteration of specific predefined data fields.
A feature in the present invention respective to the portion of the database identified by cost elements "Rerun #1" thru "Rerun #6" in the Cost Object Inclusion And Taxable Percentage Table (Table 5) enables corrected filings after a tax report has been defined and the information in Accounting Balance Data 107 has been "finalized". In this regard, judgments on the part of personnel within the business enterprise are subject to auditing and review; in some cases, certain of those judgments by personnel within the business enterprise respecting tax rates are occasionally challenged and/or corrected through the process of auditing and review conducted subsequent to the filing of a tax report. When a correction (pursuant to the auditing and review process) is in order, a corrected tax report must be generated. By preserving a copy of the Transaction Activity Log 203 (or derived transaction information) used in defining a tax report, providing the "Rerun #1" thru "Rerun #6" data element types in the Cost Object Inclusion And Taxable Percentage Table (Table 5), and providing a logical indicator for selecting use of the "Rerun #1" thru "Rerun #6" data element types, corrective reports can be output by the tax accrual system logic where the Accrual Logical Engine 117 reprocesses the information contained in the archived copy of the Transaction Activity Log 203 (or derived transaction information) and, referencing the selecting indicator, uses the Tax # (from the original report) and Rerun # data elements to define a corrective report. In this manner, the present invention provides logic, data, and a method for generating an amended tax report which enables corrections to be filed reconciling previously-filed tax reports respective to the findings of an auditor or other entity reviewing filed tax reports for the business enterprise.
Tax Accrual System Logic Overview 101 also shows Reversal Logical Engine 119 which also reads and references information from Reference Tables 115 and Accounting Balance Data 107, executes a process further described respective to FIG. 7 which reduces the tax liability to reflect taxes which have already been paid, and then writes accrual data values into Accounting Balance Data 107 as debits and credits.
FIG. 2 presents further Details of Transaction Activity Preparation System 109 as Transaction Activity Preparation System Detail 201. As previously noted a program in Business Enterprise Function Programs 105 runs at a convenient time to periodically read records in Accounting Balance Data 107 and generate a conveniently sized Transaction Activity Log 203 within Transaction Activity Preparation System 109. The data schema of one embodiment of Transaction Activity Log 203 has field definitions as indicated in Table 9.
                                  TABLE 9                                 
__________________________________________________________________________
Transaction Activity Log Field Definitions                                
__________________________________________________________________________
DATA: BEGIN OF EXP-ACT-RCD,                                               
                  "Expense Activity Rcd Layout"                           
HIERARCHY(03)     TYPE C,                                                 
RFGL-COMPANY(04)     TYPE C,                                              
PLANT-CODE(02)        TYPE C,                                             
RECORD-TYPE(01)      TYPE C,                                              
COST-CENTER(08)      TYPE C, "may contain order number"                   
MATERIAL-PRODUCED(08)                                                     
                     TYPE C,                                              
COST-ELEMENT(08)     TYPE C,                                              
SENDING-COMPANY(04)                                                       
                     TYPE C,                                              
SENDING-PLANT(02)    TYPE C,                                              
SENDING-CCNTR(08)    TYPE C,                                              
SENDING-ACTIVITY(03)                                                      
                     TYPE C,                                              
SENDING-SUBACTIVITY(03)                                                   
                    TYPE C,                                               
SENDING-MATL-ID(08)                                                       
                     TYPE C,                                              
EXTRACT-DATE(08)     TYPE D,                                              
EXTRACT-TIME(06)     TYPE C,                                              
TYPE-INDICATOR(01)                                                        
                     TYPE C,                                              
EXPENSE-DATA-TYPE(01)                                                     
                     TYPE C,                                              
PLAN-VERSION(01)     TYPE C,                                              
ORDER-TYPE(02)        TYPE C,                                             
ORDER-RESP-PLANT(020)                                                     
                     TYPE C,                                              
ORDER-RESP-CCNTR(08)                                                      
                     TYPE C,                                              
ORDER-DESCRIPTION(30)                                                     
                     TYPE C,                                              
PROJECT-NUMBER(16)                                                        
                     TYPE C,                                              
ORDER-HIERARCHY(16)                                                       
                     TYPE C,                                              
UPDATE-PERIOD(06)    TYPE C,                                              
LOCAL-CURR-CODE(05)                                                       
                     TYPE C,                                              
UNIT-OF-MEASURE-(02)                                                      
                     TYPE C,                                              
ACTUAL QUANTITY(08)                                                       
                     TYPE P DECIMALS 3,                                   
ACTUAL-LOCAL-CURR(08)                                                     
                     TYPE P DECIMALS 2,                                   
ACTUAL-US-DOLLARS(08)                                                     
                     TYPE P DECIMALS 2,                                   
TARGET-QUANTITY(08)                                                       
                     TYPE P DECIMALS 3,                                   
TARGET-LOCAL-CURR(08)                                                     
                     TYPE P DECIMALS 2,                                   
TARGET-US-DOLLARS(08)                                                     
                     TYPE P DECIMALS 2,                                   
PLAN-QUANTITY(08)    TYPE P DECIMALS 3,                                   
PLAN-LOCAL-CURR(08)                                                       
                     TYPE P DECIMALS 2,                                   
PLAN-US-DOLLARS(08)                                                       
                     TYPE P DECIMALS 2,                                   
PRICE-VAR-LOCAL(08)                                                       
                     TYPE P DECIMALS 2,                                   
PRICE-VAR-USD(08)                TYPE P DECIMALS 2,                       
__________________________________________________________________________
The data of Transaction Activity Log 203 is read by Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207.
The data of Transaction Activity Log 203 is still fairly extensive (see discussion of Business Enterprise Function Programs 105 and Transaction Activity Preparation System 109 respective to FIG. 1), and the information therein can be updated or changed at any moment in time by Business Enterprise Function Programs 105. Architecturally, Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207 establish a defined set of data from Transaction Activity Log 203 (at essentially a moment in time) at such times when Transaction Activity Log 203 is best accessed in a prompt manner so that all users of this file can have optimal response and stability of the collected data in the file.
Both Cost Center Transaction Extraction Logical Engine 205 and Order Type Transaction Logical Engine 207 (a) parse and selectively extract data necessary to define tax accrual from Transaction Activity Log 203 and (b) write output to one of two respective data schema: Cost Center Transaction Data 209 and Order Type Transaction Data 211. In this regard, Cost Center data relates to an ongoing account type which collects costs for established accounts within the accounting system, and Order Type data relates to a limited-term account type which collects costs for accounts which are appropriate to Order Types identified as more short-term in potential duration than the ongoing accounts within the accounting system. Respective to the two categories, the records in the Transaction Activity Log 203 have somewhat different active fields, and, in the preferred embodiment, it was considered more convenient to open files and handle the data in the context of the two categories by use of processes deployed in the generally parallel design depicted instead of via a single unified process that would discriminate records by field layout; other embodiments for solving this need include a single logical engine having two subroutines respective to the different record types, unified record types, and the like, as should be apparent. Process details for reading records from Transaction Activity Log 203, parsing the record, selecting data for the accrual process, and writing data as output into one of the Cost Center Transaction Data 209 and Order Type Transaction Data 211 data schema should be apparent. Cost Center Transaction Data 209 and Order Type Transaction Data 211 data schema, therefore, hold tax accrual source information for use by Accrual Logical Engine 117 in a stable and fixed form for a particular instance of tax accrual determination; in this regard, a "snapshot" of transaction activity for a period of time is created and can be preserved.
Turning now to FIG. 3, Tax Rate Acquisition System Detail 301 shows other parts of Tax Rate Acquisition System 113 as it acquires tax rate information from Tax Rate Information Source 111 for updating and changing of Reference Tables 115. Tax Rate Information Source 111 can be a database in a computer-implemented system accessible via a network linkage (such as via the Internet), it can be a set of data available in a data schema available on a computer readable disk, or it could be a data file which is periodically updated by a human (via a system and method not shown, but which should be apparent). The information in Tax Rate Information Source 111 changes periodically as different jurisdictions modify their respective tax provisions. The information in Tax Rate Information Source 111 is, therefore, a summary of this detailed information in conveniently available form. One source of such a set of data is Fast-Tax Rate File which is available from CLR Fast-Tax Corporation located in Carrollton, Tex.
Tax Rate Acquisition Logical Engine 307 reads the information from Tax Rate Information Source 111 either automatically or as prompted by a human via Monitor and Report Interface 309 to obtain a recent set of tax rate data elements. Tax Rate Acquisition Logical Engine 307 selects a subset of the information from Tax Rate Information Source 111 of interest to the particular business enterprise and writes the newly acquired tax information to New Tax Rate Database 305 to hold an unchanging and business-enterprise-relevant subset of the information. Tax Rate Uploading Logical Engine 303 reads the data in New Tax Rate Database 305 and updates appropriate tables in Reference Tables 115. Monitor and Report Interface 309 (for the Tax Rate Acquisition Logical Engine 307) and Monitor and Report Interface 311 (for the Tax Rate Uploading Logical Engine 303) enable reporting and interaction to human technicians as the processes execute to modify the tax rate information. Details for implementing the above data schema and logical engines should be apparent.
FIG. 4 shows a general overview of the larger General Tax Accrual Process 401. In this regard, a first Transaction Collection Step 403 needs to occur on a periodic basis so that all accounting transactions for a period of time are collected together to serve as inputs to the general tax accrual process. As a second general Liability Account Debiting Step 405, sales taxes which have already been paid (a requirement in some jurisdictions) need to be figured and retained as liability debits to decrease the use-tax which will be paid. Then, in Tax Determination and Accrual Step 407, use-taxes can be defined for all transactions as liability credits (Note that a liability credit will generate an increase in the tax that will need to be paid to an outside jurisdiction, while a liability debit is a decrease in the tax that will need to be paid to the outside jurisdiction).
Accrual Logical Engine Cost Center Process 501 is shown in FIG. 5 and Accrual Logical Engine Order Type Cost Process 601 is shown in FIG. 6. These two processes are logically executed by the computer in series as a unified entity (connected at Initiate Order Type Portion Step 521) by Accrual Logical Engine 117 to perform a process generating tax accrual data values and writing selected tax accrual data values into Accounting Balance Data 107.
FIG. 5 shows initiation of the Accrual Logical Engine Cost Center Process 501 with Start Step 503 where Accrual Logical Engine 117 opens Accounting Balance Data 107, Reference Tables 115, and Cost Center Transaction Data 209 for access. In Read New Cost Center Record Step 505, Accrual Logical Engine 117 reads a first (or new) record from Cost Center Transaction Data 209, and parses the Cost Center field. Referencing information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115, Accrual Logical Engine 117 executes Relevant Cost Center Decision Step 507 by comparing the Cost Center for the record with the included Cost Centers to decide if this record should proceed to Extract Cost Element Step 508 or to Last Cost Center Transaction Decision Step 519. If a match is identified, and the Cost Center is thereby to be included, Accrual Logical Engine 117 proceeds to extract the Cost Element in Extract Cost Element Step 508. Accrual Logical Engine 117 then proceeds to Relevant Cost Element Decision Step 509, references information in Table 4 (Cost Element Inclusion Table) in Reference Tables 115, and compares the Cost Element for the record with the included Cost Elements in that table to decide if this record should proceed to Step 519 or to (Cost Center) Taxable Percentage Definition Step 511. If a match is identified, and the Cost Center is thereby to be included, Accrual Logical Engine 117 proceeds to Step 511, references information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115 to acquire the relevant taxable percentage, and holds this percentage in its logic. Accrual Logical Engine 117 proceeds to (Cost Center) Postal Delivery Code Identification Step 513, references information in Table 6 (Tax Jurisdiction Code Table) in Reference Tables 115 to acquire the tax jurisdiction code, and holds this code in its logic. In this regard, the described embodiment uses the U.S. Postal Zone Improvement Plan (ZIP) code relevant to this Cost Center. It should be noted that, in the described embodiment, the Cost Centers are always defined to have relevance only within a unique one and only one particular state, so there is no need to execute Step 513 prior to Step 511. However, in another embodiment where the Cost Centers are relevant in more than one state, Accrual Logical Engine 117 executes Step 513 prior to Step 511. In another embodiment, a geopolitical demographic allocation file is used to enable allocation.
Accrual Logical Engine 117 next executes (Cost Center) Tax Rate Definition Step 515 by referencing information in Table 7 (Tax Rate Table) in Reference Tables 115 to acquire the tax rate relevant to the tax jurisdiction and holds this rate in its logic. Then, Accrual Logical Engine 117 proceeds to (Cost Center) Tax Computation and Storage Step 517 where the amount of expenditure respective to the Cost Element, the taxable percentage, and the tax rate are multiplied together to define the tax; the tax is then entered as a tax liability into the proper jurisdictional account in Accounting Balance Data 107 in conjunction with reference to information in Table 8 (Tax Cost Element Table).
Finally, respective to FIG. 5, Accrual Logical Engine 117 proceeds to Last Cost Center Transaction Decision Step 519 and ascertains if the last Cost Center record has been processed. Note that alternative routes to Step 519 are via Relevant Cost Center Decision Step 507 or Relevant Cost Element Decision Step 509 as previously discussed. Accrual Logical Engine 117 terminates Step 519 to Initiate Order Type Portion Step 521 if the last Cost Center record has been processed or to Read Cost Center Transaction Step 505 to acquire the next Cost Center transaction record if the last Cost Center record has not been processed.
FIG. 6 shows continuation of the unified process (connected at Initiate Order Type Portion Step 521) executed by Accrual Logical Engine 117 to generate tax accrual data values and write selected tax accrual data values into Accounting Balance Data 107. Accrual Logical Engine 117 continues the process begun with Accrual Logical Engine Cost Center Process 501 with Initiate Order Type Portion Step 521 where Accrual Logical Engine 117 opens Order Type Transaction Data 211 for access. In Read New Order Type Transaction Step 621, Accrual Logical Engine 117 reads a first record from Order Type Transaction Data 211 and parses the relevant Order Type field. Referencing information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) and Table 1 (Order Type Inclusion Table) in Reference Tables 115, Accrual Logical Engine 117 executes Relevant Order Type Decision Step 603 by comparing the Order Type for the record with the included Order Types (in this case the "Project Number") to decide if this record should proceed to Extract (Order Type) Cost Element Step 605 or to Last Order Type Transaction Decision Step 617. If a match is identified, and the Order Type is thereby to be included, Accrual Logical Engine 117 proceeds to extract the relevant Cost Element in Extract (Order Type) Cost Element Step 605. (In another embodiment, Order Type inclusion is established in Step 603 where an Order Type is always affiliated with a Cost Center and the inclusion decision proceeds by, firstly, identifying the affiliated Cost Center respective to the Order Type and, secondly, comparing the affiliated Cost Center to the included Cost Centers in Table 5.) Accrual Logical Engine 117 then proceeds to Relevant (Order Type) Cost Element Decision Step 607, references information in Table 4 (Cost Element Inclusion Table) in Reference Tables 115, and compares the related Cost Element for the record with the included Order Type Cost Elements in that table to decide if this record should proceed to Last Order Type Transaction Decision Step 617 or to (Order Type) Taxable Percentage Definition Step 609. If a match is identified, and the Order Type is thereby to be included, Accrual Logical Engine 117 proceeds to Step 609, references information in Table 5 (Cost Object Inclusion And Taxable Percentage Table) in Reference Tables 115 to acquire the relevant taxable percentage, and holds this percentage in its logic. Accrual Logical Engine 117 proceeds to (Order Type) Postal Delivery Code Identification Step 611, references information in Table 6 (Tax Jurisdiction Code Table) in Reference Tables 115 to acquire the tax jurisdiction code, and holds this code in its logic. In this regard, as was also noted respective to the FIG. 5 description, the described embodiment uses the U.S. Postal Zone Improvement Plan (ZIP) code relevant to this Order Type. It should be noted that, in the described embodiment, Order Type accounts are defined to have relevance uniquely within one and only one state, so there is no need to execute Step 611 prior to Step 609. However, in another embodiment where Order Type accounts are relevant in more than one state, Accrual Logical Engine 117 executes Step 611 prior to Step 609. In another embodiment, a geopolitical demographic allocation file is used to enable allocation.
Accrual Logical Engine 117 next executes (Order Type) Tax Rate Definition Step 613 by referencing information in Table 7 (Tax Rate Table) in Reference Tables 115 to acquire the tax rate relevant to the tax jurisdiction and holds this rate in its logic. Then, Accrual Logical Engine 117 proceeds to (Order Type) Tax Computation and Storage Step 615 where the amount of expenditure respective to the Cost Element, the taxable percentage, and the tax rate are multiplied together to define the tax; the tax is then entered as a tax liability into the proper jurisdictional account in Accounting Balance Data 107.
In another embodiment, assurance that the Cost Object data elements are interactively harmonious and mutually comprehensive can be achieved by executing a comparison of the Cost Center against both an inclusion table such as Table 4 (Cost Element Inclusion Table) and an exclusion table such as Table 2 (Cost Center and Order Type Exclusion Table) when executing (e.g.) Relevant Cost Center Decision Step 507 and thereby comparing the Cost Center for the record with an included Cost Center reference and an excluded Cost Center reference to decide if this record should proceed to Extract Cost Element Step 508 or to Last Cost Center Transaction Decision Step 519. Similarly, (e.g.) in Relevant Cost Element Decision Step 509, references to Table 4 and Table 3 (Cost Element Exclusion Table) in Reference Tables 115 and comparison of the Cost Element for the record with the included and excluded Cost Elements in those tables; references to Table 5 (Cost Object Inclusion And Taxable Percentage Table), Table 1 (Order Type Inclusion Table), and Table 2 (Cost Center and Order Type Exclusion Table) in Relevant Order Type Decision Step 603 and comparison of the Order Type for the record with the included and excluded Order Types in those tables; and references to Table 4 and Table 3 in Extract (Order Type) Cost Element Step 605 and comparison of the Cost Element for the record with the included and excluded Cost Elements in those tables help in establishing a data schema cross-check as the personnel using the present invention establish two separate types of tables indicating (as a first paradigm of inclusion) what is to be included and (as a second paradigm of exclusion) what is not to be excluded so that the computer executed logic can confirm both paradigms against the cost objects being processed and thereby achieve interactive harmony and mutual comprehensiveness in the references applied to the particular accounting records which are being used to define the accrued use-taxes. In this regard, the "inclusion" check could be executed first in one embodiment, or the "exclusion" check could be performed first in another embodiment. Another embodiment uses a less definite "exclusion" only check with default inclusion (the benefit being a smaller and less costly data schema size); yet another embodiment uses the less definite "exclusion" check with general default inclusion but with the addition of a limited set of additional specific inclusion checks for those data objects of special importance to the business enterprise. To facilitate closure, in another embodiment, the exclusion and inclusion data entries can be further compared to a master list to help establish that "all cost objects are present and accounted-for" and that no cost object is both included and excluded; as should be apparent, if a cost object has a reason to be both included and excluded, the cost object may not be properly detailed for the larger goals of the accounting needs of the business enterprise and an indication is thereby established that a further set of fundamental cost objects respective to that "dichotomously designated" cost object is needed.
Finally, respective to FIG. 6, Accrual Logical Engine 117 proceeds to Last Order Type Transaction Decision Step 617 and ascertains if the last Order Type record has been processed. Note that alternative routes to Step 617 are via Relevant Order Type Decision Step 603 or Relevant (Order Type) Cost Element Decision Step 607 as previously discussed. Accrual Logical Engine 117 terminates Step 617 to End Step 619 if the last Order Type record has been processed or to Read Order Type Transaction Step 621 to acquire the next Order Type transaction record if the last Order Type record has not been processed. In End Step 619, Accrual Logical Engine 117 closes all open files and generates a report to Monitor and Report Interface 129 (reporting interface logic for the Accrual Logical Engine 117).
Turning now to FIG. 7, Reversal Logical Engine 119 executes Reversal Logical Engine Process 701 to decrease the tax liability in a particular jurisdiction by debiting the liability with taxes which have already been paid as sales taxes at the time when the business enterprise acquired goods or services. In understanding the purpose of this feature in the present invention, it should be noted that the payment of sales tax in some jurisdictions must take place at the time of sale and must be collected by the seller; whereas, in other jurisdictions, the payment of sales tax in some jurisdictions may be accrued in an account by the purchaser for a period of time of sale and then paid as a part of a single payment (as a "use-tax"). Since jurisdictions extend certain tax benefits during certain times to influence and encourage certain types of activities (e.g. investment in Order Types which enhance environmental quality, expansion of the business enterprise base of the jurisdiction by encouraging industrial processing within that jurisdiction, and cooperative support with the jurisdiction of socially beneficial initiatives), effective "use-taxes" and "sales taxes" are, at times, different respective to certain goods and services. Another situation where a use-tax in some cases should be declared and paid occurs when an article is purchased in one jurisdiction and then transported into another jurisdiction for use (or when the cumulative value of a set of such articles purchased with a defined period of time and so transported exceeds a certain value threshold). One of the benefits of the present invention is that a holistic system is enabled which addresses both accrual of tax debits and credits while also enabling resolution of tax debits and credits paid in other ways than as a result of the accrual process in isolation. Reversal Logical Engine 119 is the logical engine within the present invention which executes logic to achieve that resolving feature. Two main account types facilitate these operations: an "enumerated liability account" type of account holding a listing of records respective to individual purchases of goods and services, and an "accrual liability account" type of account holding a single value which represents the appropriate cumulative impact of all entries and considerations in a respective "enumerated liability account". In the described embodiment, there is an accrual liability account for each jurisdiction (ZIP code), although other ways of organizing such records and determining such accruals could alternatively be implemented through use of data record fields which establish pointers to define the jurisdictions respective to each accrual. In the described embodiment, the enumerated liability accounts are also organized by individual ZIP code; in the following discussion, the set of enumerated liability accounts will be treated as one extended enumerated liability account.
FIG. 7 shows initiation of Reversal Logical Engine Process 701 with Start Step 703 where Reversal Logical Engine 119 opens Accounting Balance Data 107 and Reference Tables 115 for access. Start Step 703 terminates to Read Enumerated Liability Account Record Step 705 where a record in the enumerated liability account is read. Then, in (Reversal) Postal Delivery Code Extraction Step 707, the location indicators in the enumerated liability account record are used in conjunction with information in the Tax Rate Table (Table 7) and the Tax Jurisdiction Code Table (Table 6) in Reference Tables 115 to identify the postal delivery code respective to the destination of the transaction in the enumerated liability account record. Next, in (Reversal) Tax Rate Definition Step 709, information in the Tax Rate Table (Table 7) in Reference Tables 115 is again referenced to define the proper tax rate for the enumerated liability account transaction. In the following Accrual Crediting Allocation Step 711, the ZIP Code field is compared to information in the Tax Jurisdiction Code Table (Table 6) in Reference Tables 115 and the respective enumerated liability account record is allocated for accrual. If no respective enumerated liability account record is identified for allocation, an entry is sent to an exception report via Monitor and Report Interface 125. Next, in Enumerated Liability Account Debiting and Accrual Liability Account Crediting Step 713, the allocated enumerated liability account is credited for the amount of the transaction and the accrual liability account is debited for the amount of the transaction (which had been previously paid to the jurisdictional tax authority). Reversal Logical Engine 119 then executes Last Enumerated Liability Account Record Decision Step 715 to determine if the logic should progress to End Step 717 or to Read Enumerated Liability Account Record Step 705 for reading the next enumerated liability account record. If the result of Last Enumerated Liability Account Record Decision Step 715 is to transfer the logic to End Step 717, Reversal Logical Engine 119 closes all open files and generates a report to Monitor and Report Interface 125 (for the Reversal Logical Engine 119).
Finally, a program in Business Enterprise Function Programs 105 executes to allocate the taxes defined by use of the present invention to different relevant jurisdictions respective to a location respective to each enumerated liability account and accrual liability account (e.g., a business enterprise in an urban location interacts with a city jurisdictional entity, a county jurisdictional entity, and a state jurisdictional entity). An example of such a program is in the CLR Fast-Tax product previously identified in this specification.
The present invention is, therefore, enabled through use of a machine which is a special purpose computer created by combining a general purpose computer with computer program code directed to the particular function of accrued use-tax determination (alternatively termed, e.g., accrued use-tax determination software, accrued use-tax determination computer program, accrued use-tax software, accrued use-tax determination program, and/or accrued use-tax determination computer-implemented logic) so that, when connected to an electrical power source, powered by electricity, and activated to execute the computer program code (software), the special purpose computer executes the particular function of accrued use-tax determination pursuant to the instructions from the computer program code. In a commonly deployed embodiment, the general purpose computer has electrically activated components denoted as a central processing unit (CPU), at least one physical memory connected to the CPU, an input keyboard connected to the CPU, an output display (which can include, without limitation, a printer, printing terminal where output is printed on paper, cathode ray tube monitor, and/or flat panel monitor) connected to the CPU, a computer clock pulse generator within the CPU for providing periodic signals which assist in latching and interconnecting internal circuits in the CPU and in synchronizing operations of the CPU in real-time, and a connection to electrical power for energizing all of the electrically activated components of the computer. The CPU further has control circuits, a bus, and specific computer circuits for either temporarily holding data (e.g., a register or an accumulator), for executing fundamental data processing operations (e.g., an addition circuit and/or a boolean logical operation circuit), or for executing types of instructions (e.g. an arithmetic logical unit or ALU combining arithmetic and logical operations into an essentially unified sub-circuit); the specific computer circuits are connected in communication to the control bus and, in some cases, to each other through latching circuits which can individually be in either a conducting (communicating) or non-conducting (non-communicating) configuration; the collective configurations of all the latching circuits at a particular moment define a particular state of the central processor; and the state of the central processor is respectively modified and changed from the individual instructions of the computer program code as they are successively accessed in the central processing unit in conjunction with the output of the clock pulse generator. The general purpose computer also has computer program code in the form of a commercially available operating system which functions as a computer program code platform for enabling the execution of the special purpose computer program code directed to the particular function of accrued use-tax determination. In overview, the present invention is implemented by and through partial use of a computer which has been programmed to perform the accrued use-tax determination; the general purpose computer functions as a medium for realizing the functionality provided by the computer program code's functionality. The preferred embodiment is deployed on an IBM 9021-9X2 or an IBM 9021-982 mainframe computer using the MVS operating system available from IBM, Old Orchard Road, Armonk, N.Y., 10504, and the SAP-R2 application system platform available from SAP America, Inc., 625 North Governor Printz Blvd., Essington, Pa. 19029. In some embodiments, some communication linkages within an extended form of the special purpose computer may be implemented by electrical, optical, or radio-frequency signal communication interfaces and communication media which collectively use electrically-powered transmitter and receiver components which are directly or indirectly linked to at least one central processing unit. As should be apparent, in some embodiments of the present invention, a set of networked or otherwise linked general purpose computers collectively function to execute the computer program code. FIG. 8 shows an embodiment of a general purpose computer 801 for use in implementing the present invention with a mainframe computer 803 being linked via a network 805 to a desktop workstation 807. The mainframe computer 803 and desktop workstation 807 each have a respective CPU 809 and CPU 811. The mainframe computer 803 and desktop workstation 807 each also have respective logic 813 and logic 815 interactive with the respective CPUs 809 & 811. The logic 813 includes the operating system for the mainframe computer 803 and the accrued use-tax determination computer-implemented logic of the present invention discussed with respect to FIGS. 1 through 7. The logic 815 of the desktop workstation includes the operating system for the desktop computer 803 and a terminal emulator which functions with the monitor 817 for enabling human interface to the logic 813 of the mainframe computer 803. The preferred embodiment of the desktop workstation is deployed on an IBM 330-P75 Personal Computer having a Windows 95 operating system available from Microsoft Corporation, 1-T Microsoft Way, Redmond, Wash., 98052, and an "IRMA for the Mainframe" 3.0.0 terminal emulator available from Digital Communications Associates, Inc., 1000 Alderman Drive, Alpharetta, Ga. 30202-4199.
The present invention has been described in an illustrative manner. In this regard, it is evident that those skilled in the art, once given the benefit of the foregoing disclosure, may now make modifications to the specific embodiments described herein without departing from the spirit of the present invention. Such modifications are to be considered within the scope of the present invention which is limited solely by the scope and spirit of the appended claims.

Claims (36)

We claim:
1. An apparatus for determining accrued use-taxes, comprising:
a computer;
transaction record acquisition logic in said computer for acquiring transaction information characterizing purchases of goods and services, and for generating transaction records;
use-tax accrual logic in said computer linked to said transaction records; said accrual logic having an enumerated liability account for holding a listed set of said records, and said logic further having an accrual liability account for holding a single valoue representing the cumulative impact of said listed set on said use-taxes; and
tax rate acquisition logic in said computer for acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions, and for generating a data schema linked to said use-tax accrual logic having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema.
2. The apparatus of claim 1 wherein said tax rate acquisition logic further comprises logic for acquiring excluded accounting group registries and said data schema further comprises fourth data elements descriptive of said excluded accounting group registries.
3. The apparatus of claim 2 wherein said first, second, third, and fourth data elements are arranged in tables of said data schema.
4. The apparatus of claim 1 further comprising data alignment logic in said computer which is used to determine if any of said first, second, and third data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
5. The apparatus of claim 2 further comprising data alignment logic in said computer which is used to determine if any of said first, second, third, and fourth data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
6. The apparatus of claim 1 further comprising transaction record extraction logic in said computer used to read said transaction records, parse and selectively extract data necessary for defining said accrued use-taxes, and write the extracted data into a transaction data file, wherein said use-tax accrual logic is linked to said transaction data file and to said enumerated liability account so that said listed set can be constructed from said transaction data file.
7. An apparatus for determining accrued use-taxes, said apparatus having a network linkage communicating to a periodically modified tax rate database, comprising:
a computer;
transaction record acquisition logic in said computer for acquiring transaction information characterizing purchases of goods and services, and for generating transaction records;
use-tax accrual logic in said computer linked to said transaction records, said accrual logic having an enumerated liability account for holding a listed set of said records, and said logic further having an accrual liability account for holding a single value representing the cumulative impact of said listed set on said use-taxes;
tax rate acquisition logic in said computer for acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions, and for generating a data schema linked to said use-tax accrual logic having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema; and
tax rate update logic in said computer linked to said data schema and to said tax rate database for periodically acquiring new tax information from said tax rate database to replace respective third data elements.
8. The apparatus of claim 7 wherein said tax rate acquisition logic further comprises logic for acquiring data elements excluded accounting group registries, and said data schema further comprises fourth data elements descriptive of said excluded accounting group registries.
9. The apparatus of claim 8 wherein said first, second, third, and fourth data elements are arranged in tables of said data schema.
10. The apparatus of claim 7 further comprising data alignment logic in said computer which is used to determine if any of said first, second, and third data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
11. The apparatus of claim 8 further comprising data alignment logic in said computer which is used to determine if any of said first, second, third, and fourth data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
12. The apparatus of claim 7 further comprising transaction record extraction logic used to read said transaction records, parse and selectively extract data necessary for defining said accrued use-taxes, and write the extracted data into a transaction data file, wherein said use-tax accrual logic is linked to said transaction data file and to said enumerated liability account so that said listed set can be constructed from said transaction data file.
13. An apparatus for determining accrued use-taxes, said apparatus having a linkage to a sales tax payment record which contains a list of paid sales taxes, comprising:
a computer;
transaction record acquisition logic in said computer for acquiring transaction information characterizing purchases of goods and services, and for generating transaction records;
use-tax accrual logic in said computer linked to said transaction records, said accrual logic having an enumerated liability account for holding a listed set of said records, and said logic further having an accrual liability account for holding a single value representing the cumulative impact of said listed set on said use-taxes;
tax rate acquisition logic in said computer for acquiring tax jurisidction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions, and for generating a data schema linked to said use-tax accrual logic having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema; and
sales tax crediting logic in said computer linked to said sales tax payment record and to said data schema such that said paid sales taxes can be debited to said accrued use-taxes.
14. The apparatus of claim 13 wherein said tax rate acquisition logic further comprises logic for acquiring data elements descriptive of excluded accounting group registries, and said data schema further comprises fourth data elements descriptive of said excluded accounting group registries.
15. The apparatus of claim 14 wherein said first, second, third, and fourth data elements are arranged in tables of said data schema.
16. The apparatus of claim 13 further comprising data alignment logic in said computer which is used to determine if any of said first, second, and third data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
17. The apparatus of claim 14 further comprising data alignment logic in said computer which is used to determine if any said first, second, third, and fourth data elements are both included for use and also excluded from use in said use-tax accrual logic for a particular use-tax determination instance.
18. The apparatus of claim 13 further comprising transaction record extraction logic in said computer used to read said transaction records, parse and selectively extract data necessary for defining said accrued use-taxes, and write the extracted data into a transaction data file, wherein said use-tax accrual logic is linked to said transaction data file and to said enumerated liability account so that said listed set can be constructed from said transaction data file.
19. A method for determining accrued use-taxes from transaction records holding data elements which characterize purchases of goods and services, comprising the steps of:
providing a computer;
acquiring transaction information charactarizing purchases of goods and services;
generating transaction records in said computer from said transaction information;
accessing, in said computer, said transaction records to define a listed set of said records which characterize purchases of goods and services;
storing said listed set;
acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions;
generating in said computer a data schema having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema;
accessing in said computer said data schema to acquire said first, second, and third data elements;
using said listed set and using said first, second, and third data elements to determine said accrued use-taxes in said computer; and
deriving a single value representing the cumulative impact of said listed set on said use-taxes.
20. The method of claim 19 further comprising acquiring data elements descriptive of excluded accounting group registries, and generating in said data schema in said computer fourth data elements descriptive of said excluded accounting group registries.
21. The method of claim 20 wherein said first, second, third, and fourth data elements are arranged in said computer in tables of said provided data schema.
22. The method of claim 19 further comprising the step of determining if any of said first, second, and third data elements are both included for use and also excluded from use in a particular use-tax determination instance.
23. The method of claim 20 further comprising the step of determining if any of said first, second, third, and fourth data elements are both included for use and also excluded from use in a particular use-tax determination instance.
24. The method of claim 19 wherein said accessing further comprises the steps of parsing and selectively extracting data necessary for defining said accrued use-taxes from said transaction records, writing the extracted data into a transaction data file, and determining said listed set from said transaction data file.
25. A method for determining accrued use-taxes from transaction records holding data elements which characterize purchases of goods and services and from a periodically modified tax rate database, comprising the steps of:
providing a computer;
acquiring transaction information characterizing purchases of goods and services;
generating transaction records in said computer from said transaction information;
accessing, in said computer, said transaction records to define a listed set of said records which characterize purchases of goods and services;
storing said listed set;
acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions;
generating in said computer a data schema having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema;
accessing in said computer said data schema to acquire said first, second, and third data elements;
using said listed set and using said first, second, and third data elements to determine said accrued use-taxes in said computer;
driving a single value representing the cumulative impact of said listed set on said use-taxes; and
periodically acquiring new tax information from said tax rate database to replace respective third data elements.
26. The method of claim 25 further comprising acquiring into said computer data elements descriptive of excluded accounting group registries, and generating in said data schema in said computer fourth data elements descriptive of said excluded accounting group registries.
27. The method of claim 26 wherein said first, second, third, and fourth data elements are arranged in said computer in tables of said provided data schema.
28. The method of claim 25 further comprising the step of determining if any of said first, second, and third data elements are both included for use and also excluded from use in a particular use-tax determination instance.
29. The method of claim 26 further comprising the step of determining if any of said first, second, third, and fourth data elements are both included for use and also excluded from use in a particular use-tax determination instance.
30. The method of claim 25 wherein said accesing further comprises the steps of parsing and selectively extracting data necessary for defining said accrued use-taxes from said transaction records, writing the extracted data into a transaction data file, and determining said listed set from said transaction data file.
31. A method for determining accrued use-taxes from transaction records holding data elements which characterize purchases of goods and services and from a sales tax payment record which contains a list of paid sales taxes, comprising the steps of:
providing a computer;
acquiring transaction information characterizing purchases of goods and services;
generating transaction records in said computer from said transaction information;
accessing, in said computer, said transaction records to define a listed set of said records which characterize purchases of goods and services;
storing said listed set;
acquiring tax jurisdiction codes, at least one inclusive accounting group registry respective to taxes, and tax information respective to said tax jurisdiction codes for a plurality of state jurisdictions;
generating in said computer a data schema having first data elements descriptive of inclusive accounting group registries, second data elements descriptive of tax jurisdiction codes, and third data elements descriptive of tax data respective to said tax jurisdiction codes, said third data elements having a data type for holding a multiple set of taxable percentages for a cost object so that a plurality of use-tax values may be generated from said listed set with each value having its respective taxable percentage basis retained in said data schema;
accessing in said computer said data schema to acquire said first, second, and third data elements;
using said listed set and using said first, second, and third data elements to determine said accrued use-taxes in said computer;
deriving a single value representing the cumulative impact of said listed set on said use-taxes; and
debiting said paid sales taxes to said accrued use-taxes.
32. The method of claim 31 further comprising acquiring into said computer data elements descriptive of excluded accounting group registries, and generating in said data schema in said computer fourth data elements descriptive of said excluded accounting group registries.
33. The method of claim 32 wherein said first, second, third, and fourth data elements are arranged in said computer in tables of said provided data schema.
34. The method of claim 31 further comprising the step of determining if any of said first, second, and third data elements are both included for use and also excluded from use in a particular use-tax determination instance.
35. The method of claim 32 further comprising the step of determining if any of said first, second, third, and fourth data elements are both included for use and also excluded from use in a particular use-tax determination instance.
36. The method of claim 31 wherein said accessing further comprises the steps of parsing and selectively extracting data necessary for defining said accrued use-taxes from said transaction records, writing the extracted data into a transaction data file, and determining said listed set from said transaction data file.
US08/877,785 1997-06-17 1997-06-17 System for use-tax determination Abandoned USH1830H (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US08/877,785 USH1830H (en) 1997-06-17 1997-06-17 System for use-tax determination

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US08/877,785 USH1830H (en) 1997-06-17 1997-06-17 System for use-tax determination

Publications (1)

Publication Number Publication Date
USH1830H true USH1830H (en) 2000-01-04

Family

ID=25370714

Family Applications (1)

Application Number Title Priority Date Filing Date
US08/877,785 Abandoned USH1830H (en) 1997-06-17 1997-06-17 System for use-tax determination

Country Status (1)

Country Link
US (1) USH1830H (en)

Cited By (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001039142A2 (en) * 1999-11-29 2001-05-31 Dryden Matrix Technologies Llc Adaptive system for point of sale tax assessment
US20010032116A1 (en) * 2000-02-11 2001-10-18 Geoffrey Hyatt System and method for providing information on market pricing
WO2001097150A1 (en) * 2000-06-14 2001-12-20 Dryden Matrix Technologies, Llc Sales tax assessment, remittance and collection system
US20020057088A1 (en) * 1998-10-05 2002-05-16 Alessandro Carrozzi Machine for diagnostic and/or therapeutic treatment, particularly a nuclear magnetic resonance imaging machine
US20020116302A1 (en) * 2001-02-15 2002-08-22 Robert Wilmes Transaction tax settlement in personal communication devices
US20020133436A1 (en) * 2001-03-13 2002-09-19 Hermreck Scott A. System and method for tracking charitable deductions
US20020194123A1 (en) * 2001-06-07 2002-12-19 Richard Agee Rapid tax collection system and method
US20020198832A1 (en) * 2001-06-07 2002-12-26 Richard Agee System for and method of rapid collection of income taxes
US20030040992A1 (en) * 2001-08-23 2003-02-27 Pitney Bowes Incorporated Secure tax meter and certified service provider center for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US20030097303A1 (en) * 2001-06-07 2003-05-22 Richard Agee Rapid tax collection system and method-cash and cash-substitute transactions
US20030101112A1 (en) * 2001-11-26 2003-05-29 Gallagher Robert J. Intelligent apparatus, system and method for financial data computation and analysis
WO2003044700A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company Computer-based transaction tax processing system, service module, method and computer program product for providing transaction tax services
WO2003044702A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company Method, software module and software application for automatically preparing a transaction-tax declaration
WO2003044701A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company, A Delaware Corporation Methods, software modules and software application for logging transaction-tax-related transactions
US20030105687A1 (en) * 2001-11-26 2003-06-05 Wolfgang Bross Methods, data record, software interface, data warehouse module and software application for exchanging transaction- tax-related data
US20030144931A1 (en) * 2002-01-16 2003-07-31 Stokes Patricia L. Tax calculator
US20030144930A1 (en) * 2002-01-31 2003-07-31 Kulkarni Ravindra Raghunath Rao Methods and systems for managing tax audit information
US20030233297A1 (en) * 1999-08-31 2003-12-18 Accenture Properties (2) B.V. System, method and article of manufacture for organizing and managing transaction-related tax information
US20040030619A1 (en) * 2002-01-16 2004-02-12 Stokes Patricia L. System and method for calculating transaction-based taxes
US20040088233A1 (en) * 2002-10-31 2004-05-06 Brady Kevin P. Information processing system for determining tax information
US20040167835A1 (en) * 2003-02-24 2004-08-26 Jyh-Ching Yaur Record keeping system supporting tax determination
US6804689B1 (en) * 1999-04-14 2004-10-12 Iomega Corporation Method and apparatus for automatically synchronizing data to destination media
US20040230525A1 (en) * 2002-12-30 2004-11-18 Jonathan Barsade e-Commerce sales & use tax exchange system and method
US20040230490A1 (en) * 2002-12-30 2004-11-18 Jonathan Barsade Integrated e-commerce sales & use tax exchange system and method
US20040254896A1 (en) * 2002-12-30 2004-12-16 Jonathan Barsade Integrated e-commerce sales & use tax exchange system and method
US6889200B2 (en) 2001-06-07 2005-05-03 Fairshare, Llc Rapid tax collection system and method for debit-type transactions
US20050131805A1 (en) * 2001-11-19 2005-06-16 Wolfgang Bross Software interface, method and computer program product product for linking a business application to a component of a computer-based transaction tax processing system
US20050216351A1 (en) * 2004-02-17 2005-09-29 Kenneth Holbert Methods and systems for recovery of sales and use taxes on cross-state direct sales, mail order, and electronic commerce
US6993502B1 (en) 1999-11-11 2006-01-31 Cch Incorporated Transaction tax collection system and method
US20060085275A1 (en) * 2002-01-16 2006-04-20 Stokes Patricia L System and method for facilitating online transactions
US20060271913A1 (en) * 2005-05-31 2006-11-30 Erf Franklin K Method and system for providing a field configurable guide
WO2007062047A2 (en) * 2005-11-21 2007-05-31 The Crawford Group, Inc. Method and system for managing vehicle leases
US20070156500A1 (en) * 2005-12-30 2007-07-05 Wilfried Merkel Architectural design for sell from stock application software
US20070156475A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for plan-driven procurement application software
US20070156430A1 (en) * 2005-12-30 2007-07-05 Stefan Kaetker Software model deployment units
US20070156499A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for self-service procurement application software
US20070156489A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for service procurement application software
US20070156550A1 (en) * 2005-12-30 2007-07-05 Der Emde Martin V Architectural design for cash and liquidity management application software
US20070162893A1 (en) * 2005-12-30 2007-07-12 Gerd Moosmann Software model process component
US20070168240A1 (en) * 2005-12-30 2007-07-19 Shai Alfandary Architectural design for make to stock application software
US20070168303A1 (en) * 2005-12-30 2007-07-19 Gerd Moosmann Software model process interaction
US7249072B1 (en) 2000-03-17 2007-07-24 Eproperty Tax, Inc. Method and system for managing multi-jurisdictional property tax information
US20070234282A1 (en) * 2006-03-31 2007-10-04 Uta Prigge Composite application modeling
US20070233598A1 (en) * 2006-03-30 2007-10-04 Martin Von Der Emde Providing payment software application as enterprise services
US20070233728A1 (en) * 2006-03-30 2007-10-04 Joachim Puteick Foundation layer for services based enterprise software architecture
US20070233574A1 (en) * 2006-03-30 2007-10-04 Alexander Koegler Providing customer relationship management application as enterprise services
US20070233581A1 (en) * 2006-03-30 2007-10-04 Markus Peter Providing product catalog software application as enterprise services
US20070233541A1 (en) * 2006-03-30 2007-10-04 Martin Schorr Providing accounting software application as enterprise services
US20070265862A1 (en) * 2006-04-13 2007-11-15 Jens Freund Software model business process variant types
US20070265860A1 (en) * 2006-03-30 2007-11-15 Karina Herrmann Providing supplier relationship management software application as enterprise services
US7305353B1 (en) * 2001-03-01 2007-12-04 Charles Schwab Co., Inc. System and method for forecasting tax effects of financial transactions
US20070282761A1 (en) * 2006-06-01 2007-12-06 Liquid Engines, Inc. System and method to calculate tax liability of a foreign entity
US20080010178A1 (en) * 2006-07-06 2008-01-10 Centrale Taxes Inc./Central Tax Inc. Centralized property tax management system
US7319982B1 (en) * 2000-08-08 2008-01-15 Pitney Bowes Inc. Method for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US20080147528A1 (en) * 2006-12-19 2008-06-19 Talan Jonathan M Method and apparatus for automatically mapping account-data to tax-forms
US20080288358A1 (en) * 2004-11-02 2008-11-20 Josh Hall Funds collection tools and techniques
US20090132399A1 (en) * 2006-02-02 2009-05-21 Pavlou Tax Solutions, Llc System and method for preparing multi-level tax returns
US20090171819A1 (en) * 2007-12-31 2009-07-02 Sap Ag Providing payment software application as enterprise services
US20090171713A1 (en) * 2007-12-31 2009-07-02 Armin Schwarz Architectural Design for Self-Service Procurement Application Software
US20090172699A1 (en) * 2007-12-31 2009-07-02 Christoph Jungkind Architectural Design for Service Procurement Application Software
US20090171712A1 (en) * 2007-12-31 2009-07-02 Matthias Heinrichs Architectural Design for Ad-Hoc Goods Movement Software
US20090171758A1 (en) * 2007-12-31 2009-07-02 Shai Alfandary Architectural design for physical inventory application software
US20090171698A1 (en) * 2007-12-31 2009-07-02 Sap Ag Providing human capital management software application as enterprise services
US20100070324A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Plan-Driven Procurement Application Software
US20100070317A1 (en) * 2008-09-18 2010-03-18 Nir Pachter Architectural design for sell from stock application software
US20100070555A1 (en) * 2008-09-18 2010-03-18 Jacques Duparc Architectural design for time recording application software
US20100070289A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Embedded Support Application Software
US20100070391A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Tax Declaration Application Software
US20100070331A1 (en) * 2008-09-18 2010-03-18 Alexander Koegler Architectural design for service request and order management application software
US20100070330A1 (en) * 2008-09-18 2010-03-18 Peer Marschall Architectural design for customer returns handling application software
US20100070395A1 (en) * 2008-09-18 2010-03-18 Andreas Elkeles Architectural design for payroll processing application software
US20100070318A1 (en) * 2008-09-18 2010-03-18 Achim Clemens Providing logistics execution application as enterprise services
US7685063B2 (en) 2005-03-25 2010-03-23 The Crawford Group, Inc. Client-server architecture for managing customer vehicle leasing
US20100082497A1 (en) * 2008-09-18 2010-04-01 Sap Ag Providing Foundation Application as Enterprise Services
US20100138255A1 (en) * 2008-12-03 2010-06-03 Sap Ag Architectural design for manual invoicing application software
US20100138276A1 (en) * 2008-12-03 2010-06-03 Sap Ag Architectural design for make-to-specification application software
US20100153240A1 (en) * 2008-12-11 2010-06-17 Andreas Bold Providing Payroll Software Application as Enterprise Services
US20100153239A1 (en) * 2008-12-11 2010-06-17 Sap Ag Providing accounting software application as enterprise services
US7761333B2 (en) 2001-08-21 2010-07-20 Kapp Martin A Income tax preparation system for traveling taxpayers
US20100191606A1 (en) * 2009-01-23 2010-07-29 Microsoft Corporation Tax calculation extensibility techniques
US7769647B1 (en) * 2008-07-31 2010-08-03 Intuit Inc. Method and system for providing a year-round tax monitor
US7987209B2 (en) 2002-12-27 2011-07-26 Honda Motor Co., Ltd. Enhanced trade compliance system: mass amendment
US8077974B2 (en) 2006-07-28 2011-12-13 Hewlett-Packard Development Company, L.P. Compact stylus-based input technique for indic scripts
US8249936B1 (en) * 1995-05-10 2012-08-21 Taxnet Systems, Llc Point of tax reporting and automatic collection system with tax register
US8311904B2 (en) 2008-12-03 2012-11-13 Sap Ag Architectural design for intra-company stock transfer application software
US8321306B2 (en) 2008-12-03 2012-11-27 Sap Ag Architectural design for selling project-based services application software
US8321831B2 (en) 2005-12-30 2012-11-27 Sap Ag Architectural design for internal projects application software
US8326703B2 (en) 2005-12-30 2012-12-04 Sap Ag Architectural design for product catalog management application software
US8374896B2 (en) 2008-09-18 2013-02-12 Sap Ag Architectural design for opportunity management application software
US8401928B2 (en) 2008-09-18 2013-03-19 Sap Ag Providing supplier relationship management software application as enterprise services
US8401936B2 (en) 2007-12-31 2013-03-19 Sap Ag Architectural design for expense reimbursement application software
US8407664B2 (en) 2005-12-30 2013-03-26 Sap Ag Software model business objects
US8448137B2 (en) 2005-12-30 2013-05-21 Sap Ag Software model integration scenarios
US8522194B2 (en) 2005-12-30 2013-08-27 Sap Ag Software modeling
US8615452B2 (en) 2004-05-28 2013-12-24 Hewlett-Packard Development Company, L.P. Data representation of transaction-tax-related information
US8660904B2 (en) 2005-12-30 2014-02-25 Sap Ag Architectural design for service request and order management application software
US8671033B2 (en) 2007-12-31 2014-03-11 Sap Ag Architectural design for personnel events application software
US8700504B2 (en) 2002-12-30 2014-04-15 Exactor, Inc. Integrated e-commerce sales and use tax exchange system and method
US8738476B2 (en) 2008-12-03 2014-05-27 Sap Ag Architectural design for selling standardized services application software
US9418385B1 (en) * 2011-01-24 2016-08-16 Intuit Inc. Assembling a tax-information data structure

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4623964A (en) * 1981-12-23 1986-11-18 International Business Machines Corporation Homogeneous hierarchial computer business system
US5136502A (en) * 1991-10-02 1992-08-04 Fred Van Remortel System for funding, analyzing and managing health care liabilities
US5335169A (en) * 1992-01-27 1994-08-02 Dsi Of Hawaii, Inc. System for tracking multiple rate assessments on transactions
US5644724A (en) * 1994-09-28 1997-07-01 Cretzler; Donald J. Point-of-sale tax collection system and method of using same
US5799283A (en) * 1995-05-10 1998-08-25 Francisco; Paul A. Point of sale governmental sales and use tax reporting and receipt system
US5819249A (en) * 1995-11-29 1998-10-06 International Business Machines Corporation Tax coding expert system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4623964A (en) * 1981-12-23 1986-11-18 International Business Machines Corporation Homogeneous hierarchial computer business system
US5136502A (en) * 1991-10-02 1992-08-04 Fred Van Remortel System for funding, analyzing and managing health care liabilities
US5335169A (en) * 1992-01-27 1994-08-02 Dsi Of Hawaii, Inc. System for tracking multiple rate assessments on transactions
US5644724A (en) * 1994-09-28 1997-07-01 Cretzler; Donald J. Point-of-sale tax collection system and method of using same
US5799283A (en) * 1995-05-10 1998-08-25 Francisco; Paul A. Point of sale governmental sales and use tax reporting and receipt system
US5819249A (en) * 1995-11-29 1998-10-06 International Business Machines Corporation Tax coding expert system

Non-Patent Citations (19)

* Cited by examiner, † Cited by third party
Title
Dialog File 148 (IAC Trade & Industry Database), No. 08499275, "Taxware Partners with Open Market to Provide Secure Tax Systems for Electronic Commerce", PR Newswire, 2 pages, Mar. 4, 1996.
Dialog File 148 (IAC Trade & Industry Database), No. 08499275, Taxware Partners with Open Market to Provide Secure Tax Systems for Electronic Commerce , PR Newswire, 2 pages, Mar. 4, 1996. *
Edwin Brooks Niemeyer, "Taking Advantage of the Taxman," New England Business, vol. 12, No. 10, Oct. 1990, pp. 96-97.
Edwin Brooks Niemeyer, Taking Advantage of the Taxman, New England Business , vol. 12, No. 10, Oct. 1990, pp. 96 97. *
Mark A. Luscombe, "Taxation of knowledge," Taxes, vol. 74, No. 3, Mar. 1996, pp. 183-185.
Mark A. Luscombe, Taxation of knowledge, Taxes , vol. 74, No. 3, Mar. 1996, pp. 183 185. *
Michael T. Smith, et al., "Two temporary solutions: Purchasing cards trip over tax reporting," Corporate Cashflow, vol. 16, No. 9, Sep. 1995, pp. 21-22.
Michael T. Smith, et al., Two temporary solutions: Purchasing cards trip over tax reporting, Corporate Cashflow , vol. 16, No. 9, Sep. 1995, pp. 21 22. *
Nathan J. Muller, "Multicurrency accounting software arrives!" Accounting Technology, vol. 9, No. 10, Dec. 1993, pp. 47-50, 52,54.
Nathan J. Muller, Multicurrency accounting software arrives Accounting Technology , vol. 9, No. 10, Dec. 1993, pp. 47 50, 52,54. *
Robert W. Scott, "Business tax vendors race to broaden user options," Accounting Today, vol. 9, No. 21, Nov. 20-Dec. 10, 1995, pp. 26, 30-33.
Robert W. Scott, "Windows 95 colors 1996 tax software season," Accounting Today, vol. 9 No. 19, Oct. 23-Nov. 5, 1995, pp. 26, 31, 44-47.
Robert W. Scott, Business tax vendors race to broaden user options, Accounting Today , vol. 9, No. 21, Nov. 20 Dec. 10, 1995, pp. 26, 30 33. *
Robert W. Scott, Windows 95 colors 1996 tax software season, Accounting Today , vol. 9 No. 19, Oct. 23 Nov. 5, 1995, pp. 26, 31, 44 47. *
Sam W. Stearman, "Spotlight on tax software," Journal of Accountancy, vol. 178, No. 4, Oct. 1994, pp. 49-74.
Sam W. Stearman, Spotlight on tax software, Journal of Accountancy , vol. 178, No. 4, Oct. 1994, pp. 49 74. *
Stuart Kahan, "A practical guide to fixed assets software," The Practical Accountant, vol. 29, No. 2, Feb. 1996, pp. 40-46.
Stuart Kahan, A practical guide to fixed assets software, The Practical Accountant , vol. 29, No. 2, Feb. 1996, pp. 40 46. *
Taxware Partners with Open Market to Provide Secure Tax Systems for Electronic Commerce (PR Newswire, Dialog File 148 (IAC Trade & Industry Database), Document No. 08499275), Mar. 4, 1996. *

Cited By (165)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8249936B1 (en) * 1995-05-10 2012-08-21 Taxnet Systems, Llc Point of tax reporting and automatic collection system with tax register
US8788351B2 (en) 1995-05-10 2014-07-22 Taxvantage Llc Point of sale tax reporting and automatic collection system with tax register
US20020057088A1 (en) * 1998-10-05 2002-05-16 Alessandro Carrozzi Machine for diagnostic and/or therapeutic treatment, particularly a nuclear magnetic resonance imaging machine
US6804689B1 (en) * 1999-04-14 2004-10-12 Iomega Corporation Method and apparatus for automatically synchronizing data to destination media
US7043448B2 (en) * 1999-08-31 2006-05-09 Accenture Llp Organizing and managing transaction-related tax information
US20030233297A1 (en) * 1999-08-31 2003-12-18 Accenture Properties (2) B.V. System, method and article of manufacture for organizing and managing transaction-related tax information
US6993502B1 (en) 1999-11-11 2006-01-31 Cch Incorporated Transaction tax collection system and method
WO2001039142A2 (en) * 1999-11-29 2001-05-31 Dryden Matrix Technologies Llc Adaptive system for point of sale tax assessment
WO2001039142A3 (en) * 1999-11-29 2001-11-22 Dryden Matrix Technologies Llc Adaptive system for point of sale tax assessment
US20010032116A1 (en) * 2000-02-11 2001-10-18 Geoffrey Hyatt System and method for providing information on market pricing
US7249072B1 (en) 2000-03-17 2007-07-24 Eproperty Tax, Inc. Method and system for managing multi-jurisdictional property tax information
US7801780B1 (en) * 2000-03-17 2010-09-21 Thomson Reuters (Tax & Accounting) Services Inc. Method and system for managing multi-jurisdictional property tax information
US20020052792A1 (en) * 2000-06-14 2002-05-02 Johnson Kevin C. Sales tax assessment, remittance and collection system
WO2001097150A1 (en) * 2000-06-14 2001-12-20 Dryden Matrix Technologies, Llc Sales tax assessment, remittance and collection system
US7716093B2 (en) * 2000-06-14 2010-05-11 Tax Matrix Technologies, Llc Sales tax assessment, remittance and collection system
US7319982B1 (en) * 2000-08-08 2008-01-15 Pitney Bowes Inc. Method for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US7313538B2 (en) * 2001-02-15 2007-12-25 American Express Travel Related Services Company, Inc. Transaction tax settlement in personal communication devices
US20120246037A1 (en) * 2001-02-15 2012-09-27 American Express Travel Related Services Company, Inc. Transaction tax settlement in personal communication devices
US8214269B2 (en) 2001-02-15 2012-07-03 American Express Travel Related Services Company, Inc. Transactional tax settlement in personal communication devices
US20020116302A1 (en) * 2001-02-15 2002-08-22 Robert Wilmes Transaction tax settlement in personal communication devices
US7305353B1 (en) * 2001-03-01 2007-12-04 Charles Schwab Co., Inc. System and method for forecasting tax effects of financial transactions
US20080033860A1 (en) * 2001-03-01 2008-02-07 Charles Schwab & Co., Inc. System and method for forecasting tax effects of financial transactions
US9773276B2 (en) 2001-03-01 2017-09-26 Charles Schwab & Co., Inc. System and method for forecasting tax effects of financial transactions
US8429024B1 (en) 2001-03-13 2013-04-23 Intuit Inc. System and method for tracking charitable deductions
US20020133436A1 (en) * 2001-03-13 2002-09-19 Hermreck Scott A. System and method for tracking charitable deductions
US8200553B1 (en) 2001-03-13 2012-06-12 Intuit Inc. System and method for tracking charitable deductions
US7395230B2 (en) 2001-03-13 2008-07-01 Intuit Inc. System and method for tracking charitable deductions
US7188083B2 (en) 2001-06-07 2007-03-06 Fairshare, Llc System for and method of rapid collection of income taxes
US20020194123A1 (en) * 2001-06-07 2002-12-19 Richard Agee Rapid tax collection system and method
US20030097303A1 (en) * 2001-06-07 2003-05-22 Richard Agee Rapid tax collection system and method-cash and cash-substitute transactions
US20020198832A1 (en) * 2001-06-07 2002-12-26 Richard Agee System for and method of rapid collection of income taxes
US6889200B2 (en) 2001-06-07 2005-05-03 Fairshare, Llc Rapid tax collection system and method for debit-type transactions
US8433627B2 (en) * 2001-06-07 2013-04-30 Fairshare, Llc Rapid tax collection system and method
US7761333B2 (en) 2001-08-21 2010-07-20 Kapp Martin A Income tax preparation system for traveling taxpayers
US20030040992A1 (en) * 2001-08-23 2003-02-27 Pitney Bowes Incorporated Secure tax meter and certified service provider center for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US7398247B2 (en) 2001-08-23 2008-07-08 Pitney Bowes Inc. Secure tax meter and certified service provider center for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US20050131805A1 (en) * 2001-11-19 2005-06-16 Wolfgang Bross Software interface, method and computer program product product for linking a business application to a component of a computer-based transaction tax processing system
US20050065852A1 (en) * 2001-11-19 2005-03-24 Wolfgang Bross Methods, software modules and software application for logging transaction-tax-related transactions
WO2003044700A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company Computer-based transaction tax processing system, service module, method and computer program product for providing transaction tax services
US8620777B2 (en) * 2001-11-19 2013-12-31 Hewlett-Packard Development Company, L.P. Methods, software modules and software application for logging transaction-tax-related transactions
WO2003044702A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company Method, software module and software application for automatically preparing a transaction-tax declaration
WO2003044701A1 (en) * 2001-11-19 2003-05-30 Hewlett-Packard Company, A Delaware Corporation Methods, software modules and software application for logging transaction-tax-related transactions
US20030101112A1 (en) * 2001-11-26 2003-05-29 Gallagher Robert J. Intelligent apparatus, system and method for financial data computation and analysis
US20030105687A1 (en) * 2001-11-26 2003-06-05 Wolfgang Bross Methods, data record, software interface, data warehouse module and software application for exchanging transaction- tax-related data
US20060085275A1 (en) * 2002-01-16 2006-04-20 Stokes Patricia L System and method for facilitating online transactions
US20040030619A1 (en) * 2002-01-16 2004-02-12 Stokes Patricia L. System and method for calculating transaction-based taxes
US20030144931A1 (en) * 2002-01-16 2003-07-31 Stokes Patricia L. Tax calculator
US20030144930A1 (en) * 2002-01-31 2003-07-31 Kulkarni Ravindra Raghunath Rao Methods and systems for managing tax audit information
WO2003065274A1 (en) * 2002-01-31 2003-08-07 General Electronic Company Methods and systems for managing tax audit information
US7295998B2 (en) 2002-01-31 2007-11-13 General Electric Company Methods and systems for managing tax audit information
WO2004027543A2 (en) * 2002-09-23 2004-04-01 Cogito, Llc System and method for calculating transaction-based taxes
WO2004027543A3 (en) * 2002-09-23 2004-06-17 Cogito Llc System and method for calculating transaction-based taxes
US20100076876A1 (en) * 2002-10-31 2010-03-25 Brady Kevin P Information processing method for managing and determining tax provision information
US7627504B2 (en) * 2002-10-31 2009-12-01 Thomson Reuters (Tax and Accounting) Services, Inc. Information processing system for determining tax information
US8626619B2 (en) * 2002-10-31 2014-01-07 Thomson Reuters (Tax & Accounting) Services Inc. Information processing system and method for managing and determining tax information
US20040088233A1 (en) * 2002-10-31 2004-05-06 Brady Kevin P. Information processing system for determining tax information
US20110288972A1 (en) * 2002-10-31 2011-11-24 Brady Kevin P Information Processing System and Method for Managing and Determining Tax Information
US7991660B2 (en) * 2002-10-31 2011-08-02 Thomson Reuters (Tax & Accounting) Services Inc. Information processing method for managing and determining tax provision information
US7987209B2 (en) 2002-12-27 2011-07-26 Honda Motor Co., Ltd. Enhanced trade compliance system: mass amendment
US20040230525A1 (en) * 2002-12-30 2004-11-18 Jonathan Barsade e-Commerce sales & use tax exchange system and method
US20040230490A1 (en) * 2002-12-30 2004-11-18 Jonathan Barsade Integrated e-commerce sales & use tax exchange system and method
US20040254896A1 (en) * 2002-12-30 2004-12-16 Jonathan Barsade Integrated e-commerce sales & use tax exchange system and method
US7562033B2 (en) 2002-12-30 2009-07-14 Exactor, Inc. Integrated e-commerce sales & use tax exchange system and method
US8700504B2 (en) 2002-12-30 2014-04-15 Exactor, Inc. Integrated e-commerce sales and use tax exchange system and method
US8793168B2 (en) 2002-12-30 2014-07-29 Exactor, Inc. E-commerce sales and use exchange system and method
US7398239B2 (en) 2002-12-30 2008-07-08 Jonathan Barsade E-commerce sales and use tax exchange system and method
US20040167835A1 (en) * 2003-02-24 2004-08-26 Jyh-Ching Yaur Record keeping system supporting tax determination
US20050216351A1 (en) * 2004-02-17 2005-09-29 Kenneth Holbert Methods and systems for recovery of sales and use taxes on cross-state direct sales, mail order, and electronic commerce
US8615452B2 (en) 2004-05-28 2013-12-24 Hewlett-Packard Development Company, L.P. Data representation of transaction-tax-related information
US20080288358A1 (en) * 2004-11-02 2008-11-20 Josh Hall Funds collection tools and techniques
US7685063B2 (en) 2005-03-25 2010-03-23 The Crawford Group, Inc. Client-server architecture for managing customer vehicle leasing
US20060271913A1 (en) * 2005-05-31 2006-11-30 Erf Franklin K Method and system for providing a field configurable guide
WO2007062047A3 (en) * 2005-11-21 2009-05-14 Crawford Group Inc Method and system for managing vehicle leases
WO2007062047A2 (en) * 2005-11-21 2007-05-31 The Crawford Group, Inc. Method and system for managing vehicle leases
US8326703B2 (en) 2005-12-30 2012-12-04 Sap Ag Architectural design for product catalog management application software
US8380553B2 (en) 2005-12-30 2013-02-19 Sap Ag Architectural design for plan-driven procurement application software
US20070156500A1 (en) * 2005-12-30 2007-07-05 Wilfried Merkel Architectural design for sell from stock application software
US8321831B2 (en) 2005-12-30 2012-11-27 Sap Ag Architectural design for internal projects application software
US20070156475A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for plan-driven procurement application software
US20070156430A1 (en) * 2005-12-30 2007-07-05 Stefan Kaetker Software model deployment units
US20070156499A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for self-service procurement application software
US8676617B2 (en) 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8660904B2 (en) 2005-12-30 2014-02-25 Sap Ag Architectural design for service request and order management application software
US20070156489A1 (en) * 2005-12-30 2007-07-05 Arthur Berger Architectural design for service procurement application software
US20070156550A1 (en) * 2005-12-30 2007-07-05 Der Emde Martin V Architectural design for cash and liquidity management application software
US20070162893A1 (en) * 2005-12-30 2007-07-12 Gerd Moosmann Software model process component
US8327319B2 (en) 2005-12-30 2012-12-04 Sap Ag Software model process interaction
US8522194B2 (en) 2005-12-30 2013-08-27 Sap Ag Software modeling
US8448137B2 (en) 2005-12-30 2013-05-21 Sap Ag Software model integration scenarios
US8370794B2 (en) 2005-12-30 2013-02-05 Sap Ag Software model process component
US8316344B2 (en) 2005-12-30 2012-11-20 Sap Ag Software model deployment units
US8396731B2 (en) 2005-12-30 2013-03-12 Sap Ag Architectural design for service procurement application software
US20070168240A1 (en) * 2005-12-30 2007-07-19 Shai Alfandary Architectural design for make to stock application software
US20070168303A1 (en) * 2005-12-30 2007-07-19 Gerd Moosmann Software model process interaction
US8407664B2 (en) 2005-12-30 2013-03-26 Sap Ag Software model business objects
US8402426B2 (en) 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US20090132399A1 (en) * 2006-02-02 2009-05-21 Pavlou Tax Solutions, Llc System and method for preparing multi-level tax returns
US9760915B2 (en) 2006-02-02 2017-09-12 Ptp Oneclick, Llc System and method for preparing multi-level tax returns
US8438119B2 (en) 2006-03-30 2013-05-07 Sap Ag Foundation layer for services based enterprise software architecture
US8396761B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing product catalog software application as enterprise services
US8442850B2 (en) 2006-03-30 2013-05-14 Sap Ag Providing accounting software application as enterprise services
US8538864B2 (en) 2006-03-30 2013-09-17 Sap Ag Providing payment software application as enterprise services
US20070265860A1 (en) * 2006-03-30 2007-11-15 Karina Herrmann Providing supplier relationship management software application as enterprise services
US8326702B2 (en) 2006-03-30 2012-12-04 Sap Ag Providing supplier relationship management software application as enterprise services
US20070233541A1 (en) * 2006-03-30 2007-10-04 Martin Schorr Providing accounting software application as enterprise services
US8396749B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing customer relationship management application as enterprise services
US20070233581A1 (en) * 2006-03-30 2007-10-04 Markus Peter Providing product catalog software application as enterprise services
US20070233574A1 (en) * 2006-03-30 2007-10-04 Alexander Koegler Providing customer relationship management application as enterprise services
US20070233728A1 (en) * 2006-03-30 2007-10-04 Joachim Puteick Foundation layer for services based enterprise software architecture
US20070233598A1 (en) * 2006-03-30 2007-10-04 Martin Von Der Emde Providing payment software application as enterprise services
US8321832B2 (en) 2006-03-31 2012-11-27 Sap Ag Composite application modeling
US20070234282A1 (en) * 2006-03-31 2007-10-04 Uta Prigge Composite application modeling
US20070265862A1 (en) * 2006-04-13 2007-11-15 Jens Freund Software model business process variant types
US8312416B2 (en) 2006-04-13 2012-11-13 Sap Ag Software model business process variant types
US20070282761A1 (en) * 2006-06-01 2007-12-06 Liquid Engines, Inc. System and method to calculate tax liability of a foreign entity
US20080010178A1 (en) * 2006-07-06 2008-01-10 Centrale Taxes Inc./Central Tax Inc. Centralized property tax management system
US8077974B2 (en) 2006-07-28 2011-12-13 Hewlett-Packard Development Company, L.P. Compact stylus-based input technique for indic scripts
US20080147528A1 (en) * 2006-12-19 2008-06-19 Talan Jonathan M Method and apparatus for automatically mapping account-data to tax-forms
US7685033B2 (en) * 2006-12-19 2010-03-23 Intuit Inc. Method and apparatus for automatically mapping account-data to tax-forms
US8671032B2 (en) * 2007-12-31 2014-03-11 Sap Ag Providing payment software application as enterprise services
US20090171713A1 (en) * 2007-12-31 2009-07-02 Armin Schwarz Architectural Design for Self-Service Procurement Application Software
US8401936B2 (en) 2007-12-31 2013-03-19 Sap Ag Architectural design for expense reimbursement application software
US20090171712A1 (en) * 2007-12-31 2009-07-02 Matthias Heinrichs Architectural Design for Ad-Hoc Goods Movement Software
US20090172699A1 (en) * 2007-12-31 2009-07-02 Christoph Jungkind Architectural Design for Service Procurement Application Software
US8671033B2 (en) 2007-12-31 2014-03-11 Sap Ag Architectural design for personnel events application software
US8671034B2 (en) 2007-12-31 2014-03-11 Sap Ag Providing human capital management software application as enterprise services
US8510143B2 (en) 2007-12-31 2013-08-13 Sap Ag Architectural design for ad-hoc goods movement software
US8447657B2 (en) 2007-12-31 2013-05-21 Sap Ag Architectural design for service procurement application software
US20090171819A1 (en) * 2007-12-31 2009-07-02 Sap Ag Providing payment software application as enterprise services
US20090171698A1 (en) * 2007-12-31 2009-07-02 Sap Ag Providing human capital management software application as enterprise services
US8315900B2 (en) 2007-12-31 2012-11-20 Sap Ag Architectural design for self-service procurement application software
US20090171758A1 (en) * 2007-12-31 2009-07-02 Shai Alfandary Architectural design for physical inventory application software
US7769647B1 (en) * 2008-07-31 2010-08-03 Intuit Inc. Method and system for providing a year-round tax monitor
US20100070391A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Tax Declaration Application Software
US20100070317A1 (en) * 2008-09-18 2010-03-18 Nir Pachter Architectural design for sell from stock application software
US8315926B2 (en) 2008-09-18 2012-11-20 Sap Ag Architectural design for tax declaration application software
US8818884B2 (en) 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US8321250B2 (en) 2008-09-18 2012-11-27 Sap Ag Architectural design for sell from stock application software
US20100070324A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Plan-Driven Procurement Application Software
US20100082497A1 (en) * 2008-09-18 2010-04-01 Sap Ag Providing Foundation Application as Enterprise Services
US8386325B2 (en) 2008-09-18 2013-02-26 Sap Ag Architectural design for plan-driven procurement application software
US8595077B2 (en) 2008-09-18 2013-11-26 Sap Ag Architectural design for service request and order management application software
US8352338B2 (en) 2008-09-18 2013-01-08 Sap Ag Architectural design for time recording application software
US20100070318A1 (en) * 2008-09-18 2010-03-18 Achim Clemens Providing logistics execution application as enterprise services
US8374896B2 (en) 2008-09-18 2013-02-12 Sap Ag Architectural design for opportunity management application software
US20100070395A1 (en) * 2008-09-18 2010-03-18 Andreas Elkeles Architectural design for payroll processing application software
US20100070330A1 (en) * 2008-09-18 2010-03-18 Peer Marschall Architectural design for customer returns handling application software
US8401928B2 (en) 2008-09-18 2013-03-19 Sap Ag Providing supplier relationship management software application as enterprise services
US20100070289A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Embedded Support Application Software
US8380549B2 (en) 2008-09-18 2013-02-19 Sap Ag Architectural design for embedded support application software
US20100070331A1 (en) * 2008-09-18 2010-03-18 Alexander Koegler Architectural design for service request and order management application software
US20100070555A1 (en) * 2008-09-18 2010-03-18 Jacques Duparc Architectural design for time recording application software
US8326706B2 (en) 2008-09-18 2012-12-04 Sap Ag Providing logistics execution application as enterprise services
US20100138276A1 (en) * 2008-12-03 2010-06-03 Sap Ag Architectural design for make-to-specification application software
US8311904B2 (en) 2008-12-03 2012-11-13 Sap Ag Architectural design for intra-company stock transfer application software
US8738476B2 (en) 2008-12-03 2014-05-27 Sap Ag Architectural design for selling standardized services application software
US20100138255A1 (en) * 2008-12-03 2010-06-03 Sap Ag Architectural design for manual invoicing application software
US8321306B2 (en) 2008-12-03 2012-11-27 Sap Ag Architectural design for selling project-based services application software
US8321308B2 (en) 2008-12-03 2012-11-27 Sap Ag Architectural design for manual invoicing application software
US8401908B2 (en) 2008-12-03 2013-03-19 Sap Ag Architectural design for make-to-specification application software
US8671035B2 (en) 2008-12-11 2014-03-11 Sap Ag Providing payroll software application as enterprise services
US20100153239A1 (en) * 2008-12-11 2010-06-17 Sap Ag Providing accounting software application as enterprise services
US20100153240A1 (en) * 2008-12-11 2010-06-17 Andreas Bold Providing Payroll Software Application as Enterprise Services
US20100191606A1 (en) * 2009-01-23 2010-07-29 Microsoft Corporation Tax calculation extensibility techniques
US9418385B1 (en) * 2011-01-24 2016-08-16 Intuit Inc. Assembling a tax-information data structure

Similar Documents

Publication Publication Date Title
USH1830H (en) System for use-tax determination
US7552089B2 (en) Method and apparatus for automatically applying/linking transactions in a financial management system
US7685190B2 (en) Method and system for an online-like account processing and management
US6442533B1 (en) Multi-processing financial transaction processing system
US7840562B2 (en) System and method of reconciling human resource database
US20030126048A1 (en) Asset-based lease transaction management and accounting system
US6993505B1 (en) Method and system for performing CRA, HMDA, and fair lending analysis and reporting for a financial institution
Bae et al. Implementation of ERP systems: accounting and auditing implications
US7539634B2 (en) Account reconciliation system and method
US20050240601A1 (en) System and method for transactional data collection and processing
US20060149643A1 (en) Automatic business date determination systems and methods
JP2003030397A (en) Enterprise information managing device and program
US11704743B2 (en) Method and system for processing transactions based on transaction archetypes
CN115456747B (en) Automatic intelligent account settling method and device for ERP system and storage medium
US20220405859A1 (en) Recommendation system for recording a transaction
US7433878B2 (en) Method and system for interfacing with accounting systems
JP6667791B1 (en) Accounting system and program
JPH11328292A (en) Installment erasure system
US20050055279A1 (en) Flexible tax calculation architecture
JPH11161396A (en) Paperless account system
US12236492B2 (en) Method and system for processing transactions based on transaction archetypes
US7634444B2 (en) Method and apparatus for applying/linking transactions in a financial management system
Westland et al. Simulated Transactions for Auditing Service Organizations
JP2831478B2 (en) Paperless accounting system
JP2000306012A (en) Accounting data processing system and accounting data processing method

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE