WikiPatents - Community Patent Review
Create Free Account  |  License or Sell Your Patent  |  WikiPatents Marketplace  |  WikiPatents Blog
Username:  Password:  
    
Advanced Search
Automated back office transaction method and system    
United States Patent6167378   
Link to this pagehttp://www.wikipatents.com/6167378.html
Inventor(s)Webber, Jr.; Donald Gary (Mt. Baldy, CA)
AbstractA method and system provides for digital automation of the transaction space. Digital contracts are programmed to reflect the intended activity or operations of the parties in connection with their purpose. Those contracts can be drafted, ratified and stored by parties situated at any global location, so that the contracts operate on a centralized platform, whereby computational activity is initiated based on the occurrence of events independent of the system. Briefly, the device provides the framework within which contracts operate when triggered by events in order to automatically perform their intended and programmed purpose. In part, the contracts and the instructions regarding functions contained within contracts are linked based on their common purpose, that is, a specific product or service. Dissemination of instructions and data is automated and the means for dissemination and communication between the system and the parties can be as simple as an internet connection, as well as other connections. The method and system make it possible to culminate with automatic payment to the parties.
   














 Title Information Submit all comments and votes
 
Patent Text Patent PDF Print Page Summary File History
Plain text PDF images Print Summary File History
Inventor     Webber, Jr.; Donald Gary (Mt. Baldy, CA)
Owner/Assignee    
Patent assignment
All assignments
Publication Date     December 26, 2000
Application Number     08/792,925
PAIR File History     Application Data   Transaction History
Image File Wrapper   Patent Term   Fees
Litigation
Filing Date     January 21, 1997
US Classification     705/8 705/7
Int'l Classification    
Examiner     Voeltz; Emanuel Todd
Assistant Examiner     Kalinowski; Alexander
Attorney/Law Firm     Foley & Lardner
Address
Parent Case    
Priority Data    
USPTO Field of Search     705/1 705/26 705/27 705/8 705/10 705/7 707/200 707/500 707/104
Patent Tags     automated back office transaction
   
Enter a comma (,) or semicolon (;) between multiple tag words/phrases.
Describe this patent:
 Amusing   
 Clever   
 Complex   
 Efficient   
 Historic   
 Important   
 Innovative   
 Interesting   
 Practical   
 Simple   
[no votes]
Patent WIKI

Share information and news about this patent, including information and news about the technology, inventors, company, ligation and licensing.

 References Submit all comments and votes
 
*references marked with an asterisk below are user-added references
 U.S. References
 
Add a new US reference:  
ReferenceRelevancyCommentsReferenceRelevancyComments
5974395
Bellini et al.

Oct,1999

[0 after 0 votes]
5694551
Doyle et al.

Dec,1997

[0 after 0 votes]
5677955
Doggett et al.

Oct,1997

[0 after 0 votes]
5666493
Wojcik et al.

Sep,1997

[0 after 0 votes]
5634016
Steadham, Jr. et al.

May,1997

[0 after 0 votes]
5434394
Roach

Jul,1995

[0 after 0 votes]
5406475
Kouchi et al.

Apr,1995

[0 after 0 votes]
5362948
Morimoto

Nov,1994

[0 after 0 votes]
5319542
King, Jr. et al.

Jun,1994

[0 after 0 votes]
5310997
Roach et al.

May,1994

[0 after 0 votes]
5287268
McCarthy

Feb,1994

[0 after 0 votes]
5272623
Grubb et al.

Dec,1993

[0 after 0 votes]
5239462
Jones et al.

Aug,1993

[0 after 0 votes]
5163091
Graziano et al.

Nov,1992

[0 after 0 votes]
5031214
Dziewit

Jul,1991

[0 after 0 votes]
4920488
Filley

Apr,1990

[0 after 0 votes]
4912309
Danielson et al.

Mar,1990

[0 after 0 votes]
4887208
Schneider et al.

Dec,1989

[0 after 0 votes]
4799156
Shavit et al.

Jan,1989

[0 after 0 votes]
 Foreign References
 Other References
 Market Review Submit all comments and votes
   
Market Size
Estimate the gross annual revenues of the relevant market sector:
> $10B
$5B - $10B
$2B - $5B
$500M - $2B
$100M - $500M
$10M - $100M
$1M - $10M
$500K - $1M
$100K - $500K
< $100K
[No votes]
$0
 
