WO2000043903A1 - Method and system of performing electronic data interchange - Google Patents

Method and system of performing electronic data interchange Download PDF

Info

Publication number
WO2000043903A1
WO2000043903A1 PCT/NZ1999/000224 NZ9900224W WO0043903A1 WO 2000043903 A1 WO2000043903 A1 WO 2000043903A1 NZ 9900224 W NZ9900224 W NZ 9900224W WO 0043903 A1 WO0043903 A1 WO 0043903A1
Authority
WO
WIPO (PCT)
Prior art keywords
business transaction
business
means arranged
data
transactions
Prior art date
Application number
PCT/NZ1999/000224
Other languages
French (fr)
Inventor
Stephen Ross Corkill
Original Assignee
Stephen Ross Corkill
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Stephen Ross Corkill filed Critical Stephen Ross Corkill
Priority to AU19006/00A priority Critical patent/AU1900600A/en
Publication of WO2000043903A1 publication Critical patent/WO2000043903A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the invention relates to a method and system of performing electronic data interchange (EDI) between trading partners.
  • EDI electronic data interchange
  • EPI Electronic Data Interchange
  • one trading partner is a retailer and another trading partner is a supplier
  • an electronic purchase order can flow directly from the retailer's purchasing system into the order management system of the supplier.
  • the supplier in turn may send order shipment information electronically to the retailer and the information will be deposited in the appropriate business application.
  • the retailer's accounts payable can act upon it and a signal to pay can complete the cycle.
  • a difficulty may arise where one trading partner wishes to transfer several business transactions as separate EDI files must be created for each business transaction. Also, where a trading partner receives business transactions from many trading partners, the receiving trading partner receives separate EDI files for each business transaction.
  • a further difficulty may arise where the preferred timing and delivery method for business transactions for one trading partner differ from the preferred timing and delivery method of the trading partner to which business transactions are sent.
  • a supplier may wish to send out invoices with each shipment, sending these invoices by e-mail.
  • the retailer in turn may wish to receive these invoices monthly by floppy disk.
  • the invention relates to an improved method for facilitating EDI between trading partners, and in particular between suppliers and retailers.
  • the invention comprises in one form a computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of receiving an electronic input data file comprising at least one business transaction from a sender, each business transaction addressed to respective recipients; separating the data file into individual business transactions if the data file comprises more than one business transaction; and delivering each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
  • the invention comprises a computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of receiving at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; storing the business transactions in an electronic output file; and delivering the output file to the intended recipient.
  • the invention comprises in another form a system for performing electronic data interchange between trading partners, the system comprising receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
  • the invention comprises a system for performing electronic data interchange between trading partners, the system comprising receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
  • the invention comprises a computer program for performing electronic data interchange between trading partners, the program comprising receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
  • the invention also comprises in a further form a computer program for performing electronic data interchange between trading partners, the program comprising receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
  • Figure 1 is a block diagram illustrating trading partners sending transactions to each other using the invention
  • Figure 2 is a block diagram illustrating one trading partner sending transactions to more than one other trading partner
  • Figure 3 is a block diagram illustrating more than one trad ng partner sending transactions to the same trading partner
  • Figure 4 illustrates a preferred data format for file transfers
  • Figure 5 illustrates part of a preferred data format for an invoice
  • FIG. 5 A illustrates the remainder of the invoice of Figure 5
  • Figure 6 shows a preferred data format for payment advice
  • FIG. 7 is a block diagram of a mail box of the invention.
  • Figure 8 is a block diagram of a front end for processing incoming transactions
  • Figure 9 is a block diagram of a front end for processing outgoing transactions
  • Figure 10 is a flow chart showing formatting of incoming business transactions
  • Figure 1 1 is an example of an XREF transaction class.
  • the invention comprises a method of performing electronic data interchange (EDI) between trading partners, for example a retailer 2 and a supplier 4.
  • EDI electronic data interchange
  • trading partners could include any combination of suppliers, wholesalers, retailers and consumers.
  • Retailer 2 may send to supplier 4 an order for goods electronically. Such an order may be sent as a business transaction using EDI. On receiving the order the supplier 4 may send to the retailer shipping details and/ or an invoice as separate business transactions .or as one combined transaction. On receiving the invoice the retailer may send to the supplier payment details using EDI.
  • the invention provides a method of performing EDI between trading partners for example between retailer 2 and supplier 4 by interposing between the retailer and the supplier an EDI mail centre 6.
  • Retailer 2 sends business transactions intended for supplier 4 to the mail centre 6 instead of sending the transactions directly to the supplier.
  • the method of delivery includes internet e-mail, FTP transfer, or transfer of a file on a floppy disc, depending on the requirements of the retailer.
  • the supplier may send business transactions intended for the retailer to the mail centre instead of sending the transactions directly to the supplier.
  • the delivery method chosen will depend on the requirements of the supplier.
  • Retailer 2 and supplier 4 may receive business transactions from the mail centre 6 using a delivery method chosen depending on the requirements of the retailer and supplier respectively.
  • the delivery method preferences for the business transactions for individual retailers and suppliers may be stored at the mail centre 6.
  • Individual retailers and suppliers may also have preferences as to the timing that business transactions are delivered from mail centre 6. These preferences may also be stored in the mail centre.
  • Sender 8 wishes to send to recipients 10A, 10B, IOC, 10D and 10E, separate business transactions. Rather than sending the business transactions individually the sender 8 may place each of these transactions in a common file. Each transaction is addressed to a particular recipient. The common file is sent to the mail centre 6 as an electronic input data file.
  • the mail centre separates the data file into individual business transactions and stores these individual transactions in a memory. Where the input data file contains only one business transaction, the mail centre does not need to separate the file into individual transactions.
  • the mail centre 6 may then retrieve transactions intended for a particular recipient from the memory and deliver the transactions to the intended recipients.
  • the method of delivery and timing may be adjusted according to the requirements of the trading partner to which the transactions are sent.
  • Senders 8A, 8B, 8C, 8D and 8E may each wish to transfer one business transaction to the same recipient 10.
  • Each sender 8 delivers a business transaction to the mail centre 6, where the transactions are stored in a memory.
  • the mail centre 6 may then retrieve the transactions from the memory and send the transactions to the recipient 10. Rather than send the transactions individually, the mail centre may store each of the transactions intended for the recipient 10 in a single electronic output file. This file may then be delivered to the recipient 10 taking into account the delivery method and timing preferences of the recipient. It will be envisaged that the business transactions could also be stored in a memory and subsequently retrieved from the memory and stored in the output file.
  • Figure 4 illustrates a preferred format for files transferred in accordance with the invention.
  • Files are preferably sent via file transfer (FTP) and messaging based on the internet protocols of Post Office Protocol 3 (POP3) and Simple Mail Transfer Protocol (SMTP).
  • POP3 Post Office Protocol 3
  • SMTP Simple Mail Transfer Protocol
  • Each file transferred in accordance with the format includes a header 12, one or more EDI transactions 14, and a trailer 16.
  • the header 12 comprises the following data fields: EDI field Description header flag Signals that the data following is the header sender ID Where a trading partner sends a file to the mail centre, this will hold the address of the sender. Where the mail centre sends a file to a trading partner, it will hold the address of the mail centre. recipient ID Where a trading partner sends a file to the mail centre, this is left blank. Where the mail centre sends a file to a trading partner, it will hold the address of the trading partner.
  • EDI transfer no This is a unique sequential number used to determine if all transfers have been received. It is generated by the sender or the mail centre. date sent time sent
  • Each file will comprise at least one EDI transaction 14.
  • the preferred fields are as follows:
  • the file will also comprise a trailer 16, the fields of which are illustrated below:
  • Transaction classes for example, the method provides transaction classes for transactions such as invoices, orders and payment details. These transaction classes are available for any trading partner to use.
  • Transaction class definitions generally comprise a class (for example invoice), any sub-classes (for example, invoice header, invoice items) and data items or fields within each sub-class (for example product ID, quantity, and price).
  • Figures 5 and 5A illustrate a typical invoice using the "invoice” transaction class of the invention, while Figure 6 illustrates a typical payment advice using the "payment details" transaction class.
  • the preferred form method provides the facility for trading partners to define their own private transaction classes in addition to the transaction classes described above. These user-defined transaction classes may be available for other trading partners to use, or may alternatively be kept private between sender and recipient.
  • the mail centre has stored in a memory copies of public transaction class definitions. This allows the mail centre to perform functions on business transactions such as formatting or code mapping. The functions of formatting and code mapping are -more particularly described below.
  • the preferred form mail centre does not store definitions of private transaction class definitions. The mail centre simply identifies a business transaction as having a private and unknown transaction class and delivers the business transaction to the intended recipient.
  • Trading partners frequently have existing systems in place for handling EDI business transactions. These systems will generally have preferred or even fixed formats for data items.
  • One difficulty which has arisen in the past is when one trading partner prefers or requires a format which is not compatible with that of another trading partner.
  • the transaction may be formatted where necessary by the mail centre.
  • records and fields may be either fixed or variable length, and the mail centre may alter the format of these records and fields between fixed and variable length.
  • the formatting functions are performed by a front end as will be more particularly described with reference to Figures 7, 8 and 9.
  • the preferred form mail centre 6 delivers business transactions to and receives business transactions from an EDI mail box 18 of trading partner 20.
  • a front end 22 may operate to convert the format of business transactions in mail box 18 to a format compatible with the format of the system of trading partner 20.
  • the front end 22 may alternatively or additionally operate to convert the format of business transactions sent from the system of trading partner 20 to a form compatible with mail box 18.
  • Another formatting function of the front end could be performed on field delimiters when using variable length fields. This function may be defined for the individual trading partners or may be defined for a particular transaction class.
  • Figure 10 illustrates how field delimiters are processed in a business transaction.
  • the front end first establishes whether or not the incoming transaction class has field delimiters (24), whether or not these are the same as the delimiters of the trading partner (26) and whether or not the trading partner uses field delimiters for that transaction class (28). Depending on these criteria, delimiters may be added (30), removed (32), or changed (34). In some cases no action will be taken (36).
  • a further formatting function of the invention could be the alteration of field formats, for example dates, money and numbers. Certain field types within business transactions will be formatted differently by different traders. Instead of insisting that EDI transfer conform to a standard format, the front end allows for formatting of the fields during sending and receipt of business transactions. Field formatting may be performed, for example, when transactions are sent to and from mail boxes.
  • a further feature of the invention involves code mapping.
  • Trading partners involved in business transactions seldom use the same codes to identify a business entity. For example, a supplier will have its own customer code whereas a customer will use a different code as a supplier code.
  • Business transactions sent electronically frequently have descriptions of individual codes sent with each transaction. These descriptions enable the codes to be identified by the recipient.
  • the invention enables each trader to use its own codes which are mapped to the codes used by other traders, and enables traders to set up and even exchange mapping function data for new codes.
  • This exchange of mapping function data may either be performed using a special transaction class, or may be performed online at the mail centre.
  • FIG. 11 An example of a special transaction class (XREF) is shown in Figure 11.
  • One trader the originator
  • This business transaction signals that there is a new code being used.
  • the transaction may include business identifier, transaction item, code, and/or description for Doth originator and recipient.
  • the mail centre receives from the originator the XREF transaction, a message is sent to the intended recipient that a new code has been received.
  • the recipient may then use an online mail centre function to finalise the mapping, for example to enter further descriptions.

