Transaction data exchange system and approach

• US 20050278255A1
• Filed: 05/03/2005
• Published: 12/15/2005
• Est. Priority Date: 06/09/2004
• Status: Abandoned Application

• Current Assignee: Syncada LLC (US Bancorp)
• Original Assignee: Syncada LLC (US Bancorp)
• Inventors: Sather, William W., Hahn-Carlson, Dean W., Suits, David A.
• Application Number:
  US11/120,629
• Publication Number:
  US 20050278255A1
• Time in Patent Office: Days
• US Class Current: 705/52
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

Transaction processing is facilitated using an approach involving the provision of extracted data to transaction parties. According to an example embodiment of the present invention, transaction information is provided to parties to the transaction as a function of rules relating to the transaction. The rules can be used to assign accounting codes (e.g., any correlation that can be used to identify a transaction or transaction component), which are in turn used to identify information that is to be provided to one or more transaction parties.

Claims

1. A transaction-processing system for processing transaction data for transactions involving merchant offerings among transaction parties, with user profile information for transaction parties including information for associating transaction data with a transaction party and for generating and controlling access to party-specific data, the system comprising:

a computer arrangement adapted, for a particular party to a transaction, to associate transaction data with the particular party as a function of the transaction data and user profile information for the particular party,

generate party-specific data from the transaction data as a function of the particular party'"'"'s user profile information, and

provide access to the generated party-specific data to the particular party as a function of the user profile information.

2. The system of claim 1, wherein the user profile information for the particular party includes configuration information specifying a configuration format of data for which access is to be provided and wherein the computer arrangement is adapted to generate party-specific data by configuring the selected portion of the transaction data for access by the particular party as a function of the configuration information.

3. The system of claim 1, wherein the user profile information for the particular party includes information specifying a timing condition for use in determining when to generate party-specific data for which access is to be provided and wherein the computer system is adapted to generate party-specific data from the transaction data as a function of the timing condition.

4. The system of claim 3, wherein the information specifying a timing condition is indicative of a trigger event and wherein the computer system is adapted to generate party-specific data in response to the occurrence of the trigger event.

5. The system of claim 3, wherein the information specifying a timing condition specifies a calendar-based time and wherein the computer system is adapted to generate party-specific data at the specified calendar-based time.

6. The system of claim 1, wherein the user profile information for the particular party includes information specifying portions of transaction data for which access is to be provided and wherein the computer arrangement is adapted to generate party-specific data by selecting a portion of the transaction data for which access is to be provided as a function of the specified portions in the user profile information for the particular party.

7. The system of claim 1, wherein the computer arrangement is adapted to generate party-specific data from the transaction data for the particular party as a function of accounting codes associated with the transaction data.

8. The system of claim 7, wherein the user profile information for the particular party includes information for assigning accounting codes to transaction data and wherein the computer arrangement is adapted to associate the accounting codes with the transaction data as a function the user profile information and the transaction data.

9. The system of claim 7, wherein the computer arrangement is adapted to provide access to the generated party-specific data by automatically posting a general ledger (GL) account field for the particular party, using the accounting codes to identify a proper GL account field to be posted.

10. The system of claim 1, wherein the user profile information for the particular party includes data transfer protocol information and wherein the computer arrangement is adapted to provide access to the generated party-specific data to the particular party as a function of the user profile information by transferring the generated party-specific data in accordance with the data transfer protocol.

11. The system of claim 1, wherein the user profile information for the particular party includes communication information identifying a location to which the particular party wants transaction data to be sent and wherein the computer arrangement is adapted to provide access to the generated party-specific data to the particular party as a function of the user profile information by sending the party-specific data to the particular party at the identified location.

12. The system of claim 11, wherein the computer arrangement is adapted to make a record of the transmission of the party-specific data to the particular party.

13. The system of claim 11, wherein the computer arrangement is adapted to receive a receipt from the particular party acknowledging the receipt of the party-specific data and to record data indicating that the receipt was received.

14. The system of claim 1, wherein the user profile information for the particular party includes information specifying a third-party recipient of the generated party-specific data and wherein the computer arrangement is adapted to provide access to the generated party-specific data to the specified third party.

15. The system of claim 1, wherein the computer arrangement is adapted to generate a user interface for presentation to the transaction parties, the user interface adapted to

