JP2019219739A - Debt customer management system, debt customer management method, and debt customer management program - Google Patents

Abstract

To provide a debt customer management system, debt customer management method, debt customer management program that can upgrade operation efficiency pertaining to debt-workout.SOLUTION: A debt customer management system 1 according to an embodiment is the debt customer management system in which a user terminal (any of respective terminals 31 to 35), a cloud service system 10 and an internet banking system 22 are connected via a communication network 40. The cloud service system 10 comprises: a storage unit 12 that stores information to be provided to the user terminal for each debtor; means that receives money-received information indicative of a money-received amount for each debtor credited to a proxy account for each debtor from the internet banking system 22; means that reflects the money-received information on the information for each debtor stored by the storage unit 12; and means that transmits remittance information indicative of a remittance amount for each creditor to be remitted from the proxy account for each creditor pertaining to the debtor to the internet banking system 22.SELECTED DRAWING: Figure 1

Description

  Embodiments of the present invention relate to a debt customer management system, a debt customer management method, and a debt customer management program.

  Attorneys' offices where lawyers and judicial scriveners work (eg, lawyers' offices and judicial scriveners' offices) deal with debt consolidation cases. In order to deal with this debt consolidation case, it is necessary to manage the debtor who is a debt customer (various information relating to debt consolidation), but it requires more specialized knowledge and operations than other business types. In particular, due to the nature of the task of performing special tasks, task processing is complicated, and it is difficult to secure physical personnel to handle the work load. I have.

  As one of the operations related to the above-mentioned debt consolidation case, for example, there is a payment agency business (agent remittance) for remittance of a deposit from a debtor to a creditor. Unlike the manufacturing and general service industries, lawyers and judicial scriveners have distinctive remunerations and income structures, such as professional remuneration and postpaid success fees. You. For this reason, the payment agency business in a professional office is operated by a limited number of people, and the business efficiency related to debt consolidation is reduced. Therefore, the business efficiency is required to be improved.

JP 2003-67583 A JP 2011-2941 A

  An object of the present invention is to provide a debt customer management system, a debt customer management method, and a debt customer management program that can improve the operational efficiency related to debt consolidation.

  A debt customer management system according to an embodiment of the present invention is a debt customer management system in which a user terminal, a cloud service system, and an Internet banking system are connected via a communication network, and the cloud service system is provided to a user terminal. A storage unit for storing information on each debtor, a means for receiving deposit information indicating an amount of deposit for each debtor from the Internet banking system, and a debt stored by the storage unit. Means for reflecting the deposit information in the information for each creditor, and means for transmitting, to the Internet banking system, remittance information indicating the remittance amount for each creditor who transfers money from the proxy account for each creditor related to the debtor.

  The debt customer management method according to the embodiment of the present invention is directed to a debt customer management system in which a user terminal, a cloud service system, and an internet banking system are connected via a communication network, wherein the cloud service system includes information provided to the user terminal. Receiving, from the Internet banking system, deposit information indicating the deposit amount of each debtor deposited in the proxy account for each debtor, and the debtor stored by the storage unit. Reflecting the deposit information in the information of each creditor, and transmitting to the Internet banking system remittance information indicating the remittance amount of each creditor who transfers money from the proxy account for each creditor of the debtor.

  A debt customer management program according to an embodiment of the present invention provides a debt customer management system in which a user terminal, a cloud service system, and an internet banking system are connected via a communication network. Receiving payment information indicating the amount of deposit for each debtor deposited in the proxy account for each debtor, and depositing the information for each debtor stored in the storage unit provided in the cloud service system and provided to the user terminal Reflecting the information, and causing the Internet banking system to transmit remittance information indicating the remittance amount of each creditor who remits money from the proxy account for each creditor of the debtor.

  According to the embodiment of the present invention, it is possible to improve business efficiency related to debt consolidation.

It is a figure showing the schematic structure of the debt customer management system concerning an embodiment. It is a figure showing the function menu (function for the person in charge and processing person) concerning an embodiment. It is a figure showing the function menu (function for the person in charge of accounting) concerning an embodiment. FIG. 6 is a diagram illustrating a function menu (a function for an administrator) according to the embodiment. It is a figure showing a part of debt customer management information concerning an embodiment. It is a figure showing a part of debt customer management information concerning an embodiment. It is a flowchart which shows the business flow (1. acceptance) of the debt consolidation which concerns on embodiment. It is a flowchart which shows the business flow (2. preparation for settlement) of debt consolidation which concerns on embodiment. It is a flowchart which shows the business flow (3. settlement negotiation) of the debt consolidation which concerns on embodiment. It is a flowchart which shows the business flow (4. proxy remittance) of debt consolidation which concerns on embodiment. It is a flowchart which shows the business flow (5. settlement process) of debt consolidation which concerns on embodiment. It is a figure for explaining the flow of direct import of payment information by API cooperation concerning an embodiment. It is a figure for explaining the flow of indirect import of payment information by other than API cooperation concerning an embodiment. It is a figure showing the search screen before acceptance concerning an embodiment. It is a figure showing a part of new registration / edit screen concerning an embodiment. It is a figure showing a part of new registration / edit screen concerning an embodiment. It is a figure showing a part of case information creation screen after acceptance concerning an embodiment. It is a figure showing a part of case information creation screen after acceptance concerning an embodiment. It is a figure showing the top screen concerning an embodiment. It is a figure showing the case information screen concerning an embodiment. It is a figure showing the customer details screen (progress status page) concerning an embodiment. It is a figure showing the client information page concerning an embodiment. It is a figure showing the creditor information page concerning an embodiment. It is a figure showing the borrower creditor detail page concerning an embodiment. It is a figure showing the document creation information page concerning an embodiment. It is a figure showing the division payment information page concerning an embodiment. It is a figure showing the account information page concerning an embodiment. It is a figure showing the payment information page concerning an embodiment. It is a figure showing the creditor information screen concerning an embodiment. It is a figure showing the account management screen concerning an embodiment. It is a figure showing the payment management screen concerning an embodiment. It is a figure showing the payment management screen concerning an embodiment. It is a figure showing the bank payment processing screen concerning an embodiment. It is a figure showing the bank payment processing screen concerning an embodiment.

<One embodiment>
A debt customer management system according to one embodiment will be described with reference to the drawings. The debt customer management system is, for example, a system introduced by a lawyer's office or a judicial scrivener office to manage debtors who are debt customers (various information related to debt consolidation).

<Basic configuration>
As shown in FIG. 1, the debt customer management system 1 according to the embodiment includes a cloud service system 10, an external cooperation service system 20, and an office system 30. The cloud service system 10, the external cooperation service system 20, and the office system 30 are communicably connected to each other via a communication network 40 such as a WAN (Wide Area Network). As the communication network 40, for example, a computer network such as the Internet is used.

  The cloud service system 10 has a processing unit 11 and a storage unit 12. The cloud service system 10 is a system that provides software related to debt customer management (for example, cloud application software). The cloud is an abbreviation of cloud computing, and is a usage form in which computer resources are provided as a service via a computer network. As the cloud service system 10, for example, a SaaS (Software as a Service) system is used. The cloud service system 10 is configured to enable API (Application Programming Interface) cooperation with the external cooperation service system 20 via the communication network 40.

  The processing unit 11 executes various processes based on software related to debt customer management. The processing unit 11 performs processing related to debt customer management (for example, creation and update of various information) for managing various information related to debt consolidation in accordance with an instruction from the office system 30. Necessary information is acquired from the external cooperation service system 20, and processing related to debt customer management is performed using the acquired information. As the processing unit 11, for example, a CPU (Central Processing Unit) or the like is used.

  The storage unit 12 stores various information related to debt consolidation (eg, debtor information, debtor account information, case information, creditor information, debt information, negotiation record information, settlement information, trial progress information, trial expense information, remittance information , Etc.), and various software such as software related to debt customer management. As the storage unit 12, for example, a storage such as a hard disk drive (HDD) or a solid state drive (SSD) is used.

  The external cooperation service system 20 has a call center system 21 and an Internet banking system 22. The call center system 21 and the Internet banking system 22 are external systems, and are configured to be able to perform API cooperation with the cloud service system 10 via the communication network 40.

  The call center system 21 is a cloud-type call center, and provides a CTI (Computer Telephony Integration) service that integrates a computer and a telephone. The call center system 21 transmits information such as a telephone number (or customer information) to the cloud service system 10 by API cooperation with the cloud service system 10.

  The Internet banking system 22 is a service provided by various banks, and provides various services such as balance inquiry, deposit / withdrawal account inquiry, and remittance (transfer). The Internet banking system 22 receives transaction information (for example, deposit and withdrawal information) related to a bank account (proxy account) of an office that is a customer of the bank in response to access (for example, information request and the like) of the cloud service system 10. Is transmitted to the cloud service system 10 through API cooperation, or is output (transmitted) to the office system 30 as CSV (Comma Separated Value: comma-separated value) data in response to access from the office system 30. The cloud service system 10 is given a right to access a specific bank account in the Internet banking system 22 by the Internet banking system 22 in advance.

  The office system 30 has an acceptance terminal 31, a teacher terminal 32, a processing terminal 33, an accounting terminal 34, and a management terminal 35. The assignment terminal 31 is a terminal used by the staff in charge, the teacher terminal 32 is a terminal used by a teacher in the profession, and the processing terminal 33 is a terminal used by the staff in charge. The accounting terminal 34 is a terminal used by the accountant, and the management terminal 35 is a terminal used by the administrator. These terminals 31 to 35 function as user terminals used by the user of the cloud service system 10.

  Each of the terminals 31 to 35 includes an input unit that receives an input operation of an operator, a display unit that displays information, a control unit that controls each unit, a storage unit that stores information (all are not shown), and the like. ing. As each of the terminals 31 to 35, for example, a desktop personal computer, a notebook personal computer, a portable information terminal, or the like is used. Examples of portable information terminals include tablet terminals and smartphone terminals. Further, for example, a keyboard and a mouse are used as an input unit, a liquid crystal display or an organic EL (Electro Luminescence) display is used as a display unit, a CPU is used as a control unit, and a hard disk drive (HDD) or a solid state drive (SSD) is used as a storage unit. Storage is used.

  In the above-described office system 30, terminals are provided for tasks such as commissioned tasks, processing tasks, accounting tasks, management tasks, and the like. However, the present invention is not limited to this. The commissioning terminal 31 and the processing terminal 33 can be one common terminal. Further, the processing terminal 33 and the accounting terminal 34 can be used as one common terminal, and the teacher terminal 32 and the management terminal 35 can be used as one common terminal, and the number can be appropriately adjusted.

