Expenditure accounting management system and method

• US 20060206506A1
• Filed: 08/26/2005
• Published: 09/14/2006
• Est. Priority Date: 03/11/2005
• Status: Abandoned Application

• Current Assignee: Thomas J. Fitzpatrick
• Original Assignee: Thomas J. Fitzpatrick
• Inventors: Fitzpatrick, Thomas J.
• Application Number:
  US11/213,577
• Publication Number:
  US 20060206506A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems

Abstract

A web based payment card software application for an expenditure accounting management automation system that provides a plurality of event code identifiers for processing, reporting and recording expenditure spending related to transaction data activity, including a one of a plurality of expenditure identifiers associated with line item transaction data comprising multiple line items of products and/or expenditure identifiers. The expenditure identifiers and event code identifiers along with their associated GL designated accounts enable automated processing of expense and procurement account data by cardholders.

Claims

1. An expenditure accounting management system comprising a computer system configured to:

access transaction data representing a client expenditure in exchange for a plurality of products, the transaction data including one product identifier associated with one of the products and a different product identifier associated with a different one of the products;

store the transaction data in association with an expenditure identifier associated with the one product identifier and designating an account in a client accounting system and a different expenditure identifier associated with the different product identifier and designating a different account in the client accounting system; and

provide the client accounting system access to the stored transaction data including the stored expenditure identifiers.

2. The expenditure accounting management system of claim 1 wherein the computer system is further configured to associate the expenditure identifier with the one product identifier and associate the different expenditure identifier with the different product identifier.

3. The expenditure accounting management system of claim 1 wherein the computer system is further configured to receive the transaction data representing the client expenditure in exchange for the plurality of products.

4. The expenditure accounting management system of claim 1 wherein the computer system comprises a payment card company subsystem, a merchant subsystem, and a client subsystem.

5. A method of automated expenditure accounting management comprising:

associating a product identifier associated with a product and an expenditure identifier designating an account in a client accounting system;

associating a different product identifier associated with a different product and a different expenditure identifier designating a different account in the client accounting system;

storing transaction data including the product identifiers and associated expenditure identifiers; and

providing the client accounting system access to the transaction data and associated expenditure identifiers.

6. The method of claim 5 further comprising constructing a database storing the product identifiers associated with their respective expenditure identifier.

7. The method of claim 5 further comprising receiving client input related to reimbursable expenditures.

8. The method of claim 5 further comprising associating a client account with each expenditure identifier.

9. The method of claim 5 further comprising storing data in association with each expenditure identifier indicating whether the expenditure identifier relates to a personal or business transaction.

10. The method of claim 5 further comprising associating a product identifier with each of a plurality of merchant products.

11. The method of claim 5 further comprising conducting a transaction between a cardholder and a merchant.

12. The method of claim 5 further comprising querying transaction data to capture accrued expenditures.

13. The method of claim 5 further comprising associating an event code identifier with each expenditure identifier.

14. A storage medium comprising data combinable with a computer system such that the computer system:

associates a product identifier and an expenditure identifier designating an account in a client accounting system;

associates a different product identifier and a different expenditure identifier designating a different account in the client accounting system;

stores transaction data including the product identifiers and associated expenditure identifiers; and

provides the client accounting system access to the transaction data and associated expenditure identifiers.

15. The storages medium of claim 14 further comprising data combinable with the computer system such that a merchant subsystem transmits the product identifiers and expenditure identifiers.

16. The storage medium of claim 14 further comprising data combinable with the computer system such that a payment card company subsystem receives the product identifiers and expenditure identifiers.

17. The storage medium of claim 14 further comprising data combinable with the computer system such that the computer system provides a client cardholder access to the expenditure identifiers.

18. The storage medium of claim 14 further comprising data combinable with the computer system such that the computer system stores an event code identifier in association with each expenditure identifier.

19. A point of sale apparatus for a merchant comprising

a memory holding a data collection of purchased items in a single transaction with a charge card customer, each of the items being identified with an expenditure identifier, the data collection including an amount associated with each expenditure identifier and a charge card account to be charged in the single transaction, and

a transmitter to transmit the data collection to a credit card processor associated with the charge card used by the customer for payment to the merchant.

20. A charge card provider automation apparatus comprising

a receiver to receive from a merchant a data collection of purchased items in a single transaction with a charge card customer, each of the items being identified with an expenditure identifier, the data collection including an amount associated with each expenditure identifier and a charge card account to be charged in the single transaction, and

