JP2006215622A - Transaction system and transaction method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a transaction system and a transaction method for performing transactions on credit among transaction group enterprises. <P>SOLUTION: A credit transaction program 200 includes a purchase order creating unit 212, a purchase order dividing unit 214 and a settlement managing unit 218. The creating unit 212 receives a purchase order processing of a first transaction from a first transactor, generates purchase order data of transactions, adds purchase order ID to the data to store it in a purchase order DB 294, and associates a transaction ID with the created purchase order ID to store transaction data in a transaction DB 296. The dividing unit 214 receives a purchase order processing of a second transaction, and associates the transmitted transaction ID with the purchase order ID to store the transaction data in the transaction DB 296. The settlement managing unit 218 calculates counter values to be payed by an enterprise and to be received thereby, a service charge, and a split commission to be payed from a order receiving side enterprise to a order placing side enterprise to perform settlements. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a trading system and a trading method for performing a margin transaction between trading group companies as an alternative to fund procurement from a financial institution.

For example, Patent Document 1 discloses a method for efficiently managing account funds of a trading group company.
For example, Patent Literature 2 discloses a transaction method performed between traders who have accounts receivable or accounts payable.
For example, Patent Literature 3 discloses a method of offsetting trade payables and trade receivables in a certain trader.
For example, Patent Document 4 discloses a method in which a supervising company in a trading group performs deposit / withdrawal of a supervised company.
However, none of these documents considers margin trading between trading group companies as an alternative to financing from financial institutions.
JP 2002-133129 A JP 2003-76930 A JP 2003-76931 A JP 2004-38614 A

  The present invention has been made from the above-described background, and an object thereof is to provide a transaction system and method for facilitating a margin transaction between transaction group companies.

  In order to achieve the above object, a transaction management apparatus according to the present invention is a transaction management apparatus connected to a plurality of transaction apparatuses, and in each of the transactions, the other transaction apparatus for each of the transaction apparatuses is an ordering side. The transaction device is classified into the order receiving side, the consideration is paid from the ordering side to the order receiving side, and each transaction device other than the transaction device capable of placing an order for any transaction in each transaction is In each of the transactions, within the range of consideration paid for the order received from the ordering side transaction device, an order is placed with respect to the other ordering transaction device, and 1 of the ordering side transaction devices Pay a commission for each of the two or more, order each transaction, place an order for any transaction with which the transaction is associated, the transaction device that ordered the transaction, Transaction data storage means for storing transaction data associating the purchased transaction device with consideration paid for the transaction, and each of the transaction devices based on the stored transaction data Consideration to be paid to the device or consideration to be calculated from another transaction device, fee calculation means to calculate the fee based on the stored transaction data, and the calculated consideration And settlement means for settlement of the amount to be paid or the amount to be paid based on the transaction fee.

Preferably, it further comprises purchase order data storage means for storing purchase order data in which the order of the arbitrary transaction is associated with the transaction apparatus that has ordered the transaction, and each of the stored transaction data includes: An identifier for identifying the purchase order data is included, and this identifier is associated with any of the stored purchase order data.
Preferably, the settlement means pays the fee to each orderer of a transaction in which the contractor in the stored transaction is further associated with an order of any transaction with which the transaction is associated. To settle.

Preferably, the settlement means performs settlement for each of the transaction devices such that the calculated fee is paid using the consideration paid to the transaction device as a source.
Preferably, for each of the transaction devices, the fee calculation means searches the stored transaction for a transaction for which the transaction device is a contractor, and according to a consideration paid for the searched transaction. , Calculate the fee.
Preferably, the fee calculation means searches the stored transaction for transactions for which the transaction device is an orderer or a contractor for each of the transaction devices on a predetermined reference date. A fee is calculated according to the amount that the transaction apparatus can order.

Preferably, for each of the transaction devices, the fee calculation means searches for transactions for which the transaction device is a contractor from the stored transactions, and determines a certain amount of the fee for the searched transactions. Preferably, the fee calculating means sets the predetermined amount of the amount to be calculated as the amount of the fee.
Further preferably, the fee calculation means calculates the fee so that the fee is evenly distributed to each orderer of the transaction that can pay the fee.

  The transaction system according to the present invention is a transaction system having a plurality of transaction devices and a transaction management device connected to the plurality of transaction devices, and in the transaction, another transaction device for each of the transaction devices. Is classified into an ordering side and an ordering side, a consideration is paid from the ordering side to the ordering side, a fee is paid from the ordering side to the ordering side, and the plurality of transaction devices are: Including a first transaction device and a second transaction device other than the first transaction device, each of the first transaction devices placing an order for an arbitrary transaction with respect to another transaction device in each of the transactions Each of the second transaction devices has an order receiving means for receiving an order from another transaction device, and each of the transactions A second ordering means for placing an order for a transaction with another transaction device on the order side within a range of consideration paid for the transaction ordered from the transaction device on the side, the transaction management device, Corresponding to each of the transactions, an order of an arbitrary transaction associated with the transaction, the transaction device that has ordered the transaction, the transaction device that has received an order for the transaction, and a consideration paid for the transaction Based on the transaction data storage means for storing the transaction data and the stored transaction data, each transaction device calculates a value paid to another transaction device or a value paid from another transaction device. The transaction calculation means, a fee calculation means for calculating the fee based on the stored transaction data, and each transaction device pays based on the calculated consideration and the fee. And a means of payment to settle the amount or amounts to be paid.

  Further, the transaction management method according to the present invention is a transaction management method performed between a plurality of transaction devices, and in each of the transactions, the other transaction devices for each of the transaction devices are divided into an ordering side and an order receiving side. Each of the transaction devices other than the transaction device that is classified and paid to the order-receiving side from the ordering side and can place an order for any transaction in each of the transactions, receives an order from another transaction device, In each of the transactions, within the range of consideration paid for the order received from the order-side transaction device, place an order for the other order-side transaction device, and each one or more of the order-side transaction devices Paying a commission, each of the transactions, an order for any transaction associated with the transaction, the transaction device that ordered the transaction, and the transaction device that received the transaction. Transaction data in association with the payment to be paid for this transaction, and based on the stored transaction data, each of the transaction devices pays for other transaction devices, or other The consideration paid from the transaction device is calculated, the fee is calculated based on the stored transaction data, and the amount paid or paid by each of the transaction devices based on the calculated consideration and the fee To settle.

  Further, the program according to the present invention is a transaction management device including a computer and connected to a plurality of transaction devices. In each of the transactions, the other transaction devices for each of the transaction devices include an ordering side and an order receiving side. Each of the transaction devices other than a transaction device that can place an order for any transaction in each transaction receives an order from another transaction device. In each of the transactions, an order is placed with respect to the other transaction device on the order receiving side within the range of consideration paid for the order received from the transaction device on the ordering side, and one or more of the transaction devices on the ordering side are each In the transaction management apparatus that pays a fee for the transaction, each of the transactions, an order of an arbitrary transaction associated with the transaction, and the transaction that orders the transaction are arranged. A transaction data storage step for storing transaction data in which a transaction apparatus, the transaction apparatus that has received an order for the transaction, and a consideration paid for the transaction are associated, and the transaction apparatus based on the stored transaction data A consideration calculating step for calculating a consideration paid to another transaction device or a consideration paid from another transaction device, and a fee calculation step for calculating the fee based on the stored transaction data Based on the calculated consideration and the fee, the computer is caused to execute a settlement step for settlement of an amount to be paid by each transaction device or an amount to be paid.

  According to the present invention, margin trading can be performed between trading group companies as an alternative to fund procurement from a financial institution.

[Background of the present invention]
In order to facilitate understanding of the present invention, first, the background that led to the present invention will be described.
FIG. 1 is a diagram illustrating a transaction according to the transaction method of the present invention.
As shown in FIG. 1, conventionally, an order is placed and an order is received between a company A and companies B1 to B3 in a transaction group, and a transaction has been performed.

In the example shown by the straight line and two-dot chain arrows in FIG. 1, the following transactions (1) to (3) are performed.
(1) Company A places an order for a transaction with company B1 which is a counterparty company, company B1 delivers the engine to company A, and company A pays 1 billion yen to company B1 as the payment.
(2) The company B1 places an order with the company B2 which is a counterparty company, the company B2 delivers the screw to the company B1, and the company B1 pays 400 million yen to the company B2.
(3) The company B2 places an order with the company B3 which is a counterparty company, the company B3 delivers iron to the company B2, and the company B2 pays 100 million yen to the company B3.

In the case of the example shown in FIG. 1, the company A pays the company B1 when the engine is delivered from the company B1.
Similarly, the company B1 pays the company B2 when the screw is delivered from the company B2, and the company B2 pays the company B3 when the iron is delivered from the company B3.
Here, the company B3 must procure funds for delivering iron from a financial institution or the like.
When the financial institution does not lend funds to the company B3, the company B3 needs to consider the cash flow separately.

Further, even if the company B2 pays for the delivery of the company B3, when the company B1 has not delivered to the company B1, the company B1 does not pay, so the company B3 pays the company B3. I can't.
Similarly, when the company B1 has not delivered to the company A, the company A has not been paid, and therefore cannot pay the company B2.
That is, the company B1 and the company B2 also need to consider the cash flow separately when the fund procurement from the financial institution is stagnant.

  The transaction method according to the present invention was made in order to eliminate the unreasonableness in transactions in which funds must be raised from financial institutions in spite of such sales. By using “credit of the transaction that B1 promises to deliver” as the credit of the transaction between company A's trading group companies (B1, B2, B3), it is not necessary to procure funds from financial institutions. Realize improved transactions between trading group companies.

[Outline of the present invention]
Hereafter, the outline | summary of the transaction concerning this invention is demonstrated.
As indicated by the circular arrows in FIG. 1, when company A orders a transaction of an arbitrary amount from company B1 which is a counterparty company, a purchase order with an identifier (a-1) is issued.
This purchase order indicates that the issuer of this purchase order is company A, the amount of this transaction is 1 billion yen, the delivered product is an engine, and the settlement date is October 31. Yes.
The purchase order issued from the company A is uniquely identified by the identifier.
The circle included in the purchase order a-1 in FIG. 1 schematically represents the payment amount of the company A.

This purchase order can be divided and used for payment.
Specifically, when company B1 orders a transaction to purchase screws for 400 million yen from company B2, 400 million yen out of the 1 billion yen indicated in the purchase order will be paid to company B2. Can be used.
That is, 1 billion yen of the purchase order is divided into 600 million yen and 400 million yen, and the divided 400 million yen can be used for payment, and the remaining 600 million yen can be left in the hand of the company B1.
In this case, the purchase order divided by the company B1 and passed to the company B2 indicates that the amount of this transaction is 400 million yen, the delivered item is a screw, and the settlement date is October 31. Show.
Similar to the purchase order issued from the company A, the divided purchase order is assigned the identifier a-1 and indicates that the issuer is the company A.

The divided purchase order can be further divided and used for payment.
When company B2 orders a transaction to purchase iron for 100 million yen from company B3, 100 million yen out of 400 million yen shown in the divided purchase order must be used for payment to company B3. Can do.
In other words, 400 million yen of the split purchase order will be further divided into 300 million yen and 100 million yen, the divided 100 million yen will be used for payment, and the remaining 300 million yen will be handed to company B2 Can be left behind.
In this case, the purchase order further divided by the company B2 and delivered to the company B3 has a transaction amount of 100 million yen, the delivered product is iron, and the settlement date is October 31. Furthermore, similarly to the other purchase orders, the identifier a-1 is attached, indicating that the issuer is the company A.

Companies B3, B2 and B1 each deliver iron, screws and engines for the ordered transactions.
Here, the transaction between the company A and the company B1 is “a transaction in which the company A promises payment by the company B1,” and the purchase order issued in this transaction includes an identifier a-1 and a settlement date. It is included.
When company B1 delivers the engine that is the object of transaction in this transaction to company A and the date is the settlement date included in the purchase order with identifier a-1, settlement of this purchase order Is done.

As indicated by the rectangular arrow in FIG. 1, the settlement is left on hand from the company A, which is the issuer of the purchase order a-1, to the companies B1 to B3 that have left the purchase order a-1. The payment is made on October 31st, which is the settlement date, so that the purchase order amount is paid.
Specifically, the company B1 receives 600 million yen from the company A, the company B2 receives 300 million yen from the company A, and the company B3 receives 100 million yen from the company A.
The total amount received by the companies B1 to B3 is the amount indicated in the purchase order issued by the company A first.

FIG. 2 is a diagram illustrating a relationship between a trading group / partner company and a margin trading center.
As shown in FIG. 2A, the credit transaction center provides a service including the purchase order split described above, and the company A and the companies B1 to Bn use the provided service.
The company group including the company A and the companies B1 to Bn may be one trading group company or a set of business partners.
In this group of companies, whether or not there is a capital relationship is not questioned, but companies B1 to Bn need to be registered as members by company A.

In this company group, company A places an order for a transaction with trading partner company B1.
The company B1 uses the credit of this transaction to place an order for the transaction with respect to B2 or B2 ′.
At this time, the company B1 can use the purchase order split service provided from the credit transaction center to split the purchase order issued from the company A in the previous transaction and use it for payment to B2 or B2 ′.
Further, the company B1 and the company B2 or any one of them pays a predetermined amount to the credit transaction center as a service usage fee.
The company B2 or the like can use this purchase order split service to further split the purchase order issued by the company A and use it for payment of the transactions that it orders.
Similarly, the company B2 and the company B3 or any of them pays a service usage fee.

As described above, the companies B1 to Bn use the credit of the company A for transactions, so that they can be freed from anxiety about cash flow preparation at the time of payment.
Further, the companies B2 to Bn and the like can be freed from anxiety about the payment default (default) of the orderer.
The usage fee paid by the company B1 etc. to the credit transaction center may be less than the interest rate and fee paid when the loan was received from a financial institution, and the company B1 etc. You can get alternatives.

The margin trading center may pay a part of the usage fee received from the companies B1 to Bn to the company A as a dividend.
The company A can return the profit of the credit transaction center by causing the company B1 or the like to use the credit transaction center.
In addition, funds flow from company A to company B1, etc., from company B1 etc. to margin trading center, and from margin trading center to company A and circulate, and do not flow out of this trading group / partner company. Therefore, economic efficiency can be improved.
Further, as shown in FIG. 2B, the credit transaction center can provide services including purchase order splitting to a plurality of different transaction groups and business partners.

FIG. 3 is a diagram showing a profit model of a transaction.
As shown in FIG. 3, the revenue of the credit transaction center includes a usage fee received from the service user company, and the expenditure includes dividends to shareholders, taxes and other costs.
In this example, the revenue of the credit transaction center is a usage fee from companies B1 and B2.
The usage fee of the purchase order split service may be an amount obtained by multiplying the amount of the transaction ordered by each user company by a certain ratio.
Further, the usage fee may be collected from the ordering company and / or the receiving company of the transaction.
The credit transaction center does not have to collect a usage fee from the company A that first issued a purchase order and placed an order, or from the company A and its counterparty company B1.

The payee of the dividend includes, for example, company A and service provider company X.
The service providing company X provides services provided from the credit transaction center including the purchase order split service to the credit service center customer company such as the company A.
The payee of the cost includes a service provider, and the service provider is the IT system provider company X of the credit transaction center and other providers who provide people, land, and the like.
IT system provider X develops and operates a credit transaction center system.
The service provider company X and the IT system provider company X may be the same.

FIG. 4 is a diagram exemplifying a division fee paid from an order-receiving company of a transaction to an ordering company in a transaction according to the present invention. FIG. 4A is a diagram in which the order-receiving company issues or divides a purchase order. The case where the splitting fee is paid to all the ordering companies that have made the order is shown, and (b) shows the case where the ordering company pays the splitting fee to the ordering company of the transaction.
As shown in FIG. 4A, the company B1 pays a division fee to the company A that issues a purchase order and places an order for the transaction.
Further, the company B2 pays a division fee to the company B1 and the company A that have ordered the transaction by dividing the purchase order.
Similarly, the company B3 also pays a division fee to the company B2, the company B1, and the company A that have ordered the transaction by dividing the purchase order.
The division fee is calculated by the margin trading center (FIG. 2) and settled so that the ordering company pays the ordering company.

As shown in FIG. 4B, the division fee may be paid only from the company that has received an order for a certain transaction to the company that has ordered the transaction.
In this case, the company B2 pays the division fee only to the company B1 that has ordered the transaction ordered by the company B2.
In addition, the company B3 pays the division fee only to the company B2 that has ordered the transaction ordered by the company B3.

FIG. 5 is a diagram showing the funds for the split commission paid from the ordering company. (A) shows a case where a part of the purchase order amount remaining at hand is used for the split commission, and (b) Indicates the case where a part of the purchase order amount remaining on hand is not allocated to the split fee.
As shown in FIG. 5A, the company B2 remains at hand, excluding the amount paid to the company B3 (100 million) from the amount paid for the order received from the company B1 (400 million). A part of the amount (300 million) will be allocated to the split fee.
In addition, the company B1 and the company B3 can also use a part of the remaining amount for the splitting fee.
For this reason, the companies B1 to B3 do not need to raise funds from financial institutions or the like for the division fee.

As shown in FIG. 5B, the company B2 or the like may pay the division fee using a check or the like without using a part of the amount remaining on hand as the division fee.
In this case, the balance of the company B2 is left as it is at the company B2, but the company B2 needs to separately procure a division fee.

FIG. 6 is a diagram showing the calculation target of the split fee. (A) shows the case where the consideration paid for the transaction is the target of calculation of the split fee, and (b) remains at hand on a predetermined day. It shows the case where the amount of the purchase order (the amount of money paid out minus the amount to be paid) is the target for calculation of the division fee.
As shown in FIG. 6 (a), the division fee is calculated according to the consideration paid for the transaction ordered by the order-receiving company.
For example, in the case where the consideration for the transaction that the company B2 has received from the company B1 is 400 million, the division fee is calculated with 400 million paid for the transaction as a calculation target.

As shown in FIG. 6B, the division fee may be calculated according to the amount of the purchase order remaining in the hand of the order-receiving company.
For example, a company B2 receives a transaction with a consideration of 400 million from the company B1, orders a transaction with a consideration of 100 million from the company B3, and leaves 300 million as the balance of the purchase order on a given day. In such a case, the division fee is calculated using the remaining 300 million as a calculation target.
Note that the margin trading center can employ both the cases of FIG. 6A and FIG.

FIG. 7 is a diagram showing a method for calculating a split fee. (A) shows a case where a predetermined percentage of the amount to be calculated is a split fee, and (b) shows a split fee for a calculation target. Shows the case.
As shown in FIG. 7A, the division fee is calculated by multiplying the amount of each calculation object (consideration paid for the transaction) by a predetermined ratio (for example, 1%).
For example, if the contracting company receives an order for a transaction with a consideration of 400 million, a transaction with a consideration of 600 million, and a transaction with a consideration of 100 million, the split fee is a predetermined percentage of these considerations. Is multiplied by, resulting in 4 million, 6 million and 1 million for each transaction.

As shown in FIG. 7B, the division fee may be calculated as a fixed amount for each calculation target.
For example, when the fixed amount is 3 million, the division fee is 3 million which is a fixed amount regardless of the transaction price.
Note that the margin trading center can employ any of the cases of FIG. 7A and FIG.

FIG. 8 is a diagram showing a method for distributing the split fee. (A) shows a case where the split fee is equally distributed to the ordering company, and (b) shows the split fee being distributed to the ordering company. On the other hand, the case of non-uniform distribution is shown.
As shown in FIG. 8 (a), the calculated division fee is evenly distributed and paid to each ordering company.
For example, when the division fee is calculated to be 3 million, the equally distributed division fee of 1.5 million is paid to the company B1 and the company A.

As shown in FIG. 8 (b), the calculated division fee may be distributed unevenly to each ordering company and paid.
For example, when the split fee is calculated to be 3 million, the split fee of 2 million may be paid to the company B1, and the split fee of 1 million may be paid to the company A.
Note that the margin trading center can adopt both the cases of FIG. 8A and FIG.

FIG. 9 is a diagram exemplifying the division fee paid by the company B2 in the transaction shown in FIG.
As shown in FIG. 9, the division fee is calculated by multiplying the amount paid for the transaction by a predetermined ratio, and is distributed evenly and paid to each ordering company. (FIG. 4 (a), FIG. 6 (a), FIG. 7 (a) and FIG. 8 (a)).
In other words, when company A places an order with company B1 and company B1 places an order with company B2, the division fee is calculated based on the transaction amount (400 million) received from company B1 by company B2. Multiplying this amount by a predetermined ratio (1%), it is calculated to be 4 million, and is distributed equally to 2 million units and paid to each of company B1 and company A.
Hereinafter, a case where the division fee is in the form shown in FIG. 9 will be described as the first embodiment.

[First Embodiment]
FIG. 10 is a diagram illustrating the configuration of the margin transaction system 1 according to the present invention.
As shown in FIG. 10, the margin transaction system 1 includes a margin transaction server 20, a purchase management server 24, a member management server 26, an accounting server 28, and an orderer apparatus 12 ( The first transaction apparatus) and the ordering / ordering apparatuses 14-1 to 14-n (second transaction apparatus) are connected to each other via an intra-center network 290 such as a LAN or WAN, and the network 100. .
Further, the margin transaction server 20 and the accounting server 28 are connected to an external settlement system (financial institution) via the financial network 102.

The transactions shown in FIGS. 1 and 2 are executed by the orderer apparatus 12, the order placement apparatuses 14-1 to 14-n, the margin transaction server 20, the purchase management server 24, the member management server 26, and the accounting server 28. It is performed between companies B1 to Bn.
Hereinafter, these servers are collectively referred to as nodes.
Further, when any of a plurality of components such as the ordering / ordering devices 14-1 to 14-n is indicated without being specified, the ordering / ordering device 14 may be simply abbreviated.

[hardware]
Hereinafter, the hardware of each node will be described.
FIG. 11 is a diagram illustrating a hardware configuration of a computer used in each node illustrated in FIG.
As shown in FIG. 11, the computer of each node communicates with other nodes via a device main body 108 including a CPU 104 and a memory 106, a display / input device 110 including a keyboard and a display, the network 100, or the financial network 102. And a storage device 114 that records and reproduces data with respect to the recording medium 116.
That is, the computer of each node has a component as a computer capable of information processing by executing a program and communication with other nodes via a network.

[software]
Hereinafter, a program executed in each node and a database referred to by these programs will be described.

[Credit Transaction Program 200]
FIG. 12 is a diagram showing a configuration of a margin transaction program 200 executed on the margin transaction server 20 shown in FIG.
As shown in FIG. 12 (a), the margin transaction program 200 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, a member management unit 206, a purchase order viewing acceptance unit 208, a transaction management unit 210, a purchase order form. A creation unit 212, a purchase order splitting unit 214, a delivery management unit 216, a settlement management unit 218, a company DB 292 (FIG. 13), a purchase order DB 294 (FIG. 14), and a transaction DB 296 (FIG. 15) are included.
As shown in FIG. 12B, the payment management unit 218 includes a consideration calculation unit 220, a usage fee calculation unit 222, a fee calculation unit 224, and a payment unit 226.

The margin transaction program 200 realizes the transaction described with reference to FIGS. 1 to 9 by these components.
The margin transaction program 200 is supplied to the margin transaction server 20 via, for example, the recording medium 116 (FIG. 11), loaded into the memory 106, and executed on the OS operating on the margin transaction server 20.
The following programs are also supplied and executed in the same manner.

In the margin transaction program 200, the UI unit 202 controls the operation of each component of the margin transaction program 200 in accordance with a user operation on the display / input device 110 (FIG. 11).
In addition, the UI unit 202 displays information / data created by each component of the margin transaction program 200 and processing contents of each component on the display / input device 110 or stores it in the storage device 114.

The authentication / communication processing unit 204 performs communication processing required for communication with each node and authentication processing between them.
The member management unit 206 receives information / data related to the membership processing or withdrawal processing transmitted from the member management program 260 (described later with reference to FIG. 18) executed on the member management server 26, and receives the company DB 292 (FIG. 13). ) And manage companies that are members.

FIG. 13 is a diagram showing a configuration of a company database (DB) 292 that manages information of each company.
As shown in FIG. 13, the company data stored in the company DB 292 includes a company ID, a company name, a financial institution account number (hereinafter referred to as an account number), and a purchase order issuance enable flag.
The company ID is an identifier (ID) for managing registered companies, and each company is uniquely identified by this company ID.
The company name is the name of the company associated with the company ID.
The account number is a number for identifying an account established by this company in an external financial institution.
The purchase order issuance enable flag is a flag indicating whether or not an arbitrary transaction (first transaction) performed by issuing a purchase order can be ordered.

Each company is a trader who orders and / or accepts a transaction, and can be an orderer who orders a transaction and a contractor who receives a transaction from this orderer.
In addition, the company has a first trader who can be a purchaser who can place an order by issuing a purchase order, and a trader other than the first trader who is an orderer and a contractor. And a second trader.
Preferably, the first trader is one in a group of companies including a plurality of traders, and is identified by a purchase order issuance enable flag.
For example, in the company data of the company A, the purchase order issue flag is checked, and in the company data of the companies B1 to Bn, the purchase order issue flag is not checked.

The purchase order viewing accepting unit 208 (FIG. 12) accepts a purchase order request transmitted from an order placement program 140 (described later with reference to FIG. 21) executed on the order placement apparatus 14, and receives a purchase order DB 294 (FIG. 12). 14) and transaction DB 296 (FIG. 15), a purchase order possessed by the requesting company and information related to the transaction are transmitted.
The purchase order viewing accepting unit 208 searches the transaction DB 296 for a transaction in which this company is an orderer or a contractor based on the transmitted company ID, and places an order based on the purchase order ID of the retrieved transaction. Information regarding this purchase order is retrieved from the document DB 294.

FIG. 14 is a diagram showing a configuration of a purchase order DB 294 that manages information on each purchase order issued from a company that is the first trader.
As shown in FIG. 14, the purchase order data stored in the purchase order DB 294 includes a purchase order ID, an orderer, a settlement date, and a settled flag.
Here, the orderer stores the corresponding company ID in the company DB 292 (FIG. 13).

The purchase order ID is an identifier for managing the issued purchase order, and each purchase order is uniquely identified by the purchase order ID.
The orderer is a company that has ordered the transaction by issuing this purchase order using the first transaction apparatus.
The settlement date is the date on which the transaction related to this purchase order is settled.
The settled flag stores whether or not a transaction related to this purchase order has been settled.

FIG. 15 is a diagram illustrating a configuration of a transaction DB 296 that manages information on each transaction between the orderer and the contractor.
As shown in FIG. 15, the transaction data stored in the transaction DB 296 includes a transaction ID, a purchase order, an orderer, a contractor, an amount, an order item, a delivery condition, a scheduled delivery date, a delivered flag, and a verified flag. .
Here, the purchase order stores the corresponding purchase order ID in the purchase order DB 294 (FIG. 14).
Further, the orderer and the contractor store the corresponding company ID in the company DB 292 (FIG. 13).

The transaction ID is an identifier for managing a transaction performed between the orderer and the contractor, and each transaction is uniquely identified by the transaction ID.
A purchase order is a purchase order associated with this transaction.
One transaction is associated with one purchase order when the transaction (first transaction) is ordered from the first trader.
When a second trader who has received a trade order further orders a transaction (second transaction) performed by dividing a purchase order, a plurality of transactions are associated with one purchase order.
In this way, the second transaction is stored in association with the purchase order issued in the first transaction.
Note that a transaction may be uniquely identified by a transaction ID and a purchase order ID.

The orderer is a company that has ordered this transaction using the first transaction device or the second transaction device.
The contractor is a company that has received this transaction using the second transaction apparatus.
The amount is the consideration paid for this transaction.
The ordered item is a transaction object related to this transaction.
The contractor is provided with the price of the transaction by delivering the transaction object.
The delivery conditions are conditions arbitrarily determined for this transaction.
The scheduled delivery date is the scheduled date on which the contractor delivers the transaction object.

The delivered flag stores whether or not the contractor has notified that the transaction object to be delivered in this transaction has been delivered.
The inspection completion flag stores whether or not the orderer has inspected the transaction object of this transaction.

Each company can recognize the consideration paid and the consideration paid based on the amount of each searched transaction when the orderer or the contractor searches the transaction DB 296 for a transaction having its own company ID.
Each company searches the transaction DB 296 for a transaction in which the orderer or the contractor has its own company ID, and searches the purchase order DB 294 based on the purchase order ID associated with each searched transaction. Recognize the settlement date of purchase orders.

FIG. 16 is a diagram showing a reference relationship among the company DB 292, the purchase order DB 294, and the transaction DB 296.
As shown in FIG. 16, the purchase order data (company ID) included in the purchase order DB 294 refers to the company ID included in the company DB 292 so that the purchase order data is associated with the company data.
Here, a plurality of purchase order data can be associated with one company data.

Further, the purchase order included in the transaction DB 296 (order purchase order ID) refers to the purchase order ID included in the purchase order DB 294, so that the transaction data is associated with the purchase order data.
A plurality of transaction data can be associated with one purchase order data.
The orderer (company ID) and the contractor (company ID) included in the transaction DB 296 refer to the company ID included in the company DB 292.

The transaction management unit 210 (FIG. 12) receives information / data relating to ordering, order receipt and delivery of transactions transmitted from a purchase management program 240 (described later with reference to FIG. 17) executed on the purchase management server 24. , Order management processing and delivery management processing.
Further, the transaction management unit 210 performs a payment management process so that the transaction is settled on a predetermined settlement date included in the purchase order.
Specifically, the transaction management unit 210 includes a purchase order creation unit 212, a purchase order splitting unit 214, a delivery management unit 216, and a settlement management unit 218, and the above-described processing is performed by these components.

The purchase order creation unit 212 receives and processes an ordering process for the first transaction from the first trader from the purchase management program 240.
Specifically, the purchase order creation unit 212 creates purchase order data for the accepted transaction, assigns a unique purchase order ID thereto, and stores it in the purchase order DB 294.
Further, the purchase order creation unit 212 associates the unique transaction ID transmitted from the purchase management program 240 with the created purchase order ID and stores the transaction data in the transaction DB 296.
Note that when the purchase order creation unit 212 registers in the purchase order DB 294 and the transaction DB 296, all flag attributes included in the purchase order DB 294 and the transaction DB 296 are not checked.
These flags are checked when corresponding predetermined processing is performed, as will be described later.

The purchase order splitting unit 214 receives and processes the ordering process of the second transaction from the first trader or the second trader from the purchase management program 240.
Specifically, the purchase order dividing unit 214 associates the transaction ID transmitted from the purchase management program 240 with the purchase order ID, and stores the transaction data in the transaction DB 296.
That is, the purchase order dividing unit 214 newly associates one transaction with the purchase order already stored in the purchase order DB 294.
The amount of the transaction newly stored in the transaction DB 296 is smaller than the amount of any other transaction that is associated with the same purchase order as this transaction and is already stored in the transaction DB 296.
Further, as with the case of the purchase order creation unit 212, all the newly stored transaction flags are not checked.

The delivery management unit 216 receives a notification from the purchase management program 240 that the transaction contractor has delivered the transaction object, and checks the delivered flag of this transaction stored in the transaction DB 296.
Similarly, the delivery management unit 216 receives a notification that the orderer of the transaction has accepted the transaction object, and checks the accepted flag of this transaction stored in the transaction DB 296.
In this way, for each transaction, it is managed whether the contractor has delivered the transaction object and whether the orderer has accepted the transaction object.

  The settlement management unit 218 performs settlement by calculating the consideration paid in the transaction or the consideration paid, the service usage fee paid to the credit transaction center, and the division fee paid by the ordering company to the ordering company.

The consideration calculation unit 220 calculates the consideration paid to each other company or the consideration paid from the other company based on the transaction data stored in the transaction DB 296.
The consideration calculation unit 220 searches the purchase order DB 294 for the purchase order with the settlement date based on the settlement date, and associates the purchase order with the purchase order ID of the retrieved purchase order based on the purchase order ID of the purchase order. Search all trades that have been made.
Further, the consideration calculation unit 220 refers to the orderer and the orderer of each of the searched transactions, and the consideration paid to the other company or the payment from the other company for each company that is the orderer and the orderer. Calculate the consideration.
The consideration calculation unit 220 outputs the consideration paid by each company or the consideration paid to the settlement unit 226.

Similarly to the consideration calculation unit 220, the usage fee calculation unit 222 searches the purchase order DB 294 and the transaction DB 296 for the amount of consideration for each transaction, and multiplies this amount by a certain ratio to obtain a service usage fee (FIG. 2). ) Is calculated.
The usage fee calculation unit 222 searches for a company from the company DB 292 based on the orderer and the contractor of each transaction, or any of these company IDs, and the searched company and the calculated service usage fee are Output to the settlement unit 226.

The fee calculation unit 224 calculates a split fee (FIG. 9) that the ordering company pays to the ordering company based on the amount of consideration for each transaction.
More specifically, the fee calculation unit 224 searches all transactions for which the company ID is the contractor from the transaction DB 296 based on the company ID.
Next, the fee calculation unit 224 searches all transactions including the purchase order ID from the transaction DB 296 based on the purchase order ID included in the searched transaction data, and refers to the orderer of the searched transaction. To do.
In this way, the fee calculation unit 224 searches for an orderer of a transaction associated with a purchase order included in the searched transaction (a transaction ordered by dividing this purchase order).

In addition, the fee calculation unit 224 calculates a division fee by multiplying the amount of consideration of the searched transaction by a predetermined ratio.
Further, the fee calculation unit 224 distributes the divided fee evenly so that the calculated divided fee is equally distributed to each searched orderer.
In this way, the fee calculation unit 224 calculates the company for which the division fee is paid and the amount of the division fee.
The fee calculation unit 224 outputs the company to which the division fee is paid and the calculated division fee to the settlement unit 226.

The settlement unit 226 controls the consideration calculation unit 220, the usage fee calculation unit 222, and the fee calculation unit 224 to calculate the consideration, the service usage fee, and the division fee, and performs settlement on a predetermined date.
The settlement unit 226 subtracts the amount of consideration to be paid from the amount of consideration for the transaction paid by each company, and performs settlement so that the company receives the balance.
Further, when the company pays the service usage fee, the settlement unit 226 performs payment so that the company pays the service usage fee.

The settlement unit 226 settles the split commission paid by each company and the split commission paid.
The settlement unit 226 may perform settlement so that the division fee is paid from an amount received by the company for consideration.
The settlement unit 226 searches for the account number of each company from the company DB 292 based on the company ID, and requests settlement from an external financial institution.

For example, if a company receives a transaction associated with a certain purchase order ID for 400 million yen and orders another transaction associated with the same purchase order ID for 100 million yen, the settlement The part 226 performs settlement so that this company receives 300 million yen.
For example, when the split fee is calculated to be 4 million yen by multiplying the amount of the ordered transaction (400 million yen) by a predetermined ratio (1%), the settlement unit 226 The company settles the ordering companies so as to pay an amount in which the calculated division fee is evenly distributed.

When the settlement unit 226 requests the financial institution to settle the payment for the consideration, the service usage fee, and the division fee, the financial institution makes a check with the accounting server 28 of the margin transaction center 2 and the accounting system (not shown) of each company. Perform deposit / withdrawal processing.
The deposit / withdrawal process for the accounting server 28 will be described later with reference to FIG.

[Purchasing management program 240]
FIG. 17 is a diagram showing a configuration of a purchase management program 240 executed on the purchase management server 24 shown in FIG.
17 that are substantially the same as those shown in FIG. 12 are denoted by the same reference numerals.
The same applies to each configuration referred to in the description of the program hereinafter.
17, the purchase management program 240 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, an order receiving unit 242, an order confirmation requesting unit 244, an order processing unit 246, a delivery receiving unit 248, an inspection. A request unit 250 and a delivery processing unit 252 are included.
The purchase management program 240 mediates information / data between the orderer apparatus 12 and the ordering / order receiving apparatus 14 and the margin transaction server 20 by these components, and performs the transaction described with reference to FIGS. 1 and 2. to manage.

The order receiving unit 242 receives an order for a transaction from the orderer apparatus 12 or the order receiving / ordering apparatus 14.
The order receiving unit 242 transmits / receives information / data (order data) relating to the ordering of the transaction to / from the order confirmation requesting unit 244 and the order processing unit 246, and finally orders the transaction from the ordering source. Notify that the procedure has been completed.

The order confirmation requesting unit 244 receives the ordering data from the order receiving unit 242 and confirms whether or not to accept this transaction from the order receiving party of this transaction.
The order confirmation requesting unit 244 identifies the ordering / order receiving device 14 of the contractor from the ordering data, and transmits an order confirmation request to the ordering / ordering device 14.
The order confirmation request unit 244 waits for a response to the order confirmation request and accepts an order confirmation from the ordering / order receiving device 14.
When receiving the order confirmation, the order confirmation requesting unit 244 transmits to the order receiving unit 242 that the transaction has been accepted.

The order processing unit 246 receives the order data whose order has been confirmed from the order receiving unit 242 and transmits the order data to the margin transaction program 200 on the margin transaction server 20 to perform the order process.
The order processing unit 246 newly issues a unique transaction ID given to this transaction, and transmits the transaction ID included in the ordering data in order processing.
The order processing unit 246 waits for a response to the order processing, and receives a processing completion notification from the margin transaction program 200.
Upon receiving the processing completion notification, the order processing unit 246 transmits to the order receiving unit 242 that the order processing for this transaction has been performed.

When the transaction is the second transaction ordered by the second transaction person, the purchase order ID is included in the order data.
When the purchase order ID is included, the purchase order processing unit 246 transmits this purchase order ID to the margin transaction program 200 in the same manner.
The transaction ID may not be issued by the purchase management program 240 but may be issued by the margin transaction program 200 executed on the margin transaction server 20.
In this way, the purchase management program 240 receives an order for a transaction and performs an ordering process.

  The delivery accepting unit 248 receives a notification that the transaction object has been delivered from the ordering / order receiving device 14, and transmits / receives information / data (delivery data) relating to the delivery to / from the acceptance requesting unit 250 and the delivery processing unit 252. In particular, the orderer and the contractor of this transaction are notified that the delivery procedure has been completed.

The acceptance requesting unit 250 receives the delivery data from the delivery accepting unit 248, and confirms whether or not the transaction object of this transaction has been accepted with respect to the ordering party of this transaction.
The acceptance requesting unit 250 identifies the orderer's orderer apparatus 12 or the ordering / ordering apparatus 14 from the delivery data, and notifies the inspection request to these apparatuses.
Further, the acceptance requesting unit 250 waits for a response to the acceptance request, and accepts an acceptance notification from the orderer apparatus 12 or the ordering / order receiving apparatus 14.
Upon receipt of the acceptance notification, the acceptance requesting unit 250 transmits to the delivery accepting unit 248 that the transaction object for this transaction has been accepted.

The delivery processing unit 252 receives the delivery data and the received delivery data from the delivery receiving unit 248, transmits the delivery data to the margin transaction program 200 on the margin transaction server 20, and instructs the transaction update. Process the delivery.
The delivery processing unit 252 waits for a response to the delivery processing, and accepts a processing completion notification from the margin transaction program 200.
Upon receipt of the processing completion notification, the delivery processing unit 252 transmits to the delivery accepting unit 248 that the delivery process for this transaction has been performed.
In this way, the purchase management program 240 accepts delivery notification and performs inspection processing.

[Member management program 260]
FIG. 18 is a diagram showing a configuration of the member management program 260 executed on the member management server 26 shown in FIG.
As shown in FIG. 18, the member management program 260 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, a membership processing unit 262, and a withdrawal processing unit 264.
The member management program 260 mediates information and data between the orderer apparatus 12 and the margin transaction server 20 by these components, and is included in the transaction group / business partner company described with reference to FIG. Manage.

The membership processing unit 262 receives a registration request of a company that becomes a member from the orderer apparatus 12.
The membership processing unit 262 newly issues a unique company ID given to this company, includes this transaction ID in information / data (company data) about this company, and executes the margin transaction program 200 on the margin transaction server 20. Sent to and performs the membership process.
The membership processing unit 262 waits for a response to the membership processing, and accepts a processing completion notification from the margin transaction program 200.
Upon receipt of the processing completion notification, the membership processing unit 262 notifies the transmission source of the registration request that membership processing for this company has been performed.
The company ID may not be issued by the member management program 260 but may be issued by the margin transaction program 200 executed on the margin transaction server 20.

The withdrawal processing unit 264 receives from the orderer apparatus 12 a request to delete a company that is excluded from the trading group / business partner company.
The withdrawal processing unit 264 transmits the company data including the company ID of this company transmitted from the orderer apparatus 12 to the margin transaction program 200 on the margin transaction server 20, and performs the withdrawal process.
When the withdrawal processing unit 264 receives a processing completion notification from the margin transaction program 200, the withdrawal processing unit 264 notifies the sender of the deletion request that the withdrawal processing of the company has been performed.
In this way, the member management program 260 accepts company registration / deletion requests and performs membership / unsubscription processing.

[Accounting program 280]
FIG. 19 is a diagram showing a configuration of an accounting program 280 executed on the accounting server 28 shown in FIG.
As shown in FIG. 19, the accounting program 280 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, a withdrawal processing unit 282, and a deposit processing unit 284.
The accounting program 280 manages the deposit / withdrawal of the margin transaction center 2 described with reference to FIG.

The withdrawal processing unit 282 performs processing for paying a predetermined amount to a predetermined transfer destination when a payment request is made from an external financial institution.
The withdrawal processing unit 282 performs, for example, a process of paying a predetermined amount as a dividend to the company A as a shareholder and the service providing company X (FIG. 3).
In addition, the withdrawal processing unit 282 performs, for example, a process of paying a predetermined amount as a service usage fee to the IT system provider company X that is a service provider and other providers.

The deposit processing unit 284 performs processing for receiving a predetermined amount into a predetermined account when a deposit process is performed from an external financial institution.
For example, the deposit processing unit 284 performs a process of receiving a predetermined amount as a service usage fee from the companies B1 to Bn that are users of the purchase order split service.

[Orderer program 120]
FIG. 20 is a diagram showing the configuration of the orderer program 120 executed on the orderer apparatus 12 shown in FIG.
As shown in FIG. 20, the orderer program 120 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, an enrollment / unsubscription unit 122, an ordering unit 124, and an inspection unit 126.
The orderer program 120 uses these components to manage a trading group / business partner company (Fig. 2) or issue a purchase order to a company included in this business group / business partner company to place a business order. Or notify that the transaction object has been accepted.

The enrollment / unsubscription unit 122 transmits company data of the company to be enrolled or withdrawn, which is input using the display / input device 110, to the member management server 26.
The company data of the company to be withdrawn includes the company ID of this company.
In addition, the enrollment / unsubscription unit 122 causes the display / input device 110 to display necessary information.

The ordering unit 124 transmits, to the purchase management server 24, ordering data related to the ordering of the transaction input using the display / input device 110.
This ordering data includes the contractor, amount, order item, settlement date, and the like.

The inspection unit 126 receives an inspection request transmitted from the purchase management server 24 and causes the display / input device 110 to display the received information.
Further, the inspection unit 126 transmits the information / data (inspection data) of the inspection input using the display / input device 110 to the purchase management server 24.
Furthermore, the entrance / exit unit 122, the ordering unit 124, and the acceptance unit 126 may receive a response to the transmission and display the received content on the display / input device 110.
The orderer program 120 may receive an order for a transaction including an order confirmation unit 146 and a delivery contact unit 148, which will be described later with reference to FIG.

[Ordering program 140]
FIG. 21 is a diagram showing the configuration of the ordering / ordering program 140 executed on the ordering / order receiving apparatus 14 shown in FIG.
As shown in FIG. 21, the ordering / order receiving program 140 includes a user interface (UI) unit 202, an authentication / communication processing unit 204, a purchase order request unit 142, a split ordering unit 144, an inspection unit 126, an order confirmation unit 146, and a delivery notification. Part 148.
The ordering / order receiving program 140 performs ordering and / or ordering of a transaction or any one of these by these components.

The purchase order request unit 142 transmits the company ID input from the display / input device 110 to the margin transaction server 20 and requests a list of purchase orders of the company.
The purchase order request unit 142 receives a list of purchase orders transmitted from the margin transaction server 20 and causes the display / input device 110 to display the list.
This list of purchase orders includes the purchase order ID of each purchase order held by this company.
The purchase order ID can be used to select a purchase order that is split and used to pay for the transaction.
The list of purchase orders may include the amount of transactions related to this company as an orderer or contractor.

The divisional ordering unit 144 transmits the purchase order ID input using the display / input device 110 and the ordering data relating to the ordering of the transaction to the purchase management server 24.
By sending the purchase order ID to the purchase management server 24, the divided purchase order can be uniquely determined.
The order data includes the contractor, the amount, the ordered item, and the like, but does not include the settlement date, as in the ordering unit 124 of the orderer program 120 (FIG. 20).
This is because the settlement date is already included in the divided purchase order.
As with the orderer program 120, the acceptance unit 126 validates the transaction object in the divided ordering transaction.

The order confirmation unit 146 receives a transaction order confirmation request from the purchase management server 24 and causes the display / input device 110 to display the received content.
The displayed contents include the orderer of the transaction, the ordered item, and the like.
The order confirmation unit 146 transmits the order confirmation input using the display / input device 110 to the purchase management server 24.

The delivery contact unit 148 transmits to the purchase management server 24 the fact that the transaction target object of the ordered transaction that has been input using the display / input device 110 has been delivered.
The delivery contact unit 148 also receives a notification from the purchase management server 24 that the delivery process has been completed.

[Company registration operation of margin trading system 1]
FIG. 22 is a sequence diagram showing a registration operation (S10) of companies included in the transaction group / partner company shown in FIG.
As shown in FIG. 22, in step 100 (S100), the user of the company A uses the display / input device 110 of the orderer apparatus 12 to input company data relating to the registered company.
The enrollment / unsubscription unit 122 of the orderer program 120 transmits the input company data to the member management server 26.
The membership processing unit 262 of the member management program 260 receives company data.

In step 102 (S102), the admission processing unit 262 issues a new unique company ID.
In step 104 (S104), the membership processing unit 262 includes the issued company ID in the received company data and transmits it to the margin transaction server 20 to request registration of the company.
The member management unit 206 of the margin transaction program 200 accepts company data including a company ID.
In step 106 (S106), the member management unit 206 stores this company in the company DB 292 (FIG. 13) and registers the company.

In step 108 (S108), the member management unit 206 transmits a notification to the effect that registration of the company is completed to the member management server 26.
The membership processing unit 262 of the member management program 260 receives the transmitted registration completion notification.
In step 110 (S110), the admission processing unit 262 transmits information indicating that the registration has been completed to the orderer apparatus 12.
The enrollment / unsubscription unit 122 of the orderer program 120 accepts the transmitted registration completion notification and causes the display / input device 110 to display that the requested company has been registered.

In this way, the user of the company A registers the company included in the transaction group / partner company via the orderer apparatus 12.
Even when the user of the company A performs the company withdrawal process, the joining / leaving unit 122 of the orderer program 120 transmits the company data of the company to be withdrawn, and the same procedure as the joining process is executed. Thus, the withdrawal process is executed.

[Ordering operation of first transaction of margin trading system 1]
FIG. 23 is a sequence diagram showing the ordering operation (S20) of the first transaction placed by the company A, which is the first trader, in the transaction shown in FIGS.
As shown in FIG. 23, in step 200 (S200), the user of the company A uses the display / input device 110 of the orderer apparatus 12 to input order data related to the transaction to be ordered.
The ordering unit 124 of the orderer program 120 transmits the input ordering data to the purchase management server 24.
The order receiving unit 242 of the purchase management program 240 receives order data from the orderer apparatus 12.
Note that this order data does not include a purchase order ID.

In step 202 (S202), the order receiving unit 242 transmits the received order data to the order confirmation requesting unit 244.
The order confirmation request unit 244 transmits an order confirmation request to an orderee of a transaction included in the ordering data, for example, the company B1 (ordering / order receiving device 14-1).
The order confirmation unit 146 of the ordering / order receiving program 140 receives the transmitted order confirmation request on the ordering / order receiving device 14-1 of the company B1, and displays the contents on the display / input device 110.
In step 204 (S204), when the user of the company B1 confirms this content and inputs an order confirmation using the display / input device 110, the order confirmation unit 146 displays the entered order confirmation on the purchase management server. 24.
The order confirmation request unit 244 of the purchase management program 240 receives the received order confirmation.

In step 206 (S206), the order confirmation requesting unit 244 transmits this order confirmation to the order receiving unit 242.
Upon receiving the order confirmation from the order confirmation requesting unit 244, the order receiving unit 242 transmits ordering data to the ordering processing unit 246.
Upon receiving the order data, the order processing unit 246 newly issues a unique transaction ID.
In step 208 (S208), the order processing unit 246 includes the issued transaction ID in the order data and transmits it to the credit transaction server 20.
The purchase order creation unit 212 of the margin transaction program 200 receives order data including a transaction ID.

In step 210 (S210), the purchase order creation unit 212 issues a new purchase order ID, and creates purchase order data from the purchase order ID and the purchaser and settlement date included in the accepted purchase order data. And stored in the purchase order DB 294 (FIG. 14).
Further, the purchase order creation unit 212 stores data such as transaction ID, orderer, contractor, and amount included in the order data in the transaction DB 296 (FIG. 15).
In step 212 (S212), the purchase order creation unit 212 transmits a processing completion notification to the purchase management server 24.
The order processing unit 246 of the purchase management program 240 receives a processing completion notification.

In step 214 (S214), the order processing unit 246 transmits to the order receiving unit 242 that processing has been completed.
Upon receiving the processing completion notification from the order processing unit 246, the order receiving unit 242 transmits a procedure completion notification indicating that the transaction procedure has been completed to the orderer device 12 and the ordering device 14-1.

[Ordering operation of second transaction of margin trading system 1]
FIG. 24 is a sequence diagram showing the ordering operation (S30) of the second transaction that is ordered by the company B1 as the second trader in the transaction shown in FIGS.
As shown in FIG. 24, in step 300 (S300), the user of the company B1 inputs the company ID of the company B1 using the display / input device 110 of the orderer apparatus 12, and a list of purchase orders held by the company B1. Request.
The purchase order request unit 142 of the ordering program 140 transmits the input company ID to the margin transaction server 20.

Upon receiving the transmitted request, the purchase order viewing accepting unit 208 of the margin transaction program 200 searches the transaction DB 296 based on the company ID included in the request, and the transaction in which the company B1 is the orderer or the contractor. Search for.
The purchase order browsing reception unit 208 searches the purchase order DB 294 based on each purchase order ID included in each searched transaction.
The purchase order browsing reception unit 208 creates a purchase order list of the company B1 from the searched information.
The purchase order list includes at least a purchase order ID of a purchase order possessed by the company B1, and may further include an orderer, a settlement date, a transaction ID, a transaction amount, or an order item.

In step 302 (S302), the purchase order viewing receiving unit 208 transmits the created purchase order list to the order receiving apparatus 14-1 of the company B1 that is the request source.
The purchase order request unit 142 receives the transmitted purchase order list and displays it on the display / input device 110.
The user of the company B2 selects a purchase order that is divided and used for payment of the transaction from the displayed purchase order list.

In step 304 (S304), the user of the company B1 uses the display / input device 110 of the ordering / order receiving device 14 to input the purchase order ID of the selected purchase order and the ordering data related to the transaction to be ordered.
The split ordering unit 144 of the ordering program 140 includes the input purchase order ID in the ordering data, and transmits this ordering data to the purchase management server 24.

In step 202 (S202) and step 204 (S204), the order confirmation is performed by the order receiving unit 242 and the order confirmation requesting unit 244 of the purchase management program 240 as in the case of the first transaction.
Similarly, in step 206 (S206), a unique transaction ID is issued by the order processing unit 246.

In step 306 (S306), the order processing unit 246 of the purchase management program 240 further includes the issued transaction ID in the order data including the purchase order ID, and transmits it to the credit transaction server 20.
The purchase order dividing unit 214 of the margin transaction program 200 accepts order data including a purchase order ID and a transaction ID.

In step 308 (S308), the purchase order dividing unit 214 stores the order data including the purchase order ID and the transaction ID in the transaction DB 296.
Among the data stored in the transaction DB 296, at least one or more data is data that already includes this purchase order ID. Therefore, when the received order data is stored, at least two or more data are stored. This purchase order ID is included.
In this way, the purchase order is divided as the number of transactions associated with one purchase order ID increases.

In step 310 (S310), like the purchase order creation unit 212, the purchase order splitting unit 214 transmits a processing completion notification to the purchase management server 24.
The order processing unit 246 of the purchase management program 240 receives a processing completion notification.
In step 214 (S214), the order processing unit 246 and the order receiving unit 242 of the purchase management program 240 perform procedure completion notification processing as in the case of the first transaction.

[Acceptance operation of margin trading system 1]
FIG. 25 is a sequence diagram showing a transaction object inspection operation (S40) in the transaction shown in FIGS.
As shown in FIG. 25, in step 400 (S400), the user of the company B1 who has received an order for the transaction uses the ordering / order receiving device 14-1 to input that the transaction object has been delivered.
The delivery contact unit 148 of the ordering / ordering program 140 transmits the input delivery contact (delivery data) to the purchase management server 24.
The delivery accepting unit 248 of the purchase management program 240 accepts delivery notification from the ordering / order receiving device 14.

In step 402 (S402), the delivery accepting unit 248 transmits the accepted delivery report to the delivery processing unit 252.
Since the delivery processing unit 252 has received delivery notification regarding this transaction, the delivery processing unit 252 transmits an update instruction for this transaction to the margin transaction server 20.
The delivery management unit 216 of the margin transaction program 200 receives the delivered delivery notification.

In step 404 (S404), the delivery management unit 216 checks the delivered flag of this transaction data stored in the transaction DB 296 based on the transaction ID of this transaction.
By checking the delivered flag, the status of the transaction is updated, and it can be seen that the transaction has already been received.

In step 406 (S406), the delivery management unit 216 transmits a processing completion notification to the purchase management server 24.
The delivery processing unit 252 of the purchase management program 240 receives a processing completion notification.
In step 408 (S408), the delivery processing unit 252 sends a message to that effect to the delivery accepting unit 248, and the delivery accepting unit 248 sends an acceptance request to the acceptance requesting unit 250 to verify the transaction object. Let
The acceptance requesting unit 250 transmits an acceptance request to the orderer apparatus 12.
The acceptance unit 126 of the orderer program 120 receives the acceptance request from the purchase management server 24 and displays the contents on the display / input device 110.

In step 410 (S410), when the user of the company A confirms this content and inputs the inspection using the display / input device 110, the inspection unit 126 sends the input inspection notification to the purchase management server 24. Send to.
The acceptance requesting unit 250 of the purchase management program 240 receives the sent acceptance notification.

In step 412 (S412), the acceptance requesting unit 250 transmits that fact to the delivery accepting unit 248, and the delivery accepting unit 248 causes the delivery processing unit 252 to update the status of this transaction.
The delivery processing unit 252 further transmits an update instruction for the transaction to the margin transaction server 20 in order to make the status of the transaction accepted.
The delivery management unit 216 of the margin transaction program 200 accepts the sent acceptance notification.

In step 414 (S414), the delivery management unit 216 checks the accepted flag of this transaction data stored in the transaction DB 296 based on the transaction ID of this transaction.
By checking this acceptance flag, the state of this transaction is further updated, and it becomes clear that the orderer has already accepted the transaction object in this transaction.

In step 416 (S 416), the delivery management unit 216 transmits a process completion notification to the purchase management server 24.
The delivery processing unit 252 of the purchase management program 240 receives a processing completion notification.
In step 418 (S418), the delivery processing unit 252 transmits a message to that effect to the delivery accepting unit 248, and the delivery accepting unit 248 sends a transaction procedure to the orderer apparatus 12 and the ordering ordering apparatus 14-1. Send a notification of completion of the procedure to indicate that is completed.

As described above, the acceptance operation of the transaction (first transaction) between the company A and the company B1 is performed by the credit transaction server 20 and the purchase management server 24 between the orderer apparatus 12 and the ordering / order receiving apparatus 14-1. This is done by mediating data transmission / reception between them and updating the data stored in the transaction DB 296.
The acceptance operation of the transaction (second transaction) between the company B1 and the company B2 is performed in the same manner.

[Settlement processing of margin trading system 1]
FIG. 26 is a flowchart showing the transaction settlement processing (S50) shown in FIGS.
As shown in FIG. 26, in step 500 (S500), the settlement unit 226 of the margin transaction program 200 determines whether or not it is the settlement date of each purchase order data stored in the purchase order DB 294.
If it is not yet the settlement date, the settlement unit 226 returns to the process of S500, and if it is the settlement date, proceeds to the process of S502.

In step 502 (S502), the settlement unit 226 refers to the transaction DB 296 based on the purchase order ID and the company ID that is the orderer of this purchase order, and the transaction data (the first item) where the orderer is the company ID. 1 transaction data).
The settlement unit 226 determines whether or not the accepted flag of the retrieved transaction data is checked.
If the verification flag is not checked, the settlement unit 226 ends the settlement process. If it is checked, the settlement unit 226 proceeds to the process of S504.
The transaction to be settled is the first transaction and the second transaction carried out due to the first transaction, which is associated with the purchase order on the settlement date, and the orderer of the first transaction Becomes a transaction in which the transaction object has been accepted.
That is, the transactions to be settled are transactions that are ordered by issuing a purchase order that is a settlement date, and transactions that are ordered by dividing the purchase order.

In step 504 (S504), the settlement unit 226 causes the consideration calculation unit 220 to calculate the consideration paid by each company and the consideration paid.
The consideration calculation unit 220 refers to the transaction DB 296 based on the purchase order ID and searches for all transactions associated with the purchase order ID.
Further, the consideration calculation unit 220 refers to the orderer and the contractor of each of the searched transactions, calculates the consideration paid and the consideration paid for each of the enterprises that are the orderer and the contractor, and sets the calculation result to the settlement unit. Output to H.226.

In step 506 (S506), the settlement unit 226 causes the usage fee calculation unit 222 to calculate a service usage fee paid by each company.
The usage fee calculation unit 222 searches the purchase order DB 294 and the transaction DB 296 for the amount of consideration for each transaction, multiplies this amount by a certain percentage, calculates the service usage fee paid by each company, and calculates the calculation result. Output to the settlement unit 226.

In step 508 (S508), the settlement unit 226 causes the fee calculation unit 224 to calculate a split fee paid by the order-receiving company.
The fee calculation unit 224 refers to the transaction DB 296 and the transaction DB 296 based on the company ID and the purchase order ID, respectively, and searches for all the purchasers of the transactions that have been ordered by dividing a certain purchase order.
Further, the fee calculation unit 224 calculates a division fee by multiplying the amount of each transaction searched from the transaction DB 296 by a predetermined ratio, and the calculated division fee is evenly distributed to each of the ordering parties searched for. Divide the split fee evenly so that it is distributed.
The fee calculation unit 224 outputs the company to which the division fee is paid and the calculated division fee to the settlement unit 226.

In step 510 (S510), the settlement unit 226 pays or receives the amount paid by each company based on the consideration paid and received, the service usage fee paid, and the split commission paid and the split commission received. Is calculated.
The settlement unit 226 searches for the account number of each company from the company DB 292 based on the company ID, and sends the searched account number and the amount paid or received by each company to the outside via the financial network 102. Notify financial institutions and instruct payment.
Here, an external financial institution performs deposit / withdrawal processing with an accounting system (not shown) of each company via the financial network 102.
Regarding the amount paid or received by the margin transaction center 2, the accounting server 28 of the margin transaction center 2 uses the withdrawal processing unit 282 and the deposit processing unit 284 of the accounting program (FIG. 19) executed on the accounting server 28, Perform deposit / withdrawal processing.

In step 512 (S512), the settlement unit 226 checks the settlement flag of the purchase order data stored in the purchase order DB 294 based on the purchase order ID of the purchase order associated with the settled transaction. To do.
By checking the settled flag in the purchase order data, it becomes possible to know that all the transactions associated with the purchase order have been settled.

As described above, according to the margin trading system 1, each company included in the trading group / partner company uses the credit of the company A to divide the purchase order issued by the company A, The amount spent can be used to pay for transactions, thus freeing up concerns about cash flow preparation and freeing up concerns about payment defaults.
In addition, since the ordering company can obtain a division fee by issuing or dividing a purchase order to place a transaction, the use of the purchase order division service can be promoted.

[Second Embodiment]
Next, a credit transaction system 1 according to a second embodiment of the present invention will be described.
In the present embodiment, the division fee is calculated as a fixed amount per transaction received by the ordering company, and the calculated amount is paid non-equally distributed to each ordering company. Different from the first embodiment.

FIG. 27 is a diagram exemplifying a division fee paid by the company B2 in the transaction according to the second embodiment.
As shown in FIG. 27, the division fee is calculated as a fixed amount for each transaction, is distributed unevenly, and is paid to each of the ordering companies (FIG. 4 (a), FIG. 6 (a), FIG. 7 (b) and FIG. 8 (b)).
In other words, when company A places an order with company B1 and company B1 places an order with company B2, the division fee is set to a predetermined amount (for example, 3 million) for the transaction that company B2 has received from company B1. For example, 2 million is paid to the company B1 and 1 million is paid to the company A.

The fee calculation unit 224 of the margin transaction program (FIG. 12) searches all transactions for which the company ID is a contractor from the transaction DB 296 based on the company ID, and charges a fixed amount for each searched transaction. And
Next, the fee calculation unit 224 searches all transactions including the purchase order ID from the transaction DB 296 based on the purchase order ID included in the searched transaction, and refers to the orderer of the transaction.

Furthermore, the fee calculation unit 224 distributes the division fee so that the division fee is distributed non-uniformly to each searched orderer.
The fee calculation unit 224 distributes, for example, so that lower-level companies in FIG. 27 receive a larger amount of money.
The fee calculation unit 224 outputs the company to which the division fee is paid and the calculated division fee to the settlement unit 226.

  As explained above, the split fee is calculated as a fixed amount per transaction received by the contracting company, and more payment is made to the lower order companies among the ordering companies. Companies can also get more split fees and can facilitate the use of purchase order split services.

[Third Embodiment]
Next, a credit transaction system 1 according to a third embodiment of the present invention will be described.
In the present embodiment, the division fee is calculated for the amount of the balance of the purchase order on the predetermined reference date, and the calculated amount is paid non-equally distributed to each ordering company. Thus, it is different from the first embodiment.

FIG. 28 is a diagram exemplifying a division fee paid by the company B3 in the transaction according to the third embodiment.
As shown in FIG. 28, the division fee is calculated by multiplying the amount of the purchase order remaining on the order receiving company's hand on the predetermined reference date and multiplying this amount by a predetermined ratio, and is distributed unevenly. Then, payment is made to each of the ordering companies (FIGS. 4A, 6B, 7A and 8B).
In other words, when company A places an order with company B1, company B1 places an order with company B2, and company B2 places an order with company B3, the division fee is calculated based on the purchase order on the predetermined reference date. The amount remaining in hand of company B3 (for example, 100 million) as a balance is calculated as the balance, calculated by multiplying this amount by a predetermined ratio (for example, 1%), and distributed unevenly, for example, to company B2 In contrast, 500,000 is paid, 300,000 is paid to the company B1, and 200,000 is paid to the company A.

The fee calculation unit 224 of the margin transaction program (FIG. 12) searches all purchase orders for which the settled flag is not checked from the purchase order DB 294 on a predetermined reference date (for example, settlement date).
Next, the fee calculation unit 224 searches all transactions including the purchase order ID from the transaction DB 296 based on the purchase order ID included in the searched purchase order, and determines the orderer and contractor of each transaction. And refer to the amount.
In this way, the fee calculation unit 224 calculates the amount of money remaining in each of the order-receiving companies as the balance of the purchase order on the predetermined reference date.

Furthermore, the fee calculation unit 224 distributes the division fee so that the division fee is distributed non-uniformly to each searched orderer.
The fee calculation unit 224 distributes, for example, so that a lower-level company in FIG. 28 receives a larger amount of money.
The fee calculation unit 224 outputs the company to which the division fee is paid and the calculated division fee to the settlement unit 226.

  As explained above, the split fee becomes higher as the balance of the purchase order on the specified base date increases, and each company reduces the split fee by splitting the purchase order and placing a transaction and reducing the balance. As a result, the use of the purchase order split service can be promoted.

[Fourth Embodiment]
Next, a credit transaction system 1 according to a fourth embodiment of the present invention will be described.
This embodiment is different from the first embodiment in that the division fee is calculated as a fixed amount per purchase order on a predetermined reference date.

FIG. 29 is a diagram exemplifying a division fee paid by the company B3 in the transaction according to the fourth embodiment.
As shown in FIG. 29, the division fee is calculated as a certain amount per purchase order remaining on the order receiving company on a predetermined reference date, and is equally distributed and paid to each of the ordering companies. (FIG. 4 (a), FIG. 6 (b), FIG. 7 (b) and FIG. 8 (a)).
In other words, if company A places an order with company B1, company B1 places an order with company B2, and company B2 places an order with company B3, the division fee is determined by company B3 on the predetermined reference date. It is calculated as a predetermined amount (for example, 1.5 million) per purchase order remaining at hand, and is distributed evenly, for example, 500,000 is paid to company B2, 500,000 is paid to company B1, Company A is paid 500,000.

The fee calculation unit 224 of the margin transaction program (FIG. 12) searches all purchase orders for which the settled flag is not checked from the purchase order DB 294 on a predetermined reference date (for example, settlement date).
Next, the fee calculation unit 224 searches the transaction DB 296 for all transactions including this purchase order ID based on the purchase order ID included in the searched purchase order, and each orderer and contractor of each transaction. Refer to
In this manner, the fee calculation unit 224 searches for purchase orders remaining on the order receiving companies on a predetermined reference date, and sets a predetermined amount as the split fee for each purchase order.

Further, the fee calculation unit 224 distributes the division fee so that it is equally distributed to each searched orderer.
The fee calculation unit 224 outputs the company to which the division fee is paid and the calculated division fee to the settlement unit 226.

  As explained above, the split fee becomes higher as more purchase orders remain on the specified base date, and each company can reduce the split fee by shortening the period until the settlement date. Use of the purchase order split service can be promoted.

It is a figure which illustrates the transaction by the transaction method concerning this invention. It is a figure which shows the relationship between a trading group and a business partner, and a margin trading center. It is a figure which shows the profit model of transaction. It is a figure which illustrates the split commission paid to the ordering company from the contracting company of the transaction. (A) is a case where the contracting company pays the split commission to all the ordering companies that issued or split the purchase order. (B) shows a case where the order-receiving company pays a split fee to the ordering company of the transaction. It is the figure which shows the fund of the split commission which is paid from the order side enterprise, (a) shows the case where the part of the amount of the purchase order which remains at hand is used for the split commission, (b) remains at hand The case where a part of the purchase order amount is not allocated to the split fee is shown. It is a figure which shows the calculation object of a division fee, (a) shows the case where the consideration paid with respect to a transaction is made into the calculation object of a division fee, (b) is the purchase order which remains at hand on a predetermined day This is a case in which the amount of payment (the amount obtained by subtracting the amount to be paid from the amount to be paid) is subject to calculation of the division fee. It is a figure which shows the calculation method of a division fee, (a) shows the case where the predetermined ratio of the amount of calculation object is made into a division fee, (b) shows the case where a fixed amount is set for every calculation object Show. It is a figure which shows the distribution method of a split commission, (a) shows the case where a split commission is equally distributed with respect to an ordering company, (b) is a non-equal split with respect to an ordering company Shows the case of being distributed. It is a figure which illustrates the division | segmentation commission which company B2 pays in the transaction concerning the 1st Embodiment of this invention. It is a figure which illustrates the composition of margin transaction system 1 concerning the present invention. It is a figure which illustrates the hardware constitutions of the computer used in each node shown in FIG. It is a figure which shows the structure of the margin transaction program 200 performed on the margin transaction server 20 shown in FIG. It is a figure which shows the structure of the company database (DB) 292 which manages the information of each company. It is a figure which shows the structure of purchase order DB294 which manages the information of each purchase order issued from the company which is a 1st trader. It is a figure which shows the structure of transaction DB296 which manages the information of each transaction between an orderer and an order receiver. It is a figure which shows the reference relationship with company DB292, purchase order DB294, and transaction DB296. It is a figure which shows the structure of the purchase management program 240 performed on the purchase management server 24 shown in FIG. It is a figure which shows the structure of the member management program 260 performed on the member management server 26 shown in FIG. It is a figure which shows the structure of the accounting program 280 performed on the accounting server 28 shown in FIG. It is a figure which shows the structure of the orderer program 120 performed on the orderer apparatus 12 shown in FIG. It is a figure which shows the structure of the ordering / ordering program 140 performed on the ordering / order receiving apparatus 14 shown in FIG. It is a sequence diagram which shows the registration operation | movement (S10) of the company contained in the transaction group and the business partner company shown in FIG. FIG. 3 is a sequence diagram showing an ordering / ordering operation (S20) of a first transaction ordered by a company A as a first trader in the transaction shown in FIGS. 1 and 2; FIG. 5 is a sequence diagram showing an ordering / ordering operation (S30) of a second transaction ordered by a company B1 which is a second trader in the transaction shown in FIGS. 1 and 2; It is a sequence diagram which shows the acceptance operation | movement (S40) of the transaction target object in the transaction shown in FIG. 1 and FIG. It is a flowchart which shows the payment process (S50) of the transaction shown in FIGS. It is a figure which illustrates the division | segmentation commission which company B2 pays in the transaction concerning 2nd Embodiment. It is a figure which illustrates the division | segmentation commission which company B3 pays in the transaction concerning 3rd Embodiment. It is a figure which illustrates the division | segmentation commission which company B3 pays in the transaction concerning 4th Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Credit transaction system 12 ... Orderer apparatus 14 ... Order receiving / ordering apparatus 100 ... Network 102 ... Financial network 104 ... CPU
DESCRIPTION OF SYMBOLS 106 ... Memory 108 ... Device main body 110 ... Display / input device 114 ... Storage device 116 ... Recording medium 2 ... Credit transaction center 20 ... Credit transaction server 200 ... Credit Transaction program 202 ... UI unit 204 ... Authentication / communication processing unit 206 ... Member management unit 208 ... Purchase order viewing acceptance unit 210 ... Transaction management unit 212 ... Purchase order creation unit 214 .. purchase order division unit 216... Delivery management unit 218... Settlement management unit 220 .. consideration calculation unit 222 .. usage fee calculation unit 224 .. commission calculation unit 226 .. settlement unit 292 ..Company DB
294 ... Purchase order DB
296 ... Transaction DB
24 ... Purchase management server 240 ... Purchase management program 242 ... Order acceptance unit 244 ... Order confirmation request unit 246 ... Order processing unit 248 ... Delivery acceptance unit 250 ... Inspection request unit 252 ... Delivery processing unit 26 ... Member management server 260 ... Member management program 262 ... Membership processing unit 264 ... Resignation processing unit 28 ... Accounting server 280 ... Accounting program 282 ...・ Withdrawal processing unit 284 ... Deposit processing unit 290 ... Network within the center

Claims (12)

A transaction management device connected to a plurality of transaction devices, wherein in each of the transactions, the other transaction devices for each of the transaction devices are classified into an order side and an order side, and from the order side to the order side For each transaction, each transaction device other than a transaction device that receives a payment and can place an order for an arbitrary transaction receives an order from another transaction device. Within the scope of the price paid for a given order, place an order for another ordering transaction device and pay a commission to each of one or more of the ordering transaction devices,
Corresponding to each of the transactions, an order of an arbitrary transaction associated with the transaction, the transaction device that has ordered the transaction, the transaction device that has received an order for the transaction, and a consideration paid for the transaction Transaction data storage means for storing stored transaction data;
Based on the stored transaction data, each of the transaction devices calculates a consideration paid to another transaction device, or a consideration calculation means for calculating a consideration paid from another transaction device;
Fee calculation means for calculating the fee based on the stored transaction data;
A transaction management device comprising: a settlement unit that settles an amount paid by each transaction device or an amount to be paid based on the calculated consideration and a fee. A purchase order data storage means for storing purchase order data in which the order of the arbitrary transaction is associated with the transaction apparatus that has ordered the transaction;
The transaction management apparatus according to claim 1, wherein each of the stored transaction data includes an identifier for identifying the purchase order data, and is associated with one of the stored purchase order data by the identifier. The settlement means settles so that the contractor in the stored transaction pays the fee to each orderer of a transaction further associated with an order of any transaction with which the transaction is associated. The transaction management device according to claim 2. The transaction management apparatus according to any one of claims 1 to 3, wherein the settlement unit performs settlement so that the calculated fee is paid as a source of consideration paid to the transaction apparatus for each of the transaction apparatuses. . The fee calculation means searches for a transaction for which the transaction device is a contractor for each of the transaction devices from the stored transaction, and calculates a fee according to a consideration paid for the searched transaction. The transaction management device according to any one of claims 1 to 4. The fee calculation means searches for transactions in which the transaction device is an orderer or a contractor for each of the transaction devices on a predetermined reference date from the stored transactions. The transaction management device according to any one of claims 1 to 4, wherein a fee is calculated according to an amount that can be ordered. 2. The fee calculation means searches, for each of the transaction devices, a transaction for which the transaction device is a contractor from the stored transaction, and sets a certain amount for the retrieved transaction as a fee amount. The transaction management apparatus in any one of -4. The transaction management apparatus according to claim 5, wherein the fee calculation unit sets a predetermined ratio of the amount to be calculated as a fee amount. The transaction management apparatus according to any one of claims 5 to 8, wherein the fee calculation means calculates the fee so that the fee is evenly distributed to each orderer of a transaction that can pay the fee. A transaction system having a plurality of transaction devices and a transaction management device connected to the plurality of transaction devices, wherein in the transaction, the other transaction devices for each of the transaction devices are classified into an ordering side and an order receiving side. A fee is paid from the ordering side to the ordering side, a fee is paid from the ordering side to the ordering side, and the plurality of transaction devices include a first transaction device and a first transaction device. And a second transaction device other than the transaction device
Each of the first transaction devices
Each of the transactions has a first ordering means capable of placing an order for an arbitrary transaction with another transaction device,
Each of the second transaction devices
In each of the transactions, an order receiving means for receiving an order for a transaction ordered from another transaction device;
In each of the above transactions, a second ordering means for placing an order for a transaction with another transaction device on the order receiving side within a range of consideration paid for the transaction ordered from the transaction device on the ordering side,
The transaction management device includes:
Corresponding to each of the transactions, an order of an arbitrary transaction associated with the transaction, the transaction device that has ordered the transaction, the transaction device that has received an order for the transaction, and a consideration paid for the transaction Transaction data storage means for storing stored transaction data;
Based on the stored transaction data, each of the transaction devices calculates a consideration paid to another transaction device, or a consideration calculation means for calculating a consideration paid from another transaction device;
Fee calculation means for calculating the fee based on the stored transaction data;
A transaction system comprising: a settlement unit that settles an amount paid by each transaction device or an amount to be paid based on the calculated consideration and a fee. A transaction management method performed between a plurality of transaction devices. In each of the transactions, the other transaction devices for each of the transaction devices are classified into an order side and an order side, and from the order side to the order side. On the other hand, each of the transaction devices other than the transaction device that is paid for and can place an arbitrary transaction in each of the transactions receives an order from another transaction device, and in each of the transactions, from the ordering transaction device Within the range of consideration paid for the received order, place an order for another ordering transaction device, pay a fee for each of one or more of the ordering transaction devices,
Corresponding to each of the transactions, an order of an arbitrary transaction associated with the transaction, the transaction device that has ordered the transaction, the transaction device that has received an order for the transaction, and a consideration paid for the transaction Store transaction data,
Based on the stored transaction data, each transaction device calculates a price paid to another transaction device, or a price paid from another transaction device,
Calculate the fee based on the stored transaction data,
A transaction management method that settles an amount to be paid or an amount to be paid by each of the transaction devices based on the calculated consideration and a fee. A transaction management device including a computer and connected to a plurality of transaction devices, wherein in each of the transactions, the other transaction devices for each of the transaction devices are classified into an ordering side and an order receiving side, Consideration is paid to the order-receiving side, and each of the transaction devices other than the transaction device that can place an order for any transaction in each of the transactions receives an order from another transaction device. A transaction management device that places an order with respect to another ordering transaction device within a range of consideration paid for the order received from the transaction device and pays a commission to each of one or more of the ordering transaction devices In
Corresponding to each of the transactions, an order of an arbitrary transaction associated with the transaction, the transaction device that has ordered the transaction, the transaction device that has received an order for the transaction, and a consideration paid for the transaction A transaction data storage step for storing stored transaction data;
Based on the stored transaction data, each transaction device calculates a consideration paid to another transaction device, or a consideration calculation step for calculating a consideration paid from another transaction device;
A fee calculating step of calculating the fee based on the stored transaction data;
A program for causing the computer to execute a settlement step for settlement of an amount to be paid or an amount to be paid based on the calculated consideration and a fee.

Images