present information for use in authenticating particular transaction parties via user inputs, and

facilitate access to the generated party-specific data via the interface.

16. The system of claim 15, wherein the user interface is adapted to receive configuration inputs from an authenticated transaction party and wherein the computer arrangement is adapted to update profile information for authenticated transaction party in the databank in response to the configuration inputs.

17. The system of claim 1, wherein the computer arrangement is adapted to controllably manage at least one data storage arrangement to store at least one of the user profiles and the generated party-specific data.

18. The system of claim 17, further comprising the at least one data storage arrangement.

19. The system of claim 1, wherein the user profile information for the particular party includes information for auditing the transaction data and wherein the computer arrangement is adapted to

audit the transaction as a function of the user profile information,

generate party-specific data including results of the audit as a function of the particular party'"'"'s user profile information, and

provide access to the auditing results to the particular party as a function of the user profile information.

20. For use with a transaction processing system for processing transaction data for transactions involving merchant offerings among transaction parties, a method for facilitating access to selected transaction data, the method comprising:

generating and sending party-specific data to a transaction party as a function of user profile information specifying a type of transaction data, a timing characteristic identifying a time at which to generate the specified type of transaction data, a location to which the generated transaction data is to be sent and a protocol via which the generated transaction data is to be sent.

21. The method of claim 20, further comprising, after generating and sending the party-specific data:

monitoring incoming acknowledgement communications indicative of the transaction party receiving the generated and sent party-specific data,

in response to not receiving acknowledgement of receipt of the party-specific data, generating an exception indication, and

in response to receiving an acknowledgement of receipt of the party-specific data from the transaction party, recording data indicative of the acknowledgement.

22. A method for processing transaction data for transactions involving merchant offerings among transaction parties, with user profile information for transaction parties including information for associating transaction data with a transaction party and for generating and controlling access to party-specific data, the method comprising, for a particular party to a transaction:

associating transaction data with the particular party as a function of the transaction data and user profile information for the particular party;

generating party-specific data from the transaction data as a function of the particular party'"'"'s user profile information; and

providing access to the generated party-specific data to the particular party as a function of the user profile information.

23. The method of claim 22, further comprising receiving and storing the user profile information for the transaction parties.

24. The method of claim 22, wherein the user profile information includes information for assigning accounting codes to financial data for the particular transaction and wherein generating party-specific data from the transaction data as a function of the particular party'"'"'s user profile information includes generating party-specific data from the transaction data as a function of the information for assigning accounting codes.

25. The method of claim 24, further comprising assigning an accounting codes to the financial data for the particular transaction.

26. The method of claim 22, further comprising configuring the generated user-specific transaction data for use by the transaction party as a function of the transaction party'"'"'s stored profile information.

27. The method of claim 26, wherein configuring the generated user-specific transaction data for use by the transaction party as a function of the transaction party'"'"'s stored profile information includes configuring the user-specific transaction data for posting to a transaction party'"'"'s general ledger chart of accounts.

28. The method of claim 22, wherein generating party-specific data from the transaction data as a function of the particular party'"'"'s user profile information includes generating party-specific data from the transaction data as a function of a timing condition specified in the particular party'"'"'s user profile.

29. The method of claim 28, wherein generating party-specific data from the transaction data as a function of a timing condition specified in the particular party'"'"'s user profile includes generating user-specific data in response to a trigger event defined by the particular party'"'"'s user profile information.

30. The method of claim 28, generating party-specific data from the transaction data as a function of a timing condition specified in the particular party'"'"'s user profile includes generating party-specific data at a calendar-based time specified in the particular party'"'"'s user profile.

31. The method of claim 22, wherein generating party-specific data from the transaction data as a function of the particular party'"'"'s user profile information includes generating party-specific data from a selected type of information in the transaction data as a function of information in the particular party'"'"'s user profile that specifies the type of information.

32. The method of claim 22, wherein providing access to the generated party-specific data to the particular party as a function of the user profile information includes transferring the generated party-specific data in accordance with a data transfer protocol specified in the particular party'"'"'s user profile.

33. The method of claim 22, wherein providing access to the generated party-specific data to the particular party as a function of the user profile information includes transferring the generated party-specific data to a location specified in the particular party'"'"'s user profile.

34. The method of claim 33, further comprising recording data indicating the transfer of the generated party-specific data.