a memory to hold the received data collection, and

a transmitter to transmit the data collection to a credit card account member associated with the charge card used by the customer for payment to the merchant.

21. A charge card member automation apparatus comprising

a receiver to receive from a charge card provider a data collection of purchased items in a single transaction with a charge card customer, each of the items being identified with an expenditure identifier, the data collection including an amount associated with each expenditure identifier and a charge card account charged in the single transaction, and

a memory to hold the received data collection, and

processor apparatus to accumulate a plurality of received data collections and allocate charged amounts to card member accounting accounts according to received expenditure identifiers.

22. An automated expenditure accounting management system comprising a computer system including a merchant subsystem with a communication network, a client subsystem with a communication network, and a payment card company subsystem with a communication network, the computer system configured to:

associate a plurality of identifiers in association with transaction data related to purchases, including any general transaction fees charged by a merchant through the utilization of an electronic payment card by a payment cardholder;

associate a plurality of identifiers associated with transaction data related to purchases, including any general transaction fees charged by a merchant through the utilization of currency by a payment cardholder;

associate a plurality of identifiers associated with transaction data related to personal vehicle usage reimbursement expenditures by a cardholder;

associate the transaction data in association with the plurality of identifiers to an expense report subroutine within the payment card company subsystem for the processing of cardholder expense reports;

associate the transaction data in association with the plurality of identifiers to an accounting journal entry subroutine within the payment card company subsystem for the recording of cardholder expenditure; and

associate the transaction data in association with the plurality of identifiers to an expenditure analysis reporting subroutine within the payment card company subsystem for analyzing the database transaction data through client defined relational database management reports.

23. The automated expenditure accounting management system of claim 22 wherein the merchant subsystem of the computer system is further configured to:

receive via the communication network upon merchant association with a payment card company and periodically thereafter an interface file with a plurality of expenditure identifiers from the payment card subsystem;

associate each of a plurality of merchant products with an expenditure identifier thus generating a merchant expenditure identifier, interface file on the merchant subsystem, one of the plurality of products being associated with one of a plurality of expenditure identifiers and another of the plurality of products being associated with the same or a different expenditure identifier; and

comprise a point of sale apparatus with a transmitter/receiver and a memory.

24. The automated expenditure accounting management system of claim 23 wherein the merchant point of sale apparatus is configured to:

associate each of the purchased products in association with a single transaction by a cardholder with an expenditure identifier from the merchant expenditure identifier interface file;

associate any general transaction fee charged in association with a single transaction to each expenditure identifiers in an amount equal to the portion of that product fee basis;

associate each of the merchant products in association with a single transaction with a database code identifier;

associate each of the merchant products in association with a single transaction with the cardholder account number;

associate an amount in association with a single transaction that represents the total amount charged to a cardholder'"'"'s account number;

hold the data collection of the purchased products from a single transaction with a cardholder in the point of sale memory, each of the products being identified with an associated expenditure identifier, the data collection including;

(a) the amount associated with each product plus an amount that represents the pro-rata portion of any general transaction fee, (b) the cardholder'"'"'s account number, (c) the database code identifier, and (d) a transaction total amount; and

transmit the data collection of purchased product in a single transaction to the payment card company associated with the cardholder'"'"'s payment card that is used by the customer for payment of the purchased products.

25. The automated expenditure accounting management system of claim 22 wherein the client subsystem of the computer system is further configured to:

comprise a client automation apparatus with a transmitter/receiver and a memory;

provide the client access to the payment card company subsystem for the purpose of;

(a) associating and inputting a client general ledger designated account to a client expenditure identifier interface file thus generating a client expenditure identifier with an associated general ledger designated account interface file, (b) inputting client defined event code identifiers with associated general ledger designated account thus generating a client event code identifier with associated general ledger designated account interface file, and (c) inputting client defined cardholder employment identifiers in association with each cardholder account number that is issued a electronic payment card by the payment card company thus generating a cardholder'"'"'s account number with the cardholder'"'"'s employment identifiers interface file;

provide the cardholder access to the payment card company subsystem for the purpose of accessing the data collection of a plurality of transactions associated with a one of the two database code identifier transaction data (a) reviewing the merchant transmitted data collection information to the payment card company, (b) associating a event code identifier with a general ledger designated account, adding cost allocation identifiers and amounts when applicable, and adding disclosure identifiers when applicable to each of the listed expenditure identifiers;

