Method and system for providing electronic commerce between incompatible data processing systems

• US 5,794,234 A
• Filed: 08/14/1996
• Issued: 08/11/1998
• Est. Priority Date: 08/14/1996
• Status: Expired due to Term

• Current Assignee: Gula Consulting Limited Liability Company (Intellectual Ventures LLC)
• Original Assignee: EC Company
• Inventors: Church, Craig A, Chaban, Joel, Erbaugh, Mark
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/696,630
• Time in Patent Office: 727 Days
• Field of Search: 707/4, 707/10, 705/35, 705/30, 705/16, 395/200.31, 395/200.43
• US Class Current: 1/1
• CPC Class Codes: G06F 40/151 Transformation
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A system and method that provides the exchange of electronic data interchange (EDI) and electronic fund transfers (EFT) type transactions between trading partners having incompatible accounting database systems is herein provided. The system utilizes a distributed network system connecting one or more client computers representing trading partners and banking institutions to a network server. Each client computer stores data representing EDI and EFT type transactions in an accounting database having a file format that differs from one or more of its associated trading partners. A set of transactions are extracted from an accounting database and converted into a universal file format that is used to exchange data between the various client computers. The universal file format utilizes a freestyle format that accommodates any data element associated with the transactions and is not constrained to a predefined format. The exchange of data between any of the client computers is transmitted through the network server. The network server transmits the data to the appropriate destination client computer as well as perform one or more value added services prescribed by the client computers.

Claims

1. A computing system, comprising:

(a) an accounting data processing system comprising a memory for storing;

an accounting database including a plurality of transactions, each of said transactions including one or more data elements stored in accordance with a first file format associated with said accounting database, and

a plurality of output data files, each of said output data files storing a subset of said transactions in said first format;

(b) a conversion procedure that converts transactions stored in said output data files into a socket table having a universal file format and to convert received transactions stored in said universal file format to said first file format, said universal file format including any data element and incorporating a format that is independent of a predefined structure;

wherein said universal file format comprises a plurality of definition records and a plurality of data records, a subset of said definition records defining one or more data elements associated with each of said transactions and specifying an order for storing said data elements in one or more corresponding data records, each data record including each data element defined in said corresponding definition record in accordance with said order;

(c) a communications link that enables transmission and receipt of one or more transmission files from one or more trading partner computing systems associated with said computing system, wherein the one or more transmission files use said universal file format such that said plurality of definition records and said plurality of data records are transmitted; and

(d) an electronic commerce data processing system comprising a memory for storing;

a transaction database including a plurality of said transactions in said universal file format,

an outgoing transmission repository for storing one or more outgoing transmission files, each of said outgoing transmission files representing a subset of transactions stored in said transaction database, and

an incoming transmission repository for storing one or more incoming transmission files received from said communication link, each of said incoming transmission files representing transactions from one or more of said associated trading partner computing systems;

wherein said accounting data processing system utilizes said electronic commerce data processing system to exchange transactions between one or more of said associated trading partner computing systems; and

wherein said accounting data processing system utilizes said conversion procedure to convert a first subset of said transactions represented in said first format to said universal data format prior to said transmission and to convert a second subset of said transactions received from one or more of said trading partner computing systems represented in said universal data format to said first data format.

2. The system of claim 1,

wherein each of said definition records including a prefix and a plurality of data definition fields, each of said data definition fields including a predetermined number of subfields, each subfield specifying a different characteristic of said data element.

3. The system of claim 1,

wherein said data elements are selected from a set consisting of standard data elements and user-defined data elements.

4. The system of claim 1,

wherein said electronic commerce data processing system further comprising a transaction approval database listing one or more end users associated with said accounting data processing system that are able to approve one or more of said transactions;

and

wherein said electronic commerce data processing system utilizes said transaction approval database to obtain one or more approvals for a subset of said transactions prior to transmitting said transactions to one or more trading partner computing systems.

5. The system of claim 1 wherein said conversion procedure utilizes a conversion file to interpret each of said output data files.

6. The system of claim 1 wherein said transactions represent EDI and EFT type transactions.

7. The system of claim 1,

wherein a third subset of said transactions include data elements corresponding to one or more electronic funds transfers;

wherein said accounting data processing system utilizes one or more associated bank data processing systems to process said electronic funds transfers;

wherein said communications link is coupled to one or more bank interface processing systems, each bank interface processing system receiving one or more of said electronic funds transfer transactions in said first format and converting a subset of said received transactions from said first format to a second format recognizable by an associated bank data processing system associated with said accounting data processing system.

8. The system of claim 7,

wherein said communications link is coupled to a network server that receives each of said transmission files and distributes transactions contained in each received transmission file to one or more destination trading partner computing systems and bank data processing systems.

9. A distributed computing system, comprising:

a plurality of accounting data processing systems, each accounting data processing system having an accounting database storing accounting data in an associated file format, a subset of said accounting databases utilizing an associated file format that is not recognized by one or more of said accounting data processing systems;

a translator that converts accounting data stored in any of said associated file formats into a universal file format and converts accounting data stored in said universal file format to any of said associated file formats, said universal file format including any accounting data and incorporating a format that is independent of a prescribed structures;

wherein said universal file format comprises a plurality of definition records and a plurality of data records, a subset of said definition records defining one or more data elements associated with each of said transactions and specifying an order for storing said data elements in one or more corresponding data records, each data record including each data element defined in said corresponding definition record in accordance with said order; and