$0   $2.5B   $5B   $7.5B   $10B
Market Share
Estimate the percentage of the relevant market sector this invention will capture:
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Reasonable Royalty
What percentage of gross sales should the inventor or assignee be paid?
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Public's "Guesstimation" of Royalty Value
Market SizeN/A[No votes]
xMarket ShareN/A[No votes]
xReasonable RoyaltyN/A[No votes]

N/A

License Availablity
If you are NOT the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
License Availablity
If you ARE the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
Competitive Advantage
Does this invention have a significant competitive advantage over similar technologies?
Yes

No



[No votes]
Most helpful competitive advantage comment
[No comments]

Commercial Alternatives
Are there viable commercial alternatives for this invention?
Yes

No



[No votes]
Most helpful commercial alternative comment
[No comments]

 Technical Review Submit all comments and votes
 Claims Submit all comments and votes
 


What is claimed is:

1. A method for digital automation of supply chains in a vertical marketplace, comprising:

(a) generating, in a computerized system, at least one non-ratified contract for a transaction in one supply chain of the supply chains, wherein the non-ratified contract has a plurality of terms;

(b) ratifying the contract and storing the contract as a ratified contract in a database in the computerized system, said contract identifying the contracting parties, the goods or services, and the payment details;

(c) checking, in the computerized system, whether at least one term of the plurality of terms in the ratified contract indicates that at least one next contract is necessary for a next transaction in the supply chain, and if so, automatically performing steps (a) and (b) and (c) for the at least one next contract;

(d) storing, in the database, links between each ratified contract and at least one next contract that relates to the same goods or services and that relates to parties vertically linked in the distribution chain for goods and services;

(e) in response to marketplace events relating to sales of, deliveries of, or payments for goods and services, triggering the calculation, based upon the payment details specified in the related contracts, of the payable due to and from each of the parties; and

(f) following such an event, and in accordance with the contracts, executing payments directly between the parties of the net amount due to and from each party such that gross payments need not pass through one party to the next.

2. The method of claim 1, where step (f) is delayed when one of the terms in the ratified contract or non-ratified contract indicates a delay before the execution of payments.

3. The method of claim 1, wherein a first performance of step (a) is initiated by transmitting a request for a product from a customer to a seller.

4. The method of claim 1, wherein one of the terms requires delivery of a product from a first entity to a second entity, further comprising the step of creating and storing a record, when the product is provided, with information that the product is delivered.

5. The method of claim 1, further comprising the step of providing a digital template of the contract prior to step (a).

6. The method of claim 1, wherein the generating step further comprises forwarding the non-ratified contract from a first entity to a second entity specified in the non-ratified contract, and the ratifying step includes digital acceptance by the second entity.

7. The method of claim 1, wherein a unique identifier for the supply chain is associated with each contract and each transaction.

8. The method of claim 1, further comprising the step of receiving, in the computerized system, a request to view a portion of the database, via a communication link.

9. The method of claim 1, wherein the terms include any required time for performance, instructions for electronic banking, instructions for communications, and any transactional calculations.

10. The method of claim 1, wherein the ratifying step is via a digital signature.

11. A method for digital automation of supply chains in a vertical marketplace, comprising:

(a) providing a digital template of a non-ratified contract;

(b) generating, in a computerized system, at least one non-ratified contract for a transaction in one supply chain of the supply chains, wherein the non-ratified contract has a plurality of terms, and automatically forwarding the non-ratified contract from a first entity to a second entity specified in the non-ratified contract;

(c) ratifying the contract by digital acceptance by the second entity and storing the contract as a ratified contract in a database in the computerized system, said contract identifying the contracting parties, the goods or services, and the payment details;

(d) checking, in the computerized system, whether at least one term of the plurality of terms in the ratified contract indicates that at least one next contract is necessary for a next transaction in the supply chain, and if so, automatically performing steps (b) and (c) and (d) for the at least one next contract that relates to the same goods or services and that relates to parties vertically linked in the distribution chain for goods and services;

(e) in response to marketplace events relating to sales of, deliveries of, or payments for goods and services, triggering the calculation, based upon the payment details specified in the related contracts, of the payable due to and from each of the parties; and

(f) following such an event, and in accordance with the contracts, executing payments directly between the parties of the net amount due to and from each party such that gross payments need not pass through one party to the next;

(g) storing, in the database, links between each ratified contract and at least one next contract;