provide the cardholder access to the payment card subsystem expense report subroutine for the purpose of processing an employee expense report for supervisor approval by selecting an event code identifier and (a) inputting required dating parameters of the cardholder event expense period, (b) inputting applicable per diem rates for the event, and (c) submitting and notifying via email notification cardholder'"'"'s supervisor of a report for approval, the computer system automatically associating a spending report identifier to the submitted unapproved expense report and associated expenditures identifiers;

provide the cardholder'"'"'s supervisor access to the payment card company subsystem expense report subroutine for the purpose of (a) approving an expense report associated to a spending report identifier and notifying the cardholder of the approval via email notification, the computer system automatically associating a supervisor authorization identifier to the approved expense report and associated expenditure identifiers, or (b) rejecting an expense report associated to a spending report identifier and notifying the cardholder of the rejection via email notification with a supervisor commentary of rejection;

provide client accounting personnel access to the payment card company subsystem accounting journal entry subroutine for the purpose of conducting a period end closing on the transaction data for (a) accrual transaction activity including current period accrual and previous period automatic accrual reversal comprising;

     1) raw data accrual including transaction data with an expenditure identifier associated with its general ledger designated account only;

     2) event raw data accrual including transaction data expenditure identifier and an associated event code identifier with its associated general ledger designated account; and

     3) submitted raw data accrual including transaction data expenditure identifier, an associated event code identifier with its general ledger designated account and a spending report identifier;

or (b) approved expense reports transaction activity, transaction data expenditure identifier, an associated event code identifier with its general ledger designated account, a spending report identifier, and a supervisor authorization identifier; and

provide the client accounting personnel access to the payment card company subsystem expenditure analysis reporting subroutine for the querying of historical and current transaction data transaction data for management reporting analysis with dating sensitivity, identifier sensitivity, exception reporting and compliance reporting sensitivity.

26. The automated expenditure accounting management system of claim 22 wherein the payment card company subsystem of the computer system is configured to:

comprise a payment card company relational database transaction data computer server system to hold the automation software and transaction data;

comprise a payment card company automation apparatus with a transmitter/receiver and a memory;

receive via the merchant point of sale apparatus the data collection of purchased products in a single transaction with a payment cardholder, each of the products being identified with an associated expenditure identifier, the data collection including (a) an amount associated with each products plus an amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, and transaction fees, (b) the cardholder'"'"'s account number, (c) the database code identifier, and (d) a transaction total amount;

amend the data collection of purchased products in a single transaction automatically with the associated general ledger designated account from the client expenditure identifier interface file, as well as associate the cardholder'"'"'s employment identifiers from the cardholder'"'"'s account number interface file to each of the products transmitted from the merchant;

store the data collection of purchased products in a single transaction with each of the products being identified with their associated expenditure identifier in association with its general ledger designated account, the data collection including (a) an amount associated with each product(s) plus an amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, and transaction fees (b) the cardholder'"'"'s account number with employment identifiers, (c) the database code identifier, and (d) a transaction total amount;

store the transaction data in association with an expenditure identifier with one of a plurality of event code identifiers with a general ledger designated account selected from the event code identifier interface file, each one expenditure identifier being associated with an event code identifier and each different expenditure identifier being associated with the same or a different event code identifier;

store the transaction data in association with an expenditure identifier with one of a plurality of cost allocation identifiers and amounts when applicable for each associated expenditure identifier in which a per diem rate would apply;

store the transaction data in association with an expenditure identifier with a disclosure identifier such as a comment/description identifier for each associated expenditure identifier in which a identifier of those entertained would apply;

store the transaction data in association with an expenditure identifier with a computer generated spending report identifier upon submission of an expense report in association with the spending report subroutine submission;

store the transaction data in association with an expenditure identifier with a supervisor authorization identifier, to signifying only those expenditure identifiers associated with a spending report identifier for which a supervisor has approved the spending report for final client processing and recording as part of the spending report subroutine;

store the transaction data in association with an expenditure identifier with a journal entry identifier signifying the status of the merchant products associated with a cardholder account number for a specific client account with respect to accrual, reversal and final journal entry recording requirements in association with a period end closing process of the journal entry subroutine;

provide cardholder access to the stored transaction data for the purpose of inputting event code identifiers, cost allocation identifiers with amounts when applicable, and/or disclosure identifiers;

provide cardholder access to the spending report subroutine for the purpose of processing an expense report related to specific event code identifier and to input of expense report transaction data related to spending report submissions;

provide cardholder'"'"'s supervisor access to spending report subroutine for the purpose of reviewing a cardholder'"'"'s submitted expense report;