Abstract

The invention provides a computer implemented method of performing electronic data interchange between trading partners comprising the steps of receiving an electronic input data file comprising at least one business transaction from a sender, separating the data file into individual business transactions if the data file comprises more than one business transaction, and delivering each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient. The invention also provides a computer implemented method of delivering a single output file to an intended recipient, the output file comprising one or more business transactions. The invention also provides a related system and computer program.

Description

METHOD AND SYSTEM OF PERFORMING ELECTRONIC DATA INTERCHANGE
FIELD OF INVENTION
The invention relates to a method and system of performing electronic data interchange (EDI) between trading partners.
BACKGROUND
Electronic Data Interchange (EDI) is the transmission between trading partners of information in standard, computer-readable format. It includes electronic order placement, electronic shipping notification, electronic invoicing, and many other business transactions in which it is more efficient to use computer-implemented rather than manual transfer of information.
Where one trading partner is a retailer and another trading partner is a supplier, for example, an electronic purchase order can flow directly from the retailer's purchasing system into the order management system of the supplier. The supplier in turn may send order shipment information electronically to the retailer and the information will be deposited in the appropriate business application. Once an electronic invoice is sent by the supplier, the retailer's accounts payable can act upon it and a signal to pay can complete the cycle.
In traditional EDI systems a difficulty may arise where one trading partner wishes to transfer several business transactions as separate EDI files must be created for each business transaction. Also, where a trading partner receives business transactions from many trading partners, the receiving trading partner receives separate EDI files for each business transaction.
A further difficulty may arise where the preferred timing and delivery method for business transactions for one trading partner differ from the preferred timing and delivery method of the trading partner to which business transactions are sent. For example, a supplier may wish to send out invoices with each shipment, sending these invoices by e-mail. The retailer in turn may wish to receive these invoices monthly by floppy disk.
The invention relates to an improved method for facilitating EDI between trading partners, and in particular between suppliers and retailers. SUMMARY OF INVENTION
In broad terms the invention comprises in one form a computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of receiving an electronic input data file comprising at least one business transaction from a sender, each business transaction addressed to respective recipients; separating the data file into individual business transactions if the data file comprises more than one business transaction; and delivering each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
In another form the invention comprises a computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of receiving at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; storing the business transactions in an electronic output file; and delivering the output file to the intended recipient.
The invention comprises in another form a system for performing electronic data interchange between trading partners, the system comprising receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
In another form the invention comprises a system for performing electronic data interchange between trading partners, the system comprising receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
In a further form the invention comprises a computer program for performing electronic data interchange between trading partners, the program comprising receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
The invention also comprises in a further form a computer program for performing electronic data interchange between trading partners, the program comprising receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
BRIEF DESCRIPTION OF FIGURES
Preferred forms of the method will now be described by way of example and without intending to be limiting, with reference to the accompanying figures in which:
Figure 1 is a block diagram illustrating trading partners sending transactions to each other using the invention;
Figure 2 is a block diagram illustrating one trading partner sending transactions to more than one other trading partner;
Figure 3 is a block diagram illustrating more than one trad ng partner sending transactions to the same trading partner;
Figure 4 illustrates a preferred data format for file transfers;
Figure 5 illustrates part of a preferred data format for an invoice;
Figure 5 A illustrates the remainder of the invoice of Figure 5;
Figure 6 shows a preferred data format for payment advice;
Figure 7 is a block diagram of a mail box of the invention;
Figure 8 is a block diagram of a front end for processing incoming transactions;
Figure 9 is a block diagram of a front end for processing outgoing transactions; Figure 10 is a flow chart showing formatting of incoming business transactions; and
Figure 1 1 is an example of an XREF transaction class.
DETAILED DESCRIPTION OF PREFERRED FORMS
As shown in Figure 1, the invention comprises a method of performing electronic data interchange (EDI) between trading partners, for example a retailer 2 and a supplier 4. It will be appreciated that the trading partners could include any combination of suppliers, wholesalers, retailers and consumers.
Retailer 2 may send to supplier 4 an order for goods electronically. Such an order may be sent as a business transaction using EDI. On receiving the order the supplier 4 may send to the retailer shipping details and/ or an invoice as separate business transactions .or as one combined transaction. On receiving the invoice the retailer may send to the supplier payment details using EDI.
As shown in Figure 1 , the invention provides a method of performing EDI between trading partners for example between retailer 2 and supplier 4 by interposing between the retailer and the supplier an EDI mail centre 6. Retailer 2 sends business transactions intended for supplier 4 to the mail centre 6 instead of sending the transactions directly to the supplier. The method of delivery includes internet e-mail, FTP transfer, or transfer of a file on a floppy disc, depending on the requirements of the retailer. Similarly the supplier may send business transactions intended for the retailer to the mail centre instead of sending the transactions directly to the supplier. The delivery method chosen will depend on the requirements of the supplier.
Retailer 2 and supplier 4 may receive business transactions from the mail centre 6 using a delivery method chosen depending on the requirements of the retailer and supplier respectively. The delivery method preferences for the business transactions for individual retailers and suppliers may be stored at the mail centre 6.
Individual retailers and suppliers may also have preferences as to the timing that business transactions are delivered from mail centre 6. These preferences may also be stored in the mail centre.
One difficulty with traditional EDI systems is where one trading partner wishes to transfer several business transactions to another trading partner, as each EDI transaction requires a separate file. Figure 2 illustrates how this situation is addressed by the invention.
Sender 8 wishes to send to recipients 10A, 10B, IOC, 10D and 10E, separate business transactions. Rather than sending the business transactions individually the sender 8 may place each of these transactions in a common file. Each transaction is addressed to a particular recipient. The common file is sent to the mail centre 6 as an electronic input data file.
Where the input file contains more than one business transaction, the mail centre separates the data file into individual business transactions and stores these individual transactions in a memory. Where the input data file contains only one business transaction, the mail centre does not need to separate the file into individual transactions.
The mail centre 6 may then retrieve transactions intended for a particular recipient from the memory and deliver the transactions to the intended recipients. The method of delivery and timing may be adjusted according to the requirements of the trading partner to which the transactions are sent.
A further feature of the invention is illustrated in Figure 3. Senders 8A, 8B, 8C, 8D and 8E may each wish to transfer one business transaction to the same recipient 10. Each sender 8 delivers a business transaction to the mail centre 6, where the transactions are stored in a memory.
The mail centre 6 may then retrieve the transactions from the memory and send the transactions to the recipient 10. Rather than send the transactions individually, the mail centre may store each of the transactions intended for the recipient 10 in a single electronic output file. This file may then be delivered to the recipient 10 taking into account the delivery method and timing preferences of the recipient. It will be envisaged that the business transactions could also be stored in a memory and subsequently retrieved from the memory and stored in the output file.
Figure 4 illustrates a preferred format for files transferred in accordance with the invention. Files are preferably sent via file transfer (FTP) and messaging based on the internet protocols of Post Office Protocol 3 (POP3) and Simple Mail Transfer Protocol (SMTP). The invention integrating these protocols allows files to be transferred over the internet.
Each file transferred in accordance with the format includes a header 12, one or more EDI transactions 14, and a trailer 16. The header 12 comprises the following data fields: EDI field Description header flag Signals that the data following is the header sender ID Where a trading partner sends a file to the mail centre, this will hold the address of the sender. Where the mail centre sends a file to a trading partner, it will hold the address of the mail centre. recipient ID Where a trading partner sends a file to the mail centre, this is left blank. Where the mail centre sends a file to a trading partner, it will hold the address of the trading partner.
EDI transfer no. This is a unique sequential number used to determine if all transfers have been received. It is generated by the sender or the mail centre. date sent time sent
Each file will comprise at least one EDI transaction 14. The preferred fields are as follows:
EDI field Description detail flag Signals that the following data is a transaction detail sender ID This may be a duplicate of the sender ID in the header receiver ID This will be the ultimate recipient of the transaction EDI trx class Transfer classes are more fully described below EDI trx sub-class trx class version no. business transaction
The file will also comprise a trailer 16, the fields of which are illustrated below:
EDI field Description trailer flag Signals that the following data is a trailer no. of transactions Optional no. of transaction classes Optional
The method provides a set of standard predefined formats for business transactions, called "transaction classes". For example, the method provides transaction classes for transactions such as invoices, orders and payment details. These transaction classes are available for any trading partner to use. Transaction class definitions generally comprise a class (for example invoice), any sub-classes (for example, invoice header, invoice items) and data items or fields within each sub-class (for example product ID, quantity, and price).
Figures 5 and 5A illustrate a typical invoice using the "invoice" transaction class of the invention, while Figure 6 illustrates a typical payment advice using the "payment details" transaction class.
The preferred form method provides the facility for trading partners to define their own private transaction classes in addition to the transaction classes described above. These user-defined transaction classes may be available for other trading partners to use, or may alternatively be kept private between sender and recipient.
The mail centre has stored in a memory copies of public transaction class definitions. This allows the mail centre to perform functions on business transactions such as formatting or code mapping. The functions of formatting and code mapping are -more particularly described below. The preferred form mail centre does not store definitions of private transaction class definitions. The mail centre simply identifies a business transaction as having a private and unknown transaction class and delivers the business transaction to the intended recipient.
Trading partners frequently have existing systems in place for handling EDI business transactions. These systems will generally have preferred or even fixed formats for data items. One difficulty which has arisen in the past is when one trading partner prefers or requires a format which is not compatible with that of another trading partner.
Where a business transaction having a public transaction class is sent to the mail centre, the transaction may be formatted where necessary by the mail centre. For example, records and fields may be either fixed or variable length, and the mail centre may alter the format of these records and fields between fixed and variable length. Preferably the formatting functions are performed by a front end as will be more particularly described with reference to Figures 7, 8 and 9.
As shown in Figure 7, the preferred form mail centre 6 delivers business transactions to and receives business transactions from an EDI mail box 18 of trading partner 20. As shown in Figure 8, a front end 22 may operate to convert the format of business transactions in mail box 18 to a format compatible with the format of the system of trading partner 20. As shown in Figure 9, the front end 22 may alternatively or additionally operate to convert the format of business transactions sent from the system of trading partner 20 to a form compatible with mail box 18. Another formatting function of the front end could be performed on field delimiters when using variable length fields. This function may be defined for the individual trading partners or may be defined for a particular transaction class. Figure 10 illustrates how field delimiters are processed in a business transaction.
The front end first establishes whether or not the incoming transaction class has field delimiters (24), whether or not these are the same as the delimiters of the trading partner (26) and whether or not the trading partner uses field delimiters for that transaction class (28). Depending on these criteria, delimiters may be added (30), removed (32), or changed (34). In some cases no action will be taken (36).
A further formatting function of the invention could be the alteration of field formats, for example dates, money and numbers. Certain field types within business transactions will be formatted differently by different traders. Instead of insisting that EDI transfer conform to a standard format, the front end allows for formatting of the fields during sending and receipt of business transactions. Field formatting may be performed, for example, when transactions are sent to and from mail boxes.
A further feature of the invention involves code mapping. Trading partners involved in business transactions seldom use the same codes to identify a business entity. For example, a supplier will have its own customer code whereas a customer will use a different code as a supplier code. Business transactions sent electronically frequently have descriptions of individual codes sent with each transaction. These descriptions enable the codes to be identified by the recipient.
The invention enables each trader to use its own codes which are mapped to the codes used by other traders, and enables traders to set up and even exchange mapping function data for new codes. This exchange of mapping function data may either be performed using a special transaction class, or may be performed online at the mail centre.
An example of a special transaction class (XREF) is shown in Figure 11. One trader (the originator) will send to the mail centre an EDI business transaction of the class XREF. This business transaction signals that there is a new code being used. The transaction may include business identifier, transaction item, code, and/or description for Doth originator and recipient.
Once the mail centre receives from the originator the XREF transaction, a message is sent to the intended recipient that a new code has been received. The recipient may then use an online mail centre function to finalise the mapping, for example to enter further descriptions.
It will be appreciated that security of the system may be enhanced by encrypting the data portion of each business transaction sent between trading partners and the mail centre. In this situation both sender and receiver should have the facility to encrypt and decrypt files, either using their own systems or using standard features within the mail centre.
The foregoing describes the invention including preferred forms thereof. Alterations and modifications as will be obvious to those skilled in the art are intended to be incorporated within the scope hereof, as defined in the accompanying claims.

