JP7784904B2 - Asset management device and asset management method - Google Patents

Description

The present invention relates to an asset management device and an asset management method.

JP 2002-157324 A (Patent Document 1) is a background technology for this invention. This publication states, "When a contracting party who has signed a contract with a credit card company, electricity company, etc. requests to apply and register the contract details from their user terminal 2, the cancellation agent device 1 registers the contract details in association with the party identification information. When the contracting party or a person related to that party requests to apply for cancellation from their user terminal 2, the cancellation agent device 1 obtains the contract details associated with the party identification information and transmits a request to the contracting party terminal 4 to execute the cancellation procedure, which requires the party identification information and contract details" (see abstract).

Japanese Patent Application Laid-Open No. 2002-157324

Patent Document 1 describes how, upon the death of a contracting party, the cancellation procedures for the service to which the contracting party has subscribed will be carried out on behalf of the contracting party. However, Patent Document 1 does not describe how the service contract will be taken over by an heir or other person upon the death of the contracting party.

On the other hand, asset management devices that manage assets owned by customers manage assets that will be inherited by heirs upon the customer's death. Furthermore, inheriting assets carries unique risks, such as the imposition of inheritance tax and the infringement of the legally reserved portion.

Therefore, one aspect of the present invention aims to appropriately manage inheritance risks associated with inheriting assets, thereby preventing unexpected disadvantages from occurring to the heirs.

To solve the above problem, one aspect of the present invention employs the following configuration: An asset management device that manages a customer's assets includes a processor and memory. The memory stores asset information indicating the heirs who will inherit the customer's inheritance assets and the value of each of the inheritance assets. The processor calculates the total value of the inheritance assets indicated by the asset information and outputs an inheritance risk alert based on the calculated total amount.

One aspect of the present invention makes it possible to appropriately manage inheritance risks associated with inheriting assets, thereby preventing unexpected disadvantages for the heirs.

Other issues, configurations, and advantages will become clear from the description of the following embodiments.

FIG. 1 is an explanatory diagram illustrating an example of an outline of a use case of a customer's asset management system during their lifetime in the first embodiment. FIG. 1 is an explanatory diagram illustrating an example of an outline of a use case of the asset management system at the time of the death of a customer in the first embodiment. 1 is a block diagram illustrating a configuration example of an asset management device according to a first embodiment. 1 is a block diagram showing an example of the configuration of a work execution device according to a first embodiment; 10 is an example of a customer table according to the first embodiment. 10 is an example of a legal heir table in the first embodiment. 10 is an example of an asset information table according to the first embodiment. 10 is an example of a work performing company table according to the first embodiment. 10 is an example of a simple property inventory table according to the first embodiment. 10 is an example of an encryption key table according to the first embodiment. 10 is an example of a deletion rank table according to the first embodiment. 10 is an example of a selectable deletion rank table according to the first embodiment. 10 is an example of an inheritance risk table in the first embodiment. 10 is a flowchart illustrating an example of asset information registration processing when a customer is alive according to the first embodiment. 10 is a flowchart illustrating an example of information registration processing according to the first embodiment. 10 is a flowchart illustrating an example of encryption processing according to the first embodiment. 10 is a flowchart illustrating an example of an estimated amount daily update process according to the first embodiment. 10 is a flowchart illustrating an example of a deletion rank/inheritance risk alert update process in Example 1. 10 is a flowchart illustrating an example of an asset information update process executed during a customer's lifetime in the first embodiment. 10 is a flowchart illustrating an example of asset information management processing after the death of a customer according to the first embodiment. 10 is a flowchart illustrating an example of a death information linking process according to the first embodiment. 10 is a flowchart illustrating an example of a simple property inventory generation process according to the first embodiment.

Embodiments of the present invention will now be described in detail with reference to the drawings. In this embodiment, identical components will generally be assigned the same reference numerals, and repeated explanations will be omitted. It should be noted that this embodiment is merely one example for realizing the present invention, and does not limit the technical scope of the present invention.

Figure 1 is an explanatory diagram showing an example of an outline of a use case of an asset management system during a customer's lifetime. The asset management system includes, for example, an asset management device 100 owned by a servicer company and a work execution device 200 owned by each of multiple work execution companies. The asset management device 100 and each of the work execution devices 200 are connected to each other via a network such as the Internet.

Customer referral companies introduce asset management services to customers with assets and refer those customers to servicer companies. In return for receiving customer referrals, servicer companies may pay customer referral fees to customer referral companies. Servicer companies introduce asset management services to their customers.

A customer applies to a servicer company for asset management services. Using, for example, a terminal owned by the customer (such as a personal computer (PC) or smartphone), the customer inputs information about the assets the customer owns, information about the heirs who will inherit the assets the customer owns, and information about the inherited assets that will be passed on to each heir. The customer's terminal then transmits the input asset information to the asset management device 100.

The asset management device 100 encrypts and temporarily stores the received asset information, and transmits a list of the encrypted asset information (hereinafter simply referred to as encrypted asset information) to the work execution device 200 owned by the work execution company. The work execution device 200 stores the encrypted asset information. The asset management device 100 also stores estimated valuation information of inherited assets and heir information (either unencrypted or encrypted using a specified algorithm). Assets to be registered include financial assets such as cash, deposit accounts, securities, and cryptocurrencies, SNS (Social Networking Service) IDs and passwords, as well as real estate and movable property (i.e., it may include both liquid and inliquid assets).

In addition, a customer can use their own terminal to instruct the asset management device 100 to update (e.g., add and/or delete) asset information. Upon receiving an instruction to update asset information, the asset management device 100 transmits a contractor notification indicating information identifying the customer who instructed the update of asset information to the work execution device 200 that stores the encrypted asset information of that customer. Upon receiving the contractor notification, the work execution device 200 transmits the encrypted asset information to the asset management device 100.

The asset management device 100 obtains the asset information by decrypting the encrypted asset information and presents it to the customer's terminal. The customer references the presented asset information and inputs updates to the asset information into the terminal, which then transmits the updates to the asset management device 100. The asset management device 100 encrypts and temporarily stores the asset information reflecting the updates, and transmits the encrypted asset information reflecting the updates to the work execution device 200. The work execution device 200 updates the customer's encrypted asset information to encrypted asset information reflecting the updates.

Furthermore, a customer can use their own terminal to instruct the asset management device 100 to update (e.g., add and/or delete) the estimated inherited asset value information and/or heir information. Upon receiving an instruction to update the estimated inherited asset value information and/or heir information, the asset management device 100 obtains the customer's estimated inherited asset value information and/or heir information and presents it on the customer's terminal. The customer references the presented estimated inherited asset value information and/or heir information and inputs the updated details of the estimated inherited asset value information and/or heir information into the terminal, and the terminal transmits the updated details to the asset management device 100. The asset management device 100 stores the estimated inherited asset value information and/or heir information reflecting the updated details.

The asset information includes, for example, data indicating the details of the asset and a deletion flag indicating how each type of asset should be handled after the customer's death (for example, not deleting the data even after the customer's death is confirmed, deleting the data a specified number of days after the customer's death, or deleting the data immediately after the customer's death is confirmed). The deletion flag is set, for example, based on the customer's specifications, but may be changed automatically when there are changes in laws or guidelines, as described below.

The task execution device 200 on which a customer's encrypted asset information is registered may be designated by the customer, designated by the servicer company, or determined randomly. All of a customer's asset information may be registered on a single task execution device 200, or may be distributed and registered across multiple task execution devices 200.