provide client accounting personnel access to the accounting journal entry subroutine for the purpose of processing accounting period closings; and

provide client accounting personnel access to the expenditure analysis reporting subroutine for the querying of transaction data for management analysis reporting.

27. The expenditure accounting management system of claim 26 wherein the payment card company computer subsystem is further configured to have a cardholder expense report preparation and approval process subroutine to:

provide access to a cardholder to selected transaction data which has an association to a specific event code identifier in a standardized payment card company expense report format;

associate a specific start date and a specific end date to the expense report identified to the specific event code identifier including the duration of time in days in which the cardholder incurred the event expenditures through the inputting of the dating event parameters;

associate, if applicable, a per diem rate parameter with respect to the per diem rate applicable to the event code identifier site location through the inputting of a per diem rate in association with the specific event code identifier;

store the prepared cardholder expense report through the submission of the completed expense report via the subroutine as a spending report with an associated system generated spending report identifier associated to each of the products that are associated with the specific event code identifier, the spending report identifier having a suffix character set to identify resubmission of amended expense reports, and notify the supervisor via email notification of a spending report identifier that needs approval;

provide access to the cardholder'"'"'s supervisor to select a spending report identifier for the purpose, (a) approving an expense report associated to a spending report identifier and notifying the cardholder of the approval via email notification and transmitting reimbursement/repayment data from a cardholder'"'"'s expense report submission that is associated with the supervisor authorization identifier in association with a specific spending report identifier to the client'"'"'s payroll department for inclusion with the next scheduled cardholder payroll period, or (b) rejecting an expense report associated to a spending report identifier and notifying the cardholder of the rejection via email notification with a supervisor commentary of rejection; and

associating a system generated supervisor authorization identifier to the approved spending report identifiers; and

store the approved cardholder expense report associated to an approved spending report identifier in association with a supervisor authorization identifier.

28. The expenditure accounting management system of claim 26 wherein the payment card company computer subsystem is further configured to have an accounting journal entry subroutine to:

provide the client personnel access to the payment card company subsystem accounting journal entry subroutine for the purpose of generating and approving period end closing journal entries in association with the transaction data for (a) accrual transaction activity including current period accrual and previous period automatic accrual reversal,

     1) raw data accrual, transaction data with an expenditure identifier associated with its general ledger designated account only;

     2) event raw data accrual, transaction data expenditure identifier and an associated event code identifier with its associated general ledger designated account;

     3) submitted raw data accrual, transaction data expenditure identifier, an associated event code identifier with its general ledger designated account and a spending report identifier;

or (b) approved expense reports transaction activity, transaction data expenditure identifier, an associated event code identifier with its general ledger designated account, a spending report identifier, and a supervisor authorization identifier;

associating journal entry identifiers to each of the products within the client specific transaction database as determined by cardholder account numbers associated with a specific client account that indicates whether the merchant products are associated or unassociated with an expenditure identifier, event code identifier, spending report identifier and/or a supervisor authorization identifier as of the processing date of a period end closing subroutine process including journal entry identifiers associated with the merchant products to identify whether the status of the merchant product as of the processing date is an accrual status product requiring an automatic reversal in the subsequent accounting period close or a final recoded status product wherein no reversal in the subsequent accounting period close; and

store the journal entry identifiers in association with the period end closing routine process with the merchant products in accordance with the relevant status of the merchant products as of the date of the processing.

29. The expenditure accounting management system of claim 26 wherein the payment card company computer subsystem is further configured to have an expenditure analysis reporting subroutine to:

provide the client personnel access to the payment card company subsystem expenditure analysis reporting subroutine for the querying of transaction data including historical and current transaction data for management reporting analysis with selection sensitivity for transaction dates, identifiers, exception reporting and compliance reporting.

30. The expenditure accounting management system of claim 22 wherein the computer system is further configured to receive the transaction data representing expenditures in exchange for the plurality of products, its associated expenditure identifiers, database code identifier, cardholder'"'"'s account number, and the transaction total amount.

31. The expenditure accounting management system of claim 22 wherein the computer system is further configured to receive the transaction data representing expenditures in exchange for the plurality of products, with the purchase amount for the merchant product, as well as the amount that represents the pro-rata portion of any general transaction fee including sales tax, value added taxes, surcharges, or transaction fees.

32. A method of automated expenditure management comprising:

associating an expenditure identifier that is associated with a general ledger designated account to the merchant product from a single transaction;

