JP7611791B2 - Information processing device, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and a program.

Conventionally, there are technologies for proposing and managing investment targets as a means of managing financial assets (see, for example, Patent Document 1).

JP 2016-095724 A

Traditionally, asset management services used by end users for asset management have been run by investment management companies using discretionary assets managed by individual financial institutions. In such cases, bundling has traditionally occurred. Details of bundling will be discussed later.

The present invention was made in consideration of this situation, and aims to eliminate bundling of multiple operational services offered by individual financial institutions.

In order to achieve the above object, an information processing device according to one aspect of the present invention comprises:
An end user device managed by an end user who receives N operation services (N is an integer value equal to or greater than 1) using his/her own assets;
an asset manager device managed by an asset manager who manages the end user's assets in a predetermined management unit;
M operator devices (M is an integer value of 1 or more) that are managed by M operators who operate at least a part of the N operation services by making contracts with the end users;
An information processing device that communicates with each other,
an individual unit management means for managing the N individual units by associating each of the N individual units obtained as a result of dividing the management unit in the information processing device with each of the N operational services operated within the framework of the management unit for the end user;
The individual unit management means
an operation service management means for managing data associated with a specific operation service, including contract status data indicating the status of the contract between the end user and the manager for the specific operation service, as operation service data, by linking the operation service data with an operation service identifier capable of identifying the specific operation service, and the individual unit associated with the specific operation service, for each of the N operation services;
a user interface means for providing a user interface used by the end user or the operator to the end user device or the operator device when the contract for the predetermined operation service is concluded, during the contract, or when the contract is terminated;
Including,
The individual unit management means executes processing using the operation service data in the individual unit associated with the specified operation service identifier based on an operation of the end user or the manager for the specified operation service using the user interface.

An information processing method and a program corresponding to the above-mentioned information processing device of one aspect of the present invention are also provided as an information processing method and a program of one aspect of the present invention.

The present invention makes it possible to eliminate bundling of multiple operational services within an individual financial institution.

FIG. 1 is a diagram for explaining a conventional technique for comparison with the first embodiment of the present invention, and is a diagram showing an overview of differentiated management in individual company back office systems. FIG. 13 is a diagram for explaining a conventional technique for comparison with the first embodiment of the present invention, showing an overview of a format for expanding a box for managing discretionary assets. FIG. 1 is a diagram for explaining problems of a conventional method for comparison with the first embodiment of the present invention, and is a diagram showing an overview of problems with simultaneous operation in a sub-account system. FIG. 1 is a diagram for explaining problems of a conventional method for comparison with the first embodiment of the present invention, and is a diagram showing an overview of problems with simultaneous operation in a sub-account system. FIG. 1 is a diagram for explaining problems of a conventional method for comparison with the first embodiment of the present invention, and is a diagram showing an overview of problems with simultaneous operation in a dedicated product method. 1 is a diagram showing a configuration of an information processing system including a service provider server according to a first embodiment of the present invention. 7 is a block diagram showing an example of a hardware configuration of a service provider server 1 in the information processing system of FIG. 6. 8 is a functional block diagram showing an example of a functional configuration of the service provider server shown in FIG. 7 according to the first embodiment of the information processing device of the present invention. 9 is a diagram for explaining an overview of a virtual account management section in the functional configuration of the service provider server in FIG. 8. FIG. 5 is a diagram for explaining an overview of the discretionary asset matching management unit and the individual management unit in the virtual account management unit, in comparison with the conventional method of FIG. 4. FIG. 9 is a diagram illustrating the discretionary asset matching management section of the virtual account management section in FIG. 8. This figure explains an example of a function related to an application from an end user as an example of a function of the end user transaction execution unit of the individual management unit of the virtual account management unit in Figure 8. This figure explains an example of a function related to contributions from an end user as an example of a function of the end user transaction execution unit of the individual management unit of the virtual account management unit in Figure 8. FIG. 10 is a diagram illustrating an example of a function related to virtual account opening, as an example of a function of an end-user transaction execution unit among the individual management units of the virtual account management unit in FIG. 8. FIG. 10 is a diagram illustrating an example of the function of a back-office generated transaction execution unit in the individual management unit of the virtual account management unit in FIG. 8 . FIG. 11 is a diagram showing an example of providing full-scale goal-based operation as a specific example of the effects that can be achieved by the service provider server 1 of the first embodiment. FIG. 17 illustrates an example implementation for providing the goal-based operation of FIG. 16. FIG. 11 is a diagram illustrating a conventional method for comparison with the second embodiment of the present invention, taking a subaccount system as an example. 19 is a diagram for explaining a conventional technique for comparison with the second embodiment of the present invention, using an example different from that of FIG. 18 . FIG. 13 is a diagram for explaining a problem of intermediary customer referral as a problem of a conventional method for comparison with the second embodiment of the present invention. FIG. 11 is a diagram showing a configuration of an information processing system including a service provider server according to a second embodiment of the present invention. 8 is a functional block diagram showing an example of a functional configuration of the service provider server shown in FIG. 7 according to a second embodiment of the information processing device of the present invention. FIG. 1 is a diagram showing an overview of a method for managing the contract status of discretionary investment contracts for management services provided by an investment management company. FIG. 1 is a diagram showing an overview of the flow of an end user's application for a discretionary investment contract with an investment management company. FIG. 1 is a diagram showing an overview of the process for an end user to terminate a discretionary investment contract with an investment management company. FIG. 23 is a diagram showing an overview of access control executed by a service provider server having the functional configuration of FIG. 22. FIG. 13 is a diagram showing an overview of the linking between management services and investment management companies, which is necessary for access control to management service data. FIG. 13 is a diagram illustrating an overview of access control for operational service data. FIG. 1 is a diagram showing an overview of end-user data acquisition and management. FIG. 1 is a diagram showing an overview of access control for end-user data. FIG. 1 is a diagram showing an overview of the hub functions of individual financial institutions and investment management companies. FIG. 23 is a diagram showing a specific example of a selective operation service among the services that can be provided by the bazaarization of operation services by the service provider server 1 of FIG. 22. FIG. 33 is a diagram showing an example of the flow relating to an application for a discretionary investment contract behind the scenes of the selective management service shown in the example screen of FIG. 32. FIG. 23 is a diagram showing a specific example of a basket-type operation service, among the services that can be provided by the bazaarization of operation services by the service provider server 1 of FIG. 22. FIG. 1 is a diagram showing an overview of an operation service. FIG. 13 is a diagram showing an example of a template for a discretionary investment contract document. 11 is a diagram showing the relationship between an operation service and an operation service ID. FIG. 1 illustrates the relationship between end users and accounts. A diagram showing the relationship between a general account and a trading account. A diagram showing an example of management of general accounts and account classifications. FIG. 2 illustrates the relationship between fund accounts and virtual account codes. FIG. 13 is a diagram showing an example of handling of investment targets. FIG. 1 is a diagram showing an example of a flow of new contributions. FIG. 13 is a diagram showing a flow of rebalancing. FIG. 13 is a diagram showing the relationship between portability and commands. FIG. 13 is a diagram showing the plug-in implementation of the conclusion of a discretionary investment contract and associated functions. FIG. 13 is a diagram showing an example of a connection method for electronic delivery of documents.

[First embodiment]
Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.

First, before describing the first embodiment of the present invention, a conventional method and its problems will be described.
FIG. 1 is a diagram for explaining a conventional technique for comparison with the first embodiment of the present invention, and shows an overview of differentiated management in individual company back office systems.

In order to launch new investment management services at individual financial institutions that manage assets not managed under discretionary investment contracts (hereinafter referred to as "non-discretionary assets"), it is necessary to manage assets managed under discretionary investment contracts (hereinafter referred to as "discretionary assets") separately.
The separate management of discretionary and non-discretionary assets is carried out in each company's back-office system.
There are two methods for managing discretionary assets separately: opening a sub-account to manage discretionary assets linked to a trading account (hereinafter referred to as the "sub-account method"), and preparing dedicated products for discretionary assets (hereinafter referred to as the "dedicated product method").
When a company wanted to enter into multiple discretionary investment contracts at the same time, the traditional approach was to expand the box that managed discretionary assets within each company's back-office system.
Separate management refers to the imposition of restrictions on assets that have been entrusted to an investment management company under a discretionary investment contract, to prevent end users from buying, selling, or withdrawing funds without the investment management company's knowledge.
The difference between the subaccount system and the dedicated product system is how cash is handled (under the subaccount system, cash is treated as cash, whereas under the dedicated product system, it is converted into cash equivalent securities (e.g., MRF) and then handled).

Here, the end user refers to the person who holds the general account. The person may be a natural person or a legal entity.
The subject of a given action taken by an end user, usually the end user, but also including actions taken by others on behalf of the end user.
Examples of other persons entrusted with the management of the operation of the system include guardians, guardians of minors, guardians of adults, and sales representatives of companies that sell the management service.
The seller of the investment management service may be an individual financial institution, or it may be an intermediary that acts as an intermediary or agent for the individual financial institution.

Figure 2 is a diagram for explaining a conventional method for comparison with the first embodiment of the present invention, and shows an overview of a format for expanding a box for managing discretionary assets.

When a company wanted to enter into multiple discretionary investment contracts at the same time, the traditional approach was to expand the box that managed discretionary assets within each company's back-office system.
This conventional method had issues with operating multiple investment services simultaneously on one trading account (hereinafter referred to as "simultaneous operation").
Below we will discuss the challenges of simultaneously operating the sub-account system and the dedicated product system.

Figure 3 is a diagram for explaining the issues of the conventional method for comparison with the first embodiment of the present invention, and shows an overview of the issues with simultaneous operation in the sub-account method.

Under the subaccount system, there are existing services that have introduced multiple operational services.
These existing services use a concept equivalent to a virtual account code in a fund account (such as a department or branch) to open sub-accounts upon receiving an application for management services.
However, with this method, it is necessary to define information equivalent to a virtual account code in advance and open sub-accounts, and there is no service that provides "simultaneous operation of any number of accounts."

Figure 4 is a diagram for explaining the issues of the conventional method for comparison with the first embodiment of the present invention, and shows an overview of the issues with simultaneous operation in the sub-account method.

This requires that the individual company back office systems implement the following steps 1 to 3 of processing in order to perform various processes (such as withholding capital gains tax) for which they are responsible.
The first process is a process of aggregating data to grasp transactions and asset status that have occurred across an entire trading account, including multiple subaccounts.
The second process is the processing of transactions and data across the aggregated trading accounts (transaction creation).
The third process is a process (apply) in which a transaction created for the entire trading account is split, recreated, and executed as transactions for non-discretionary assets and each subaccount.
The reason why it is necessary to implement the aggregation and division flow of the first to third processes is due to the difficulty of expressing processes of different granularity, such as transaction accounts and fund accounts, in a single system.
Due to the complexity (cost) of this system, sales on a certain scale are necessary from a business perspective, and services that provide simultaneous operation of pre-configured operational services are currently limited to individual major financial institutions.

Figure 5 is a diagram for explaining the issues of the conventional method for comparison with the first embodiment of the present invention, and shows an overview of the issues of simultaneous operation in the dedicated product method.