The asset management device 100 determines whether there is a real risk of problems occurring at the time of inheritance for the customer's assets, and if it determines that there is a real risk of problems occurring at the time of inheritance, it issues an inheritance risk alert to the customer (for example, by sending an inheritance risk alert to a terminal owned by the customer). The inheritance risk alert indicates, for example, that there is a risk of problems occurring at the time of inheritance for the customer's assets, or that the customer can receive paid consultation regarding the inheritance risk from a registered FP (Financial Planner) affiliated with the servicer company.

If necessary, a customer who receives an inheritance risk alert can apply for a paid consultation on inheritance risk countermeasures with a registered FP using, for example, the customer's own terminal, via the asset management device 100. When the asset management device 100 receives an application for a paid consultation, the servicer company shares the customer application information with the registered FP. The customer application information includes, for example, customer information (including, for example, the customer's name and contact information), customer asset information, heir information, estimated valuation information for inherited assets, and the type of inheritance risk alert.

The registered FP, who has received the customer application information, will provide the customer with a fee-based consultation on inheritance risks. The customer may pay the fee for the fee-based consultation to the asset management device 100 or directly to the registered FP. The fee paid for the fee-based consultation may be apportioned between the servicer company and the registered FP, for example, or may be received by either the servicer company or the registered FP. In this way, by allowing the customer to receive an inheritance risk alert before death and provide a fee-based consultation on inheritance risks to a registered FP, the customer can expect to reduce disputes between heirs based on the wishes and actions of the deceased during their lifetime, and the servicer company and/or registered FP can receive a consultation fee.

Note that an insurance company used by a customer is an example of a customer referral company. Also, insurance companies and financial institutions used by customers are examples of servicer companies. Also, judicial scrivener offices and law firms are examples of work-performing companies.

Figure 2 is an explanatory diagram showing an example of an overview of a use case of an asset management system when a customer dies. When a customer dies, the customer's legal heir notifies the customer-referring company of the customer's death. The customer-referring company then notifies the servicer company of the death.

The servicer company registers death information in the asset management device 100. The asset management device 100 sends a death notification and a work instruction based on the death notification to the work execution device 200 that stores the customer's assets. Upon receiving the death notification and the work instruction, the work execution device 200 deletes the asset data as necessary based on the deletion flag for each asset type.

Each work execution device 200 that receives the death notification and work instruction generates a simple asset inventory that lists the assets after deletion processing has been performed as necessary, and transmits it to the asset management device 100. Note that the deletion processing and simple asset inventory generation processing described above may also be performed manually by the user of the work execution device 200. Specifically, for example, the work execution device 200 decrypts the list of assets including the deletion flag for the customer and displays it on a display device, and accepts input from the user of the work execution device 200 via an input device, thereby deleting asset data and generating a simple asset inventory.

When the asset management device 100 receives a simple asset inventory from each of the multiple task execution devices 200, it merges the received simple asset inventory. Furthermore, the asset management device 100 adds inheritance information, such as the heirs of the assets included in the simple asset inventory, estimated appraised value, and/or inheritance risk alerts, to the merged simple asset inventory based on the customer's wishes. The servicer company obtains the simple asset inventory (or the merged simple asset inventory if the simple asset inventories have been merged) from the asset management device 100 and sends it to the legal heirs.

The legal heirs-at-law will identify the assets to be inherited from the simple property inventory they have obtained. They may also identify additional assets to be inherited that are not listed in the simple property inventory. The legal heirs-at-law (especially if, for example, an inheritance risk alert has been issued in the simple property inventory) can apply to the servicer company for inheritance planning consultation.

The servicer company shares the information of legal heirs who have applied for inheritance planning consultation with the registered FP. The information of legal heirs shared with the registered FP includes, for example, information described in a simple property inventory. The registered FP, which has received the information of the legal heirs, provides the legal heirs with advice on inheritance planning. In this way, when a customer dies, the legal heirs can consult a registered FP about inheritance planning based on an inheritance risk alert, etc., which is expected to reduce disputes between heirs, and if the inheritance planning consultation is paid for, the servicer company and/or the registered FP can also receive a consultation fee.

Figure 3 is a block diagram showing an example configuration of the asset management device 100. The asset management device 100 is composed of a computer having, for example, a CPU (Central Processing Unit) 101, memory 102, auxiliary storage device 103, communication device 104, input device 105, and display device 106.

CPU 101 includes a processor and executes programs stored in memory 102. Memory 102 includes ROM (Read Only Memory), a non-volatile storage element, and RAM (Random Access Memory), a volatile storage element. ROM stores unchanging programs (e.g., BIOS (Basic Input/Output System)). RAM is a high-speed, volatile storage element such as DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by CPU 101 and data used when the programs are executed.

The auxiliary storage device 103 is a large-capacity, non-volatile storage device such as a magnetic storage device (HDD (Hard Disk Drive)) or flash memory (SSD (Solid State Drive)), and stores programs executed by the CPU 101 and data used when the programs are executed. In other words, the programs are read from the auxiliary storage device 103, loaded into memory 102, and executed by the CPU 101.

The input device 105 is a device, such as a keyboard or mouse, that receives input from an operator. The display device 106 is a device, such as a display or printer, that outputs the results of program execution in a format that can be viewed by the operator.

The communication device 104 is a network interface device that controls communication with other devices according to a predetermined protocol. The communication device 104 also includes a serial interface such as a USB (Universal Serial Bus).

Some or all of the programs executed by the CPU 101 may be provided to the asset management device 100 via a network from removable media (CD-ROM, flash memory, etc.), which are non-transitory storage media, or from an external computer equipped with a non-transitory storage device, and stored in the non-volatile auxiliary storage device 103, which is also a non-transitory storage medium. For this reason, the asset management device 100 should preferably have an interface for reading data from removable media. The same applies to the work execution device 200.

The asset management device 100 is a computer system configured on a single physical computer or on multiple logically or physically configured computers, and may operate in separate threads on the same computer, or on a virtual computer constructed on multiple physical computer resources. The same applies to the work execution device 200.

The CPU 101 includes, for example, an asset registration unit 111, a key management unit 112, an encryption unit 113, an information linking unit 114, a death notification receiving unit 115, an inheritance tax calculation unit 116, and an inheritance share calculation unit 117. The asset registration unit 111 acquires the customer's asset information and registers it in the asset information table 223. The key management unit 112 manages the encryption key for encrypting the customer's asset data. The encryption unit 113 encrypts the customer's asset data using the encryption key.

The information linking unit 114 exchanges information with the task execution device 200. The death notification receiving unit 115 receives a death notification indicating that a customer has died. The inheritance tax calculation unit 116 calculates the inheritance tax that is expected to be levied at the time of the customer's death. The legal share calculation unit 117 calculates the legal share of each of the customer's legal heirs.

For example, the CPU 101 functions as the asset registration unit 111 by operating in accordance with the asset registration program loaded into the memory 102, and functions as the key management unit 112 by operating in accordance with the key management program loaded into the memory 102. The relationship between programs and functional units is similar for the other functional units included in the CPU 101. The relationship between programs and functional units is also similar for the functional units included in the CPU 201 of the work execution device 200, which will be described later.

In addition, some or all of the functions of the CPU 101 and the functional units included in the CPU 201 of the task execution device 200 may be realized by hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array).

The auxiliary storage device 103 stores, for example, a customer table 121, a legal heir table 122, an asset information table 123, a work performing company table 124, a simple asset inventory table 125, an encryption key table 126, a deletion rank table 127, a selectable deletion rank table 128, and an inheritance risk table 129.

The customer table 121 holds personal information and death information for customers. The legal heir table 122 holds information about legal heirs for customers. The asset information table 123 holds information about assets owned by customers. The work performing company table 124 holds information about work performing companies that are users of the work performing device 200.

The simple asset inventory table 125 holds information showing a simple inventory of a customer's assets that is generated at the time of the customer's death. The encryption key table 126 holds information related to the encryption key used to encrypt the customer's asset data. The deletion rank table 127 holds information defining the deletion rank that indicates how the customer's asset data will be deleted after the customer's death. The selectable deletion rank table 128 holds information indicating the selectable deletion rank for each asset type. The inheritance risk table 129 holds information for determining the inheritance risk for each heir.

In addition, some or all of the information stored in the auxiliary storage device 103 and the auxiliary storage device 203 of the work execution device 200 described below may be stored in the memory 102 and the memory 202 of the work execution device 200 described below, respectively, or may be stored in a database connected to the device.

In this embodiment, the information used by the asset management system is not dependent on the data structure and may be expressed in any data structure. In this embodiment, the information is expressed in table format, but the information can be stored in an appropriately selected data structure from, for example, a list, database, or queue.

Figure 4 is a block diagram showing an example configuration of the work execution device 200. The work execution device 200 is configured, for example, by a computer having a CPU 201, memory 202, auxiliary storage device 203, communication device 204, input device 205, and display device 206.

The hardware description of the CPU 201, memory 202, auxiliary storage device 203, communication device 204, input device 205, and display device 206 is omitted here, as it is the same as the hardware description of the CPU 101, memory 102, auxiliary storage device 103, communication device 104, input device 105, and display device 106.

The CPU 201 includes, for example, a data acquisition unit 211, a decryption unit 212, a data storage unit 213, and an information linkage unit 214. The data acquisition unit 211 acquires data from various tables held in the auxiliary storage device 103. The decryption unit 212 decrypts encrypted customer asset data. The data storage unit 213 stores information in various tables held in the auxiliary storage device 103. The information linkage unit 214 exchanges information with the asset management device 100.

The auxiliary storage device 203 holds, for example, a customer table 221, an asset information table 223, a simple asset inventory table 225, a deletion rank table 227, a selectable deletion rank table 228, and an inheritance risk table 229. The information that can be stored in the customer table 221, asset information table 223, a simple asset inventory table 225, a deletion rank table 227, a selectable deletion rank table 228, and an inheritance risk table 229 is similar to the information that can be stored in the customer table 121, asset information table 123, a simple asset inventory table 125, a deletion rank table 127, a selectable deletion rank table 128, and an inheritance risk table 129, respectively, and therefore will not be described further.

Figure 5 is an example of a customer table 121. The customer table 121 includes, for example, a customer ID column 1211, a name column 1212, an address column 1213, a telephone number column 1214, a login ID column 1215, a password column 1216, a tax-exempt allowance column 1217, a taxable amount column 1218, an inheritance tax alert column 1219, a legally reserved share alert column 12110, a date of death column 12111, and a date of receipt of death column 12112.

The customer ID column 1211 holds an ID that identifies the customer. The name column 1212 holds information indicating the customer's name. The address column 1213 holds information indicating the customer's address. The telephone number column 1214 holds information indicating the customer's telephone number. The login ID column 1215 holds information indicating the login ID used by the customer to log in to the asset management device 100. The password column 1216 holds information indicating the password used to log in to the asset management device 100.

The tax-exempt limit column 1217 holds information indicating the tax-exempt limit for inherited assets (inheritance tax) at the time of a customer's death. The taxable amount column 1218 holds information indicating the taxable amount for inherited assets (inheritance tax) at the time of a customer's death. The inheritance tax alert column 1219 holds an inheritance tax alert, which is an alert (flag) indicating that inheritance tax will be levied upon the death of the customer. If the value of the inheritance tax alert column 1219 is "1", inheritance tax will be levied upon the death of a customer, and if the value of the inheritance tax alert column 1219 is "0", inheritance tax will not be levied upon the death of a customer.

The reserved share alert column 12110 holds the reserved share alert, which is an alert (flag) that indicates whether any of the legal heirs who will become legal heirs when a customer dies will have their reserved share infringed. When a customer with a value of "1" in the reserved share alert column 12110 dies, it is determined that someone will have their reserved share infringed, and when a customer with a value of "1" in the reserved share alert column 12110 dies, it is determined that no one will have their reserved share infringed. Note that both the inheritance tax alert and the reserved share alert are examples of inheritance risk alerts.

The date of death column 12111 holds information indicating the date of death of the customer. The date of death receipt column 12112 receives the date on which the customer's death notification was received. If a customer's death notification has not been received, for example, null values are stored in the date of death column 12111 and the date of death receipt column 12112 corresponding to that customer.

Figure 6 is an example of the legal heir table 122. The legal heir table 122 includes, for example, an heir ID column 1221, a customer ID column 1222, a name column 1223, an address column 1224, a telephone number column 1225, and a relationship column 1226.

The heir ID column 1221 holds an ID that identifies a legal heir. The customer ID column 1222 holds the customer ID of the customer who is the deceased relative to the legal heir indicated by the heir ID column 1221. The name column 1223 holds information indicating the name of the legal heir. The address column 1224 holds information indicating the address of the legal heir. The telephone number column 1225 holds information indicating the telephone number of the legal heir. The relationship column 1226 holds information indicating the relationship of the legal heir indicated by the heir ID column 1221 to the deceased customer.

Figure 7 is an example of the asset information table 123. The asset information table 123 includes, for example, an asset ID column 1231, a customer ID column 1232, an heir ID column 1233, an encryption key ID column 1234, a deletion rank column 1235, a type column 1236, an estimated amount column 1237, a registration date column 1238, an update date column 1239, a corresponding date column 12310, and a data column 12311.

The asset ID column 1231 holds an ID that identifies the asset of the customer indicated in the customer ID column 1232. The customer ID column 1232 holds a customer ID. The heir ID column 1233 holds an heir ID that identifies the heir who will inherit the assets indicated in the type column 1236 and estimated amount column 1237. Note that a "-" is stored in the heir ID column 1233 corresponding to assets that the customer has not designated as inheritance targets.

Note that even if an asset may be subject to inheritance tax under the current tax system, if the customer does not wish for the asset to be inherited by a legal heir, such as when the customer wishes to donate the asset, a "-" is entered in the heir ID field 1233 corresponding to the asset. Additionally, even if no heir is considered for each asset at the time of asset registration, a "-" is permitted to be entered in the heir ID field 1233. Furthermore, for assets such as SNS that are not subject to inheritance tax under the current tax system, an heir may be designated in the heir ID field 1233, for example, to entrust the management of the SNS account to the customer upon their death.

The encryption key ID column 1234 holds an ID that identifies the encryption key that encrypted the data stored in the data column 12311. The deletion rank column 1235 holds the deletion rank of the data stored in the data column 12311. The type column 1236 holds information indicating the type of asset.

The estimated amount column 1237 holds information indicating the value (estimated amount) of the asset. The registration date column 1238 holds information indicating the date the record was registered. The update date column 1239 holds information indicating the date the record was last updated. If the record has not been updated, a null value, for example, is stored in the update date column 1239. The response date column 12310 holds information indicating the date on which action was taken, such as including the record in a simple inventory, after notification of the death of the customer indicated in the customer ID column 1232 was received.

Data column 12311 holds encrypted data indicating assets. If the asset type is cash, information indicating the location of the cash is an example of data; if the asset type is a deposit account, information indicating the deposit account is an example of data; if the asset type is an SNS, the login ID and password for the SNS are examples of data.

Figure 8 is an example of the work performing company table 124. The work performing company table 124 includes, for example, a company ID column 1241, a company name column 1242, and a contact column 1243. The company ID column 1241 holds an ID that identifies the work performing company. The company name column 1242 holds information indicating the name of the work performing company. The contact column 1243 holds information indicating the contact information of the work performing company.

Figure 9 is an example of the simple property inventory table 125. The simple property inventory table 125 includes, for example, an inventory ID column 1251, an asset ID column 1252, an heir ID column 1253, an estimated amount column 1254, an inheritance tax alert column 1255, a legal share alert column 1256, and a company ID column 1257. The inventory ID column 1251 holds an ID that identifies the simple property inventory. The asset ID column 1252 holds the asset IDs of the assets included in the simple property inventory.

The heir ID column 1253 holds the heir ID. The estimated amount column 1254 holds information indicating the value of the assets (estimated amount). The inheritance tax alert column 1255 holds an inheritance tax alert. The reserved share alert column 1256 holds an reserved share alert. The company ID column 1257 holds the company ID of the company performing the work that created the simple property inventory.

Figure 10 is an example of the encryption key table 126. The encryption key table 126 includes, for example, an encryption key ID column 1261 and an encryption key column 1262. The encryption key ID column 1261 holds an encryption key ID. The encryption key column 1262 holds an encryption key.

Figure 11 is an example of the deletion rank table 127. The deletion rank table 127 includes, for example, a deletion rank column 1271 and a posthumous correspondence column 1272. The deletion rank column 1271 holds the deletion rank. The posthumous correspondence column 1272 holds information indicating the posthumous correspondence of the customer for the asset data for which the deletion rank indicated in the deletion rank column 1271 is set.

In the example of Figure 11, asset data with a deletion rank set to "A" cannot be deleted even if notification of a customer's death is received. Asset data with a deletion rank set to "B" is deleted immediately when notification of a customer's death is received. Asset data with a deletion rank set to "C" is deleted N days after the customer's death date (after a specified period has elapsed). Note that deletion ranks may include only "A" and either "B" or "C."

Figure 12 is an example of the selectable deletion rank table 128. The selectable deletion rank table 128 includes, for example, a type column 1281 and a deletion rank column 1282. The type column 1281 holds information indicating the type of asset. The deletion rank column 1282 holds information indicating the deletion ranks that can be selected for asset data of the type indicated in the type column 1281.

In the example of Figure 12, for assets subject to inheritance tax, such as cash, savings accounts, and real estate, only deletion rank "A" can be selected (i.e., they cannot be deleted even if a death notice is received). On the other hand, for assets that are not subject to inheritance tax at the time of asset information registration, such as SNS and NFTs (Non-Fungible Tokens), any of deletion ranks "A," "B," or "C" can be selected.

Figure 13 is an example of the inheritance risk table 129. The inheritance risk table 129 includes, for example, an heir ID column 1291, a customer ID column 1292, a total amount column 1293, a legal share column 1294, an inheritance amount column 1295, and an excess/infringement amount column 1296. The heir ID column 1291 holds the heir ID. The customer ID column 1292 holds the customer ID.

The total amount column 1293 holds information indicating the total amount of assets that the heir will inherit from the customer in the event of the customer's death. The reserved share column 1294 holds information indicating the reserved share that the heir can inherit from the customer in the event of the customer's death. The inherited amount column 1295 holds information indicating the value of the inherited assets based on the reserved share that the heir can inherit from the customer in the event of the customer's death (inherited amount = estimated total amount of the customer's inherited assets x individual reserved share). The excess/infringement amount column 1296 holds information indicating the difference between the total amount of inherited assets that the heir will inherit from the customer in the event of the customer's death minus the reserved amount.

Figure 14 is a flowchart showing an example of the asset information registration process when the customer is alive. Before the asset information registration process of Figure 13 is executed, the values of the work performing company table 124, deletion rank table 127, selectable deletion rank table 128, deletion rank table 227, and selectable deletion rank table 228 are registered in advance.

The customer referral company introduces the asset management service to the customer, who is the deceased (S101). The customer referral company then refers the customer to the servicer company, which then introduces the asset management service to the customer, and the customer applies for the asset management service (S102). Note that the customer may also apply for the asset management service to the servicer company without the customer being introduced by the customer referral company.

The asset registration unit 111 acquires the customer information, legal heir information, estimated inherited asset amount information, and asset information entered by the customer on the customer's terminal, and executes an information registration process to register the information in the customer table 121, legal heir table 122, asset information table 123, and inheritance risk table 129 (S103). Details of step S103 will be described later. The encryption unit 113 executes an encryption process to encrypt the asset data using an encryption key (S104). Details of step S104 will be described later.

The information linking unit 114 transmits the information registered in the asset information table 123 to the work execution device 200, the data storage unit 213 registers the received information in the asset information table 223, and the information linking unit 114 deletes the data registered in the data column 12311 of the asset information table 123 (S105). By processing step S105, the asset data is deleted from the asset information table 123 of the asset management device 100, improving security.

In addition, the information linking unit 114 may also send the information registered in the customer table 121 and the inheritance risk table 129 to the work execution device 200, and the information received by the data storage unit 213 may be registered in the customer table 221 and the inheritance risk table 229.

The information linking unit 114 executes the deletion rank/inheritance risk alert update process (S106) and terminates the asset information registration process. Details of step S106 will be described later.

Figure 15 is a flowchart showing an example of the information registration process in step S103. The asset registration unit 111 acquires customer information, legal heir information, estimated inherited asset amount information, and asset information entered by the customer on the customer's terminal (S1031).

The customer information entered in step S1031 is the value stored in customer table 121, excluding the customer ID, heir ID, date of death, taxable amount, inheritance tax alert, reserved share alert, and date of death receipt. The legal heir information entered in step S1031 is the heir ID stored in customer table 121, the values of the fields in legal heir table 122, excluding the heir ID and customer ID, and the reserved share stored in inheritance risk table 129.

The estimated amount information for inherited assets entered in step S1031 is the heir and estimated amount for each asset type stored in the customer table 121. The asset information entered in step S1031 is the asset type, deletion rank, and data among the values stored in the asset information table 123.

When a customer inputs the type of asset, the asset registration unit 111 refers to the selectable deletion rank table 128 and presents the deletion rank corresponding to that type to the customer's terminal, and the customer selects the deletion rank to input from the presented deletion ranks.

In step S1031, the tax-exempt limit included in the customer information may be entered directly by the customer, or the asset management device 100 may store information in advance to identify the tax-exempt inheritance share based on the customer's family structure and the relationship to the legal heirs, and when the customer enters the family structure and relationship, refer to that information to identify the tax-exempt limit.

In step S1031, the value of the legally reserved share may be directly input by the customer as legal heir information, or the asset management device 100 may store information in advance to identify the legally reserved share from the customer's family structure and the relationship to the legal heir, and when the customer inputs the family structure and relationship, the asset management device 100 may refer to that information to identify the legally reserved share.

In the above example, in step S103, the asset registration unit 111 acquires the customer information, legal heir information, and asset information entered by the customer on the customer's terminal. However, a servicer company representative may also hear from the customer about the customer information, legal heir information, estimated inherited asset amount information, and asset information, and the asset registration unit 111 may accept input of the information heard via the input device 105.

The asset registration unit 111 generates a new customer ID, links the generated customer ID to the acquired customer information, and stores the generated record in the customer table 121 (S1032). Furthermore, in step S1032, the inheritance tax calculation unit 116 stores the difference between the estimated total amount of assets of the type indicated in the selectable deletion rank table 128 among the inherited assets but for which the selectable deletion rank is only A, minus the tax-exempt limit, as the taxable amount in the customer table 121.

The asset registration unit 111 generates a new heir ID for each legal heir indicated in the acquired legal heir information, and stores the records generated by linking each heir ID corresponding to a legal heir with the legal heir information corresponding to that heir ID and the customer ID generated in step S1032 in the legal heir table 122 (S1033).

The asset registration unit 111 generates a new asset ID for each asset indicated in the asset information, obtains the registration date, and stores the generated record in the asset information table 123 by linking each asset ID corresponding to the asset with the customer ID generated in step S1031, the deletion rank corresponding to the asset, the asset type, the registration date, asset data corresponding to the asset type, the taxable amount, and the estimated asset amount (S1034).

The asset registration unit 111, inheritance tax calculation unit 116, and reserved share calculation unit 117 generate and store records in the inheritance risk table 129 for each generated heir ID, and further issue inheritance tax alerts and reserved share alerts as necessary (S1035). Specifically, the reserved share calculation unit 117 stores the generated heir ID, the generated customer ID, the total estimated amount for each heir indicated by the estimated inheritance asset amount information, and the reserved share indicated by the legal heir information in the inheritance risk table 129.

Furthermore, the reserved share calculation unit 117 stores the value obtained by multiplying the total estimated amount indicated by the estimated amount information of the inherited assets by the reserved share of each heir as the inheritance amount in the inheritance risk table 129. The reserved share calculation unit 117 also stores the difference obtained by subtracting the inheritance amount from the total amount stored in the inheritance risk table 129 as the excess/infringement amount in the inheritance risk table 129.

Furthermore, in step S1035, if the inheritance tax calculation unit 116 determines that the taxable amount stored in the customer table 121 is positive, it sets the inheritance tax alert corresponding to the customer ID in the customer table 121 to "1" (i.e., issues an inheritance tax alert), and if it determines that the taxable amount stored in the customer table 121 is 0 or negative, it sets the inheritance tax alert corresponding to the customer ID in the customer table 121 to "0" (i.e., does not issue an inheritance tax alert).

In addition, in step S1035, if the reserved share calculation unit 117 determines that there is an heir whose excess inheritance/infringement amount stored in the inheritance risk table 129 is negative, it sets the reserved share alert corresponding to that customer ID in the customer table 121 to "1" (i.e., issues an reserved share alert), and if it determines that there is no heir whose excess inheritance/infringement amount stored in the inheritance risk table 129 is negative, it sets the reserved share alert corresponding to that customer ID in the customer table 121 to "0" (i.e., does not issue an reserved share alert).

The asset registration unit 111 then determines whether at least one of an inheritance tax alert and a legally reserved share alert has been issued in step S1035 (S1036). If the asset registration unit 111 determines that neither an inheritance tax alert nor a legally reserved share alert has been issued (S1036: No), it terminates the information registration process.

If the asset registration unit 111 determines that at least one of an inheritance tax alert and a legally reserved share alert has been issued (S1036: Yes), it displays a pop-up on the screen of the customer's terminal, for example, recommending that the customer consult with a specialist (e.g., a paid consultation), and sends the customer to a specialist based on the customer's selection (S1037), thereby terminating the information registration process.

In step S1037, the asset registration unit 111 may also display information indicating the type of inheritance risk alert (at least one of an inheritance tax alert and a reserved share alert) that has been issued on the screen of the terminal held by the customer. Furthermore, in step S1037, if an reserved share alert has been issued, the asset registration unit 111 may also display the heir IDs of heirs whose inheritance excess/infringement amount is a negative value on the screen of the terminal held by the customer.

Figure 16 is a flowchart showing an example of the encryption process in step S104. The encryption unit 113 generates an encryption key for encrypting the asset data, and uses the generated encryption key to encrypt the asset data stored in the asset information table 123 in step S1033 (S1041). The encryption unit 113 can generate the encryption key using any encryption key generation algorithm. In this embodiment, the encryption unit 113 generates the encryption key using a common key encryption method.

Furthermore, in step S1041, the encryption unit 113 may perform encryption using a different encryption key for each asset indicated by the asset information acquired in step S1031, or may perform encryption using a different encryption key for each type of asset indicated by the asset information acquired in step S1031, or may perform encryption using the same encryption key for all assets indicated by the asset information acquired in step S1031, or may use the same encryption key for all assets of customers with the same customer ID.

The key management unit 112 generates a new encryption key ID for each encryption key generated in step S1041, stores the encryption key IDs corresponding to the encryption keys corresponding to the data encrypted in step S1041 in the asset information table 123, and stores the combinations of the generated encryption key IDs and the corresponding encryption keys in the encryption key table 126 (S1042), thereby completing the encryption process.

Figure 17 is a flowchart showing an example of the estimated amount daily update process. The inheritance tax calculation unit 116 acquires (monitors) a chart (price trend) of a predetermined type of asset on a daily basis (S1701). Note that in step S1701, the inheritance tax calculation unit 116 may acquire a chart of the predetermined type of asset at a predetermined time interval other than daily (e.g., hourly, weekly, or monthly). Note that the predetermined type of asset may include, for example, assets with high volatility such as virtual currencies and NFTs. The inheritance tax calculation unit 116 also acquires a chart of the predetermined type of asset from, for example, an external system connected to the asset management device 100.

The inheritance tax calculation unit 116 updates the estimated amount of the specified type of asset in the asset information table 123 according to the chart acquired in step S1701, the information linking unit 114 transmits the updated estimated amount and information indicating the record for which the estimated amount has been updated to the work execution device 200, the data storage unit 213 updates the asset information table 223 according to the received estimated amount (S1072), and the estimated amount date and time update process ends.

Figure 18 is a flowchart showing an example of the deletion rank/inheritance risk alert update process in step S106. The information linking unit 114 determines whether there has been a change in the asset rules and/or whether there has been a change in the estimated value of the customer's assets (S1061).

In step S1061, the information linking unit 114 determines that a rule change regarding an asset has occurred, for example, when information regarding a rule change regarding an asset (information indicating the content of the rule change and the type of asset for which the rule change is being made) is input to the input device 105, or when such information indicating a rule change regarding an asset is received from an external system connected to the asset management device 100.

Legal amendments, guideline changes, new legal precedents, changes to deposit regulations, and changes to the terms of use of SNS are all examples of rule changes. The following mainly describes an example of determining whether a rule change has occurred in step S1061, in which the information linking unit 114 determines whether there is a type of asset that was not subject to inheritance tax before the legal amendment (including legal amendments, guideline changes, or new legal precedents) but has become subject to inheritance tax as a result of the legal amendment. Further examples of rule changes include changes to the inheritance tax exemption limit and changes to the types of assets that are subject to inheritance tax.

Furthermore, in step S1061, the information linking unit 114 determines that the estimated asset amount has changed if it determines that there is a record in the asset information table 123 in which the estimated amount has been changed, for example, by the estimated amount daily update process of FIG. 17 or the asset information update process of FIG. 19 described below. Note that in step S1061, the information linking unit 114 may determine that the estimated asset amount has changed only if it determines that there is a record in the asset information table 123 in which the estimated asset amount has been changed by more than a predetermined amount (for example, more than 100,000 yen) by the estimated amount daily update process of FIG. 17 or the asset information update process of FIG. 19 described below (i.e., changes to the estimated amount less than the predetermined amount may be ignored).

If the information linking unit 114 determines that there are no assets of a type that were not subject to inheritance tax before the legal amendment, etc. but have become subject to inheritance tax due to the legal amendment, etc., and determines that there has been no change in the estimated value of the customer's assets (S1061: NO), it repeats the processing of step S1061. Note that when the processing of step S1061 has been repeated for a predetermined time, the deletion rank/inheritance risk alert update processing may be terminated.