associating the same or a different expenditure identifier with a general ledger designated account to a different merchant product from a single transaction;

associating a database code identifier to each of the merchant products from a single transaction;

associating a cardholder account number that is associated with the employment identifiers to each of the merchant products from a single transaction;

associating a merchant product from a single transition further with the input of an event code identifier that is associated with a general ledger designated account, a cost allocation identifiers with an amount, and a disclosure identifier;

associating a different merchant product from a single transaction further with the input of a different event code that is associated with a general ledger designated account, a cost allocation identifier with the an amount, and a disclosure identifier;

associating a spending report identifier and a supervisor authorization identifier to each of the merchant products as part of the preparation and approval process of the specific event code identifier expense report subroutine submission;

storing the transmitted transaction data with an expenditure identifier that is associated with automatically with the general ledger designated account for a merchant product from a single transaction;

storing the transmitted transaction data with the same or a different expenditure identifier that is associated automatically with the general ledger designated account for a different merchant product form a single transaction;

storing the transmitted transaction data with a database identifier for each of the merchant products from a single transaction;

storing the transmitted cardholder account number that is associated with the employment identifiers for each of the merchant products from a single transaction;

storing the inputted event code identifier that is associated with a general ledger designated account for each of the merchant products from a single transaction;

storing the inputted cost allocation identifiers with an amount for each of the merchant products from a single transaction;

storing the inputted disclosure identifier for each of the merchant products from a single transaction;

storing the automatically generated spending report identifiers to each of the merchant products from a single transaction when submitting an expense report as part of the spending report subroutine;

storing the automatically generated supervisor authorization identifier to each of the merchant products from a single transaction when a submitted expense report is approved as part of the spending report subroutine; and

providing the cardholder, the cardholder'"'"'s supervisor, and client personnel including the client general ledger accounting system access to the stored transaction data including expenditure identifiers that are associated with a general ledger designated account, cardholder account number that are associated with employment identifiers, event code identifiers that is associated with a general ledger designated accounts, cost allocation identifiers with amounts, disclosure identifiers, spending report identifiers, and supervisor authorization identifier.

33. The method of claim 32 further comprising constructing a database of transaction data storing the products with each of their respective identifiers and any associated general ledger designated accounts and employment identifiers.

34. The method of claim 32 further comprising receiving client personnel input related to identifier maintenance, company policy compliance parameters and reimbursable expenditures.

35. The method of claim 32 further comprising receiving cardholder input related to cardholder related identifier maintenance and reimbursable expenditures.

36. The method of claim 32 further comprising associating a general ledger designated account with each expenditure identifier, as well as associating the same or a different general ledger designated account with each event code identifier.

37. The method of claim 32 further comprising associating the related employment identifiers with each cardholder account number.

38. The method of claim 32 further comprising storing data in association with each product indicating whether the product purchased by the cardholder from a single transaction is associated to a business expenditure or personal expenditure.

39. The method of claim 32 further comprising associating an expenditure identifier from the merchant expenditure identifier interface file to each of a plurality of merchant products.

40. The method of claim 32 further comprising conducting a transaction between a merchant and a cardholder.

41. The method of claim 32 further comprising associating an event code identifier that is associated with a general ledger designated account with each merchant product.

42. The method of claim 32 further comprising a method for associating transaction data, as part of the expense report subroutine, that has not yet been submitted as an expense report and thus a spending report identifier is not yet been associated with the product, and an event code identifier has not been associated with said product as raw data accrual information for the accounting journal entry subroutine to the client'"'"'s general ledger accounting system with a automatic reversal feature during the client'"'"'s next accounting period by associating each such product with the general ledger designated account that is associated with that product'"'"'s expenditure identifier.

43. The method of claim 32 further comprising a method for associating transaction data, as part of the expense report subroutine, that has not been submitted as an expense report and thus a spending report identifier is has not been associated with the product, but an event code identifier has been input and thus associated with said product as event raw data accrual information for the accounting journal entry subroutine to the client'"'"'s general ledger accounting system with a automatic reversal feature during the client'"'"'s next accounting period by associating each such product with the general ledger designated account that is associated with that product'"'"'s event code identifier.

44. The method of claim 32 further comprising a method for associating transaction data, as part of the expense report subroutine, that has been submitted as an expense report and thus a spending report identifier has been associated with the product, and event code identifier has been associated with said product, but a supervisor authorization identifier does not yet indicate approval as submitted raw data accrual information for the accounting journal entry subroutine to the client'"'"'s general ledger accounting system with a automatic reversal feature during the client'"'"'s next accounting period by associating each such product with the general ledger designated account that is associated with that product'"'"'s event code identifier.