(h) associating a unique identifier for the supply chain with each contract and each transaction;

(i) wherein a first performance of step (b) is initiated by transmitting a request for a product from a customer to a seller;

(j) wherein one of the terms requires delivery of a product from one entity to an other entity, further comprising the steps of creating and storing a record, when the product has been provided, with information that the product is delivered; and calculating payables and transferring payment from each second entity to each first entity; and

(k) wherein the database stores information on amounts due and payable by a plurality of entities including the first entity and the second entity, and wherein the calculating step includes offsetting amounts due between the plurality of entities.

12. The method of claim 11, wherein the terms include any required time for performance, instructions for electronic banking, instructions for communications, and any transactional calculations.

13. The method of claim 11, wherein the ratifying step is via a digital signature.

14. A system for digital automation of supply chains in a vertical marketplace, each of the supply chains having a plurality of transactions between a plurality of parties including a buyer, a seller and a supplier, including at least one transaction between the buyer and the seller, and a transaction between the seller and the supplier, comprising:

(a) storage in a database for at least one non-ratified contract corresponding to each transaction of the plurality of transactions in one of the supply chains, wherein each non-ratified contract has a plurality of terms, and wherein each non-ratified contract is approved by one of the parties;

(b) storage in the database for at least one ratified contract corresponding to each of the non-ratified contracts, wherein the ratified contract is approved by an other one of the parties, said contract identifying the contracting parties, the goods or services, and the payment details;

(c) a plurality of stored links between ratified contracts, including at least one link between the ratified contracts for the transaction in the supply chain between the buyer and the seller and the ratified contract for the transaction in the supply chain between the seller and the supplier that relate to the same goods or services in the distribution chain;

(d) a computer implemented calculation mechanism which, in response to triggering marketplace events relating to sales of, deliveries of, or payments for goods and services, calculates, based upon the payment details specified in the related contracts, the payable due to and from each of the parties; and

(e) a computer-implemented payment mechanism which, following such an event, and in accordance with the contracts, executes payments directly between the parties of the net amount due to and from each party such that gross payments need not pass through one party to the next.

15. The system of claim 14, wherein one of the terms in the ratified contract or non-ratified contract indicates a delay before the execution of payments.

16. The system of claim 14, further comprising a digital template of the non-ratified contract.

17. The system of claim 14, wherein a unique identifier for the supply chain is associated with each contract.

18. The system of claim 14, wherein the computerized system includes links between ratified and non-ratified contracts in the specified portion, and the links are traversable responsive to a received request to view a specified portion of the database.

19. The system of claim 14, wherein the terms include any of required time for performance, instructions for electronic banking, instructions for communications, and any transactional calculations.

20. The system of claim 14, wherein one of the terms indicates delivery of a product from a first entity to a second entity is required, and wherein the database includes storage for records with information that the product is delivered, when the product is delivered.

21. The system of claim 20, wherein the database includes storage for records of calculated payables for payment from the second entity to the first entity.

22. The system of claim 21, wherein the database includes storage for records of information on amounts due and amounts payable by a plurality of entities including the first entity and the second entity, and amounts due between the plurality of entities are offset in the stored calculated payables.

23. A method for using an electronic data processing system to manage the accounting of parties carrying out common transactions in a vertical marketplace, said method including the following steps:

establishing on the system digital representations of contracts between the parties, each contract identifying the contracting parties, the goods or services, and the payment details;

within the system, establishing digital linkages between contracts that relate to the same goods or services and that relate to parties vertically linked in the distribution chain for those goods and services;

in response to marketplace events relating to sales of, deliveries of, or payments for goods and services, triggering the calculation, based upon the payment details specified in the related contracts, of the payable due to and from each of the parties; and

following such an event, and in accordance with the contracts, executing payments directly between the parties of the net amount due to and from each party such that gross payments need not pass through one party to the next.

24. A method in accordance with claim 23 wherein at least one of the contracts contains a term that calls for a delay between a marketplace event and the execution of payments.

25. A method in accordance with claim 23 wherein one of said marketplace events is the receipt of a request for a product transmitted from a customer to a seller.

26. A method in accordance with claim 23 wherein one of said marketplace events is the delivery of a product, and wherein a permissible contract term is product delivery.

27. A method in accordance with claim 23 wherein a digital template for a contract is provided.

28. A method in accordance with claim 23 wherein both ratified and non-ratified contracts can be created and which method includes the steps of transmitting a non-ratified contract from a first entity to a second entity specified in the non-ratified contract, and thereafter receiving digital acceptance and ratification of the contract from the second party.

29. A method in accordance with claim 23 and further comprising the step of receiving, in the computerized system, a request to view a portion of the database, via a communication link.
 Description Submit all comments and votes
 


BACKGROUND OF THE INVENTION

The present invention concerns a method and system for the digital automation of the transaction space. Automation of the transaction space includes, in part, automation of supplier fulfillment instructions, special instructions, logistics, shipping coordination, generation of transactional data, necessary reporting, payments and banking in consideration of completed transactions. The parties participating in the transaction space include, first, sellers that digitally transmit point of sale ("POS") data to the system, then the primary order fulfillment company, the shipper, banks and preceding levels of suppliers, manufacturers, shippers and banks. Specifically, the method and system enable digital contracts of these parties to operate together. The digital contracts are drafted, are ratified for usage by the contracting parties, are stored and operate automatically upon the occurrence of certain events. Two or even thousands of contracts may represent the business instructions of the parties for a given product or transaction. When certain events occur, the system identifies the contracts that are associated with the specified transaction. These contracts are linked; then, an event triggers computational activity as specified in the contracts. The various activities of the transaction space for the supply chain are thereby automated. Traditionally, with conventional computing and accounting and with EDI, business is conducted on a transactional basis, not on a contract basis, with computational operations physically located at each entity. Transactional data is transmitted sequentially, from suppliers to manufacturers, up through the supply chain ending at the top with the final seller. With electronic data interchange (EDI), transactions are transmitted electronically; the initiation of a corresponding transaction may be accomplished manually or even mechanically automated. The linkage of parties by EDI has thus far been limited to only two levels of automation, that is invoice generation upon EDI receipt of a product order ("PO"). This system uses contracts to generate new transactional data and to minimize or eliminate the need to exchange transactional data in order to generate new data. Further, the transactional data can be consolidated into report form, thus precluding the need to deliver all transactional data to each party.

A conventional sales architecture provides that an order is placed at a point of sale ("POS"), and the ordered product is eventually delivered to the ordering party. There are a number of significant events and actions, nevertheless, that must occur manually prior to delivery of the product. Most of these events and actions are not traditionally automated. To the contrary, an intense amount of human interaction is conventionally required in order to complete the commercial transaction initiated by the order.

Consider, by way of example, a commercial transaction wherein a buyer places an order at a POS for a particular device. This initiates the seller's action of ordering the device from the supplier. The supplier will then order the device from the manufacturer. In turn, the manufacturer will order the correct parts required to make and deliver the device from various parts suppliers. The manufacturer will pay the various parts suppliers, resulting in the manufacturer's bank transferring funds from the manufacturer's account to the various parts suppliers' accounts at the suppliers' banks, and the parts suppliers will deliver the parts to the manufacturer. Once the manufacturer delivers the manufactured device to the supplier, the supplier will pay the manufacturer. Thereafter, there is a transfer of funds from the supplier's account to the manufacturer's account at their respective financial institutions. The supplier will deliver the part to the seller, resulting in a transfer of funds from the seller to the supplier. Finally, the seller delivers the part to the buyer, resulting in a transfer of funds from the buyer to the seller from their respective accounts. Each of these steps occurs independently and sequentially. Moreover, any particular link in the chain of the commercial transaction will require independent action. Such action may include physical verification of receipt of the goods from a carrier, physical or automated verification of credit, physical authorization of payment, etc. Additionally, inventorying is done by each party in the chain. Each action taken requires some human input, magnifying chance for error. When commercial transactions on a national basis are aggregated, these actions are repeated innumerable times each day.

In another example, consider "back office" applications. "Back office" refers to the work such as accounting and computing used to fulfill orders, to invoice, to log receipts, etc. This has also been denominated the "transaction space." Typical accounting involves many manual procedures including, in part, logging purchase orders, drafting bills of materials, ordering shipping, scheduling shipping, invoicing, recording sales, issuing purchase orders, drafting receivers, receiving bills, recording payables, accounting for these transactions and functions, credit, collections, receivables and payables. As listed here, these represent fifteen manual steps, much staffing of personnel, large volumes of paper and, consequently, the handling and filing of large amounts of paper documents. These steps do not include additional steps of journal, ledgers, financial reports and m