JP2003223564A - System and method of managing defined contribution pension plan - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a new buying and selling method for merchandise to be operated in the defined contribution pension plan. <P>SOLUTION: This system includes a subscriber dealing detail database 6a for managing dealing contents and dealing status on an operating instruction for each subscriber, a plan dealing detail database 6b for managing dealing contents and dealing status on an operating instruction for each plan, and an operating instruction part 2 which obtains access to the subscriber dealing detail database 6a, developing the operating instruction formed by integrating, for each plan, the operating instruction for each subscriber belonging to the same plan, adding a record on the operating instruction for each plan to the plan dealing detail database 6b, and passing an order for the operating instruction for each plan to an operated-merchandise seller system 30 connected through a network. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a defined contribution pension processing method and a defined contribution pension processing system, and more particularly, to a method for trading managed products in a defined contribution pension plan.

[0002]

2. Description of the Related Art Generally, an individual who orders a sales order for a financial product must directly visit a sales company that sells the financial product or access a call center operated by this company. In particular, when depositing financial products, etc., the selling entity often differs according to the characteristics of the financial product, so you must individually go to the sales company that handles the products subject to deposit and perform the procedures individually. . Therefore, in addition to the time and procedural burdens on individuals, there is also a financial burden of having to bear remittance fees and the like. On the other hand, a merchandise sales company, when accepting an order from an individual, needs to manage an individual profile, trading history, etc. for each customer and perform an administrative procedure for each customer. Therefore, if the number of customers becomes enormous, there is an inconvenience that the cost required for administrative procedures regarding individual record management and trading is excessive.

In recent years, the defined contribution pension has been attracting attention as a system replacing the conventional defined benefit pension. This pension system is a system in which each member chooses and manages investment products at his or her own risk, and receives benefits that fluctuate according to investment performance in the future. Regarding the defined contribution pension, for example, in Japanese Patent Laid-Open No. 2000-250982, purchases and orders for products (managed products) for pension management of employees are made between a network-connected company and a financial product sales company. A direct pension fundable electronic trading system is disclosed. The company manages the contribution for each employee based on the employee master table generated by the payroll program, and makes a purchase plan and purchases of financial products for operation. In the system disclosed in this publication, these works that were performed offline are brought online, and the sales company is instructed to purchase products from the terminal of the computer system of the company.

[0004]

SUMMARY OF THE INVENTION An object of the present invention is to provide a new trading method for investment products in a defined contribution pension plan.

[0005]

[Means for Solving the Problems] In order to solve such a problem, a first invention is to provide a transaction content and a transaction related to an operation instruction for each subscriber by a record provided corresponding to the operation instruction for each subscriber. A subscriber transaction statement database that manages the status and a plan transaction statement database that manages the transaction content and transaction status related to the operation instruction in the plan unit by the record provided corresponding to the operation instruction in the plan unit, and the subscriber Access the transaction statement database, generate operation instructions that aggregate the operation instructions for each subscriber belonging to the same plan for each plan, add a record related to the operation instructions for each plan to the plan transaction statement database, and An operation instruction section that orders operation instructions for each plan to the operation product seller system connected via the network. To provide a defined contribution pension processing system.

[0006] The operation instruction section uses the order number assigned to each operation instruction to be placed in the operation commodity seller system.
It is preferable to link the record relating to the operation instruction for each plan to be ordered and the record relating to the operation instruction for each subscriber which is the target of aggregation when generating the operation instruction for this plan unit.

[0007] The above operation instruction section adds up the purchase amounts for each subscriber at the time of placing an order for the purchase of the operation products.
It is preferable to calculate the purchase amount for each plan.

[0008] The above operation instruction section sums up the sales quantity for each subscriber when placing an order to sell the operation products,
You may calculate the quantity sold on a plan basis. In this case, if the quantity fraction necessary to round up the quantity fraction of the sale quantity of the plan unit is recorded in the plan-specific fraction adjustment account, this operation instruction department will reverse the recorded quantity fraction. By performing the above, it is preferable that the sales quantity of the plan unit including the fractional quantity is made an integer quantity. In addition, if the number of fractions necessary to round up the number of fractions sold per plan is not recorded in the fraction adjustment account for each plan, the operation instruction section includes the number of fractions included in the number sold per plan. It is desirable to round off and round off the rounded amount to the fraction adjustment account for each plan.

The operation instruction unit may generate an operation instruction for each plan for a standard price type product by aggregating operation instructions for each subscriber belonging to the same plan for each plan. In addition, the operation instruction section, in addition to the plan operation for the operation instruction of the subscribers belonging to the same plan, for the item management type product managed by the plan account method, the individual operation instruction item key unit assigned by the operation product seller. The operation instruction for each plan may be generated by aggregating with.

In the first aspect of the invention, when the operation instruction for each ordered plan is contracted, the contracted result for each plan is reflected in the plan transaction details database, and the contracted result for each plan is apportioned to each subscriber. It is desirable to further include a contract result reflecting unit for calculating the contract result for each subscriber and reflecting the contract result for each subscriber in the subscriber transaction statement database.

The contract result reflecting unit is arranged in the plan transaction statement database and the subscriber transaction statement database.
It is preferable to reflect the contract result in the record specified by the order number added to the contract-based contract result.

[0012] It is preferable that the contract result reflecting unit calculates the contract sales amount of each subscriber by apportioning the contract sales amount of each plan to each subscriber at the time of contract sales of the managed products. In this case, the contract result reflecting unit may distribute the fractional amount of money generated by proration of the sale contract amount of each plan to each subscriber according to a preset priority rule. This priority rule is
It may be in the order of the subscribers whose amount of money is smaller than the smallest calculated currency unit.

The contract result reflecting unit, even when calculating the purchase contract amount for each subscriber by apportioning the purchase contract amount for each plan at the time of the purchase contract for the managed product, to each subscriber. Good. In this case, the execution result reflection unit may distribute the fractional quantity generated by the proportional distribution of the contracted purchase amount per plan to each subscriber according to the equity ratio of the subscriber calculated on the basis of the purchase price. preferable. In addition, it is desirable that the contract result reflecting unit rounds down the number of significant digits of the contracted amount of purchase contracts for each subscriber and records the fractional quantity generated by the rounding down as a fraction adjustment account for each plan.

In the first aspect of the invention, the record provided in correspondence with the order number is used to update the trading receipt management database for managing the receipt status of the operation instruction in plan units and the receipt status in the trading receipt management database. A trade reception check unit may be further provided. When the operation instruction for each plan is sent to the operation product seller system, this trading reception check unit sets the reception status in the record for the operation product seller specified by the order number to the waiting status, and executes the contract for each plan. When the result is received from the operation product seller system, the reception status in the record for the operation product seller specified by the order number is set to "received".

When the operation instruction in plan units is transmitted to the asset management organization system, the trading reception check unit sets the reception status in the record for the asset management organization specified by the order number to the waiting state, and sets the reception status in plan units. When the collation result of the contract result is received from the asset management system,
It is preferable to set the reception status in the record for the asset management organization specified by the order number to "received".

The contract result reflecting section reflects the contract result in the plan transaction statement database and the contract result in the subscriber transaction statement database, provided that the transaction reception check section has obtained the collation from the asset management organization. And is preferably performed. Then, it is preferable that the contract result reflecting unit updates the plan balance and the subscriber balance on the condition that the trading reception check unit has obtained the collation from the asset management organization.

According to the second aspect of the present invention, when ordering an operation instruction for a standard price type product to an operation product seller, an operation instruction in which the operation instructions for each subscriber belonging to the same plan are aggregated for each plan is generated. The first means for transmitting the operation instruction for each plan to the operation product seller system connected via the network, and the operation for each subscriber when ordering the operation instruction for the accumulated fund balance type to the operation product seller The second means for transmitting the order to the operation product seller system connected via the network and the same means when ordering the operation instruction for the item management type product managed by the plan account method to the operation product seller An operation instruction is created by aggregating the operation instructions for each subscriber belonging to the plan for each plan. The third to be sent to the merchandise seller system
And the operation instruction for the item management type product managed by the subscriber account management method to the operation product seller, the operation instruction for each subscriber is the operation product seller system connected through the network. And a fourth means for transmitting the defined contribution pension processing system.

A third invention provides a defined contribution pension processing method executed in a record-related operation management system. In this processing method, the system aggregates the operation instructions for each subscriber belonging to the same plan for each plan, and the first step for generating the operation instruction for each plan, The order number is assigned to each operation instruction to be ordered, and the transaction contents and transaction status related to the operation instruction for each plan are managed using this order number as a key, and the subscriber who is the aggregation target of the operation instruction for each plan The system has a second step of managing transaction contents and transaction status regarding a unit operation instruction, and a third step in which the system transmits a plan unit operation instruction to an operation commodity seller system connected via a network. .

Here, in the third invention, it is preferable that the first step includes a step of calculating the purchase amount for each plan by adding up the purchase amounts for each subscriber.

Further, it is preferable that the first step includes a step of calculating the sales quantity in plan units by adding up the sales quantities for each subscriber.

In the first step, when the quantity fraction necessary for rounding up the quantity fraction in the sales quantity of the plan unit is recorded in the plan-specific fraction adjustment account,
It is preferable to include a fourth step in which the sold quantity of each plan unit is converted into an integer quantity by performing the reversal of the recorded fractional quantity. In this 4th step, if the rounded-off amount for each plan is not rounded up, the rounded-off amount is rounded down to the nearest whole number. In addition, it is desirable to record the rounded down fractions in the plan-specific fraction adjustment account.

Further, in the third invention, when the order-based operation instruction for each plan is executed, the system reflects the result of the execution for each plan in the transaction contents relating to the operation instruction for each plan, and the system. The 6th step of calculating the contract result for each subscriber by apportioning the contract result for each plan by the subscriber, and the system, the transaction contents regarding the contract result for each subscriber regarding the operation instruction for each subscriber. And a seventh step to reflect the above.

Further, in the third invention, an eighth step for specifying an operation instruction for each subscriber and an operation instruction for each plan by the order number added to the execution result for each plan may be further provided. .

The sixth step may include a step of calculating the contracted amount of sale for each subscriber by apportioning the contracted amount of sale for each plan to each subscriber at the time of contract for sale of the managed product. preferable. This 6th
The step of may include the step of distributing the fractional amount of money generated by the apportionment of the sale contract amount of the plan unit to each subscriber according to a preset priority rule. This priority rule may be in descending order of subscribers with less than the smallest calculated monetary unit.

The sixth step is a step of calculating the purchase contract amount for each subscriber by apportioning the purchase contract amount for each plan at the time of the purchase contract for the managed product to each subscriber. May be included.

The sixth step is a step of allocating the fractional quantity generated by the apportionment of the purchase contract amount in plan units to the respective subscribers according to the ownership ratio of the subscribers calculated on the basis of the purchase price. May be included.

The sixth step includes a step of rounding down less than the significant digit of the contracted amount of purchase for each subscriber, and a step of recording the fractional quantity generated by the rounding down as a fraction adjustment account for each plan. You may stay.

In the third invention, the system is
An eighth step of managing the reception status of the operation instruction for each plan ordered by the order number may be further provided.
This 8th step is a step of managing the reception status for the operation product seller specified by the order number as a reception wait when the operation instruction in units of plan is transmitted to the operation product seller system, and the contract of each plan. When the result is received from the operation product seller system, the step of managing the reception status for the operation product seller specified by the order number as received.

