Transaction accounting auditing approach and system therefor

• US 7,574,386 B2
• Filed: 05/03/2005
• Issued: 08/11/2009
• Est. Priority Date: 06/09/2004
• Status: Active Grant

• Current Assignee: Syncada LLC (US Bancorp)
• Original Assignee: US Bank National Association (US Bancorp)
• Inventors: Hahn-Carlson, Dean W., Suits, David A., Beck, Elizabeth A.
• Primary Examiner(s): Zeender; F.
• Assistant Examiner(s): BUCHANAN, CHRISTOPHER R
• Application Number:
  US11/120,623
• Publication Number:
  US 20050278221A1
• Time in Patent Office: 1,561 Days
• Field of Search: None
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Accounting data is classified to facilitate transaction processing and management. According to an example embodiment, data based rules are implemented for classifying transaction-related data into accounting categories. Accounting information is processed as a function of the data based rules and accordingly automatically classified. This processing involves, for example, the identification of particular data based rules to apply to the accounting information, applying the rules and processing the information accordingly.

Claims

1. A transaction payment system to audit transaction data for a multitude of different transaction parties as a function of contract terms agreed to by a buyer of merchant offerings and a seller of the merchant offerings for each transaction, the system comprising:

a software-programmed circuit configured, for each of a multitude of sets of transaction data, to

execute an identification algorithm, using the transaction data set and stored profile data for a multitude of transaction participants, to identify data element-specific classification rules pertaining to at least one of a buyer and a seller;

select one of a plurality of data-auditing algorithms respectively programmed on behalf of disparate entities;

execute the selected data-auditing algorithm to audit individual data elements within each set of transaction data using the set of transaction data and the identified data element-specific classification rules as inputs to the algorithm, to determine a condition of electronic payment data validation for each data element.

2. The system of claim 1, wherein the software-programmed circuit is further configured to

prior to auditing against line-item-expense-classification rules, generate payment authorization data for the transaction as a function of the transaction data and the contract terms;

and

generate payment validation data to validate the payment authorization data as applied to each data element in the transaction data set in response to the determined condition of electronic payment data validation.

3. The system of claim 2, wherein the software-programmed circuit is further configured to, prior to authorizing payment for the transaction,

associate the transaction data with at least one of the buyer and the seller, and

in response to the associating, select the contract terms used in authorizing payment.

4. The system of claim 3, wherein the software-programmed circuit is further configured to, prior to auditing transaction data and after associating the transaction data, electronically record the transaction data on behalf of and in electronic association with said at least one of the buyer and the seller.

5. The system of claim 4, wherein the software-programmed circuit is further configured to

electronically record the transaction data on behalf of and in association with said at least one of the buyer and the seller by recording transaction data from a transaction-based document under a general accounting code associated with at least one of the buyer and the seller, and

audit individual data elements to classify transaction data including line-item transaction data by associating said line-item transaction data from the transaction data set with a line-item accounting classification.

6. The system of claim 1, wherein the software-programmed circuit is further configured to audit individual data elements against line-item-accounting-classification rules provided by said one of the buyer and the seller by, for each line item in said transaction data, classifying line-item transaction data under a line-item accounting classification as a function of the data element-specific classification rules and the type of accounting data in the line item.

7. The system of claim 6, wherein the software-programmed circuit is further configured to classify the line-item transaction data under a line-item accounting classification as a function of the data element-specific classification rules and the type of accounting data in the line item by processing alphanumeric type line item identification in accordance with the line-item classification rules to identify the type of accounting data in the line item.

8. The system of claim 6, wherein the software-programmed circuit is further configured to classify the line-item transaction data under a line-item accounting classification as a function of the data element-specific classification rules and the type of accounting data in the line item by processing a merchant offerings code in the line item identification in accordance with the line-item classification rules to identify the type of accounting data in the line item.

9. The system of claim 6, wherein the software-programmed circuit is further configured to classify the line-item transaction data under a line-item accounting classification as a function of the data element-specific classification rules and the type of accounting data in the line item by processing a universal product code (UPC) in the line item identification in accordance with the data element-specific classification rules to identify the type of accounting data in the line item.

10. The system of claim 1, further comprising storing each data element in the audited transaction data set in association with an accounting classification as a function of the auditing.

11. The system of claim 1, further comprising monitoring changes to the data element-specific classification rules.

12. The system of claim 11, further comprising monitoring a user ID associated with a user implementing changes to the data element-specific classification rules.

13. The system of claim 11, further comprising storing the data element-specific classification rules and wherein monitoring changes to the data element-specific classification rules includes monitoring changes to the stored line-item accounting classification rules.

14. The system of claim 1, further comprising storing the data element-specific classification rules and restricting access to the stored data element-specific classification rules.

15. The system of claim 14, wherein restricting access to the stored data element-specific classification rules includes granting access for modifying the stored data element-specific classification rules as a function of a security condition associated with a user for which access is to be granted.

16. The system of claim 1, wherein the software-programmed circuit is configured to audit individual data elements within each set of transaction data using data element-specific classification rules by

retrieving previously-stored line-item data elements having a classification assigned thereto, and

using the data element-specific classification rules to determine whether the classification assigned to the previously-stored line-item data elements is proper.

17. The system of claim 1, wherein the software-programmed circuit is configured to audit individual data elements within each set of transaction data using data element-specific classification rules by

retrieving previously-stored line-item data elements having a classification assigned thereto, and

using data element-specific classification rules provided by a third party that is independent from the buyer and the seller to determine whether the classification assigned to the previously-stored line-item accounting data is proper.