Information processing system, information processing method, and information processing program

Abstract

To provide technology that can streamline and improve the efficiency of interactions between agent offices and financial institutions in debt consolidation work or overpayment refund claims work.SOLUTION: An information processing system comprises: an acceptance registration reception unit for accepting registration of acceptance information from a terminal of an agent office, wherein the acceptance information includes information on a debtor who has delegated the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as financial institutions from which the debtor has borrowed; an acceptance notification unit for issuing acceptance notifications to the one or more financial institutions identified by the acceptance information; and an acceptance content transmitting unit which, upon receiving a confirmation request for the acceptance notification from a terminal of the financial institution, transmits, to the terminal of the financial institution, acceptance content including information on the debtor who has declared the financial institution as a financial institution from which the debtor has borrowed, and information on the agent office delegated by the debtor.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing method, and an information processing program. [Background technology]

[0002] Currently, in debt consolidation work, the exchange of acceptance notices, claims reports, and transaction histories between law firms and financial institutions is mainly done on paper (by fax or mail), which is time-consuming and labor-intensive, and prone to human error.

[0003] Patent Document 1 proposes a real estate transaction support device that is connected to a financial institution's terminal and a judicial scrivener's terminal via a network. This device displays registration request information on the judicial scrivener's terminal, and upon receiving information from the judicial scrivener's terminal that the registration has been completed, notifies the financial institution's terminal that the registration request has been completed. However, this device does not mediate the exchange between the law firm and the financial institution in the debt consolidation business. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2023-72172 Summary of the Invention [Problem to be solved by the invention]

[0005] The present invention has been made in consideration of the above points, and its object is to provide a technology that can streamline and improve the efficiency of interactions between agent offices and financial institutions in debt consolidation services or overpayment refund services. [Means for solving the problem]

[0006] An information processing system according to a first aspect of the present invention includes: a registration reception unit that receives registration of entrusted information from a terminal of the agent office, the entrusted information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; an acceptance notification unit that issues acceptance notifications to one or more financial institutions identified by the acceptance information; an assignment content sending unit that, upon receiving a confirmation request for the assignment notice from the terminal of the financial institution, sends to the terminal of the financial institution assignment content including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; Equipped with.

[0007] According to this embodiment, when the agent office receives the registration of the mandate information from a terminal, the agent office automatically sends a notice of mandate to one or more financial institutions specified by the mandate information. This allows the sending of notices to multiple financial institutions to be consolidated and prevents human errors such as overlooking or mistaking the recipient. It also reduces postage costs and realizes a paperless system. This streamlines and streamlines the exchanges between the agent office and financial institutions in the debt consolidation business or the overpayment refund claim business.

[0008] An information processing system according to a second aspect of the present invention is the information processing system according to the first aspect, The acceptance notification unit displays information indicating that the acceptance notification has been received on a progress management screen displayed on the financial institution's terminal, or sends the acceptance notification to the financial institution's terminal by at least one of email, SMS, or SNS.

[0009] An information processing system according to a third aspect of the present invention is the information processing system according to the second aspect, The system further includes a progress management section that tallies the number of cases for which a predetermined period has passed since the acceptance notice was received without the acceptance content being confirmed, and highlights the number on the progress management screen.

[0010] According to this embodiment, it is possible to prompt the financial institution to confirm the contents of the contract, and it is possible to prevent a complaint from being filed with the Financial Services Agency due to a long period of neglecting to confirm the contents of the contract.

[0011] An information processing system according to a fourth aspect of the present invention is the information processing system according to the second or third aspect, The financial institution further includes a response registration reception unit that receives, from a terminal of the financial institution, registration of response information in response to the acceptance notice, the response information including information on the debtor, information indicating whether or not there is a transaction with the debtor, and information on the law firm or judicial scrivener's office entrusted by the debtor; The progress management unit tallies the number of cases for which the accepted content has been confirmed but for which the response information has not been registered, and further displays the number of cases on the progress management screen.

[0012] According to this aspect, the financial institution can easily grasp on the progress management screen the number of cases for which the contents of the contract have been confirmed but response information has not been registered.

[0013] An information processing system according to a fifth aspect of the present invention is the information processing system according to the fourth aspect, a claim notification and transaction history registration receiving unit for receiving registration of claim notification and transaction history information for the debtor from a terminal of the financial institution when there is a transaction with the debtor; The progress management unit tallies the number of cases for which the response information has been registered but for which the claim notification and transaction history have not been registered, and further displays the number of cases on the progress management screen.

[0014] According to this embodiment, financial institutions can easily grasp on the progress management screen the number of cases for which they have registered response information but have not yet registered the claims report and transaction history.

[0015] An information processing system according to a sixth aspect of the present invention is the information processing system according to the fifth aspect, a claim notification and transaction history response notification unit that sends a claim notification and transaction history response notification to the agent office identified by the response information; a claim and transaction history sending unit that, upon receiving a confirmation request for the claim and transaction history response notice from the terminal of the agent office, sends the claim and transaction history information of the financial institution for the debtor to the terminal of the agent office; Further provided are:

[0016] According to this embodiment, when a financial institution receives a registration of a claim notification and transaction history along with response information from its terminal, the system automatically sends a response notification of the claim notification and transaction history to the agent office identified by the response information, thereby preventing human error such as sending the wrong address. It also reduces postage costs and achieves a paperless system. This further streamlines and streamlines the exchanges between the agent office and financial institutions in debt consolidation or overpayment refund claims.

[0017] An information processing system according to a seventh aspect of the present invention is the information processing system according to the sixth aspect, The system further includes a second progress management unit that tallies the number of cases for which a predetermined period has passed since the receipt of the claim notification / transaction history response notice without the claim notification / transaction history information being confirmed, and highlights the number of cases on a second progress management screen displayed on the terminal of the agent seal office.

[0018] According to this embodiment, it is possible to prompt the agent office to check the claim notification and transaction history information.

[0019] An information processing method according to an eighth aspect of the present invention is an information processing method executed by a computer, A step of accepting registration of entrustment information from a terminal of the agent office, the entrustment information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; sending a notice of acceptance to one or more financial institutions identified by the acceptance information; a step of transmitting, upon receiving a confirmation request for the acceptance notice from the terminal of the financial institution, to the terminal of the financial institution, the acceptance details including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; Includes:

[0020] An information processing program according to a ninth aspect of the present invention comprises: A step of accepting registration of entrustment information from a terminal of the agent office, the entrustment information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; sending a notice of acceptance to one or more financial institutions identified by the acceptance information; a step of transmitting, upon receiving a confirmation request for the acceptance notice from the terminal of the financial institution, to the terminal of the financial institution, the acceptance details including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; to be executed by the computer. [Effects of the Invention]

[0021] According to the present invention, it is possible to rationalize and improve the efficiency of the exchanges between an agent office and a financial institution in the debt consolidation business or the business of claiming the return of excessive interest payments. [Brief explanation of the drawings]

[0022] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a system including an information processing system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating a schematic configuration of an information processing system according to an embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of information stored in the progress management database. [Figure 4] FIG. 4 is a diagram illustrating an example of the operation of the information processing system according to an embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 6] FIG. 6 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 7] FIG. 7 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 8] FIG. 8 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 9] FIG. 9 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 10] FIG. 10 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 11] FIG. 11 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 12] FIG. 12 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 13] FIG. 13 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 14] FIG. 14 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 15] FIG. 15 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 16] FIG. 16 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 17] FIG. 17 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 18] FIG. 18 is a diagram showing an example of a screen displayed on a terminal of a financial institution. [Figure 19] FIG. 19 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 20] FIG. 20 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 21] FIG. 21 is a diagram showing an example of a screen displayed on the terminal of the agent's office. [Figure 22] FIG. 22 is a diagram showing an example of a screen displayed on the terminal of the agent's office. DETAILED DESCRIPTION OF THE INVENTION

[0023] Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the drawings used in the following description, parts that may be configured identically will be designated by the same reference numerals, and duplicate explanations will be omitted. In this specification, an agent's office refers to an office staffed by lawyers or certified judicial scriveners who are capable of performing debt consolidation or overpayment refund claims, and may be, for example, a law firm or a judicial scrivener's office. In addition, a financial institution may be, for example, a money lender such as a consumer finance company, a credit card company, or a credit sales company. In this specification, a claim notification and transaction history refers to a claim notification and / or transaction history.

[0024] (Device configuration) FIG. 1 is a diagram showing the overall configuration of a system including an information processing system 2 according to one embodiment. As shown in FIG. 1, the information processing system 1 is communicably connected to terminals 3A-3C of one or more agent offices and terminals 4A-4C of one or more financial institutions via a network such as the Internet. The network may be either a wired line or a wireless line, and the type and form of the line are not important. At least a portion of the information processing system 1 is realized by one or more computers.

[0025] Fig. 2 is a diagram showing a schematic configuration of the information processing system 2. As shown in Fig. 2, the information processing system 2 has a communication unit 21, a control unit 22, and a storage unit 23. The units 21 to 23 are connected to each other via a bus or a network so as to be able to communicate with each other.

[0026] Of these, the communication unit 21 is a communication interface between the information processing system 2 and an external network. The communication unit 21 transmits and receives information between the information processing system 2 and the agent office terminals 3A to 3C and the financial institution terminals 4A to 4C via an external network such as the Internet.

[0027] The storage unit 23 is a non-volatile data storage such as a flash memory, a hard disk, etc. The storage unit 23 stores various data handled by the control unit 22. For example, the storage unit 23 includes a progress management database 23a.

[0028] FIG. 3 is a diagram illustrating an example of information stored in the progress management database 23a. As shown in FIG. 3, the progress management database 23a stores, for each case, information about the debtor, the agent office authorized by the debtor, information about one financial institution declared by the debtor as a lender, and the status of the case, all associated with each other along with the case number. The status indicates the progress of the interaction between the agent office and the financial institution, and may be, for example, one selected from the following: awaiting acceptance confirmation (from the financial institution), awaiting contract response (from the financial institution), completed (no transactions), awaiting claim notification and transaction history response (from the financial institution), awaiting confirmation of claim notification and transaction history (from the agent office), and a completed claim notification and transaction history response (from the agent office). As shown in FIG. 3, the progress management database 23a may further store, in association with each other, one or more pieces of information among the acceptance notification date, acceptance content confirmation date, contract response date, claim notification and transaction history response date, and claim notification and transaction history confirmation date.

[0029] Note that the memory unit 23 does not necessarily have to be physically located within the information processing system 2, and part or all of the memory unit 23 may be located within another device (e.g., cloud storage) that is communicatively connected to the information processing system 2 via an external network.

[0030] 2, the control unit 22 has an assignment registration reception unit 22a, an assignment notification unit 22b, an assignment content transmission unit 22c, a progress management unit 22d, a response registration reception unit 22e, a claim statement and transaction history registration reception unit 22f, a claim statement and transaction history response notification unit 22g, a claim statement and transaction history transmission unit 22h, and a second progress management unit 22i. Each of these units 22a to 22i may be realized by a processor in the information processing system 2 executing a predetermined program, or may be implemented in hardware.

[0031] The assignment registration reception unit 22a accepts the registration of assignment information from the agent's terminals 3A-3C. The assignment information may include information on the debtor who has entrusted the agent's debt consolidation or overpayment refund claim service to the agent's office and information on one or more financial institutions from which the debtor has declared creditors. For example, the assignment registration reception unit 22a may display an assignment registration screen (see FIG. 6) on the agent's terminals 3A-3C and acquire the debtor's information (such as name, maiden name, date of birth, address, former address, and heir's name) and financial institution information (such as financial institution membership code) entered on the assignment registration screen as the assignment information to be registered. The assignment information may further include one or more of the following: the date of assignment, the date of assignment notification, the agent's name, the case number within the agent's office, the response policy, and response request information.

[0032] When the assignment registration reception unit 22a accepts the registration of assignment information, it may associate the debtor's information, the agent's office information, and the financial institution information for each financial institution identified by the assignment information, and store them as a new case in the progress management database 23a.

[0033] When the assignment registration reception unit 22a accepts the registration of the assignment information, the assignment notification unit 22b sends an assignment notification to one or more financial institutions identified by the assignment information. As an example, the assignment notification unit 22b may display information indicating the receipt of the assignment notification on the progress management screen (see FIG. 9) displayed on the financial institution's terminals 4A to 4C (for example, by incrementing the value displayed in the "Assignment Contact Confirmation Required" box by 1). As another example, the assignment notification unit 22b may send the assignment notification to the financial institution's terminals 4A to 4C by at least one of email, short message (SMS), and social networking service (SNS), as shown in FIG. 12. When the assignment information registration is accepted from the agent's terminals 3A to 3C, the assignment notification unit 22b automatically sends an assignment notification to one or more financial institutions identified by the assignment information. This allows for the unification of notification transmission to multiple financial institutions and prevents human error, such as overlooking or mistaking a recipient.

[0034] When the acceptance notification unit 22b notifies the financial institution of the acceptance, it may change the status of the case stored in the progress management database 23a to "waiting for acceptance confirmation (from the financial institution)", or may store the date and time of the acceptance notification as the acceptance notification date of the case in the progress management database 23a.

[0035] When the assignment content transmission unit 22c receives a confirmation request for the assignment notice from the financial institution's terminal 4A-4C, it transmits to the financial institution's terminal 4A-4C the assignment content, including information on the debtor who declared the financial institution as a borrower and information on the agent office entrusted by the debtor. For example, referring to Fig. 10, when a list of cases for which an assignment notice has been received is displayed on the financial institution's terminal 4A-4C, and one case is selected and the "Intervention Information" button is clicked (or touched), the assignment content transmission unit 22c extracts the assignment content of the case from the progress management database 23a and transmits it to the financial institution's terminal 4A-4C for display, as shown in Fig. 11.

[0036] When the assignment content sending unit 22c sends the assignment content to the financial institution's terminal 4A to 4C, it may change the status of the case stored in the progress management database 23a to "waiting for contract response (from the financial institution)", or it may store the date and time when the assignment content was sent in the progress management database 23a as the assignment content confirmation date for the case.

[0037] The progress management unit 22d refers to the progress management database 23a, tallying the number of cases for which a predetermined period (e.g., two weeks) has passed since the acceptance notice was received without the acceptance content being confirmed (i.e., cases whose status is "awaiting acceptance confirmation" and whose acceptance notice date is more than two weeks ago), and highlights these cases on the progress management screen (see FIG. 9). Specifically, for example, referring to FIG. 9, the progress management unit 22d may highlight the number of cases ("11") for which a predetermined period has passed since the acceptance notice was received without the acceptance content being confirmed in a different color (or a larger size or a different font, etc.) in the "Acceptance Contact Confirmation Required" box, separately from the number of cases ("6") before that period has passed. Here, the "predetermined period" may be a period that can be set arbitrarily by the financial institution. By highlighting the number of cases for which a predetermined period (for example, two weeks) has passed since the acceptance notice was received without the acceptance details being confirmed, financial institutions can be urged to confirm the acceptance details, and this can prevent complaints from being filed with the Financial Services Agency due to the acceptance details being neglected for a long period of time.

[0038] The response registration acceptance unit 22e accepts the registration of response information in response to the assignment notice from the financial institution's terminals 4A to 4C. The response information may include information about the debtor, information indicating whether or not there is a transaction with the debtor, and information about the law firm or judicial scrivener's office entrusted by the debtor. For example, when the "No Transaction" button is clicked (or touched) while the assignment details are displayed on the financial institution's terminals 4A to 4C (see FIG. 11), the response registration acceptance unit 22e may display a screen (see FIG. 13) for inputting the details (classification) of the no transaction on the financial institution's terminals 4A to 4C, and acquire the details entered on the screen as the no-transaction response information. Also, for example, when the contract details are displayed on the agent's terminal 3A to 3C (see Figure 11) and the "Contract Registration" button is clicked (or touched), the response registration receiving unit 22e may display a screen (see Figure 15) on the financial institution's terminal 4A to 4C for inputting the details of the contract (transaction), and obtain the details entered on the screen as response information indicating that a transaction has occurred.

[0039] If the response information indicates that a transaction has occurred, the response registration receiving unit 22e may change the status of the case stored in the progress management database 23a to "waiting for a response to the claim report and transaction history (from the financial institution)," or may store the date and time when the registration of the response information is accepted as the contract response date of the case in the progress management database 23a. On the other hand, if the response information indicates that no transaction has occurred, the response registration receiving unit 22e may change the status of the case stored in the progress management database 23a to "completed (no transaction)."

[0040] The progress management unit 22d may refer to the progress management database 23a, and tally the number of cases for which the contents of the assignment have been confirmed but for which response information has not been registered (i.e., cases with a status of "awaiting contract response"), and further display this on the progress management screen (see FIG. 9). Specifically, for example, the progress management unit 22d may display the number of cases for which the contents of the assignment have been confirmed but for which response information has not been registered in a "contract response required" box displayed on the progress management screen (see FIG. 9). This allows the financial institution to easily grasp, on the progress management screen, the number of cases for which the contents of the assignment have been confirmed but for which response information has not been registered.

[0041] The progress management unit 22d may refer to the progress management database 23a, tally the number of cases for which a predetermined period (e.g., two weeks) has passed since the confirmation of the assignment contents without the registration of response information (i.e., cases whose status is "awaiting contract response" and whose assignment contents confirmation date is more than two weeks ago), and highlight these cases on the progress management screen (see FIG. 9). Specifically, for example, with reference to FIG. 9, the progress management unit 22d may highlight the number of cases ("4") for which a predetermined period has passed since the confirmation of the assignment contents without the registration of response information in a box for "contract response required" in a more conspicuous color (or in a larger size or a different font, etc.) than the number of cases ("9") for which the period has not yet passed. This can encourage financial institutions to register response information.

[0042] When there is a transaction with a debtor, the claim statement and transaction history registration acceptance unit 22f accepts the registration of claim statement and transaction history information for the debtor from the financial institution's terminals 4A to 4C. For example, when a list of contracts for the debtor is displayed on the financial institution's terminals 4A to 4C (see FIG. 17), and one contract is selected and the "Claim statement and transaction history registration" button is clicked (or touched), the response registration acceptance unit 22e may display a screen (see FIG. 18) for uploading an electronic file of claim statement and transaction history information on the financial institution's terminals 4A to 4C, and acquire the electronic file entered on that screen as the claim statement and transaction history information to be registered.

[0043] When the claim notification and transaction history registration reception unit 22f receives registration of claim notification and transaction history information from the financial institution's terminals 4A to 4C, it may change the status of the case stored in the progress management database 23a to "Waiting for confirmation of claim notification and transaction history (from the agent's office)", or may store the date and time when the registration of the claim notification and transaction history information is received as the claim notification and transaction history response date for the case in the progress management database 23a.

[0044] The progress management unit 22d may refer to the progress management database 23a, tally up the number of cases for which response information has been registered but for which claim notification and transaction history information has not been registered (i.e., cases with a status of "awaiting response to claim notification and transaction history"), and further display this on the progress management screen (see FIG. 9). Specifically, for example, the progress management unit 22d may display the number of cases for which response information has been registered but for which claim notification and transaction history information has not been registered in a "Claim notification response required" box displayed on the progress management screen (see FIG. 9). This allows financial institutions to easily grasp, on the progress management screen, the number of cases for which response information has been registered but for which claim notification and transaction history information has not been registered.

[0045] The progress management unit 22d may refer to the progress management database 23a, tally the number of cases for which a predetermined period (e.g., two weeks) has passed since the registration of response information without the registration of claim report and transaction history information (i.e., cases whose status is "Awaiting response to claim report and transaction history" and whose contract response date is more than two weeks ago), and highlight these cases on the progress management screen (see FIG. 9). Specifically, for example, referring to FIG. 9, the progress management unit 22d may highlight the number of cases ("13") for which a predetermined period has passed since the registration of response information without the registration of claim report and transaction history information in a more conspicuous color (or a larger size or a different font, etc.) in the "Claim report response required" box, separately from the number of cases ("2") for which the period has not yet passed. This can encourage financial institutions to register claim report and transaction history information.

[0046] The claim statement and transaction history response notifying unit 22g sends a claim statement and transaction history response notice to the agent office identified by the registered response information. As an example, the claim statement and transaction history response notifying unit 22g may display information indicating receipt of the claim statement and transaction history response notice (e.g., by incrementing the value of the "Claim Confirmation Required" box) on the second progress management screen (see FIG. 19) displayed on the agent office terminals 3A-3C. As another example, the claim statement and transaction history response notifying unit 22g may send the claim statement and transaction history response notice to the agent office terminals 3A-3C via at least one of email, short message (SMS), and social networking service (SNS). Upon receiving registration of claim statement and transaction history information from the financial institution's terminals 4A-4C, the claim statement and transaction history response notifying unit 22g automatically sends a claim statement and transaction history response notice to the agent office identified by the registered response information, thereby preventing human error, such as overlooking or misplacing the destination.

[0047] When the claim statement and transaction history transmission unit 22h receives a confirmation request for the claim statement and transaction history reply notice from the agent office terminal 3A-3C, it transmits the claim statement and transaction history information to the agent office terminal 3A-3C. For example, referring to FIG. 20, when a list of cases for which a claim statement and transaction history reply notice has been received is displayed on the agent office terminal 3A-3C, if a case is selected and the "Assigned Information" button is clicked (or touched), the claim statement and transaction history transmission unit 22h may transmit and display the assigned information for the selected case to the agent office terminal 3A-3C, as shown in FIG. 21. Then, when the "Download Claim Statement" button on the screen displaying the assigned information is clicked (or touched), the claim statement and transaction history transmission unit 22h may transmit and display a list of contracts (contracts with debtors of one financial institution) identified by the reply information registered for that case to the agent office terminal 3A-3C, as shown in FIG. 22. Next, when the download button for the "claim statement" or "transaction history" displayed for each contract is clicked (or touched), the claim statement / transaction history sending unit 22h may send the claim statement / transaction history information corresponding to the contract to the agent's office terminals 3A to 3C.

[0048] When the claim report and transaction history sending unit 22h sends the claim report and transaction history information to the agent office terminals 3A to 3C, it may change the status of the case stored in the progress management database 23a to "Claim report and transaction history response completed (from agent office)", or may store the date and time of sending the claim report and transaction history information in the progress management database 23a as the claim report and transaction history confirmation date for the case.

[0049] The second progress management unit 22i refers to the progress management database 23a, tallying the number of cases for which a predetermined period (e.g., two weeks) has passed since the receipt of a claim report and transaction history response notice without the claim report and transaction history information being verified (i.e., cases whose status is "Awaiting claim report and transaction history verification" and whose claim report and transaction history response date is more than two weeks ago), and highlights these cases on the second progress management screen (see FIG. 19). Specifically, for example, referring to FIG. 19, the second progress management unit 22i may highlight the number of cases ("16") for which a predetermined period has passed since the receipt of a claim report and transaction history response notice without the claim report and transaction history information being verified, in a more conspicuous color (or a larger size or a different font, etc.), in the "Claim Verification Required" box, separately from the number of cases ("8") before the period passed. Here, the "predetermined period" may be a period that can be set arbitrarily by the agent's office. By highlighting the number of cases for which a predetermined period (for example, two weeks) has passed since the receipt of the notification of claim and transaction history response without the confirmation of the claim and transaction history information, it is possible to urge the agent's office to confirm the claim and transaction history information, and to prevent complaints from being filed with the bar association or the judicial scrivener's association due to the failure to confirm the claim and transaction history information for a long period of time.

[0050] (Example of operation) Next, an example of the operation of the information processing system 2 will be described with reference to Fig. 4 to Fig. 21. Fig. 4 is a diagram for explaining an example of the operation of the information processing system 2. Figs. 5 to 21 are diagrams showing examples of screens displayed on terminals 3A to 3C of agent offices or terminals 4A to 4C of financial institutions.

