Automated transaction processing system and approach

• US 7,925,551 B2
• Filed: 06/09/2004
• Issued: 04/12/2011
• Est. Priority Date: 06/09/2004
• Status: Active Grant

• Current Assignee: Syncada LLC (US Bancorp)
• Original Assignee: Syncada LLC (US Bancorp)
• Inventors: Hahn-Carlson, Dean W., Suits, David A., Kanathur, Raghunandan, Xie, Weiwen
• Primary Examiner(s): Gart; Matthew S
• Assistant Examiner(s): HAYLES, ASHFORD S
• Application Number:
  US10/864,761
• Publication Number:
  US 20050278220A1
• Time in Patent Office: 2,498 Days
• Field of Search: 705/30, 707/102, 707/205
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Transaction processing is facilitated using an approach for automatically grouping transaction-based documents as a function of matching data in the documents. In one example embodiment of the present invention, data from selected attribute fields in transaction-based documents is parsed as the documents are received at a transaction processor. When data in selected attribute fields from two or more documents match, the transaction processor automatically groups the documents having matching data under a particular anchor identification code defined as a function of the match. Upon receipt of one or more other transaction-based documents, the transaction processor advances progress towards completion of the common transaction to which the documents apply. With this approach, predefined data (e.g., a purchase order number) need not necessarily be included with a particular transaction document in order to group the document with another document belonging to the same common transaction.

Claims

1. A transaction-processing system comprising:

a transaction databank having a plurality of anchor locations, each anchor location for storing a plurality of transaction-profile attributes that correspond to one of a plurality of transactions involving merchant offerings among parties including buyers and sellers; and

a computer arrangement adapted to;

determine each transaction by identifying a plurality of common attributes that define the transaction, the identified common attributes being carried by respective transaction-based documents as respectively provided by different parties to the transaction, the different parties to the transaction having different party-identifying attributes;

assign an anchor identification (ID) to each transaction for which common attributes carried by respective transaction-based documents have been identified;

for each transaction, use the identified common attributes to construct a plurality of transaction-profile attributes in a particular one of the anchor locations identified by the anchor ID;

parse incoming transaction-based documents for the attributes of anchor locations stored in the transaction databank and, in response to finding insufficient matching attributes carried by one of the incoming transaction-based documents and stored in the transaction databank under an existing anchor location, establish a new anchor location in the transaction databank and store the attributes from the one of the incoming transaction-based documents in the new anchor location; and

in response to another transaction-based document carrying transaction-profile attributes for a particular one of the anchor locations, use the constructed transaction-profile attributes in the particular anchor location to advance progress toward completion of the transaction for the particular anchor location by generating and outputting electronic payment data for the transaction.

2. The system of claim 1, wherein the computer arrangement is adapted to identify attributes for a transaction by matching attributes that are common to two or more respective transaction-based documents, and wherein the anchor ID is not one of the common attributes.

3. The system of claim 2, wherein the computer arrangement is adapted to match the attributes from specific transaction-profile attribute fields in each of the two or more transaction-based documents.

4. The system of claim 3, wherein the computer arrangement is adapted to access user-defined information identifying the specific transaction-profile attribute fields to use in matching the attributes.

5. The system of claim 1, wherein the computer arrangement is adapted to identify the attributes for a transaction as a function of predefined fields associated with an anchor location.

6. The system of claim 5, wherein the computer arrangement is adapted to parse incoming transaction-based documents for the identified attributes in the predefined fields and, in response to an incoming transaction-based document including the identified attributes, group the transaction-based document under the anchor location.

7. The system of claim 1, wherein the computer arrangement is adapted to define attribute fields used for establishing attributes that identify a particular transaction as a function of data in the defined attribute fields of the respective transaction-based documents, and wherein the anchor ID is not one of the common attributes.

8. The system of claim 7, wherein the computer arrangement is adapted to parse incoming transaction-based documents for data in the defined attribute fields and, in response to a transaction-based document including data in the defined attribute fields that matches the transaction-profile attributes of a particular one of the anchor locations, to assign the transaction-based document an anchor ID associated with the particular anchor location.

9. The system of claim 7, wherein the computer arrangement is adapted to define a first group of anchor attribute fields used for establishing attributes that identify a particular transaction as a function of the attribute fields in first and second transaction-based documents, and to define a second group of anchor attribute fields that identify the particular transaction as a function of the attribute fields in one of the first and second transaction-based documents and in a third transaction-based document, the first and second groups of attribute fields being different and both defining transaction-based documents belonging to the same transaction.