<Cloud service system>
Next, the above-described cloud service system 10 will be described. The cloud service system 10 provides various information and various software (application software) to the office system 30. The processing unit 11 of the cloud service system 10 implements various processes based on software according to a user's input operation on each of the terminals 31 to 35 of the office system 30 to realize various functions (means).

  As shown in FIG. 2 to FIG. 4, the function menu of the application software provided by the cloud service system 10 includes “list of consultants / search”, “list / search before acceptance”, “list / search after acceptance”, “bank It is composed of "account cooperation", "account deposit / withdrawal management", "form batch output instruction", and "master management". In the login, the user operates the user terminal, inputs a user ID and a password, and logs in to the cloud service system 10.

(Functions for staff in charge and processing)
As shown in FIG. 2, the "function for the person in charge / processing" in the function menu includes "list of consultants / search", "list / search before acceptance", and "list / search after acceptance" (FIG. 2). (See the unfilled frame inside.) These various functions are intended for use by a person in charge and accounting (accounting and accounting group).

  Customer management is performed on a case-by-case basis for each consultant (obligor). The pre-acceptance information management is a function for managing information before the acceptance, and manages information such as a correspondence history, a hearing sheet output (information), and a handover after the acceptance. The post-acquisition information management is a function for managing information after the acceptance, for example, information such as client account information, conversation history, document creation (information), deposit / withdrawal information, litigation information, creditor list (information). to manage. The list of creditors (information) includes details of creditors, for example, borrowing status, arrangement information, negotiation history, and the like. The file management is a function for performing file management related to business.

  Usually, a consultant (debt borrower) consults about debts by telephone or e-mail. In this case, the receptionist in charge operates the reception terminal 31 and inputs the consultant information (for example, basic consultant information) about the consultant. The input consultant information is automatically stored in the storage unit 12 of the cloud service system 10. In recent years, the number of consultants who click on advertisements on web pages and consult from LPs (landing pages) has increased. In this case, when the consultant inputs necessary information to the LP, the consultant information input to the LP is automatically stored in the storage unit 12 of the cloud service system 10 in cooperation with the LP and the cloud service system 10. Is stored. This eliminates the necessity for the commissioned person to input the counselor information by himself, thereby improving work efficiency.

  When the consultant is not a new customer (when the consultant information is stored in the storage unit 12), the cloud service system 10 performs API cooperation with the call center system 21 in response to a call from the consultant. Then, the telephone number (or customer information) of the consultant is obtained from the call center system 21. Then, the cloud service system 10 searches for consultant information that matches the acquired telephone number (or customer information), and automatically displays the matched consultant information on the display unit of the commissioned terminal 31. This automatically displays the consultant information about the caller who called, and eliminates the need for the person in charge to check the consultant's name, address, etc. and read out the consultant information, improving work efficiency Can be done.

(Function for accounting staff)
As shown in FIG. 3, the “function for accounting staff” in the function menu includes “bank account cooperation” and “account deposit / withdrawal management” relating to the bank account (proxy account) of the office (filled in FIG. 3). None). The “bank account linkage” includes “accepting deposits” and “reflecting withdrawals”. The “account management” includes “account list / search”, “payment list / search”, and “payment list / search”. These various functions are assumed to be used by an accountant (accounting group), and include, for example, an API link function and a CSV output function.

(Administrator function)
As shown in FIG. 4, the "function for manager" in the function menu includes "form batch output instruction" and "master management" (see a box without filling in FIG. 4). As the “form batch output instruction”, there are “number of totals before acceptance CSV”, “number of totals after acceptance CSV”, and “summary result total CSV” (CSV output function). The “master management” includes “various master management”, “account management”, and “template registration”. These various functions are intended for use by a manager (for example, an office manager or a consultant).

  As described above, the cloud service system 10 is provided with various functions. However, the present invention is not limited to this. For example, the cloud service system 10 may be provided with a “client function” or a “remote defense function”. Is also possible. The “function for client” includes “confirmation of progress” and “simplified message transmission”. The client is a former counselor, and the counselor is treated as a client when he requests the office to arrange debts.

  In the function for the client, for example, an SMS (short message service) exchange is performed through software of the cloud service system 10. As an entire system, for example, a client system is constructed separately from the cloud service system 10, and a client terminal (for example, a desktop personal computer, a notebook personal computer, a portable information terminal, etc.) of the client and the cloud service system 10 (For example, data transmission / reception). In the remote defense function, for example, a professional teacher responds to a consultation of a client who is located in a remote place by cooperation between the client terminal and the cloud service system 10.

<Debt customer management information>
Next, an example of debt customer management information will be described.

  As shown in FIGS. 5 and 6, debt customer management information includes, for example, case information, client information, dialogue record (information), client account information, borrower creditor details (information), and negotiation record (information). , Settlement information, payment information, payment information, and the like. These pieces of information are associated with each other and managed on a case-by-case basis for each client (obligor). Debt customer management information is information that is stored in the storage unit 12 of the cloud service system 10 and that can be accessed by user terminals (for example, each of the terminals 31 to 35) permitted by the cloud service system 10. Note that the various types of information shown in FIGS. 5 and 6 are merely examples, and the present invention is not limited thereto.

  As shown in FIG. 5, the case information is information relating to a debt consolidation case, and includes, for example, information such as a case name, a case acceptance date, a trust status, a trustee, a lawyer in charge, a clerk in charge, a completion date, and remarks. In.

  The client information (obligor information) is information on the client, for example, last name (including kana), first name (including kana), old name, fixed telephone, mobile phone, FAX, Email, date of birth, Includes information such as gender, occupation, income, residence, zip code, address, permanent zip code, permanent address, old zip code, old address, family secret, contact means, contact means supplement, mail means, mail means supplement, remarks, etc. In.

  The conversation record (information) is information relating to the record of the conversation with the requester, and includes, for example, information such as the date and time of the conversation, the person in charge, the means of conversation, the contact direction, and the contents of the conversation.

  The client account information (obligor account information) is information related to the client account, and includes, for example, a financial institution name, a store name, an account type, an account number, an account name, a virtual account number, a monthly deposit amount, a first deposit date, It contains information such as the date of payment.

  As shown in FIG. 6, the borrower details (information) are information on the creditor and the debt. For example, the creditor, progress, borrowing start date, initial borrowing amount, monthly repayment amount, contracted debt balance, It contains information such as the balance of the direct debt, the member number, the contract number, the date of sending the notification of acceptance, the date of receiving the statement, the date of sending the settlement proposal, and remarks.

  The negotiation record (information) is information on the negotiation record with the creditor, and includes, for example, information such as the date and time of the conversation, the person in charge, the outline of the negotiation, the communicator, the means of conversation, the contact direction, and the details of the negotiation.

  Settlement information is information about the settlement with the creditor, for example, settlement status, settlement settlement date, settlement amount, repayment / overpayment method, repayment agency, number of payments, first repayment date, first repayment amount, second repayment date, From the second time to the repayment amount, etc. are included.

  The deposit information (deposit history information) is information relating to deposit, and includes, for example, a deposit source type, a deposit type, a deposit source name, a scheduled deposit date, a scheduled deposit amount, a deposit actual date, a deposit amount (deposit amount), remarks, and the like. Contains information.

  The dispensing information (dispensing history information) is information relating to dispensing, and includes, for example, dispensing source type, dispensing type, dispensing destination name, scheduled disbursement date, scheduled disbursement amount, actual dispensing date, and dispensing date. It contains information such as the amount of money (withdrawal amount) and remarks.

<Business flow>
Next, an example of a business flow for debt consolidation in the debt customer management system 1 will be described. The business flow of this debt consolidation is “1. Acceptance (see FIG. 7)”, “2. Preparation for Reconciliation (see FIG. 8)”, “3. Negotiation for Reconciliation (see FIG. 9)”, “4. 10) "and" 5. Settlement process (see FIG. 11) ".

(1. Acceptance)
As shown in FIG. 7, the commissioned person accepts a new consultation from a consultant (obligor) by telephone or email (step S1), and operates the input unit of the commissioned terminal 31 in the office system 30 to make a telephone call or a call. Information such as a name is input (step S2), hearing and counseling is performed (step S3), and consultation information is input or updated by operating the input unit of the commissioned terminal 31 (step S4).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to input or update of consultant information to the commissioned terminal 31 in response to the input operation of the commissioned person on the commissioned terminal 31. Then, the consultant information input or updated by the commissioned terminal 31 is stored in the storage unit 12. In inputting (or updating) the consultant information, for example, "list of consultants: basic consultant", "list of consultants: details", "list of consultants: income and expenditure", "list of consultants: borrowing status" Information and functions related to the “consultant list: response policy / important matters”, “consultant list: required hearing items”, “consultant list: response / escalation history”, etc. are provided to the commissioned terminal 31, and Corresponding information is entered by the person in charge.

  The person in charge determines whether or not temporary acceptance is performed (step S5), and if it is determined that temporary acceptance is not to be performed (NO in step S5), re-following is performed or the operation is stopped (end). . On the other hand, if it is determined that a temporary assignment is to be made (YES in step S5), the person in charge confirms the interview (step S6). The input section of the terminal 31 is operated to input or update the consultant information (step S7).

  As described above, the processing unit 11 of the cloud service system 10 accepts information and functions (for example, various screens and function menus) related to input or update of the consultant information in accordance with the input operation of the assigned terminal 31 by the assigned person. Provided to the terminal 31, for example, the consultant information input or updated by the commissioned terminal 31 is stored in the storage unit 12. Also in the input (or update) of the consultant information, the information is input by the person in charge, as described above.

  Thereafter, the person in charge receives the document (for example, a commission contract) (step S8), receives a written communication (for example, a notification of a document entry method) (step S9), and confirms the return of the document. (Step S10). If the return has not arrived, the person in charge will contact you again. On the other hand, if the return has arrived, the document is checked (step S11), and a document sending list such as sent or unsent is created (step S12). If the documents are incomplete, the consultant is contacted. If there is no incompleteness, the teacher performs identity verification (interview) by telephone interview (step S13).

  On the other hand, if the interview requested by the consultant is the visit interview in step S6, the teacher performs identity verification (interview) through the visit interview (step S13). After the interview (after the telephone interview or the visit to the office), the teacher determines whether or not to be accepted (step S14). In addition, the teacher operates the teacher terminal 32 in the telephone interview, retrieves the consultant information corresponding to the consultant who came to the interview from the storage unit 12 of the cloud service system 10, and displays the information on the display unit of the teacher terminal 32. The user can see and confirm the displayed consultant information. As a result, the teacher can easily obtain necessary information, so that work efficiency can be improved.

  Thereafter, if the teacher decides not to accept the assignment (NG in step S14), the assignment manager determines the possibility of the assignment (step S15), and if there is no possibility of the assignment, the assignment task is stopped. Yes (end). On the other hand, if the teacher determines that the assignment is accepted (OK in step S14), the processing staff operates the input unit of the processing terminal 33 in the office system 30 to input or update the assignment information (step S16). When the teacher decides to be accepted, the clerk or the like is instructed to send out documents (for example, a commission contract) as necessary, such as not receiving required documents (step S17).

  The processing unit 11 of the cloud service system 10 provides the processing terminal 33 with information and functions (for example, various screens and function menus) related to the input or update of the acceptance information in response to the input operation of the processing person on the processing terminal 33. Then, the acceptance information input or updated by the processing terminal 33 is stored in the storage unit 12. In the input (or update) of the acceptance information, for example, "list of consultants: basic consultant", "list of consultants: response / escalation history", "case information: basic information", "case information: client information" , Information and functions related to “case information: creditor information” and the like are provided to the processing terminal 33, and information corresponding thereto is input by the processor. A part of the commission information (for example, client information) is inherited from the consultant information.

  The accountant operates the input unit of the accounting terminal 34 in the office system 30 to input or update the acceptance information as necessary, for example, when inputting or updating information related to accounting (step S18).

  The processing unit 11 of the cloud service system 10 provides the accounting terminal 34 with information and functions (for example, various screens and function menus) relating to the input or update of the acceptance information in response to the input operation of the accounting terminal 34 by the accountant. Then, the acceptance information input or updated by the accounting terminal 34 is stored in the storage unit 12. In the input (or update) of the acceptance information, for example, information and functions related to “case information: deposit / withdrawal information” and the like are provided to the accounting terminal 34, and information corresponding thereto is input by the accounting staff.

  The administrator operates the input unit of the management terminal 35 in the office system 30 and obtains various information related to debt client management as needed, for example, when searching for the cause of the failure to reach the temporary acceptance (step S1). S19). The various information is provided from the cloud service system 10 to the management terminal 35, and is displayed on the display unit of the management terminal 35. The administrator sees and confirms the information.

  The processing unit 11 of the cloud service system 10 provides the management terminal 35 with information and functions (for example, various screens and function menus) related to debt customer management in response to an input operation of the management terminal 35 by the administrator. Various kinds of information such as the number of consultation progress / daily / cumulative consultation, the number of provisional acceptances / rate, and the number / rate of actual acceptances are read from the unit 12 and transmitted to the management terminal 35. Thereby, the manager can easily grasp various information related to the debt customer management, so that the work efficiency can be improved. Note that it is also possible to transfer the read information to a system managed separately.