In the eighth step, when the operation instruction in plan units is transmitted to the asset management organization system, the reception status for the asset management organization specified by the order number is managed as a reception wait, and in the plan unit When the matching result against the execution result is received from the asset management system,
Preferably, the step of managing the reception status for the asset management organization specified by the order number as having been received.

In a fourth aspect of the present invention, in the defined contribution pension processing method executed in a record-related operation and management organization system (RK system), when an operation instruction regarding a standard price type product is ordered from an operation product seller, the RK system is The first step is to generate an operation instruction in which operation instructions for each subscriber belonging to the same plan are aggregated for each plan, and to send the operation instruction for each plan to the operation commodity seller system connected via the network. And a second step for the RK system to send an operation instruction for each subscriber to the operation product seller system connected via the network when ordering an operation instruction for the accumulated fund accumulation type to the operation product seller. , RK system when ordering the operation instruction for the item management type product managed by the plan account method to the managed product seller , To generate the operational orders that consolidates the operational orders of subscriber units belonging to the same plan in the plan units,
The third step of transmitting the operation instruction for each plan to the operation product seller system connected via the network, and the operation instruction for the item management type product managed by the subscriber account management method to the operation product seller. In the case of placing an order, the RK system has a fourth step of transmitting an operation instruction for each subscriber to an operation commodity seller system connected via a network.

A fifth invention is a computer program for causing a record-related operation and management organization system (RK) to execute a defined contribution pension processing method, wherein the RK system is:
The first step of generating operation instructions for each plan by aggregating the operation instructions for each subscriber belonging to the same plan for each plan, and for each operation instruction that the RK system places an order with the operation product seller Numbering the number, and using this order number as a key, manage the transaction content and transaction status related to the operation instruction for each plan, and the transaction content for the operation instruction for each subscriber who is the aggregation target of this operation instruction for each plan. And a defined contribution pension processing method including a second step of managing a transaction status, and a third step in which the RK system transmits an operation instruction in plan units to an operation product seller system connected via a network. Provide a computer program to be executed by a record-related management system.

A sixth invention is a recording medium in which a computer program for causing a record-related operation and management organization system (RK) to execute a defined contribution pension processing method is recorded, and the RK system is a subscriber belonging to the same plan. The first step of generating operation instructions in plan units by aggregating the operation instructions in units of plans, and the RK system assigns an order number to each operation instruction to order to the operation product seller, Using the order number as a key, it manages the transaction details and transaction status related to the operation instructions for each plan, and the transaction details and transaction status related to the operation instructions for each subscriber who is the aggregation target of this operation instruction for each plan. The second step and the RK system are operation product seller systems in which operation instructions in plan units are connected via a network. To provide a recording medium having a computer program recorded thereon for executing the defined contribution processing method and a third step of transmitting to the recording-related operating agency system.

[0033]

BEST MODE FOR CARRYING OUT THE INVENTION (First Embodiment) First, the role of a player who appears in a defined contribution pension system will be briefly described. FIG. 1 is an explanatory diagram of a corporate defined contribution pension system. In the defined contribution pension plan, plan sponsors,
Subscribers, asset management institutions, operation management institutions, and managed product sellers will appear as players. "Plan Sponsor"
Is a person who defines his / her defined contribution pension agreement. In the case of a corporate pension plan, a company is a plan sponsor in principle, but if a defined contribution pension agreement is established for each business site in the company (one company, many plans), each business site becomes a plan sponsor. In addition, when multiple companies stipulate the same defined contribution pension agreement (multi-company one plan), the representative company becomes the plan sponsor. The plan sponsor contributes contributions based on the defined contribution pension agreement that is premised on a labor-management agreement and pays it to the asset management institution. In the case of an individual pension,
The National Pension Fund Federation becomes the plan sponsor.

A "subscriber" is an employee in a corporate pension. In accordance with the defined contribution pension rules stipulated by the plan sponsor, the subscriber selects an investment product from among a plurality of investment products presented in advance based on his / her own judgment. The selection of investment products is performed by designating an investment ratio (for example, 50% of monthly contributions is product A, 30% is product B, and 20% is product C). In addition, the member of the individual pension is a sole proprietor or an employee of a company that does not contribute a premium and has applied for membership.

The "asset management institution" is a person who clearly separates the contributions collectively contributed by the plan sponsor from the property of the plan sponsor (company property) and the property of the subscriber and stores them as pension assets. . In the case of a corporate pension, a trust bank that has an asset management contract with a company that is a plan sponsor becomes the asset management institution. The asset management institution will settle funds with the managed product seller in connection with contributions and deposits. In the case of individual pensions, the financial institutions outsourced to the National Pension Fund Federation correspond to asset management institutions.

The "operation and management institution" has a role as an agent for managing the pension assets from the viewpoint of the subscriber and is a person selected from the plan sponsor by an operation and management contract or the like. As the operation management institution, for example, a bank, a credit union, etc., a securities company, a life insurance company, a non-life insurance company, an agricultural cooperative, etc. or a post office etc. are assumed. The operation management organization performs the operation-related work and the record-related work. In particular, the record-related operation management organization that specializes in the latter record-related work is hereinafter referred to as "Record Keeper" or "RK". Further, the "managed product seller" is a person who sells managed products selected by the operation management organization.

FIG. 2 is a diagram showing a relationship among players (a record keeper which is a part of an operation management organization, an asset management organization, an operation product seller). FIG. 2A is a logical interface, and FIG. b) shows physical interfaces respectively. In light of the legal provisions that only the owner can dispose of (sell and sell) assets, the asset management agency, which is positioned as an agent of the participants, plays the main role in the sale and purchase of products. It is an institutional idea. According to this concept, the asset management institution carries out product operation instructions (purchase order or sales order) for the managed product seller, and the execution result (purchase contract or sale contract) from the managed product seller is also the asset management organization. Will be received ((a) in the same figure).

However, in the information transmission via the asset management organization, there is a disadvantage that a time lag occurs between the record keeper and the managed product seller. Therefore, in order to prevent such a time lag, in this embodiment, information is transmitted by the physical interface shown in FIG. For example, as shown in (b-1) of the figure, when ordering an operation instruction to the operation product seller system 30,
The record keeper system 10 (hereinafter, referred to as “RK system”) directly transmits the operation instruction data to the operation product seller system 30, provided that the asset management organization has obtained the approval. However, because the asset management organization manages the operation instruction data, the RK system 10 also transfers the operation instruction data to be ordered to the asset management organization system 20. On the other hand, as shown in FIG. 2B-2, the contract result data transmitted from the operation product seller system 30 is directly received by the RK system 10 and
Transfers the contract result data to the asset management system 20. Receiving this, the asset management institution system 20 collates the contract result data and transmits the collation result data to the RK system 10. Then, the RK system 10 updates the transaction details, balance, etc. based on the received verification result data. As described above, in the physical interface, the record keeper plays a role of a relay point between the product seller and the asset management organization.

Next, the products managed in the defined contribution pension system will be described. In the case of a corporate pension plan, the operation management organization makes a proposal about what kind of investment product the plan sponsor (company) adopts as its own pension plan (hereinafter simply referred to as “plan”) Determined by agreement. In this embodiment, in order to facilitate management in an operation management organization (record keeper),
Depending on the product characteristics, the managed product is a base price type product,
It is categorized as either a reserve balance accumulation type product or an item management type product.

Here, the "base price type product" means a product whose market value can be evaluated based on the base price, and examples thereof include an investment trust and a life insurance special account type product. Regarding the managed products classified as the standard price type products, the record keeper manages the balance of the subscriber based on the balance quantity (unit number basis). The “accumulated balance accumulated product” refers to a product for which the managed product seller calculates the balance for each subscriber, and examples thereof include insurance products, ordinary deposits, and savings deposits. The “detailed management type product” refers to a product for which sale, revenue distribution, market value evaluation, etc. occur in units of contracts purchased in the past, and examples thereof include time deposit, MMF, GIC and the like. Regarding the managed products that are classified as item management type products, the record keeper manages the balance breakdown by past purchase contract unit (however, the breakdown may be summarized), and the transaction details by subscriber or plan unit. to manage.

There are a plan account method and a subscriber account method as the account management method for the managed products. The "plan account method" refers to a method in which the seller of managed products does not manage subscriber units, but only manages plan units. With regard to the managed products managed by this account management system, the record keeper specifies the details of the sales for each subscriber, aggregates (collects) the plan units, and places an order with the managed product seller. Further, the record keeper apportions the contract result received from the managed product seller to each subscriber for each breakdown.

On the other hand, the "subscriber account method" refers to a method in which a managed product seller manages on a subscriber basis. Regarding the managed products managed by this account management method, the record keeper does not specify the details of buying and selling, but places an order by the order quantity or order amount of each subscriber, and receives the details specified by the managing product seller as the contract result. . The breakdown received is managed mainly by reflecting the balance received from the investment product seller as it is, mainly for the purpose of evaluating the assets. In the present embodiment, the trading process is constructed assuming the following four types as the combination of the product characteristics and the account management system.

(Product type) Type Product Characteristics Account management method (1) Base price plan account (2) Accumulated reserve balance subscriber account (3) Detailed management plan account (4) Detail management type subscriber account

Here, all standard price type products belong to type (1). Regarding this type (1), the record keeper aggregates the subscriber-specific operation instructions for individual subscribers on a plan-by-plan basis and places an order as a plan-based operation instruction. Further, the record keeper also receives the contract result in units of plans and prorates the contract result to each subscriber. Further, all the reserve balance accumulated products belong to the type (2). Regarding this type (2), the record keeper orders the operation instruction individually received from the subscriber as an operation instruction for each subscriber. Further, the record keeper also receives the contract result for each subscriber. Further, the item management type products are classified into type (3) and type (4). The type (3) is similar to the standard price type product (type (1)), but management is performed in individual detailed key fine units to be described later. Type (4)
Is the same as the reserve balance accumulated product (type (2)), but is managed in units of individual item keys. It should be noted that which of the plan account and the subscriber account is used to manage each item management type product is set in advance at the discretion of the managed product seller.

Next, a computer network system that realizes product sales in the defined contribution pension system will be described. FIG. 3 is a configuration diagram of the computer network system according to the present embodiment. This network system includes an RK system 10 (that is, a "record-related operation management organization system") and an asset management organization system 20.
And an operation product seller system 30.
The RK system 10 and the asset management organization system 20 and the RK system 10 and the operation product seller system 30 are connected via a wired or wireless communication network. These systems 10, 20, 30
It is mainly composed of a general computer having a CPU, a RAM, a ROM, a storage device (such as a magnetic disk device), and a communication device for communicating with an external system.

When the RK system 10 is functionally regarded as a subsystem relating to trading processing (trading subsystem), the RK system 10 includes a reception unit 1, an operation instruction unit 2, a trading reception check unit 3, and a trade result reflection unit. 4 and an external interface 5. Data transmission / reception between the RK system 10 and the external systems 20 and 30 is performed via the external interface 5. Also,
Although various databases are stored in the storage device accessible to the computer in the RK system 10,
With respect to the transaction-related business related to trading, the subscriber transaction detail database 6a, the plan transaction detail database 6b, the trading receipt management database 6c, the plan balance database 6d, and the subscriber balance database 6e are important.