10. The system of claim 1, wherein the computer arrangement is adapted to parse incoming transaction-based documents for the identified attributes of anchor locations in the transaction databank and, in response to finding matching attributes carried by the transaction-based document and stored in the transaction databank under a particular anchor location, store the attributes from the transaction-based document in the particular anchor location.

11. The system of claim 1, wherein the computer arrangement is adapted to retrieve information from all transaction-based documents stored in the transaction databank and labeled with a particular anchor ID in response to a user request including the anchor ID.

12. The system of claim 1, wherein the computer arrangement is adapted to retrieve transaction-profile attributes stored in a particular anchor location in response to a user request including transaction-profile attributes from one of the transaction-based documents stored in the particular anchor location.

13. The system of claim 1, wherein the computer arrangement is adapted to assign restriction criteria to transaction-profile attributes for a particular transaction and, in response to detecting attributes of a new transaction-based document that match the transaction-profile attributes, including the restriction criteria, for the particular transaction, use the attributes of the new transaction-based document to construct a plurality of transaction-profile attributes in another one of the anchor locations.

14. The system of claim 13, wherein the computer arrangement is adapted to assign restriction criteria that limits an anchor location to storing only one of a particular type of transaction-based document, and to construct a plurality of transaction-profile attributes for the new transaction-based document in another one of the anchor locations in response to the new transaction-based document having attributes matching the type of another transaction-based document stored in the limited anchor location.

15. The system of claim 1, wherein the computer arrangement is adapted to advance progress toward completion of a transaction by generating transaction completion data for an active, previously incomplete transaction in response to the other transaction-based document including an update for the transaction-profile attributes in the particular one of the anchor locations.

16. The system of claim 15, wherein the computer arrangement is adapted to send the transaction completion data to users identified by the transaction-profile attributes in the particular anchor location.

17. The system of claim 15, wherein the computer arrangement is adapted to authorize payment for a particular transaction having transaction-profile attributes stored in a particular anchor location in response to receiving a transaction-based document having attributes that identify the document as belonging to the anchor location and indicating a transaction condition that is sufficient to authorize payment.

18. The system of claim 1, wherein the computer arrangement is further adapted to delineate the different party-identifying data in the transaction databank.

19. The system of claim 18, wherein the computer arrangement is further adapted to construct transaction-profile attributes in anchor locations according to the different party-identifying data.

20. The system of claim 1, wherein each anchor location having constructed transaction-profile attributes corresponds to only one unique transaction.

21. The system of claim 1, wherein the computer arrangement is adapted to merge transaction-profile attributes from two anchor locations to construct transaction-profile attributes in a new anchor location that corresponds to only one unique transaction having certain characteristics common to transactions to which said two anchor locations apply.

22. The system of claim 1, wherein the computer arrangement is further adapted to automatically monitor transaction data stored in the anchor locations for order fulfillment data and to automatically update order fulfillment status for transaction-based documents stored in the anchor locations in response to transaction data indicating characteristics of order fulfillment for the transaction.

23. The system of claim 1, wherein the computer arrangement is further adapted to store expense-related transaction-profile attributes in one of the anchor locations and to automatically classify expenses represented by the expense-related transaction-profile attributes into expense categories.

24. The system of claim 1, wherein the computer arrangement is further adapted to automatically generate and deliver interface documents to users identified by the transaction-profile attributes for a particular transaction, the interface documents including information for the particular transaction.

25. The system of claim 1, wherein the computer arrangement is further adapted to automatically generate transaction-profile attributes on a repetitive basis for a cyclic transaction having at least one particular anchor location, the automatically-generated transaction-profile attributes being used to reconstruct transaction-profile attributes in the at least one particular anchor location for the cyclic transaction.

45. The system of claim 1, wherein the anchor ID is not one of the common attributes.

26. A transaction-processing system for facilitating transactions involving merchant offerings among parties including buyers and sellers, aspects of each transaction being characterized by transaction-based documents, the system comprising:

a transaction databank having a plurality of anchor locations, each anchor location for storing a plurality of transaction-profile attributes that correspond to one of the transactions; and

a computer arrangement adapted to;

parse attribute fields from at least two incoming documents and, in response to finding matching information in selected ones of the parsed attribute fields, automatically identify the at least two incoming documents as belonging to a transaction for which payment has not been made, generate a new anchor identification number as a function of the data in the parsed attribute fields, store data from the parsed attribute fields in an anchor location in the transaction databank and identify the anchor location with the new anchor identification number; and