Claims

1. A computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of: receiving an electronic input data file comprising at least one business transaction from a sender, each business transaction addressed to respective recipients; separating the data file into individual business transactions if the data file comprises more than one business transaction; and delivering each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
2. A computer implemented method as claimed in claim 1 further comprising the steps of storing at least one of the business transactions from the separated data file in a memory; and retrieving the at least one business transaction from the memory for delivery to the intended recipient.
3. A computer implemented method of performing electronic data interchange between trading partners, the method comprising the steps of: receiving at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; storing the business transactions in an electronic output file; and delivering the output file to the intended recipient.
4. A computer implemented method as claimed in claim 3 further comprising the steps of storing at least one of the business transactions in a memory and retrieving the business transactions from the memory for storing in the output file.
5. A computer implemented method as claimed in any one of the preceding claims wherein at least one business transaction comprises data in at least one public predefined format, the method further comprising the step of delivering to the intended recipient the business transaction and/ or output data file based on both the individual requirements of the recipient and the format of the business transaction.
6. A computer implemented method as claimed in any one of the preceding claims wherein at least one business transaction comprises data in at least one format defined by one or more of the trading partners.
7. A computer implemented method as claimed in claim 5 or claim 6 further comprising the step of translating data in a first format in the at least one business transaction to data in a second format.
8. A system for performing electronic data interchange between trading partners, the system comprising: receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
9. A system as claimed in claim 8 further comprising a memory in which is stored at least one of the business transactions from the separated data file; and retrieval means arranged to retrieve the at least one business transaction from the memory for delivery to the intended recipient.
10. A system for performing electronic data interchange between trading partners, the system comprising: receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
11. A system as claimed in claim 10 further comprising a memory arranged to store at least one of the business transactions; and retrieval means arranged to retrieve the business transactions from the memory for storing in the output file.
12. A system as claimed in any one of claims 8 to 11 wherein at least one business transaction comprises data in at least one public predefined format, the system further comprising delivery means arranged to deliver to the intended recipient the business transaction and/or output data file based on both the individual requirements of the recipient and the format of the business transaction.
13. A system as claimed in any one of claims 8 to 12 wherein at least one business transaction comprises data in at least one format defined by one or more of the trading partners.
14. A system as claimed in claim 12 or claim 13 further comprising translation means arranged to translate data in a first format in the at least one business transaction to data in a second format.
15. A computer program for performing electronic data interchange between trading partners, the program comprising: receiving means arranged to receive an electronic input data file wherein the input data file comprises at least one business transaction from a sender, each business transaction addressed to respective recipients; separating means arranged to separate the data file into individual business transactions if the data file comprises more than one business transaction; and delivery means arranged to deliver each business transaction to the intended recipient of that business transaction based on the individual requirements of the recipient.
16. A program as claimed in claim 15 further comprising means arranged to store at least one of the business transactions from the separated data file in a memory; and retrieval means arranged to retrieve the at least one business transaction from the memory for delivery to the intended recipient.
17. A computer program for performing electronic data interchange between trading partners, the program comprising: receiving means arranged to receive at least one business transaction from respective senders based on the individual requirements of each sender, each business transaction addressed to a common recipient; means arranged to store the business transactions in an electronic output file; and delivery means arranged to deliver the output file to the intended recipient.
18. A program as claimed in claim 17 further comprising means arranged to store at least one of the business transactions in a memory; and retrieval means arranged to retrieve the business transactions from the memory for storing in the output file.
19. A program as claimed in any one of claims 15 to 18 wherein at least one business transaction comprises data in at least one public predefined format, the program further comprising delivery means arranged to deliver to the intended recipient the business transaction and/ or output data file based on both the individual requirements of the recipient and the format of the business transaction.
20. A program as claimed in any one of claims 15 to 19 wherein at least one business transaction comprises data in at least one format defined by one or more of the trading partners.
21. A program as claimed in claim 19 or claim 20 further comprising translation means arranged to translate data in a first format in the at least one business transaction to data in a second format.
22. A program as claimed in any one of claims 15 to 21 embodied on a computer readable medium.
PCT/NZ1999/000224 1999-01-22 1999-12-22 Method and system of performing electronic data interchange WO2000043903A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU19006/00A AU1900600A (en) 1999-01-22 1999-12-22 Method and system of performing electronic data interchange

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NZ333888 1999-01-22
NZ33388899 1999-01-22