The interface between the record keeper (RK) and the seller of managed products will be schematically described for each time of purchase and sale. It should be noted that, regardless of whether the product is the base price type, accumulated reserve balance type, or item management type, the purchase instruction is always based on the amount (the purchase contract is based on the quantity).
The sale order is always carried out on a volume basis (sale contracts are on a value basis). In addition, the asset management organization is
Despite (4), managed products are managed only on a plan basis, not on a subscriber basis. for that reason,
The operation instructions and contract results sent from the record keeper to the asset management organization are always on a plan basis.

(Interface at the time of purchase) FIG. 4 is a diagram showing an interface at the time of purchase regarding the standard price type product. In the standard price type product, regarding the same product,
Purchase orders of individual subscribers belonging to the same plan are ordered after consolidating them in plan units, and the contracts are also executed in plan units (plan unit / product unit). Purchase amount per plan (amount related to purchase order: also called purchase order amount)
Is calculated by adding up the purchase prices for each subscriber.

For example, as shown in (a) of the same figure, subscribers 1 and 2 belong to the same plan A, and the purchase instruction of the subscriber 1 is a commodity A and a subscriber 2 with a purchase price of 1,000 yen. Consider the case in which the purchase instruction for each indicates the product A for the purchase amount of 2,000 yen. In this case, the operation instruction unit 2 of the RK system 10 relates to each of the subscribers 1 for the same product A.
Purchase instructions from 2 are aggregated in units of plan A. As a result, the total purchase price for Plan A for product A will be 3,000 yen, which is the sum of the purchase price of subscriber 1 of 1,000 yen and the purchase price of subscriber 2 of 2,000 yen. The operation order unit 2 orders the purchase order (plan A, product A, plan purchase amount of 3,000 yen) for each plan from the operation product seller system 30, and at the same time, executes the plan purchase order with the asset management organization. It is also transferred to the system 20.

Then, as shown in FIG. 9B, when the operation merchandise seller system 20 receives the fact that the previously ordered plan purchasing instruction has been executed with 30 units (about a fixed amount), RK
The trading receipt check unit 3 of the system 10 sends the purchase agreement in plan units to the asset management institution system 20 and requests verification. Then, the contract result reflecting unit 4 of the RK system 10 executes contract processing on condition that the collation result from the asset management institution system 20 is OK (suitable for collation), and the contract amount of 30 units per plan is set for the subscriber 1 , 2. This apportionment is performed according to the ratio of the purchase amount (1,000 yen, 2,000 yen) of the individual subscribers 1 and 2 to the plan purchase amount of 3,000 yen. As a result, subscriber 1 has 10 units (= 30 units x 1,
000 yen / 2,000 yen), 20 for subscriber 2 (= 30 × 2,000)
Yen / 3,000 yen) will be allocated to each.

In the purchase and sale of the standard price type product, the managed product seller uses the managed product seller management key to associate (link) with his / her own management unit. The asset management organization uses the asset management organization management key to associate the product with its own management unit, although the same applies to the sale and purchase of products described below. Here, the "managed product seller management key" refers to a key that the managed product seller sets to identify the plan unit managed by the record keeper side in association with its own management unit. Examples of managed product seller management keys are (branch code + deposit type + account number) set for banks, (branch code + account number) set for securities companies, life insurance companies and damages. In the case of an insurance company, a security number or the like can be used. Further, the "asset management institution key" is a key set by the asset management institution so as to identify a plan unit managed by the record keeper side in association with its own management unit. As such a key, for example, a securities number in the case of a life insurance company or a non-life insurance company, and a special contract number in the case of a trust bank can be used.

FIG. 5 is a diagram showing an interface at the time of purchase regarding a reserve balance accumulated product. Purchase instructions for products with accumulated accumulated reserves are not aggregated on a plan-by-plan or product-by-plan basis, unlike the standard-value-type products, and are ordered as-is to the sellers of managed products as operation instructions on a subscriber-by-subscriber basis (subscriber-by-subscriber Product unit). Then, similar to the ordering, the contract result from the managed product seller is also received for each subscriber and for each product.

For example, as shown in FIG. 7A, the purchase instruction of the subscriber 1 is the product A with a purchase amount of 1,000 yen, and the purchase instruction of the subscriber 2 is the purchase amount of 2,000 yen with respect to the product A. Consider the case instructing. As described above, since the asset management institution manages only on a plan-by-plan basis and on a product-by-product basis, the operation instruction unit 2 needs to notify the asset management institution system 20 of the order amount for each plan related to the sale and purchase of the product A. is there. Therefore, the operation instruction unit 2 collects the purchase instructions from the subscribers 1 and 2 for each plan A as the data for the asset management organization. Then, the operation instruction unit 2 places an order for a purchase instruction for each subscriber and a purchase instruction for each plan for each of the subscribers 1 and 2 with respect to the operation commodity seller system 30, and at the same time, the asset management institution system. For 20,
Send only purchase instructions for each plan.

Then, as shown in FIG. 6B, when the purchase instruction of the subscriber 1 is 10 and the purchase instruction of the subscriber 2 is 20, the operating product seller system 30 subscribes. Person 1,
The purchase contracts for each of the two types and the purchase contracts for each plan (contract amount = 30 units) are transmitted to the RK system 10 as contract results. Purchase agreements on a per-plan basis are necessary for reconciliation at asset management institutions that manage products only on a per-plan basis. Upon receipt of these purchase contracts, the trade reception check unit 3 displays the contract-based contract result in the asset management system 2
Send to 0 to request verification. Then, the contract result reflection unit 4 confirms that the collation result from the asset management institution system 20 is OK.
Execution processing is performed on the condition that In the case of products with accumulated reserves, orders and contracts are made on a subscriber-by-subscriber / product-by-commodity basis, so no apportionment occurs like with standard-value products.

In the sale and purchase of accumulated reserve balance products, the managed product seller associates the managed product seller with the managed product seller management key and the seller-side subscriber management key. Further, the asset management organization uses the asset management organization management key to associate it with its own management unit. here,
The "subscriber management key on the seller side" is a key for identifying the subscriber on the operation product seller side after the plan is specified on the operation product seller management key. Corresponds to the subscriber number. As the subscriber management key on the seller side, for example, in the case of a life insurance company or a non-life insurance company, an insured person number can be used.

FIG. 6 is a diagram showing an interface at the time of purchase for the item management type product (plan account system). In the case of the item management type product managed by the plan account method, the ordering and the contracting are performed in the plan unit and the product unit as in the case of the standard price type product. Therefore, the point that it is necessary to aggregate the operation instructions from the subscriber unit to the plan unit and the point that it is necessary to apportion the execution result from the plan unit to the subscriber unit,
This is the same as for the standard value type product.

When purchasing this type of product,
In addition to the managed product seller management key, an individual detail key is added to the contract result by the managed product seller. here,
The "individual item key" is a managed product seller in order to specify the plan and subscribers with the managed product seller management key and the seller's subscriber management key, and to manage the details as a separate record. The key given by. Since the rate of the item management type product fluctuates day by day, it is necessary to manage the balance differently for the same product but with different purchase dates. Therefore, the individual detail key is used to manage the balance on a purchase unit basis. As the individual specification key, for example, set date + (serial number within set date), interest rate + set date + (serial number within set date), etc. can be used (however, items in parentheses may not be used). At the time of sale, the order of reversing this key is specified in ascending / descending order (in the case of the plan account method). The record keeper manages the contract result (purchase contract and sale contract) for each individual detail key. Note that the numbering method of the individual detailed key is left to the discretion of the seller of the managed product, but in the example of the figure, the contracted date of purchase is used as the individual detailed key.

FIG. 7 is a diagram showing an interface at the time of purchase for the item management type product (subscriber account system). The item management type products managed by the subscriber account system are ordered and contracted on a subscriber-by-subscriber basis or on a product-by-subscriber basis, similar to the reserve balance accumulated product.

When purchasing this type of product,
The contract result is given an individual item key numbered by the product seller in addition to the product product seller management key and the seller side subscriber management key. The record keeper is
The contract result is managed by this individual detail key.

(Interface at the time of sale) FIG. 8 is a diagram showing an interface at the time of sale regarding the standard price type product. For NAV products, as with the purchase of this product, the sales instructions for the same product received from individual subscribers belonging to the same plan are aggregated on a per-plan basis and ordered, and their contracts are also on a per-plan basis. Held (plan-based / product-based). The sales quantity per plan (quantity relating to sales order: also called sales order quantity) is calculated by adding up the sales quantity for each subscriber.

For example, as shown in (a) of the same figure, the sales instruction of the subscriber 1 indicates the product A with the sales quantity of 30 units, and the sales instruction of the subscriber 2 indicates the sales quantity of 50 units with the product A. Consider the case that In this case, the operation instruction unit 2 aggregates the sale instructions from the respective subscribers 1 and 2 for the same product A in plan A units. As a result, the total amount of sales of Plan A for product A (plan sales amount) is 80 units, which is the sum of the sales volume of Subscriber 1 of 30 units and the sales volume of Subscriber 2 of 50 units. Then, the operation instruction unit 2 orders the sale instruction (plan A, product A, plan sale quantity of 80 units) for each plan from the operation commodity seller system 30 and, at the same time, orders the asset management institution system 20. Also sends the same sale order.

Then, as shown in (b) of the figure, when it is received from the operating product seller system 30 that the sale order ordered earlier is contracted at 16,000 yen (plan contract amount).
The trade receipt check unit 3 transmits the contract result to the asset management institution system 20 and requests verification. Then, the contract result reflecting unit 4 executes contract processing on condition that the collation result from the asset management institution system 20 is OK, and apportions the plan contract amount of 16,000 yen to the subscribers 1 and 2. This apportionment is based on the individual subscriber 1,
It is carried out according to the ratio of the sales volume of 2 (30 units, 50 units).
As a result of this apportionment, subscriber 1 will receive 6,000 yen (= 16,000
× 30/80 units, 10,000 yen for subscriber 2 (= 16,000 yen ×)
50/80) will be distributed respectively.

FIG. 9 is a diagram showing an interface at the time of selling a reserve balance accumulated product. For accumulated reserve balance products, the sales instruction for the same product received from individual subscribers belonging to the same plan is directly ordered to the managed product seller on a subscriber basis, and the contract from the managed product seller is also on a subscriber basis. Will be carried out (subscriber unit / product unit).

For example, as shown in FIG. 7A, the sales instruction of the subscriber 1 indicates the product A with the sales quantity of 30 units, and the sales instruction of the subscriber 2 indicates the product A with the sales quantity of 50 units. Consider the case. The operation instruction unit 2 collects the sale instructions from the subscribers 1 and 2 in plan A units as data for the asset management organization. Then, the operation instruction unit 2 orders a sale instruction for each subscriber and a sale instruction for each plan with respect to the operation product seller system 30, and only a sale instruction for each plan with respect to the asset management institution system 20. To send.

Then, as shown in FIG. 9B, the selling instruction of the subscriber 1 is 6,000 yen and the selling instruction of the subscriber 2 is 10,000.
If the contract is made in yen, the managed product seller system 20 will sell the contract related to each of the subscribers 1 and 2, and sell the contract for the asset management institution (plan contract amount = 16,000).
And a circle) to the RK system 10. In response to this,
The contract result reflecting unit 4 executes contract processing without performing proportional division on condition that the collation result from the asset management organization regarding the contract for sale is OK.

FIG. 10 is a diagram showing an interface at the time of sale of the item management type product (plan account system). In the item management type product managed by the plan account method, orders and contracts are made in plan units, product units, and detailed units (for example, contract date units). Similar to the base price type product, aggregation on a plan basis and apportionment on a subscriber basis is required, but the feature of this type of product is that a detailed unit is added. Details can be specified by individual item keys specified in advance by the seller of the product, for example, first-in first-out on a contract date basis (purchase date), last-in first-out on a contract date basis, or ascending or descending order of individual item keys. The keeper does. If the contract date is the same for both first-in, first-out and last-in, first-out, the ordering date or ordering time will be taken out.

For example, consider an order to sell subscribers 1 and 2 who belong to the same plan A as shown in FIG. Subscriber 1's sale order for product A is the individual item key 99/8/2
5 (In this case, the purchase contract date is used as the individual item key)
Sold 10 units, individual item key 99/9/25 sold 1 unit
There are 0 units and 10 units sold with individual detail key 99/10/25. In addition, the sales order of the subscriber 2 regarding the same product A is as follows: the individual item key 99/8/25 sells 20 units, the individual item key 99/9/25 sells 20 units, and individual item key 99 / 10/25
The attached sales volume is 10 units. In this case, operation instruction section 2
Sells the sales instructions from the subscribers 1 and 2 for the same product A in plan A units and individual detail key units. As a result, three plan sale instructions are created for each individual detail key, and the sales volume of each plan is the same as the sales volume of subscriber 1 and subscriber 2 for the same individual detail key.
It will be the total of the quantity sold and the quantity sold. For example, the number of plans sold with individual detail key 99/8/25 is 30 units, which is the sum of 10 units sold by subscriber 1 and 20 units sold by subscriber 2. The operation instruction unit 2 orders the operation commodity seller system 30 to sell three sales instructions with individual detail keys (plan sales quantity 30 units, 30 units, 20 units), and at the same time, the asset management institution system 20. Also send these sales instructions.

Then, as shown in (b) of the same figure, when the three plan selling instructions are executed at 6,000 yen, 6,000 yen, and 4,000 yen (plan contract amount), respectively, the trading reception check unit 3 sells them. To the asset management institution system 20 to individually request collation regarding each contract result. Then, the contract result reflecting unit 4 executes contract processing on condition that the collation result from the asset management institution system 20 is OK, and apportions the plan contract amount to the subscribers 1 and 2. This apportionment is performed in units of individual detail keys, and is performed according to the ratio of the sales quantity of each subscriber 1 and 2 to the plan sales quantity. This allows the individual item key 99/8/2
Regarding 5, for subscriber 1, 2,000 yen (= 6,000 × 10 units / 30
4,000 yen (= 6,000 yen x 20 units / 30 units) will be allocated to each subscriber. Similarly, for individual detail key 99/9/25, 2,000 yen will be distributed to subscriber 1 and 4,000 yen to subscriber 2, respectively, and individual detail key 99/10/25 will be 2,000 per subscriber. Yen and 2,000 yen will be distributed to each subscriber 2.

In selling this type of merchandise, in addition to the operation merchandise seller management key, an individual detail key is added to the execution result by the operation merchandise seller. Then, the record keeper manages the sale contract result with the individual detailed key.

FIG. 11 is a diagram showing an interface at the time of sale of the item management type product (subscriber account system). In the case of the item management type product managed by the subscriber account system, orders are placed on a subscriber-by-subscriber basis, and on a product-by-product basis. The specifics of the details are done independently by the seller of the managed products. The relationship between the order data and the contract data is 1: N.

For example, as shown in FIG. 7A, the sales instruction of the subscriber 1 indicates the product A with the sales quantity of 30 units, and the sales instruction of the subscriber 2 indicates the product A with the sales quantity of 50 units. Consider the case. The operation instruction unit 2 collects the sale instructions from the subscribers 1 and 2 in plan A units as data for the asset management organization. Then, the operation instruction unit 2 orders a sale instruction for each subscriber and a sale instruction for each plan with respect to the operation product seller system 30, and only a sale instruction for each plan with respect to the asset management institution system 20. To send.

Then, as shown in FIG. 9B, of the 30 units sold by the subscriber 1, 10 units are individual detail key 99/8/25 with the sale amount 2,000 yen, 10 units are individual detail key It is assumed that the sale price is 2,000 yen with 99/9/25, and 10 contracts with individual detail key 99/10/25 are contracted with 2,000 yen. Of the 50 units sold by Subscriber 2, 20 units are sold with individual detail key 99/8/25 for 4,000 yen, 20 units are sold with individual detail key 99/9/25 for 4,000 yen, 10 It is assumed that the mouth is executed with the individual detail key 99/10/25 and the contract amount is 4,000 yen. In this case, the operation product seller system 30 has the respective subscribers 1, 2
The sale contract relating to the asset management agency and the sale contract regarding the unit of the plan and the unit of the contract date for the asset management organization are transmitted to the RK system 10.
The contract result reflecting unit 4 executes contract processing without performing proportional division on condition that the collation result from the asset management institution system 20 regarding the contract for sale is OK.

When selling this type of product,
In addition to the operation product seller management key and the subscriber management key on the seller side, the individual product key described above is added to the contract result by the operation product seller. Then, the record keeper and the individual detail key manage the contract result in detail units.

The feature of this embodiment lies in the method of selling and selling products managed by the plan account method. Specifically,
The point is that subscriber operation instructions belonging to the same plan are aggregated to place an order for the plan operation instructions, and that the result of the plan contract is reflected in the contract result for each subscriber. Therefore, in the following description, a standard price type product, which is a typical example of products handled on a plan / product basis, will be mainly described, and a description management type product (plan account method) will also be referred to as appropriate.

FIG. 12 is a diagram showing a time-series flow of a series of trading processes. FIG. 13 is a diagram showing an example of data management at the time of purchase, and FIG. 14 is a diagram showing an example of data management at the time of sale. Hereinafter, description will be given along the time-series flow of FIG. 12 with reference to the cases of FIGS. 13 and 14 as appropriate.

(Subscriber Operation Instruction Reception Processing) Prior to placing an order for operation instructions relating to trading, the reception unit 1 uses an operation instruction for each subscriber (subscriber operation instruction) as a trigger for reception (reception) of the data. Subscriber transaction details database 6a
Register at any time. The receiving unit 1 may be configured as a partial function of the trading subsystem. In this case, the reception unit 1 enters the database 6a based on the sale information for each subscriber, which is delivered from the contribution management subsystem, the benefit subsystem, the revenue sharing / maturity subsystem, etc. located in the preceding stage of the trading subsystem. To register. Also, the reception section 1
May be configured as part of a contribution management subsystem, a benefit subsystem, a revenue sharing / maturity subsystem, and the like.

FIG. 15 is a diagram showing a relationship between a transaction to be traded and a trade category. Typical transactions subject to transaction processing include “payment”, “transfer”, “transfer”, “asset disposal”, “interest payment / earnings distribution” and the like. For example, in the case of “payment” (transaction by normal contribution), the purchase order is generated as the subscriber operation instruction because the sales category is “buy”. In "custody" (a transaction in which the subscriber sells one product and buys another product), the sales category is "sale" and "buy", so both the sales instruction and the purchase instruction are subscribers. Operation instructions are generated. In the case of "replacement", the sale order is first ordered, and the purchase order is placed after the receipt of the sale contract. In addition, the "transfer" (transactions that accompany the transfer of plans due to job changes, etc.) will make a purchase order, and the "asset disposal" (sale of assets due to start of benefits, death, severe disability, etc.) will make a sale order and a purchase order, In "Interest payment / Revenue distribution", a purchase order is generated. Each time the accepting unit 1 accepts a transaction to be traded, it newly adds a record regarding a subscriber operation instruction (sale instruction, purchase instruction) regarding the transaction to the subscriber transaction statement database 6a.

FIG. 16 shows the subscriber transaction details database 6
It is a figure which shows an example of a. The subscriber transaction statement database 6a manages the transaction content and transaction status (status) related to the operation instruction (operation instruction for each subscriber) of each subscriber for each subscriber. The database 6a is configured as a set of records associated with individual subscriber operation instructions. One record is "plan number", "subscriber number", "commodity code", "order number", "order date", "trade category", "transaction category", "order amount / quantity", "contract". "Amount / quantity", "transaction status",
Items such as an "individual detail key" are associated with each other.

Here, the "plan number" is a code peculiar to the plan, which is given to identify the plan. In addition, a company code is added to the plan number as necessary in order to support the above-mentioned one-company multi-plan or multi-company one plan. The "subscriber number" is a subscriber-specific code given for subscriber identification. The “commodity code” is a code unique to the product, which is given for identifying the product in the plan. The “order number” is a number for order management, which is assigned by the record keeper (RK) for each order of one operation instruction, and the order number and the order case correspond one-to-one. Therefore, the order number is stored in the database 6 in the RK system 10.
In addition to being used as the access keys a to 6c, it is also used as a key for reception management with an external system (for example, the asset management institution system 20 or the operation product seller system 30). "Order date" is managed product seller system 3
0 is the date when ordering the operation instruction. Either "buy" or "sell" is set in the "trading category" depending on the content of the operation instruction.

The "transaction category" is a category of the transaction subject to the above-mentioned trading process, and specifically, "payment", "transfer", "transfer", "asset disposal", "interest payment / Revenue sharing ”etc. are set. The "ordering amount / quantity" is the ordering amount or the ordering amount related to the operation instruction, and the quantity (number of units) is described in the sale instruction and the amount is described in the purchase instruction. The "contract amount / quantity" is the contract amount or contract amount shown in the contract result for the operation instruction, and the sales instruction describes the amount and the purchase instruction describes the quantity (number of units), respectively. It should be noted that the "ordered amount / quantity" and the "contracted amount / quantity" may be separate items for the amount and the amount. The “transaction status” indicates the current status of the transaction and is updated at any time according to the current trading stage of the transaction. In the present embodiment, either "accepted", "ordered", or "committed" is set in the "transaction status". As described above, the “individual detail key” is a key numbered by the operation product seller.

In the case of purchase shown in FIG. 13 and the case of sale shown in FIG. 14, when the subscriber operation instruction (buying instruction or selling instruction) is separately received from the subscribers A and B belonging to the same plan (arrow "a. "Reception"), the reception unit 1 newly adds a record regarding the subscriber A and a record regarding the subscriber B to the subscriber transaction statement database 6a. In addition,
At the time of receiving a trading order, the "Order number", "Order date" and "Commitment amount / quantity" (number of shares purchased or sale amount) are blank, and "Transaction status" is set to "Received". .

(Plan operation instruction order processing) Operation instruction section 2
The subscriber aggregates subscriber operation instructions for each plan, creates an operation instruction for each plan (hereinafter referred to as "plan operation instruction"), and orders the created plan operation instruction. FIG. 17 is a flowchart of a plan operation instruction processing routine executed by the operation instruction unit 2. This process is performed daily, for example, 3 times a day.
Executed at regular start times.

First, in step 1, the operation instruction section 2
Accesses the subscriber transaction details database 6a,
Items to be processed in this processing task (subscriber operation instructions) are extracted as target data. This extraction condition is whether the "ordering date" (ordering date) in the database 6a is a business date,
It is before that (order date ≤ business date).

In step 2, the operation instruction section 2 performs the aggregation processing of the extracted target data, aggregates the subscriber operation instructions for each subscriber on a plan basis, and outputs the operation instruction for each plan (plan operation instruction). To generate. Here, “plan unit” means that operation instructions of a plurality of subscribers regarding the same product are integrated into one, provided that they belong to at least the same plan. In that sense, it is at least necessary that the same "plan number" and the same "product code" are used as aggregation conditions for each plan. ", Etc. may be added as appropriate. In addition, in the case of a plan account type item management type product, in addition to the above-mentioned aggregation condition, the condition is that the "individual item key" is the same.

The ordering amount / quantity of the plan operation instruction (plan ordering amount / quantity) is the sum of the “ordering amount / quantity” of the plurality of subscriber operation instructions to be aggregated. For example, in the purchase case of FIG. 13, the purchase amount of subscriber A is 1,00
The sum of 0 yen and the purchase price of subscriber B 5,000 yen 6,000
Yen is the plan order amount. In addition, in the case of sale in FIG. 14, the sales quantity of subscriber A is 1000 units and the sales quantity of subscriber B is 1000 units.
The total quantity of 5000 units is 6000 units, which is the plan order quantity.

In step 3, the operation instruction section 2 assigns a new order number to the plan operation instruction generated in the previous step 2 and orders data in which the order number and the plan operation instruction are associated with each other. (Order data for each plan) is generated (arrow "b. Order" in FIGS. 13 and 14).

In the following step 4, the operation instruction section 2
Accesses the subscriber transaction statement database 6a and updates the database 6a. Specifically, regarding the subscriber operation instruction extracted as the target data, the order number assigned in step 3 is described and
The transaction status is set to "Ordered".

In step 5, the operation instruction section 2 accesses the plan transaction specification database 6b and adds a new record relating to the plan operation instruction created this time as an update process of this database 6b. FIG. 18 is a diagram showing an example of the plan transaction statement database 6b.
The plan transaction statement database 6b manages the transaction content and transaction status (status) of a project in which operation instructions of a plurality of subscribers belonging to the same plan are aggregated for the same product in plan units. The database 6b is configured as a set of records associated with each plan operation instruction. One record is "plan number", "product code", "order number", "order date",
"Trade category", "Trade category", "Order amount / quantity",
"Commitment amount / quantity", "Transaction status", "Individual item key"
And the like are associated with each other. In the plan transaction statement database 6b, transactions are managed on a plan basis, not on a subscriber basis, but there is no "subscriber number".
Other than that, the configuration is similar to that of the subscriber transaction statement database 6a. Similar to the subscriber transaction details database 6a, the registered items in the plan transaction details database 6b are also managed using the order number as a key.

Regarding the “plan number”, “commodity code”, “ordering date”, “trade category”, “transaction category”, etc. in the plan transaction statement database 6b, the information of the subscriber operation instruction which is the aggregation target remains unchanged. Taken over. Also,
"Order number" is the order number assigned in step 3, and "Transaction status" is "when adding a new record".
"Ordered" is set. In addition, "Order amount / quantity"
Is the plan order amount or the plan order quantity aggregated for each plan. For example, in the purchase case of FIG. 13, the plan order amount of 6,000 yen is described as “order amount / quantity” of the plan transaction statement database 6b, and in the sale case of FIG. 14, the plan order amount of 6,000 units is “order amount / quantity”. It is described as "quantity".

In the following step 6, the operation instruction section 2
Accesses the trading reception management database 6c and updates the database 6c. FIG. 19 is a diagram showing an example of the trading reception management database 6c. The trading reception management database 6c manages the reception status of operation instructions (plan operation instructions) in units of orders (plan units in this embodiment). The database 6c is configured as a set of records associated with each plan operation instruction. One record is "order number", "receiver category", "plan number", "product code", "creation date", "reception status", "receipt date", "result category"
It is configured by associating items such as "," and is managed using the "order number" as a key.

Here, the "order number" is the order number assigned in step 3. The "reception source category" is the reception source of the transmission data from the RK system 10, and is set to either "asset management organization" or "operating product seller". The “creation date” is the date when this record was created, and the “reception date” is the date when the data was received from the receiving source. The “reception status” indicates the reception status of the item, and is set to either “waiting for reception” or “received”. The “verification result classification” is the verification result from the asset management organization, and is set to either “OK (appropriate)” or “NG (unsuitable)”. The "verification result classification" is used only in the record for the asset management organization and not in the record for the managed product seller.

The operation instruction section 2 creates a record in the trading receipt management database 6c for each destination to which the operation instruction is transmitted. Therefore, in this step 6, usually, for one investment instruction, for the operation product seller (“reception source classification” = “operation product seller”) and for the asset management organization (“reception source classification” = “asset”). Two records of the management organization ") are generated.

Finally, in step 7, the operation instruction section 2 simultaneously transmits a plan operation instruction, which is ordering data, to the operation commodity seller system 30 and the asset management institution system 20 via the external interface 5 (see FIG. 13 and the arrow in FIG. 14, ').

(Trading Receipt Checking Process) The trading receipt checking unit 3 performs a receipt check from the operation product seller system 30 and the asset management institution system 20 as a pre-process of the trade result reflecting process, and the trading receipt management database 6
The update process of c is performed. FIG. 20 shows the trade reception check unit 3.
5 is a flow chart of a trade reception check processing routine executed by. The trading reception check unit 3 is an external system 2
Every time data is received from 0 or 30, this trade reception check processing is executed. The reception management is performed from the ordering of the plan operation instruction to the operation product seller system 30 until the reception of the verification result from the asset management institution system 20.

When the trade receipt check unit 3 receives the contract result data from the product seller system 30 (see FIG. 13).
And the arrow in FIG. 14), this process is activated at any time by using this reception as a trigger. When receiving the contract result data, the procedure from step 11 onward is executed according to the determination result of step 10. First, in step 11, the trading reception management database 6c is updated. Specifically, the trade reception check unit 3 includes a trade reception management database 6c.
And the record for the product seller is extracted using the order number that forms part of the contract result data as a key. Then, the “reception status” of the extracted record is changed from “waiting for reception” to “received” (update of reception status). Then, in step 12, the contract result data received from the managed product seller system 30 is transferred to the asset management organization system 20 (arrows in FIGS. 13 and 14), and the asset management organization side is requested to collate the contract results. The content transferred to the asset management institution system 20 is the contract result for each plan regardless of the account method. Through the above procedure,
The trade receipt check process on the date of receipt of the trade result data ends.

The asset management institution system 20 having received the contract result data collates the contract result data and sends the collation result to the RK system 10. Note that the asset management institution settles the purchase price and the sale price with the managed product seller on the settlement date specified by the contract result data.

On the other hand, when the trading reception check unit 3 receives the collation result data from the asset management institution system 20 (arrows in FIGS. 13 and 14), this reception is used as a trigger to start the present processing at any time. When the matching result data is received, the procedure from step 13 onward is executed according to the determination result of step 10. First, in step 13, the trading reception management database 6c is updated. Specifically, the trade reception check unit 3 accesses the trade reception management database 6c and extracts a record for the asset management institution using the order number as a key. Then, the “reception status” of the extracted record is changed from “waiting for reception” to “received” (update of reception status). And step 1
4, the trade receipt check unit 3 confirms that the verification result is OK.
The contract result data is output to the contract result reflection unit 4 under the condition that the above condition is satisfied (arrows in FIGS. 13 and 14). Through the above procedure, the trading reception check process on the contract collation data reception date ends.

(Contract Result Reflecting Process) Contract result reflecting unit 4
Is subject to the verification from the asset management agency,
The contract result is reflected in the transaction detail databases 6a and 6b and the balance databases 6d and 6e for each subscriber and for each plan (“c. Contract” in FIGS. 13 and 14). FIG. 21 shows
6 is a flowchart of a contract result reflection processing routine executed by a contract result reflection unit 4. The contract processing result reflection processing is executed at a time and date, for example, four times a day at regular time start, and sequentially processes the items output / accumulated from the trading receiving unit 3 in the preceding stage.

First, in step 20, the contract result reflecting unit 4 attaches contract result data for each plan / product as an update process of the plan transaction detail database 6b. Specifically, the contract result reflecting unit 4 accesses the plan transaction statement database 6b and extracts a record to be processed by using the order number in the contract result data as a key. And the "transaction status" of the extracted records
Change from "ordered" to "committed". At the same time, the contracted amount of sale or the contracted amount of purchase is described in the “contracted amount / quantity” of this record. For example, in FIG.
In the purchase case, if the contracted purchase amount for each plan is 6000 units, the balance amount / quantity of the plan (the number of units purchased)
Describes 6000 mouths. Further, in the case of sale in FIG. 14, when the contract sale amount for each plan is 6,012 yen, the "balance amount / quantity" (sale amount) of the plan is 6,012.
A circle is described.

In step 21, the contract result reflecting unit 4
Accesses the plan balance database 6d to update the contract balance in order to reflect the contract result. FIG. 22 is a diagram showing an example of the plan balance database 6d. The plan balance database 6d manages a cumulative total (plan balance) obtained by accumulating the balances of a plurality of subscribers belonging to the same plan for each product for each plan. This database 6d is
It is configured as a set of records associated with individual products for each plan, and one record is configured by associating items such as “plan number”, “product code”, and “balance information”. . "Balance information" includes contribution balance, balance quantity, book value balance, etc. for each plan.
It is held on both a contract basis and a delivery basis.

The contract result reflecting unit 4 extracts a record to be processed in the plan balance database 6d using the plan number and the product code in the contract result data as keys. Then, the contract amount / constant amount is added / subtracted to / from the current balance amount / balance amount described in the “balance information” of the extracted record. For example, in the purchase case of FIG. 13, regarding the purchased products, the “balance amount” of the plan to which the subscribers A and B belong is updated to 66006 units, which is the current number of 60,000 units plus an approximately constant amount of 6006 units. Further, in the sale case of FIG. 14, regarding the sold product, the “balance amount” of the plan to which the subscribers A and B belong is from the current quantity of 66006 units to the sales quantity of 6
It will be updated to 60006 with 000 subtracted.

In step 22, the contract result reflecting unit 4
Performs an apportioning process for each subscriber, that is, a process of apportioning a contracted amount of money or a contracted amount for each plan for each subscriber who belongs to the plan (calculation of contracted results for each subscriber).
This apportionment is performed according to the subscriber order amount or the proportion of the subscriber order amount to the plan order amount or plan order quantity. For example, in the purchase case of FIG. 13, the order amount 1,000 yen of the subscriber A accounts for 1/6 of the plan order amount 6,000 yen, and the order amount 5,000 yen of the subscriber B accounts for the plan order amount 6,000 yen. The ratio is 5/6. Therefore, for subscriber A, 1/6 of 6006 contracts (= 1001
5) out of 6006 units of purchase contract amount for subscriber B.
6 (= 5005 units) is apportioned. Further, in the sale case of FIG. 14, 1000 units of the sales amount (number of units sold) of the subscriber A account for 1/6 of the 6000 units sold of the plan, and the subscriber B
The sales amount of 5,000 yen is 5/6 of the 6000 units sold. Therefore, the subscriber A is prorated to 1/6 (= 1,002 yen) of the sold contract amount of 6,012 yen, and the subscriber B is prorated to 5/6 (= 5,010 yen) of the sold contract amount of 6,012 yen.

In step 23, the contract result reflecting unit 4
In order to reflect the contract result for each subscriber, the contract result data for each subscriber / commodity unit is attached as the updating process of the subscriber transaction statement database 6a. Specifically, the contract result reflecting unit 4 accesses the subscriber transaction statement database 6a, and extracts a record to be processed by using the order number added to the contract result data in plan units as a key. Then, the “transaction status” of the extracted record is changed from “ordered” to “committed”. At the same time, the "contract amount / quantity" of this record is the subscriber contract amount / quantity calculated in the previous step 23, that is, the plan contract amount or the plan contract amount is proportionally distributed to each subscriber. Described. For example, in FIG.
In the purchase case of No. 3, the subscriber transaction statement database 6a
In subscriber A's "balance amount / quantity" (number of units purchased), 1001 units are described, and subscriber B's "balance amount / amount"
5005 units are described in (Number of shares purchased). Further, in the sale case of FIG. 14, the "balance amount / quantity" (sale amount) of the subscriber A in the subscriber transaction statement database 6a is 1,
002 yen is described, and the subscriber B's "balance amount / amount" (sale amount) is 5,010 yen.

In step 24, the contract result reflecting unit 4
Accesses the subscriber balance database 6e, and updates the balance information described in the record corresponding to the case this time as the update processing. FIG. 23 is a diagram showing an example of the subscriber balance database 6e. The subscriber balance database 6e manages the balance of each subscriber on a subscriber basis. The database 6e is configured as a set of records associated with individual products for each subscriber, and one record includes “plan number”, “subscriber number”, “product code”, and “balance information”. Are associated with each other. "Balance information" includes contribution balance, balance quantity, book value balance, etc. for each subscriber.
It is held on both a contract basis and a delivery basis.

The contract result reflecting unit 4 accesses the subscriber transaction details database 6a and the plan transaction details database 6b, and reflects the contract result in the record specified by the order number added to the contract-based contract result. . Specifically, the record to be processed is extracted from the subscriber balance database 6e using the plan number, subscriber number, and product code in the contract result data as keys. Then, the contract amount / constant amount is added / subtracted to / from the current balance amount / balance amount described in the “balance information” of the extracted record. For example, in the purchase case of FIG. 13, the “balance amount” of the subscriber A in the subscriber balance database 6e.
Is updated to 11001 units, which is the total amount of 1001 units, which is prorated to the current number of 10,000 units, and is updated to 1101 units.
Will be updated to 55005 units, which is an addition of the approximately fixed amount of 5,005 units, which is distributed to the current quantity of 50000 units. Further, in the case of sale shown in FIG. 14, the subscriber A in the subscriber balance database 6e is
“Balance quantity” is the current quantity of 11001 units and sold quantity of 1000
It is updated to 10001 units after subtracting the number of units, and the "balance amount" of subscriber B is updated to 50005 units, which is the current quantity of 55005 units minus the sales amount of 5000 units.

According to this embodiment, the time and procedural burden on the subscriber regarding the trading procedure is reduced, so that the convenience of the subscriber can be improved. This is because, when ordering sales, the subscriber instructs the operation management organization (record keeper), which is a common contact point, without paying attention to which sales entity sells each managed product. Because you only have to do it. Further, since the subscriber does not need to directly contact the seller of the managed product, it is possible to reduce the risk of transfer of funds at the time of transfer and the fee, so that the burden on the subscriber can be further reduced.

[0107] Further, basically, the seller of managed products does not need to manage individual data of subscribers individually.
Merchandise can be bought and sold based on the plan operation instructions aggregated in plan units. As a result, it is possible to reduce system resources and office costs on the side of the managed product seller by releasing the management of personal data.
Furthermore, if the cost reduction on the side of the managed product seller is reflected in the dividend of the managed product, it will contribute to the profits of the subscribers.

On the other hand, operation management organization (record keeper)
For this reason, by constructing the system according to the present embodiment, it is possible to efficiently perform the record management for each subscriber and for each plan, and it is possible to speed up the process. That is, in the present embodiment, the information about the subscriber (transaction details or balance) and the information about the plan (transaction details or balance) are constructed in different databases.
Specifically, the transaction details are constructed separately by the subscriber transaction details database 6a and the plan transaction details database 6b, and the balances are constructed separately by the subscriber balance database 6e and the plan balance database 6d. There is. In this way, by building a separate database for each category (subscriber or plan), R can be compared with the case where the information of both categories is managed by a single database.
Data management in the K system 10 becomes easy. At the same time, when the information of one category is needed in another process, the necessary information can be quickly read from the database of that category, so that the processing speed can be increased. Especially in a defined contribution pension system where the record keeper needs to manage the record of a huge amount of data, if such a database is constructed, R
It is possible to significantly improve the efficiency of system processing in the K system 10.

Further, the transaction details for each subscriber and the transaction details obtained by aggregating them for each plan are linked to each other by the same order number. In other words, the record related to the operation instruction for each plan and the record related to the operation instruction for each subscriber, which is the target of aggregation when the operation instruction for each plan is generated, are linked by the order number. Since the order number is assigned for each order of the sales order, the sales can be uniquely specified from the order number. Then, in a series of trading processes from the ordering to the reflection of the contract, the transaction details of both the subscriber and the plan are managed based on the order number. As a result, the RK system 10 can easily specify the correspondence between the subscriber transaction details and the plan transaction details by using the order number as a key, and can efficiently manage the data for each subscriber / plan.

(Second Embodiment) As described above, in the defined contribution pension system, it is necessary to consolidate the operational instructions for each subscriber on a plan-by-plan basis and to distribute the contracted results for each plan on a per-subscriber basis. is there. Therefore, in the aggregation / proportioning process of products managed by the plan account method (base price type products, etc.), a fractional amount of money or a fractional amount is generated.
Here, the fractional amount is an indivisible amount that occurs during the fraction adjustment calculation, and is an amount less than the minimum currency unit (a decimal digit yen in the case of Japanese yen). In addition, the quantity fraction is an indivisible quantity (decimal digits of the quantity) that occurs during the fraction adjustment calculation, and is a quantity that is less than the minimum order quantity unit (decimal digits). Therefore, the present embodiment relates to a fraction adjustment process for ensuring fairness among subscribers at the time of aggregation / proportionation. The fraction adjustment occurs in the following three patterns as shown in FIG.

(Fraction adjustment pattern) (Pattern 1) Adjustment of fractional amount when apportioning sale contract amount (Pattern 2) Adjustment of quantity fraction when prorating proportional amount of purchase contract (Pattern 3) Aggregation of sales order quantity (sale quantity) Fraction adjustment

Since the system configuration of the RK system 10 is basically the same as that of the first embodiment, the description of the same parts will be omitted here. However, the items relating to the quantity in the above-mentioned database are held in units less than the unit (for example, the sixth place after the decimal point), and the items relating to the amount are held in the unit of the number of currency units. Further, the RK system 10 does not need to manage the fractional amount of money, but needs to record and manage the fractional quantity as a fractional adjustment account. The reason for not managing the fractional amount of money is that the fractional amount of money generated in a certain transaction is distributed to each subscriber in that transaction (therefore, the subsequent fractional amount of money is not used in subsequent transactions). Further, the reason for managing the quantity fraction is that the quantity fraction generated in a certain trading can be used in the subsequent trading. In the present embodiment, in the subscriber balance database 6e, the quantity fraction is managed as a dummy subscriber in plan units and product units. The dummy subscriber is a virtual subscriber provided exclusively for adjusting the quantity fraction, and is distinguished from a normal subscriber by being provided with a "fraction adjustment plan code".

(Pattern 1) When apportioning the sale contract amount
Fractional amount adjustment In the sale of products under the plan account method, there is a fractional amount when apportioning the delivery amount (plan sales contract amount) in units of plan for each subscriber. Therefore, the contract result reflecting unit 4 in the RK system 10 distributes the generated fractional amount of money to each subscriber involved in the sale. The subscriber who distributes the fractional amount of money is determined according to a preset priority rule. The priority rules are as follows, and the rules are applied in order of rule 1, rule 2, and rule 3. Most cases can be ranked by the application of Rule 1. Rule 2 is applied when the order of the subscribers cannot be determined by Rule 1 which is applied with the highest priority to ensure fairness among the subscribers, that is, the decimal fraction of multiple subscribers is the same. Will be the case. Rule 3 is applied to the case where the order of the subscribers cannot be determined by the rule 2, that is, the case where the sales quantities of a plurality of subscribers are the same. The fractional amount of money is distributed to each subscriber in the order of priority and in the smallest currency unit (one yen unit in the case of Japanese yen).

(Priority Rule) (Rule 1) Minimum Currency Unit in Calculation (Yen in this embodiment)
Lower order of money (Rule 2) Larger sales volume (Rule 3) Younger subscriber number

FIG. 25 is an explanatory diagram of the fractional amount adjustment when the sale contract amount is prorated. The order quantity of the plan is instructed by the subscribers A to E belonging to the same plan to sell products
It is assumed that the contract sale price for the 78 units was 94 yen. First, the contract sale amount of 94 yen is apportioned to the subscribers A to E in accordance with the equity ratio of each subscriber calculated on the basis of the sales volume. And the contract sale amount 94
The amount obtained by multiplying the yen by the equity ratio of each subscriber is the contracted sale price before the adjustment. This ownership ratio is determined as a ratio of the subscriber order quantity to the ordered plan order quantity (also considering the dummy subscriber order quantity). For example,
The equity ratio of subscriber A who sold 23.660 units is (23.660 / 7
8) Therefore, the contracted amount of this subscriber A's sale before adjustment is 28.5133 yen. Similarly to the case of the subscriber A, the subscriber sale contract amount of each of the subscribers B to E is also uniquely calculated from the product of the equity ratio of each subscriber and the plan sale contract amount.

Next, the fractional amount of the subscriber sale contract amount before adjustment is rounded down, and the subscriber sale contract amount after adjustment is calculated. Thereby, for example, the adjusted amount of money for the subscriber A is 28.5133 yen to 28.0000 yen, and the total amount of money for the subscribers A to E is 91.43333 yen to 90.0000 yen. In addition, since the initial contract sale price is 94 yen, 4.0000 yen will be included as a fractional amount.

Next, the subscribers A to E are rearranged according to the above-mentioned priority rule. In this case, ranking can be performed only according to Rule 1 (in order from the largest amount of money less than yen), and the priority order of the subscribers is that subscriber B is the highest priority, and
Subscriber A, subscriber C, and subscriber D are in this order. Then, in order of this subscriber, a fractional amount of 4 yen will be distributed in units of 1 yen. In this case, 1 yen is allocated to each of the top 4 subscribers E, C, B and A.

As described above, the fractional amount of money generated in this sale is prorated to the subscribers A to E involved in the sale, and the rounded down fraction is 0.0000 yen. As a result, it is not necessary to carry over the fractional amount of money for future trading, so the RK system 1
There is no need to manage the fractional amount of money at zero.

(Pattern 2) When apportioning the purchase contract amount
Adjusting the fractional quantity in the plan In the purchase of products under the plan account method, a fractional quantity is generated when the contracted quantity per plan (planned contracted quantity) is proportionally distributed to the weighted persons. Therefore, the contract result reflecting unit 4 in the RK system 10 rounds down the fractional quantity generated for each subscriber and manages it as a plan share. This quantity fraction is managed by the dummy subscriber as a fraction adjustment balance for each plan.

FIG. 26 is an explanatory diagram of the quantity fraction adjustment at the time of apportioning the purchase contract amount. Subscribers A to E who belong to the same plan direct purchase of products and plan order amount
It is assumed that the contract purchase amount for the 41 yen was 32 units. First, for each of the subscribers A to E, 32 units of the contracted purchase amount of the plan are distributed to each subscriber according to the equity ratio of each subscriber calculated on the basis of the purchase price. The amount of the contract purchase amount of 32 units multiplied by the equity ratio of each subscriber is the contract purchase amount before adjustment. This equity ratio is determined as the ratio of the subscriber order amount to the ordered plan amount. For example, since the ownership ratio of subscriber A who ordered the purchase of 14.0000 yen is (14/41), this subscriber A
The contracted amount of subscriber purchases before adjustment will be 10.926829 units.
Similarly to the case of the subscriber A, the contract sales amount of the subscribers B to E is also uniquely calculated from the product of the equity ratio of each subscriber and the contracted purchase amount of the plan.

Next, the number of significant digits (for example, the third place after the decimal point) of the subscriber purchase contract amount before adjustment is rounded down, and the adjusted subscriber purchase contract amount after adjustment is made an integer quantity. As a result, for example, the adjusted quantity of subscriber A is 10.926829 to 10.9260, and the total quantity of subscribers A to E is 32.0000.
From 00 to 31.9980. In addition, since the original contracted purchase amount of 32 units was 32 units, 0.0020 units were recorded as a fractional quantity and managed as the balance of dummy subscribers.
Regarding the apportionment of the purchase commitment amount, it is decided by apportioning the plan order amount of 41 yen by the share ratio based on the purchase amount.

As described above, the quantity fraction generated in the current purchase is prorated to the subscribers A to E involved in the purchase, and the quantity fraction less than the significant digit is set as the fraction adjustment balance 0.0020 units to the dummy subscriber. Managed by. In this way, RK system 1
By managing the quantity fraction with 0, the quantity fraction generated this time can be carried over to the next and subsequent sale.

(Pattern 3) Sales order quantity (sales quantity)
Volume fraction adjustment at the time of consolidation When the sale orders from multiple subscribers belonging to the same plan are consolidated, because the equity of each subscriber is managed including the fraction, the sale volume aggregated for each plan Fraction occurs in (plan sales quantity). The fraction less than one unit included in this plan sales quantity is the quantity that cannot be ordered in the order unit (plan unit). Therefore, in this case, with reference to the fraction adjustment account for each plan (plan equity), (1) round down the fractions included in the plan sales quantity, or
(2) By rounding up the fractional quantity included in the plan sale quantity, or by either method, the plan sale quantity is converted into an integer quantity that can be ordered. The above (2) is performed when the fractional adjustment account for each plan (plan equity) has already recorded the fractional quantity necessary for rounding up the fractional quantity. In this case, the recorded amount will be reversed and this will be added to the plan sales amount. For the quantity to be deducted from the fraction adjustment account by plan, the whole number of parts is sold, and for the fractional part (quantity fraction), only the minimum amount necessary for the fractional part of the plan sales quantity to be raised to an integer is taken. Break it down. In addition, in the case of reversal, a new transaction detail of sale of the dummy subscriber is newly created in the subscriber transaction detail database 6a, and the balance is updated at the timing of reflecting the contract result, like a normal subscriber involved in the sale. I do. The amount available for sale is grasped by using the balance of the dummy subscriber and the transaction details. The quantity available for sale is the quantity obtained by subtracting the quantity sold on the order basis from the quantity sold on the order basis (the quantity not yet arrived on the delivery date) from the balance quantity. On the other hand, the above (1) is when the above (2) cannot be performed, that is, when the quantity fraction necessary for rounding up the quantity fraction in the plan sales quantity is not recorded in the plan-specific fraction adjustment account. To be executed. Fractions that are rounded down from the plan sales amount are recorded in the plan-specific fraction adjustment account and managed as the balance of dummy subscribers.

FIG. 27 is an explanatory diagram of quantity fraction adjustment at the time of consolidating sales order quantities. It is assumed that the subscribers A to E belonging to the same plan direct the sale of a product and the total sales volume of the subscribers A to E is 76.700 units. In this case, the dummy subscriber's balance quantity (balance adjustment balance by plan)
As 1.500 units, that is, a fraction of the plan sales quantity
More than 0.300 units required to round up 0.700 units to 1.000 units are included. Therefore, 1.300 units (the whole number part is retired) will be revoked from the dummy subscriber's balance volume, and the final plan sales volume will be 78.000 units. And, as the balance quantity of the dummy subscriber after the reversal, it is 0.
200 mouths remain.

The above calculation method is equivalent to the following calculation method. That is, the sales quantity of each of the subscribers A to E is divided into an integer part and a decimal part, and the sum of each is calculated. When summing the integer parts, all the integer parts of the dummy subscribers are destroyed, so the balance quantity of the dummy subscribers is added.
As a result, dummy subscribers (1.000 units) and subscribers A ~
The total amount sold with E minutes (75.000 units) is 76.000 in the whole number part.
Speak In addition, the total of the decimal part excluding the dummy subscriber is
Since it is 1.700 units, the decimal part of the dummy subscriber is 0.3000.
By breaking down only the mouth, the total of the fractional part becomes 2.000. As a result, the number of plans sold will be 78.000, which is the total of 76.000 in the integer part and 2.000 in the decimal part. The balance of the dummy subscribers after reversal is 1.500-1.000
-0.200 = 0.3000.

As described above, in the present embodiment, the apportioning process of apportioning the contracted amount / quantity of the plan unit to the subscriber unit, or the aggregating process of consolidating the operation instruction of the subscriber unit into the plan unit is performed as a fractional amount and This is done after considering the fractional quantity. This makes it possible to reduce the burden of fraction management in the RK system 10 and at the same time, to ensure fairness among subscribers in proportional division and the like at a high level.

Further, in the present embodiment, the subscriber balance database 6e is provided with a dummy subscriber for the fraction adjustment account, and the quantity fraction is managed by the balance information of the dummy subscriber. In other words, the fraction adjustment account can be centrally managed in the subscriber balance database 6e, like a normal subscriber. as a result,
Since it is not necessary to separately provide a database for the fraction adjustment account, it is possible to improve the efficiency of system resources in the RK system 10.

A recording medium recording a computer program that realizes the functions of the above-described first and second embodiments may be supplied to the RK system 10 shown in FIG. In this case, at least one of the computers forming the RK system 10 can read and execute the computer program stored in the recording medium to achieve the object of the present invention. Therefore, since the computer program itself read from the recording medium realizes the novel function of the present invention, the recording medium recording the computer program constitutes the present invention. Examples of the recording medium recording the computer program include a CD-ROM, a flexible disk, a hard disk, a memory card, an optical disk, and a DVD-R.
Examples include OM and DVD-RAM. Further, the computer program itself for realizing each of the above-described embodiments also has a new function.

[0129]

According to the present invention, trading processing suitable for a defined contribution pension system can be realized systematically. That is, the record keeper, which manages a huge amount of data on a subscriber-by-subscriber basis, aggregates operation instructions for each subscriber on a plan-by-plan basis and places an order with the operation product seller as a plan-by-plan operation instruction. Especially when consolidating the sales volume for each subscriber,
By adjusting the quantity fraction, fairness among subscribers can be secured at a high level. Also, the record keeper reflects the contract result received from the managed product seller on a per-plan basis after apportioning it to each subscriber. In particular, when apportioning the contracted amount or contracted amount for each subscriber, if the fractional amount or the fractional amount is adjusted, the fairness among the subscribers can be secured at a high level.

[Brief description of drawings]

[Fig.1] Illustration of a corporate defined contribution pension system

FIG. 2 is a diagram showing a relationship between players.

FIG. 3 is a configuration diagram of a computer network system according to the present embodiment.

FIG. 4 is a diagram showing an interface at the time of purchase regarding a standard price type product

FIG. 5 is a diagram showing an interface at the time of purchase relating to a reserve balance accumulated product.

FIG. 6 is a diagram showing an interface at the time of purchase for a detailed management type product (plan account method).

FIG. 7 is a diagram showing an interface at the time of purchase for a detailed management type product (subscriber account method).

FIG. 8 is a diagram showing an interface at the time of selling a standard price type product.

FIG. 9 is a diagram showing an interface at the time of selling a reserve balance accumulated product.

FIG. 10 is a diagram showing an interface at the time of selling a detailed management type product (plan account method).

FIG. 11 is a diagram showing an interface at the time of selling a detailed management type product (subscriber account method).

FIG. 12 is a diagram showing a time-series flow of a series of trading processes.

FIG. 13 is a diagram showing an example of data management at the time of purchase.

FIG. 14 is a diagram showing an example of data management at the time of sale.

FIG. 15 is a diagram showing the relationship between transactions subject to sales transactions and sales categories.

FIG. 16 is a diagram showing an example of a subscriber transaction statement database.

FIG. 17: Flowchart of operation instruction ordering processing routine for each plan

FIG. 18 is a diagram showing an example of a plan transaction statement database.

FIG. 19 is a diagram showing an example of a trading reception management database.

FIG. 20 is a flowchart of a trade reception check processing routine.

FIG. 21 is a flowchart of a contract result reflection processing routine.

FIG. 22 is a diagram showing an example of a plan balance database.

FIG. 23 is a diagram showing an example of a subscriber balance database.

FIG. 24 is an explanatory diagram of a fraction adjustment generation pattern.

FIG. 25 is an explanatory diagram of the fractional amount adjustment when the sale contract amount is prorated.

FIG. 26 is an explanatory diagram of quantity fraction adjustment at the time of apportionment of purchase contract amount.

[Fig. 27] An explanatory diagram of quantity fraction adjustment at the time of consolidating sales order quantities

[Explanation of symbols]

1 reception desk 2 Investment instruction section 3 Trading reception check section 4 Execution result reflection section 5 External interface 6a Subscriber transaction details database 6b Plan transaction details database 6c Trading receipt management database 6d Plan balance database 6e Subscriber balance database 10 RK system 20 Asset management system 30 Managed product seller system

Claims (39)

[Claims] 1. In a defined contribution pension processing system, a subscriber transaction statement database that manages the transaction contents and transaction status relating to the operation instruction of each subscriber by means of a record provided corresponding to the operation instruction of each subscriber. By accessing the plan transaction statement database that manages the transaction contents and transaction status related to the operation instruction for each plan by the record provided corresponding to the operation instruction for each plan, and the subscriber transaction statement database, Generate an operation instruction that aggregates the operation instructions for each subscriber belonging to the plan for each plan, add a record related to the operation instruction for each plan to the plan transaction details database, and add the operation instruction for each plan to the network. And an operation instruction section for ordering to an operation product seller system connected via Defined contribution processing system according to claim. 2. The operation instruction unit generates a record regarding an operation instruction for each plan to be ordered and an operation instruction for each plan according to an order number assigned to each operation instruction to be ordered from the operation product seller system. The defined contribution pension processing system according to claim 1, characterized in that the defined contribution pension processing system is linked with a record relating to an operation instruction for each subscriber, which is the target of aggregation. 3. The operation instruction section adds up the purchase amounts for each subscriber at the time of placing an order to purchase the operation products,
The defined contribution pension processing system according to claim 1 or 2, wherein the purchase amount is calculated for each plan. 4. The operation order section adds up the sales quantity for each subscriber at the time of placing an order to sell the operation products,
The defined contribution pension processing system according to claim 1 or 2, characterized in that the sales amount in plan units is calculated. 5. The operation instruction section, when the quantity fraction necessary for rounding up the quantity fraction in the sales quantity of the plan unit is recorded in the plan-specific fraction adjustment account, the relevant quantity is recorded. The defined contribution pension processing system according to claim 4, wherein the sold amount of the plan unit including the number of fractions is made into an integer by reversing the fraction. 6. The operation order section, if the quantity fraction necessary for rounding up the quantity fraction in the sales quantity of the plan unit is not recorded in the fraction adjustment account for each plan, the sales quantity of the plan unit is added. The defined contribution pension processing system according to claim 5, wherein the included quantity fraction is rounded down, and the rounded down quantity fraction is recorded in the plan-specific fraction adjustment account. 7. The operation instruction section generates an operation instruction for each plan by aggregating operation instructions for each subscriber belonging to the same plan for each unit of the plan with respect to the standard price type product. The defined contribution pension processing system according to any one of claims 1 to 6. 8. The operation instruction section adds, in addition to the operation instruction of the subscribers belonging to the same plan, the operation instruction section of the item management type product managed by the plan account method, to the individual product provided by the operation product seller. The defined contribution pension processing system according to any one of claims 1 to 6, wherein the operation instruction is generated for each plan by aggregating by detail key unit. 9. When the operation instruction for each ordered plan is contracted, the contracted result for each plan is reflected in the plan transaction details database, and the contracted result for each plan is proportionally distributed to each subscriber. 3. The defined contribution pension according to claim 1 or 2, further comprising: a contract result reflecting section for calculating the contract result for each subscriber and reflecting the contract result for each subscriber in the subscriber transaction statement database. Processing system. 10. The contract result reflecting unit reflects the contract result in the record specified by the order number added to the contract result of the plan in the plan transaction statement database and the subscriber transaction statement database. The defined contribution pension processing system according to claim 9, wherein 11. The contract result reflecting unit calculates the contract sales amount per subscriber by apportioning the contract contract sales amount to each subscriber at the time of sales contract of the managed product. The defined contribution pension processing system according to claim 9 or 10. 12. The contract result reflecting unit distributes a fractional amount of money generated by proration of the contracted sale amount of money to each subscriber according to a preset priority rule. The defined contribution pension processing system according to item 11. 13. The defined-contribution pension processing system according to claim 12, wherein the priority rules are in descending order of amount of money less than the minimum calculated currency unit. 14. The contract result reflecting unit calculates the purchase contract amount for each subscriber by apportioning the purchase contract amount for each plan at the time of the purchase contract for the managed product to each subscriber. The defined contribution pension processing system according to claim 9 or 10. 15. The contract result reflecting section distributes the fractional quantity generated by the proportional distribution of the contracted purchase amount in plan units to each subscriber according to the ownership ratio of the subscriber calculated on the basis of the purchase price. The defined contribution pension processing system according to claim 14, wherein: 16. The contract result reflecting unit cuts off less than the significant digit of the contracted purchase amount of each subscriber and records the fractional quantity generated by the cutoff as a fraction adjustment account for each plan. The defined contribution pension processing system according to claim 15. 17. A trading reception management database that manages the reception status of operation instructions in plan units by a record provided corresponding to the order number, and a trading reception check unit that updates the reception status in the trading reception management database. The transaction reception check unit further sets the reception status in the record for the operation product seller specified by the order number to the reception waiting state when the operation instruction for each plan is transmitted to the operation product seller system. The receiving status in the record for the managed product seller specified by the order number is set to "received" when the contracted result for each plan is received from the managed product seller system. The defined contribution pension processing system described. 18. The transaction reception check unit sets the reception status in the record for the asset management institution, which is specified by the order number, to the reception waiting state when the operation instruction for each plan is transmitted to the asset management institution system. 18. When the collation result of the unit execution result is received from the asset management organization system, the reception status in the record for the asset management organization specified by the order number is set to "received". Defined contribution pension processing system. 19. The contract result reflecting section reflects the contract result in the plan transaction statement database and the subscriber transaction statement database, on condition that the trade receipt check section has obtained a collation from an asset management institution. The reflection of the contract result in step 1 is performed.
The defined contribution pension processing system described in 8. 20. The contract result reflecting unit updates the plan balance and the subscriber balance on the condition that the transaction reception check unit obtains a collation from the asset management organization. The defined contribution pension processing system according to claim 19. 21. In the defined contribution pension processing system, when ordering an operation instruction for a standard price type product to an operation product seller, an operation instruction in which the operation instructions for each subscriber belonging to the same plan are aggregated for each plan is generated. However, if the first means for transmitting the operation instruction for the plan unit to the operation product seller system connected via the network and the operation instruction for the accumulated fund balance type to the operation product seller, A second means for transmitting a unit operation instruction to an operation product seller system connected via a network, and an order for an operation instruction for an item management type product managed by the plan account method to the operation product seller , Generate an operation instruction that aggregates the operation instructions for each subscriber belonging to the same plan for each plan, and
When the third means for transmitting to the operation product seller system connected through the network and the operation instruction regarding the item management type product managed by the subscriber account management method are ordered to the operation product seller, And a fourth means for transmitting the operation instruction of the above to the operation product seller system connected through the network. 22. A defined contribution pension processing method executed in a record-related operation management institution system, wherein the system aggregates operation instructions for each subscriber belonging to the same plan for each plan A first step of generating an instruction, wherein the system assigns an order number for each operation instruction to be ordered from the operation product seller, and uses the order number as a key,
A second step of managing the transaction content and transaction status related to the operation instruction for each plan, and managing the transaction content and transaction status related to the operation instruction for each subscriber who is the aggregation target of the operation instruction per plan unit; The system further comprises a third step of transmitting the operation instruction in plan units to an operation product seller system connected via a network, the defined contribution pension processing method. 23. The settlement according to claim 22, wherein the first step includes a step of calculating the purchase amount for each plan by adding up the purchase amounts for each subscriber. Contribution pension processing method. 24. The defined contribution pension according to claim 22, wherein the first step includes a step of calculating the sales quantity for each plan by adding up the sales quantities for each subscriber. Processing method. 25. The first step, if a fractional quantity necessary for rounding up a fractional quantity in the quantity sold in units of a plan is recorded in a plan-specific fractional adjustment account, is recorded as such. 3. The method further comprises a fourth step of converting the quantity sold, which is a unit of the plan including the quantity fraction, into an integer quantity by performing the rounding down of the quantity fraction.
The defined contribution pension processing method described in 4. 26. In the fourth step, when the number of fractions necessary for rounding up the fraction of the quantity sold in plan units is not recorded in the plan-specific fraction adjustment account, the sale quantity in plan units 26. The defined contribution pension processing method according to claim 25, characterized in that the fractional quantity included in is rounded down, and the rounded down fraction is recorded in the plan-specific fractional adjustment account. 27. A fifth step in which, when an order-based operation instruction for a plan is executed, the system reflects the execution result for each plan in the transaction content related to the operation instruction for each plan; The sixth step of calculating the contract result for each subscriber by apportioning the contract result for each subscriber, and the system converts the contract result for each subscriber into the transaction content related to the operation instruction for each subscriber. 23. The defined contribution pension processing method according to claim 22, further comprising a seventh step of reflecting. 28. The method according to claim 27, further comprising an eighth step of specifying an operation instruction for each subscriber and an operation instruction for each plan based on the order number added to the execution result for each plan. Defined contribution pension processing method described in. 29. The sixth step includes the step of calculating the contracted amount of sale for each subscriber by apportioning the contracted amount of sale for each plan to each subscriber at the time of contracting sale of the managed product. 28. The defined contribution pension processing method according to claim 27. 30. The sixth step includes a step of distributing a fractional amount of money generated by proration of sale contract amount of money in plan units to each subscriber according to a preset priority rule. The defined contribution pension processing method according to claim 29. 31. The defined contribution pension processing method according to claim 30, wherein said priority rules are in the order of subscribers with the largest amount of money less than the minimum calculated currency unit. 32. The sixth step calculates the purchase contract amount for each subscriber by apportioning the purchase contract amount for each plan to each subscriber at the time of execution of the purchase contract for the managed product. 28. The defined contribution pension processing method according to claim 27, further comprising steps. 33. In the sixth step, a fractional quantity generated by apportioning the contracted amount of purchase contracts is distributed to each subscriber in accordance with the share ratio of the subscriber calculated on the basis of the purchase price. 33. The defined contribution pension processing method according to claim 32, further comprising: 34. The sixth step comprises a step of rounding down less than a significant digit of the contracted amount of purchase contracts for each subscriber, and a step of recording a quantity fractional amount generated by the truncation as a fraction adjustment account for each plan. 34. The defined contribution pension processing method according to claim 33, comprising: 35. The system further comprises an eighth step of managing the reception status of the operation instruction for each plan ordered by the order number, wherein the eighth step sells the operation instruction for each plan. When sending to the management system, the step of managing the reception status for the operation product seller specified by the order number as a reception waiting, and when receiving the execution result of the plan unit from the operation product seller system, specifying by the order number 28. The defined contribution pension processing method according to claim 27, further comprising the step of managing the reception status for the managed product seller as received. 36. In the eighth step, when the operation instruction in plan units is transmitted to the asset management organization system, the reception status for the asset management organization specified by the order number is managed as a reception waiting, 36. When the collation result with respect to the unit contract result is received from the asset management organization system, the step of managing the reception status for the asset management organization specified by the order number as received has been included. Defined contribution pension processing method. 37. In the defined contribution pension processing method executed in a record-related operation management institution system, when an operation order for a standard price type product is ordered from an operation product seller, the system belongs to the same plan. The first is to generate an operation instruction in which the operation instructions for each unit are aggregated for each plan and to send the operation instruction for each plan to the operation product seller system connected through the network.
And the order of the operation instruction regarding the accumulated fund balance type to the operation product seller, the system transmits the operation instruction for each subscriber to the operation product seller system connected via the network. When ordering a step and an operation instruction related to a detail management type product managed by the plan account method to an operation product seller, the above-mentioned system aggregates the operation instruction for each subscriber belonging to the same plan for each plan. Is generated, and the third step of transmitting the operation instruction in units of the plan to the operation product seller system connected via the network, and the operation instruction for the item management type product managed by the subscriber account management method are operated. When placing an order with a product seller, the system sells operation products in which operation instructions for each subscriber are connected via a network. 4 to be transmitted to the system
And a defined contribution pension processing method. 38. A computer program for causing a record-related operation management institution system to execute a defined contribution pension processing method, wherein the system aggregates operation instructions for each subscriber belonging to the same plan for each plan. A first step of generating an operation instruction for each plan; the system assigns an order number for each operation instruction to be ordered from the operation product seller, and uses the order number as a key,
A second step of managing the transaction content and transaction status related to the operation instruction for each plan, and managing the transaction content and transaction status related to the operation instruction for each subscriber who is the aggregation target of the operation instruction per plan unit; A computer program for causing a system for operating a record-related contribution to execute a defined contribution pension processing method, the system including a third step of transmitting the operation instruction in plan units to an operation product seller system connected via a network. . 39. A recording medium on which the computer program according to claim 38 is recorded.