in response to another transaction-based document carrying data in attribute fields matching data in selected ones of the attribute fields stored in the anchor location identified with the new anchor identification number, use the data stored in the attribute fields and in the other transaction-based document to process payment for the transaction.

27. The system of claim 26, wherein the transaction databank is further configured and arranged to store user profile information for each party to the transaction, the user profile information including processing instructions for processing incoming documents corresponding to a particular transaction in which the party is involved, the computer arrangement being further adapted to process information from incoming documents corresponding to the particular transaction in accordance with the processing instructions.

28. In an environment of multiple parties to a transaction, a transaction terminal for processing transaction information related to an active transaction pursuant to a contract between one of the parties and another one of the parties, the transaction terminal comprising:

at least one computer-based circuit being software-programmed and configured and arranged to

compare attribute values of transaction-based documents and identify common attribute values between at least two of the transaction-based documents;

define an anchor identification (ID) as a function of the identified common attribute values, the anchor ID being used to identify a new transaction also pursuant to the contract;

label the at least two transaction-based documents with the anchor ID and store the labeled transaction-based documents in a database; and

in response to receiving another transaction-based document having attribute values that match attribute values in at least one of the at least two of the transaction-based documents, and prior to payment for the active transaction being made, use the stored transaction-based documents and the other transaction-based document to advance progress toward completion of the active transaction.

29. In an environment of multiple parties to a transaction, a transaction terminal for processing transaction information related to a transaction pursuant to a contract between one of the parties and another one of the parties, the terminal comprising:

at least one computer-based circuit being software-programmed and configured and arranged to

compare elements of transaction-based documents and identify common elements between at least two of the transaction-based documents;

compare the common elements with stored profile information associated with the one and the other one of the parties; and

define an anchor identification (ID) with the identified common elements and the profile information, the anchor ID being used to identify a new active transaction also pursuant to the contract for which performance of the transaction has not been completed by both parties to the transaction.

30. A method for facilitating transactions involving merchant offerings among parties including buyers and sellers, aspects of each common transaction being characterized by transaction-based documents that are respectively provided by different parties to the common transaction, the method comprising:

for each common transaction, identifying attributes that define the common transaction, the identified attributes being carried by respective transaction-based documents as respectively provided from the different parties to the common transaction, the different parties to the common transaction having different party-identifying attributes;

assigning an anchor identification (ID) to each common transaction for which attributes carried by respective transaction-based documents have been identified;

for each common transaction, using the identified attributes to construct a plurality of transaction-profile attributes in a particular anchor location of a transaction databank having a plurality of anchor locations and identifying the particular anchor location with the anchor ID;

parsing incoming transaction-based documents for the identified attributes of anchor locations stored in the transaction databank and, in response to finding insufficient matching attributes carried by one of the incoming transaction-based documents and stored in the transaction databank under an existing anchor location, establishing a new anchor location in the transaction databank and storing the attributes from the transaction-based document in the new anchor location; and

in response to another transaction-based document carrying transaction-profile attributes for a particular one of the anchor locations, using the constructed transaction-profile attributes in the particular anchor location to advance progress toward completion of the common transaction for the particular anchor location by generating and outputting electronic payment data for initiating payment to a seller on behalf of a buyer for the transaction.

31. The method of claim 30, wherein identifying attributes that define the common transaction includes matching attributes that are common to two or more respective transaction-based documents.

32. The method of claim 31, wherein matching attributes that are common to two or more respective transaction-based documents includes matching attributes from specific transaction-profile attribute fields in each of the two or more transaction-based documents.

33. The method of claim 32, wherein matching attributes from specific transaction-profile attribute fields includes accessing user-defined information identifying the specific transaction-profile attribute fields.

34. The method of claim 30, wherein identifying attributes that define the common transaction includes defining attribute fields used for establishing attributes that identify a particular transaction as a function of data in the defined attribute fields of the respective transaction-based documents.

35. The method of claim 30, wherein using the identified attributes to construct a plurality of transaction-profile attributes in a particular anchor location includes parsing incoming transaction-based documents for the identified attributes of anchor locations in the transaction databank and, in response to finding matching attributes carried by the transaction-based document and stored in the transaction databank under a particular anchor location, storing the attributes from the transaction-based document in the particular anchor location.