45. The method of claim 32 further comprising a method for associating transaction data, as part of the expense report subroutine, that has been submitted as an expense report and thus a spending report identifier is has been associated with the product, an event code identifier has been associated with said product, and the supervisor authorization identifier indicates spending report approval as an approved spending report information for the accounting journal entry subroutine to the client'"'"'s general ledger accounting system with a no automatic reversal feature during the client'"'"'s next accounting period by associating each such product with the general ledger designated account that is associated with that product'"'"'s event code identifier.

46. A storage medium comprising data combinable with a computer system such that the computer system:

associates a merchant product and an expenditure identifier designating a general ledger designated account in a client general ledger accounting system;

associates a different merchant product and the same or a different expenditure identifier designating the same or a different general ledger designated account in a client general ledger accounting system;

associates a merchant product and an event code identifier designating a general ledger designated account in a client general ledger accounting system;

associates a different merchant product and the same or a different event code identifier designating the same or a different general ledger designated account in a client general ledger accounting system;

stores transaction data including the merchant products and associated expenditure identifiers and associated event code identifiers; and

provides the cardholder, cardholder'"'"'s supervisor, and client personnel including the client general ledger accounting system access to the transaction data, the associated expenditure identifiers and event code identifiers that are associated with merchant products.

47. The storage medium of claim 46 further comprising data combinable with the computer system such that a merchant subsystem transmits the merchant products, expenditure identifiers, database identifier, and cardholder'"'"'s account number, along with the amount of each merchant product price cost, the amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, transaction fees, and the total transaction amount.

48. The storage medium of claim 46 further comprising data combinable with the computer system such that a payment card company subsystem receives the merchant products, expenditure identifiers, database identifier, and cardholder'"'"'s account number along with the amount of each merchant product price cost, the amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, transaction fees, and the total transaction amount.

49. The storage medium of claim 46 further comprising data combinable with the computer system such that a payment card company subsystem amends the general ledger designated account that is associated with the received expenditure identifier and amends the employment identifiers associated with the received cardholder'"'"'s account number to the transaction data previously stored.

50. The storage medium of claim 46 further comprising data combinable with the computer system such that the computer system provides a cardholder access to the expenditure identifiers.

51. The storage medium of claim 46 further comprising data combinable with the computer system such that the computer system provides a cardholder access to the event code identifiers with their associated general ledger designated accounts, the cost allocation identifiers with amounts and disclosure identifiers for the purpose of inputting relevant data.

52. The storage medium of claim 46 further comprising data combinable with the computer system such that the computer system stores the event code identifier with its associated general ledger designated account, the cost allocation identifiers with amounts and disclosure identifiers.

53. A point of sale apparatus for a merchant comprising:

memory holding a data collection of purchased products in a single transaction with a payment card customer, each of the products associated with an expenditure identifier, the data collection including an amount associated with purchase price of each product, the amount that represents the pro-rata portion of an general transaction fee such as sales tax, value added taxes, surcharges, transaction fees, the total transaction amount, and a cardholder'"'"'s account number to be charged in the single transaction; and

a transmitter to transmit the data collection to a payment card company associated with a payment card used by the customer for payment of the merchant products.

54. A payment card company automation apparatus comprising:

a receiver to receive from a merchant a data collection of purchased products in a single transaction with a cardholder, each of the products being identified as a merchant product with an associated expenditure identifier, the data collection including an amount associated with each product, the amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, transaction fees, the total transaction amount, and a cardholder'"'"'s account number to be charged in the single transaction;

memory to hold the received data collection; and

a transmitter to transmit the data collection to a client and/or cardholder associated with the cardholder account number used by the customer for payment of the merchant products.

55. A client business transactions or a cardholder personal transactions automation apparatus comprising:

a receiver to receive from a payment card company a data collection of purchased products in a single transaction with a payment card customer, each of the products with an associated expenditure identifier, the data collection including (a) an amount associated with each product(s) plus an amount that represents the pro-rata portion of any general transaction fee such as sales tax, value added taxes, surcharges, transaction fees, (b) the cardholder'"'"'s account number, (c) the database code identifier, and (d) a transaction total amount charged;

memory to hold the received data collection; and

processor apparatus to accumulate a plurality of received data collections and allocate charged amounts to the cardholder'"'"'s account number according to received product(s) and expenditure identifiers.