Management device, management method, and management program

Abstract

Efficiently managing multiple requests from financial institutions. [Solution] The management device is characterized by comprising: a reception unit that receives requests from users to a first institution for the purpose of identifying heirs; a determination unit that determines whether or not a family tree that identifies the heirs based on the deceased person related to the received request and that was previously created by a second institution exists in the storage unit; and an output unit that outputs the family tree to the first institution if it is determined that the family tree exists.

Description

Technical Field

[0001] The present invention relates to a management device, a management method, and a management program for managing inheritance procedures.

Background Art

[0002] In recent years, various systems for assisting in identifying legal heirs have been developed. For example, there is a system that uses OCR (Optical Character Recognition) to identify the names of people from the character information printed on a household register transcript when identifying legal heirs.

[0003] As a system for assisting in identifying legal heirs, for example, there is a technology that displays the procedures required for inheritance procedures, assigns a number to each case, manages based on the assigned number, stores at least one progress information such as an instruction to resolve deficiencies corresponding to inheritance information, acceptance of an inheritance application, and completion of inheritance procedures (Patent Document 1). Alternatively, there is a technology that acquires image data of a household register transcript, recognizes the character information contained in the image data, and generates a family tree based on the character information recognized from the character information described in the household register transcript regarding the people described in the household register transcript (Patent Document 2).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] Conventional technologies make it possible to easily identify legal heirs. However, systems that assist in identifying legal heirs are used by the client company and will handle inheritance procedures for a large number of users who are clients of that company, rather than just a few users. In the case of inheritance procedures for a large number of users, the management and processing of procedures become enormous, so efficient management is required.

[0006] Therefore, this disclosure proposes a management device, a management method, and a management program that can efficiently manage multiple requests from clients. [Means for solving the problem]

[0007] To solve the above problems, one form of management device relating to this disclosure is characterized by comprising: a reception unit that receives requests from users to a first institution for the purpose of identifying heirs; a determination unit that determines whether or not a family tree that identifies the heirs based on the deceased person relating to the received request and that was previously created by a second institution exists in the storage unit; and an output unit that outputs the family tree to the first institution if it is determined that the family tree exists. [Effects of the Invention]

[0008] According to one embodiment, multiple requests from the client can be managed efficiently. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the overview of the management system according to the embodiment. [Figure 2] This figure shows an overview of the management process according to the embodiment. [Figure 3] This figure shows an example configuration of a management device according to an embodiment. [Figure 4] This figure shows an example of an application information storage unit according to the embodiment. [Figure 5] Figure (1) shows an example of an administrative information storage unit according to the embodiment. [Figure 6] It is a diagram (2) showing an example of the secretariat information storage unit according to the embodiment. [Figure 7] It is a diagram showing an example of a document received by the reception unit according to the embodiment. [Figure 8] It is a diagram showing an example of a resubmitted document received by the reception unit according to the embodiment. [Figure 9] It is a diagram showing an example of a family tree created by the creation unit according to the embodiment. [Figure 10] It is a diagram showing an example of a defect created by the creation unit according to the embodiment. [Figure 11] It is a diagram (1) showing an example of a user interface displayed by the display control unit according to the embodiment. [Figure 12] It is a diagram (2) showing an example of a user interface displayed by the display control unit according to the embodiment. [Figure 13] It is a diagram showing an example of a management screen of request information displayed by the display control unit according to the embodiment. [Figure 14] It is a diagram showing an example of a detailed screen of request information displayed by the display control unit according to the embodiment. [Figure 15] It is a sequence diagram explaining the processing flow of the management system according to the embodiment. [Figure 16] It is a flowchart (1) showing the procedure of the status classification process according to the embodiment. [Figure 17] It is a flowchart (2) showing the procedure of the status classification process according to the embodiment. [Figure 18] It is a flowchart (3) showing the procedure of the status classification process according to the embodiment. [Figure 19] It is a flowchart (4) showing the procedure of the status classification process according to the embodiment. [Figure 20] It is a flowchart (5) showing the procedure of the status classification process according to the embodiment. [Figure 21] It is a diagram explaining a modification example of the management system according to the embodiment. [Figure 22]It is a diagram showing an overview of the family tree management process according to an embodiment. [Figure 23] It is a diagram showing a configuration example of a management device according to an embodiment. [Figure 24] It is a diagram showing an example of a family tree information storage unit according to an embodiment. [Figure 25] It is a flowchart showing the procedure of a process for determining whether to send a family tree according to an embodiment. [Figure 26] It is a hardware configuration diagram showing an example of a computer that realizes the functions of a management device.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described in detail based on the drawings. In the following embodiments, the same parts are denoted by the same reference numerals, and redundant descriptions are omitted.

[0011] (1. Embodiment) (1-1. Overview of the Management System According to the Embodiment) The management process according to the present disclosure is implemented by the management system 1 shown in FIG. 1. Using FIG. 1, the configuration of the management system 1 according to the embodiment and the overview of the management process by the management system 1 will be described. FIG. 1 is a diagram showing an overview of the management system 1 according to the embodiment.

[0012] As shown in FIG. 1, the management system 1 includes a management device 100, an administrator terminal 100a, a financial institution terminal 10, and a user terminal 20.

[0013] The management device 100 is an information processing device that manages requests from financial institutions for the identification of heirs, etc. For example, the management device 100 may be a server device, a PC (Personal Computer), a cloud server, etc. As shown in Figure 1, the management device 100 has, for convenience, a general affairs 담당 (general affairs 담당), an initial review 담당 (initial review 담당), and a re-review 담당 (re-review 담당) as functions for management processing, and manages requests received from financial institutions. For example, the management device 100 receives a request to identify legal heirs, identifies the legal heirs, and transmits the results of the identification to the financial institution. The management device 100 also stores each piece of information and the results of the processing in a database. The management device 100 may have a function to perform OCR processing to convert requested documents into image data, or it may be a device that works in cooperation with dedicated OCR equipment.

[0014] The administrator terminal 100a is a terminal used by administrators and administrative staff who use the management device 100. The administrative staff is the organization that processes requests received from financial institutions using the management device 100.

[0015] Financial institution terminal 10 is a terminal device used by a financial institution. Financial institution terminal 10 is provided, for example, at each branch of a financial institution. Specifically, as shown in Figure 1, financial institution terminal 10a is provided at branch A of a financial institution. Financial institution terminal 10b is provided at branch B of a financial institution. In the following, when it is not necessary to distinguish between financial institution terminal 10a and financial institution terminal 10b, they will simply be referred to as "financial institution terminal 10".

[0016] One example of a financial institution is a bank. A bank branch is a facility that conducts banking operations in a location separate from the bank's head office. The operations performed by a bank include, for example, the withdrawal of account deposits to legal heirs when the account holder dies. For example, in the case of branch A shown in Figure 1, when the account holder, who is the user, dies, the branch will identify the legal heirs and withdraw the account deposits to the identified legal heirs. In this case, branch A communicates with the management device 100 via the communication network N using the financial institution terminal 10. Specifically, branch A requests the management device 100 to create a family tree in order to identify the legal heirs.

[0017] The user terminal 20 is a terminal device used by a user. A user is a customer of a financial institution who has an account with that financial institution, or a person who has some relationship with the person who has an account. For example, when the account holder of an account with a financial institution passes away, the user requests the financial institution to handle the inheritance procedures. Specifically, the user uses the user terminal 20 to send the documents necessary for the inheritance procedures to the financial institution terminal 10. Alternatively, the user may bring or mail the documents necessary for the inheritance procedures to the financial institution.

[0018] The administrator terminal 100a, financial institution terminal 10, and user terminal 20 mentioned above are, for example, information processing devices such as desktop PCs, tablet PCs, notebook PCs, mobile phones, smartphones, and PDAs (Personal Digital Assistants). Note that the number of management devices 100, administrator terminals 100a, financial institution terminals 10, and user terminals 20 is not limited to those shown in Figure 1.

[0019] (1-2. Overview of Management Processes) Next, we will explain the overview of the management process by the management system 1 using Figure 2. Figure 2 is a diagram showing the overview of the management process according to the embodiment.

[0020] First, the financial institution terminal 10 receives application documents from the user terminal 20 requesting identification of heirs (step S1). The application documents are documents that identify the legal heirs, including the user, such as the user's family register. The financial institution terminal 10 converts the application documents received from the user into image data and transmits (uploads) the image data to the management device 100.

[0021] When the management device 100 receives image data of application documents from the financial institution terminal 10, it registers a request to identify legal heirs based on the information contained in the received image data (step S2).

[0022] Furthermore, the management device 100 will update the status information of registered requests as needed, indicating the progress of each request. In other words, the management device 100 classifies the status of each request and makes the classified information available to financial institutions at any time, thereby enabling them to manage a large volume of requests.