36. The method of claim 30, further comprising assigning restriction criteria to transaction-profile attributes for a particular common transaction and, in response to detecting attributes of a new transaction-based document that match the transaction-profile attributes, including the restriction criteria, for the particular common transaction, using the attributes of the new transaction-based document to construct a plurality of transaction-profile attributes in another one of the anchor locations.

37. The method of claim 30, wherein using the constructed transaction-profile attributes in the particular anchor location to advance progress toward completion of the common transaction for the particular anchor location includes generating transaction completion data in response to the other transaction-based document including an update for the transaction-profile attributes in the particular one of the anchor locations.

38. The method of claim 37, further comprising authorizing payment for a particular transaction having transaction-profile attributes stored in a particular anchor location in response to receiving a transaction-based document having attributes that identify the document as belonging to the anchor location and indicating a transaction condition that is sufficient to authorize payment.

39. A method for facilitating transactions involving merchant offerings among parties including buyers and sellers, aspects of each common transaction being characterized by transaction-based documents that are respectively provided by different parties to the common transaction, the method comprising:

for each common transaction, identifying primary and secondary attributes that define the common transaction and assigning higher weight to the primary attribute, relative to the secondary attribute, the identified attributes being carried by respective transaction-based documents as respectively provided from the different parties to the common transaction, the different parties to the common transaction having different party-identifying attributes;

assigning an anchor identification (ID) to each common transaction for which attributes carried by respective transaction-based documents have been identified;

for each common transaction, using the identified attributes to construct a plurality of transaction-profile attributes in a particular anchor location of a transaction databank having a plurality of anchor locations and identifying the particular anchor location with the anchor ID; and

in response to another transaction-based document carrying transaction-profile attributes for a particular one of the anchor locations, using the constructed transaction-profile attributes in the particular anchor location to advance progress toward completion of the common transaction for the particular anchor location by matching the other transaction based document with the attributes in the particular anchor location as a function of the primary and secondary attributes and their corresponding weight and by generating and outputting electronic payment data for initiating payment to a seller on behalf of a buyer for the transaction.

40. The method of claim 39, further comprising:

receiving a conflicting transaction-based document carrying transaction-profile attributes for a particular one of the anchor locations;

comparing the primary and secondary attributes of the conflicting transaction-based document and the other transaction-based document; and

determining which of the conflicting and other transaction-based documents better match the transaction-profile attributes in the particular anchor location as a function of the primary and secondary attributes in each of the transaction-based documents.

41. The method of claim 40, further comprising:

assigning another anchor location to another common transaction for which attributes carried by the one of the conflicting and other transaction-based documents that does not better match the transaction-profile attributes in the particular anchor location as a function of the primary and secondary attributes in each of the transaction-based documents.

42. A transaction-processing system for facilitating transactions involving merchant offerings among parties including buyers and sellers, aspects of each common transaction being characterized by transaction-based documents that are respectively provided by different parties to the common transaction, the system comprising:

means for storing a plurality of transaction-profile attributes that correspond to a transaction;

means, for each common transaction for which at least one party to the transaction has not performed, for identifying attributes that define the common transaction, the identified attributes being carried by respective transaction-based documents as respectively provided from the different parties to the common transaction, the different parties to the common transaction having different party-identifying attributes;

means for assigning an anchor identification (ID) to each common transaction for which attributes carried by respective transaction-based documents have been identified;

means, for each common transaction, for using the identified attributes to construct a plurality of transaction-profile attributes in a particular one of the anchor locations identified by the anchor ID;

means for parsing incoming transaction-based documents for the identified attributes of anchor locations stored in the transaction databank and, in response to finding insufficient matching attributes carried by one of the incoming transaction-based documents and stored in the transaction databank under an existing anchor location, establishing a new anchor location in the transaction databank and storing the attributes from the transaction-based document in the new anchor location; and

means, responsive to another transaction-based document carrying transaction-profile attributes for a particular one of the anchor locations, for using the constructed transaction-profile attributes in the particular anchor location to advance progress toward completion of the common transaction for the particular anchor location.

43. The system of claim 42, wherein the storing means includes a transaction databank, and wherein the anchor ID is not one of the common attributes.

44. The system of claim 42, wherein the assigning means includes a CPU-based circuit programmed to retrieve and associate an ID code that is unique to the each common transaction, wherein the storing means includes a memory databank, and wherein the means for using the constructed transaction-profile attributes includes a CPU-based circuit programmed to audit the common transaction as a function of the plurality of transaction-profile attributes, and wherein the anchor ID is not one of the common attributes.