If the information linking unit 114 determines that there is an asset of a type that was not subject to inheritance tax before the legal amendment, etc. but has become subject to inheritance tax due to the legal amendment, etc. (S1061: YES), it notifies each work execution device 200 of the asset type (i.e., the rule change details), and the data acquisition unit 211 acquires a record containing the asset type from the asset information table 223 (S1062).

The data storage unit 213 updates the deletion rank of "B" or "C" contained in the acquired record to "A" (S1063). Furthermore, if the data storage unit 213 determines in step S1063 that the deletion ranks corresponding to the type in the selectable deletion rank table 228 include "B" and "C," it deletes "B" and "C."

In addition, if the information linking unit 114 determines in step S1601 that there are no assets of a type that were not subject to inheritance tax before the legal amendment, etc. but have become subject to inheritance tax due to the legal amendment, etc., but determines that there has been a change in the estimated value of the customer's assets, it skips the processing of steps S1062 and S1063 and transitions to the processing of step S1064, which will be described later.

In step S1063, the asset registration unit 111 may also obtain a record containing the relevant type from the asset information table 123, and update the deletion rank of "B" or "C" contained in the obtained record to "A." Furthermore, if the asset registration unit 111 determines in step S1063 that the deletion ranks corresponding to the relevant type in the selectable deletion rank table 228 include "B" and "C," it deletes "B" and "C."

The deletion rank update process in step S1603 allows data on assets that were not subject to inheritance tax when the asset information was registered to be changed so that they are not deleted upon the customer's death, thereby responding to legal changes, etc.

In step S1061, the information linking unit 114 may determine whether there are any assets of a type that were subject to inheritance tax before the legal amendment, etc. but are no longer subject to inheritance tax due to the legal amendment, etc. If the information linking unit 114 determines that there are any assets of a type that were subject to inheritance tax before the legal amendment, etc. but are no longer subject to inheritance tax due to the legal amendment, etc., the information linking unit 114 notifies each work execution device 200 of the type, and the data storage unit 213 may acquire a record in the asset information table 223 that includes the type and update the deletion rank of "A" contained in the acquired record to "B" or "C", or may notify the customer via the asset management device 100 that the deletion rank of "A" contained in the acquired record can be updated to "B" or "C".

In addition, in step S1061, the information linking unit 114 may determine whether a revision to the rules and regulations related to the assets (for example, the terms of use of an SNS) has made it impossible for the asset type to be transferred to anyone other than the individual. If the information linking unit 114 determines that a revision to the rules and regulations related to the assets (for example, the terms of use of an SNS) has made it impossible for the asset type to be transferred to anyone other than the individual, it notifies each task execution device 200 of the type, and the data storage unit 213 acquires a record in the asset information table 223 that includes the type, and updates the deletion rank of "A" included in the acquired record to "B" or "C".

The information linking unit 114 notifies each task execution device 200 of the type of asset that is now subject to inheritance tax (rule change details), and the data acquisition unit 211 calculates the total estimated amount of assets subject to inheritance tax for each customer in the asset information table 223, and the total amount of inherited assets subject to inheritance tax for each heir in the asset information table 223 (S1064).

If the tax-exempt limit has changed due to the rule change detected in step S1061, the data storage unit 213 updates the tax-exempt limit in the customer table 221, and (if updated) updates the taxable amount for each customer in the customer table 221 based on the updated tax-exempt limit and the sum of the estimated amount of assets subject to inheritance tax for each customer calculated in step S1064 (S1065).
Furthermore, in step S1605, if the reserved share has changed due to the rule change detected in step S1061, the data storage unit 213 updates the reserved share in the inheritance risk table 229, and (if updated) updates the total amount, inherited amount, and excess amount/infringement amount in the inheritance risk table 229 based on the updated reserved share and the total amount of inherited assets subject to inheritance tax for each heir calculated in step S1064.

The data storage unit 213 updates the inheritance tax alert and the inheritance share alert in the customer table 221 in the same manner as in step S1035 according to the taxable amount and excess inheritance amount/infringement amount changed in step S1065, issues an alert whose value changes from "0" to "1" (S1066), and terminates the deletion rank/inheritance risk alert update process. Note that the alert issued in step S1066 is the same as that described in step S1035, and is displayed on the screen of the customer's terminal via the asset management device 100.

In addition, in steps S1064, S1065, and S1066, it is desirable that the asset management device 100 also updates the values in the customer table 121, asset information table 123, and inheritance risk table 129, just like the work execution device 200. If the asset management device 100 updates the inheritance tax alert and the legally reserved share alert in the customer table 121 and any alerts change from "0" to "1," the asset management device 100 may issue those alerts instead of the work execution device 200.

The inheritance risk alert update process in step S1066 makes it possible to automatically issue an inheritance risk alert when the estimated asset value changes, thereby reducing the burden of monitoring the customer's inheritance risk on the customer, servicer company, work implementation company, etc.

In addition, in step S1066, when the inheritance tax alert and the reserved share alert are updated, if the value of any alert changes from "1" to "0," a notification indicating that the alert has been canceled may be sent to the client's terminal.

The determination in step S1061 may be performed by the information linking unit 214 of the work execution device 200. In the example described above, the deletion rank/inheritance risk alert update process in step S106 is performed as part of the information registration process in FIG. 14, but it may also be performed periodically independently of the information registration process.

Figure 19 is a flowchart showing an example of asset information update processing executed during a customer's lifetime. The customer logs in to the asset management device 100 (S201). Specifically, for example, the customer sends a login ID and password to the asset management device 100 from their own terminal, and if the asset registration unit 111 determines that the received login ID and password combination is included in the customer table 121, it determines that the login was successful and obtains the customer ID of the record containing that combination.

The asset registration unit 111 acquires all records corresponding to the customer ID from the asset information table 123 (S202). The information linking unit 114 sends the asset ID to the work execution device 200, the data acquisition unit 211 acquires encrypted data corresponding to the customer ID from the asset information table 223, and the information linking unit 214 sends it to the asset management device 100 (S203).

The asset registration unit 111 presents the list of records acquired in step S201 to the customer, for example, by sending it to a terminal owned by the customer or by displaying it on the display device 106 (S204). However, in step S204, the key management unit 112 identifies the encryption key ID included in the record acquired in step S201 and acquires the encryption key corresponding to that encryption key ID, the encryption unit 113 decrypts the data using that encryption key, and the asset registration unit 111 presents the decrypted data in place of the data included in the acquired record.

The customer sends the corrections to be made to the presented record (e.g., deletion rank, asset type, and/or data corrections) to the asset management device 100 from their own terminal (S205). The asset registration unit 111 updates the record in the asset information table 123 by reflecting the received corrections in the record (S206). The asset registration unit 111 may also store the update date in the updated record.

When data is updated during record updating, the key management unit 112 obtains the encryption key ID contained in the updated record and obtains the encryption key associated with the obtained encryption key from the encryption key table 126 (S207), and the encryption unit 113 encrypts the data of the record in the asset information table 123 (if the data has been updated) with the obtained encryption key (S208).

The information linking unit 114 sends the updated record in the asset information table 123 to the work execution device 200, the data storage unit 213 updates the record in the asset information table 223, and the asset registration unit 111 deletes the data for the record in the asset information table 123 (S209), and the asset information update process ends.

In step S205, the customer may send an addition instruction indicating the additional content of the record from their own terminal. In this case, in step S206, the asset registration unit 111 adds a record generated by linking the additional content with the customer ID to the asset information table 123. Furthermore, the processing of step S207 is omitted, and in step S208, the encryption unit 113 generates an encryption key and encrypts the record included in the added data with the generated encryption key. The key management unit 112 generates an encryption key ID corresponding to the encryption key and stores the combination of the encryption key ID and encryption key in the encryption key table 126. Furthermore, in step S209, the information linkage unit 114 transmits the added record in the asset information table 123 to the work execution device 200. The data storage unit 213 adds the record to the asset information table 223. The asset registration unit 111 deletes the data of the added record from the asset information table 123, and the asset information update processing ends.