[0023] As will be explained in more detail later, for example, the management device 100 classifies requests into statuses such as "Initial Registration Completed," "Resubmission Registration Completed," "Awaiting Initial Review," "Awaiting Re-review," "Awaiting Call for Deficiency," and "Successfully Completed." For example, in step S2, if the management device 100 has made progress such as "Application documents received," it registers the status as "Initial Registration Completed."

[0024] Next, the management device 100 checks whether there are any deficiencies in the received application documents. Deficiencies refer to things like missing information that would hinder the process of identifying legal heirs. If there are deficiencies in the application documents, the management device 100 registers a progress statement indicating "there are deficiencies." In this case, the management device 100 creates a deficiency report indicating the deficiencies and sends the deficiency report data to the financial institution terminal 10 (step S3). If the deficiency report data has been sent, the management device 100 registers a progress statement indicating "deficiency report data has been output."

[0025] The financial institution terminal 10 transmits the received deficiency data to the user terminal 20 (step S4). The management device 100 may also make a phone call to the user terminal 20 to inform them of the deficiency if there is a deficiency in the document (step S5). For example, the management device 100 can choose to transmit the deficiency data to the user terminal 20, or to send an email or make a phone call to inform them of the deficiency. Subsequently, for example, if the management device 100 has made a phone call to the user terminal 20, it registers the status as "deficiency call made".

[0026] The user terminal 20 sends the resubmitted documents to the financial institution terminal 10 based on the received deficiency data (step S6). The financial institution terminal 10 sends the received resubmitted documents to the management device 100 (step S7). When the management device 100 receives the resubmitted documents, it registers the progress as "Resubmitted documents received". Subsequently, the management device 100 checks whether there are any deficiencies in the resubmitted documents.

[0027] The management device 100 checks for any deficiencies in the resent documents received from the financial institution terminal 10, and if there are no deficiencies, it uses AI-OCR (Artificial Intelligence Optical Character Recognition) to analyze the family register transcript. The management device 100 uses the analysis results to identify multiple legal heirs and create a family tree. The management device 100 outputs the family tree, which is the result of identifying the heirs, to the financial institution terminal 10 (step S8). Subsequently, if the management device 100 has progressed to the point of "creating a family tree and sending it to the financial institution terminal 10", it registers the status as "successfully completed".

[0028] The management device 100 registers the progress status for each request. The management device 100 can display the number of registered progress statuses to the financial institution terminal 10 (step S9). The financial institution terminal 10 can check the progress status of requests using the user interface provided by the management device 100. In addition, the financial institution terminal 10 can check the information of each user who made a request at any time.

[0029] In this way, the management device 100 can easily manage requests by receiving requests from the financial institution terminal 10 to identify heirs and classifying the progress status of each request. Furthermore, because the management device 100 classifies requests by progress status, it is easy to refer to the progress status.

[0030] (1-3. Configuration of the control device according to the embodiment) Next, the configuration of the management device 100 that performs the management processing according to the embodiment will be described. Figure 3 is a diagram showing an example of the configuration of the management device 100 according to the embodiment.

[0031] As shown in Figure 3, the management device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The communication unit 110 is implemented, for example, by a NIC (Network Interface Card) or a network interface controller. The communication unit 110 is connected to a network (e.g., the Internet) by wire or wireless connection and transmits and receives information with financial institution terminals 10 and user terminals 20, etc., via the Internet. For example, the communication unit 110 may transmit and receive information using any communication standard or technology such as Wi-Fi (registered trademark), Bluetooth (registered trademark), SIM (Subscriber Identity Module), or LPWA (Low Power Wide Area).

[0032] The memory unit 120 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as hard disks and optical discs.

[0033] The memory unit 120 includes an application information memory unit 121 and an administrative office information memory unit 122. The information stored in the memory unit 120 will be explained below using Figures 4 to 6. In the examples shown in Figures 4 to 6, the information stored in the memory unit 120 may be conceptually represented as "A01," but in reality, each piece of information described later will be stored in the memory unit 120.

[0034] The application information storage unit 121 stores information common to both the administrative office that receives the requests for management and the financial institution making the requests, among the information used in the management processing according to the embodiment.

[0035] Figure 4 shows an example of the application information storage unit 121 according to the embodiment. As shown in Figure 4, the application information storage unit 121 stores the following items: "common management number", "financial institution management number", "application date", "application deadline", "status", and "period of retention in the same status".

[0036] The "Common Management Number" is a number assigned to a request and is common to both the management device 100 and the financial institution terminal 10. The "Common Management Number" is identification information used to identify a request. The "Common Management Number" is a unique identification number issued by the management device 100. The "Financial Institution Management Number" is a number assigned to each financial institution to distinguish them. The "Application Date" is the date the request was submitted. The "Application Deadline" is the deadline for the request. The "Status" is a classification indicating how far along the processing of the request is. The "Period of Retention in the Same Status" is the number of days that have elapsed since the status was updated.

[0037] As illustrated in Figure 4, the management device 100 indicates that it has assigned the financial institution management number "B01" to the request with common management number "A01". The application date for this request is "January 1, 2024", and the application deadline is "March 31, 2024". The management device 100 has classified this request as "Initially Registered", indicating that the request has been received. This status has lasted for "1 day".

[0038] Similarly, when the management device 100 has completed up to step S3 in Figure 2 for the request with common management number "A02", it updates the status to "Retransmission Registered" and registers it. When the management device 100 has completed up to step S8 in Figure 2 for the request with common management number "A03", it updates the status to "Successfully Completed" and registers it. When the management device 100 has completed up to step S2 in Figure 2 for the request with common management number "A04", it updates the status to "Waiting for Initial Review" and registers it.

[0039] Next, the Secretariat Information Storage Unit 122 will be explained using Figures 5 and 6. The Secretariat Information Storage Unit 122 stores how many requests there are in each status category. Figure 5 is Figure (1) showing an example of the Secretariat Information Storage Unit 122 according to the embodiment. As shown in Figure 5, the Secretariat Information Storage Unit 122a stores the following items: "Financial Institution", "Initial Registration Completed", "Resending Completed", "Awaiting First Review", "Awaiting Second Review", and "Normally Completed". "Financial Institution" is the name of the financial institution that made the request. "Initial Registration Completed" is the number of requests that were registered in the management device 100 when the request was received from the financial institution terminal 10 or user terminal 20. "Resending Completed" is the number of cases in which the management device 100 received a deficiency report and missing or corrected documents from the financial institution terminal 10 or user terminal 20. "Awaiting First Review" is the number of cases in which a deficiency report or family tree creation is awaited. "Awaiting re-examination" indicates the number of cases awaiting confirmation of whether the initial examination report or family tree is correct. "Successfully completed" indicates the number of cases in which the management device 100 has created a family tree to identify the heirs and has finished outputting the created family tree to the financial institution terminal 10.

[0040] In the example shown in Figure 5, the management device 100 indicates that the status of requests received from financial institution "Branch A" is as follows: "250 requests are initially registered," "21 requests are resent," "75 requests are awaiting initial review," "15 requests are awaiting re-review," and "5 requests are successfully completed." In another example, the management device 100 indicates that the status of requests received from financial institution "Branch B" is as follows: "170 requests are initially registered," "11 requests are resent," "9 requests are awaiting initial review," "7 requests are awaiting re-review," and "3 requests are successfully completed." In another example, the management device 100 indicates that the status of requests received from financial institution "Branch C" is as follows: "670 requests are initially registered," "170 requests are resent," "55 requests are awaiting initial review," "25 requests are awaiting re-review," and "20 requests are successfully completed."

[0041] As shown in Figure 5, the secretariat information storage unit 122b stores the following items: "Waiting for re-examination of deficiencies," "Request for creation of deficiency report," "Waiting for call regarding deficiencies," and "Call regarding deficiencies completed." "Waiting for re-examination of deficiencies" is the number of requests for the creation of deficiency reports, in which case there are no errors in the documents output from the financial institution terminal 10 or user terminal 20. "Waiting for call regarding deficiencies" is the number of cases in which there are deficiencies in the documents output from the financial institution terminal 10 or user terminal 20, before the management device 100 makes a call to the user terminal 20. "Call regarding deficiencies completed" is the number of cases in which there are deficiencies in the documents output from the financial institution terminal 10 or user terminal 20, after the management device 100 has made a call to the financial institution terminal 10 or user terminal 20.

[0042] As illustrated in the example in Figure 5, the management device 100 shows that the status of requests received from financial institution "Branch A" is as follows: 27 requests are "awaiting re-examination for deficiencies," 100 requests are "requests for creation of deficiency reports," 21 requests are "awaiting phone calls for deficiencies," and 22 requests have "phone calls for deficiencies made." In another example, the management device 100 shows that the status of requests received from financial institution "Branch B" is as follows: 16 requests are "awaiting phone calls for deficiencies," 60 requests are "requests for creation of deficiency reports," 35 requests are "awaiting phone calls for deficiencies," and 7 requests are "awaiting phone calls for deficiencies." In another example, the management device 100 indicates that the status of requests received from the financial institution "Branch C" is as follows: "240" requests are "awaiting a call regarding deficiencies," "210" requests are "requests for creation of deficiency reports," "120" requests are "awaiting a call regarding deficiencies," and "100" requests are "awaiting a call regarding deficiencies."