Publications (1)

Publication Number Publication Date
WO2000043903A1 true WO2000043903A1 (en) 2000-07-27

Family

ID=19927118

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/NZ1999/000224 WO2000043903A1 (en) 1999-01-22 1999-12-22 Method and system of performing electronic data interchange

Country Status (2)

Country Link
AU (1) AU1900600A (en)
WO (1) WO2000043903A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1100032A2 (en) * 1999-11-12 2001-05-16 Nortel Networks Limited Method implemented on a wireless pre-paid platform of business-to-business transaction processing and billing.
KR20010099047A (en) * 2001-08-17 2001-11-09 전효진 Automated system for exporting documents and method for managing document and recording medium thereof
KR20020069590A (en) * 2001-02-26 2002-09-05 글로팩스코리아(주) a management system for forwarding input or output goods and method thereof
KR100407397B1 (en) * 2000-09-08 2003-11-28 주식회사 한국무역정보통신 Trade form electronic filing document and trade automation system by electronic data interchange
KR100443912B1 (en) * 2002-01-31 2004-08-09 에프피에스코리아(주) Business method for providing freight forwarding services by having data jointly with trading companies and computer readable medium having stored thereon computer executable instruction for performing the same

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5205977A (en) * 1989-08-31 1993-04-27 Amp Incorporated Method of securing an insert in a shell
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4951196A (en) * 1988-05-04 1990-08-21 Supply Tech, Inc. Method and apparatus for electronic data interchange
US5205977A (en) * 1989-08-31 1993-04-27 Amp Incorporated Method of securing an insert in a shell
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1100032A2 (en) * 1999-11-12 2001-05-16 Nortel Networks Limited Method implemented on a wireless pre-paid platform of business-to-business transaction processing and billing.
EP1100032A3 (en) * 1999-11-12 2002-02-13 Nortel Networks Limited Method implemented on a wireless pre-paid platform of business-to-business transaction processing and billing.
KR100407397B1 (en) * 2000-09-08 2003-11-28 주식회사 한국무역정보통신 Trade form electronic filing document and trade automation system by electronic data interchange
KR20020069590A (en) * 2001-02-26 2002-09-05 글로팩스코리아(주) a management system for forwarding input or output goods and method thereof
KR20010099047A (en) * 2001-08-17 2001-11-09 전효진 Automated system for exporting documents and method for managing document and recording medium thereof
KR100443912B1 (en) * 2002-01-31 2004-08-09 에프피에스코리아(주) Business method for providing freight forwarding services by having data jointly with trading companies and computer readable medium having stored thereon computer executable instruction for performing the same