[0051] As shown in Fig. 4, first, the mandate registration acceptance unit 22a accepts the registration of mandate information from the terminals 3A to 3C of the agent's office (step S10). For example, when the "mandate registration" button is clicked (or touched) on the menu screen (see Fig. 5) displayed on the terminals 3A to 3C of the agent's office, the mandate registration acceptance unit 22a transmits and displays the mandate registration screen (see Fig. 6) to the terminals 3A to 3C of the agent's office. Next, when the debtor's information (name, maiden name, date of birth, address, former address, heir's name, etc.) and financial institution information (financial institution membership code, etc.) are entered on the mandate registration screen, and then the "register" button is clicked (or touched), the mandate registration acceptance unit 22a acquires the entered information as the mandate information to be registered.

[0052] As a modified example, referring to Fig. 5, when the "Import File" button is clicked (or touched) on the menu screen displayed on the agent office terminals 3A to 3C, the mandate registration reception unit 22a may transmit and display a file import screen (see Fig. 7) to the agent office terminals 3A to 3C. Next, when a file created in advance is uploaded via the file import screen, the mandate registration reception unit 22a may acquire information on the debtors and financial institutions listed in the uploaded file as the mandate information to be registered.

[0053] When the assignment registration reception unit 22a accepts the registration of assignment information, it may associate the debtor's information, the agent's office information, and the financial institution information for each financial institution identified by the assignment information, and store them as a new case in the progress management database 23a.

[0054] Next, the assignment acceptance notification unit 22b sends an acceptance notification to one or more financial institutions identified by the assignment acceptance information (step S11). For example, when the "Progress Management" button is clicked (or touched) on a menu screen (see FIG. 8) displayed on the financial institution's terminal 4A-4C, the progress management unit 22d transmits and displays a progress management screen (see FIG. 9) on the financial institution's terminal 4A-4C. At this time, the assignment acceptance notification unit 22b displays information indicating that the assignment acceptance notification has been received on the progress management screen for the one or more financial institution's terminal 4A-4C identified by the assignment acceptance information (for example, by incrementing the value of the number displayed in the "Assignment Contact Confirmation Required" box by 1). Then, when the "Assignment Contact Confirmation Required" box is clicked (or touched) on the progress management screen (see FIG. 9), the assignment acceptance notification unit 22b displays a list of cases for which the assignment acceptance notification has been received, as shown in FIG. 10.

[0055] As a variant, referring to Figure 12, the acceptance notification unit 22b may send the acceptance notification to the terminals 4A to 4C of one or more financial institutions identified by the acceptance information by at least one of email, short message (SMS), and social networking service (SNS).

[0056] When the acceptance notification unit 22b notifies the financial institution of the acceptance, it may change the status of the case stored in the progress management database 23a to "waiting for acceptance confirmation (from the financial institution)", or may store the date and time of the acceptance notification as the acceptance notification date of the case in the progress management database 23a.

[0057] Next, when the assignment content transmission unit 22c receives a confirmation request for the assignment notice from the financial institution's terminal 4A-4C, it transmits to the financial institution's terminal 4A-4C the assignment content, including information on the debtor who declared the financial institution as a borrower and information on the agent office entrusted by the debtor (step S12). For example, referring to Fig. 10, when a list of cases for which an assignment notice has been received is displayed on the financial institution's terminal 4A-4C, and one case is selected and the "Intervention Information" button is clicked (or touched), the assignment content transmission unit 22c extracts the assignment content of the case from the progress management database 23a and transmits it to the financial institution's terminal 4A-4C for display, as shown in Fig. 11.

[0058] When the assignment content sending unit 22c sends the assignment content to the financial institution's terminal 4A-4C, it may change the status of the case stored in the progress management database 23a to "waiting for contract response (from the financial institution)," or may store the date and time when the assignment content was sent in the progress management database 23a as the assignment content confirmation date of the case. Furthermore, the progress management unit 22d may refer to the progress management database 23a, and tally up the number of cases for which a predetermined period (for example, two weeks) has passed since the acceptance notice was received without the assignment content being confirmed (i.e., cases whose status is "waiting for acceptance confirmation" and whose acceptance notice date is more than two weeks ago), and highlight the number of cases in a "requires acceptance contact confirmation" box on the progress management screen (see FIG. 9).

[0059] Next, the response registration acceptance unit 22e accepts the registration of response information to the acceptance notice from the financial institution's terminals 4A to 4C (step S13). For example, when the "No Transaction" button is clicked (or touched) while the acceptance details are displayed on the financial institution's terminals 4A to 4C (see FIG. 11), the response registration acceptance unit 22e displays a screen (see FIG. 13) for inputting the details (category) of the no transaction on the financial institution's terminals 4A to 4C, and acquires the content entered on the screen as the response information for no transaction. Also, for example, when the acceptance details are displayed on the agent's office's terminals 3A to 3C (see FIG. 11), and the "Register Contract" button is clicked (or touched), the response registration acceptance unit 22e displays a screen (see FIG. 15) for inputting the details of the contract (transaction) on the financial institution's terminals 4A to 4C, and acquires the content entered on the screen as the response information for transaction.

[0060] Next, the claim notification and transaction history registration receiving unit 22f determines whether or not the financial institution has had any transactions with the debtor based on the registered response information (step S14). If the response information indicates that there has been no transaction (step S14: NO), the response registration receiving unit 22e may change the status of the case stored in the progress management database 23a to "Completed (no transaction)."

[0061] On the other hand, if the response information indicates that a transaction has occurred (step S14: YES), the response registration receiving unit 22e may change the status of the case stored in the progress management database 23a to "waiting for response to claim report and transaction history (from financial institution)," or may store the date and time when the registration of the response information is accepted in the progress management database 23a as the contract response date of the case. Furthermore, the progress management unit 22d may refer to the progress management database 23a, and tally up the number of cases for which the accepted content has been confirmed but for which response information has not been registered (i.e., cases with the status "waiting for contract response"), and display this in the "contract response required" box on the progress management screen (see FIG. 9).

[0062] Next, if the reply information indicates that a transaction has occurred (step S14: YES), the claim statement / transaction history registration acceptance unit 22f accepts the registration of claim statement / transaction history information for the debtor from the financial institution's terminal 4A-4C (step S15). For example, when the "Contract List" button is clicked (or touched) while the assignment details are displayed on the agent's office terminal 3A-3C (see FIG. 16), the claim statement / transaction history registration acceptance unit 22e transmits and displays a list of contracts (contracts with the financial institution's debtor) identified by the reply information to the financial institution's terminal 4A-4C, as shown in FIG. 17. Next, when the "Claim Statement" or "Transaction History" upload button displayed for each contract is clicked (or touched), the reply registration acceptance unit 22e displays a screen (see FIG. 18) for uploading an electronic file of the claim statement / transaction history information on the financial institution's terminal 4A-4C, and acquires the electronic file entered on the screen as the claim statement / transaction history information to be registered.

[0063] When the claim statement and transaction history registration acceptance unit 22f accepts the registration of claim statement and transaction history information from the financial institution's terminals 4A to 4C, it may change the status of the case stored in the progress management database 23a to "Awaiting confirmation of claim statement and transaction history (from the agent's office)," or may store the date and time when the registration of claim statement and transaction history information is accepted as the claim statement and transaction history reply date for the case in the progress management database 23a. Furthermore, the progress management unit 22d may refer to the progress management database 23a and tally up the number of cases for which reply information has been registered but for which claim statement and transaction history information has not been registered (i.e., cases with the status "Awaiting reply to claim statement and transaction history"), and display this in the "Claim statement reply required" box on the progress management screen (see Figure 9).

[0064] Next, the claim form and transaction history response notifying unit 22g sends a claim form and transaction history response notice to the agent office identified by the registered response information (step S16). For example, when the "Progress Management" button is clicked (or touched) on the menu screen (see FIG. 5) displayed on the agent office terminal 3A-3C, the progress management unit 22d sends and displays the second progress management screen (see FIG. 19) on the agent office terminal 3A-3C. At this time, the claim form and transaction history response notifying unit 22g displays information indicating that the claim form and transaction history response notice has been received on the second progress management screen for the agent office terminal 3A-3C identified by the registered response information (for example, by incrementing the value displayed in the "Claim form confirmation required" box by 1). Then, when the "Claim form confirmation required" box is clicked (or touched) on the second progress management screen (see FIG. 19), the claim form and transaction history response notifying unit 22g displays a list of cases for which claim form and transaction history response notices have been received, as shown in FIG. 20.

[0065] As a variant, the claim statement / transaction history response notification unit 22g may send the claim statement / transaction history response notification to the agent office terminals 3A to 3C by at least one of email, short message (SMS), and social networking service (SNS).

[0066] Next, when the claim proof and transaction history transmission unit 22h receives a confirmation request for the claim proof and transaction history reply notice from the agent office terminal 3A-3C, it transmits the claim proof and transaction history information to the agent office terminal 3A-3C (step S17). For example, referring to FIG. 20, when a list of cases for which a claim proof and transaction history reply notice has been received is displayed on the agent office terminal 3A-3C, if a case is selected and the "Assigned Information" button is clicked (or touched), the claim proof and transaction history transmission unit 22h transmits and displays the assigned information for the selected case to the agent office terminal 3A-3C, as shown in FIG. 21. Then, when the "Download Claim Proof" button on the screen displaying the assigned information is clicked (or touched), the claim proof and transaction history transmission unit 22h transmits and displays a list of contracts (contracts with debtors of one financial institution) identified by the reply information registered for that case to the agent office terminal 3A-3C, as shown in FIG. 22. Next, when the download button for the "claim statement" or "transaction history" displayed for each contract is clicked (or touched), the claim statement / transaction history sending unit 22h sends the claim statement / transaction history information corresponding to the contract to the agent's office terminals 3A to 3C.

[0067] When the claim report and transaction history sending unit 22h sends the claim report and transaction history information to the agent office terminals 3A to 3C, it may change the status of the case stored in the progress management database 23a to "Claim report and transaction history response completed (from agent office)," or may store the date and time of sending the claim report and transaction history information in the progress management database 23a as the claim report and transaction history confirmation date of the case. Furthermore, the second progress management unit 22i may refer to the progress management database 23a and tally up the number of cases for which a predetermined period (e.g., two weeks) has passed since the receipt of the claim report and transaction history response notice without the claim report and transaction history information being confirmed (i.e., cases whose status is "awaiting claim report and transaction history confirmation" and whose claim report and transaction history response date is more than two weeks ago), and highlight these cases in a "Claim report confirmation required" box on the second progress management screen (see FIG. 19).

[0068] According to the above-described embodiment, when the agent office receives registration of assignment information from terminals 3A-3C, it automatically sends an assignment notification to one or more financial institutions identified by the assignment information. This allows for the consolidation of notification to multiple financial institutions and prevents human error, such as overlooking or mistaking a recipient. It also reduces postage costs and achieves a paperless system. This streamlines and streamlines communication between the agent office and financial institutions in debt consolidation or overpayment refund claims.

[0069] Furthermore, according to this embodiment, the progress management unit 22d tallies the number of cases for which a predetermined period of time has passed since the acceptance notice was received without the acceptance content being confirmed, and highlights the number of cases on the progress management screen displayed on the financial institution's terminals 4A to 4C, thereby urging the financial institution to confirm the acceptance content and preventing a complaint from being filed with the Financial Services Agency due to a long period of neglecting to confirm the acceptance content.

[0070] Furthermore, according to this embodiment, when a claim notification and transaction history registration is received from a financial institution's terminal 4A-4C along with response information to the acceptance notice, the claim notification and transaction history response notice is automatically sent to the agent office identified by the response information, thereby preventing human error such as sending the wrong address. This also reduces postage costs and realizes a paperless system. This further streamlines and streamlines the exchanges between the agent office and financial institutions in debt consolidation operations or overpayment refund claims operations.

[0071] It should be noted that the above description of the embodiment and the disclosure of the drawings are merely examples for explaining the invention described in the claims, and the invention described in the claims is not limited by the description of the embodiment or the disclosure of the drawings. The components of the above embodiment can be combined in any manner without departing from the spirit of the invention.

[0072] Furthermore, the information processing system 2 according to the above-described embodiment may be configured by one or more computers, but the program for realizing the information processing system 2 on one or more computers and the computer-readable recording medium on which the program is non-transitory are also protected by this case. [Explanation of symbols]

[0073] 2. Information Processing Systems 21 Communications Department 22 Control Unit 22a Registration Reception Department 22b Notice of Appointment 22c Assignment Contents Transmission Department 22d Progress Management Department 22e Response Registration Reception Department 22f Claim Notification and Transaction History Registration Reception Department 22g Claim Notification and Transaction History Response Notification Section 22h Claim Notification and Transaction History Transmission Department 22i 2nd Progress Management Department 23 Memory section 23a Progress Management Database 3A~3C Agent's office terminal 4A~4C Financial institution terminals

Claims

1. a registration reception unit that receives registration of entrusted information from a terminal of the agent office, the entrusted information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; an acceptance notification unit that issues acceptance notifications to one or more financial institutions identified by the acceptance information; an assignment content sending unit that, upon receiving a confirmation request for the assignment notice from the terminal of the financial institution, sends to the terminal of the financial institution assignment content including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; An information processing system comprising:

2. The acceptance notification unit displays information indicating that the acceptance notification has been received on a progress management screen displayed on the terminal of the financial institution, or sends the acceptance notification to the terminal of the financial institution by at least one of email, SMS, and SNS. The information processing system according to claim 1 .

3. The system further includes a progress management unit that tallies the number of cases for which a predetermined period has passed since the acceptance notice was received without confirmation of the acceptance content, and highlights the number of cases on the progress management screen. The information processing system according to claim 2 .

4. The financial institution further includes a response registration reception unit that receives, from a terminal of the financial institution, registration of response information in response to the acceptance notice, the response information including information on the debtor, information indicating whether or not there is a transaction with the debtor, and information on the law firm or judicial scrivener's office entrusted by the debtor; the progress management unit counts the number of cases for which the accepted content has been confirmed but for which the response information has not been registered, and further displays the number of cases on the progress management screen. The information processing system according to claim 3 .

5. a claim statement and transaction history registration reception unit that receives registration of claim statement and transaction history information for the debtor from a terminal of the financial institution when a transaction with the debtor has occurred; the progress management unit tallies the number of cases for which the response information has been registered but for which the claim notification and transaction history have not been registered, and further displays the number of cases on the progress management screen. The information processing system according to claim 4 .

6. a claim / transaction history response notifying unit that sends a claim / transaction history response notification to the agent office identified by the response information; a claim statement and transaction history sending unit that, upon receiving a confirmation request for the claim statement and transaction history response notice from the terminal of the agent office, sends the financial institution's claim statement and transaction history information for the debtor to the terminal of the agent office; The information processing system according to claim 5 , further comprising:

7. The system further comprises a second progress management unit that tallies the number of cases for which a predetermined period has passed since the receipt of the claim notification and transaction history response notice without confirmation of the claim notification and transaction history information, and highlights the number of cases on a second progress management screen displayed on the terminal of the agent seal office. The information processing system according to claim 6.

8. 1. A computer-implemented information processing method, comprising: a step of accepting registration of entrustment information from a terminal of the agent office, the entrustment information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; sending a notice of acceptance to one or more financial institutions identified by the acceptance information; a step of transmitting, upon receiving a confirmation request for the acceptance notice from the terminal of the financial institution, to the terminal of the financial institution, the acceptance details including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; An information processing method including:

9. a step of accepting registration of entrustment information from a terminal of the agent office, the entrustment information including information on debtors who have entrusted the agent office with debt consolidation work or overpayment refund claims work, and information on one or more financial institutions that the debtor has declared as lenders; sending a notice of acceptance to one or more financial institutions identified by the acceptance information; a step of transmitting, upon receiving a confirmation request for the acceptance notice from the terminal of the financial institution, to the terminal of the financial institution, the acceptance details including information on the debtor who declared the financial institution as a borrower and information on the agent office delegated by the debtor; An information processing program that causes a computer to execute the above.

Images