[0043] Figure 6 is Figure (2) showing an example of the secretariat information storage unit 122 according to the embodiment. As shown in Figure 6, the secretariat information storage unit 122c stores the following items: "Financial Institution", "Normal Uploaded", "Deficiency Uploaded", "90 Days Elapsed", "Withdrawal Request Received", and "Withdrawn". "Normal Uploaded" is the number of family trees that the management device 100 has output to the financial institution terminal 10. "Deficiency Uploaded" is the number of deficiency notices that the management device 100 has output to the financial institution terminal 10 or user terminal 20. "90 Days Elapsed" is the number of requests that have been received from the financial institution terminal 10 for 90 days. "Withdrawal Request Received" is the number of requests for which the financial institution terminal 10 or user terminal 20 has contacted the management device 100 to withdraw the request. "Withdrawn" is the number of requests that have been withdrawn.

[0044] In the example shown in Figure 6, the management device 100 indicates that the status of requests received from financial institution "Branch A" is as follows: 70 requests are "Uploaded successfully," 95 requests are "Uploaded with deficiencies," 3 requests are "90 days elapsed," 17 requests have been requested to be withdrawn, and 15 requests have been withdrawn. In another example, the management device 100 indicates that the status of requests received from financial institution "Branch B" is as follows: 87 requests are "Uploaded successfully," 42 requests have been "Uploaded with deficiencies," 10 requests are "90 days elapsed," 8 requests have been requested to be withdrawn, and 8 requests have been withdrawn. In another example, the management device 100 indicates that the status of requests received from financial institution "Branch C" is as follows: "291 requests uploaded successfully," "300 requests uploaded with deficiencies," "70 requests that have been inactive for 90 days," "77 requests with withdrawal requests," and "76 requests that have been withdrawn."

[0045] Returning to Figure 3, let's continue the explanation of the control unit 130. The control unit 130 is implemented by, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit), GPU (Graphics Processing Unit), etc., which executes a program stored inside the management device 100 using RAM or the like as a working area. The control unit 130 is also a controller and is implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

[0046] As shown in Figure 3, the control unit 130 includes a reception unit 131, a classification unit 132, a creation unit 133, a display control unit 134, and an output unit 135.

[0047] The reception unit 131 receives multiple requests aimed at identifying heirs. For example, the reception unit 131 receives a request to identify heirs from a financial institution terminal 10. Subsequently, the reception unit 131 stores information about the received requests in the storage unit 120.

[0048] Here, the documents accepted by the reception unit 131 will be explained using Figures 7 and 8. Figure 7 is a diagram showing an example of documents accepted by the reception unit 131 according to this embodiment. As shown in Figure 7, the reception unit 131 accepts a family register transcript 300 from the financial institution terminal 10. The family register transcript 300 includes family registers from the Taisho 4th year, Showa 23rd year, and Heisei 6th year. The reception unit 131 may accept the family register transcript 300 as image data or as a paper document. Furthermore, if the user is using a service in a country that provides family register transcripts 300 as electronic data, the reception unit 131 may accept the family register transcript as electronic data.

[0049] The management device 100 requires all documents, including the family register transcript 300, to be complete in order to identify the legal heirs. However, since users are often unfamiliar with inheritance procedures, all documents may not be available when the status is "Initial Registration Completed." Furthermore, financial institutions may not be able to receive all documents by the deadline due to various circumstances of the user. Therefore, the reception unit 131 accepts not only the documents received when the status is "Initial Registration Completed," but also documents resent by financial institutions (hereinafter referred to as "resent documents"). An example of resent documents is shown in Figure 8.

[0050] Figure 8 shows an example of a resubmitted document received by the reception unit 131 according to this embodiment. The resubmitted document 400 includes a deficiency notice 401 and missing documents 402, including a family register transcript. The deficiency notice 401 is a document output from the management device 100 when there are deficiencies in the documents of the received request. The missing documents 402 are documents that were missing or had corrections when the request was received from the financial institution terminal 10 with the status of "initial registration completed". For example, the missing document 402 is a family register transcript.

[0051] When the management device 100 classifies a document into the "awaiting initial review" status, if there are missing documents or documents that need correction, it sends a deficiency notice 401 to the financial institution terminal 10. The financial institution terminal 10, upon receiving the deficiency notice 401, sends it to the user terminal 20. The user terminal 20, upon receiving the deficiency notice 401, sends the resent documents 400, including the missing documents 402, to the financial institution terminal 10. The financial institution terminal 10, upon receiving the resent documents 400, sends them to the management device 100. As a result, the reception unit 131 receives the resent documents 400 sent from the financial institution terminal 10.

[0052] The classification unit 132 classifies the processes for identifying heirs, which are carried out based on multiple received requests, according to the status indicating the progress of the process. The classification unit 132 automatically classifies the status when image data is uploaded. For example, when the classification unit 132 uploads the request application data to the management device 100, it automatically classifies the status as "Initially Registered". The classification unit 132 also classifies the status based on the time elapsed since the request was registered. For example, if 24 hours have passed since the request was in the "Initially Registered" status, the classification unit 132 classifies it as "Awaiting First Review".

[0053] The classification unit 132 automatically classifies the status after a predetermined number of days have elapsed. For example, if 90 days have passed since the date the request was received, the classification unit 132 automatically classifies it as "90 days elapsed".

[0054] The classification unit 132 classifies the status when it has notified the requester of the request or made a judgment regarding the documents attached to the request. Here, notification refers to, for example, sending a notice of deficiencies to the financial institution terminal 10 or user terminal 20, or making a phone call. Judgment regarding documents refers to, for example, the examination of documents by the "initial review officer" or "secondary review officer" to determine whether there are any errors or deficiencies.

[0055] Specifically, when the reception unit 131 receives a request, the classification unit 132 updates the status classification to "Initially Registered". Next, the classification unit 132 performs a format check on the "Initially Registered" request, and if there are no deficiencies in the documents, it classifies the status to "Awaiting First Review". On the other hand, if there are deficiencies in the documents, the classification unit 132 classifies the status to "Request for Creation of Deficiency Letter".

[0056] The classification unit 132 checks the contents of the documents for requests marked "awaiting initial review," and if there are no deficiencies in the documents, it classifies the status to "awaiting re-review." On the other hand, if there are deficiencies in the documents, the classification unit 132 classifies the status to "request for creation of deficiency notice." Alternatively, if there are deficiencies in the documents, the classification unit 132 classifies the status to "awaiting deficiency call."

[0057] The classification unit 132 checks for errors in the family tree for requests marked "awaiting re-examination," and if there are no errors, it classifies the status as "successfully completed." On the other hand, if there are errors in the deficiency report, the classification unit 132 corrects the errors and classifies the status again as "awaiting re-examination." Then, if there are no errors in the deficiency report, the classification unit 132 classifies the status as "deficiency awaiting re-examination."

[0058] The classification unit 132 outputs a deficiency report to the financial institution terminal 10 for requests marked "awaiting re-examination due to deficiencies," and if the missing documents are output from the financial institution terminal 10, it classifies the status as "registered for resubmission."

[0059] The classification unit 132, upon receiving a withdrawal notification from the financial institution terminal 10 for a request that was initially registered, classifies the status as "withdrawal request made." Next, for requests that were previously classified as "withdrawal request made," the classification unit 132 classifies the status as "90 days elapsed" if 90 days have passed since the request was received. The management device 100 then deletes the data for requests that have been in use for 90 days or more.

[0060] This allows the management device 100 to classify multiple requests by status, and to determine how many requests are in each status.

[0061] The creation unit 133 creates a family tree corresponding to a request for which the processing of documents has been completed from the financial institution terminal 10, including an indication of the identified heir. For example, the creation unit 133 creates a family tree for requests for which there are no deficiencies in the documents attached to the request received from the reception unit 131, or for which deficiencies have been resolved. Completion of document processing means, for example, when all documents are complete for a request that is in the status of "awaiting initial review" or "awaiting re-review". For example, the creation unit 133 creates a family tree for a request that has been classified as "awaiting initial review" by the classification unit 132. The creation unit 133 creates a family tree from the family register transcript, identifying those who are direct descendants, direct ascendants, and collateral relatives of the deceased as heirs. The creation unit 133 creates a family tree with marks added to distinguish the deceased and the heirs. In this way, the creation unit 133 can create a family tree that visualizes the relationship between the deceased and the heirs.

[0062] The creation unit 133 creates a family tree showing the relationships between individuals, for example, based on information from a family register. Here, we will explain the procedure by which the creation unit 133 creates a family tree from information from a family register.

