Management device, management method, and management program

Abstract

To efficiently manage multiple requests from financial institutions. [Solution] The management device is characterized by comprising: a reception unit that receives multiple requests for the purpose of identifying heirs; a classification unit that classifies processes for identifying heirs that are executed based on the received multiple requests by status indicating the progress of the processes; and a display control unit that displays the classified status. For example, the display control unit displays the number of the multiple requests currently registered for each status.

Description

[Technical Field]

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

[0002] In recent years, various systems have been developed to help identify legal heirs. For example, there is a system that identifies names of legal heirs by using optical character recognition (OCR) on the text information printed on family registers.

[0003] As a system for supporting the identification of legal heirs, for example, a technology is known that displays the steps required for inheritance procedures, assigns a number to each case, manages the information based on the assigned number, and stores at least one piece of progress information such as instructions to resolve deficiencies corresponding to the inheritance information, acceptance of the inheritance notification, and completion of the inheritance procedures (Patent Document 1).Alternatively, a technology is known that acquires image data of a family register, recognizes character information contained in the image data, and generates a family tree based on the recognized character information regarding the people listed in the family register (Patent Document 2). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-228051 [Patent Document 2] Japanese Patent Publication No. 2024-022551 Summary of the Invention [Problem to be solved by the invention]

[0005] By using conventional technology, it is possible to easily identify legal heirs. However, systems that support the identification of legal heirs are used by clients, and handle inheritance procedures not for a small number of users, but for a large number of users who are clients of the client. Inheritance procedures for a large number of users require a huge amount of management and procedural processing, so it is necessary to manage them efficiently.

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

[0007] In order to solve the above problems, one form of management device according to the present disclosure is characterized by comprising: a reception unit that receives multiple requests aimed at identifying heirs; a classification unit that classifies the processing for identifying heirs that is executed based on the multiple received requests by status indicating the progress of the processing; and a display control unit that displays the classified status. [Effects of the Invention]

[0008] According to one aspect of the embodiment, it is possible to efficiently manage multiple requests from request sources. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an overview of a management system according to an embodiment. [Figure 2] FIG. 1 is a diagram illustrating an overview of a management process according to an embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of the configuration of a management device according to the embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of an application information storage unit according to the embodiment. [Figure 5] FIG. 1 is a diagram (1) illustrating an example of a secretariat information storage unit according to an embodiment. [Figure 6] FIG. 10 is a diagram (2) illustrating an example of the secretariat information storage unit according to the embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of a document accepted by a accepting unit according to the embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a document to be resent that is accepted by a accepting unit according to the embodiment. [Figure 9] FIG. 10 is a diagram showing an example of a family tree created by a creating unit according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a defect report created by a creating unit according to an embodiment. [Figure 11] FIG. 1 is a diagram (1) showing an example of a user interface displayed by a display control unit according to an embodiment. [Figure 12] FIG. 10 is a diagram (2) showing an example of a user interface displayed by the display control unit according to the embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of a management screen of request information displayed by a display control unit according to the embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a detailed screen of request information displayed by a display control unit according to the embodiment. [Figure 15] FIG. 4 is a sequence diagram illustrating a processing flow of a management system according to an embodiment. [Figure 16] 1 is a flowchart (1) showing the procedure of a status classification process according to an embodiment. [Figure 17] 10 is a flowchart (2) showing the procedure of the status classification process according to the embodiment. [Figure 18] 10 is a flowchart (3) showing the procedure of the status classification process according to the embodiment. [Figure 19] 10 is a flowchart (4) showing the procedure of the status classification process according to the embodiment. [Figure 20] 10 is a flowchart (5) showing the procedure of the status classification process according to the embodiment. [Figure 21] FIG. 10 is a diagram illustrating a modified example of the management system according to the embodiment. [Figure 22] FIG. 2 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of a management device. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the following embodiments, the same components are designated by the same reference numerals, and redundant description will be omitted.

[0011] (1. Embodiment) (1-1. Overview of the management system according to the embodiment) The management process according to the present disclosure is performed by a management system 1 shown in Fig. 1. The configuration of the management system 1 according to the embodiment and an overview of the management process performed by the management system 1 will be described with reference to Fig. 1. 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 identifying heirs, etc. For example, the management device 100 is a server device, a personal computer (PC), a cloud server, etc. As shown in FIG. 1 , the management device 100 conveniently has a general affairs department, an initial identification department, and a re-identification department as functions in the management process, 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 identification results to the financial institution. The management device 100 also stores each piece of information and the processing results in a database. The management device 100 may have its own function of performing OCR processing to convert requested documents into image data, or it may be a device that works in conjunction with a dedicated OCR device.

[0014] The administrator terminal 100a is a terminal used by the administrator and secretariat who use the management device 100. The secretariat is an organization that uses the management device 100 to process requests received from financial institutions.

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

[0016] An example of a financial institution is a bank. A bank branch is a facility located away from the bank's headquarters where banking operations are carried out. Operations performed by a bank include, for example, refunding account deposits to legal heirs when an account holder dies. For example, when a user account holder dies, Branch A shown in FIG. 1 identifies the legal heirs and refunds the account deposits to the identified legal heirs. At this time, Branch A uses a financial institution terminal 10 to communicate with the management device 100 via the communication network N. Specifically, Branch A requests the management device 100 to create a family tree 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 holds an account with the financial institution, or a person who has some kind of relationship with the account holder. For example, when an account holder who holds an account with the financial institution dies, the user requests the financial institution to handle inheritance procedures. Specifically, the user uses the user terminal 20 to send documents necessary for the inheritance procedures to the financial institution terminal 10. The user may also bring or mail the documents necessary for the inheritance procedures to the financial institution.

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

[0019] (1-2. Overview of management process) Next, an overview of the management process performed by the management system 1 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an overview of the management process according to the embodiment.