(2. Preparation for settlement)
As shown in FIG. 8, the commissioned person operates the input unit of the commissioned terminal 31 in the office system 30 to perform supplementary update of the pre-acceptance information as necessary, such as when updating the information before commissioning (step S <b> 1). S21).

  At the start of the negotiation, the processing staff operates the input unit of the processing terminal 33 in the office system 30 to create an intervention notice (document) and stores it in the storage unit of the processing terminal 33 (step S22). Then, an intervention notice is sent and a transaction history is requested by fax or the like (step S23). The trader sends the transaction history to the office by facsimile, mail, mail or the like in response to a request from the office (step S24). The processing person receives the transaction history (information) from the trader, operates the input unit of the processing terminal 33 based on the received transaction history, performs a redrawing calculation (step S25), and further inputs the debt status or Update is performed (step S26).

  The processing unit 11 of the cloud service system 10 provides the processing terminal 33 with information and functions (for example, various screens and function menus) relating to the input and update of the debt status in response to the input operation of the processing person on the processing terminal 33. The debt status (information) input or updated by the processing terminal 33 is stored in the storage unit 12. In this debt status registration, for example, information and functions related to “Creditor information: Add borrower creditor”, “Creditor information: Borrower creditor details”, and “Creditor information: Negotiation record” are processed. The information is provided to the terminal 33, and the corresponding information is input by the processor.

  The accountant operates the input unit of the accounting terminal 34 in the office system 30 to start the deposit management (monthly loop until the remuneration is accumulated), and receives the deposit CSV (an example of the deposit information) from the Internet banking system 22. The payment information is acquired and taken into the cloud service system 10 (step S27), and the payment information displayed on the display unit of the accounting terminal 34 is checked based on the payment CSV to determine whether or not payment has been made (step S28).

  If the accountant determines that there is a deposit (YES in step S28), the accountant operates the input unit of the accounting terminal 34 to manage the deposit information (step S29). Negotiation is permitted (step S30). In addition, as a procedure of the remuneration amount appropriation including a plan, for example, first, a deposit is stored, and it is determined whether or not the person has a payment amount. After taking the start fee + the administrative fee = the amount received at the time of the commission, the reward = the amount received from the settlement, the accountant transfers the expenses from the deposit account.

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) related to the management of the payment information to the accounting terminal 34 in response to an input operation performed by the accountant on the accounting terminal 34. In the payment confirmation, for example, information and functions related to “bank payment processing”, “case information: account information”, “case information: payment / withdrawal information”, “payment management: payment information search”, and the like are provided to the accounting terminal 34. Is done.

  On the other hand, when it is determined that there is no payment (NO in step S28), the accountant performs a payment reminder operation for the client (step S31). In this payment dunning operation, the accounting clerk instructs the requester by telephone in the case of "1.1 times no payment", and in the case of "2.2 times no payment", issues a warning to the requester. If "3. No payment has been made even after two weeks have passed since the letter was sent", a notice of resignation notice will be sent. If "4. No payment has been made after one or two weeks have passed since the notice of resignation", a lawyer will be sent. Resignation with the permission of, and send a notice of resignation to the client or the company.

  In response to the aforementioned resignation decision, the processing staff operates the input unit of the processing terminal 33 in the office system 30 to reflect the resignation information (step S32) and disassemble the book relating to the client (step S33).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to the resignation process to the processing terminal 33 in response to an input operation performed by the processing staff on the processing terminal 33. Is stored in the storage unit 12. In the resignation process, for example, “case information: entrustment status”, “creditor information: progress information”, “case information: document creation”, “case information: account information”, “case information: deposit / withdrawal information”, “case” Information and functions related to “information: preparation of a balance sheet” and the like are provided to the processing terminal 33, and information corresponding thereto is input by a processor.

  The administrator operates the input unit of the management terminal 35 in the office system 30 as necessary, for example, when managing deposit / deposit / withdrawal sales information. The money / deposit / withdrawal sales information is managed (step S34). This deposit / deposit / withdrawal sales information is provided from the cloud service system 10 to the management terminal 35 and displayed on the display unit of the management terminal 35. The administrator checks the various types of information.

  The processing unit 11 of the cloud service system 10 provides the management terminal 35 with information and functions (for example, various screens and function menus) related to deposit / deposit / withdrawal sales management in response to an input operation by the administrator on the management terminal 35. As an example, the deposit / deposit / withdrawal sales information is transmitted to the management terminal 35. In the deposit / deposit / payment sales management, information and functions related to, for example, “account management: account information search” are provided to the management terminal 35.

(3. Settlement negotiations)
As shown in FIG. 9, as a start of the settlement negotiation (the same operation is repeated until the company-wide settlement), the processor checks the settlement proposal contents with the client (step S41), and presents the settlement plan to the trader (creditor). (Step S42). The trader also presents the settlement plan according to the settlement plan from the office (step S43). The processor determines whether the negotiation based on the settlement proposal has been broken (step S44), and if it is determined that the negotiation has been broken (YES in step S44), the processing shifts to court correspondence (step S45).

  When the teacher shifts to court support (step S45), the teacher starts court support and operates the input unit of the teacher terminal 32 in the office system 30 to perform trial progress management (step S46). In addition, the frequency of the trial itself is low, and the court manages with a view to bankruptcy recovery.

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to the trial progress management to the teacher terminal 32 in response to the teacher's input operation on the teacher terminal 32. The entered or updated trial progress information is stored in the storage unit 12. In the trial progress management, for example, information and functions related to “Creditor information: Information on litigation” and the like are provided to the teacher terminal 32, and information corresponding thereto is input by the teacher.

  The accountant operates the input unit of the accounting terminal 34 in the office system 30 and manages the trial expenses according to the above-mentioned correspondence by the teacher in the court (step S47).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) related to the trial accounting management to the accounting terminal 34 in response to the input operation of the accounting terminal 34 by the accounting staff. The trial accounting information input or updated by 34 is stored in the storage unit 12. In the case accounting management, for example, information and functions related to “account information: actual cost registration” and the like are provided to the accounting terminal 34, and information corresponding thereto is input by an accounting clerk.

  On the other hand, in the above-mentioned step S44, when it is determined that the negotiation has not been broken (NO in step S44), the processing person makes a final confirmation to the client (step S48). In the final confirmation, the contents of the settlement are confirmed with the client, for example, the refund amount, repayment date, lump sum / split in the overpayment request, and the repayment amount, number of repayments, interest, default clause, etc. in the voluntary arrangement. Be done.

  If the requester does not agree with the settlement plan in the final confirmation (NG in step S48), the processor re-negotiations with the trader (step S49). On the other hand, if the client is satisfied with the settlement plan in the final confirmation (OK in step S48), the input unit of the processing terminal 33 in the office system 30 is operated to input or update the settlement information by the settlement conclusion ( Step S50).

  The processing unit 11 of the cloud service system 10 provides the processing terminal 33 with information and functions (for example, various screens and function menus) related to settlement settlement in accordance with an input operation of the processing terminal 33 by the processing staff. The reconciliation information input or updated by is stored in the storage unit 12. In the settlement, for example, “Creditor information: progress”, “Creditor information: rearrangement information”, “Case information: Document creation”, “Case information: Account information”, “Case information: Deposit / withdrawal information”, etc. Relevant information and functions are provided to the processing terminal 33, and the corresponding information is input by the processor.

  Thereafter, the processing staff prepares and sends a settlement document (step S51), and when the company-wide settlement is completed (step S52), determines whether or not there is a proxy remittance (step S53). The settlement copy is sent to the client by e-mail or mail. Further, in the company-wide reconciliation, the company does not go to the next until the remuneration is collected for the entire company, that is, until the company-wide reconciliation can be made. However, in the case of a preliminary settlement (when threatening to send a notice of intervention), the settlement may be made before the remuneration is accumulated, and in some cases, proxy remittance may be started before the company-wide collection.

  If it is determined that there is a proxy remittance (the step S53 is present), the processing staff guides the requester to the proxy remittance (step S54). The proxy remittance guide is sent to the client by e-mail or mail. On the other hand, if it is determined that there is no proxy remittance (there is no step S53), the process proceeds to the preparation for settlement by the accountant.

  The accountant operates the input unit of the accounting terminal 34 in the office system 30 to register or update the transfer information (step S55), and when the company-wide repayment is completed, prepares the settlement (step S56). Remittance is sent to the company (creditor) based on the transfer information (proxy remittance). The proxy remittance will be described in detail in (4. Proxy remittance) described later.

  The processing unit 11 of the cloud service system 10 provides the processing terminal 33 with information and functions (for example, various screens and function menus) related to the vibrating management in response to the input operation of the accounting terminal 34 by the accountant. The substitute information input or updated by 34 is stored in the storage unit 12. In the rescheduling management, for example, it relates to “Creditor information: rearrangement information”, “case information: account information”, “case information: deposit / withdrawal information”, and “bank withdrawal processing: creation / import of Zengin data”. The information and functions to be provided are provided to the accounting terminal 34, and the corresponding information is input by the accounting staff.

  The administrator operates the input unit of the management terminal 35 in the office system 30 as necessary, for example, when managing the transfer result, and transfers the transfer result information, which is one of various types of information related to debt customer management. It is managed (step S57). The substitute result information is provided from the cloud service system 10 to the management terminal 35, and is displayed on the display unit of the management terminal 35. The administrator sees and confirms the information. For example, the manager determines where to set the axis of sales (payment or acceptance).

  The processing unit 11 of the cloud service system 10 provides the management terminal 35 with information and functions (for example, various screens and function menus) related to vibration management in response to an input operation performed by the administrator on the management terminal 35. In the transfer management, for example, information and functions related to “management of the number of remittances”, “management of transfer conversion rate” and the like are provided to the management terminal 35.

(4. Proxy remittance)
As shown in FIG. 10, the requester (obligor) deposits money into a proxy account of the office (step S61). The accounting clerk operates the input unit of the accounting terminal 34 to obtain a deposit CSV (an example of deposit information) from the Internet banking system 22 as a proxy remittance start (a monthly loop until payment is completed), The payment is taken into the service system 10 (step S62), and the payment information displayed on the display unit of the accounting terminal 34 is checked based on the payment CSV to determine whether or not payment has been made (step S63).

  If the accountant determines that there is no payment (NG in step S63), the accountant performs a payment reminder operation for the client (step S64). In this payment dunning operation, the accounting clerk instructs the requester by telephone in the case of "1.1 times no payment", and in the case of "2.2 times no payment", issues a warning to the requester. If "3. No payment has been made even after two weeks have passed since the letter was sent", a notice of resignation notice will be sent. If "4. No payment has been made after one or two weeks have passed since the notice of resignation", a lawyer will be sent. Resignation with the permission of, and send a notice of resignation to the client or the company.

  The processing staff operates the input unit of the processing terminal 33 in the office system 30 to reflect the resignation information in accordance with the above-mentioned resignation decision (step S65), and disassemble the book relating to the client (step S66).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to the resignation process to the processing terminal 33 in response to an input operation performed by the processing staff on the processing terminal 33. Is stored in the storage unit 12. In the resignation process, for example, “case information: entrustment status”, “creditor information: progress information”, “case information: document creation”, “case information: account information”, “case information: deposit / withdrawal information”, “case” Information and functions related to “information: preparation of a balance sheet” and the like are provided to the processing terminal 33, and information corresponding thereto is input by a processor.

  On the other hand, if the accountant determines that there is a payment (OK in step S63), the input section of the accounting terminal 34 is operated to manage the payment information (step S67) and create remittance data (step S68). ), Arrange remittance (step S69), reflect the remitted data (step S70), and when the company-wide payment is completed (step S71), shift the processing to the settlement process (step S72). In the remittance arrangement, a comprehensive transfer is instructed to the Internet banking system 22 based on the remittance data, and the remittance is sent to a trader (creditor).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to remittance management to the accounting terminal 34 in response to an input operation by the accountant on the accounting terminal 34. Is stored in the storage unit 12. In the remittance management, for example, it relates to “case information: account information”, “case information: deposit / withdrawal information”, “bank withdrawal processing: creation of remittance data”, “bank withdrawal processing: capture of remitted data”, and the like. Information and functions are provided to the accounting terminal 34, and corresponding information is input by an accounting person in charge.

  The administrator operates the input unit of the management terminal 35 in the office system 30 as necessary, for example, when managing the transfer result, and transfers the transfer result information, which is one of various types of information related to debt customer management. It is managed (step S73). The substitute result information is provided from the cloud service system 10 to the management terminal 35, and is displayed on the display unit of the management terminal 35. The administrator sees and confirms the information. For example, the manager determines where to set the axis of sales (payment or acceptance).

  The processing unit 11 of the cloud service system 10 provides the management terminal 35 with information and functions (for example, various screens and function menus) related to vibration management in response to an input operation performed by the administrator on the management terminal 35. In the transfer management, for example, information and functions related to “management of the number of remittances”, “management of transfer conversion rate” and the like are provided to the management terminal 35.

(5. Settlement process)
As shown in FIG. 11, the accounting person operates the input unit of the accounting terminal 34 in the office system 30 to prepare a business report (Step S81) and prepares a payment report to start the payment procedure (Step S81). In step S82, a set of documents is sent to the client (step S83), and the deposit is settled (step S84).

  The processing unit 11 of the cloud service system 10 provides information and functions (for example, various screens and function menus) relating to the settlement of deposits to the accounting terminal 34 in response to an input operation by the accountant on the accounting terminal 34. The deposit information entered by the user is stored in the storage unit 12. In the account settlement, for example, information and functions related to “client information: account information”, “client information: deposit / withdrawal information” and the like are provided to the accounting terminal 34, and information corresponding thereto is provided by the accounting staff. Will be entered.

  Thereafter, the accountant performs a filing operation such as file discarding (step S85), and performs an operation end process by operating the input unit of the accounting terminal 34 in the office system 30 (step S86).

  The processing unit 11 of the cloud service system 10 provides the information and functions (for example, various screens and function menus) relating to the task termination process to the accounting terminal 34 in response to the input operation of the accounting terminal 34 by the accountant. The work completion information input by the storage unit 34 is stored in the storage unit 12. In the business termination processing, for example, information and functions related to “case information: acceptance status”, “creditor information: progress status” and the like are provided to the accounting terminal 34, and information corresponding to these is input by the accounting staff. You.

(Import of deposit / withdrawal information into cloud service system)
Next, a flow of taking in the deposit / withdrawal information from the Internet banking system 22 into the cloud service system 10 will be described with reference to FIGS.

  As shown in FIG. 12, it is possible to directly import and withdrawal information (for example, CSV data) from the Internet banking system 22 to the cloud service system 10 by API cooperation between the Internet banking system 22 and the cloud service system 10.

  Regarding the payment processing, the requester (obligor) transfers the amount of the agreement to an account (agent account) designated by the office every month. After confirming the payment, the accountant of the office operates the input unit of the accounting terminal 34 in the office system 30 to directly transfer the payment information (for example, CSV data) from the Internet banking system 22 through the API cooperation to the cloud service system. Take in to 10.

  The deposit information is deposited data indicating the deposit amount of each debtor who has deposited into the proxy account for each debtor. This deposit information is transmitted from the Internet banking system 22 to the cloud service system 10 and is reflected by the processing unit 11 on the information for each debtor stored in the storage unit 12. That is, the information for each debtor is updated based on the payment information, or the payment information is added to the information for each debtor. The reflection includes updating (or inputting) information and adding information (for example, storing information in association with information for each debtor).

  Regarding the withdrawal processing, the accountant of the office operates the input unit of the accounting terminal 34 in the office system 30 to transfer the remittance information (for example, CSV data) in the Zengin format from the cloud service system 10 to the Internet banking. Send to system 22. After the transmission is completed, the remittance (transfer) to the creditor based on the remittance information is immediately performed, and thus the process proceeds to the confirmation process as it is. In the confirmation process, the cloud service system 10 receives payment information (for example, CSV data) from the Internet banking system 22 in response to the completion of remittance.

  The remittance information is remittance data indicating the remittance amount of each creditor who transfers money from the proxy account for each creditor. This remittance information is transmitted from the cloud service system 10 to the Internet banking system 22. The Internet banking system 22 deposits the amount of the agreement into a predetermined account for each creditor based on the remittance information.

  The withdrawal information is remitted data indicating the withdrawal amount of each creditor who has withdrawn from the proxy account for each creditor. This withdrawal information is transmitted from the Internet banking system 22 to the cloud service system 10 and is reflected by the processing unit 11 on the information for each debtor stored in the storage unit 12. That is, the information for each debtor is updated based on the payment information. That is, the information for each debtor is updated based on the dispensing information, or the dispensing information is added to the information for each debtor.

  As shown in FIG. 13, even with a method other than the API cooperation described above, it is possible to take in the deposit / withdrawal information from the Internet banking system 22 into the cloud service system 10.

  Regarding the payment processing, the requester (obligor) transfers the amount of the agreement to an account (agent account) designated by the office every month. After confirming the payment, the accountant in the office operates the input unit of the accounting terminal 34 in the office system 30 to output payment information (for example, CSV data) from the Internet banking system 22 to the accounting terminal 34, The payment information is imported from the accounting terminal 34 into the cloud service system 10 and taken in. The payment information is payment-completed data as described above.

  Regarding the withdrawal processing, the accountant of the office operates the input unit of the accounting terminal 34 in the office system 30 to transfer the remittance information (for example, CSV data) in the Zengin format from the cloud service system 10 to the accounting terminal. 34, and the remittance information is imported from the accounting terminal 34 to the Internet banking system 22. Then, after the remittance to the creditor is completed, the accounting person outputs withdrawal information (for example, CSV data) from the Internet banking system 22 to the accounting terminal 34, and sends the withdrawal information from the accounting terminal 34 to the Internet banking system 22. Import and import to and confirm withdrawal. As described above, the remittance information is remittance data, and the withdrawal information is remittance data.

  As described above, there are the direct capture method using the API linkage illustrated in FIG. 12 and the indirect capture method other than the API linkage illustrated in FIG. In the direct capture method, the deposit / withdrawal information is directly transmitted and received between the cloud service system 10 and the Internet banking system 22, whereas in the indirect capture method, the information is transmitted and received via the accounting terminal 34. That is, in the indirect import method, it is necessary to temporarily import the deposit / withdrawal information from the Internet banking system 22 to the accounting terminal 34. For this reason, the indirect import method is a method in which the business efficiency is lower than the direct import method. Therefore, in order to improve the operational efficiency related to debt consolidation, it is preferable to use a direct import method using API linkage.

<Screen related to debt customer management>
Next, screens related to debt customer management, that is, screens displayed on user terminals (each of the terminals 31 to 35) used by users such as a person in charge, a teacher, a person in charge of processing, a person in charge of accounting, and an administrator will be described. . The screens in FIGS. 14 to 34 are merely examples, and are not limiting. These images are provided from the cloud service system 10 to the user terminal. Various functions such as automatic calculation and information transfer are realized by the processing unit 11 of the cloud service system 10.

(Search screen before acceptance)
As shown in FIG. 14, when "list of consultants" in the pre-acceptance menu is clicked, a pre-acceptance search screen is displayed on the display unit of the user terminal. The user (for example, a person in charge) operates the input unit of the user terminal while looking at the screen, and inputs information to necessary items. The screen is displayed after the user logs in to the cloud service system 10 (the same applies to other screens).

  Regarding the consultant search, it is possible to input any one of the consultant No., the consultant name, and the telephone number to perform the search. Regarding the consultant's name, it is possible to search by inputting either the first name or the last name. If there is no corresponding number in the target only by telephone number search, a new registration screen opens. In addition, you can exclude test inquiries (excluding test emails), exclude accepted (excluding projects that have been entered on this acceptance date), return documents (exclude projects that have been entered on the document return date), or temporarily save only (temporarily saved projects) ) Can be searched. In addition, it is possible to search by the acceptance status, the response status, NA information, and other information. In the status / person in charge / NA (next action) information, a plurality of search items can be designated and selected. Each search item can be used by multiplying it, and it is possible to narrow down by a plurality of conditions such as a person in charge and a status.

(New registration / edit screen)
As shown in FIG. 15, when “New consultant registration” in the pre-acceptance menu is clicked, a new registration / edit screen is displayed on the display unit of the user terminal as shown in FIGS. 15 and 16. The user (for example, a person in charge) operates the input unit of the user terminal while looking at the screen, and inputs information to necessary items. The new registration / edit screen is, as shown in FIG. 15, new consultant registration, acceptance status, income and expenditure, as shown in FIG. 16, borrowing status, response policy / important items, response / escalation registration, response / escalation It has various items such as history. The new registration / edit screen cannot be displayed on one screen of the display unit, and is scrolled by the user to view the entire screen.

  In the new consultant registration (see FIG. 15), there are items such as name (last name) / name (first name), person in charge, etc., but first name (last name) / name (first name), type, advertisement, and search word (not shown) Is a required item. Note that temporary storage can be performed even when the above-described required items have not been input. However, only the name is required.

  In the acceptance status (see FIG. 15), there are items such as a temporary acceptance date, a document return date, an acceptance date, and an end date.

  In terms of income and expenditure (see FIG. 15), there are items such as income, expenditure, income other than the above, and expenditure other than the above, and further, there are respective items. For expenditures and other expenditures, there is a comment column for each item. There are also items of total income, total expenditure and surplus deduction (all are not shown), and when the above items are input, the amount is input by automatic calculation (total income = monthly income for the individual + income other than the above, Total expenditure = each expenditure item + expenditure other than the above, surplus deduction = total income-total expenditure).

  In the borrowing situation (see FIG. 16), there are items such as completed / remaining bonds, trader name (branch name) and the like. When the number of divisions is entered in the column of division, the amount of funds is automatically calculated and displayed in the column of resources (resource amount = remaining bonds / number of divisions). It is also possible to manually overwrite the amount of the funds. The total funding is the expected repayment after the settlement, and is the total funding of the borrower whose request target (□) is checked. In the supplementary field, guarantors, collateral, high-priced products, and court-related supplementary items are entered. The total debt, total, and current repayment (upper row) are the total number of loans, total remaining debt, and total monthly repayment of the entire borrower, and the total requested debt, total, and current repayment (lower) are subject to the request ( □) indicates the total number of borrowers checked, the total remaining debt, and the total monthly repayment amount. “(No intervention) repayment amount” is the total repayment amount-the repayment amount for the request.

  In the response policy / important matters (see FIG. 16), there are items such as a response policy, cost estimation, transfer agency service, and required transaction, and further, each item is included in the required transaction item. Only when the response policy is voluntary, the amount is displayed by the automatic calculation in the cost estimate column. The calculation formula is (starting fee + solution fee) × the number of requests and an administrative fee, and the setting of the starting fee and solution fee must be completed in advance. It is possible to overwrite this cost estimate manually. Also, when the transfer agency service is selected, the amount of the calculation formula of “the number of requested objects × the agency fee” is automatically displayed in the agency fee total column. It is also possible to manually overwrite this amount. In addition, the amount is displayed by automatic calculation in the column of the cost reserve amount each time. The calculation formula is the amount after discount / the number of divisions (rounded to the nearest 100 yen). The amount is displayed by the automatic calculation in the column of commission + total amount of funding. The calculation formula is the total amount of the agency fee + the amount of the monthly funds to be requested. In addition, there are items such as scheduled interview, scheduled interview date, interview method, and a lawyer in charge of interview (all not shown).

  In the correspondence / escalation registration (see FIG. 16), there are items such as a correspondence date and time and a responder. In the column of the corresponding person, the logged-in user is initially displayed. When registering with another responder, select the responder from the pull-down menu.

  In the correspondence / escalation history (see FIG. 16), the histories are displayed in the order of newest correspondence date and time (older correspondence is lower).

(Case information creation screen after acceptance)
As shown in FIG. 17, when “Create new case information” is clicked on the consultant basic bar, the case information creation screen (takeover screen) after acceptance is displayed on the user terminal as shown in FIGS. 17 and 18. It is displayed on the display. A user (for example, a person in charge of processing or a person in charge of accounting) operates an input unit of the user terminal while watching the screen, and inputs information to necessary items. The incident information creation screen has various items such as consultant basic information as shown in FIG. 17, and income and expenditure, borrowing status, response policy, and acceptance status as shown in FIG. The case information creation screen cannot be displayed on one screen of the display unit, and is scrolled by the user to view the entire screen.

  The case information creation screen is a screen for linking data before and after acceptance. On this screen, new case information / creditor data after acceptance is created (this process can be performed only once). The consultant information is passed on to the case information (information after acceptance). The operation of clicking "New case information" is performed only once. Once the case information has been created, "case information details", which is a button for transitioning to the case information after acceptance, is displayed. It should be noted that there are portions where the item names and display formats are different between the consultant information and the case information.

  For borrowers (see FIG. 18), registration before acceptance is free text, and registration after acceptance is a selection from the master. On the handover screen, the creditor registered in the creditor master is estimated and displayed by the processing unit 11 from the registered contents before the acceptance. As an example 1, before the acceptance: aaa → after the acceptance: aaa corporation, or as an example 2, before the acceptance: bbb → after the acceptance: unknown (blank display). If the corresponding creditor is not displayed, select from the existing creditor pull-down or register in the creditor master.

(the top screen)
As shown in FIG. 19, when “TOP” in the menu after the acceptance is clicked, a top screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of processing or a person in charge of accounting) checks necessary information by looking at the screen or inputs information by operating an input unit of the user terminal.

  The top screen is a screen for providing deposit / withdrawal schedule information and deposit / withdrawal result information. On this screen, payment schedules and results, withdrawals and results for the past three days and the past week from today are listed by number and amount. When any part of the number or the amount of money in the list is clicked, the screen transits to the detail screen. As an example, when “93” of the planned number of items on the top screen is clicked, the upper screen in FIG. 19 transits to the detail screen which is the lower screen in FIG.

(Incident information screen)
As shown in FIG. 20, when "case information" in the menu after the acceptance is clicked, a case information screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of processing or a person in charge of accounting) checks necessary information by looking at the screen or inputs information by operating an input unit of the user terminal.

  The case information screen is a screen for providing case information. On this screen, a column for case information search and search results are displayed. In the search results, a list of case information is displayed. When the “confirm” button in the list is clicked, the screen transits to a customer details screen (see FIG. 21).

  As shown in FIG. 21, on the customer details screen, in addition to the case information, “progress status tab”, “client information tab”, “creditor information tab”, “document creation tab”, “split payment plan tab”, “Account information tab” and “deposit / withdrawal information tab” are displayed.

  As shown in FIG. 21, when the “progress status tab” is clicked, a progress status page indicating the progress status of the selected incident information is displayed. The progress status page is a tab page for providing a progress status so that cooperation can be made between other departments like a message board. On this progress status page, the progress status (latest information) for each task is displayed.

  As shown in FIG. 22, when the “client information tab” is clicked, a client information page showing the client information relating to the selected case information is displayed. The requester information page is a tab page for managing information on the requester (obligor), exchange with the requester, and the like. On this client information page, client information, dialogue records, client account information, and workplace information are displayed. The requester information column records basic information of the requester, such as name, contact information, and address. In the field of the dialogue record, a history such as the exchange between the requester and the user (office) is left. In the field of the client account information, basic remuneration, account information, and payment information of the client are registered. Based on the information registered here, management of account information, automatic creation of acquisition money information, and the like are performed. Thereby, work efficiency can be improved. In the column of workplace information, information such as the workplace of the client and the former workplace is recorded.

  As shown in FIG. 23, when the “Creditor Information Tab” is clicked, a creditor information page showing creditor information relating to the selected case information is displayed. The creditor information page is a tab page for providing a list of borrower creditor information on creditors who are borrowers of the client (obligor). On this creditor information page, borrower creditor information, specifically, debt status and progress are displayed for each borrower creditor information. Thereby, the user can grasp the debt status and progress status of each creditor. When the “Reference” button in the list is clicked, the screen transits to the borrower's creditor detail page (see FIG. 24).

  As shown in FIG. 24, on the borrower's creditor detail page, in addition to the case information, borrower's creditor details, negotiation records, rearrangement information, and litigation information are displayed. This borrower details page is a page for managing creditors by lowering the hierarchy to one creditor. In the column of case information, a creditor name and a progress display for each creditor are added. The borrower details column records the debt status, management of the progress of processing operations, special notes at the time of negotiations, and remuneration at the time of settlement. In the column of the negotiation record, the exchange between the creditor and the user (office) is recorded. The settlement information column records information on settlement with creditors. Account information (reward management) and deposit / withdrawal information are automatically generated based on the settlement information registered here. Thereby, work efficiency can be improved. The litigation information column is for managing litigation relating to debt consolidation cases, and records litigation information.

  As shown in FIG. 25, when the “document creation tab” is clicked, a document creation page showing the document creation information on the selected case information is displayed. The document creation page is a tab page for generating a document (template) used for business. On the borrower's creditor detail page, the borrower's creditor information to be prepared and the columns for preparing the document are displayed. If a designated document is registered in the document creation column, a document to be used in business can be created with a single button using data (client name, address, debt status, etc.) in the system.

  As shown in FIG. 26, when the “split payment plan tab” is clicked, a split payment page showing split payment information relating to the selected case information is displayed. The split repayment page is a tab page for simulating a repayment plan and creating and printing a repayment plan schedule for the client. On this split payment information page, a split payment plan is displayed. More specifically, when "Import borrower's organization information" on the upper screen in FIG. 26 is clicked, a schedule table or a performance table is created as shown in the lower screen.

  As shown in FIG. 27, when the "account information tab" is clicked, an account information page showing the requester's account information regarding the selected case information is displayed. The account information page is a tab page for managing the client's account information. Although the account information is displayed on this account information page, it is possible to manage the degree of remuneration and proxy remittance. When a client (borrower) receives a deposit, the funds are automatically allocated to rewards and proxy remittances.

  As shown in FIG. 28, when the “payment / payment information tab” is clicked, a payment / payment information page showing the client's payment / payment information regarding the selected case information is displayed. The deposit / withdrawal information page is a tab page for managing the client's payment schedule, payment result, payment schedule, and payment result. On this deposit / withdrawal information page, scheduled management information of remuneration / expenses and a deposit / withdrawal list are displayed.

(Credit information screen)
As shown in FIG. 29, when “Creditor Information” in the menu after acceptance is clicked, a creditor information screen is displayed on the display unit of the user terminal. The user (for example, a processing person or an accounting person) checks necessary information by looking at the screen.

  The creditor information screen is a screen for providing creditor information. On this screen, a column of creditor information search and search results are displayed. In the search results, a list of case information is displayed. When the “confirm” button in the list is clicked, the screen transits to a customer details screen (see FIG. 21).

(Account management screen)
As shown in FIG. 30, when "account management" in the menu after acceptance is clicked, an account management screen is displayed on the display unit of the user terminal. The user (for example, an accountant) confirms necessary information by looking at the screen.

  The account management screen is a screen for providing account management information and confirming the movement of the account information item in the entire office. On this screen, a field for account information search and search results are displayed. In the search results, a list of case information is displayed. It is possible to output a list of accounts as a search result in CSV format.

(Payment management screen)
As shown in FIG. 31, when “payment management” is clicked in the menu after acceptance, a payment management screen is displayed on the display unit of the user terminal. The user (for example, an accountant) confirms necessary information by looking at the screen.

  The payment management screen is a screen for providing payment information and managing the status of payment (requester payment, overpaid money return, etc.). On this screen, a column for payment information search and search results are displayed. In the search result, a list of payment schedule information and payment execution information for each case is displayed. With this payment management screen, it is possible to improve the work efficiency such as unpaid tracking. In addition, it is possible to output a deposit list of search results in CSV format.

(Withdrawal management screen)
As shown in FIG. 32, when “payment management” in the menu after the acceptance is clicked, a withdrawal management screen is displayed on the display unit of the user terminal. The user (for example, an accountant) confirms necessary information by looking at the screen.

  The withdrawal management screen is a screen for providing withdrawal information and managing the status of withdrawal (requester refund, proxy remittance, etc.). On this screen, a column for withdrawal information search and search results are displayed. In the search results, a list of withdrawal schedule information and withdrawal execution information for each case is displayed. With this payment management screen, it is possible to improve business efficiency, such as tracking unpaid money. Note that the withdrawal list of the search results can be output in CSV format.

(Bank payment processing screen)
As shown in FIG. 33, when "bank payment processing" in the menu after acceptance is clicked, a bank payment processing screen is displayed on the display unit of the user terminal. The user (for example, an accountant or the like) looks at the screen and operates the input unit of the user terminal to input information (for example, select a file).

  The bank payment processing screen is a screen for capturing payment information (paid information). On this screen, a column of the bank deposit confirmation process and a bank deposit confirmation history are displayed. In the bank deposit processing confirmation history, execution information of bank deposit processing (date and time of execution of bank deposit processing, processing result, etc.) is displayed in a list.

  In FIG. 33, regarding the processing of receiving the deposit information, the deposit information once extracted from the Internet banking system 22 to the user terminal is transferred to the cloud service system 10 by the indirect import method other than the API linkage described above (see FIG. 13). Although the uploading to be taken in is exemplified, when the above-described direct incorporation method by API cooperation (see FIG. 12) is adopted, by clicking a button, the deposit information is directly sent from the Internet banking system 22 to the cloud service system 10. Can be captured.

(Bank withdrawal processing screen)
As shown in FIG. 34, when "bank withdrawal processing" in the menu after acceptance is clicked, a bank withdrawal processing screen is displayed on the display unit of the user terminal. The user (for example, an accountant) checks necessary information by looking at the screen, or inputs information by operating the input unit of the user terminal (for example, selecting a processing target).

  The bank withdrawal processing screen is a screen for creating and loading withdrawal information. On this screen, a column of bank withdrawal processing and a withdrawal search result are displayed. In the withdrawal search result, remittance information (for example, case name, scheduled withdrawal date, requester name, creditor name, withdrawal item, withdrawal amount, Etc.) are listed. This remittance information (withdrawal instruction information) is information for remittance (withdrawal) of the amount of the agreement from the agency account of the office to the individual accounts of a plurality of creditors, and is transmitted to the Internet banking system 22. You.

  Regarding the remittance information (dispensing instruction information) fetching process, as in the case of the above-described remittance information, the user terminal uploads the remittance information to the Internet banking system 22 by an indirect fetching method other than the API linkage. Alternatively, the remittance information may be fetched directly from the cloud service system 10 to the Internet banking system 22 by a direct fetching method based on API linkage.

  Here, the debt consolidation case ends when a settlement is established between the client (obligor) and the trader (creditor) about six months after the request. That's where the profession usually comes in contact with creditors on behalf of debtors. Thereafter, the debtor makes monthly payments according to the payment plan negotiated between the agent, the profession, and the creditors. However, debtors are eager to continue to serve as a point of contact. The reason for this is that if a lawyer or judicial scrivener is inserted between the debtor and the creditor, the debtor will not directly interact with the creditor, and the mental burden on the debtor will be reduced. In addition, when the debtor borrows from multiple creditors, the transfer is usually made to each creditor, but on behalf of the repayment (proxy remittance), the debtor makes all repayments once a month. By transferring money to an account of a business office, the responsibilities will be transferred to creditors on behalf of the company, so there is no hassle. In addition, the repayment date differs for each creditor, and there is also a point that it is not necessary to live on a repayment day. Furthermore, even if there is a delay in repayment after the settlement, if the repayment is performed on behalf of the creditor, the contact from the creditor will be made first, and the contact from the creditor will be basically made. In that the mental burden on the debtor is reduced.

  For these reasons, the demand for debt consolidation cases has increased at the professional offices, but as the number of obligors requesting monthly proxy repayments (proxy remittances) has increased, Because of the shortage and the lack of business, he has not met the debtor's request. Normally, in debt consolidation cases, due to the nature of the task of managing debt customers and performing special tasks, business processing is complicated, and special payment agency services such as agency payment require specialized knowledge, Since it is difficult to secure physical personnel to handle the amount of work, there is a need for more efficient work related to debt consolidation.

  Therefore, in the present embodiment, in the cloud service system 10, information on each debtor regarding the debt consolidation case is centrally managed. The information for each debtor includes various information (for example, debtor information, debtor account information, case information, creditor information, and the like) input by a user's input operation on the user terminal (any of the terminals 31 to 35). Debt information, negotiation record information, trial progress information, trial expense information, remittance information, etc.) are reflected, and various information (for example, deposit / withdrawal information, etc.) obtained from the external cooperation service system 20 are also reflected. Accordingly, the user can easily obtain information on each debtor in which various types of information are reflected from the cloud service system 10, so that the operational efficiency related to debt consolidation can be improved. As a result, even if the number of debtors requesting monthly substitute payments increases, it is possible for the professional office to suppress shortages of workers and prevent the business from turning around. Can be raised.

  As described above, according to the embodiment, information and functions related to debt consolidation are provided to the user (office) by the cloud service system 10. For example, various information for each debtor (for example, debtor information, debtor account information, case information, creditor information, debt information, negotiation record information, settlement information, trial progress information, trial expense information, remittance information, deposit and withdrawal Information and the like are associated and centrally managed, stored in the storage unit 12 of the cloud service system 10, and appropriately provided to the user in response to the user's request. Accordingly, the user can easily obtain various information for each debtor from the cloud service system 10, so that the operational efficiency related to debt consolidation can be improved.

  Further, the cloud service system 10 directly receives the deposit information from the Internet banking system 22 and reflects the received deposit information on the information for each debtor stored in the storage unit 12 of the cloud service system 10. As a result, the deposit information is automatically reflected in the information for each debtor, and therefore the user does not need to perform data input work or import work related to the deposit information, and the deposit information ( (Paid-in data), it is possible to improve the operational efficiency related to debt consolidation. Furthermore, since the cloud service system 10 can transmit the remittance information to the Internet banking system 22, the user only needs to issue a remittance instruction to the cloud service system 10 after confirming the payment, and the remittance information is transmitted to the Internet banking system 22. Can be easily transmitted, and the operational efficiency related to debt consolidation can be improved.

  Further, the cloud service system 10 directly receives the withdrawal information from the Internet banking system 22 and reflects the received withdrawal information on the information for each debtor stored in the storage unit 12 of the cloud service system 10. As a result, the withdrawal information is automatically reflected in the information for each debtor, so that the user does not need to perform data input work or take-in work related to the withdrawal information and can easily withdraw from the cloud service system 10. Since it becomes possible to acquire money information (paid-out data), it is possible to improve the operational efficiency related to debt consolidation.

<Other embodiments>
In the above description, the application of the debt customer management system 1 to a system for a debtor from a financial institution has been described as an example. However, the present invention is not limited to this, and for example, a debt due to a traffic accident or other reasons may be caused. It is also possible to apply to a system for persons.

  In the above description, various functions are provided in the cloud service system 10. However, as the functions, for example, a facsimile (fax) transmission function can be provided. Normally, the user operates a user terminal to print a notice document or the like from the cloud service system 10 and manually transmits a facsimile to related companies. However, when the cloud service system 10 implements the fax transmission function, it becomes possible to fax the notification document or the like from the cloud service system 10 directly to the related companies. As a result, it is possible to reduce manual labor and erroneous transmission, reduce costs, and the like. As a result, it is possible to improve the operational efficiency related to debt consolidation. For example, the cloud service system 10 can be used for notification of intervention (see steps S22 and S23 in FIG. 8), notification of resignation (see resignation due to unpaid money in FIGS. 8 and 10), and presentation of a settlement plan (see step S42 in FIG. 9). FAX transmission function can be used.

  Further, in the above description, not only telephone calls but also e-mail communications are frequently performed as a means of communication from a professional office to a consultant or a client. At this time, there is a risk that erroneous transmission or erroneous attachment of a document due to a mistake in designation of an e-mail address or the like may occur. One way to eliminate such risks is to specify a destination for each business flow on the cloud service system 10 so that the exchange of e-mails or messages can be performed safely without the above-mentioned concerns without using individual mailer software. It is possible to provide a limiting function (a destination limiting function) and the like. Since an e-mail is used as one of the contact methods to the debtor, the e-mail transmission function having the above-mentioned destination limitation function is a function generally used. The phases include, for example, sending a document (see step S8 in FIG. 7), sending a settlement document (see step S51 in FIG. 9), and proxy remittance guidance (see step S54 in FIG. 9).

  The above-described embodiments can take the form of a hardware embodiment, a software embodiment, or an embodiment including both hardware and software. Software includes, but is not limited to, firmware, microcode, resident software, and the like. Further, the program according to the above-described embodiments may take the form of a computer program product stored in a computer-usable (for example, computer-readable) storage medium. The computer-usable storage medium is, for example, any device capable of containing, storing, transmitting, transmitting, and carrying a program used by a system, an apparatus, an apparatus, or the like. Examples of the storage medium include an electronic medium, a magnetic medium, an optical medium, a magneto-optical medium, an infrared medium, a semiconductor system (or an apparatus or a device), and a transmission medium. Examples of the storage medium include a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), a solid state drive (SSD), a removable disk, an optical disk, a fixed magnetic disk, and a magnetic tape.

  While some embodiments of the present invention have been described above, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. These new embodiments can be implemented in other various forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and their equivalents.

DESCRIPTION OF SYMBOLS 1 Debt customer management system 10 Cloud service system 11 Processing part 12 Storage part 20 External cooperation service system 21 Call center system 22 Internet banking system 30 Office system 31 Acceptance terminal 32 Teacher terminal 33 Processing terminal 34 Accounting terminal 35 Management terminal 40 Communication network

Claims (6)

A debt customer management system in which a user terminal, a cloud service system, and an internet banking system are connected via a communication network,
The cloud service system,
A storage unit for storing information provided to the user terminal for each debtor,
Means for receiving, from the Internet banking system, payment information indicating a deposit amount for each of the debtors deposited in a proxy account for each of the debtors;
Means for reflecting the payment information in the information for each debtor stored by the storage unit,
A means for transmitting remittance information indicating a remittance amount for each creditor to be remitted from the proxy account for each creditor pertaining to the debtor to the Internet banking system,
Debt customer management system. The cloud service system,
Means for receiving from the Internet banking system withdrawal information indicating a withdrawal amount for each of the creditors withdrawn from the proxy account for each of the creditors,
Means for reflecting the withdrawal information in the information for each debtor stored by the storage unit,
The debt customer management system according to claim 1, further comprising: In a debt client management system in which a user terminal, a cloud service system, and an Internet banking system are connected via a communication network,
The cloud service system,
A storage unit that stores information provided to the user terminal for each debtor,
Receiving, from the Internet banking system, payment information indicating a deposit amount for each of the debtors deposited in a proxy account for each of the debtors;
Reflecting the payment information in the information for each debtor stored by the storage unit;
Transmitting, to the Internet banking system, remittance information indicating a remittance amount for each creditor to be remitted from the proxy account for each creditor related to the debtor;
Perform debt customer management methods. The cloud service system,
Receiving from the Internet banking system withdrawal information indicating a withdrawal amount for each of the creditors withdrawn from the proxy account for each of the creditors;
Reflecting the withdrawal information in the information for each debtor stored by the storage unit;
The debt customer management method according to claim 3, wherein In a debt client management system in which a user terminal, a cloud service system, and an Internet banking system are connected via a communication network,
In the computer provided in the cloud service system,
From the Internet banking system, receiving payment information indicating the deposit amount for each debtor deposited in a proxy account for each debtor,
A step of storing the deposit information in the information for each debtor stored in the storage unit included in the cloud service system and provided to the user terminal;
Transmitting, to the Internet banking system, remittance information indicating a remittance amount for each creditor to be remitted from the proxy account for each creditor related to the debtor;
Debt customer management program to get you running. The computer receiving from the Internet banking system withdrawal information indicating the withdrawal amount for each of the creditors withdrawn from the proxy account for each of the creditors;
Reflecting the withdrawal information in the information for each debtor stored by the storage unit;
6. The debt customer management program according to claim 5, for executing the following.