[0063] First, the creation unit 133 determines the marital and parent-child relationships of all individuals appearing on the family tree based on information from the family register. Based on the determined marital and parent-child relationships, the creation unit 133 connects the individuals with lines. Below, an example is given in which marital relationships are connected horizontally and parent-child relationships are connected vertically.

[0064] For example, the creation unit 133 places the person who is the husband and the person who is the wife side by side based on the determined marital relationship, and connects the couple with a double line. If the marriage has been dissolved, the creation unit 133 places an "X" mark on the double line between the couple. If there are multiple marriages, the creation unit 133 places the spouses side by side with the person in question at the center.

[0065] Furthermore, the creation unit 133 draws a line downwards from the center of the double line between the parents (the married couple) based on the determined parent-child relationship, and places the child there. If there are multiple children, the creation unit 133 arranges them in age order, with the oldest on the left and the youngest on the right. In the case of a child adopted by a joint parent-child adoption, the arrangement in the creation unit 133 is the same as for a child not adopted, but the line is a double line. In the case of a child adopted by only the father or mother, the creation unit 133 places the child directly below the father or mother and connects the parent and child with a double line.

[0066] Next, we will explain in more detail how heirs are identified. Those who can become heirs are limited to the deceased's spouse and blood relatives, and the spouse is always an heir. For this reason, the creation unit 133 checks whether the deceased has a spouse based on the information in the family register. If a spouse exists, the creation unit 133 sets the spouse as an heir.

[0067] Furthermore, the creation unit 133 checks whether there are any heirs other than the spouse. Individuals who can be heirs other than the spouse are assigned a priority order (inheritance order). First priority is lineal descendants. Lineal descendants are blood relatives belonging to a later generation than the deceased, such as children, grandchildren, and great-grandchildren. Second priority is lineal ascendants. Lineal ascendants are blood relatives belonging to an earlier generation than the deceased, such as parents and grandparents. Third priority is siblings, and if there are no siblings, then nephews or nieces are assigned. Therefore, the creation unit 133 checks the relationship information to see if there are individuals corresponding to the first through third priority levels, and sets the first person to be identified as the heir.

[0068] Furthermore, if the member information includes information indicating that a person listed in the family register has been disinherited (grounds for disinheritance), the creation unit 133 will create a family tree that excludes the disinherited person from being an heir. For example, suppose there are three children in the first order of inheritance, but one of them has grounds for disinheritance. In this case, the creation unit 133 will exclude the child with grounds for disinheritance from being an heir and set the remaining two children as heirs.

[0069] Here, we will explain the documents created by the creation unit 133 using Figures 9 and 10. Figure 9 is a diagram showing an example of a family tree created by the creation unit 133 according to this embodiment. The creation unit 133 creates a family tree 500 based on the requested family register transcript. The family tree 500 has a deceased person mark 501, which is a mark indicating the deceased, and an heir mark 502, which is a mark indicating the heir. The deceased is a person who has died leaving behind property and assets. An heir is a person who inherits the property and assets of the deceased. In Figure 9, Mr. A is marked with the deceased person mark 501, and his spouse Ms. B, and his children Mr. C, Ms. D, Ms. E, and Mr. F are marked with the heir mark 502, which is an heir mark.

[0070] The creation unit 133 may also create a family tree that includes marks indicating the order of inheritance, in addition to the deceased person mark 501 and the heir mark 502. In Figure 9, the creation unit 133 assigns a first-place mark to the spouse B, who is first in line to inheritance, and assigns second-place marks to the children C, D, E, and F, who are second in line to inheritance, and creates the family tree. The information of the created family tree 500 is then stored in the secretariat information storage unit 122.

[0071] Figure 10 shows an example of a deficiency notice created by the creation unit 133 according to this embodiment. When the creation unit 133 receives a request from the financial institution terminal 10 and there are deficiencies in the documents, it creates a deficiency notice to inform the financial institution terminal 10 of the deficiencies. For example, the creation unit 133 creates a deficiency notice 600 that lists the names of the missing documents. The management device 100 transmits the created deficiency notice 600 to the financial institution terminal 10. The financial institution terminal 10 transmits the deficiency notice 600 transmitted from the management device 100 to the user terminal 20.

[0072] The deficiency notice 600 has a read code 601 that links it to which request it corresponds to. The read code 601 is code information that can be read by the management device 100, and is, for example, a barcode (one-dimensional barcode information or two-dimensional barcode information, etc.). The read code 601 may also be a QR code (registered trademark). The read code 601 functions as key information for linking the deficiency notice with the documents resent by the financial institution in response to the deficiency notice and the requester. This allows the management device 100 to gather the documents used for identifying heirs and creating family trees. Subsequently, the information of the created deficiency notice 600 is stored in the secretariat information storage unit 122.

[0073] The display control unit 134 displays the classified status. For example, the display control unit 134 displays the status classified by the classification unit 132 using a user interface. Here, the user interface displayed by the display control unit 134 will be described using Figures 11 and 12. Figure 11 is Figure (1) showing an example of the user interface displayed by the display control unit 134 according to the embodiment. The user interface 700 shown in Figure 11 is a user interface displayed on the secretariat operating the management device 100, and is displayed on the screen of the administrator terminal 100a, for example. The user interface 700 is a screen that displays the status and number of requests. The status and number of such requests are classified and displayed as General Affairs Staff 701, Initial Review Staff 702, Second Review Staff 703, and Completed 704.

[0074] General affairs staff 701 is categorized into the following items: "Initial registration completed," "Resent registration completed," "Successfully completed," "Defective document call completed," "Withdrawal request made," and "90 days elapsed." Initial review staff 702 has "Waiting for initial review," "Defective document creation request," and "Waiting for defect call." Second review staff 703 has "Waiting for second review," "Second review," and "Waiting for second review due to defects." "Second review" refers to the number of requests for a document that has already been reviewed and is scheduled to be reviewed again. Completed 704 has "Normal portion uploaded," "Defective document uploaded," and "Withdrawn."

[0075] As shown in Figure 11, the display control unit 134 displays the number of currently registered requests for each status classified by the classification unit 132. The display control unit 134 updates and displays the number of currently registered requests after a certain period of time has elapsed. The display control unit 134 also updates and displays the number of currently registered requests after a predetermined number of days has elapsed. The period of time elapsed is, for example, 24 hours. The predetermined number of days is, for example, 90 days.

[0076] In Figure 11, the display control unit 134 displays the total number of entries for branches A, B, and C stored in the secretariat information storage unit 122. The display control unit 134 also assigns and displays status classifications for each person in charge.

[0077] Figure 12 is a diagram (2) showing an example of a user interface displayed by the display control unit 134 according to the embodiment. The user interface 700a shown in Figure 12 is a user interface displayed on the screen of the financial institution terminal 10, for example, on the screen of branch A of the financial institution. The user interface 700a includes the financial institution 705, the secretariat 706, and completed 707.

[0078] Financial institution 705 has "Correlation diagram uploaded" and "Deficiency report uploaded". "Correlation diagram uploaded" is the number of requests for which the management device 100 has sent a correlation diagram (family tree) to the financial institution terminal 10. Secretariat 706 has "Under review". "Under review" is the number of requests being reviewed by the management device 100. Completed 707 has "Correlation diagram downloaded", "Deficiency report downloaded", "90 elapsed", and "Withdrawn". "Correlation diagram downloaded" is the number of requests for which the financial institution terminal 10 has downloaded a correlation diagram (family tree) received from the management device 100. "Deficiency report downloaded" is the number of requests for which the financial institution terminal 10 has downloaded a deficiency report received from the management device 100. In Figure 12, the display control unit 134 displays the number of financial institution branch A entries stored in the secretariat information storage unit 122.

[0079] Comparing Figure 11 and Figure 12, we see that the financial institution terminal 10, which made multiple requests, and the management device 100, which performs the process of identifying the heirs, display different status classifications in their user interfaces. The display control unit 134 displays different user interfaces because the management device 100 and the financial institution terminal 10 want to display different status classifications. For example, the secretariat operating the management device 100 is looking for detailed information such as what status the requests have progressed to. In contrast, the financial institution operating the financial institution terminal 10 is looking for general information such as how many requests there are. For example, the status displayed as "Under Review" on the financial institution terminal 10 is displayed on the management device 100 with detailed status classifications such as "Initial Registration Completed," "Resending Registration Completed," "Waiting for First Review," "Waiting for Second Review," "Waiting for Second Review," "Successfully Completed," "Waiting for Deficiency Re-review," "Request for Deficiency Letter Creation," "Waiting for Deficiency Call," and "Defective Call Completed." In this way, the display control unit 134 changes the display of the user interface on the financial institution terminal 10 and the management device 100.

[0080] The display control unit 134 can display different numbers of status classification items on the management device 100 and the financial institution terminal 10. For example, in Figure 11, the management device 100 has 15 items. In Figure 12, the financial institution terminal 10 has 7 items.