Also Published As

Publication number Publication date
AU1900600A (en) 2000-08-07

Similar Documents

Publication Publication Date Title
US6934691B1 (en) System and method for managing mail/bills through a central location
US7966192B2 (en) Method and apparatus for processing electronic dispute data
US7949600B1 (en) Method for facilitating payment of a computerized transaction
US6151588A (en) Full service trade system
US20080215354A1 (en) Method and System for Exchanging Business Documents
AU744159B2 (en) System for supplying automatic status updates using electronic mail
US8423437B2 (en) Certified email system and method
TW464814B (en) A method and system for bill presentment and payment
US20010025262A1 (en) Computer apparatus for monitoring and updating accountancy records
US20150052076A1 (en) System, method, and article of manufacture for filtering mail items based on recipient preference
US5331543A (en) Business monitoring system and method
WO2004100027A2 (en) Point-of-sale electronic receipt generation
WO1997002539A1 (en) Electronic money sending system
US20020143674A1 (en) Invoice distribution method and apparatus
JP2000357155A (en) Message retrieval system
EP1617363A1 (en) Integrated mail-piece tracking and on-line document viewing
WO2000043903A1 (en) Method and system of performing electronic data interchange
US20040167819A1 (en) Gift notification method
JP2002049744A (en) Mail system
JP7135232B1 (en) Fudo Pharmaceutical Matching System, Fudo Pharmaceutical Matching Method, Fudo Pharmaceutical Matching Server and Program
JP3368571B2 (en) Electronic remittance system, relay system, remittance method
US7974882B1 (en) Method and system for creating a comprehensive undeliverable-as-addressed database for the improvement of the accuracy of marketing mailing lists
US7280982B1 (en) System and method for a fee address system
JP2001283116A (en) Device and method for processing money reception and recording medium for storing money reception processing program
KR20180119441A (en) Method for automatic registering product information on the online shopping-mall

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 506340

Country of ref document: NZ

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase