JP7548628B2 - Financial product transaction management device, financial product transaction management method, and program - Google Patents

Description

The present invention relates to technology for managing and supporting transactions of financial products such as foreign exchange.

As a method of trading financial products such as foreign exchange, limit orders are known in addition to market orders, which trade at the price at the time of the order. A limit order is an order form in which a customer specifies a buying and selling price in advance, and a financial product dealer places a buy order for the target financial product when the price of the financial product falls to the specified price, and places a sell order for the financial product when the price rises to the specified price. Conventionally, there are known inventions that use computer systems to place limit orders for financial products (see, for example, Patent Document 1). On the other hand, limit orders for financial products often include if-done orders (an order form in which two prioritized orders are placed simultaneously, and when the first-priority order is filled, the second-priority order is automatically made effective; the same applies throughout this specification). In addition, a system is known that automatically places if-done orders while avoiding risk (see, for example, Patent Document 2).

JP 2006-99787 A JP 2008-130002 A

However, the invention described in the cited document 1 has a problem in that it cannot handle limit orders for if-done orders. In addition, the invention described in the cited document 2 is configured so that only first-priority orders are executed when the market price reaches one price, and only second-priority orders are executed when the market price reaches another price, which creates a problem in that profit-making opportunities that would otherwise exist are missed.

The present invention was made in consideration of the above problems, and aims to provide a financial product transaction management device that enables customers using the system to make limit orders for financial products without having to go through complicated ordering procedures, while avoiding risks and taking full advantage of profit opportunities to carry out rational transactions.

In order to achieve this object, the invention described in claim 1 is a financial product transaction management device that manages the buying and selling of financial products, and includes a market price information acquisition means for acquiring market price information of the financial products, an order information generation means for generating order information of the financial products generated based on buying and selling order application information for placing an order for a transaction of one of the financial products, and a contract information generation means for carrying out a transaction to contract the order based on processing of the order information generated by the order information generation means, and the order information generation means generates a pre-order information for a first order as an order to place one transaction of the financial products when the market price becomes a first price, the pre-order information being generated based on one of the buying and selling order application information. The execution information generating means repeats the steps of generating one or more first order information as the order information, and generating one or more second order information as the order information of a second order as an order for executing one transaction of the financial product when the market price of the financial product becomes the second price, and the execution information generating means repeats the steps of executing a transaction to execute one or more of the first orders based on processing one or more of the first order information when the market price of the financial product becomes the first price, and executing a transaction to execute one or more of the second orders based on processing one or more of the second order information when the market price of the financial product becomes the second price.

The invention described in claim 2 is characterized in that, in addition to the configuration described in claim 1, the order information includes order status information that determines whether the order information is in an uncontracted state or a contracted state, and the contract information generating means converts the order status information from the uncontracted state to the contracted state when the first order based on the first order information and the second order based on the second order information are contracted.

The invention described in claim 3 is characterized in that, in addition to the configuration described in claim 1 or 2, a specific order information group among the plurality of order information groups includes third order information that places a stop order to sell at a price lower than the first order based on the first order information and the second order based on the second order information, and another order information group of the specific order information group includes fourth order information that places a stop order to buy at a price higher than the first order based on the first order information and the second order based on the second order information, and when the stop order based on the third order information or the stop order based on the fourth order information is executed, the execution information generating means cancels all of the order information related to the unexecuted orders that form the order information group.

The invention described in claim 4 is a financial product transaction management method performed in a financial product transaction management device that manages the buying and selling of financial products, comprising a market price information acquisition procedure performed in a market price information acquisition means that acquires market price information of the financial product, an order information generation procedure in which order information of a financial product is generated based on buying and selling order application information for placing an order for a transaction of one type of the financial product, and a contract information generation procedure in which a transaction is performed to contract the order based on processing of the order information generated in the order information generation procedure, and in the order information generation procedure, an order for placing a transaction of one of the financial products when the market price, generated based on one of the buying and selling order application information, becomes a first price. The method is characterized in that the method repeatedly generates one or more first order information as the order information of a first order as a statement, and generates one or more second order information as the order information of a second order as an order to trade one of the financial products when the market price becomes the second price, and in the contract information generation procedure, when the market price of the financial product becomes the first price, a transaction is executed to contract one or more of the first orders based on processing one or more of the first order information, and when the market price of the financial product becomes the second price, a transaction is executed to contract one or more of the second orders based on processing one or more of the second order information.

The invention described in claim 5 is a program that causes a computer to function as a financial product transaction management device described in any one of claims 1 to 3.

According to the invention described in claims 1 and 4, one or more first order information is generated as order information for a first order as an order for performing one transaction of a financial product when the market price becomes a first price, which is generated based on one buy/sell order application information, and one or more second order information is generated as order information for a second order as an order for performing one transaction of a financial product when the market price becomes a second price. When the market price of the financial product becomes the first price, one or more first orders are executed based on the processing of the first order information, and when the market price of the financial product becomes the second price, one or more second orders are executed based on the processing of the second order information. By repeating this process, when multiple order information groups are executed sequentially, one or more first order information and one or more second order information are executed, and the customer can earn higher profits than when only one order information is executed. This allows customers using the system to execute rational transactions by fully utilizing profit opportunities while avoiding risks without performing complicated order procedures.

According to the invention described in claim 2, it is possible to execute an order based on a first order information group having first order information and a second order information group, and to automatically repeat a transaction using an if-done order multiple times.

According to the invention described in claim 3, when third order information that places a stop-limit order to sell at a price lower than the first order information and the second order information, or fourth order information that places a stop-limit order to buy at a price higher than the first order information and the second order information, is executed, all unexecuted order information that forms the first order information group and the second order information group is cancelled, thereby preventing a situation in which the customer suffers a disadvantage due to the market price rising or falling below a certain price, and avoiding risk to the customer.

According to the invention described in claim 5, the financial product transaction management device of the present invention can be programmed and realized on various computer hardware.

1 is a system configuration diagram of a financial product transaction management system according to an embodiment of the present invention and a functional block diagram of a financial product transaction management device. 4 is a schematic diagram of field definitions in an order table of the financial product exchange management device. FIG. 4 is a schematic diagram of field definitions of a customer account information table of the financial product exchange management device. FIG. 2 is a schematic diagram of field definitions in a currency pair order condition table of the financial product exchange management device. FIG. 13 is a flowchart showing a processing procedure when a limit order is executed by an if-done order in the financial product exchange management device. 13 is a flowchart showing the basic procedure for placing an order and executing a contract based on first order information and second order information in the financial product transaction management device. 11 is a flowchart showing an ordering process and a contract process of order information of a new order information group in the financial product transaction management device. 13 is a flowchart showing a contract process as a stop-loss order at a stop-loss price in the financial product transaction management device. 13 is an image diagram of an input screen displayed on a display unit of the client terminal. 13 is an image diagram of an order history screen displayed on the display unit of a client terminal in the first contract procedure, and an image diagram showing the data structure of each order information item. 13 is an image diagram of an order history screen displayed on the display unit of a client terminal in the first contract procedure, and an image diagram showing the data structure of each order information item. 13 is a time chart of a first contract procedure. 13 is an image diagram showing an order history screen displayed on the display unit of the client terminal in the second contract procedure, and an image diagram showing the data structure of each order information item. 13 is a time chart of a second contract procedure. An image diagram of an order history screen displayed on the display unit of a client terminal in the third contract procedure, and an image diagram showing the data structure of each order information. 13 is a time chart of a third contract procedure.

One embodiment of the invention will be described below with reference to the drawings.

[System configuration and data structure]
1 is a system configuration diagram and a functional block diagram of a financial instruments transaction management system according to this embodiment. As shown in the figure, the financial instruments transaction management system 1A comprises a financial instruments transaction management device 1 and n (n≧1) client terminals 2 ₁ to 2 _n as online terminals. The financial instruments transaction management device 1 and the client terminals 2 ₁ to 2 _n are capable of communicating with each other via the Internet 3 as a WAN (Wide Area Network). The financial instruments transaction management system 1A according to this embodiment handles foreign exchange as a financial instrument.

The financial product transaction management device 1 is a server computer managed and operated by a financial product dealer, and manages the buying and selling of financial products. The financial product transaction management device 1 has a Web server function and a database function for storing large amounts of data. The client terminals 2 ₁ , ..., 2 _n are communication terminals with data communication functions that are owned and used by individuals or corporations who buy and sell financial products (i.e., users of the financial product transaction management system 1A), and correspond to personal computers, mobile phone terminals, etc. The client terminals 2 ₁ , ..., 2 _n have operation units 21 ₁ , ..., 21 _n used to input various instructions such as a mouse or keyboard, and display units 22 ₁ , ..., 22 _n consisting of an LCD (Liquid Crystal Display) or the like for displaying various instructions and various images input from the operation units 21 ₁ , ..., 21 _n . Since the client terminals 2 ₁ , ..., 2 _n , the operation units 21 ₁ , ..., 21 _n , and the display units 22 ₁ , ..., 22 _n have the same configuration, they will be referred to as the client terminal 2, the operation unit 21, and the display unit 22 hereinafter unless a distinction needs to be made.

Although not shown in FIG. 1, the financial product transaction management device 1 is equipped with at least one CPU (Central Processing Unit), a RAM (Random Access Memory) that functions as the CPU's working area, a ROM (Read Only Memory) in which a startup boot program and the like are recorded, an auxiliary storage device such as a hard disk in which various programs and data and the like are recorded, and a communication interface used for sending and receiving data. The auxiliary storage device records programs for the OS (Operating System), various application programs, data recorded in a database, and the like. These programs and data work in cooperation with hardware resources to realize various functions through the calculations of the CPU.

The financial product transaction management device 1 may be formed by a single server computer or multiple network computer systems.

As shown in FIG. 1, the financial product transaction management device 1 has a data processing unit 10 as a functional means realized based on the various programs and hardware resources described above, and a database 18 in which various data processed by the data processing unit 10 is recorded. The data processing unit 10 performs processes such as generating and processing various data used in the financial product transaction management device 1, and further has a front page distribution unit 11 as functional means, an order input reception unit (order input reception means) 12, a deposit/withdrawal information generation unit 13, a contract information generation unit (contract information generation means, record management means) 14, an account information generation unit 15, an order information generation unit (order information generation means) 16, a database (DB) connection base unit 17, and a price information reception unit (market price information acquisition means) 19.

The order input reception unit 12 receives data regarding various orders input from the client terminal 2 and performs various processes necessary to complete orders for financial products.

The deposit/withdrawal information generation unit 13 accepts deposit/withdrawal requests from the client terminal 2 and creates a list of deposits and withdrawals based on the requests.

The order information generation unit 16 generates information about executed orders for financial products based on the information processed by the order input reception unit 12. Orders here include so-called market orders, limit orders, and if-done orders.

In this embodiment, the financial product transaction management device 1 applies if-done orders only to new orders, simplifying the system configuration and creating a system that is easy for customers to use. Therefore, the order information generation unit 16 is configured to generate order information only for new orders.

The contract information generation unit 14 performs contract processing based on the order generated by the order information generation unit 16, and processing for sending information regarding the completed contract processing to the customer's client terminal 2. Note that "contract" here refers to various procedures and processing for completing the sale and purchase of financial products based on the customer's order. Furthermore, the contract information generation unit 14 records the order information generated by the order information generation unit 16 in the database 18, and manages the recording status of the order information in the database 18.

The account information generation unit 15 has a function of generating customer deposit balance information and managing the deposit balance information as margin information (i.e., information to verify that an order can be executed). The information on deposit balance generated by the account information generation unit 15 is periodically compared with information on the customer's actual deposit balance provided by financial institutions such as banks to ensure consistency with the actual deposit balance.

The database connection base unit 17 converts data generated and processed in the data processing unit 10 to data recorded in the database 18, and also performs the processing required to exchange data between the data processing unit 10 and the database 18.

The database 18 records data used by the financial product transaction management device 1. In this embodiment, the database 18 is formed by a relational database, but any format suitable for recording and rewriting large amounts of data, such as an object database, may be used. The database 18 records an order table (order information recording means) 181, a customer account information table 182, a currency pair order condition table 183, and a sequence number table 184. A sequence number uniquely assigned to each piece of order information (described later) is recorded in the sequence number table 184. The order table 181, the customer account information table 182, and the currency pair order condition table 183 will be described in detail later.

The front page delivery unit 11 creates image data to be displayed on the display unit 22 of the client terminal 2 and transmits the created image data to the client terminal 2.

The price information receiving unit 19 acquires market price information (market price information) of financial products handled by the financial product transaction management device 1, and performs necessary processing on the acquired information for use by the data processing unit 10. In this embodiment, the price information receiving unit 19 acquires market price information for foreign exchange.

In addition, the data processing unit 10, database 18, front page distribution unit 11, order input reception unit (order input reception means) 12, deposit/withdrawal information generation unit 13, contract information generation unit 14, account information generation unit 15, order information generation unit 16, database connection base unit 17, and price information reception unit 19 in the financial product transaction management device 1 may be configured in any form. For example, when the financial product transaction management device 1 is formed as a network computer system consisting of multiple server computers, each component may be distributed and arranged on multiple server computers. In addition, these server computers may be arranged across computer systems owned by multiple traders and server administrators (for example, computer systems owned or managed by financial securities exchanges, other financial product transaction management companies, providers, hosting system providers, etc.). The server computers may be formed as a so-called cloud computer system. Furthermore, at least some of the components of the data processing unit 10, database 18, front page distribution unit 11, order input reception unit (order input reception means) 12, deposit/withdrawal information generation unit 13, contract information generation unit 14, account information generation unit 15, order information generation unit 16, database connection base unit 17, and price information reception unit 19 may be provided in the client terminal 2, rather than in the financial product transaction management device 1.

Figure 2A is a schematic diagram of the field definitions of order table 181, Figure 2B is a schematic diagram of the field definitions of customer account information table 182, and Figure 2C is a schematic diagram of the field definitions of currency pair order condition table 183. As shown in these figures, each of tables 181, 182, and 183 has fields for the number of items. Each field is specified with a name (field name), a data type (type) such as characters, numbers, or date and time, a data length (length) such as bit length, a designation that the field cannot be left blank (Not Null), the presence or absence of a default value (default value), the data item name (remarks), etc.

In the above-mentioned financial product transaction management device 1, when limit orders for financial products are made, limit orders for multiple financial products of the same type can be made through multiple if-done orders with one reservation order.

[Transaction Procedure]
Next, a transaction procedure for limit orders using if-done orders in the financial product transaction management system 1A of this embodiment will be described.

[Order information generation procedure]
3 is a flow chart showing the processing steps when generating order information for a limit order by an if-done order in the financial product transaction management device 1 of this embodiment. The processing steps when placing an order will be described below with reference to this figure.

A customer using the financial product transaction management system 1A accesses the financial product transaction management device 1 using a client terminal 2. The front page distribution unit 11 of the financial product transaction management device 1 displays the input screen 40 shown in FIG. 7 on the display unit 22 of the accessed client terminal 2. The customer inputs order details data into the input screen 40 using the operation unit 21. Specifically, the following processes (Process 1) to (Process 4) are performed on the input screen 40.

(Process 1)
The input screen 40 is provided with buy/sell request input buttons 41 for selecting a tradable currency pair. The client selects the currency pair he/she wishes to buy/sell using the buy/sell request input button 41. In Fig. 7, "US Dollar (USD)/Japanese Yen (JPY)" is shown selected for buying/selling Japanese Yen and US Dollar.

(Process 2)
The input screen 40 is provided with an order condition selection button 43 for selecting the order conditions for a limit order. The client selects "Double Repeat If Done" which indicates the transaction form of this embodiment on the order condition selection button 43. Note that "Repeat If Done" refers to a transaction form in which one order causes the financial product transaction management device 1 to automatically and repeatedly perform if-done orders.

Then, as shown in FIG. 7, various buttons are provided on the input screen 40. These various buttons include a lower order price input field 44a for inputting a lower order price (hereinafter referred to as the "lower order price"), which is the lower order price of a new order or a settlement order, forming the "first order information" described later, an upper order price input field 44b for inputting an upper order price (hereinafter referred to as the "upper order price"), which is the higher order price of a new order or a settlement order, forming the "second order information" described later, an amount input field 44c for inputting the order amount for each order, an expiration display field 44d for displaying the expiration dates of the "first order information" and the "second order information", and a button for preventing the customer from suffering excessive disadvantages when the market price suddenly drops or rises. the first stop-loss price input field 44g for inputting the price of a stop-loss order lower than the lower order price and the upper order price (hereinafter referred to as the "first stop-loss price") which forms the "third order information" described later; the second stop-loss price input field 44h for inputting the price of a stop-loss order higher than the lower order price and the upper order price (hereinafter referred to as the "second stop-loss price") which forms the "fourth order information" described later; and an order confirmation button 45 for confirming the order details.

In addition, instead of either the lower order price input field 44a or the upper order price input field 44b, a profit amount designation field may be provided for inputting the profit amount when the first order and the second order are executed once. In this case, the order input acceptance unit 12 automatically calculates the upper order price (or lower order price) based on the price of the first order (or the price of the second order) input in the lower order price input field 44a (or the upper order price input field 44b) and the amount input in the amount input field 44c.

(Process 3)
The customer inputs desired values into each of these input fields and selects the desired transaction type, etc., using each selection button.

In FIG. 7, 80.00 yen is input in the lower order price input field 44a, 90.00 yen is input in the upper order price input field 44b, and 10,000 (currency) is input in the amount input field 44c. Also, in FIG. 7, a stop-loss order is selected using the stop-loss order selection buttons 44e and 44f, and 70.00 yen is input in the first stop-loss price input field 44g and 100.00 yen is input in the second stop-loss price input field 44h.

(Process 4)
After completing input and selection in each input field and each selection field, when the customer clicks the order confirmation button 45 provided on the input screen 40, the data entered on the input screen 40 is transmitted to the financial product transaction management device 1, and the procedure of step S2 described below is carried out. Note that if the customer clicks the reset button 46 instead of the order confirmation button 45, the above process is cancelled, and the input screen 40 returns to the state before the above (process 1) was carried out.

When the order confirmation button 45 is clicked in the above (Process 4) and the transmitted data is supplied to the financial instruments transaction management device 1, the order input reception unit 12 of the financial instruments transaction management device 1 confirms the contents of the input order. Specifically, it confirms the expiration date selected in the expiration date display field 44d, and further inspects the order price of the supplied data (Step S2). Specifically, the order input reception unit 12 performs the following inspection method 1 and inspection method 2.

(Testing method 1) The order input reception unit 12 compares the lower order price entered in the lower order price input field 44a and the upper order price entered in the upper order price input field 44b with the current exchange rate price received by the price information receiving unit 19. If the lower order price is equal to or lower than the current exchange rate price and the upper order price is equal to or higher than the current exchange rate price, the order input reception unit 12 performs a trading procedure according to the "first contract procedure" described below. If the lower order price and the upper order price are both higher than the current exchange rate price, the order input reception unit 12 performs a trading procedure according to the "second contract procedure" described below. If the upper order price is equal to or lower than the current exchange rate price, the order input reception unit 12 performs a trading procedure according to the "third contract procedure" described below.

(Testing method 2) The order input reception unit 12 compares the lower side price entered in the lower side order price input field 44a with the upper side order price entered in the upper side order price input field 44b for the currency pair selected using the buy/sell request input button 41. The order input reception unit 12 determines that the price is fair when the upper side order price is higher than the lower side order price.

If the lower order price and the upper order price are judged to be fair prices ("No" in step S3), the account information generation unit 15 obtains the margin information of the customer from the customer account information table 182. Specifically, the numerical data recorded in the "amnt" field 182a shown in FIG. 2B is obtained as the margin information.

The order input acceptance unit 12 compares the acquired margin information with the customer's total order amount (i.e., the total order amount calculated based on the values entered in each input field 44a, 44b, 44g, 44h) and checks whether the margin amount is equal to or greater than the total order amount. The order information generation unit 16 generates an "order information group" (described later) only when the margin amount is equal to or greater than the total order amount ("No" in step S5). This allows limit orders using if-done orders to be accepted only when the customer is able to reliably make payment.

If the margin amount is equal to or greater than the total order amount ("No" in step S5), the order input reception unit 12 checks whether the order conditions satisfy various conditions for if-done orders other than those described above, based on the data recorded in the currency pair order conditions table 183 (step S6).

If the various conditions for the if-done order are not met ("Yes" in step S7), the order input reception unit 12 treats the entered order as an error and rejects the order (step S10).

If the various conditions for an if-done order are met ("No" in step S7), and it is determined that the order conditions meet all of the conditions necessary for a limit order via an if-done order described above, the front page distribution unit 11 displays a confirmation screen (not shown) on the display unit 22 of the client terminal 2. The confirmation screen (not shown) lists the order conditions entered and selected by the customer on the input screen 40, and has an approval button (not shown) that is clicked if the listed contents are correct.

When the customer clicks the approval button (not shown) by operating the operation unit 21, the order information generation unit 16 of the financial product transaction management device 1 generates order information based on the data entered in step S1 (step S8). Specifically, the multiple pieces of data entered in the above procedure are grouped together in units of order prices, and each piece of order information is formed by assigning a sequence number to the order recorded in the sequence number table 184 for each unit of information. The multiple pieces of order information formed in one step S8 procedure generate multiple pieces of order information (hereinafter simply referred to as "order information groups") that at least have order information for placing limit orders for multiple financial products of the same type at two prices (i.e., a lower order price and an upper order price) for a certain number of products.

The order information generating unit 16 records the generated order information group in the order table 181 (step S9). Specifically, the corresponding order information (i.e., data corresponding to the items in the "Notes" column 181a) is recorded in each field shown in FIG. 2A. For example, the sequence number assigned in step S8 is recorded in the "ord_seq" field 181b. The "cust_seq" field 181c records a customer number uniquely determined for each customer, and the "style_id" field 181d records the product name. The "ccy_pair_id" field 181e records an ID number uniquely determined for each currency pair. The combination of this ID number and the currency pair is recorded in an ID table (not shown) separately provided in the database. The "ord_amnt" field 181f records the order amount for each order information. The "buy_sell_id" field 181g records data indicating whether it is a sell order or a buy order, the "ord_rate" field 181h records the order price, and the "limit_time" field 181i records the order price. The "ord_cond" field 181j records "1" indicating that the order type is an if-done order. The "ifd_ord_seq" field 181k records the sequence number of the if-done order. The "new_close" field 181m records data indicating whether it is a new order or a continuing order (settlement order). With the above steps, order processing for a limit order using an if-done order in this embodiment is completed.

[Generation of order information and order information groups]
When the order processing is completed, the order information generation unit 16 first generates the first two order information groups (hereinafter referred to as the "first order information group" and the "second order information group" respectively). (a2) and (b2) of FIG. 8 and (c2) of FIG. 9 show image diagrams of the order information groups and the order information constituting them. As shown in the figures, the first order information 51A, 51D, the second order information 51B, 51E, the third order information 51C, and the fourth order information 51F are constituted in a state where the data inputted to the input screen 40 (see FIG. 7) is inputted into the fields of the order table 181 (see FIG. 2A). The first order information 51A, the second order information 51B, and the third order information 51C constitute the first order information group 50A, and the first order information 51D, the second order information 51E, and the fourth order information 51F constitute the second order information group 50B.

As shown in FIG. 8 and FIG. 9, each of the first order information 51A, 51D is configured as information for placing a limit order to buy the same type of financial product at one price (lower order price). Each of the second order information 51B, 51E is configured as information for placing a limit order to sell the same type of financial product at another price (upper order price). The third order information 51C is configured as information for placing a stop-loss order to sell at a first stop-loss price lower than the first order information 51A, 51D and the second order information 51B, 51E. The fourth order information 51F is configured as information for placing a stop-loss order to buy at a second stop-loss price higher than the first order information 51A, 51D and the second order information 51B, 51E.

[Buying and Selling Information Settings]
When generating the order information, the order information generating unit 16 sets the buying and selling information 181g of each of the order information 51A to 51E. In this embodiment, the order information generating unit 16 sets the buying and selling information 181g of the first order information 51A, 51D and the fourth order information 51F as "buy", and the buying and selling information 181g of the second order information 51B, 51E and the third order information 51C as "sell". When performing contract processing based on each of the order information 51A to 51F, this buying and selling information 181g is used by the contract information generating unit 14 to determine the type of buying and selling processing to be performed on the customer account information table 182, a system (not shown) of a financial institution that trades financial products, and the like.

[Setting limit orders and stop-limit orders]
When generating the order information, the order information generating unit 16 sets information indicating either a limit order or a stop order in the order condition information 181j of each of the order information 51A to 51E. In this embodiment, each is set based on a comparison between the prices input in the lower order price input field 44a and the upper order price input field 44b of the input screen 40 (i.e., the lower order price and the upper order price) and the market price at the time of generation (hereinafter referred to as the "market order price"). Specifically, the following (Setting Condition 1) to (Setting Condition 4) are set.
(Setting condition 1) When the order information is generated, if the market order price is higher than the lower order price and lower than the upper order price, the order condition information 181j of the first order information 51A, 51D and the second order information 51B, 51E is set as "limit price". The order condition information 181j of the third order information 51C and the fourth order information 51F is set as "stop price".
(Setting condition 2) When the order information is generated, if the market order price is lower than the lower order price and the upper order price, the order condition information 181j of the first order information 51A is set as "stop order", and the order condition information 181j of the first order information 51D and the second order information 51B and 51E is set as "limit order". The order condition information 181j of the third order information 51C and the fourth order information 51F is set as "stop order".
(Setting condition 3) When the order information is generated, if the market order price is higher than the lower order price and the upper order price, the order condition information 181j of the second order information 51E is set as "stop order", and the order condition information 181j of the first order information 51A, 51D, and the second order information 51B is set as "limit order". The order condition information 181j of the third order information 51C and the fourth order information 51F is set as "stop order".
(Setting condition 4) When generating order information, if the market order price is equal to the lower order price or the upper order price, for example, if the market order price is equal to the lower order price, the generation of each order information 51A, 51B, 51C, 51D, 51E, and 51F is canceled.

In this embodiment, each order information 51A-51F includes order condition information 181j that determines whether it is a limit order or a stop order. This makes it possible to realize a transaction using an if-done order even when the order information of the first order that is executed first (e.g., first order information 51A) is a limit order for buying that is higher than the market price at the time of ordering, or when the order information of the first order that is executed first (e.g., second order information 51E) is a limit order for selling that is lower than the market price at the time of ordering (see (Second Execution Procedure) (Third Execution Procedure) described below).

The contract information generation unit 14 records each piece of order information 51A-51F generated by the order information generation unit 16 in the order table 181 and customer account information table 182 of the database 18, and manages the recording status of the order information in the order table 181 thereafter. Specifically, it communicates with the order table 181 and customer account information table 182, and issues instructions for inputting, modifying, and deleting data in response to changes in the status of each piece of order information 51A-51F.

[View Order Information]
The front page delivery unit 11 displays the generated order information group and the order information constituting it on the display unit 22 of the client terminal 2. (a1) and (b1) of Fig. 8 and (c1) of Fig. 9 are image diagrams of the order history screen displayed on the display unit 22. In the figures, the display unit 22 displays the main fields of the order information groups 50A and 50B and the order information 51A, 51B, 51C, 51D, 51E, and 51F constituting them.

[Rejection of an order]
In addition, if the inspection in step S2 determines that at least one of the order prices in the first order information 51A and the second order information 51B is an inappropriate price ("Yes" in step S3), or if the amount of margin is less than the total order amount in step S5 ("Yes" in step S5), the order input receiving unit 12 treats the input order as an error and rejects the order (step S10).

[Limit order execution process (first execution procedure)]
4 to 6 are flow charts showing the procedure of contract processing after order processing of a limit order by an if-done order has been performed in the financial product transaction management device 1 of this embodiment. The procedure will be explained below with reference to these figures.

[Basic procedure for placing and executing orders]
4 is a flow chart showing the basic procedure of placing an order and executing a contract based on the first order information and the second order information in the financial product transaction management device 1 of this embodiment. The basic procedure will be described with reference to this figure.

The order information generating unit 16 performs an ordering process for each of the order information 51A, 51B, and 51C constituting the first order information group 50A generated in step S8, and each of the order information 51D, 51E, and 51F constituting the second order information group 50B (step S21). Here, "ordering process" refers to changing the status information 181o of the first order information 51A, 51D and the second order information 51B, 51E constituting each of the order information groups 50A and 50B from "waiting" to "ordering", which is treated as placing a limit order in terms of financial product trading. The financial product transaction management device 1 processes order information whose status information 181o is "waiting" (for example, second order information 51B shown in (a1) and (a2) of FIG. 8) as a limit order before order processing after generation, and process order information whose status information 181o is "ordering" (for example, first order information 51A shown in (a1) and (a2) of FIG. 8) as a limit order after order processing.

As shown in (a1) and (a2) of FIG. 8, when the procedure of step S21 is completed, the first order information 51A in the first order information group 50A and the second order information 51E in the second order information group 50B, in which the new/payment information 181m indicates "new", have status information 181o of "on order". On the other hand, the other order information 51B, 51C, 51D, and 51F, in which the new/payment information 181m indicates "payment", have status information 181o of "waiting".

In this state, the price information receiving unit 19 of the financial product transaction management device 1 continues to acquire information on the exchange rate. Then, when the market price is not equal to or higher than the fourth order price (or equal to or lower than the third order price) ("No" in step S22) and is equal to or higher than the upper order price (or equal to or lower than the lower order price) ("Yes" in step S23), the contract information generating unit 14 performs contract processing for the second order information (or first order information) (step S24). Here, "contract processing" refers to changing the status information 181o of any order information from "ordering" to "completed" and performing buying and selling processing for the any financial product. In addition, in financial product transactions, this "contract processing" is treated as a position being acquired, a limit order being contracted, and a first-priority order being completed in an if-done order based on a specific order information group (here, the second order information group 50B).

Figure 10 shows a time chart that shows a schematic representation of a contract based on a limit order in the financial product transaction management system 1A of this embodiment. For example, as shown in the figure, assume that the market purchase price of US dollars is 85.00 yen per dollar at time t1 when order information is generated (step S8) and an order is placed (step S21) by an if-done order.

After the order information is placed, the market price of the US dollar rises, and at time t2 when the market purchase price 71 becomes 90.00 yen per dollar ("Yes" in step S23), the contract information generation unit 14 performs processing to contract the second order information 51E (step S24). That is, as shown in FIG. 8, when the contract processing is completed, the status information 181o of the second order information 51E in the second order information group 50B is converted from "ordering" to "completed", and the corresponding data in the database 18 is rewritten. Specifically, the data in the "amnt" field 182a in the customer account information table 182 is increased or decreased by the amount of the contract.

At time t2' (effectively at the same time as time t2), the order information generating unit 16 checks whether the first order information and the second order information of the same order information group (for example, the first order information 51D and the second order information 51E of the second order information group 50B) have been contracted (i.e., whether the status information 181o is "concluded"). If both of the order information have not been contracted ("No" in step S25), the order information generating unit 16 performs ordering processing for the first (or second) order information and the fourth (or third) order information that constitute the same order information group as the contracted order information (step S27). That is, as shown in (b2) of FIG. 8, the status information 181o of the first order information 51D of the second order information group 50B is changed from "waiting" to "ordering" (step S27). As shown in FIG. 8 (b1), the front page distribution unit 11 displays on the display screen 47 that the order information 51E has been contracted and that the first order information 51D has become "on order." As a result, the second-ranked order in the if-done order based on the second order information group 50B is treated as being valid.

When one of the first order information and the second order information constituting the same order information group is executed and then the other is executed, the status information 181o of the third order information 51C or the fourth order information 51F constituting the order information group is also changed from "waiting" to "ordering" (step S27). That is, when the first order information 51D of the second order information group 50B is executed at time t2' in FIG. 10, the status information 181o of the fourth order information 51F of the second order information group 50B is changed from "waiting" to "ordering" as shown in (b1) (b2) in FIG. 8. This makes it possible to execute an order for which a position has been acquired by a stop-loss order.

After this, the process returns to step S22 and subsequent steps. When the market price is not equal to or higher than the fourth order price (or is not equal to or lower than the third order price) ("No" in step S22) and is equal to the lower order price ("Yes" in step S23), the contract information generation unit 14 performs contract processing for the first order information (step S24).

For example, as shown in FIG. 10, when the market purchase price of the US dollar falls after time t2' and the market purchase price 71 of the US dollar becomes 80.00 yen per dollar at time t3, the contract information generation unit 14 performs processing to contract the limit order based on the first order information 51A, 51D. As a result, the second-priority order in the if-done order based on the second order information group 50B is treated as having been executed. Also, the first-priority order in the if-done order based on the first order information group 50A is treated as having been executed.

At the same time, the contract information generation unit 14 cancels the fourth order information 51F. Here, "cancellation" refers to changing the status information 181o of any order information from "waiting" or "ordering" to "invalid," and in financial product trading, this is treated as canceling the limit order without executing it.

That is, as shown in (b1) of FIG. 8, the status information 181o of the first order information 51A, 51D is converted from "ordering" to "completed," and the status information 181o of the fourth order information 51F is converted from "ordering" to "invalid." Then, as shown in (c1) of FIG. 9, the front page distribution unit 11 displays on the display screen 47 that the first order information 51A, 51D has been contracted and the fourth order information 51F has become invalid.

Then, the contract information generation unit 14 rewrites the data corresponding to the first order information 51A, 51D and the second order information 51E in the database 18. Specifically, at time t3 in FIG. 10, the contract information generation unit 14 erases each of the order information 51D, 51E, and 51F that constitute the second order information group 50B. The contract information generation unit 14 also performs buying and selling processing on the customer account information table 182 and the system (not shown) of the financial institution that trades financial products. This allows the customer to earn a profit equal to the difference between the sell order at time t2 and the buy order at time t3.

When the status information of the first order information and the second order information among the order information constituting one order information group becomes "completed" ("Yes" in step S25), the order information generation unit 16 performs ordering processing for the order information of the new order information group (step S26). In this embodiment, as shown at time t3' in FIG. 10, ordering processing is performed for the first order information 51D, the second order information 51E, and the fourth order information 51F of the new second order information group 50C. The specific contents of the procedure in step S26 will be described later.

The order information generation unit 16 then performs ordering processing for the first (or second) order and the third (or fourth) order information of the other order information group (step S27). In this embodiment, at time t3' in FIG. 10, ordering processing is performed for the second order information 51B of the first order information group 50A. As a result, the second-ranked order in the if-done order based on the first order information group 50A is treated as being valid. Then, the process returns to step S22 and subsequent steps.

That is, in this embodiment, when contract processing is performed at the lower order price and the upper order price, contract processing of two order information is performed (for example, second order information 51E, 51B at time t2 in FIG. 10, and first order information 51D, 51A at time t3). That is, if-done orders are repeatedly performed multiple times in such a way that two limit orders (one is a new limit order, the other is a settlement limit order) are contracted each time the market price 71 reaches the lower order price and the upper order price. Therefore, the customer can make a large profit in a short period of time compared to the case where if-done orders are performed in such a way that one limit order is contracted each time the market price reaches the lower order price and the upper order price.

In addition, in this embodiment, the first order information 51A, 51D and the second order information 51B, 51E constituting the order information groups 50A, 50B are contracted in the reverse order. For example, in this embodiment, the second order information 51E is contracted (at time t2), the first order information 51D is contracted (at time t3), the first order information 51A is contracted (at time t3), the second order information 51B is contracted, and so on. In this manner, the contract processing between the first order information 51A, 51D and the second order information 51B, 51E is repeated. As a result, in the contract processing after time t3, when a plurality of order information groups, i.e., the first order information group 50A and the second order information group 50B), are contracted sequentially, a pair of first order information (i.e., the first order information 51A and the first order information 51D) and a pair of second order information (i.e., the second order information 51B and the second order information 51E) are contracted. As a result, customers can earn higher profits when a transaction is processed than if only one order was processed.

[Ordering new order information group (step S26)]
5 is a flow chart showing the ordering process for the order information in the new order information group in step S26. The procedure will be described in detail below with reference to the flow chart.

When placing a new order information group, the account information generating unit 15 again obtains the margin information of the customer from the customer account information table 182. Then, the order input receiving unit 12 again compares the obtained margin information with the customer's total order amount to confirm whether the amount of the margin is equal to or greater than the total order amount (step S261). If the amount of the margin is less than the total order amount ("Yes" in step S262), the process is suspended until it is equal to or greater than the total order amount, and if the amount of the margin is equal to or greater than the total order amount ("No" in step S262), the order information generating unit 16 again performs order processing for the order information group deleted in step S26 (step S263). In this embodiment, as shown in FIG. 9, at time t3' (effectively at the same time as time t3), the order information generating unit 16 performs order processing for the second order information group 50C having the same configuration as the second order information group 50B. In addition, the order information generating unit 16 performs order processing for the order information of the second order information 51E (step S263). As in step S9, the order information generation unit 16 records the second order information group 50C for which ordering processing has been performed in the order table 181 (step S264). When the second order information group 50C is ordered in step S263, the front page distribution unit 11 causes the display unit 22 of the client terminal 2 to display the second order information group 50C.

[Contract processing (cancellation processing) of stop-loss order at stop-loss price (step S28)]
6 is a flow chart showing the process of executing a stop-loss order at the stop-loss price in step S28. The details of the procedure will be described below with reference to the same figure.

If the market price of the financial product becomes equal to or higher than the fourth order price (or equal to or lower than the third order price) ("Yes" in step S22), the contract information generation unit 14 performs contract processing for the fourth order information 51F (or the third order information 51C) and cancels all uncontracted order information (step S281).

For example, if the market price rises further after time t2' in FIG. 10 and exceeds 100 yen per dollar, which is the price of the fourth order information, as shown at time t4 in the figure, the contract information generating unit 14 performs contract processing for the fourth order information 51F. As a result, a stop-limit order for "settlement" of a sell order of 100.00 yen per dollar is contracted for the first order information 51D that was contracted at time t2. In addition, the contract information generating unit 14 cancels the first order information 51A and 51D whose status information 181o is "ordering" and the third order information 51C whose status information 181o is "waiting". Furthermore, the contract information generating unit 14 also cancels all future orders for the order information. That is, the contract information generating unit 14 deletes data on the ungenerated order information group from the order table 181 and performs processing to stop the generation of the order information group that has not yet been generated.

In addition, in this embodiment, even if the market price falls sharply and the market price of the financial product falls below the third order price (1 dollar = 70.00 yen), the contract information generating unit 14 will perform the same cancellation process as above.

After processing of step S281, the financial product exchange management device 1 terminates all contract processing based on the order information (step S282).

In this way, when the third order information 51C, which places a sell stop order at a price lower than the first order information 51A and the second order information 51B, or the fourth order information 51F, which places a sell stop order at a price higher than the first order information 51D and the second order information 51E, is matched, all of the order information that forms a set of order information 50A, 50B and has not been matched is cancelled, thereby preventing a situation in which the customer is disadvantaged by the market price rising or falling below a certain price and avoiding risk to the customer.

In the above embodiment, the case where the upper order price is first set at time t2 and then the lower order price is set at time t3 has been described. However, even if the lower order price is first set at time t2 and then the upper order price is set at time t3, the financial instruments transaction management device 1 of this embodiment performs the same first contract procedure. In this case, contract processing of the first order information 51A of the first order information group 50A is performed at time t2 (the first-priority order of the first order information group 50A is treated as being established), and ordering processing of the first order information 51D of the second order information group 50B (the first-priority order of the second order information group 50B is treated as being valid) and ordering processing of the second order information 51B of the first order information group 50A (the second-priority order of the first order information group 50A is treated as being valid) are performed at time t2'. At time t3, contract processing is performed for the second order information 51B of the first order information group 50A, and contract processing is performed for the second order information 51E of the second order information group 50B (the second-priority order of the first order information group 50A and the first-priority order of the second order information group 50B are treated as having been contracted). At time t4, ordering processing is performed for the first order information 51A of the first order information group (not shown) (the first-priority order of the first order information group is treated as having been validated).

[Limit order execution process (second execution procedure)]
FIG. 11 shows an image of the order history screen displayed on the display unit of the client terminal in the second contract procedure, and an image showing the data structure of each order information, and FIG. 12 shows a time chart of the second contract procedure.

As shown in FIG. 11, in the second contract procedure, when the procedure of step S21 is first completed, the first order information 51A in the first order information group 50A has the order condition information 181j set to "stop-limit." In other words, this first order information 51A is configured as information for placing a new stop-limit order to buy the same type of financial product at a lower order price based on one buy/sell order application information. All other aspects are the same as the first contract procedure.

In the second contract procedure, the processing is the same as in the first contract procedure. However, as shown in FIG. 12, at time t2, the contract processing of the stop order is performed based on the first order information 51A. Note that the first order information that is placed for the second time or later (for example, the first order information 51A that is placed at time t3' in FIG. 12) is order information for a buy limit order, similar to the first contract procedure.

By executing the second limit order, when the first order information and the second order information are at a price higher than the market price of the financial product at the time of placing the order, a rational transaction can be automatically executed by fully utilizing profit opportunities while avoiding risks through an if-done order transaction.

[Limit order execution process (third execution procedure)]
FIG. 13 shows an image of the order history screen displayed on the display unit of the client terminal in the third contract procedure, and an image showing the data structure of each order information, and FIG. 14 shows a time chart of the third contract procedure.

As shown in FIG. 13, in the third contract procedure, when the procedure of step S21 is first completed, the second order information 51E in the second order information group 50B has the order condition information 181j set to "stop-limit." In other words, this second order information 51E is configured as information for placing a new stop-limit sell order for the same type of financial product at the upper order price based on one buy/sell order application information. All other aspects are the same as the first contract procedure.

In the third contract procedure, the processing is the same as in the first contract procedure. However, as shown in FIG. 14, at time t2, the contract processing of the stop order is performed based on the second order information 51E. Note that the second order information placed from the second time onwards (for example, in FIG. 14, the second order information 51E placed at time t3') is order information for a sell limit order, similar to the first contract procedure.

By executing the third limit order contract process, when the first order information and the second order information are at a price lower than the market price of the financial product at the time of placing the order, a rational transaction can be automatically executed by fully utilizing profit opportunities while avoiding risks through an if-done order transaction. This allows the present invention to be applied to a variety of transactions in accordance with market conditions, etc., and realizes a system that is highly convenient for customers.

[Order information error processing and order information cancellation processing]
In addition, after each piece of order information 51A-51F is generated by the procedure of steps S1-S9, if there is a request from the client terminal 2 to change the price and amount of each piece of order information 51A-51F, the financial product transaction management device 1 of this embodiment treats the request as an illegal request and processes it as an input error. This makes it possible to prevent excessive workload for the bank, which is the source of the financial product trade, from being caused by frequent requests for price and amount.

On the other hand, when a request is made to cancel an if-done order that has already been executed by clicking the order cancel button (not shown) displayed on the display unit 22 of the client terminal 2, the contract information generation unit 14 of the financial product transaction management device 1 extracts the order information group contained in the if-done order for which a cancellation request has been made, and processes all unexecuted order information from this order information group as having been cancelled. The data of the cancelled order information group and the order information data are deleted from the order table 181.

As described above, in this embodiment, when the order information is executed, the status information 181o is converted from "Ordering", which indicates an unexecuted state after the order is placed, to "Completed", which indicates an executed state, thereby recording the execution state of each of the order information 51A to 51F, i.e., whether or not the order is executed. In addition, by generating multiple order information groups 50A and 50B based on one buy/sell order application information, each group includes first order information 51A and 51D as order information for placing a limit order for the same type of financial product at one price, and second order information 51B and 51E as order information for placing limit orders for the financial product at another price, it is possible to automatically repeat transactions using if-done orders multiple times on a computer system based on one order procedure. This allows customers using the system to make rational transactions by fully utilizing profit opportunities while avoiding risks without having to go through complicated order procedures.

The above embodiment can also be implemented as shown below in (Variation 1) to (Variation 9).

(Variation 1)
In the above embodiment, the first order information 51A, 51D and the second order information 51B, 51E are configured to be repeated an unlimited number of times, but the input screen 40 may be provided with a repeat count selection field, and the if-done order may be repeated the number of times input in the repeat count selection field. In this case, each of the order information 51A to 51F is configured to include information for recording the number of repetitions.

(Variation 2)
In the above embodiment, the input screen 40 is provided with a first stop loss price input field 44g and a second stop loss price input field 44h, and the third order information 51C and the fourth order information 51F are set as order information for setting a stop loss price. However, instead of this, the input screen may be configured not to have at least one of these price input fields 44g and 44h, and not to set at least one of the third order information 51C and the fourth order information 51F.

(Variation 3)
In the above embodiment, a trail input field may be further provided on the input screen 40, and trail information may be provided as attribute information of the first order information 51A, 51D and the second order information 51B, 51E, so that when the market price rises or falls by more than the trail information, the order price information 181h of each of the order information 51A to 51F is increased or decreased by the price of the trail information.

(Variation 4)
In the above embodiment, the input screen 40 is provided with a lower order price input field 44a and a lower order price input field 44b, and the lower order price and the upper order price are set according to the prices input in the price input fields 44a and 44b. However, instead of this, the first order information may be set to the same price as the market order price at the time of generating the order information (step S8), and the upper order price may be set based on information input from the input screen (for example, the price input in the upper order price field or the profit amount for each if-done order input in the profit amount input field), and a limit order may be placed by if-done order.

(Variation 5)
In the above embodiment, in (setting condition 1), if the market order price is higher than the lower order price and lower than the upper order price, the order condition information 181j of the first order information 51A, 51D and the second order information 51B, 51E is set as "limit price", and in (setting condition 4), if the market order price is equal to the lower order price or the upper order price at the time of generating the order information, the generation of each order information 51A, 51B, 51C, 51D, 51E, 51F is canceled. However, instead of this configuration, in (setting condition 1), if the market order price is equal to or higher than the lower order price and lower than the upper order price, the order condition information 181j of the first order information 51A, 51D and the second order information 51B, 51E may be set as "limit price", and (setting condition 4) may not exist. Specifically, for example, when the market order price is equal to the lower order price, the order information generating unit 16 may be configured to set the order condition information 181m of the first order information 51A as “market”, which is a market order, set the order condition information 181m of the first order information 51D and the second order information 51B, 51E as “limit order”, and set the third order information 51C and the fourth order information 51F as “stop order”.

(Variation 6)
In the above embodiment, in (setting condition 2), if the market order price is lower than the lower order price and the upper order price when the order information is generated, the order condition information 181j of the first order information 51A is set as a "stop order", and in (setting condition 4), if the market order price is equal to the lower order price or the upper order price when the order information is generated, the generation of each of the order information 51A, 51B, 51C, 51D, 51E, and 51F is canceled. However, instead of this configuration, in (setting condition 2), if the market order price is equal to or lower than the lower order price and the upper order price when the order information is generated, the order condition information 181j of the first order information 51A may be set as a "stop order", and (setting condition 4) may not exist.

(Variation 7)
In the above embodiment, in (setting condition 3), if the market order price is higher than the lower order price and the upper order price when the order information is generated, the order condition information 181j of the second order information 51E is set as a "stop order", and in (setting condition 4), if the market order price is equal to the lower order price or the upper order price when the order information is generated, the generation of each order information 51A, 51B, 51C, 51D, 51E, and 51F is canceled. However, instead of this configuration, in (setting condition 3), if the market order price is equal to or higher than the lower order price and the upper order price when the order information is generated, the order condition information 181j of the first order information 51A may be set as a "stop order", and (setting condition 4) may not exist.

(Variation 8)
In the above embodiment and (Modification 1) to (Modification 7), the order condition information 181j (see FIG. 8 and FIG. 9) of one or both of the first order information 51A, 51D and the second order information 51B, 51E is set as "limit order" or "stop order", and they are configured to function as limit orders or stop orders. However, instead of this configuration, the order condition information 181j of the first order information 51A, 51D and the second order information 51B, 51E may be set as "market order", which is a market order, and function similarly to an if-done order. Specifically, the contract information generating unit 14 performs the procedure of placing the first order information 51A, 51D and the second order information 51B, 51E (step S21) between the procedure of step S23 and the procedure of step S24 in the flowchart shown in FIG. 4.

That is, in (Modification 8), when the current exchange market price received by the price information receiving unit 19 matches the lower order price or the upper order price ("Yes" in step S23), the contract information generating unit 14 places an order for the first order information 51A, 51D or the second order information 51B, 51E corresponding to the order price (step S21) and executes the contract (step S24). Note that, in (Modification 8), as in the above embodiment and (Modification 1) to (Modification 7), each order information 51A, 51B, 51C, 51D, 51E, 51F has new/settlement information 181m (see Figures 8 and 9). Therefore, even if the first order information 51A, 51D and the second order information 51B, 51E are set as market orders, the same function as an if-done order can be realized.

Furthermore, in (Variation 8), the order condition information 181j of the third order information 51C and the fourth order information 51F may be set to "market order" and configured to function in the same way as a stop-loss order. Specifically, in the flowchart shown in FIG. 4, the contract information generating unit 14 performs the procedure of placing orders for the third order information 51C and the fourth order information 51F (step S21) between the procedure of step S22 and the procedure of step S28. That is, when the current exchange rate price received by the price information receiving unit 19 matches the third order price or the fourth order price ("Yes" in step S22), the contract information generating unit 14 places an order for the third order information 51C or the fourth order information 51F corresponding to that order price (step S21) and performs a cancellation process (step S28).

In addition, in (Variation 8), the processes of steps S25, S26, and S27 shown in FIG. 4 are not performed. That is, in (Variation 8), after the process of step S24 is completed, the process returns to step S22, and the subsequent processes are repeated. In this case, a margin check process (similar to steps S261 and S262) may be performed after the process of step S24 and before the process of step S22 is performed.

(Variation 9)
The financial product transaction management system 1A in the above embodiment and each modified example is designed to handle foreign exchange as a financial product, but this is not limited to this, and the present invention can also be applied to financial product transaction management systems that handle other financial products, such as stocks and bonds.

It goes without saying that the above-mentioned embodiments and modifications are merely examples of the present invention, and do not mean that the present invention is limited to the above-mentioned embodiments and modifications.

1A: Financial product transaction management system 1: Financial product transaction management device 2, _{2 1} to 2 _n : Client terminal 12: Order input reception unit (order input reception means)
14...Contract information generation unit (contract information generation means, record management means)
16: Order information generation unit (order information generation means)
19... Price information receiving unit (market price information acquisition means)
50A, 50B, 50C, 50D, 50E... Order information group 51A, 51D... First order information 51B, 51E... Second order information 51C... Third order information 51D... Fourth order information 181... Order table (order information recording means)
181o...Status information (order status information)

Claims (5)

A financial product transaction management device for managing buying and selling of financial products, comprising:
A market price information acquisition means for acquiring market price information of the financial product;
an order information generating means for generating order information for a financial product based on buy/sell order application information for placing an order for trading one type of said financial product;
a contract information generating means for performing a transaction to contract the order based on processing of the order information generated by the order information generating means;
Equipped with
The order information generating means
generating one or more first order information as the order information of a first order as an order to execute one transaction of the financial product when the market price reaches a first price, the first order information being generated based on one of the buy/sell order application information, and generating one or more second order information as the order information of a second order as an order to execute one transaction of the financial product when the market price reaches a second price;
The contract information generating means
When the market price of the financial product reaches the first price, a transaction is carried out to execute the one or more first orders based on processing of the one or more first order information;
A financial product exchange management device characterized by repeating the process of executing a transaction to contract one or more of the second orders based on processing one or more of the second order information when the market price of the financial product becomes the second price. The order information includes order status information for determining whether the order is in an uncontracted state or a contracted state;
2. The financial instruments transaction management device according to claim 1, characterized in that the contract information generating means converts the order status information from the uncontracted status to the contracted status when the first order based on the first order information and the second order based on the second order information are contracted. A specific order information group among the plurality of order information groups includes third order information that places a stop-limit order to sell at a price lower than the first order based on the first order information and the second order based on the second order information, and another order information group of the specific order information group includes fourth order information that places a stop-limit order to buy at a price higher than the first order based on the first order information and the second order based on the second order information,
3. The financial instruments transaction management device according to claim 1, wherein, when the stop order based on the third order information or the stop order based on the fourth order information is executed, the execution information generating means cancels all of the order information relating to unexecuted orders that form the order information group. A financial product transaction management method carried out in a financial product transaction management device that manages buying and selling of financial products, comprising:
A market price information acquisition procedure performed by a market price information acquisition means for acquiring market price information of the financial product;
an order information generation step in which order information for a financial product is generated based on buy/sell order application information for placing an order for trading one type of said financial product;
a contract information generating step for executing a transaction to contract the order based on processing of the order information generated in the order information generating step;
Equipped with
In the order information generation procedure,
generating one or more first order information as the order information of a first order as an order to execute one transaction of the financial product when the market price becomes a first price, the first order information being generated based on one of the buy/sell order application information, and generating one or more second order information as the order information of a second order as an order to execute one transaction of the financial product when the market price becomes a second price;
In the contract information generating procedure,
when the market price of the financial product reaches the first price, a transaction is made to execute the one or more first orders based on processing of the one or more first order information;
A financial product transaction management method characterized by repeating the process of executing a transaction to contract one or more of the second orders based on processing of one or more of the second order information when the market price of the financial product becomes the second price. A program that causes a computer to function as a financial product transaction management device according to any one of claims 1 to 3.