a communications network that provides one or more transmission paths between each of said accounting data processing systems, wherein the one or more transmission files use said universal file format such that said plurality of definition records and said plurality of data records are transmitted;

wherein each of said accounting data processing systems utilizes said translator to exchange accounting data between one or more accounting data processing systems.

10. The system of claim 9,

wherein said definition records including a prefix and a plurality of data definition fields, each of said data definition fields including a predetermined number of subfields, each subfield specifying a different characteristic of said data element.

11. The system of claim 9,

wherein said data elements are selected from a group consisting of standard data elements and user-defined data elements.

12. The system of claim 9,

wherein each of said accounting data processing systems utilizing an electronic commerce processing system for transmitting and receiving accounting data between each of said accounting data processing systems, said accounting data transmitted in one or more transmission files utilizing said universal file format;

a network server receiving each of said transmission files and distributing accounting data stored in said received transmission files to one or more destination accounting data processing systems.

13. The system of claim 12,

wherein said accounting data represents EDI and EFT type transactions;

a banking interface processing system coupled to said communication network for receiving one or more of said transmission files, said transmission files including accounting data representing one or more EFT type transactions, said banking interface processing system translating said received accounting data from said universal file format into a second file format for transmission to a bank data processing system in communication with said banking interface processing system.

14. The system of claim 13

wherein each of said electronic commerce processing systems further comprising a transaction approval database listing one or more end users associated with one of said accounting data processing system that are able to approve one or more transactions;

and

wherein said electronic commerce processing system utilizes said transaction approval database to obtain one or more approvals for a subset of said transactions prior to transmitting said transactions to said network server.

15. The system of claim 9 wherein said translator utilizes a conversion file associated with a specified accounting database, said conversion file used to interpret said specified accounting database'"'"'s file format.

16. A computer readable storage medium for use with a computer system associated with an accounting database storing a plurality of transactions in a first file format, each of said transactions including one or more data elements, said computer system coupled to a network in communication with one or more client computers, said medium comprising:

a conversion procedure for translating a subset of said transactions in said first file format to a universal file format and from said universal file format to said first file format, said universal file format used to transmit said transactions to one or more client computers associated with one or more accounting databases having incompatible file formats with said first file format, said universal file format independent of a predefined structure and including any data element, said universal file format including a plurality of definition records and a plurality of data records, a subset of said definition records defining one or more data elements and an order for storing each data element in a corresponding data record, such that said plurality of definition records and said plurality of data records are transmitted.

17. The medium of claim 16 further comprising,

a conversion file for use with said conversion procedure in interpreting said subset of transactions in said first file format.

18. The medium of claim 16,

wherein said header records include a plurality of definition records, each definition record including a prefix and a plurality of data definition fields, each of said data definition fields including a predetermined number of subfields, each subfield specifying a different characteristic of a specific data element.

19. The medium of claim 16,

wherein said data elements are selected from a group consisting of standard data elements and user-defined data elements.

20. A computer-implemented method for providing electronic commerce between a plurality of trading partners, each trading partner associated with a data processing system connected to a communication link and at least one central computing system, each of said data processing systems having an accounting database including a plurality of transactions stored in a file format that is incompatible with one or more other accounting databases, said method comprising the steps of:

extracting one or more transactions stored in one of said accounting databases associated with a specified trading partner, each of said transactions including one or more data elements;

formatting said transactions into a plurality of records associated with one or more outgoing transmission files incorporating a universal file format that stores any data element included in said transactions independent of a predefined structure, each of said transactions destined for one or more trading partners,

wherein said plurality of records comprises a plurality of definition records and a plurality of data records, a subset of said definition records defining one or more data elements associated with each of said transactions and specifying an order for storing said data elements in one or more corresponding data records; and

transmitting each outgoing transmission file to said central computing system for distribution of said transactions in each of said outgoing transmission files to a respective destination trading partners,

wherein at least one outgoing transmission file uses said universal file format such that said plurality of definition records and said plurality of data records are transmitted.

21. The method of claim 20,

wherein each of said definition records include a prefix and a plurality of data definition fields, each of said data definition fields including a predetermined number of subfields, each subfield specifying a different characteristic of said data element.

22. The method of claim 20,

wherein said data elements are selected from a group consisting of standard data elements and user-defined data elements.

23. The method of claim 20 further comprising the step of:

for each trading partner;

receiving one or more incoming transmission files from an associated trading partner in said universal file format, and

converting transactions stored in each of said received incoming transmission files into a file format associated with said accounting database.

24. The method of claim 23,

wherein said extracted transactions are stored in one or more output data files, each output data file including a subset of said extracted transactions in accordance with a prescribed classification;

and

said method further comprising the step of providing one or more input data files containing said converted transactions, each of said input data files including a subset of said converted transactions in accordance with a prescribed classification.

25. The method of claim 20,

wherein each of said trading partners is connected to one or more banking client computer systems through said communication link;

wherein said transactions include one or more EDI and EFT type transactions; and

wherein said transmitting step further distributes said EFT type transactions to one or more of said banking client computer systems.

26. The method of claim 25,

wherein each of said banking client computer systems comprise a bank interface system and a bank data processing system;

said method further comprising the step of

for each banking client computer system;

verifying that each of said received transactions meets one or more approval requirements;

translating said received transactions having obtaining said approval requirements to a second data format associated with said bank data processing system; and

transmitting said translated transactions to said bank data processing system.

27. The method of claim 26,

wherein said bank data processing system is in communication with a banking network including one or more automated clearing houses;

and

wherein said bank data processing system transmits said translated transactions to said banking network.