Figure 20 is a flowchart showing an example of asset information management processing after a customer's death. The legal heirs of a deceased customer notify the customer-referring company of the death by providing information identifying the customer (e.g., customer name, address, telephone number, etc.) and the customer's date of death (S301). The customer-referring company then notifies the servicer company of the death (S302). Note that the legal heirs of a deceased customer may also notify the servicer company directly of the death without notifying the customer-referring company of the death.

The servicer company registers the customer's death information in the asset management device 100 (S303). Specifically, for example, the death notification receiving unit 115 accepts input of the customer's customer ID (for example, by referring to the customer table 121, the customer ID corresponding to the combination of the customer's name, address, and telephone number included in the death notification) and the date of death into the input device 105 by the servicer company, and stores the date of death in the record in the customer table 121 that includes the customer ID.

The information linking unit 114 executes a death information linking process to link death information with the work execution device 200 (S304). Details of the death information linking process in step S304 will be described later. The data storage unit 213 references the deletion rank of the record corresponding to the customer ID in the asset information table 223 and deletes the record according to the deletion rank (S305). Specifically, the data storage unit 213 deletes records corresponding to the customer ID with a deletion rank of "B", and if N days have passed since the date of death of the customer, it also deletes records corresponding to the ID with a deletion rank of "C".

The information linking unit 114 executes a simple asset inventory generation process to generate a simple asset inventory for the customer (S306). Details of the simple asset inventory generation process in step S306 will be described later. The servicer company acquires the simple asset inventory from the asset management device 100 (S307). The servicer company sends the acquired simple asset inventory to the legal heir (S308), thereby completing the asset information management process after the customer's death. Note that instead of the processes of steps S307 and S308, the asset management device 100 may execute a process to send the simple asset inventory to a terminal owned by the legal heir.

Figure 21 is a flowchart showing an example of the death information linking process in step S304. Based on the death notification, the information linking unit 114 obtains from the customer table 121 a record corresponding to the customer indicated in the death notification (S3041). The information linking unit 114 obtains from the legal heir table 122 a record containing the customer ID and from the asset information table 123 a record containing the customer ID (S3042).

The information linking unit 114 identifies the encryption key ID contained in each record of the asset information table 123 acquired in step S3042, and acquires records corresponding to each identified encryption key ID from the encryption key table 126 (S3043). The information linking unit 114 transmits to the work execution device 200 the records acquired from the legal heir table 122 in step S3042, the records acquired from the customer data in step S3041, and the records acquired from the encryption key table 126 in step S3043 (S3044), and terminates the death information linking process.

Figure 22 is a flowchart showing an example of the simple asset inventory generation process of step S306. The decryption unit 212 uses each encryption key received in step S3044 (contained in the record obtained from the encryption key table 126) to decrypt the data corresponding to the customer ID in the asset information table 123 (S3051). The data storage unit 213 stores the data decrypted in step S3051 in the asset information table 223 (S3052).

The information linking unit 214 generates a simple asset inventory based on the record containing the decrypted data in the asset information table 223, generates a new inventory ID, and generates a record linking the generated inventory ID with the simple asset inventory (S3053).

Specifically, for example, the information linking unit 214 generates a record that associates the asset ID corresponding to the decrypted data in the asset information table 223, the heir ID and estimated amount corresponding to the asset ID in the asset information table 223, the values of the inheritance tax alert and legally reserved share alert corresponding to the customer ID in the customer table 221, the company ID of the work performing company using the work performing device 200, and the inventory ID.

The information linking unit 214 may also include decrypted data in the record, but it is desirable not to include data on certain types of assets (for example, a deposit account PIN number) in the record. Furthermore, the information linking unit 214 may add to records with an inheritance share alert value of "1" the heir IDs of heirs of the customer whose inheritance excess/infringement amount is a negative value.

The information linking unit 214 sends the generated record to the asset management device 100, and the information linking unit 114 stores the received record in the simple asset inventory table 125 (S3054), terminating the simple asset inventory generation process. Note that if the asset management device 100 receives records linking an inventory ID and a simple asset inventory from multiple work execution devices 200, the information linking unit 114 stores the multiple records in the simple asset inventory table 125, thereby generating a merged simple asset inventory.

As described above, the asset management system of this embodiment receives asset information from a customer during their lifetime, including asset type, deletion rank, and asset data, and after the customer's death, it handles post-death actions for each type of asset data (delete or undelete) based on the deletion rank for each asset type, then generates a simple asset inventory and hands it over to the legal heirs, allowing inheritance to be carried out in accordance with the customer's wishes during their lifetime.

In particular, for example, a customer can register their social media account and password combination in the asset management system with a deletion rank of "B" or "C," which will prevent the social media account and password combination from being passed on to their legal heirs after their death, thereby protecting their privacy.

In addition, the asset management system of this embodiment can adapt the handling of a customer's asset data after death to the changed rules by changing the deletion rank as necessary when it detects a change in asset rules.

In addition, the asset management system of this embodiment issues inheritance tax alerts, indicating that inheritance tax will be levied when a customer's assets are inherited, and inheritance share alerts, indicating that an heir will have their inheritance share infringed when a customer's assets are inherited, while the customer is still alive. This allows the customer, who is the heir, to deal with inheritance risks themselves, reducing inheritance troubles when the customer dies.

In addition, the asset management system of this embodiment automatically updates inheritance tax alerts and reserved share alerts based on rule changes and changes in the estimated amount of inherited assets (especially assets with high volatility), allowing the client, who is the heir, to deal with inheritance risks themselves, reducing inheritance issues upon the client's death.

In addition, the asset management system of this embodiment includes inheritance tax alerts and reserved share alerts in the simplified asset inventory sent to heirs upon the death of a client, so that heirs are aware that inheritance tax will be owed or that an heir's reserved share has been infringed upon, reducing problems at the time of inheritance.

The present invention is not limited to the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

Furthermore, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole in hardware, for example by designing them as integrated circuits. Furthermore, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing programs that realize each function. Information such as programs, tables, and files that realize each function can be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

Furthermore, the control and information lines shown are those deemed necessary for explanation, and do not necessarily represent all control and information lines on the product. In reality, it is safe to assume that almost all components are interconnected.

100 Asset management device, 101 CPU, 102 Memory, 103 Auxiliary storage device, 104 Communication device, 105 Input device, 111 Asset registration unit, 112 Key management unit, 113 Encryption unit, 114 Information linkage unit, 115 Death notification reception unit, 116 Inheritance tax calculation unit, 117 Legal share calculation unit, 121 Customer table, 122 Legal heir table, 123 Asset information table, 124 Work performing company table, 125 Simple asset inventory table, 126 Encryption key table, 127 Deletion rank table, 128 Selectable deletion rank table, 129 Inheritance risk table, 200 Work performing device, 201 CPU, 202 Memory, 203 Auxiliary storage device, 204 Communication device, 205 Input device, 211 Data acquisition unit, 212 Decryption unit, 213 Data storage unit, 214 Information Linkage Unit, 223 Asset Information Table, 227 Deletion Rank Table, 229 Inheritance Risk Table

Claims (9)

An asset management device for managing customer assets,
a processor and a memory,
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The processor:
Calculating the total amount of the assets subject to inheritance indicated by the asset information;
An inheritance risk alert is output based on the calculated total amount,
The memory stores information indicating a tax-exemption limit when the heir inherits the inheritance target assets of the customer,
The processor:
outputting an inheritance tax alert indicating that inheritance tax will be levied upon the death of the client based on the total amount of the assets subject to inheritance and the tax-exempt limit;
If we receive information indicating a change in rules regarding an asset,
Update the tax-free allowance based on the content of the rule change;
An asset management device that outputs the inheritance tax alert based on the total amount of the assets subject to inheritance and the updated tax-free limit . An asset management device for managing customer assets,
a processor and a memory,
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The processor:
Calculating the total amount of the assets subject to inheritance indicated by the asset information;
An inheritance risk alert is output based on the calculated total amount,
The memory stores information indicating a tax-exemption limit when the heir inherits the inheritance target assets of the customer,
The processor:
outputting an inheritance tax alert indicating that inheritance tax will be levied upon the death of the client based on the total amount of the assets subject to inheritance and the tax-exempt limit;
If information indicating a change in the value of each of the assets subject to inheritance is obtained,
The amount after the change indicated by the information is reflected in the asset information;
An asset management device that outputs the inheritance tax alert based on the total amount of assets subject to inheritance after the change and the tax-exempt limit. An asset management device for managing customer assets,
a processor and a memory,
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The processor:
Calculating the total amount of the assets subject to inheritance indicated by the asset information;
An inheritance risk alert is output based on the calculated total amount,
The memory stores information indicating the legally reserved portion of each of the heirs,
The processor:
calculating the total amount of the assets to be inherited by each of the heirs by referring to the asset information;
Calculate the inheritance amount of each of the heirs based on the total amount of the assets to be inherited and the reserved share;
outputting an inheritance share alert indicating that one of the heirs will have his or her inheritance share infringed upon the death of the client, based on the total amount of the assets to be inherited by each of the heirs and the inheritance reserve amount of each of the heirs;
If we receive information indicating a change in rules regarding an asset,
Update the legally reserved portion based on the content of the rule change;
Recalculating the inheritance amount for each of the heirs based on the total amount of the assets to be inherited and the updated inheritance share;
An asset management device that outputs the reserved share alert based on the total amount of the assets to be inherited by each of the heirs and the recalculated amount of inheritance remaining for each of the heirs. An asset management device for managing customer assets,
a processor and a memory,
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The processor:
Calculating the total amount of the assets subject to inheritance indicated by the asset information;
An inheritance risk alert is output based on the calculated total amount,
The memory stores information indicating the legally reserved portion of each of the heirs,
The processor:
calculating the total amount of the assets to be inherited by each of the heirs by referring to the asset information;
Calculate the inheritance amount of each of the heirs based on the total amount of the assets to be inherited and the reserved share;
outputting an inheritance share alert indicating that one of the heirs will have his or her inheritance share infringed upon the death of the client, based on the total amount of the assets to be inherited by each of the heirs and the inheritance reserve amount of each of the heirs;
If information indicating a change in the value of each of the assets subject to inheritance is obtained,
The amount after the change indicated by the information is reflected in the asset information;
Recalculating the total amount of the assets to be inherited after the change that each of the heirs will inherit;
Recalculating the inheritance amount of each of the heirs based on the total amount of assets subject to inheritance after the change and the reserved share;
An asset management device that outputs the reserved share alert based on the recalculated total amount of the assets to be inherited by each heir and the recalculated remaining inheritance amount for each heir. 5. The asset management device according to claim 1,
The processor:
If we receive information indicating that said customer has died,
An asset management device outputs an asset inventory showing the heirs who are scheduled to inherit the client's inheritance assets, the amounts of each of the inheritance assets, and the inheritance risk alert. An asset management method in which an asset management device manages assets of a customer, comprising:
the asset management device includes a processor and a memory;
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The asset management method includes:
The processor calculates the total amount of the assets to be inherited indicated by the asset information,
The processor outputs an inheritance risk alert based on the calculated total amount,
The memory stores information indicating a tax-exemption limit when the heir inherits the inheritance target assets of the customer,
The asset management method includes:
The processor outputs an inheritance tax alert indicating that an inheritance tax will be levied upon the death of the client based on the total amount of the assets subject to inheritance and the tax-exempt limit;
If the processor obtains information indicating a rule change regarding the asset,
The processor updates the tax-exempt amount based on the content of the rule change;
An asset management method in which the processor outputs the inheritance tax alert based on the total amount of the assets subject to inheritance and the updated tax-free limit. An asset management method in which an asset management device manages assets of a customer, comprising:
the asset management device includes a processor and a memory;
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The asset management method includes:
The processor calculates the total amount of the assets to be inherited indicated by the asset information,
The processor outputs an inheritance risk alert based on the calculated total amount,
The memory stores information indicating a tax-exemption limit when the heir inherits the inheritance target assets of the customer,
The asset management method includes:
The processor outputs an inheritance tax alert indicating that an inheritance tax will be levied upon the death of the client based on the total amount of the assets subject to inheritance and the tax-exempt limit;
When the processor acquires information indicating a change in the amount of each of the assets to be inherited,
The processor reflects the changed amount indicated by the information in the asset information,
An asset management method in which the processor outputs the inheritance tax alert based on the total amount of assets subject to inheritance after the change and the tax-exempt limit. An asset management method in which an asset management device manages assets of a customer, comprising:
the asset management device includes a processor and a memory;
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The asset management method includes:
The processor calculates the total amount of the assets to be inherited indicated by the asset information,
The processor outputs an inheritance risk alert based on the calculated total amount,
The memory stores information indicating the legally reserved portion of each of the heirs,
The asset management method includes:
The processor refers to the asset information and calculates the total amount of the inheritance assets that each of the heirs will inherit;
The processor calculates the inheritance amount of each of the heirs based on the total amount of the assets to be inherited and the legally reserved share;
The processor outputs an inheritance share alert indicating that one of the heirs will have his or her inheritance share infringed upon the death of the client, based on the total amount of the assets to be inherited by each of the heirs and the inheritance reserve amount of each of the heirs;
If the processor obtains information indicating a rule change regarding the asset,
The processor updates the legally reserved portion based on the content of the rule change;
The processor recalculates the inheritance amount of each of the heirs based on the total amount of the assets to be inherited and the updated inheritance amount;
An asset management method in which the processor outputs the inheritance share alert based on the total amount of the assets to be inherited by each of the heirs and the recalculated inheritance amount for each of the heirs. An asset management method in which an asset management device manages assets of a customer, comprising:
the asset management device includes a processor and a memory;
The memory stores asset information indicating the heirs who will inherit the assets of the client and the amounts of the assets;
The asset management method includes:
The processor calculates the total amount of the assets to be inherited indicated by the asset information,
The processor outputs an inheritance risk alert based on the calculated total amount,
The memory stores information indicating the legally reserved portion of each of the heirs,
The asset management method includes:
The processor refers to the asset information and calculates the total amount of the inheritance assets that each of the heirs will inherit;
The processor calculates the inheritance amount of each of the heirs based on the total amount of the assets to be inherited and the legally reserved share;
The processor outputs an inheritance share alert indicating that one of the heirs will have his or her inheritance share infringed upon the death of the client, based on the total amount of the assets to be inherited by each of the heirs and the inheritance reserve amount of each of the heirs;
When the processor acquires information indicating a change in the amount of each of the assets to be inherited,
The processor reflects the changed amount indicated by the information in the asset information,
The processor recalculates the total amount of the assets to be inherited after the change that each of the heirs is scheduled to inherit,
The processor recalculates the inheritance amount of each of the heirs based on the total amount of the assets to be inherited after the change and the legally reserved share,
An asset management method in which the processor outputs the inheritance share alert based on the recalculated total amount of the assets to be inherited by each heir and the recalculated inheritance amount for each heir.