[0020] First, the financial institution terminal 10 receives an application document requesting the identification of heirs from the user terminal 20 (step S1). The application document is a document for identifying legal heirs including the user, such as a certified copy of the user's family register. The financial institution terminal 10 converts the application document 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 the image data of the application documents from the financial institution terminal 10, it registers a request to identify the legal heirs based on the information contained in the received image data (step S2).

[0022] The management device 100 updates the status information of the registered requests, indicating the progress of the requests, as appropriate. That is, the management device 100 classifies the status of each request and enables the financial institution to check the classified information at any time, thereby enabling the financial institution to manage a large number of requests.

[0023] Details will be described later, but for example, the management device 100 classifies requests into statuses such as "initial registration completed," "re-registered," "waiting for initial inspection," "waiting for re-inspection," "waiting for call due to deficiency," and "successfully completed." For example, in step S2, when there is progress such as "application documents accepted," the management device 100 registers the status as "initial registration completed."

[0024] Next, the management device 100 checks whether the received application documents are complete. A deficiency refers to a missing piece of information that would cause problems in the process of identifying legal heirs. If the application documents are complete, the management device 100 registers a progress message stating "there is a deficiency." In this case, the management device 100 creates a deficiency notice indicating that there is a deficiency, and transmits the deficiency notice data to the financial institution terminal 10 (step S3). If the deficiency notice data has been transmitted, the management device 100 registers a progress message stating "the deficiency notice data has been output."

[0025] The financial institution terminal 10 transmits the received deficiency data to the user terminal 20 (step S4). If there is a deficiency in the document, the management device 100 may call the user terminal 20 to inform the user of the deficiency (step S5). For example, the management device 100 can select a means of informing the user of the deficiency, such as sending the deficiency data to the user terminal 20 or sending an email or a phone call to inform the user of the deficiency. After that, for example, if there is progress such as "a call has been made to the user terminal 20," the management device 100 registers the status "call regarding deficiency completed."

[0026] The user terminal 20 transmits the resent document to the financial institution terminal 10 based on the received deficiency data (step S6). The financial institution terminal 10 transmits the received resent document to the management device 100 (step S7). When the management device 100 receives the resent document, it registers a progress message stating "resent document received." Thereafter, the management device 100 checks whether the resent document has any deficiencies.

[0027] The management device 100 checks whether there are any defects in the resent documents received from the financial institution terminal 10, and if there are no defects, analyzes the family register using AI-OCR (Artificial Intelligence Optical Character Recognition). Using the results of the analysis, the management device 100 identifies multiple legal heirs and creates 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). Thereafter, if there is progress such as "the family tree has been created and sent to the financial institution terminal 10," the management device 100 registers a status of "successful completion."

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

[0029] In this way, the management device 100 can easily manage requests by accepting requests to identify heirs from the financial institution terminal 10 and classifying the progress status for each request. Furthermore, since the management device 100 classifies requests by progress status, the progress status can be easily referenced.

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

[0031] 3, the management device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The communication unit 110 is realized by, for example, a network interface card (NIC) or a network interface controller. The communication unit 110 is connected to a network (e.g., the Internet) by wire or wirelessly, and transmits and receives information to and from the financial institution terminal 10, the user terminal 20, and the like via the Internet. For example, the communication unit 110 may transmit and receive information using any communication standard or communication technology, such as Wi-Fi (registered trademark), Bluetooth (registered trademark), a subscriber identity module (SIM), or low power wide area (LPWA).

[0032] The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk.

[0033] The storage unit 120 has an application information storage unit 121 and a secretariat information storage unit 122. The information stored in the storage unit 120 will be described below with reference to Figures 4 to 6. In the examples shown in Figures 4 to 6, the information stored in the storage unit 120 may be conceptually represented as "A01", but in reality, each piece of information described below is stored in the storage unit 120.

[0034] The application information storage unit 121 stores, among the information used in the management process according to the embodiment, information that is common to the secretariat that accepts requests for management targets and the financial institution that makes the requests.

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

[0036] The "common management number" is a number assigned to the request, and is a number common to the management device 100 and the financial institution terminal 10. The "common management number" is identification information for identifying the 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 from each other. The "application date" is the date on which the request was submitted. The "application deadline" is the deadline for the request. The "status" is a classification that indicates how far the processing of the request has progressed. The "same status retention period" is the number of days that have passed since the status was updated.

[0037] Using the example of FIG. 4, the management device 100 indicates that it has assigned a financial institution management number "B01" to a request with a common management number "A01." The application date of this request is "January 1, 2024," and the application deadline is "March 31, 2024." The management device 100 then classifies this request into a status of "initial registration completed," which indicates that the request has been accepted. This status has continued for "1 day."

[0038] Similarly, for a request with common management number "A02," when processing has been completed up to step S3 in FIG. 2, the management device 100 updates the status to "resent registration completed" and registers it. For a request with common management number "A03," when processing has been completed up to step S8 in FIG. 2, the management device 100 updates the status to "successfully completed" and registers it. For a request with common management number "A04," when processing has been completed up to step S2 in FIG. 2, the management device 100 updates the status to "awaiting initial inspection" and registers it.

[0039] Next, the secretariat information storage unit 122 will be described with reference to FIGS. 5 and 6. The secretariat information storage unit 122 stores the number of requests for each status category. FIG. 5 is a diagram (1) illustrating an example of the secretariat information storage unit 122 according to an embodiment. As shown in FIG. 5, the secretariat information storage unit 122a stores the following items: "Financial institution," "Initial registration completed," "Retransmission completed," "Awaiting initial verification," "Awaiting re-verification," and "Successful completion." "Financial institution" is the name of the financial institution that made the request. "Initial registration completed" refers to the number of requests registered in the management device 100 when the request was received from the financial institution terminal 10 or the user terminal 20. "Retransmission completed" refers to the number of requests for which the management device 100 has received deficiency notices and missing or corrected documents from the financial institution terminal 10 or the user terminal 20. "Awaiting initial verification" refers to the number of deficiency notices or family tree creations awaiting completion. "Waiting for re-verification" is the number of cases where the initial verification is waiting for confirmation of the deficiency notice or family tree for errors. "Completed normally" is the number of cases where the management device 100 has created a family tree to identify the heirs and output the created family tree to the financial institution terminal 10.

[0040] 5, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch A," there are "250" requests that are "initial registration completed," "21" requests that are "resent completed," "75" requests that are "awaiting initial verification," "15" requests that are "awaiting re-verification," and "5" requests that are "completed normally." In another example, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch B," there are "170" requests that are "initial registration completed," "11" requests that are "resent completed," "9" requests that are "awaiting initial verification," "7" requests that are "awaiting re-verification," and "3" requests that are "completed normally." In another example, the management device 100 indicates that the status of requests received from the financial institution "C Branch" is as follows: "670 requests registered for the first time," "170 requests retransmission completed," "55 requests awaiting initial verification," "25 requests awaiting reverification," and "20 requests completed successfully."

[0041] As shown in FIG. 5, the secretariat information storage unit 122b stores the following items: "Waiting for re-inspection of deficiency," "Request for creation of deficiency notice," "Waiting for call due to deficiency," and "Call due to deficiency completed." "Waiting for re-inspection of deficiency" is the number of requests for which there are no errors in the deficiency notice. "Request for creation of deficiency notice" is the number of requests for creation of a deficiency notice to notify the user terminal 20 of any deficiencies in the document output from the financial institution terminal 10 or the user terminal 20. "Waiting for call due to deficiency" is the number of cases in which there are deficiencies in the document output from the financial institution terminal 10 or the user terminal 20 before the management device 100 makes a call to the user terminal 20. "Call due to deficiency completed" is the number of cases in which there are deficiencies in the document output from the financial institution terminal 10 or the user terminal 20 after the management device 100 makes a call to the financial institution terminal 10 or the user terminal 20.

[0042] 5, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch A," there are "27" requests for "waiting for re-inspection for deficiency," "100" requests for "request to create deficiency letter," "21" requests for "waiting for call due to deficiency," and "22" requests for "call due to deficiency." In another example, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch B," there are "16" requests for "waiting for call due to deficiency," "60" requests for "request to create deficiency letter," "35" requests for "waiting for call due to deficiency," and "7" requests for "waiting for call due to deficiency." In another example, the management device 100 indicates that the status of requests received from the financial institution "C Branch" is "240 requests for "Waiting to call due to deficiency," "210 requests for "Request to create deficiency letter," "120 requests for "Waiting to call due to deficiency," and "100 requests for "Waiting to call due to deficiency."

[0043] FIG. 6 is a diagram (2) showing an example of the secretariat information storage unit 122 according to the embodiment. As shown in FIG. 6, the secretariat information storage unit 122c stores the following items: "Financial institution," "Normally uploaded," "Defective notice uploaded," "90 days passed," "Withdrawal request made," and "Withdrawn." "Normally uploaded" is the number of cases in which the management device 100 has output a family tree to the financial institution terminal 10. "Defective notice uploaded" is the number of cases in which the management device 100 has output a defect notice to the financial institution terminal 10 or the user terminal 20. "90 days passed" is the number of requests for which 90 days have passed since the request was received from the financial institution terminal 10. "Withdrawal request made" is the number of cases in which a request to withdraw a request was received from the financial institution terminal 10 or the user terminal 20. "Withdrawn" is the number of requests that have been withdrawn.

[0044] 6, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch A," there are "70 requests for which "normal upload has been completed," "95 requests for which deficiency notices have been uploaded," "3 requests for which 90 days have passed," "17 requests for which a request for withdrawal has been made," and "15 requests for which the request has been withdrawn." In another example, the management device 100 indicates that, regarding the status of requests received from the financial institution "Branch B," there are "87 requests for which "normal upload has been completed," "42 requests for which a request for deficiency notices has been uploaded," "10 requests for which 90 days have passed," "8 requests for which a request for withdrawal has been made," and "8 requests for which the request has been withdrawn." In another example, the management device 100 indicates that the status of requests received from the financial institution "C Branch" is as follows: "291 requests have been uploaded successfully," "300 requests have been uploaded with deficiencies," "70 requests have passed 90 days," "77 requests have been requested for withdrawal," and "76 requests have been withdrawn."

[0045] Returning to Fig. 3, the explanation of the control unit 130 will continue. The control unit 130 is realized by, for example, a central processing unit (CPU), a micro processing unit (MPU), a graphics processing unit (GPU), or the like executing a program stored inside the management device 100 using RAM or the like as a work area. The control unit 130 is also a controller, and is realized by, for example, an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0046] As shown in FIG. 3, the control unit 130 includes a receiving unit 131, a classifying unit 132, a creating unit 133, a display control unit 134, and an output unit 135.

[0047] The reception unit 131 receives a plurality of requests for the purpose of identifying an heir. For example, the reception unit 131 receives a request to identify an heir from the financial institution terminal 10. The reception unit 131 then stores information on the received plurality of requests in the storage unit 120.

[0048] Here, documents accepted by the reception unit 131 will be described with reference to FIGS. 7 and 8. FIG. 7 is a diagram showing an example of a document accepted by the reception unit 131 according to the embodiment. As shown in FIG. 7, the reception unit 131 accepts a family register copy 300 from the financial institution terminal 10. The family register copy 300 includes a Taisho 4 (1915) type, a 1948 (1948) type family register, and a 1994 type family register. The reception unit 131 may accept the family register copy 300 as image data or as a written document. Furthermore, if the user is receiving the service in a country that provides the family register copy 300 as electronic data, the reception unit 131 may accept the family register copy as electronic data.

[0049] In order for the management device 100 to identify legal heirs, all documents, including the family register copy 300, must be available. However, since users are often unfamiliar with inheritance procedures, it is not always the case that all documents are available when the status is "initial registration completed." Furthermore, financial institutions may not always be able to receive all documents by the due date due to various circumstances on the part of the user. Therefore, the reception unit 131 receives documents that were received when the status was "initial registration completed," as well as documents that have been resent from financial institutions (hereinafter referred to as "re-sent documents"). An example of a re-sent document is shown in FIG. 8.

[0050] 8 is a diagram showing an example of a resent document accepted by the accepting unit 131 according to the embodiment. The resent document 400 includes a notice of deficiency 401 and a missing document 402 including a family register copy. The notice of deficiency 401 is a document output from the management device 100 when there is a deficiency in the accepted requested document. The missing document 402 is a document that was missing or had corrections when the request was accepted from the financial institution terminal 10 with a status of "initial registration completed." For example, the missing document 402 is a family register copy.

[0051] When the document is classified into the "awaiting initial inspection" status and there are missing documents or documents that need to be corrected, the management device 100 sends a deficiency notice 401 to the financial institution terminal 10. The financial institution terminal 10 that receives the deficiency notice 401 sends it to the user terminal 20. The user terminal 20 that receives the deficiency notice 401 sends a retransmitted document 400 including the missing documents 402 to the financial institution terminal 10. The financial institution terminal 10 that receives the retransmitted document 400 sends the retransmitted document 400 to the management device 100. As a result, the reception unit 131 receives the retransmitted document 400 sent from the financial institution terminal 10.

[0052] The classification unit 132 classifies the processes for identifying heirs, which are executed based on multiple accepted requests, by status indicating the progress of the processes. The classification unit 132 automatically classifies the status when image data is uploaded. For example, when request application data is uploaded to the management device 100, the classification unit 132 automatically classifies the status as "initial registration completed." The classification unit 132 classifies the status based on the time elapsed since the request was registered. For example, if 24 hours have passed since the request was registered as "initial registration completed," the classification unit 132 classifies the request as "awaiting initial inspection."

[0053] The classification unit 132 automatically classifies the status when a predetermined number of days has passed. For example, when 90 days have passed since the date of receiving the request, the classification unit 132 automatically classifies the status as "90 days passed."

[0054] The classification unit 132 classifies the status when it notifies the requester of the request or when it makes a judgment regarding the documents attached to the request. Here, a notification is, for example, sending a notice of deficiency to the financial institution terminal 10 or the user terminal 20, making a phone call, etc. A judgment regarding the documents is, for example, an appraisal by a "first appraisal clerk" or a "re-appraisal clerk" to check whether the documents are free of errors or deficiencies.

[0055] Specifically, when the receiving unit 131 receives a request, the classification unit 132 updates the status classification to "initial registration completed." Next, the classification unit 132 performs a format check on the "initial registration completed" request, and if there are no defects in the documents, the classification unit 132 classifies the status to "awaiting initial inspection." On the other hand, if there are defects in the documents, the classification unit 132 classifies the status to "request for creation of deficiency notice."

[0056] The classification unit 132 checks the contents of the document for a request for "waiting for initial inspection," and if there are no defects in the document, classifies the status as "waiting for re-inspection." On the other hand, if there are defects in the document, the classification unit 132 classifies the status as "request to create a document with defects." Alternatively, if there are defects in the document, the classification unit 132 classifies the status as "waiting for a call regarding defects."

[0057] The classification unit 132 checks whether there are any errors in the family tree for a request for "awaiting re-scanning," and if there are no errors, classifies the status as "normal completion." On the other hand, if there are any errors in the request for deficiency, the classification unit 132 corrects the errors and classifies the request as "awaiting re-scanning" again. If there are no errors in the request for deficiency, the classification unit 132 classifies the request as "awaiting re-scanning due to errors."

[0058] The classification unit 132 outputs a notice of deficiency to the financial institution terminal 10 for a request for "waiting for re-inspection of deficiency," and if the missing documents are output from the financial institution terminal 10, classifies the status as "registered for re-transmission."

[0059] For a request with an "initial registration completed" status, if the classification unit 132 receives a notification of withdrawal from the financial institution terminal 10, the classification unit 132 classifies the status as "withdrawal request made." Next, for a request with a "withdrawal request made," if 90 days have passed since the request was received, the classification unit 132 classifies the status as "90 days passed." For requests for which 90 days have passed, the management device 100 deletes the data.

[0060] As a result, the management device 100 classifies multiple requests by status, and can determine how many requests are in each status.

[0061] The creation unit 133 creates a family tree corresponding to a request received from the financial institution terminal 10 for which document processing has been completed, including a display indicating the identified heirs. For example, the creation unit 133 creates a family tree for a request received from the reception unit 131 for which the documents attached to the request are complete or for which the deficiencies have been resolved. Document processing is completed when, for example, all documents are complete for a request in a status of "awaiting initial verification" or "awaiting re-verification." For example, the creation unit 133 creates a family tree for a request classified by the classification unit 132 as "awaiting initial verification." The creation unit 133 creates a family tree from a certified copy of the family register, with the deceased's lineal descendants, lineal ascendants, and collateral relatives as heirs. The creation unit 133 creates a family tree with marks assigned to each of the deceased and the heirs to distinguish them from each other. This allows the creation unit 133 to 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 people based on, for example, information in a family register. Here, a procedure for the creation unit 133 to create a family tree from information in a family register will be described.

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

[0064] For example, the creation unit 133 arranges the person who corresponds to the husband and the person who corresponds to the wife in parallel based on the determined marital relationship, and connects the couple with a double line. If the marital relationship has been dissolved, the creation unit 133 puts a cross on the double line between the couple. If there are multiple marital relationships, the creation unit 133 arranges the spouses in parallel with the corresponding person at the center.

[0065] Furthermore, the creation unit 133 draws a ruled line downward from the center of the double line between the parent couple based on the determined parent-child relationship, and positions the child. If there are multiple children, the creation unit 133 positions them in order of age, with the oldest child on the left and the youngest child on the right. If the child is adopted by a parent-child union, the creation unit 133 positions them in the same way as for children who are not adopted, but with a double line. If the child is adopted by only the father or mother, the creation unit 133 positions the child directly below the father or mother, connecting the parent and child with a double line.

[0066] Next, we will explain in more detail how to identify heirs. People who can become heirs are limited to the spouse of the deceased and blood relatives of the deceased, and the spouse is always an heir. For this reason, the creation unit 133 checks whether the deceased had a spouse from the information in the family register. If a spouse exists, the creation unit 133 sets the spouse as an heir.

[0067] The creation unit 133 also checks whether there are any heirs other than the spouse. A priority order (inheritance order) is set for people other than the spouse who can become heirs. Lineal descendants are set as the first priority. Lineal descendants are blood relatives who belong to a generation later than the deceased, such as children, grandchildren, and great-grandchildren. Lineal ascendants are set as the second priority. Lineal ascendants are blood relatives who belong to a generation earlier than the deceased, such as parents and grandparents. Siblings are set as the third priority, and if there are no siblings, nephews or nieces are set. Therefore, the creation unit 133 checks whether there are any corresponding people in order from first priority to third priority based on the relationship information, and sets the first corresponding person as the heir.

[0068] In addition, if the member information includes heir disinheritance information (reason for heir exclusion) indicating that a person listed in the family register has been disinherited, the creation unit 133 creates a family tree in which the person who has been disinherited is excluded from the heirs. For example, suppose there are three children who are first in line, and one of them has a reason for disinheritance. In this case, the creation unit 133 excludes the child with the reason for disinheritance from the heirs, and sets the remaining two children as heirs.

[0069] Here, a document created by the creation unit 133 will be described with reference to FIGS. 9 and 10. FIG. 9 is a diagram showing an example of a family tree created by the creation unit 133 according to the embodiment. The creation unit 133 creates a family tree 500 based on a requested copy of a family register. The family tree 500 has a decedent mark 501 indicating a decedent and an heir mark 502 indicating an heir. A decedent is a person who dies leaving behind property, assets, etc. An heir is a person who inherits the property, assets, etc. of the decedent. In FIG. 9, a decedent mark 501 indicating a decedent is assigned to Mr. A, and heir marks 502 indicating heirs are assigned to his spouse, Child B, and his children, Child C, Child D, Child E, and Child F.

[0070] The creation unit 133 may create a family tree with marks indicating the order of heirs in addition to the decedent mark 501 and the heir mark 502. In FIG. 9, the creation unit 133 creates a family tree by adding a first-place mark to the spouse's child B, who is first in the order of inheritance, and adding second-place marks to the children C, D, E, and F, who are second in the order of inheritance. Thereafter, the information of the created family tree 500 is stored in the secretariat information storage unit 122.

[0071] FIG. 10 is a diagram showing an example of a deficiency notice created by the creation unit 133 according to the embodiment. When there is a deficiency in the requested documents received from the financial institution terminal 10, the creation unit 133 creates a deficiency notice to inform the financial institution terminal 10 of the deficiency. For example, the creation unit 133 creates a deficiency notice 600 that lists the names and titles 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 notice of insolvency 600 has a read code 601 that links the notice of insolvency to a corresponding request. The read code 601 is code information that can be read by the management device 100, such as a barcode (one-dimensional barcode information, 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 notice of insolvency to the requester or documents resent by the financial institution in response to the notice of insolvency. This allows the management device 100 to prepare documents to be used for identifying heirs and creating a family tree. The information on the created notice of insolvency 600 is then 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 with reference to FIGS. 11 and 12. FIG. 11 is a diagram (1) showing an example of the user interface displayed by the display control unit 134 according to an embodiment. The user interface 700 shown in FIG. 11 is a user interface displayed by the secretariat that operates the management device 100, and is displayed, for example, on the screen of the administrator terminal 100a. The user interface 700 is a screen that displays the status and number of requests. The status and number of requests are categorized and displayed as general affairs staff 701, initial verification staff 702, re-verification staff 703, and completed 704.

[0074] The general affairs staff 701 is classified into the following categories: "Initial registration completed," "Resend registration completed," "Completed normally," "Defective call completed," "Withdrawal request made," and "90 days passed." The initial inspection staff 702 has "Waiting for initial inspection," "Request for creation of defect letter," and "Waiting for defect call." The re-inspection staff 703 has "Waiting for re-inspection," "Re-re-inspection," and "Waiting for re-inspection of defects." "Re-re-inspection" is the number of requests for documents that have been inspected once and are scheduled to be inspected again. The completed 704 has "Normally uploaded," "Defect letter uploaded," and "Withdrawn."

[0075] As shown in Fig. 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 passed. The display control unit 134 also updates and displays the number of currently registered requests after a predetermined number of days has passed. "After a certain period of time" means, for example, the passage of 24 hours. "The predetermined number of days" means, for example, the passage of 90 days.

[0076] 11, the display control unit 134 displays the total number of items for Branch A, Branch B, and Branch C stored in the secretariat information storage unit 122. The display control unit 134 also displays the statuses sorted by each person in charge.

[0077] Fig. 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 Fig. 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 a financial institution 705, an office 706, and a completed 707.

[0078] Financial institution 705 has "Correlation diagram uploaded" and "Denial notice 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," "Denial notice downloaded," "90 days passed," 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. "Denial notice downloaded" is the number of requests for which the financial institution terminal 10 has downloaded a delinquency notice received from the management device 100. In FIG. 12 , the display control unit 134 displays the number of branch A of the financial institution stored in the secretariat information storage unit 122.

[0079] 11 and 12, the financial institution terminal 10 that has made multiple requests and the management device 100 that executes the process of identifying heirs display user interfaces with different status classifications. The display control unit 134 displays different user interfaces with different classifications because the status classifications to be displayed differ between the management device 100 and the financial institution terminal 10. For example, the administrative office operating the management device 100 requests detailed information, such as the progress of the requests. In contrast, the financial institution operating the financial institution terminal 10 requests general information, such as the number of requests. For example, the status displayed on the financial institution terminal 10 as "Initial registration completed," "Resend registration completed," "Waiting for initial verification," "Waiting for re-verification," "Waiting for third verification," "Completed successfully," "Waiting for re-verification due to deficiency," "Request for creation of deficiency letter," "Waiting for call due to deficiency," and "Call due to deficiency completed" are displayed in the management device 100. In this way, the display control unit 134 changes the display of the user interface between the financial institution terminal 10 and the management device 100.

[0080] The display control unit 134 can change the number of status classification items displayed between the management device 100 and the financial institution terminal 10. For example, in Fig. 11, the number of items in the management device 100 is 15. In Fig. 12, the number of items in the financial institution terminal 10 is 7.

[0081] Furthermore, when the display control unit 134 receives a change to the screen display from the financial institution terminal 10, it can also display a user interface in accordance with the change. The display control unit 134 receives and displays a change on the financial institution terminal 10 to not display status categories that have been searched for less frequently than other statuses. The display control unit 134 also receives and displays a change on the financial institution terminal 10 to not display status categories that have been searched for less frequently than other statuses. In this way, the financial institution terminal 10 can, for example, not display statuses that have been searched for less frequently than other statuses, thereby allowing the user to concentrate on the required processing and improving business efficiency.

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

[0083] When the management device 100 is currently processing the 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, details of the request information will be described with reference to FIGS. 13 and 14. FIG. 13 is a diagram illustrating an example of a management screen for request information displayed by the display control unit 134 according to an embodiment. As shown in FIG. 13, when an arbitrary status is selected on a user interface that displays statuses, the display control unit 134 displays information about the request corresponding to the selected status. When an arbitrary status is selected, the display control unit 134 displays detailed information about the selected status. For example, when the status "Waiting for initial inspection" is selected, the display control unit 134 displays a list of requests for "Waiting for initial inspection." Furthermore, when the common management number of an arbitrary request is clicked from the list of requests, the display control unit 134 displays detailed application information.

[0085] 13, the display control unit 134 displays a selection screen 800 on the terminal screen of the secretariat operating the management device 100. The selection screen 800 has 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 a button for pressing the search button 806 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 a display when the status 803 is selected and the search button 806 is pressed. When the status 803 is selected to be, for example, a request with a status of "initial registration" and the search button 806 is pressed, the display control unit 134 displays a search result screen 800a.

[0087] The search result screen 800a displays requests that match the status selected on the selection screen 800, and includes a search result 807. In FIG. 13, the display control unit 134 displays the search result 807, indicating that the financial institution management number "B01" was assigned to the request with the common management number "A01." This request indicates that the management device 100 assigned the financial institution management number "B01" to the request with the common management number "A01." The request has an application date of "January 1, 2024" and an application deadline of "March 31, 2024." The management device 100 then classifies this request as having a status of "initial registration," which indicates that the request has been accepted. This status indicates that the status has continued for "1 day."

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

[0089] When pressed, the resend document upload button 901 transitions from the screen being viewed to a screen for uploading the document to be resent. When pressed, the file download button 902 transitions to a screen for downloading a file. When pressed, the withdraw button 903 transitions to a screen for withdrawing the request being viewed. When pressed, the data delete button 904 displays a screen for deleting the request being viewed. Request information details 905 is a screen that displays detailed information about the request. Update history 906 is a screen that displays which person updated the request processing. Note that the display control unit 134 does not limit the buttons displayed on the details screen to those described above, and can change whether or not a button is displayed depending on the authority.

[0090] The display control unit 134 displays a details screen for each request by pressing the common management number 801 on the selection screen 800 in FIG. 13 and displaying the details screen 900 in FIG. 14. For example, the display control unit 134 displays the same content as the search result 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. In this way, the management device 100 can assign a common management number to the request and sort the requests according to the status classification and update, making it possible to easily display 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. In addition, the output unit 135 outputs a notice to the financial institution terminal 10 or the user terminal 20, to which a reading code is attached that links the deficiency notice created by the creation unit 133 with the request.

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

[0093] 15, first, financial institution terminal 10 transmits application data to management device 100 (step S11). Management device 100 accepts the transmitted application data (step S12). If there is a defect in the application data, management device 100 creates a defect notice to notify the fact (step S13).

[0094] Management device 100 transmits the created deficiency notice to financial institution terminal 10 (step S14). Financial institution terminal 10, which has accepted the deficiency notice transmitted from management device 100, transmits the deficiency notice to user terminal 20 (step S15).

[0095] The user terminal 20, which has received the notice of deficiency sent from the financial institution terminal 10, sends the missing documents or the corrected documents as documents to be resent to the financial institution terminal 10 (step S16). The financial institution terminal 10, which has received the documents to be resent from the user terminal 20, sends the documents to be resent to the management device 100 (step S17).

[0096] The management device 100, which has received the resent document from the financial institution terminal 10, creates a family tree if there are no defects in the document (step S18). The management device 100 transmits the created family tree to the financial institution terminal 10 (step S19), and ends the process.

[0097] Next, the detailed procedure of the process shown in FIG. 15 will be described with reference to FIG. 16 and subsequent figures. FIG. 16 is a flowchart (1) showing the procedure of the status classification process according to the embodiment. As shown in FIG. 16, first, the management device 100 determines whether or not a request has been received from the financial institution terminal 10 (step S101). If a request has not been received (step S101; No), the management device 100 waits until a request is received. On the other hand, if a 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 there are any deficiencies in the documents (step S104). If there are any deficiencies in the documents (step S104; Yes), the management device 100 notifies the financial institution terminal 10 in writing or by phone that there are deficiencies in the documents (step S106). The management device 100 determines whether there is a reply from the financial institution (step S107). If there is no reply from the financial institution (step S107; No), the management device 100 waits until it receives a reply. On the other hand, if there is a reply from the financial institution (step S107; Yes), the management device 100 ends the process.

[0099] On the other hand, if there is no defect in the document (step S104; No), the management device 100 updates the status to "waiting for initial inspection" (step S105) and ends the process.

[0100] 17 is a flowchart (2) showing the procedure for the status classification process according to the embodiment. The management device 100 first determines whether there is a request for "waiting for initial inspection" (step S201). If there is no request for "waiting for initial inspection" (step S201; No), the management device 100 waits until a request for "waiting for initial inspection" arrives. On the other hand, if there is a request for "waiting for initial inspection" (step S201; Yes), the management device 100 determines whether there are any defects in the requested documents (step S202).

[0101] If the requested document has any deficiencies (step S202; Yes), the management device 100 requests the creation of a deficiency notice (step S204). When the management device 100 receives the request to create a deficiency notice, it creates the deficiency notice (step S205) and proceeds to step S301. On the other hand, if the requested document has no deficiencies (step S202; No), the management device 100 creates a family tree (step S203) and proceeds to step S401.

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

[0103] If there is an error in the deficiency statement (step S302; Yes), the management device 100 corrects the deficiency statement (step S303). After correction, the management device 100 returns the document to step S302 again to check whether there is an error in the deficiency statement. On the other hand, if there is no error in the deficiency statement (step S302; No), the management device 100 updates the status to "Waiting for re-inspection of deficiency" (step S304).

[0104] Thereafter, the management device 100 transmits a notice of deficiency to the financial institution terminal 10 (step S305). The management device 100 determines whether there are any documents to be resent from the financial institution terminal 10 (step S306). If there are no documents to be resent (step S306; No), the management device 100 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 there is a possibility that the resent documents that have been checked will be found to be defective again.

[0105] 19 is a flowchart (4) showing the procedure of the status classification process according to the embodiment. The management device 100 determines whether or not the created family tree has been accepted (step S401). If the created family tree has not been accepted (step S401; No), the management device 100 waits until it is accepted. On the other hand, if the created family tree has been accepted (step S401; Yes), the management device 100 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 correction, the management device 100 returns to step S402 and determines whether there is an error in the family tree. On the other hand, if there is no error in the family tree (step S402; No), the management device 100 transmits the family tree to the financial institution terminal 10 (step S404). Then, the management device 100 updates the status classification to "successful completion" (step S405).

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

[0108] If no notification of withdrawal of the request is received from the financial institution terminal 10 (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 passed" (step S504) and terminates the process.

[0109] On the other hand, if a request to withdraw the request is received from the financial institution terminal 10 (step S502; Yes), the status classification is updated to "withdrawal request made" (step S505), and the process ends.

[0110] (2. Modifications of the embodiment) (2-1. Management of multiple financial institutions) In the above embodiment, an example has been shown in which the management device 100 manages multiple requests. Here, the management device 100 may manage multiple financial institutions or multiple branches. Management of multiple financial institutions will be described using FIG. 21. FIG. 21 is a diagram illustrating a modified example of the management system 1 according to the embodiment. Descriptions that overlap with those described above will be omitted.

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

[0112] The management device 100 assigns financial institution management numbers to each of the multiple financial institution terminals 10, classifies the status of requests, and displays them on the screen, thereby making it easy to manage multiple financial institutions or branches.

[0113] In addition, in the first and second embodiments, it has been described that the management device 100 receives and manages requests from financial institutions. However, the management device 100 is not limited to financial institutions, and can also receive requests from a wide range of clients, including corporations such as companies and professionals, and individuals.

[0114] (3. Other embodiments) The processing according to the above-described embodiment may be implemented in various different forms other than the above embodiment.

[0115] 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 using a known method. Furthermore, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0116] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0117] Furthermore, the above-described embodiments and modifications can be combined as appropriate within the scope of not causing any contradiction in the processing content.

[0118] Furthermore, the effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0119] (4. Effects of the Management Device According to the Present Disclosure) As described above, the management device (management device 100 in the embodiment) according to the present disclosure includes 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 that are executed based on the multiple received requests by status indicating the progress of the processes. The display control unit displays the classified status.

[0120] In this way, the management device can easily manage multiple requests to identify heirs by classifying the status of the requests according to progress and displaying them on the screen. The management device can also easily manage multiple financial institutions.

[0121] Since the management device 100 and the financial institution share the same common management number, the management device 100 can easily display the progress of multiple requests by sorting requests by status classification and update. Also, since the management device 100 manages multiple requests by financial institution number, even if a progress confirmation email or the like is sent from the user or financial institution, the progress status can be immediately confirmed and communicated based on the financial institution number.

[0122] The management device also displays the number of currently registered requests for each status, allowing the management device to display the number of requests that must be processed and the number of requests being processed by each person in charge to be seen at a glance, making it easy to manage multiple requests.

[0123] Furthermore, when a desired status is selected on the user interface that displays the statuses, the management device displays information about the request corresponding to the selected status. This allows the management device to check the details screen of each request, making it easy to manage multiple requests.

[0124] The management device also displays a user interface with different status classifications for the first institution (in this embodiment, the financial institution terminal 10) that has made multiple requests and the second institution (in this embodiment, the management device 100) that executes the process of identifying the heirs. This allows the management device to appropriately change the status classifications required for the first institution and the second institution. The management device also makes it easier for each person in charge of processing requests at the second institution to process the requests by displaying the status classifications required. The management device also provides 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 questions about the progress from financial institutions and users by classifying the statuses by progress.

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

[0126] The management device (management device 100 in the embodiment) according to the present disclosure further includes a creation unit (creation unit 133 in the embodiment) and an output unit (output unit 135 in the embodiment). The creation unit creates a family tree corresponding to a request for which document processing has been completed among requests accepted from a first institution (financial institution terminal 10 in the embodiment), including a display indicating identified heirs. The output unit outputs the created family tree to the first institution (financial institution terminal 10 in the embodiment).

[0127] In this way, if the request received from the first institution contains no deficiencies in the documents, etc., the management device can create a family tree to identify the heirs, and provide the first institution with a family tree that allows the heirs to be easily identified.

[0128] In addition, if there is an deficiency in the requested documents received from a first institution (in this embodiment, the financial institution terminal 10), the management device creates a deficiency notice to inform the first institution of the deficiency, and outputs a notification to the first institution (in this embodiment, the financial institution terminal 10) with an attached reading code linking the created deficiency notice to the request.

[0129] The management device can easily manage multiple requests by linking the defect description and the request using the read code.

[0130] (5. Hardware Configuration) Information devices such as the management device 100 according to the above-described embodiment are realized by a computer 1000 having a configuration as shown in FIG. 22, for example. The management device 100 according to the embodiment will be described below as an example. FIG. 22 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, a RAM 1200, a ROM (Read Only Memory) 1300, an HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input / output interface 1600. The components of the computer 1000 are connected by a bus 1050.

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

[0132] The ROM 1300 stores boot programs such as a basic input output system (BIOS) executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000 .

[0133] HDD 1400 is a computer-readable recording medium that non-temporarily records programs executed by CPU 1100 and data used by such programs. Specifically, HDD 1400 is a recording medium that records a program that executes a calculation process according to the present disclosure, which is an example of program data 1450.

[0134] The communication interface 1500 is an interface for connecting the computer 1000 to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data generated by the CPU 1100 to other devices via the communication interface 1500.

[0135] 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 an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 also transmits data to an output device such as a display, a speaker, or a printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs and the like recorded on a predetermined recording medium. Examples of media include optical recording media such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disk), magneto-optical recording media such as an MO (Magneto-Optical disk), tape media, magnetic recording media, and semiconductor memories.

[0136] For example, when the computer 1000 functions as the management device 100 according to the embodiment, the CPU 1100 of the computer 1000 executes a management program loaded onto the RAM 1200, thereby realizing functions such as the control unit 130. The HDD 1400 stores a program for executing the management process according to the present disclosure and data in the storage unit 120. The CPU 1100 reads and executes program data 1450 from the HDD 1400, but as another example, the CPU 1100 may obtain these programs from another device via an external network 1550.

[0137] The above describes the embodiments of the present application in detail based on the drawings, but these are merely examples, and the present invention can be implemented in other forms that include the embodiments described in the Disclosure of the Invention section and that have been modified and improved in various ways based on the knowledge of those skilled in the art. [Explanation of symbols]

[0138] 1 Management System 10 Financial institution terminals 20 User terminal 100 Management device 110 Communications Department 120 Storage section 121 Application information storage unit 122 Secretariat Information Storage Department 130 Control Unit 131 Reception 132 Classification Department 133 Creation Department 134 Display control unit 135 Output section 300 Family register 400 Resent Documents 500 Family Tree 600 Letter of deficiency 700 User Interface 700a User Interface 800 Selection Screen 800a Search results screen 900 Details Screen

Claims

1. a reception unit that receives a plurality of requests for identifying heirs; a classification unit that classifies the processes for identifying heirs that are executed based on the received multiple requests by status indicating the progress of the processes; a display control unit that displays the classified status; A management device comprising:

2. The display control unit displaying the number of the plurality of requests currently registered for each of the statuses; The management device according to claim 1 .

3. The display control unit When an arbitrary status is selected on the user interface displaying the status, information on the request corresponding to the selected status is displayed. The management device according to claim 1 .

4. The display control unit The user interface is displayed with different status classifications for a first institution that has made the multiple requests and a second institution that executes a process to identify the heir.

4. The management device according to claim 3.

5. The display control unit When a change in the screen display is received from the first institution, a user interface is displayed in accordance with the change.

5. The management device according to claim 4.

6. a creation unit that creates a family tree corresponding to a request received from the first institution for which document processing has been completed, the family tree including an indication of identified heirs; an output unit that outputs the created family tree to the first institution; The management device according to claim 1 , further comprising:

7. a creating unit that creates a letter of deficiency to notify the first institution of the deficiency in the requested documents received from the first institution when the documents are deficiency; an output unit that outputs a notice to the first institution, to which a read code that links the created deficiency notice with the request is attached; The management device according to claim 1 , further comprising:

8. The computer We have received multiple requests aimed at identifying heirs, classifying the processes for identifying heirs that are executed based on the plurality of accepted requests into statuses that indicate the progress of the processes; Displaying the classified status. A management method comprising:

9. Computer, a reception unit that receives a plurality of requests for identifying heirs; a classification unit that classifies the processes for identifying heirs that are executed based on the received multiple requests by status indicating the progress of the processes; a display control unit that displays the classified status; A management program that causes the device to function as a management device comprising:

Images