In order to realize simultaneous management using a dedicated product method, it was necessary to prepare different investment targets in order to separately manage the assets for each management service.
However, it is practically impossible to prepare different investment targets for an arbitrary number of operation services for the following first and second reasons.
The first reason is that investment targets for listed securities (such as individual stocks and ETFs) cannot be freely structured.
The second reason is that while unlisted securities (such as domestic unlisted investment trusts) can be structured to a certain extent, it takes time and is costly to structure them.
Therefore, there are no existing services that provide simultaneous operation of multiple operation services using a dedicated product method.
Although there are some companies that offer multiple types of investment services using a dedicated product system, they are either exclusive or have trading account restrictions, and currently there are no existing services that allow simultaneous operation of multiple investment services using the same trading account.

Next, we will explain the first embodiment of the present invention, which can solve the problems associated with the conventional methods described above.

Figure 6 is a diagram showing the configuration of an information processing system including a service provider server according to the first embodiment of the present invention.

The information processing system shown in Figure 6 is configured to include a service provider server 1 managed by a service provider, an individual company back office system 2 and an individual company operation server 3 managed by a financial institution individual company K, and an end user terminal 4 managed by an end user.
The service provider server 1, the individual company back office system 2, the individual company operation server 3, and the end user terminal 4 are connected to each other via a predetermined network N. Note that the network N is the Internet in this embodiment, but the form is not particularly limited, and other types of networks such as Bluetooth (registered trademark), Wi-Fi, and LAN (Local Area Network) can be adopted.

FIG. 7 is a block diagram showing an example of a hardware configuration of the service provider server 1 in the information processing system of FIG.
The service provider server 1 includes a CPU 11 , a ROM 12 , a RAM 13 , a bus 14 , an input/output interface 15 , an output unit 16 , an input unit 17 , a storage unit 18 , a communication unit 19 , and a drive 20 .

The CPU 11 executes various processes according to a program recorded in the ROM 12 or a program loaded from the storage unit 18 to the RAM 13 .
The RAM 13 also stores data and the like necessary for the CPU 11 to execute various processes.

The CPU 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input/output interface 15 is also connected to this bus 14. An output unit 16, an input unit 17, a memory unit 18, a communication unit 19, and a drive 20 are connected to the input/output interface 15.

The output unit 16 is composed of a display, a speaker, etc., and outputs various information as images and sounds.
The input unit 17 is composed of a keyboard, a mouse, etc., and is used to input various information.

The storage unit 18 is composed of a hard disk, a DRAM (Dynamic Random Access Memory), etc., and stores various data.
The communication unit 19 communicates with other devices (in the example of FIG. 6, the individual company back office system 2, the individual company operation server 3, and the end user terminal 4) via a network N including the Internet.

Removable media 31, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is appropriately loaded into the drive 20. A program read from the removable media 31 by the drive 20 is installed in the storage unit 18 as necessary.
Further, the removable medium 31 can store various data stored in the storage unit 18 in the same manner as the storage unit 18 .

Although not shown, the individual company back office system 2, the individual company operation server 3, and the end user terminal 4 of the information processing system in FIG. 6 also have the hardware configuration shown in FIG. 7.

Next, the functional configuration of the service provider server 1 having the hardware configuration shown in FIG. 7 will be described with reference to FIG.
FIG. 8 is a functional block diagram showing an example of the functional configuration of the service provider server shown in FIG. 7 according to the first embodiment of the information processing apparatus of the present invention.

As shown in FIG. 8, the CPU 11 of the service provider server 1 is provided with a virtual account management section 51 .
Here, the virtual account management unit 51 will be described with reference to FIG. 9 and FIG.

Figure 9 is a diagram outlining the virtual account management section of the functional configuration of the service provider server in Figure 8.

The basic policies of the first embodiment of the present invention for solving the problems of the conventional methods described above with reference to FIGS. 1 to 5 and for realizing simultaneous operation are the following policies 1 and 2.
That is, policy 1 is that a distinction is made between non-discretionary assets and discretionary assets in the individual company back office system 2, as shown in FIG.
Policy 2 is that, as shown in Figure 9, a management system for fund accounts (hereinafter also referred to as "virtual accounts" as appropriate) that subdivide discretionary assets for each management service will be set up on the service provider server 1 (external from the perspective of the individual company back office system 2).
The virtual account management unit 51 is the "fund account management system that subdivides discretionary assets for each management service" under policy 2.

The above-mentioned policy 1 can be realized in almost all individual company back office systems 2 by adopting either the dedicated product method or the subaccount method.
Therefore, by adopting a virtual account management unit 51 capable of realizing policy 2, simultaneous operation of multiple operational services becomes possible in most individual company back office systems 2.

In other words, it is assumed that, among the devices of financial institution individual company K that manage the assets of the end user, the individual company back office system 2 manages discretionary assets, which are assets under the management of the end user's discretionary investment contract, and non-discretionary assets, which are assets not under the management of the end user's discretionary investment contract, in the end user's trading account (Policy 1 above).
The virtual account management unit 51 communicates with the individual company back office system 2 via the communication unit 19 and performs the following management.
The virtual account management unit 51 performs processing to manage N fund accounts (four discretionary assets A to D in the example of Figure 9) obtained as a result of dividing the discretionary assets in the service provider server 1 into N, by corresponding each of the N management services (N is an integer value greater than or equal to 1) operated within the framework of discretionary assets.

Specifically, the virtual account management unit 51 is provided with a discretionary assets matching management unit 61 and an individual management unit 62 .
FIG. 10 is a diagram for explaining an overview of the discretionary asset matching management unit and the individual management unit in the virtual account management unit, in comparison with the conventional method in FIG.
In the individual company back office system 2, discretionary assets and non-discretionary assets are managed separately, as in the conventional method of FIG.
However, in the conventional method of FIG. 4, within the framework of a trading account in the individual company back office system 2, a sub-account is set and managed for each operation service.
In contrast, in the first embodiment of the present invention, discretionary assets and non-discretionary assets are simply managed separately in the trading accounts of the individual company back office system 2. Management for each management service is performed individually within the service provider server 1 using fund accounts for each management service (fund accounts A to C in the example of FIG. 10).
The functional block that performs this type of management is the virtual account management unit 51.
Specifically, in step SA, the discretionary asset matching management unit 61 attempts to share transactions with the individual company back office system 2 .
In step SB, the individual manager 62 applies transactions to each fund account. Here, applying a transaction means dividing and reconstructing transactions for the entire trading account on a fund account basis, and executing individual transaction processing for each fund account.

Furthermore, below, the discretionary asset matching management unit 61 and the individual management unit 62 will be explained separately in that order.

FIG. 11 is a diagram illustrating the discretionary asset matching management section of the virtual account management section in FIG.
As shown in FIG. 11, the discretionary asset matching management unit 61 imports all transactions related to discretionary assets that occur in the individual company back office system 2 and performs equivalent processing, thereby achieving sharing of the transactions of step SA in FIG.
11, a match is achieved between the entire discretionary assets in the individual company back office system 2 and the entire discretionary assets in the service provider server 1 (virtual account management unit 51). As a result, when performing necessary processing (e.g., capital gains tax calculation, etc.), the individual company back office system 2 does not need to grasp the distinctions within the fund accounts, and it is sufficient to grasp the total of the discretionary assets.
In the following, the state in which the entire discretionary assets of the individual company back office system and the service provider server 1 (virtual account management unit 51) match is referred to as "discretionary asset replication."
In other words, the discretionary asset consistency management unit 61 has a function of maintaining discretionary asset replication.

On the other hand, the individual management unit 62 has a function of managing the handling of fund accounts within the service provider server 1 (virtual account management unit 51).
In other words, the individual management unit 62 has the function of handling fund accounts that further subdivide discretionary assets within the service provider server 1 (virtual account management unit 51), assuming discretionary asset replication by the discretionary asset consistency management unit 61.

Here, in order to enable the service provider server 1 (virtual account management unit 51 ) to handle fund accounts in greater detail than the individual company back office system 2 , the individual management unit 62 places emphasis on the handling of transactions.
That is, transactions that occur in the operation service are broadly classified into the following three types.

The first type of transaction is an end-user transaction.
The transaction may involve, for example, a user order (new contribution, additional contribution, partial withdrawal, full withdrawal, change of investment style, installment deposit, etc.).
The functional block that controls the execution of this first type of transaction within the service provider server 1 (virtual account management unit 51) is the end-user transaction execution unit 71.

The second type of transaction is a transaction generated by the individual company back office system 2 .
The functional block that controls the execution of this second type of transaction within the service provider server 1 (virtual account management unit 51) is the back-office generated transaction execution unit 72.

The third type of transaction is a transaction generated by the service provider server 1 (virtual account management unit 51) (for example, a transaction related to rebalancing).
This transaction is, for example, associated with an execution order and its agreement (service provider server 1--execution order --> individual company back office system 2--agreement --> service provider server 1), collection of management fees, and the like.
Also for example, the transaction is an execution order, i.e. an order generated by the service provider server 1 for the purchase or sale of an investment security.
The functional block that controls the execution of this third type of transaction within the service provider server 1 (virtual account management unit 51) is the self-generated transaction execution unit 73.

Furthermore, below, the end user transaction execution unit 71 and the back office generated transaction execution unit 72 will be explained individually in that order.

Figure 12 is a diagram illustrating an example of a function related to an application from an end user as an example of a function of the end user transaction execution unit of the individual management unit of the virtual account management unit in Figure 8.

In order to provide the operation service, the end-user transaction execution unit 71 needs to accept transactions such as application, removal, and cancellation from the end-user.
For this type of transaction, the end-user transaction execution unit 71 provides virtual account code information and cooperates.

For example, assume that an end user makes a new application for operation service A. In this case, the following series of processes are executed.
First, it is assumed that an end user operates the end user terminal 4 to press "New Application" for operation service A on, for example, an individual company operation service page managed by the individual company operation server 3. In this case, a fund account opening instruction is issued, and the virtual account code A is linked to the service provider server 1. The fund account opening instruction includes the end user's trading account ID.
The end-user transaction execution unit 71 opens fund account A (a virtual account with virtual account code A for investment service A).
After this, in the case of the subaccount method and only for the first time, the discretionary asset matching management unit 61 executes a process for linking the subaccount opening instruction with the individual company back office system 2. As a result, a subaccount is opened in the individual company back office system 2.

Figure 13 is a diagram illustrating an example of a function related to contributions from an end user as an example of a function of the end user transaction execution unit of the individual management unit of the virtual account management unit in Figure 8.

Next, it is assumed that the end user makes a contribution using non-discretionary assets to the management service A shown in FIG. 12 for which the application has been completed.
In this case, the following series of processes are executed.
That is, first, the end user operates the end user terminal 4 to execute "contribution" for the operation service A, for example, on the individual company operation service page managed by the individual company operation server 3. In this case, a carry-out instruction is issued, and the virtual account code is linked in the service provider server 1. The contribution instruction includes the trading account ID along with the contribution amount.
The discretionary asset matching management unit 61 executes control to link the carry-out instruction with the individual company back office system 2. In the individual company back office system 2, a transfer instruction is given in the case of the subaccount system, and a purchase instruction for assets equivalent to cash is given in the case of the dedicated product system.
The individual company back office system 2 contributes from non-discretionary assets to discretionary assets in accordance with the contribution instruction.
The discretionary asset matching management unit 61 controls the linkage of contribution completion from the individual company back office system 2 to the service provider server 1 .
The end user transaction execution unit 71 performs the contribution process to fund account A.

Figure 14 is a diagram illustrating an example of a function related to opening a second virtual account as an example of a function of the end user transaction execution unit of the individual management unit of the virtual account management unit in Figure 8.

The service provider server 1 allows a financial institution to open a fund account according to an arbitrary virtual account code created as required by the financial institution.
If a virtual account code that has not been defined in advance is linked, a fund account can be opened in the same way. Here, "any number" means that there is no limit to the number of virtual accounts, in principle, except for hardware restrictions such as system resources.
Therefore, financial institutions can open any number of fund accounts according to their individual needs, and by managing assets separately in each fund account, they can "simultaneously manage any number of accounts."
That is, first, an end user operates the end user terminal 4 to press “new application” for operation service B, which is different from operation service A, on an individual company operation service page managed by the individual company operation server 3, for example.
In this case, a fund account opening instruction is issued, and the virtual account code B is linked to the service provider server 1. The fund account opening instruction includes the end user's trading account ID.
The end-user transaction execution unit 71 opens fund account B (a virtual account with virtual account code B for investment service B).
In this way, when opening a second or more fund accounts, the sub-accounts already opened on the individual company back office system 2 side are shared, so there is no need to open a new sub-account.

The above describes the end-user transaction execution unit 71 of the individual management unit 62 in Fig. 8. Next, the back-office generated transaction execution unit 72 of the individual management unit 62 will be described.
FIG. 15 is a diagram illustrating an example of the function of the back-office generated transaction execution unit in the individual management unit of the virtual account management unit in FIG. 8.

For example, it is assumed that a transaction occurs in the individual company back office system 2 in conjunction with the balance and buying and selling of discretionary assets.
Examples of transactions that occur within the individual company back office system 2 include the following:
The first transaction is a dividend or distribution (hereinafter referred to as a "dividend/distribution") on securities held in the discretionary assets.
The second transaction is the withholding of capital gains tax on the sale proceeds.
These transactions need to be captured by the service provider server 1 in order to maintain the state of discretionary asset replication.
However, since the individual company back office system 2 is responsible for processing the entire trading account, the granularity is different from that of the fund account managed by the service provider server 1, and conversion is necessary.
The back-office generated transaction execution unit 72 is a functional block that performs such conversion and executes transactions in units of fund accounts.

For example, in the case of dividends/distributions, the processing is carried out as follows:
In step SC1, the individual company back office system 2 registers dividend and distribution information from the investment target securities.
In step SC2, the individual company back office system 2 creates a transaction for depositing the dividend/distribution for the discretionary assets (hereinafter referred to as a "dividend/distribution transaction" in the procedure). Here, the information included in the dividend/distribution transaction includes the trading account ID, the securities ID, the payment amount, the balance reference date, the payment date, the total right holding quantity, etc.
In step SC3, the individual company back office system 2 executes (applies) the processing of the dividend/distribution transaction to the discretionary assets.
In step SC4, the discretionary asset matching management unit 61 of the service provider server 1 executes control for linking dividend/distribution transactions in the service provider server 1.
In step SC5, the back-office generated transaction execution unit 72 calculates the payment amount for each fund account from the dividend/distribution transaction and the securities balance of each fund account on the balance reference date. As a calculation method, for example, a method of apportioning the payment amount by the securities balance of each fund account on the balance reference date can be used.
In step SC6, the back-office generated transaction execution unit 72 deposits the funds into each fund account.

For example, the withholding of capital gains tax is processed in the same manner, as follows:
In step SD1, the individual company back office system 2 registers a sales agreement.
In step SD2, the individual company back office system 2 creates a transaction for withholding capital gains tax (hereinafter referred to as a "collection transaction" in the procedure) from the sale profit/loss and the total profit/loss. Here, information included in the collection transaction includes the trading account ID, the sale contract date, whether to withhold or refund, the settlement amount, etc.
In step SD3, the individual company back office system 2 executes (applies) the collection transaction process to the discretionary assets.
In step SD 4 , the discretionary asset matching management unit 61 of the service provider server 1 executes control for linking the collection transaction in the service provider server 1 .
In step SD5, the back-office generated transaction execution unit 72 calculates the settlement amount for each fund account from the collection transaction and the sale agreement for each fund account. The settlement amount can be calculated by a method such as dividing the amount by the sale agreement price for each fund account.
In step SD6, the back-office generated transaction execution unit 72 collects/refunds the settlement amount from each fund account.

As explained above regarding the withholding process for dividends/distributions and capital gains tax, the following two points are important:
The first important point is that transactions regarding discretionary assets are coordinated with the service provider server 1 .
The second important point is that the service provider server 1 can allocate the amount based on the data for each fund account held therein.
By satisfying these two points, even if there are any number of fund accounts, transactions generated in the individual company back office system 2 can be appropriately converted into fund account level transactions managed within the service provider server 1.

In summary, the service provider server 1 of the first embodiment communicates with the individual company back office system 2. This individual company back office system 2 manages discretionary assets and non-discretionary assets separately in the trading accounts of end users.
In this case, the virtual account management unit 51 of the service provider server 1 manages N virtual accounts (fund accounts) obtained as a result of dividing the discretionary assets within the service provider server 1 into N accounts by corresponding each of the N operating services (N is an integer value greater than or equal to 1) operated within the framework of discretionary assets.

The virtual account management unit 51 has a discretionary asset matching management unit 61 and an individual management unit 62 .
The discretionary asset reconciliation management unit 61 manages to maintain a consistent state between the discretionary assets in the individual company back office system 2 and the discretionary assets in the service provider server 1 by executing processing of all transactions related to the end user's discretionary assets that occur in the individual company back office system 2.
The individual management unit 62 manages the N virtual accounts by executing transaction processing using the virtual accounts associated with each of the N operational services, assuming the above-mentioned matching state.

The individual management unit 62 has an end-user transaction execution unit 71 , a back-office generated transaction execution unit 72 , and a self-generated transaction execution unit 73 .
The end-user transaction execution unit 71 executes transaction processing based on an operation by an end user as transaction processing for a predetermined operation service among the N operation services.
The back-office generated transaction execution unit 72 processes transactions related to the predetermined operation service among transactions generated in the individual company back-office system 2 as transactions for the predetermined operation service.

The service provider server 1 of the first embodiment thus configured can achieve the following various effects.
That is, by applying the service provider server 1 of the first embodiment, it becomes possible to link any number of fund account openings with management services.

Specifically, for example, as shown in FIG. 16, by applying the service provider server 1 of the first embodiment, it is possible to provide, for example, a full-scale goal-based operation.
FIG. 16 is a diagram showing an example of providing a full-scale goal-based operation as a specific example of the effect that can be achieved by the service provider server 1 of the first embodiment.

That is, the end user M operates the end user terminal 4 to start registering a new goal on the screen G1.
The end user M operates the end user terminal 4 to select the goal name, period, and starting investment amount, as well as the management service to which the management will be entrusted, on the screen G2, and submits an application.
Financial institution individual company K (individual company operation service page managed by individual company operation server 3) issues a virtual account code at the same time as the application, and links a fund account opening instruction and the virtual account code to the service provider server 1.
The service provider server 1 receives the instruction and opens a fund account.
A discretionary investment contract is concluded between end user M and investment management company T.
The individual company back office system 2 transfers cash from the non-discretionary assets to the discretionary assets of the trading account.
The service provider server 1 registers a new contribution order in the fund account.
This allows the investment management business operator T to start managing the assets in the fund account. That is, the end user terminal 4 displays screen G3.

Figure 17 shows an example implementation of the goal-based operation shown in Figure 16.

In other words, as an example scenario, we will consider a case where an end user already has three fund accounts (retirement funds, education savings (for eldest son), and overseas travel savings for 2021) and starts a new overseas travel savings for 2022 with discretionary management.

The flow at this time is as follows:
In step SE1, the end user operates the end user terminal 4 to select one of a number of management services and apply for a new savings management plan.
In step SE2, when an application is made, the individual company management server 3 assigns a virtual account code D for the new management and instructs the service provider server 1 to open a fund account.
In step SE3, the service provider server 1 instructs the individual company back office system 2 to contribute the investment start amount. Upon receiving the contribution instruction, the individual company back office system 2 transfers the contributed amount from the non-discretionary assets to the discretionary assets.
In step SE4, after the contribution is completed, the service provider server 1 opens a new fund account linked to the virtual account code D and starts operation.

Furthermore, for example, application of the service provider server 1 of the first embodiment makes it possible to reduce the degree of difficulty in development and the associated costs.
As mentioned above, there was a difficulty in implementing processes with different granularity in a single system.
By applying the service provider server 1 of the first embodiment, the individual company back office system 2 is responsible for data processing of the entire trading account, and the service provider server 1 is responsible for data distribution to the fund account.
By applying the service provider server 1 of the first embodiment, it can be said that the degree of difficulty of development is reduced compared to the conventional method for the following two reasons, and an advantage in terms of cost is recognized.
The first point is that the system is divided according to the granularity (hierarchy) of the targets: trading accounts and fund accounts.
The second point is that the function of operating an operation service individually (for example, only one) in the individual company back office system 2 can be utilized (improved reusability).

The information processing device to which the present invention is applied is not particularly limited to the service provider server 1 of the first embodiment, and various other embodiments are possible.
Specifically, for example, the information processing device to which the present invention is applied is
Among devices of a manager who manages a predetermined object, an information processing device that at least communicates with another information processing device that distinguishes and manages a first type management unit and a second type management unit in a management unit in which the predetermined object is managed,
An information processing device can be adopted which is equipped with an individual unit management means which corresponds, for each of N services (N is an integer value equal to or greater than 1) operated within the framework of the first type management unit, to each of the N individual units obtained as a result of dividing the first type management unit within the information processing device into the N units, and executes a process of managing the N individual units.

Here, if we associate this with the service provider server 1 of the first embodiment,
The predetermined object is an asset,
the unit of management is an end user's trading account;
the first type management unit is a discretionary asset of the end user;
The second type of management unit is a non-discretionary asset of an end user;
the service is an operation service,
The individual units are virtual accounts.

However, to reiterate, the information processing device having such a configuration is not particularly limited to the service provider server 1 of the first embodiment.
That is, by appropriately modifying the embodiment of the information processing device having such a configuration, it is possible to expand the range of application as follows, for example.
For example, asset migration of non-discretionary assets allows for virtual account implementation of the entire securities account.
For example, the service provider server 1 in the first embodiment does not require the presence or absence of an investment mandate contract, and this point is the same in the other embodiments.
Thus, for example, discretionary asset replication can be extended to maintain trading account replication, allowing extension to trading accounts.
For example, in the case of trading account replication, not only transactions of discretionary assets but also transactions of the entire trading account can be processed in cooperation with the service provider server 1 .
For example, it can be expanded to assets other than securities.
For example, the service provider server 1 in the first embodiment does not limit the type of transaction, and this also applies to the other embodiments.
Therefore, for example, it is possible to expand transactions to include cash, security tokens, cryptocurrencies, etc.

[Second embodiment]
Next, a second embodiment of the present invention will be described with reference to the drawings.

First, before explaining the second embodiment of the present invention, we will explain the conventional method and its problems.

Figure 18 is a diagram explaining a conventional method for comparison with the second embodiment of the present invention, using the subaccount method as an example.

Investment trusts, which are widely used for asset management, involve numerous investment trust management companies and are formulated to suit specific purposes.
On the other hand, participation in conventional investment management services as an investment management company T is generally provided by a single company.
From the end user's perspective, this appears as if the account and operational services have been bundled together (hereinafter referred to as "bundling").
This bundling creates no pressure to select, making it difficult to encourage the evolution of services, such as by reducing costs or improving operational capabilities.
As described in the first embodiment, there are currently limitations on the number of operations services that can be provided using a company's own account.
The following description will be based on the conventional sub-account method described in the first embodiment shown in FIG.
Since the slots are limited, there is little incentive to incorporate multiple investment management companies T, and no existing services exist.
One reason for the lack of incentive is the high cost of opening additional sub-accounts.
Because the cost of opening additional sub-accounts is high, in order to maintain economic rationality, financial institutions themselves or their group companies often act as investment managers.

Figure 19 is a diagram illustrating a conventional method for comparison with the second embodiment of the present invention, using an example different from that of Figure 18.

In addition, as shown in FIG. 19, there are cases where the system provider or its group company becomes the investment management companies T1 and T2.
In this case, the system provider may bear the cost of opening additional sub-accounts, so that no burden is incurred by the individual financial institutions KA and KB.
However, the essential incentive structure remains the same; the only change is that the party responsible for collecting the burden has been the system provider.
The second reason for the lack of incentives is the costs involved in incorporating new investment managers T1 and T2.
Under conventional methods, in most cases individual financial institutions connect directly with investment management companies.
For example, if investment management company T1 and investment management company T2 wish to provide management services to individual financial institutions KA and KB, four connections are required: individual financial institution KA-investment management company T1, individual financial institution KB-investment management company T1, individual financial institution KA-investment management company T2, and individual financial institution KB-investment management company T2.
This means that as the number of individual financial institutions KA, KB and investment management companies T1, T2 increases, the number of connections increases exponentially, and the cost of these connections is one of the obstacles to eliminating bundling.

Figure 20 is a diagram explaining the issue of intermediary customer referral as an issue of the conventional method for comparison with the second embodiment of the present invention.

One way to resolve the issues with bundling is to use intermediary traffic.
The intermediary customer introduction refers to a method in which an individual financial institution KA that is implementing an operation service introduces an end user M to another individual financial institution KB that is also implementing an operation service.
Even when using an intermediary to send customers, the following first to third hurdles exist.
The first hurdle is to avoid outflow of deposit balances (outflow of assets) at the individual financial institutions (KA) that are the source of the customers.
The second hurdle is the cost of connecting with the destination.
The third hurdle is the possibility of a bias towards promoting the most profitable operational services (including the company's own services).
Because of these first to third hurdles, although intermediary customer referrals partially solve the bundling issues, they cannot be said to be sufficient.

Next, we will explain the second embodiment of the present invention, which can solve the problems associated with the conventional methods described above.

Figure 21 is a diagram showing the configuration of an information processing system including a service provider server according to the second embodiment of the present invention.

The information processing system shown in FIG. 21 is configured to include a service provider server 1 managed by a service provider, individual company back office systems 2-1 through 2-p and individual company investment servers 3-1 through 3-k managed by p (p is an integer value of 1 or greater) individual financial institutions K1 through Kp, end user terminals 4-1 through 4-q managed by q (q is an integer value of 1 or greater) end users M1 through Mq, and investment management company terminals 5-1 through 5-r managed by r (r is an integer value of 1 or greater) investment management companies T1 through Tr, respectively.

In the following, when there is no need to distinguish between the individual financial institutions K1 to Kp, they will be collectively referred to as the "individual financial institution K." When referring to the individual financial institution K, the individual back-office systems 2-1 to 2-p will be collectively referred to as the "individual company back-office system 2," and the individual operation servers 3-1 to 3-k will be collectively referred to as the "individual company operation server 3."
Furthermore, when there is no need to distinguish between end users M1 to Mq, they will be collectively referred to as "end user M." Furthermore, when referring to end user M, end user terminals 4-1 to 4-q will be collectively referred to as "end user terminal 4."
Furthermore, when there is no need to distinguish between the investment management providers T1 through Tr, they will be collectively referred to as the "investment management provider T." Furthermore, when referring to the investment management provider T, the investment management provider terminals 5-1 through 5-r will be collectively referred to as the "investment management provider terminal 5."

The service provider server 1, the individual company back office system 2, the individual company management server 3, the end user terminal 4, and the investment management company terminal 5 are connected to each other via a specified network N. Note that in this embodiment, the network N is the Internet, but the form is not particularly limited, and other types of networks such as Bluetooth (registered trademark), Wi-Fi, and LAN (Local Area Network) can also be used.

Although not shown, among the information processing system of FIG. 21 of the second embodiment, the service provider server 1, the individual company back office system 2, the individual company management server 3, the end user terminal 4, and the investment management company terminal 5 also have the hardware configuration shown in the service provider server 1 of FIG. 7 of the first embodiment.

Next, with reference to FIG. 22, a functional configuration of the service provider server 1 according to the second embodiment having the hardware configuration shown in FIG. 7 will be described.
FIG. 22 is a functional block diagram showing an example of the functional configuration of the service provider server shown in FIG. 7 according to the second embodiment of the information processing apparatus of the present invention.

As shown in FIG. 22, the CPU 11 of the service provider server 1 is provided with a virtual account management section 51 .
The virtual account management unit 51 of the second embodiment is provided with a discretionary asset matching management unit 61, an individual management unit 62, and a user interface control unit 63 similar to those of the first embodiment, as well as an access control unit 64, an end user management unit 65, an operation service management unit 66, and an investment management company management unit 67.
The storage unit 18 of the service provider server 1 is provided with an end user DB 81 , an investment management service DB 82 , and an investment management company DB 83 .

Here, the basic policies of the second embodiment of the present invention for solving the problems of the conventional techniques described above with reference to FIGS.
Basic policy 1 is a policy that enables a plurality of individual financial institutions (individual financial institutions KA and KB in the example of FIG. 20) to inexpensively realize simultaneous operation of a plurality of operational services.
Basic policy 2 is a policy that standardizes connections with multiple investment management companies (investment management companies T1 and T2 in the example of FIG. 20) so that these multiple investment management companies can be incorporated at low cost.
The simultaneous operation of Basic Policy 1 can be achieved by simply applying the method of any number of virtual accounts to a trading account that was made possible in the first embodiment. Therefore, the service provider server 1 of the second embodiment has, in principle, the same functional configuration as the service provider server 1 of the first embodiment, that is, the discretionary asset matching management unit 61, the individual management unit 62, and the user interface control unit 63 as in the first embodiment.
Therefore, in the following explanation, as functional configurations for realizing basic policy 2, we will explain the differences from the first embodiment, namely, the access control unit 64, the end user management unit 65, the operation service management unit 66, and the investment management company management unit 67, with reference to Figures 23 to 30 as appropriate.

First, in order to realize Basic Policy 2, a discretionary investment contract between end user M and an investment management company is a prerequisite. Therefore, the management of the contract status, application, and cancellation of a discretionary investment contract with an investment management company will be explained with reference to Figures 23 to 25.

Figure 23 shows an overview of the method for managing the contract status of discretionary investment contracts for management services operated by an investment management company.

As a premise, a discretionary investment contract is made for each management service. This discretionary investment contract is concluded between the end user M and the investment management business operator T.
However, since financial institution K is responsible for holding, purchasing, and selling securities, the written discretionary investment contract may be prepared in joint names.
The discretionary investment contracts are managed as "discretionary investment contract document template sets" (hereinafter referred to as "template sets") for each management service.
In order to realize multiple discretionary investment contracts, as shown in FIG. 23, the virtual account management unit 51 of the service provider server 1 distinguishes the template sets that make up the discretionary investment contracts for each management service, and enables the investment management company T to manage the template sets through a management screen or API.

The functional blocks that function to realize the method of managing the contract status of a discretionary investment contract as shown in FIG. 23 are an operation service management unit 66 and a user interface control unit 63.
The operation service management unit 66 manages data linked to a predetermined operation service, including a template set for a discretionary investment contract between the end user M and the investment management business operator T for the predetermined operation service, as operation service data. Note that operation service data other than the template set will be described later. The operation service data is stored in the operation service DB 82 for each of multiple operation services.
Specifically, for example, the operation service management unit 66 links the operation service data (only the template set is shown in the example of Figure 23), an operation service ID that can identify the specified operation service, and the specified operation service (and the associated fund account), and manages each of N operation services (three operation services A, B, and C in the example of Figure 23).
The user interface control unit 63 provides the end user terminal 4 or the investment management company terminal 5 with a user interface (a management screen or API in the example of Figure 23) to be used by the end user M or the investment management company T when concluding, during, or canceling a discretionary investment contract for a specified management service.

Next, the flow of application for a discretionary investment contract by an end user M with an investment management business operator T will be described.
FIG. 24 is a diagram showing an outline of the flow of an application for a discretionary investment contract by an end user with an investment management business operator.

The virtual account management unit 51 of the service provider server 1 manages the contract status of a discretionary investment contract for each combination of a fund account and management service.
For example, the flow of a contract application is as follows.
That is, in step SF1, end user M operates end user terminal 4 to select a fund account for which he/she wishes to introduce the management service on financial institution individual company K (individual company management service page managed by individual company management server 3).
In the following, the act of end user M operating end user terminal 4 to perform a specified action on financial institution individual company K (individual company operation service page managed by individual company operation server 3) will be abbreviated as "end user M performs a specified action."
In step SF2, the end user M selects a management service that entrusts the management of the fund account to the end user.
In step SF3, the end user M applies for the operation service. At that time, the end user M confirms and agrees to the pre-contract documents and the like.
In step SF4, the operation service management unit 66 of the service provider 1 registers the discretionary investment contract in the operation service DB 82 as being under application.
In step SF5, the investment management business operator T operates the investment management business operator terminal 5 to obtain all of the discretionary investment contracts (management service data such as data sets) for which applications are being made.
In step SF6, investment management business operator T operates investment management business operator terminal 5 to accept the application.
In step SF7, the operation service management unit 66 of the service provider server 1 accepts the application and registers the discretionary investment contract (operation service data such as a data set) in the operation service DB 82 as having been concluded.
In step SF8, the discretionary asset matching management unit 61 of the service provider server 1 executes control to link the conclusion information to the individual company back office system 2 of financial institution individual company K.
In step SF9, financial institution individual company K (individual company management service page managed by individual company management server 3) notifies end user M that a discretionary investment contract has been concluded via end user terminal 4. Note that the fact that a discretionary investment contract has been concluded may be notified to end user M by email or mail, without going through end user terminal 4.

Next, a process for the end user M to terminate a discretionary investment contract with the investment management business operator T will be described.
FIG. 25 is a diagram showing an overview of the process for an end user to cancel a discretionary investment contract with an investment management company.

The virtual account management unit 51 of the service provider server 1 cancels a discretionary investment contract for each combination of fund account and management service, in the same manner as for applications.
For example, the process for terminating a contract is as follows:
That is, in step SG1, end user M operates end user terminal 4 to apply for cancellation of the operation service on financial institution individual company K (individual company operation service page managed by individual company operation server 3).
In the following, the act of end user M operating end user terminal 4 to perform a specified action on financial institution individual company K (individual company operation service page managed by individual company operation server 3) will be abbreviated as "end user M performs a specified action."
In step SG2, the financial institution KA specifies the discretionary investment contract for the target management service and submits a cancellation request to the service provider server 1. In this case, the discretionary investment contract is uniquely identified by the fund account and the management service.
In step SG3, the operation service management unit 66 of the service provider 1 receives the cancellation application and registers the contract as being cancelled in the operation service DB 82.
In step SG4, the operation service management unit 66 acquires from the operation service DB 82 a list of contracts for which the operation service is in a cancelled state.
In step SG5, the operation service management unit 66 creates an asset sale instruction for the assets in the fund account linked to the contract being terminated.
In step SG6, the discretionary asset matching management unit 61 of the service provider server 1 executes control to link an asset selling instruction to the individual company back office system 2 of financial institution individual company K.
In step SG7, the discretionary asset matching management unit 61 executes control to link the agreements associated with the sales instructions from the individual company back office system 2 of financial institution K.
In step SG8, upon completion of the transfer of all contracts associated with the sale of assets, the management service management unit 66 registers the discretionary investment contract as terminated in the management service DB 82 in step SG9.

Next, the access control required to realize the basic policy 2 of the second embodiment will be described.
FIG. 26 is a diagram showing an outline of the access control executed by the service provider server having the functional configuration of FIG.

In order to properly execute the discretionary investment contract, the investment management businesses TX and TY are required to carry out, for example, the following first to third businesses.
The first task is to monitor the operational status as the responsibility of the operations manager.
The second task is to periodically check the appropriateness of the contract (e.g., anti-money laundering checks) as a responsibility of the party that enters into the contract.
The third business is customer support.
In order to carry out these first to third businesses, the investment management businesses TX and TY need to understand the data held by the service provider 1, such as customer information, contract data, and management information.
Naturally, it is not permitted for an investment management company TY, which provides a different management service, to refer to data on the management service provided by an investment management company TX. Conversely, it is not permitted for an investment management company TX, which provides a different management service, to refer to data on the management service provided by an investment management company TY.
On the other hand, when an individual financial institution KX provides an operation service, it is necessary to refer to data on the entire operation service.
For the above reasons, in order for multiple investment management companies TX and TY to participate in the management service, it is necessary to create a mechanism for appropriately controlling access to data from individual financial institutions KA and the investment management companies TX and TY. Such a mechanism or process for appropriately controlling access is called access control.
The access control is performed by the access control unit 64 shown in FIG.

There are three types of data held within Service Provision 1: The first type of data is data linked to the operational service.
The second type of data is data linked to end user M.
The third type of data is other data.

The data associated with the first type of operation service is operation service data.
That is, the management service data includes, in addition to the template set as shown in FIG. 23, information regarding the contract and management information within the fund account, for example.
As described above, the operation service data is stored for each operation service in the operation service DB 82 in Fig. 22 and managed by the operation service management unit 66. That is, an operation service ID capable of identifying the operation service is assigned to the operation service, and the operation service ID is linked to the operation service data and managed.

The second type of data linked to end user M (hereinafter referred to as "end user data") is, for example, customer information (so-called personal information) such as end user M's name and address.
The end user data is stored in the end user DB 81 in Fig. 22 and managed by the end user management unit 65. That is, the end user M is assigned an end user ID that can identify the end user M, and the end user ID is linked to the end user data and managed.

The third type of other data includes, for example, brand master data and various settings.
Additionally, data relating to investment management company T (hereinafter referred to as "investment management company data") is also an example of other data. The investment management company data is stored in investment management company DB 83 of Fig. 22 and managed by investment management company management unit 67. That is, an investment management company T is assigned an investment management company ID that can identify it, and the investment management company ID is managed in association with the investment management company data.

Access control is required for a first type of operational service data and a second type of end-user data.
Therefore, the following describes access control for both operational service data and end user data.

Figure 27 shows an overview of the linking between management services and investment management companies, which is necessary for access control to management service data.

In preparation for access control to management service data, the service provider server 1 first links the management service ID with the investment management company ID in order to manage the link between the investment management company T and each of the one or more management services provided by the investment management company T.
This makes it possible to link the management service data with the investment management company T.

Figure 28 shows an overview of access control for operational service data.

For example, the general flow of determining whether or not an access right to a template set for an operational service provided by a financial institution KA is present is as follows.
In step SH1, the access control unit 64 acquires the role to which the person in charge belongs.
In the example of FIG. 28, the role of a person in charge TXT of an investment management company TX, the role of a person in charge TYT of an investment management company TY, or the role of a person in charge KAT of a financial institution KA is acquired.
In step SH2, if the acquired role belongs to a person in charge KAT of a financial institution KA, the access control unit 64 proceeds to step SH2-a; otherwise (if it belongs to a person in charge of an investment management company T), the access control unit 64 proceeds to step SH3.
In step SH2-a, the access control unit 64 gives the financial institution employee KAT access authority to all of the template sets X-1 and X-2, thereby completing the access control process.
On the other hand, if the role is that of a person in charge of investment management business operator T, in step SH3, the access control unit 64 acquires the investment management business operator ID of the investment management business operator T to which the person in charge indicated by the role belongs.
In step SH4, the access control unit 64 acquires the investment management business operator ID associated with each of the management service IDs of the respective management services.
In step SH5, if the investment management provider ID acquired in step SH3 and step SH4 respectively match, the access control unit 64 grants the person in charge access authority to the template set identified by the management service ID associated with the investment management provider ID acquired in step SH4.
If there is a mismatch in step SH5, it is determined that there is no access authority.
Furthermore, in practice, access rights (CRUD), such as whether or not a user has read, update, or delete authority, are precisely controlled according to the role in practice (such as legal officer or operations manager).

The access control to the operational service data has been described above.
Next, access control to end-user data will be described.
FIG. 29 is a diagram showing an overview of the acquisition and management of end-user data.

Data relating to end user M is received and stored by financial institution KA through account opening etc.
The service provider server 1 receives and stores personal information necessary for the conclusion and maintenance of a discretionary investment contract as end user data of the end user M from the individual financial institutions KA in the following manner.
In step SI1, end user M operates end user terminal 4 to apply for a discretionary investment contract for management services on financial institution individual company KA (individual company management service page managed by individual company management server 3).
In the following description, the act of end user M operating end user terminal 4 to perform a predetermined action on financial institution individual company KA (individual company operation service page managed by individual company operation server 3) will be abbreviated as "end user M performs a predetermined action." As described above, "end user M performs a predetermined action" includes the case where a salesperson who conducts face-to-face business with end user M acts on behalf of (entrusts) end user M to perform a predetermined action.
In step SI2, the discretionary asset matching management unit 61 of the service provider server 1 executes control for coordinating discretionary investment contract application instructions to which customer information has been added at individual financial institutions KA.
In step SI3, the user interface control unit 63 of the service provider server 1 causes the end user terminal 4 to display a contract application UI.
In step SI4, the end user M agrees to the application through the contract application UI.
In step SI 5 , the end-user management unit 65 of the service provider server 1 acquires the customer information 81 and contract information 82 of the end user M who has agreed to the application as end-user data, and stores them in the end-user DB 81 .
In step SI6, the discretionary asset matching management unit 61 executes control to link end user data (customer information) with individual financial institutions KA (at regular intervals after the contract is concluded).
In step SI7, the end-user management unit 65 updates the end-user data (customer information) in accordance with the linkage content in step SI6.

Figure 30 shows an overview of access control for end user data.

The authority of each of the personnel of the individual financial institution KA and the investment management companies TX and TY to access end user data (customer information) is determined in the following manner.
That is, in step ST1, the access control unit 64 acquires the role to which the person in charge belongs.
In the example of FIG. 30, the role of a person in charge TXT of an investment management company TX, the role of a person in charge TYT of an investment management company TY, or the role of a person in charge KAT of a financial institution KA is acquired.
In step ST2, if the acquired role belongs to a person in charge KAT of a financial institution KA, the access control unit 64 proceeds to step ST2-a; otherwise (if it belongs to a person in charge of an investment management company T), the access control unit 64 proceeds to step ST3.
In step ST2-a, the access control unit 64 gives the financial institution employee KAT permission to access the end user data, which ends the access control process.
On the other hand, if the role is that of a person in charge of investment management business operator T, in step ST3, the access control unit 64 acquires the investment management business operator ID of the investment management business operator T to which the person in charge indicated by the role belongs.
In step ST4, the access control unit 64 acquires all operation service IDs of one or more operation services to which the end user M has subscribed (including those under contract, excluding those that have been cancelled).
In step ST5, the access control unit 64 acquires all of one or more investment management business operator IDs that are linked to the one or more management service IDs for which subscribed that were acquired in step ST4.
In step ST6, if the investment management company ID acquired in step SH3 is included in the investment management company ID acquired in step SH5, the access control unit 64 grants access authority to the person in charge of the investment management company identified by the investment management company ID acquired in step SH3.
Specifically, for example, when end user M has applied for only management service X-1 and has not applied for or has canceled other management services, the person in charge TXT of investment management company TX is given the authority to access the end user data (customer information) of end user M. In contrast, the person in charge TYT of investment management company TY is not given the authority to access.
By implementing the above access control, data can be protected in a situation in which an individual financial institution KA providing management services and multiple investment management companies T (in this example, investment management companies TX and TY) participate.

Next, a hub function between financial institutions K and investment management business operators T, which becomes possible by application of the service provider server of the second embodiment, will be described.
FIG. 31 is a diagram showing an overview of the hub function of individual financial institutions and investment management companies.

In the conventional method, in most cases, financial institutions KA, KB, and KC directly connected to the investment management company TX, and the connection costs resulting from the multiplicative increase in connections were a hurdle.
In order to overcome this hurdle, a hub function that connects the individual financial institutions KA, KB, KC and the investment management company TX in the service provider server 1 of the second embodiment will be described.
First, a financial institution individual company ID capable of identifying a previously defined financial institution individual company K and an investment management company ID capable of identifying an investment management company T are defined to be globally unique values.
Being globally unique means that within the scope managed by the service provider server 1, there is no other individual financial institution K or investment management business operator T having the same individual financial institution ID and investment management business operator ID.
Next, a proxy unit 52 is prepared to function on the service provider server 1, allowing the investment management company T to access the virtual account management unit 51n associated with each individual financial institution Kn (n is an arbitrary value, and in the example of Figure 31 is any of A, B, or C).
That is, a virtual account management unit 51 is prepared for each individual financial institution K. The virtual account management unit 51 of each individual financial institution K may be provided in a separate device as the service provider server 1. For this reason, it would be costly and difficult for the investment management business operator T to individually establish a connection with the virtual account management unit 51 of each individual financial institution K.
Therefore, the proxy unit 52 is provided to transparently handle the virtual account management unit 51 provided for each individual financial institution K.

For example, the flow of operations in which an investment management company TX finds an accessible virtual account management unit 51 from among a number of individual financial institutions KA, KB, and KC is as follows.
In step STU1, the investment management business operator TX operates the investment management business operator terminal 5 to connect to the proxy unit 52 using its own investment management business operator ID (X).
In step STU2, the proxy unit 52 inquires of each of the virtual account management units 51A, 51B, and 51C associated with each of the pre-registered financial institutions KA, KB, and KC as to whether the investment management company ID (X) is accessible.
In step STU3, each of the virtual account management units 51A, 51B, and 51C associated with each of the individual financial institutions KA, KB, and KC determines whether the investment management company ID (X) inquired about in step STU2 is accessible or not, and returns the result of the determination to the proxy unit 52.
In step STU4, the proxy unit 52 aggregates the judgment results from each of the virtual account management units 51A, 51B, and 51C linked to each individual financial institution KA, KB, and KC, and obtains a virtual account management unit 51 that can be accessed by the investment management company TX.

Incidentally, with regard to steps STU2 and 3, instead of making an inquiry each time as described above, a method may be used in which information on the investment management company ID is shared in advance between proxy unit 52 and each virtual account management unit 51.
Once the accessible virtual account management unit 51 has been identified, the proxy unit 52 relays access from the investment management company TX to the virtual account management unit 51, making it possible to access the data held by the virtual account management unit 51 in accordance with the procedures described above in the access control section.
By adopting such a hub function between individual financial institution K and investment management company T, individual financial institution K and investment management company T can appropriately access data by simply establishing a connection to the virtual account management unit 51 or proxy unit 52 once, thereby achieving cost reduction effects.

To summarize the above, the service provider server 1 of the second embodiment communicates with an end user terminal 4 managed by an end user M who receives N (N is an integer value of 1 or greater) management services using his or her assets, an individual company back office system 2 managed by an individual financial institution K which manages the assets of end user M in a trading account, and M investment management business terminals 5 managed by each of M (M is an integer value of 1 or greater) investment management business T which manage at least a portion of the N management services by entering into a contract with end user M.
The operation service management unit 66, as shown in Figure 23, for example, treats data linked to a specified operation service, including contract status data (e.g., the template set in Figure 23) indicating the status of the contract between the end user M and the investment management company T for the specified operation service, as operation service data, and links the operation service data to an operation service ID that can identify the specified operation service and a fund account corresponding to the specified operation service, and manages the data for each of N operation services.
The user interface control unit 63 provides the end user terminal 4 or the investment management company terminal 5 with a user interface to be used by the end user M or the investment management company T when a contract for a specified management service is concluded, during the contract, or when the contract is terminated.
In this case, the virtual account management unit 51 performs processing using management service data in a fund account associated with a specified management service ID based on operations for a specified management service using the user interface of the end user M or investment management company T.

Furthermore, the service provider server 1 of the second embodiment can execute access control for the operator service data as shown in FIG. 26 in the following manner.
That is, the investment management company management unit 67 manages, for each asset management company of M, the correspondence between the management service ID of one or more management services for which a specified investment management company T has entered into a contract with an end user M among the N management services, and the investment management company ID of the specified investment management company T.
When an operation is performed using the user interface by a specified investment management company Tk among the investment management companies T of M, the access control unit 64 permits access to one or more management service data identified by one or more management service identifiers associated with the asset management company ID of the specified investment management company Tk.
The virtual account management unit 51 executes processing using the operational service data to which access is permitted.

Furthermore, the service provider server 1 of the second embodiment can execute access control for end-user data as shown in FIG. 27 in the following manner.
That is, the end user management unit 65 manages data linked to the end user M as end user data (customer information, which is personal information).
When a specified investment management business operator T performs an operation using the user interface, the access control unit 64 determines whether or not any of the management services of M operated by the specified investment management business operator T has a contract with the end user M, and if it determines that there is, it permits access to the end user data of the end user M, whereas if it determines that there is not, it prohibits access to the end user data.

Furthermore, the service provider server 1 of the second embodiment can realize a hub function for an individual financial institution K and an investment management business T as shown in FIG. 31 in the following manner.
That is, a dedicated virtual account management unit 51 is provided for each of P (P is an integer value of 1 or greater) individual financial institutions K.
When an access request is received from the investment management company terminal 5 of a specified investment management company T, the proxy unit 52 connects the investment management company terminal 5 of the specified investment management company T to the dedicated virtual account management unit 51 of each of one or more individual financial institutions K linked to the specified investment management company T.

The service provider server 1 of the second embodiment thus configured can achieve the following various effects.
That is, by applying the service provider server 1 of the second embodiment, the hurdle of bundling is eliminated, enabling a plurality of investment management businesses T to provide any number of management services.
Hereinafter, this state will be referred to as the "bazaarization of management services," with financial institutions K regarded as the market and investment management companies T as tenants selling products.
That is, by applying the service provider server 1 of the second embodiment, it becomes possible to realize a bazaar of operational services, and as a result, it becomes possible to provide services such as those shown in FIG. 32 and FIG.

FIG. 32 is a diagram showing a specific example of a selective operation service, among the services that can be provided by the bazaarization of operation services by the service provider server 1 of FIG.
As described above in the first embodiment, the service provider server 1 can open any fund account and link each to an investment service. By expanding this, it becomes possible to realize a service that allows the end user M to select an investment category and an investment service. Hereinafter, such a service will be referred to as a "selection-type investment service."

The specific flow of the selective operation service is as follows:
That is, in step SK1, the end user M operates the end user terminal 4 to select the operation category at the time of goal registration on the screen G10, and presses "Proceed to operation service selection."
In step SK2, a screen G11 showing a list of management services and indices belonging to the management category is displayed on the end user terminal 4. In the screen G11, the indices are used as criteria when the end user M makes a selection. Specifically, for example, the indices include the Sharpe ratio, the annualized return, and the rating.
In step SK3, the end user M operates the end user terminal 4 to select the management service for which he/she wishes to apply for a discretionary investment contract from the list on the screen G11, and presses "Apply for management service." As a result, the screen displayed on the end user terminal 4 advances from the screen G11 to the screen G12.
In step SK4, the end user M operates the end user terminal 4 to press "Open" on the discretionary investment contract pre-document on the screen G12. As a result, the latest document registered in advance by Y Investment Advisor, the investment management business operator T of the management service "Smart Fund", is displayed on the end user terminal 4, although this is not shown in the figure.
In step SK5, the end user M checks the pre-contract documents etc., and operates the end user terminal 4 to press "Agree and apply" on the screen G12.
In step SK6, the virtual account management unit 51 of the service provider server 1 generates a transaction indicating that the end user M has applied for the management service "Smart Fund," and updates the customer information database.

FIG. 33 is a diagram showing an example of the flow of a discretionary investment contract application that takes place behind the scenes of the selective management service shown in the example screen of FIG.
In this example, the discretionary assets of the management service applied for by the end user M are managed by an individual financial institution KA, and the processing is carried out by a dedicated virtual account management unit 51A of the management service provider server 1.

In step SL1, the investment management business TX operates the investment management business terminal 5 to submit a template set.
In step SL2, the end user M operates the end user terminal 4 to apply for the operation service.
In step SL3, the virtual account management unit 51A creates data to be delivered, such as pre-contract documents, and registers the contract status as "applied for." During this step SL3, steps SK4 to SK6 in FIG. 32 are being carried out for the end user M.
In step SL4, the investment management business operator TX operates the investment management business operator terminal 5 to confirm the application details.
In step SL5, the investment management business operator TX operates the investment management business operator terminal 5 to accept the application.
In step SL6, the virtual account management unit 51A creates data to be delivered in the document to be delivered at the time of contract conclusion, and updates the contract status to "concluded."
Thereafter, the flow of management is the same as that described above in the first embodiment in which any fund account is opened and linked to each management service.

Figure 34 shows a specific example of a basket-type operation service, one of the services that can be provided by the service provider server 1 in Figure 22 by creating a bazaar of operation services.

When operational services become more bazaar-like, the increase in options may lead to a problem in which the law of decision avoidance becomes more likely to apply to end users M.
For example, in the case of investment trusts, at some financial institutions, it is possible to purchase more than 1,000 different investment services.
Given that many searches reveal sites that provide tips on how to choose investment trusts, it is likely that the law of decision aversion is at work when buying and selling investment trusts.
A service that can solve these problems is the "basket-type investment service."

The specific flow of the basket-type investment service is as follows:
That is, in step SM1, the end user M operates the end user terminal 4 to select the operation category at the time of goal registration on the screen G201, and presses "Proceed to selection of operation service basket."
In step SM2, a screen G202 showing a list of operation services and indexes belonging to the operation category is displayed on the end user terminal 4.
In step SM3, the end user M operates the end user terminal 4 to select the operation service that he/she wishes to include in the operation service basket from the list on the screen G202, and presses "Apply for operation service basket." As a result, the screen displayed on the end user terminal 4 advances from the screen G202 to the screen G203.
In step SM4, although not shown, pre-contract documents and the like relating to all operation services included in the operation service basket are delivered (displayed on the end-user terminal 4).
In step SM5, the end user M checks all pre-contract documents, etc., and operates the end user terminal 4 to press "Agree and apply" on screen G202.

As a result, even if the number of operational services increases due to the bazaarization of operational services, it becomes unnecessary to force the end user M to make a single selection.
In addition, as an expansion of the investment service basket, it is possible to periodically adjust the weighted allocation based on investment service indicators such as the Sharpe ratio and annualized return.
The adjustment may be made based on advice from the financial institution to the end user M, or based on a request from the end user M to the financial institution.
It is expected that these various services (adjustment mechanisms) will create selection pressure to choose better operation services, leading to improvements in operation services.

The second embodiment of the present invention has been described above.

Next, we will explain the definitions of the terms used in the first and second embodiments described above, with reference to Figures 35 to 41 as appropriate.

Figure 35 shows an overview of the operational service.

35, a management service refers to a series of services and a system therefor that provide a forum for an end user M to enter into a specific discretionary investment contract with an investment management business operator T and entrust the management of the assets of the end user M to the investment management business operator T. Also, an investment management business operator ID is used to uniquely identify an investment management business operator T.
That is, as shown in FIG. 35, an investment management business operator T, which is assigned an investment management business operator ID, and an end user M exchange documents prior to the conclusion of a discretionary investment contract, documents to be provided at the time of conclusion of a discretionary investment contract, and the transfer of discretionary investment assets through a forum provided by the management service.

Figure 36 shows an example of a template set for a discretionary investment contract document.

As shown in FIG. 36, this service manages template sets for each version of a discretionary investment contract document.
Here, the "documents prior to the conclusion of a discretionary investment contract" may include, for example, the following documents:
1. Pre-conclusion document for discretionary investment contract 2. Form of consent for provision of personal information to a third party 3. Form of consent for electromagnetic delivery 4. Pre-conclusion document for investment trust contract 5. Discretionary investment contract terms and conditions In addition, the "pre-conclusion documents for discretionary investment contract, etc." may be managed as a collection of documents that are combined in whole or in part, or they may be managed all separately.
Hereinafter, in this embodiment, the "documents prior to the conclusion of a discretionary investment contract, etc." will be described as being managed as a single collection of documents.
Discretionary investment contracts are managed by linking together the documents provided prior to the conclusion of the discretionary investment contract and the documents provided at the time of the conclusion of the discretionary investment contract.
The documents to be provided prior to the conclusion of a discretionary investment contract and the documents to be provided at the time of the conclusion of a discretionary investment contract are each subject to version control, and their history and differences are collectively managed as a "discretionary investment contract document template set."

Figure 37 shows the relationship between operation services and operation service IDs.

As shown in FIG. 37, an operation service and an operation service ID are associated with each other.
That is, the operation service ID uniquely identifies the operation service.
In addition, the management service is constructed based on the discretionary investment contract. Therefore, the management service and the template set of the discretionary investment contract document have one-to-one correspondence.

Figure 38 shows the relationship between end users and accounts.

A financial institution KX is assigned an individual financial institution ID that identifies the financial institution KX.
End user M opens a securities account (general account) with financial institution KX.
End user M is assigned an end user ID that identifies the general account held by end user M within financial institution KX.
In this way, the end user KX's general account at financial institution KX is identified by the financial institution individual ID and the end user ID.

Figure 39 shows the relationship between the general account and the trading account.

As shown in Fig. 39, a trading account that actually manages transactions is managed as belonging to a general account. Here, multiple trading accounts (N in the example of Fig. 39) belong to one general account.
For example, a general account, a specified account, and a NISA account are examples of transaction accounts.

Figure 40 shows an example of managing general accounts and account categories.

Unlike Figure 39, general accounts and specified accounts can also be expressed using a combination of a general account and an account type (specified account or general account) as shown in Figure 40. This is one example of expressing a trading account. Therefore, as long as the above-mentioned service can be realized, general accounts and trading accounts may be managed using any expression method.
In addition, assets under discretionary investment management are managed within a trading account.

Figure 41 shows the relationship between fund accounts and virtual account codes.

As shown in FIG. 41, in order to manage multiple discretionary investments within one trading account, the discretionary investment assets are managed using virtual account codes.
A combination of the trading account ID and the virtual account code is used to identify a virtual account that manages assets for discretionary investment management, that is, a fund account.
Each company can define any number of virtual account codes.

Although one embodiment of the present invention has been described above, the present invention is not limited to the above-mentioned embodiment, and any modifications, improvements, etc. that can achieve the object of the present invention are included in the present invention.

For example, in the above embodiment, the individual company back office system 2 is configured to register dividend and distribution information from the investment target securities, but the investment target can be handled as follows.

Figure 42 shows an example of how investment targets are handled.

As shown in FIG. 42, it is possible to have multiple management services (management services A and B in the example of FIG. 42) and different investment targets.
In the explanation of any number of virtual accounts for a trading account in virtual account management unit 51, we have explained that the dedicated product method is an improvement on the method for separate management. As a result, it is possible to separately manage the assets of the fund account, which is the unit of management, and it is no longer necessary to prepare a dedicated product for each management service.
In other words, even if the number of operation services increases due to the effect of the second embodiment, it is no longer necessary to increase the number of investment targets proportionately. This provides the following effects.

First, it will be possible to handle items that cannot be prepared as dedicated products, such as listed securities.
Specifically, for example, it is possible to make thematic investments by making one company appear in multiple themes.

Secondly, even if it is possible to prepare a dedicated product such as an investment trust, the cost of structuring can be reduced.
Specifically, investments in major indexes such as TOPIX and S&P 500 can be standardized.
That is, as shown in FIG. 42, investment trust b is included as an investment target in both management services A and B, while investment trusts a and c are investment targets only in management services A and B, respectively.

Below, we will explain how to handle shared investment targets using specific examples.
Here, it is assumed that the discretionary investment contract has already been concluded. In addition, it is assumed that the separate management of discretionary assets in the individual company back office system 2 is a subaccount system. It is also assumed that no cash reserves are generated.

Figure 43 shows an example of the flow of new contributions.

A case where new contributions are made simultaneously to the above-mentioned operation services A and B will be described.
First, in step SN1, end user M applies for new contributions of 1 million yen to investment service A in fund account K and 1.5 million yen to investment service B in fund account L.
Next, in step SN2, the service provider server 1 instructs the individual company back office system 2 to transfer 2.5 million yen from non-discretionary assets to discretionary assets. Specifically, for example, in the case of the dedicated product method, an instruction is given to purchase a cash equivalent.
Next, in step SN3, the individual company back office system 2 transfers 2.5 million yen from non-discretionary assets to discretionary assets.
Next, in step SN4, the service provider server 1 calculates the purchase amounts of the investment targets in the fund accounts K and L (hereinafter referred to as "investment instructions").
Specifically, for example, in accordance with management service A, fund account K is calculated to have 400,000 yen in investment trust a, 600,000 yen in investment trust b, and 0 yen in investment trust c.
Also, for example, fund account L is calculated according to management service B with 0 yen for investment trust a, 1 million yen for investment trust B, and 500,000 yen for investment trust c.
Next, in step SN5, the service provider server 1 communicates an operation instruction to the execution person KAT.
Next, in step SN6, the execution person KAT executes the buy order based on the investment instructions and performs contract processing.
Next, in step SN7, the execution person KAT registers the contract details in the individual company back office system 2.
Next, in step SN8, the execution person KAT communicates the details of the contract generated by the purchase instruction to the service provider server 1.
Next, in step SN9, the service provider server 1 executes contract processing for each of the fund accounts K and L, and updates the balances.

The investment instruction linkage in step SN5 can be performed in two ways: one in which the investment instructions of fund accounts K and L are consolidated, and the other in which the investment instructions are not consolidated.
Specifically, for example, the contents shared with the execution officer KAT in each method are as follows:
That is, in the aggregation method, the contents of a 400,000 yen purchase in investment trust a, a 1.6 million yen purchase in investment trust b, and a 500,000 yen purchase in investment trust c are linked.
In addition, in the non-aggregation method, the details of a 400,000 yen purchase in investment trust a and a 600,000 yen purchase in investment trust b are linked, and the details of a 1,000,000 yen purchase in investment trust b and a 500,000 yen purchase in investment trust c are linked.

Figure 44 shows the rebalancing process.

In the above-mentioned management services A and B, the following description will be given on the assumption that the unit price changes and rebalancing is performed accordingly, as shown below.
That is, it is assumed that the unit price of each investment trust has changed as follows:
Suppose the unit price of investment trust A changes from 10,000 yen to 10,000 yen (unchanged), the unit price of investment trust B changes from 10,000 yen to 15,000 yen (+50%), and the unit price of investment trust C changes from 10,000 yen to 12,000 yen (+20%).
In this case, the allocation ratio of each discretionary investment service changes due to fluctuations in the unit price, so rebalancing is carried out as follows to return to the original ratio.
In other words, the ratio of management service A is investment trust a:investment trust b=4:6, and the ratio of management service B is investment trust b:investment trust c=2:1.

Specifically, rebalancing is performed through the following steps.
That is, in step SO1, rebalancing management instructions for fund accounts K and L are generated at the service provider server 1.
Specifically, for example, fund account K follows management service A, with investment trust a purchased for 120,000 yen, investment trust b cancelled for 120,000 yen, and investment trust c purchased for 0 yen (no trading).Fund account L follows management service B, with investment trust a purchased for 0 yen (no trading), investment trust b cancelled for 100,000 yen, and investment trust c purchased for 100,000 yen.
Next, in step SO2, the service provider server 1 communicates an operation instruction to the execution person KAT.
Next, in step SO3, the execution person KAT executes the rebalancing order based on the investment instruction and performs contract processing.
Next, in step SO4, the execution person KAT registers the contract details in the individual company back office system 2.
Next, in step SO5, the execution person KAT communicates the details of the contract generated by the rebalancing to the service provider server 1.
Next, in step SO6, the service provider server 1 executes contract processing for each of the fund accounts K and L, and updates the balances.

In addition, the investment instruction linkage in step SO2 can be performed in two ways: a method of consolidating the investment instructions of fund accounts K and L, and a method of not consolidating the investment instructions.
Specifically, for example, the contents shared with the execution officer KAT in each method are as follows:
In other words, in the consolidation method, the contents of a 120,000 yen purchase in investment trust a, a 220,000 yen redemption in investment trust b, and a 100,000 yen purchase in investment trust c are linked.
In addition, in the non-aggregation method, the 120,000 yen purchase in investment trust a and the 120,000 yen non-cancellation details in investment trust b are linked, and the 100,000 yen cancellation in investment trust b and the 100,000 yen purchase in investment trust c are linked.

Figure 45 shows the relationship between portability and commands.

Here, additional explanations will be given on the terms used in the explanation of FIG.
In other words, portability means that a system can be connected not only to a specific company's system, but also to the same type of system of another company. In other words, portability means that a system can be connected to each of a plurality of financial institutions, individual companies K.
An individual company refers to a Type 1 financial instruments business operator or a registered financial institution that introduces this service.
Additionally, a "side effect" refers to a change, such as creation, update, or deletion, to data held by the Service that occurs in connection with any processing related to discretionary investment management.

This results in the following relationship:
In other words, securities account management is complicated, and generally there are many systems that are tightly integrated with each other. As a result, the lineup is centered on the back office systems that are essential for securities account management, and it is rare to be able to combine it with other companies' services, even if they have the same functions.
It can be said that this service is a system for managing discretionary investment management that has the portability to eliminate tight coupling with individual company back office systems 2 and enable connection to any system.

Specifically, this service incorporates the following three features to ensure high portability:
First, all side effects on data held by this service are caused by commands. Specifically, for example, the path by which a command was generated (i.e. the generator) and the side effects are independent of each other.
Secondly, it is possible to switch the command generation route so that it can be sent to either the individual company back office system 2 or the virtual account management unit 51.
Specifically, for example, various methods can be selected according to the configuration of the individual company back office system 2, such as importing the individual company specifications, calculation according to the specifications of the virtual account management unit 51, and replicating the individual company specifications.
Thirdly, a layer is provided that generates commands from data in the individual company back office system 2 .
Specifically, by providing a layer that absorbs the differences in the specifications of each financial institution's individual KX, it is possible to connect with a variety of back-office systems.

Figure 46 shows the plug-in implementation of discretionary investment contracts and associated functions.

Here, additional explanations will be given on the terms used in the explanation of FIG.
The component is a part of this service that provides discretionary investment contract management functions, from contract conclusion to cancellation and deletion.
An individual company refers to a Type 1 financial instruments business operator or a registered financial institution that introduces this service.
End user M refers to an individual or a corporation who enters into a discretionary investment contract and entrusts the management of assets to a third party.
The life cycle of a discretionary investment contract, or contract life cycle, refers to the series of steps involved in a contract, starting from the agency of an individual company in concluding a discretionary investment contract, through consent to any changes to the contract content, termination, and deletion of data after termination.

This provides the following advantages.
In other words, up until now, systems for concluding discretionary investment contracts and providing associated functions have been closely dependent on the sales screen, whether the service is online or face-to-face, and there have been no systems that can provide functions related to the contract lifecycle on any sales screen.
However, with this service, it is possible to separate functions related to the contract lifecycle from the sales screen and incorporate them into any sales screen.

Specifically, this service introduces the following three features to enable functions related to the contract lifecycle to be separated from the sales screen and incorporated into any sales screen.
First, the site creation function related to the life cycle of discretionary investment contracts has been separated. Specifically, financial institution KX can take responsibility for orders, while components can take responsibility for the contract life cycle.
Secondly, the transition between individual company sites and component sites is a transfer method. Specifically, the components are responsible for hosting, which improves portability through operational independence.
Thirdly, the function of storing data related to the life cycle of discretionary investment contracts has been separated. Specifically, it has become possible for each component to store data and for individual financial institutions to access the data.

FIG. 47 is a diagram showing an example of a connection method for electronic delivery of documents.
That is, as shown in Fig. 47, when an end user M requests the display of a delivery document, the data of the delivery document requested after authentication and authorization is linked, and the requested document is displayed. At this time, a function for supplementing documents related to discretionary investment contracts is provided in the component.

Furthermore, the hardware configuration shown in FIG. 7 is merely an example for achieving the objectives of the present invention and is not particularly limited.

Furthermore, the functional block diagrams shown in Figures 8 and 22 are merely examples and are not particularly limited. In other words, it is sufficient that the information processing system is provided with a function that can execute the above-mentioned series of processes as a whole, and the type of functional block used to realize this function is not particularly limited to the examples in Figures 8 and 22.

Furthermore, the locations of the functional blocks are not limited to those shown in FIG. 8 and FIG. 22, and may be arbitrary.
Furthermore, one functional block may be configured as a single piece of hardware, a single piece of software, or a combination of both.

When the processing of each functional block is executed by software, the program constituting the software is installed into a computer or the like from a network or a recording medium.
The computer may be a computer built into dedicated hardware, or may be a computer capable of executing various functions by installing various programs, such as a server, a general-purpose smartphone, or a personal computer.

Recording media containing such programs are not only configured as removable media that are distributed separately from the device body in order to provide each user with the program, but also as recording media etc. that are provided to each user in a state where they are already installed in the device body.

In this specification, the steps of describing a program to be recorded on a recording medium include not only processes that are performed in chronological order, but also processes that are not necessarily performed in chronological order but are executed in parallel or individually.

In addition, in this specification, the term "system" refers to an overall device that is composed of multiple devices, multiple means, etc.

In summary, an information processing device to which the present invention can be applied is sufficient if it has the following configuration, and can take a variety of different forms.

That is, an information processing device to which the present invention is applied (for example, the service provider server 1 in FIG. 8)
Among devices of a manager who manages a predetermined object, an information processing device that at least communicates with another information processing device that distinguishes and manages a first type management unit and a second type management unit in a management unit in which the predetermined object is managed,
An individual unit management means (e.g., the virtual account management unit 51 in FIG. 8 ) that associates each of the N individual units obtained as a result of dividing the first type management unit in the information processing device with each of the N services (N is an integer value equal to or greater than 1) operated within the framework of the first type management unit, and executes a process of managing the N individual units.
It will be enough to have this.

This will allow any number of fund accounts to be opened and linked to management services. It will also allow any number of fund accounts to be opened and managed.

moreover,
The predetermined object is an asset,
the unit of management is an end user's trading account;
The first type of management unit is a discretionary asset that is an asset under the discretionary investment contract of the end user,
The second type of management unit is a non-discretionary asset that is an asset outside the management of the end user's discretionary investment contract,
the service is an operation service,
The individual units are virtual accounts;
The individual unit management means
Corresponding each of the N virtual accounts obtained as a result of dividing the discretionary assets in the information processing device into the N items to each of the N operation services operated within the framework of the discretionary assets, and managing the N virtual accounts.
It is possible.

moreover,
The individual unit management means
a discretionary asset consistency management means (e.g., a discretionary asset consistency management unit 61 in FIG. 8 ) for managing the discretionary assets in the back-office system and the discretionary assets in the information processing device to maintain a consistency state by executing processing of all transactions related to the discretionary assets of the end user that occur in the back-office system;
An individual unit management means (e.g., the individual management unit 62 in FIG. 8 ) for managing the N virtual accounts by executing transaction processing using the virtual accounts respectively associated with each of the N operation services on the premise of the state of the match;
may have the following structure:

Furthermore, the individual unit management means
an end-user transaction execution unit (e.g., the end-user transaction execution unit 71 in FIG. 8 ) for executing a transaction process based on an operation by the end user as the transaction process for a predetermined operation service among the N operation services;
a back-office generated transaction execution unit (e.g., the back-office generated transaction execution unit 72 in FIG. 8 ) that executes processing of transactions related to the predetermined operation service among the transactions generated in the back-office system as processing of the transactions for the predetermined operation service;
may include.

In addition, an information processing device to which the present invention is applied (for example, the service provider server 1 in FIG. 22)
An end user device (e.g., the end user terminal 4 in FIG. 21 ) managed by an end user who receives N operation services (N is an integer value equal to or greater than 1) using his/her own assets;
An asset manager device (e.g., the individual company back office system 2 in FIG. 21 ) managed by an asset manager who manages the end user's assets in a predetermined management unit;
M investment management device (e.g., the investment management company terminal 5 in FIG. 21 ) managed by M investment managers (M is an integer value of 1 or more) who manage at least a part of the N investment services by making contracts with the end users;
An information processing device that communicates with each other,
For the end user, an individual unit management means (e.g., a virtual account management unit 51 in FIG. 22 ) is provided that executes a process of managing the N individual units by associating each of the N individual units obtained as a result of dividing the management unit in the information processing device with each of the N operation services operated within the framework of the management unit,
The individual unit management means
An operation service management means (e.g., the operation service management unit 66 in FIG. 22 ) that manages data associated with a specific operation service, including contract status data indicating the status of the contract between the end user and the manager for the specific operation service, as operation service data, by linking the operation service data with an operation service identifier capable of identifying the specific operation service, and the individual unit associated with the specific operation service, for each of the N operation services;
A user interface means (e.g., a user interface control unit 63 in FIG. 22) that provides a user interface used by the end user or the operator to the end user device or the operator device when the contract for the specified operation service is concluded, during the contract, or when the contract is terminated;
Including,
The individual unit management means is sufficient to execute processing using the operation service data in the individual unit associated with the specified operation service identifier based on operations performed by the end user or the operator on the specified operation service using the user interface.

This will eliminate the hurdle of bundling, making it possible for multiple investment management companies T to provide any number of management services.

moreover,
The individual unit management means
an investment manager management means (e.g., the investment management business operator management unit 67 in FIG. 22 ) for managing, for each of the M investment managers, the association between the management service identifier of one or more investment services for which a predetermined investment manager has concluded the contract with the end user among the N investment services and an investment manager identifier capable of identifying the predetermined investment manager;
an access control means (e.g., an access control unit 64 in FIG. 22 ) for permitting access to the one or more operation service data identified by the one or more operation service identifiers associated with the operator identifier of the predetermined operator when an operation is performed by the predetermined operator using the user interface;
Further comprising:
the individual unit management means executes a process using the operational service data to which access is permitted;
It is possible.

moreover,
The individual unit management means
An end user management means (e.g., the end user management unit 65 in FIG. 22 ) for managing data associated with the end user as end user data;
Further equipped with
The access control means includes:
When an operation is performed using the user interface by a predetermined operator among operators of M, it is determined whether or not there is an operation service of M operated by the predetermined operator that has concluded the contract with the end user, and when it is determined that there is, access to the end user data is permitted, whereas when it is determined that there is no such contract, access to the end user data is prohibited.
It is possible.

moreover,
a dedicated individual unit management means for each of P operators (P is an integer value of 1 or more);
A connection means (e.g., a proxy unit 52 in FIG. 31 ) for connecting the asset manager device of a predetermined asset manager to the individual unit management means dedicated to each of the one or more asset managers associated with the predetermined asset manager when an access request is received from the asset manager device of the predetermined asset manager.
The sensor may further include:

1: Service provider server, 2: Individual back office system, 3: Individual management server, 4: End user terminal, 5: Investment management company terminal, 11: CPU, 20: Drive, 31: Removable media, 51, 51A, 51B, 51C, 51n: Virtual account management unit, 52: Proxy unit, 61: Discretionary asset matching management unit, 62: Individual management unit, 63: User interface control unit, 64: Access control unit, 65: End user management unit, 66: Management service management unit, 67: Investment management company management unit, 71: End user transaction execution unit, 72: Back office generated transaction execution unit, 73: Self generated transaction execution unit, 81: End user DB, 82: Management service DB, 83: Investment management company DB

Claims (6)

An end user device managed by an end user who receives N operation services (N is an integer value equal to or greater than 1) using his/her own assets;
an asset manager device managed by an asset manager that manages the assets of the end user in a trading account of the end user ;
M operator devices (M is an integer value of 1 or more) that are managed by M operators who operate at least a part of the N operation services by making contracts with the end users;
An information processing device that communicates with each other,
a virtual account management means for managing the N virtual accounts by associating the N virtual accounts obtained as a result of dividing the trading account of the end user in the information processing device with each of the N operation services for the end user ;
The virtual account management means includes:
an operation service management means for managing data associated with a specific operation service, including contract status data indicating the status of the contract between the end user and the manager for the specific operation service, as operation service data, by linking the operation service data with an operation service identifier capable of identifying the specific operation service, and the virtual account associated with the specific operation service, for each of the N operation services;
a user interface means for providing a user interface used by the end user or the operator to the end user device or the operator device when the contract for the predetermined operation service is concluded, during the contract, or when the contract is terminated;
Including,
The virtual account management means executes a process using the operation service data in the virtual account associated with the operation service identifier of the specified operation service based on an operation of the end user or the manager for the specified operation service using the user interface.
Information processing device. The virtual account management means includes:
an operator manager means for managing, for each of the M operators, the association between the operation service identifier of one or more operation services for which a specified operator has concluded a contract with the end user among the N operation services and an operator identifier capable of identifying the specified operator;
an access control means for permitting access to the one or more operation service data identified by the one or more operation service identifiers associated with the operator identifier of the predetermined operator when an operation is performed by the predetermined operator using the user interface;
Further comprising:
the virtual account management means executes a process using the operational service data to which access is permitted;
The information processing device according to claim 1 . The former virtual account management instrument is
an end user management means for managing data associated with the end user as end user data;
Further equipped with
The access control means includes:
When an operation is performed by a predetermined operator among operators of M using the user interface, it is determined whether or not there is an operation service of M operated by the predetermined operator that has concluded the contract with the end user, and when it is determined that there is, access to the end user data is permitted, whereas when it is determined that there is no such contract, access to the end user data is prohibited.
The information processing device according to claim 2 . a virtual account management means for each of the managers P (P is an integer value of 1 or more);
4. The information processing device according to claim 1, further comprising: a connection means for connecting, when an access request is received from the manager device of a specified manager, the virtual account management means dedicated to each of the one or more asset managers linked to the specified manager and the manager device of the specified manager. An end user device managed by an end user who receives N operation services (N is an integer value equal to or greater than 1) using his/her own assets;
an asset manager device managed by an asset manager who manages the assets of the end user in a trading account of the end user ;
M operator devices (M is an integer value of 1 or more) that are managed by M operators who operate at least a part of the N operation services by making contracts with the end users;
An information processing method executed by information processing devices that communicate with each other, comprising:
a virtual account management step of managing the N virtual accounts by associating the N virtual accounts obtained as a result of dividing the trading account of the end user in the information processing device with each of the N operation services for the end user , and
The virtual account management step includes:
an operation service management step of managing data associated with a specific operation service, including contract status data indicating the status of the contract between the end user and the manager for the specific operation service, as operation service data, by linking the operation service data with an operation service identifier capable of identifying the specific operation service, and the virtual account associated with the specific operation service, for each of the N operation services;
a user interface step of providing a user interface used by the end user or the operator to the end user device or the operator device when the contract for the predetermined operation service is concluded, during the contract, or when the contract is terminated;
Including,
The virtual account management step includes a step of executing a process using the operation service data in the virtual account associated with the operation service identifier of the predetermined operation service based on an operation of the end user or the manager for the predetermined operation service using the user interface,
Information processing methods. An end user device managed by an end user who receives N operation services (N is an integer value equal to or greater than 1) using his/her own assets;
an asset manager device managed by an asset manager who manages the assets of the end user in a trading account of the end user ;
M operator devices (M is an integer value of 1 or more) that are managed by M operators who operate at least a part of the N operation services by making contracts with the end users;
Each computer that communicates with
execute a control process including a virtual account management step of associating each of the N virtual accounts obtained as a result of dividing the trading account of the end user in the computer into the N virtual accounts with each of the N operation services for the end user, and executing a process of managing the N virtual accounts ;
As a control process of the virtual account management step,
an operation service management step of managing data associated with a specific operation service, including contract status data indicating the status of the contract between the end user and the manager for the specific operation service, as operation service data, by linking the operation service data with an operation service identifier capable of identifying the specific operation service, and the virtual account associated with the specific operation service, for each of the N operation services;
a user interface step of providing a user interface used by the end user or the operator to the end user device or the operator device when the contract for the predetermined operation service is concluded, during the contract, or when the contract is terminated;
and executing a control process including
As at least a part of the control processing of the virtual account management step, a process using the operation service data is executed in the virtual account associated with the operation service identifier of the predetermined operation service based on an operation of the end user or the manager for the predetermined operation service using the user interface.
program.

Images