Methods, software modules and software application for logging transaction-tax-related transactions

• US 20050065852A1
• Filed: 11/26/2001
• Published: 03/24/2005
• Est. Priority Date: 11/19/2001
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Heumueller, Norbert, Bross, Wolfgang, Oesterle, Fritz
• Granted Patent: US 8,620,777 B2
• Time in Patent Office: Days
• US Class Current: 705/19
• CPC Class Codes: G06Q 20/207 Tax processing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

The invention is directed to a computer-based method for logging transaction-tax-related transactions, the method using rules which define, depending on transaction data, what transactions have to be logged, the method comprising: receiving a logging request for a transaction; evaluating the logging rules with transaction data of said transaction, logging said transaction if the result of the evaluation demands it. The invention is also directed to related software modules and a related software application.

Claims

1. A computer-based method for logging transaction-tax-related transactions, wherein the transactions to be logged may include a previously calculated transaction-tax amount of the transaction, the method using rules which define, depending on transaction data, what transactions have to be logged and what data items of a transaction have to be logged, the method comprising:

receiving a logging request for a transaction;

evaluating the logging rules with transaction data of said transaction,

selecting, in response to an outcome of the evaluation which demands that the transaction is logged, the data items of the transaction which have to be logged, according to the result of the evaluation;

logging, in response to an outcome of the evaluation which demands that the transaction is logged, the selected data items of the transaction;

wherein the rules and their evaluation enable the decision as to whether a transaction and which data items are logged to depend on at least one of the type of the transaction and a jurisdiction which is relevant for the transaction;

wherein the method is carried out by a software module which can be invoked independently of a software module for the previous calculation of the transaction-tax amount of the transaction.

2. The method of claim 1, wherein the transaction data available for the processing of the logging request does not contain a direct indication of whether the transaction has to be logged or which items of transaction data have to be logged, so that these decisions are only based on the evaluation of the logging rules with the data of the transaction.

3. The method of claim 1, wherein the logging rules are fetched from a content service module in which the rules can be configured by a user.

4. The method of claim 1, wherein incomplete transaction data are completed by an automatic compliance procedure, and the completed data are logged.

5. A software module for logging transaction-tax related transactions for use in a transaction-tax processing application, wherein the transactions to be logged may include a previously calculated transaction-tax amount of the transaction, the software module arranged to:

use rules which define, depending on transaction data, what transactions have to be logged and what data items of a transaction have to be logged;

receive a logging request for a transaction;

evaluate the logging rules with transaction data of said transaction,

select, in response to an outcome of the evaluation which demands that the transaction is logged, the data items of the transaction which have to be logged, according to the result of the evaluation;

log, in response to an outcome of the evaluation which demands that the transaction is logged, the selected data items of the transaction;

wherein the rules and their evaluation enable the decision as to whether a transaction and which data items are logged to depend on at least one of the type of the transaction and a jurisdiction which is relevant for the transaction;

wherein the software module can be invoked independently of a software module for the previous calculation of the transaction-tax amount of the transaction.

6. The software module of claim 5, wherein the transaction data available for the processing of the logging request does not contain a direct indication of whether the transaction has to be logged or which items of transaction data have to be logged, so that these decisions are only based on the evaluation of the logging rules with the data of the transaction.

7. The software module of claim 5, wherein the module is callable before a calculation of the transaction tax of the transaction in order to take a decision whether a transaction tax calculation is required for a particular transaction.

8. The software module of claim 5, wherein the module is arranged to fetch the logging rules from a content service module in which the rules can be configured by a user.

9. The software module of claim 5, further comprising an interface for receiving the logging request.

10. The software module of claim 9, wherein the interface uses a Web-protocol.

11. The software module of claim 9, wherein the software module interface is callable with an HTTP request.

12. The software module of claim 11, arranged such that transaction data are handed over to the software module together with the HTTP request in a tagged form.

13. The software module of claim 11, arranged such that transaction data are handed over to the software module together with the HTTP request as an XML document.

14. A software application for computer-based transition-tax processing, comprising a software module for logging transaction-tax related transactions according to logging rules which define, depending on transaction data, what transactions have to be logged and what data items of a transaction have to be logged;

the software application providing a logging rule configuration interface which enables the logging, rules to be input and configured by a user without a need to change hard-coded programs;

the logging module comprising a component for reading the rules input via the logging rule configuration interface;

the logging module arranged to;

receive a logging request for a transaction;

evaluate the logging rules with transaction data of said transaction,

select, in response to an outcome of the evaluation which demands that the transaction is logged, the data items of the transaction which have to be logged, according to the result of the evaluation;

log, in response to an outcome of the evaluation which demands that the transaction is logged, the selected data items of the transaction;

wherein the rules and their evaluation enable the decision as to whether a transaction and which data items are logged to depend on at least one of the type of the transaction and a jurisdiction which is relevant for the transaction;

wherein the software module can be invoked independently of a software module for the previous calculation of the transaction-tax amount of the transaction.