[0081] Furthermore, the display control unit 134 can also display the user interface in accordance with the change when it receives a change in the screen display from the financial institution terminal 10. The display control unit 134 accepts and displays a change on the financial institution terminal 10 to not display classifications of statuses that have been searched fewer times than other statuses. The display control unit 134 also accepts and displays a change on the financial institution terminal 10 to not display classifications of statuses that have fewer occurrences than other statuses. In this way, the financial institution terminal 10 can concentrate on the required processing by, for example, not displaying statuses that have been searched fewer times than other statuses, thereby improving the efficiency of operations.

[0082] The display control unit 134 displays different user interfaces for each different financial institution. For example, the display control unit 134 displays 10 status items at branch A and 5 status items at branch B. By displaying different user interfaces for each financial institution, the management device 100 can display a user interface suitable for each financial institution.

[0083] When the management device 100 is processing a request, the display control unit 134 displays the status on the user interface of the financial institution terminal 10 without changing the classification.

[0084] Next, the details of the request information will be explained using Figures 13 and 14. Figure 13 is a diagram showing an example of a request information management screen displayed by the display control unit 134 according to the embodiment. As shown in Figure 13, when any status is selected on the user interface where the status is displayed, the display control unit 134 displays the information of the request corresponding to the selected status. When any status is selected, the display control unit 134 displays detailed information of the selected status. For example, when the status "Waiting for initial review" is selected, the display control unit 134 displays a list of requests that are "Waiting for initial review". Also, when the common management number of any request is clicked from the list of requests, the display control unit 134 displays detailed application information.

[0085] In Figure 13, the display control unit 134 displays the selection screen 800 on the terminal screen of the secretariat operating the management device 100. The selection screen 800 includes a common management number 801, a financial institution management number 802, a status 803, an application date 804, an application deadline 805, and a search button 806. The search button 806 is pressed when at least one of the common management number 801 to the application deadline 805 on the selection screen 800 has been selected or entered.

[0086] Here, the display control unit 134 considers the display when status 803 is selected and the search button 806 is pressed. When status 803 is selected, for example, when a request with the status "Initially Registered" is selected and the search button 806 is pressed, the display control unit 134 displays the search results screen 800a.

[0087] The search results screen 800a is a screen that displays requests that match the status selected by the selection screen 800, and has search results 807. In Figure 13, the display control unit 134 shows that the search results 807 indicates that for a request with common management number "A01", the financial institution management number "B01" has been assigned. The management device 100 indicates that for such a request, the financial institution management number "B01" has been assigned for a request with common management number "A01". The application date for such a request is "January 1, 2024", and the application deadline is "March 31, 2024". The management device 100 then classifies such a request into the status "Initially Registered", which indicates that the request has been accepted. This status indicates that it has continued for "1 day".

[0088] Figure 14 is a diagram showing an example of a detailed request information screen displayed by the display control unit 134 according to the embodiment. As shown in Figure 14, the display control unit 134 displays the detailed screen 900. The detailed screen 900 includes a resend document upload button 901, a file download button 902, a withdrawal button 903, a data deletion button 904, request information details 905, and an update history 906.

[0089] The Resend Document Upload button 901, when pressed, transitions the user from the currently viewed screen to a screen for uploading resend documents. The File Download button 902, when pressed, transitions the user to a screen for downloading files. The Withdrawal button 903, when pressed, transitions the user to a screen for withdrawing the currently viewed request. The Data Delete button 904, when pressed, displays a screen for deleting the currently viewed request. The Request Information Details screen 905 displays detailed information about the request. The Update History screen 906 displays which person updated the processing of the request. Note that the display control unit 134 is not limited to the buttons shown on the details screen, and can change whether or not to display buttons depending on the user's authority.

[0090] The display control unit 134 displays the details screen for each request by pressing the common management number 801 on the selection screen 800 in Figure 13 and displaying the details screen 900 in Figure 14. For example, the display control unit 134 displays the same content as the search results screen 800a in the request information details 905. The display control unit 134 displays the name and authority of each person in charge, the update date and time, and the update content in the update history 906. As a result, the management device 100 can assign a common management number to requests and sort requests by status classification and updates, making it easy to see how far the processing has progressed.

[0091] The output unit 135 outputs the family tree created by the creation unit 133 to the financial institution terminal 10. The output unit 135 also outputs a notification to the financial institution terminal 10 or the user terminal 20, which has a reading code attached that links the deficiency report and the request created by the creation unit 133.

[0092] (1-4. Procedure for management processing according to the embodiment) The procedure for the management process according to the above embodiment will be specifically explained with reference to Figures 15 to 20. Figure 15 is a sequence diagram illustrating the processing flow of the management system 1 according to the embodiment.

[0093] As shown in Figure 15, first, the financial institution terminal 10 transmits application data to the management device 100 (step S11). The management device 100 receives the transmitted application data (step S12). If there are any deficiencies in the application data, the management device 100 creates a deficiency notice to inform the recipient of these deficiencies (step S13).

[0094] The management device 100 sends the created deficiency report to the financial institution terminal 10 (step S14). The financial institution terminal 10, having received the deficiency report sent from the management device 100, sends the deficiency report to the user terminal 20 (step S15).

[0095] Upon receiving the deficiency notice from the financial institution terminal 10, the user terminal 20 sends the missing or corrected documents back to the financial institution terminal 10 as resent documents (step S16). Upon receiving the resent documents from the user terminal 20, the financial institution terminal 10 sends the resent documents to the management device 100 (step S17).

[0096] Upon receiving the resent documents from the financial institution terminal 10, the management device 100 creates a family tree if the documents are complete (step S18). The management device 100 then sends the created family tree to the financial institution terminal 10 (step S19) and terminates the process.

[0097] Next, the detailed procedure for the action shown in Figure 15 will be explained using Figures 16 and later. Figure 16 is a flowchart (1) showing the procedure for status classification processing according to the embodiment. As shown in Figure 16, first, the management device 100 determines whether or not it has received a request from the financial institution terminal 10 (step S101). If the request has not been received (step S101; No), the management device 100 waits until it receives a request. On the other hand, if the request has been received (step S101; Yes), the management device 100 registers the request (step S102).

[0098] The management device 100 performs a format check on the registered request (step S103). The management device 100 determines whether or not there are any deficiencies in the document (step S104). If there are deficiencies in the document (step S104; Yes), the management device 100 notifies the financial institution terminal 10 of the deficiencies in the document by written document or telephone (step S106). The management device 100 determines whether or not a reply has been received from the financial institution (step S107). If no reply has been received from the financial institution (step S107; No), the management device 100 waits until a reply is received. On the other hand, if a reply has been received from the financial institution (step S107; Yes), the management device 100 terminates the process.

[0099] On the other hand, if there are no deficiencies in the documents (step S104; No), the management device 100 updates the status to "awaiting initial review" (step S105) and terminates the process.

[0100] Figure 17 is a flowchart (2) showing the procedure for classifying the status according to the embodiment. First, the management device 100 determines whether or not there is a request for "awaiting initial review" (step S201). If there is no request for "awaiting initial review" (step S201; No), the management device 100 waits until a request for "awaiting initial review" comes in. On the other hand, if there is a request for "awaiting initial review" (step S201; Yes), the management device 100 determines whether or not there are any deficiencies in the request document (step S202).

[0101] If there are deficiencies in the requested documents (Step S202; Yes), the management device 100 requests the creation of a deficiency report (Step S204). Upon receiving the request for the creation of a deficiency report, the management device 100 creates the deficiency report (Step S205) and proceeds to Step S301. On the other hand, if there are no deficiencies in the requested documents (Step S202; No), the management device 100 creates a family tree (Step S203) and proceeds to Step S401.

[0102] Figure 18 is a flowchart (3) showing the procedure for classifying the status according to the embodiment. The management device 100 determines whether or not it has received the created deficiency report (step S301). If it has not received the created deficiency report (step S301; No), the management device 100 waits until it receives it. On the other hand, if it has received the created deficiency report (step S301; Yes), the management device 100 determines whether or not there is an error in the deficiency report (step S302).

[0103] If the management device 100 finds an error in the deficiency report (step S302; Yes), it corrects the deficiency report (step S303). After the correction, the management device 100 returns to step S302 to check if there are any errors in the deficiency report. On the other hand, if the management device 100 finds no errors in the deficiency report (step S302; No), it updates the status to "Waiting for further review of deficiency" (step S304).

[0104] Subsequently, the management device 100 transmits a deficiency report to the financial institution terminal 10 (step S305). The management device 100 determines whether or not there are documents to be resent from the financial institution terminal 10 (step S306). If there are no documents to be resent (step S306; No), it waits until it receives the documents to be resent. On the other hand, if there are documents to be resent (step S306; Yes), the management device 100 receives the documents to be resent, checks them again (step S307), and returns them to (1). This is because the resent documents that have been checked may still be found to be deficient.

[0105] Figure 19 is a flowchart (4) showing the procedure for classifying the status according to the embodiment. The management device 100 determines whether or not it has received the created family tree (step S401). If it has not received the created family tree (step S401; No), the management device 100 waits until it receives it. On the other hand, if it has received the created family tree (step S401; Yes), it determines whether or not there are any errors in the family tree (step S402).

[0106] If there is an error in the family tree (step S402; Yes), the management device 100 corrects the family tree (step S403). After the correction, the management device 100 returns to step S402 to determine if there are any errors in the family tree. On the other hand, if there are no errors in the family tree (step S402; No), the management device 100 sends the family tree to the financial institution terminal 10 (step S404). Then, the management device 100 updates the status classification to "successfully completed" (step S405).

[0107] Figure 20 is a flowchart (5) showing the procedure for classifying the status according to the embodiment. The process shown in Figure 20 is to be executed continuously after the management device 100 receives a request and while the request is pending. The management device 100 determines whether or not it has received a request from the financial institution terminal 10 (step S501). If the management device 100 has not received a request from the financial institution terminal 10 (step S501; No), it waits until it receives one. If the management device 100 has received a request from the financial institution terminal 10 (step S501; Yes), it determines whether or not it has received notification from the financial institution terminal 10 to withdraw the request (step S502).

[0108] If the financial institution terminal 10 has not received notification to withdraw the request (Step S502; No), the management device 100 determines whether 90 days have passed since the request was received (Step S503). If 90 days have not passed since the request was received (Step S503; No), the management device 100 returns to Step S502. On the other hand, if 90 days have passed since the request was received (Step S503; Yes), the management device 100 updates the status classification to "90 days elapsed" (Step S504) and terminates the process.

[0109] On the other hand, if a request to be withdrawn is received from the financial institution terminal 10 (step S502; Yes), the status classification is updated to "Withdrawal Request Received" (step S505), and the process is terminated.

[0110] (2. Modified examples of the embodiment) (2-1. Management of multiple financial institutions) The above embodiment shows an example in which the management device 100 manages multiple requests. Here, the management device 100 may manage multiple financial institutions or multiple branches. The management of multiple financial institutions will be explained using Figure 21. Figure 21 is a diagram illustrating a modified example of the management system 1 according to the embodiment. Explanations that overlap with those described above will be omitted.

[0111] Management system 1 includes financial institution terminals 10, specifically financial institution terminal 10c of branch A of bank A, financial institution terminal 10d of branch A of bank Z, financial institution terminal 10e of branch B of bank Z, a management device 100, and a communication network N.

[0112] The management device 100 can easily manage multiple financial institutions or branches by assigning a financial institution management number to each of the multiple financial institution terminals 10, classifying the status of requests, and displaying them on the screen.

[0113] Furthermore, in Embodiments 1 and 2, it was explained that the management device 100 receives and manages requests from financial institutions. However, the management device 100 can also receive requests from a wide range of clients, including corporations, legal and accounting firms, and individuals, not just financial institutions.

[0114] (2-2. Output of family tree to other financial institutions) In embodiments 1 and 2 described above, an example was shown in which the management device 100 receives a request from a client (user) and creates a family tree concerning the user. However, it is generally assumed that the deceased person has accounts at multiple financial institutions. Therefore, it is expected that the user will also request the creation of a family tree from those multiple financial institutions. In this regard, if a family tree is created at one financial institution, sharing that family tree with multiple financial institutions can save time and effort for both the user and the financial institutions. Such processing will be described below. Note that the processing in this modified example will be performed by management device 100A, which is another example of the management device disclosed in this disclosure.

[0115] When the management device 100A creates a family tree based on a request from a client (user), it stores the created family tree in the storage unit 120A. Then, when the same client requests the creation of a family tree from another bank, the management device 100A determines whether a family tree exists in the storage unit 120A, and if a family tree exists, it can send the stored family tree. Now, using Figure 22, the overview of the family tree management process by the management system 1 will be explained. Figure 22 is a diagram showing the overview of the family tree management process according to the embodiment.

[0116] First, the user requests financial institution A Bank to identify the heirs. Financial institution terminal 10c at Bank A receives the request to identify the heirs from user terminal 20c (step S21). Having received the request, financial institution terminal 10c transmits the request received from the user to management device 100A (step S22). Next, management device 100A, having received the request, creates a family tree based on the request. Management device 100A saves the created family tree to the management DB. Finally, management device 100A transmits the created family tree to financial institution terminal 10c (step S23).

[0117] Next, the same user requests Z Bank, a different financial institution from A Bank, to identify the heirs. This is because the deceased may have contracts with multiple financial institutions. In other words, Z Bank's financial institution terminal 10d receives the request to identify the heirs from the user terminal 20c (step S24). In this example, the same user requests the creation of a family tree from multiple financial institutions, but such requests can also be made by other users. That is, the first user may make a request to financial institution A Bank, and the second user may make a request to another financial institution, Z Bank. The second user may be, for example, an heir listed in the family tree who is different from the first user.

[0118] The financial institution terminal 10d that received the request transmits the request received from the user to the management device 100A (step S25). The management device 100A that received the request determines whether or not a family tree previously created by the financial institution exists in the management DB. For example, the management device 100A determines whether or not a family tree exists based on a request made by the user to financial institution A to create a family tree in the past. If it is determined that a family tree exists, the management device 100A transmits the family tree to the financial institution terminal 10d (step S26). If it is determined that a family tree does not exist, the management device 100A creates a family tree and transmits it to the financial institution terminal 10d.

[0119] In this way, the management device 100A stores family trees that it has previously received requests for in the management database within the storage unit 120A, so that when a user requests the creation of a family tree from another financial institution, it can transmit the stored family tree. This eliminates the need for the management device 100A to create the same family tree multiple times.

[0120] (2-3. Configuration of the control device according to the embodiment) Next, the configuration of the management device 100A that performs the management processing according to the embodiment will be described. Figure 23 is a diagram showing an example of the configuration of the management device 100A according to the embodiment. Here, the same configuration described in Figure 3 will be omitted, and only the control unit 130A and the family tree information storage unit 123 included in the storage unit 120A will be described.

[0121] The family tree information storage unit 123 stores the created family tree among the information used in the management processing according to the embodiment. Figure 24 is a diagram showing an example of the family tree information storage unit 123 according to the embodiment. As shown in Figure 24, the family tree information storage unit 123 stores the following items: "Family Tree ID", "Creation Date", "Requester ID", "Financial Institution Name", "Financial Institution ID", "Deceased", and "Heir".

[0122] "Family Tree ID" is an identification number used to identify the created family tree. "Creation Date" is the date the family tree was created. "Client ID" is an identification number used to identify the client who requested the creation of the family tree. "Financial Institution Name" is the name of the financial institution to which the client made the request. "Financial Institution ID" is an identification number used to identify the financial institution to which the client made the request. "Deceased" is the person who died leaving behind assets. "Heir" is the person who inherits the assets of the deceased.

[0123] To illustrate with the example in Figure 24, the management device 100A registers that the date the family tree was created is "April 1, 2024" for the request with family tree ID "F01". In this request, the name of the requesting financial institution is "Bank D", and the financial institution ID identifying the financial institution is "C01". For the request with family tree ID "F01", the management device 100A registers the deceased "J01" and heir "X01" listed in the family tree.

[0124] Returning to Figure 23, let's continue the explanation of the control unit 130A. As shown in Figure 23, it includes a reception unit 131, a determination unit 136, an update unit 137, and an output unit 135.

[0125] The reception unit 131 receives requests from users to a second financial institution for the purpose of identifying heirs. Here, the second institution is a different financial institution from the one that previously received a request to create a family tree. For example, the reception unit 131 receives a request to identify heirs from the financial institution terminal 10d. Subsequently, the reception unit 131 stores the information of the received request in the storage unit 120A.

[0126] Furthermore, the reception unit 131 may accept requests from the user or a second institution to send a family tree to multiple other institutions with a single request. For example, if the deceased had accounts at multiple financial institutions, the user would have to request the creation of a family tree from each of these institutions. However, if a family tree has already been created at one financial institution, the user can use that family tree and avoid having to request the creation of a family tree from each of the other financial institutions.

[0127] Therefore, the reception unit 131 may accept a request from the user or a second institution to send a family tree to multiple other institutions in a single request.

[0128] For example, the reception unit 131 receives a request to send a family tree to several financial institutions selected by the user from among several financial institutions where the deceased had accounts.

[0129] This reduces the processing load on the management device 100A by preventing it from receiving a large number of requests, such as sending family trees to each of multiple financial institutions. Furthermore, users are saved the trouble of having to request family tree creation from each of the multiple financial institutions.

[0130] The determination unit 136 determines, based on the deceased person related to the request received by the reception unit 131, whether or not a family tree that identifies the heirs and was previously created by the first institution exists in the storage unit 120A. Here, the first institution is a financial institution that previously made a request for family tree creation to the management device 100A. For example, if the determination unit 136 receives a request for family tree creation from the second financial institution, it determines whether or not a family tree previously created by the first financial institution exists in the storage unit 120A. If the determination shows that a previously created family tree exists in the storage unit 120A, the determination unit 136 determines that the family tree should be sent to the second financial institution. On the other hand, if the determination shows that no previously created family tree exists in the storage unit 120A, the determination unit 136 returns the process to the reception unit 131 in order to create a new family tree.

[0131] The determination unit 136 determines whether or not a family tree has been created in the past concerning the deceased. For example, if the user has previously requested a family tree to be created from a financial institution, a family tree already exists. In that case, determining whether or not a family tree has been created in the past can save the user the trouble of creating a new family tree.

[0132] Therefore, the determination unit 136 determines whether or not a family tree related to the deceased has been created in the past. The determination unit 136 determines, for example, that the user who made the request is the person in question. This is to prevent the family tree from being misused by others. This is because financial institutions accept requests to create family trees for heirs, but they are required to verify whether or not the user who made the request is related to the deceased.

[0133] Specifically, the determination unit 136 sets the name, date of birth, and date of death of the deceased listed in the family tree as conditions for determining whether the user who made the request is a designated heir, or whether the deceased related to the request is the same as the deceased listed in the family tree. For example, the determination unit 136 determines whether the user who made the request is involved in the inheritance. Specifically, when the user applies for a request to create a family tree, they enter the name, date of birth, and date of death of the deceased in the application form. Based on this, the determination unit 136 compares the information of the deceased applied for with the information of a family tree created in the past to determine whether the user who made the request is an heir. The determination unit 136 also determines whether the user who made the request is an heir listed in the family tree by comparing the information of the deceased applied for with the information of a family tree created in the past. Furthermore, if the determination unit 136 cannot make a determination based on the information of the deceased, for example, it sets the condition as whether the information of a predetermined number of heirs listed in the family tree matches. Specifically, the determination unit 136 uses the condition that the names of two or more heirs match as a condition for determination. This allows the management device 100A to determine that the user who made the request is an heir listed in the family tree, even if the deceased and the requesting user have the same name. Furthermore, it ensures that the user can reliably obtain their own family tree and prevents the family tree from being sent to users who are not involved in the inheritance.

[0134] The update unit 137 updates the family tree information when a predetermined period has elapsed since the date the family tree was created by the first institution. For example, the update unit 137 sets the predetermined period to one month and updates the family tree. The conditions for updating the family tree information are explained below. For example, if an heir listed in the current family tree dies, the update unit 137 creates and updates the family tree excluding the deceased heir. Also, for example, if an heir listed in the current family tree loses their eligibility as an heir, the update unit 137 creates and updates the family tree excluding the person who lost their eligibility. Also, for example, if a person other than the heirs listed in the current family tree becomes eligible to inherit, the update unit 137 creates and updates the family tree including the new heir. If a new family tree is not created, the update unit 137 updates the date listed in the family tree. This allows the management device 100A to always keep the family tree provided to users or financial institutions up-to-date.

[0135] The update unit 137 updates the family tree information when a predetermined period has elapsed since the date the family tree was created by the first institution. For example, the update unit 137 sets the predetermined period to one month and updates the family tree. This is because, when using a family tree created in the past at another financial institution, the information shown in the family tree may have changed if a long period of time has passed since its creation.

[0136] The update unit 137 determines whether or not there have been any changes to the information in the family tree after a predetermined period has elapsed since the family tree was created. If the update unit 137 determines that there have been no changes to the information since the family tree was created, it does not change the contents of the family tree and records the date and time when the changes to the family tree were confirmed. Subsequently, the update unit 137 can keep the family tree up-to-date by repeatedly determining whether or not a predetermined period has elapsed since the date and time of such update.

[0137] On the other hand, if the update unit 137 determines that there has been a change in information after the family tree has been created, it updates the information in the family tree. A change in family tree information means, for example, that the heirs shown in the family tree have changed. Specifically, a change in heirs means that the heir listed in the family tree has died or that the heir has lost their eligibility as an heir. In this case, the update unit 137 obtains the updated heir information from the user and updates the family tree. The update unit 137 may also update the family tree to include the new heir if, for example, a person who is newly eligible to be an heir appears in addition to the heirs listed in the current family tree. This allows the management device 100A to always keep the family tree it provides to the user or financial institution up to date.

[0138] If the output unit 135 determines that a family tree exists, it outputs the family tree to a second institution. For example, if the output unit 135 determines that a family tree exists, it outputs a setting screen asking whether or not to output the family tree to a second financial institution. The user then sets whether or not to output from the setting screen. If the user determines that it is acceptable to output the family tree to another financial institution, the output unit 135 outputs the family tree to the other financial institution. Note that the determination of whether or not it is acceptable to output the family tree to another financial institution can be requested not only from the user but also from heirs or financial institutions. The output unit 135 can also pre-set whether or not it is acceptable to output the family tree to another financial institution. If the output unit 135 receives a determination from the user or financial institution that it is not acceptable to output the family tree to another financial institution, it will not output it to the other financial institution.

[0139] Furthermore, the output unit 135 outputs the family tree to multiple other institutions in response to requests from the user or financial institution. For example, in response to a request received by the reception unit 131 to output the family tree to multiple financial institutions in a single request, the output unit 135 outputs the family tree to those other financial institutions. This allows the management device 100A to eliminate the need for the user or financial institution to repeatedly request the creation of the family tree.

[0140] Furthermore, the output unit 135 can also provide information to the user or financial institution based on a request from the requesting party. For example, suppose a user requests to know how many heirs there are in the family tree they have created. In such a case, the output unit 135 will output a response to the request if it can confirm that the user who made the request is indeed the person in question.

[0141] Furthermore, in the above embodiment, the management device 100A was described as receiving requests from users or financial institutions and, if a family tree has been created in the past, outputting that family tree to other financial institutions. However, the management device 100A can also receive requests from a wide range of clients, including not only financial institutions but also corporations such as companies and professional service providers, or individuals.

[0142] (2-4. Procedure for management processing according to the embodiment) Detailed procedures for the management process according to the above embodiment will be explained with reference to Figure 25. Figure 25 is a flowchart showing the procedure for determining whether or not to send a family tree according to the embodiment. As shown in Figure 25, first, the management device 100A determines whether or not it has received a request from the user to create a family tree (step S601). If the request for family tree creation has not been received (step S601; No), the management device 100A waits until a request is received. On the other hand, if the request for family tree creation has been received (step S601; Yes), the management device 100A identifies the deceased person to whom the request pertains (step S602).

[0143] Next, the management device 100A determines whether or not a family tree has been created in the past concerning the deceased (step S603). If a family tree has been created in the past concerning the deceased (step S603; Yes), the management device 100A sends the previously created family tree to the financial institution to which the user made the second or subsequent request (step S604). This is because the family tree was created at the financial institution to which the first request was made, and the family tree created in the first request is sent to the financial institution to which the second request was made. On the other hand, if there is no family tree that has been created in the past concerning the deceased (step S603; No), the management device 100A creates a new family tree and sends it to the financial institution (step S605), and then terminates the process.

[0144] (3. Other Embodiments) The processing according to the above-described embodiment may be carried out in various other forms besides those described above.

[0145] For example, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above document and drawings can be changed at will unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0146] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0147] Furthermore, the embodiments and modifications described above can be combined as appropriate, provided that the processing content is not inconsistent.

[0148] Furthermore, the effects described herein are merely illustrative and not limiting; other effects may also occur.

[0149] (4. Effects of the control device related to this disclosure) As described above, the management device (management device 100 in the embodiment) relating to this disclosure comprises a reception unit (reception unit 131 in the embodiment), a classification unit (classification unit 132 in the embodiment), and a display control unit (display control unit 134 in the embodiment). The reception unit receives multiple requests for the purpose of identifying heirs. The classification unit classifies the processes for identifying heirs, which are executed based on the received requests, according to the status indicating the progress of the processes. The display control unit displays the classified status.

[0150] In this way, the management device can easily manage multiple requests for identifying heirs by classifying their status according to their progress and displaying them on the screen. Furthermore, the management device can also easily manage multiple financial institutions.

[0151] Because the management device 100 shares a common management number with financial institutions, it can easily display the progress of multiple requests by sorting them based on their status and updating status. Furthermore, since the management device 100 manages multiple requests using financial institution numbers, it can immediately check the progress status and communicate with users or financial institutions even if they send emails or other communications requesting progress updates, based on the financial institution number.

[0152] Furthermore, the management device displays the number of currently registered requests for each status. This allows the management device to display the number of requests that need to be processed, and the number of requests each person is handling can be seen at a glance, making it easy to manage multiple requests.

[0153] Furthermore, when a user selects a status on the user interface where the status is displayed, the management device will display information about the request corresponding to that selected status. This allows the management device to view the details screen for each request, making it easier to manage multiple requests.

[0154] Furthermore, the management device displays a user interface with different status classifications for the first institution that made multiple requests (financial institution terminal 10 in this embodiment) and the second institution that performs the process of identifying the heirs (management device 100 in this embodiment). This allows the management device to appropriately change the status classification display required by the first and second institutions. In addition, the management device makes it easier for each person in charge of processing the requests at the second institution to process the requests by displaying the necessary status classification. Furthermore, the management device can provide a visually easy-to-understand user interface by classifying and displaying the progress of request processing by status. Even when there are multiple requests, the management device can immediately respond to inquiries about the progress from financial institutions and users by classifying the status according to the progress.

[0155] Furthermore, when the management device receives a request for a change in the screen display from the first institution (in this embodiment, the financial institution terminal 10), it displays the user interface accordingly. This allows the management device to constantly provide a user interface that meets the requests of the first institution. In addition, since the management device can display different user interfaces for each of the multiple first institutions, it can provide an appropriate user interface for each of the multiple first institutions.

[0156] The management device relating to this disclosure (management device 100 in this embodiment) further comprises a creation unit (creation unit 133 in this embodiment) and an output unit (output unit 135 in this embodiment). The creation unit creates a family tree corresponding to a request for which the processing of documents has been completed among the requests received from a first institution (financial institution terminal 10 in this embodiment), including an indication of the identified heir. The output unit outputs the created family tree to the first institution (financial institution terminal 10 in this embodiment).

[0157] Thus, if the request received from the first institution is complete and there are no deficiencies in the documents, the management device can create a family tree to identify the heirs, thereby providing the first institution with a family tree that allows for easy identification of the heirs.

[0158] Furthermore, if the management device finds any deficiencies in the request documents received from the first institution (in this embodiment, the financial institution terminal 10), it creates a deficiency notice to inform the first institution of the deficiencies, and outputs a notification to the first institution (in this embodiment, the financial institution terminal 10) with a reading code attached that links the created deficiency notice to the request.

[0159] The management device can easily manage multiple requests by linking the deficiency report and the request using a reading code.

[0160] As described above, the management device relating to this disclosure (management device 100A in the embodiment) comprises a reception unit (reception unit 131 in the embodiment), a determination unit (determination unit 136 in the embodiment), and an output unit (output unit 135 in the embodiment). The reception unit receives requests from users to a first institution (second financial institution in the embodiment) for the purpose of identifying heirs. The first institution is a financial institution that has previously requested the management device to create a family tree. The determination unit determines, based on the deceased person related to the received request, whether a family tree that identifies the heirs and was previously created by the second institution (first financial institution in the embodiment) exists in the storage unit (storage unit 120A in the embodiment). The second institution is a financial institution different from the financial institution that previously requested the creation of a family tree. If the output unit determines that a family tree exists, it outputs the family tree to the first institution.

[0161] In this way, if a family tree for identifying heirs has been created in the past, the management device can send the existing family tree to the financial institution, thus avoiding the trouble of creating the same family tree twice.

[0162] Furthermore, the management device sets the name, date of birth, and date of death of the deceased as recorded in the family tree as conditions for determining whether the user making the request is a designated heir, or whether the deceased in the request is the same person as the deceased in a previously created family tree. This allows the management device to reliably determine whether the user making the request is an heir as recorded in the family tree by comparing the information of the deceased recorded in the application form with the information of the deceased in a previously created family tree. In addition, even if the deceased or two or more users making the request have the same name, the management device can prevent the family tree from being passed on to users other than the heirs by using the information of the deceased as a condition for determination.

[0163] Furthermore, the management system updates the family tree information after a predetermined period has elapsed since the family tree was created by the second institution. This ensures that the management system always provides users or financial institutions with the most up-to-date family tree. In addition, the management system can immediately reflect any changes in the heirs listed in the family tree.

[0164] Furthermore, the management system accepts requests from the user or the first institution to send family trees to multiple other institutions with a single request, and outputs the family trees to the other institutions as requested. This allows the management system to save the user the trouble of performing multiple procedures. In addition, by using the same family tree, the management system can prevent errors in how family trees are recorded between financial institutions.

[0165] (5. Hardware Configuration) The information devices such as the management device 100 according to the embodiment described above are realized by a computer 1000 having a configuration such as that shown in Figure 26. Hereinafter, the management device 100 according to the embodiment will be described as an example. Figure 26 is a hardware configuration diagram showing an example of a computer 1000 that realizes the functions of the management device 100. The computer 1000 has a CPU 1100, RAM 1200, ROM (Read Only Memory) 1300, HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input / output interface 1600. The various parts of the computer 1000 are connected by a bus 1050.

[0166] The CPU 1100 operates based on programs stored in the ROM 1300 or HDD 1400, and controls various parts. For example, the CPU 1100 loads the programs stored in the ROM 1300 or HDD 1400 into the RAM 1200 and executes processing corresponding to the various programs.

[0167] ROM1300 stores boot programs such as the BIOS (Basic Input Output System) executed by CPU1100 when computer 1000 starts up, as well as programs that depend on the computer 1000's hardware.

[0168] HDD1400 is a computer-readable recording medium that non-temporarily records programs executed by CPU1100 and data used by such programs. Specifically, HDD1400 is a recording medium that records a program that performs the calculation processing related to this disclosure, which is an example of program data 1450.

[0169] The communication interface 1500 is an interface for the computer 1000 to connect to an external network 1550 (e.g., the Internet). For example, the CPU 1100 can receive data from other devices or transmit data it generates to other devices via the communication interface 1500.

[0170] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the CPU 1100 receives data from input devices such as a keyboard or mouse via the input / output interface 1600. The CPU 1100 also transmits data to output devices such as a display, speaker, or printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs recorded on a predetermined recording medium (media). Examples of media include optical recording media such as DVDs (Digital Versatile Discs) and PDs (Phase Change Rewritable Disks), magneto-optical recording media such as MOs (Magneto-Optical Disks), tape media, magnetic recording media, or semiconductor memory.

[0171] For example, when computer 1000 functions as a management device 100 according to the embodiment, the CPU 1100 of computer 1000 realizes functions such as the control unit 130 by executing a management program loaded on RAM 1200. The HDD 1400 stores programs that execute the management processing according to this disclosure, as well as data in the storage unit 120. The CPU 1100 reads and executes program data 1450 from the HDD 1400, but as another example, these programs may be obtained from other devices via an external network 1550.

[0172] Although embodiments of the present application have been described in detail based on the drawings, these are illustrative examples, and the present invention can be implemented in various other forms with modifications and improvements based on the knowledge of those skilled in the art, starting with the embodiments described in the disclosure section of the invention. [Explanation of Symbols]

[0173] 1 Management System 10 Financial Institution Terminals 20 User Terminals 100 Management device 110 Communications Department 120 Storage section 121 Application information storage unit 122 Secretariat Information Storage Department 123 Family tree information storage unit 130 Control Unit 131 Reception Department 132 Classification Department 133 Creative Section 134 Display Control Unit 135 Output section 136 Judgment section 137 Update Department 300 Family Register Transcripts 400 Resending documents 500 Family Trees 600 Letter of deficiency 700 User Interfaces 700a User Interface 800 Selection screen 800a Search Results Screen 900 Details screen

Claims

1. A reception desk that receives requests from users to the first agency for the purpose of identifying heirs, A determination unit determines whether or not a family tree that identifies the heirs based on the deceased person to whom the request received above exists in the memory unit, and whether or not a family tree previously created by the second institution exists. If it is determined that the aforementioned family tree exists, an output unit outputs the family tree to the first institution, A control device characterized by being equipped with the following features.

2. The determination unit, As a condition for determining whether the user who made the aforementioned request is a designated heir, or whether the deceased person to whom the request pertains is the same as the deceased person to whom the family tree previously created is set, the name, date of birth, and date of death of the deceased person listed in the family tree are set. The control device according to feature 1.

3. The update unit updates the information in the family tree when a predetermined period has elapsed since the date the family tree was created by the second organization. The control device according to claim 1, further comprising:

4. The aforementioned reception unit is A request is accepted from the user or the first institution to transmit the family tree to multiple other institutions in a single request. The output unit is, In response to the aforementioned request, the family tree will be output to the aforementioned multiple institutions. The control device according to feature 1.

5. Computers We accept requests from users to the first agency for the purpose of identifying heirs. Based on the deceased person to whom the aforementioned request was received, it is determined whether or not a family tree identifying the heirs, which was previously created by the second institution, exists in the memory unit. If it is determined that the aforementioned family tree exists, the family tree is output to the first institution. A management method characterized by including the following.

6. Computers, A reception desk that receives requests from users to the first agency for the purpose of identifying heirs, A determination unit determines whether or not a family tree that identifies the heirs based on the deceased person to whom the request received above exists in the memory unit, and whether or not a family tree previously created by the second institution exists. If it is determined that the aforementioned family tree exists, an output unit outputs the family tree to the first institution, A management program characterized by functioning as a management device equipped with the necessary components.

Images