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

Description

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

Debt consolidation cases are handled at professional offices where professionals such as lawyers and judicial scriveners work (for example, law firms and judicial scrivener offices). In order to handle this debt consolidation case, it is necessary to manage the debtor who is the debtor (various information relating to debt consolidation), but specialized knowledge and work are required compared to other business types. In particular, business processing is complicated due to the nature of business that carries out special business, and it is difficult to secure physical personnel to handle the work volume. Therefore, it is desired to improve business efficiency related to debt consolidation. There is.

As one of the services related to the debt consolidation case described above, there is, for example, a payment agency service (remittance remittance) for transferring a deposit from a debtor to a creditor. Professional industries such as lawyers and judicial scriveners have characteristic rewards and income systems such as professional rewards and postpaid success fees, unlike the manufacturing industry and general service industry, so specialized knowledge is also required for payment agency services. It For this reason, the payment agency work in the professional office is operated by a limited number of people, and the work efficiency relating to debt consolidation is reduced, so that improvement of the work efficiency is required.

JP, 2003-67583, A JP, 2011-2941, A

The problem to be solved by the present invention is to provide a debt customer management system, a debt customer management method, and a debt customer management program capable of improving work 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 and a cloud service system are connected via a communication network, and the cloud service system debts information provided to the user terminal. A storage unit that stores the information for each debtor, a means for reflecting the case information regarding the debt case for each debtor in the information for each debtor stored by the storage unit, and the information for each debtor stored by the storage unit, Means for reflecting the creditor information on the obligor for each obligor, means for reflecting the debt information for the obligor for each obligor to the information for each obligor stored by the storage unit, and the debt stored by the storage unit The means for reflecting the settlement information regarding the settlement with each obligor to the information for each obligor, and the information for each obligor stored by the storage unit, for each obligor who has deposited in the proxy account for each obligor A means for reflecting the deposit information indicating the deposit amount, and a means for reflecting the withdrawal information indicating the withdrawal amount for each obligor withdrawn from the proxy account for each obligor, in the information for each obligor stored in the storage unit With.

A debt customer management method according to an embodiment of the present invention is a debt customer management system in which a user terminal and a cloud service system are connected via a communication network, and the cloud service system stores information provided to the user terminal for each debtor. A step of reflecting the case information regarding the debt case of each debtor in the information of each debtor stored by the storage section, and the information of each debtor stored in the storage section The step of reflecting the creditor information on the obligor of each obligor, the step of reflecting the debt information of the obligor of each obligor to the information of each obligor stored by the storage section, Information for each debtor, and the information for each debtor stored by the storage unit, including the steps for reflecting the settlement information regarding the settlement for each debtor, and the information for each debtor who has deposited in the proxy account for each debtor. A step of reflecting the deposit information indicating the amount, and a step of reflecting the withdrawal information indicating the withdrawal amount of each obligee withdrawn from the proxy account for each obligee, to the information for each obligor stored by the storage unit. To execute.

A debt customer management program according to an embodiment of the present invention is a debt customer management system in which a user terminal and a cloud service system are connected via a communication network, and a computer included in the cloud service system uses a storage unit included in the cloud service system. The step of reflecting the case information regarding the debt case of each debtor in the information of each debtor stored and provided to the user terminal, and the information of each debtor stored in the storage unit, the creditor of each debtor The step of reflecting the creditor information regarding the debtor, the step of reflecting the debt information regarding the debt of each creditor in the information for each debtor stored in the storage section, and the information for each debtor stored in the storage section, Steps that reflect the settlement information regarding the settlement with each obligor and the information for each obligor stored in the storage unit, and the deposit information that shows the amount of deposit for each obligor that has deposited in the proxy account for each obligor And a step of reflecting the withdrawal information indicating the amount of withdrawal for each obligee withdrawn from the proxy account for each obligee, to the information for each obligor stored by the storage unit.

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

It is a figure which shows schematic structure of the debt customer management system which concerns on embodiment. It is a figure which shows the function menu (function for ordering/processing personnel) which concerns on embodiment. It is a figure which shows the function menu (function for accounting staff) which concerns on embodiment. It is a figure which shows the function menu (function for managers) which concerns on embodiment. It is a figure which shows a part of debt customer management information which concerns on embodiment. It is a figure which shows a part of debt customer management information which concerns on embodiment. It is a flow chart which shows the business flow (1. acceptance) of debt consolidation concerning an embodiment. It is a flow chart which shows the business flow (2. settlement preparation) of debt consolidation concerning an embodiment. It is a flow chart which shows the business flow (3. settlement negotiation) of debt consolidation concerning an embodiment. It is a flow chart which shows the business flow (4. proxy remittance) of debt consolidation concerning an embodiment. It is a flow chart which shows the business flow (5. settlement process) of debt consolidation concerning an embodiment. It is a figure for demonstrating the flow of the direct taking in of the deposit/withdrawal information by API cooperation which concerns on embodiment. It is a figure for demonstrating the flow of indirect acquisition of deposit/withdrawal information by means other than API cooperation which concerns on embodiment. It is a figure which shows the pre-acceptance search screen which concerns on embodiment. It is a figure which shows a part of new registration / edit screen which concerns on embodiment. It is a figure which shows a part of new registration / edit screen which concerns on embodiment. It is a figure which shows a part of case information creation screen after the appointment which concerns on embodiment. It is a figure which shows a part of case information creation screen after the appointment which concerns on embodiment. It is a figure which shows the top screen which concerns on embodiment. It is a figure which shows the case information screen which concerns on embodiment. It is a figure which shows the customer detailed screen (progress situation page) which concerns on embodiment. It is a figure which shows the client information page which concerns on embodiment. It is a figure which shows the creditor information page which concerns on embodiment. It is a figure which shows the borrower creditor detailed page which concerns on embodiment. It is a figure which shows the document creation information page which concerns on embodiment. It is a figure which shows the division payment information page which concerns on embodiment. It is a figure which shows the account information page which concerns on embodiment. It is a figure which shows the deposit/withdrawal information page which concerns on embodiment. It is a figure which shows the creditor information screen which concerns on embodiment. It is a figure which shows the account management screen which concerns on embodiment. It is a figure which shows the payment management screen which concerns on embodiment. It is a figure which shows the payment management screen which concerns on embodiment. It is a figure which shows the bank deposit processing screen which concerns on embodiment. It is a figure which shows the bank withdrawal processing screen which concerns on embodiment.

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

<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 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 for cloud computing, and is a usage form in which computer resources are provided in the form of services 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 be capable of 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. In response to an instruction from the office system 30, the processing unit 11 performs processing related to debt customer management for managing various information related to debt consolidation (for example, creation and update of various information), and 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 relating to debt consolidation (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/withdrawal information), and various software such as software relating 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 capable of 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 statement inquiry, and remittance (transfer). The Internet banking system 22 responds to an access (for example, information request) of the cloud service system 10 to transaction information (for example, deposit/withdrawal information) related to a bank account (proxy account) of an office which is a customer of the bank. 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) data according to the access of the office system 30. Note that the cloud service system 10 is given in advance by the internet banking system 22 the right to access a specific bank account in the internet banking system 22.

The office system 30 has an accepting terminal 31, a teacher terminal 32, a processing terminal 33, an accounting terminal 34, and a management terminal 35. The accepting terminal 31 is a terminal used by a person in charge of acceptance, the teacher terminal 32 is a terminal used by a teacher who is a professional, and the processing terminal 33 is a terminal used by a person in charge of processing. The accounting terminal 34 is a terminal used by a person in charge of accounting, and the management terminal 35 is a terminal used by an administrator. These terminals 31 to 35 function as user terminals used by users 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 (none of which is shown), and the like. ing. As each of the terminals 31 to 35, for example, a desktop personal computer, a notebook personal computer, a personal digital assistant or the like is used. Examples of mobile information terminals include tablet terminals and smartphone terminals. Further, for example, a keyboard or a mouse is 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 a control unit, and a hard disk drive (HDD) or a solid state drive (SSD) is a storage unit. Storage is used.

In the office system 30 described above, a terminal is provided for each business such as the acceptance work, the processing work, the accounting work, and the management work, but the present invention is not limited to this, and when some work is processed by one person, It is also possible to make the accepting terminal 31 and the processing terminal 33 into one common terminal. Further, the processing terminal 33 and the accounting terminal 34 can be one common terminal, and the teacher terminal 32 and the management terminal 35 can be one common terminal, and the numbers can be appropriately adjusted.

<Cloud service system>
Next, the cloud service system 10 described above 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 realizes various functions (means) by executing various types of processing based on software according to a user's input operation to each of the terminals 31 to 35 of the office system 30.

As shown in FIGS. 2 to 4, the function menus of the application software provided by the cloud service system 10 include “consultant list/search”, “pre-listing list/search”, “post-listing list/search”, and “bank”. It is composed of “account linkage”, “account deposit/withdrawal management”, “form batch output instruction” and “master management”. In the login, the user operates the user terminal to input the user ID and password to log in to the cloud service system 10.

(Functions for appointment/processing personnel)
As shown in FIG. 2, "functions for accepting and processing persons" in the function menu include "list of consultants/search", "list/search before accepting" and "list/search after accepting" (FIG. 2). See the unfilled frame inside). These various functions are assumed to be used by a person in charge of accounting/accounting (acceptance/accounting group).

Customer management is performed on a case-by-case basis for each consultant (debtor). The pre-acceptance information management is a function of managing information before being accepted, and manages information such as correspondence history, hearing sheet output (information), and transfer after acceptance. Post-acquisition information management is a function to manage post-acquisition information. For example, information such as client account information, dialogue history, document creation (information), deposit/withdrawal information, litigation information, creditor list (information), etc. to manage. The creditor list (information) includes details of creditors, such as borrowing status, arrangement information, and negotiation history. File management is a function for managing files related to business.

Usually, the counselor (debtor) consults the debt by telephone or e-mail. In this case, the accepting person in charge operates the accepting terminal 31 to input consultant information (eg, consultant basic information) regarding the consultant. The inputted consultant information is automatically stored in the storage unit 12 of the cloud service system 10. Further, in recent years, the number of consultants who click on an advertisement on a web page to consult from an LP (landing page) is increasing. In this case, when the counselor inputs necessary items to the LP, the counselor information input to the LP is automatically stored in the storage unit 12 of the cloud service system 10 by the cooperation between the LP and the cloud service system 10. Is stored. As a result, the person in charge of accepting the work does not need to input the consultant information by himself, so that the work efficiency can be improved.

When the consultant is not a new customer (when the consultant information is stored in the storage unit 12), the cloud service system 10 responds to the call from the consultant by the API cooperation with the call center system 21. , Obtains the telephone number (or customer information) of the consultant 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 accepting terminal 31. As a result, the consultant information about the consultant who made the call is automatically displayed, and the person in charge of accepting the work does not need to check the consultant's name and address to read out the consulter information, improving work efficiency. Can be made.

(Functions for accounting personnel)
As shown in FIG. 3, “functions for accounting personnel” in the function menu include “bank account cooperation” and “account deposit/withdrawal management” regarding the bank account (representative account) of the office (filled in FIG. 3). See the frame without). "Bank account cooperation" includes "receipt of deposit" and "reflecting withdrawal". The "account deposit/withdrawal management" includes "account list/search", "deposit list/search", and "withdrawal list/search". These various functions are intended for use by an accounting person (accounting group), and include, for example, an API cooperation function and a CSV output function.

(Functions for administrators)
As shown in FIG. 4, "functions for administrator" in the function menu include "form batch output instruction" and "master management" (see the unfilled frame in FIG. 4). The “form batch output instruction” includes “pre-acceptance total number CSV”, “post-acceptance total number CSV” and “substitution record 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 an administrator (for example, an office manager or a consultant).

As described above, the cloud service system 10 is provided with various functions, but the present invention is not limited to this. For example, the cloud service system 10 may be provided with a “requester function” or a “remote defense function”. Is also possible. The "requester function" includes "progress status confirmation" and "simple message transmission". The client is a former consultant, and the client is treated as a client when he/she requests the debt consolidation from the office.

In the client function, as an example, SMS (short message service) exchange is performed through software of the cloud service system 10. As an overall 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 laptop computer, a mobile information terminal, etc.) owned by the client and the cloud service system 10. Data cooperation (for example, data transmission/reception). Further, in the remote defense function, for example, the cooperation of the client terminal and the cloud service system 10 allows the teacher of a professional profession to respond to the consultation of the client at a remote location.

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

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

As shown in FIG. 5, the case information is information relating to debt consolidation cases, and includes, for example, information such as case name, case acceptance date, trustee status, trustee, lawyer in charge, clerk in charge, completion date, and remarks. I'm out.

The requester information (debtor information) is information about the requester, and includes, for example, family name (including kana), first name (including kana), old name, landline phone, mobile phone, fax, email, date of birth, Includes information such as gender, occupation, income, residence, zip code, address, permanent postal code, permanent register, old postal code, old address, family secret, contact method, contact method supplement, mailing method, mailing method supplement, remarks, etc. I'm out.

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

The client account information (obligor account information) is information relating to the client account, for example, financial institution name, store name, account type, account number, account name, virtual account number, monthly deposit amount, first deposit date, It includes information such as deposit date.

As shown in FIG. 6, the borrower creditor details (information) is information relating to the creditor and the debt. For example, the creditor, the progress status, the loan start date, the first loan amount, the monthly repayment amount, the contractual debt balance, It includes information such as outstanding debt balance, membership number, contract number, appointment notice dispatch date, statement receipt date, settlement proposal dispatch date, and remarks.

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

Settlement information is information about a settlement with a creditor, such as settlement status, settlement date, settlement amount, repayment/overpayment method, repayment agency, number of payments, first repayment date, first repayment date, second repayment date, Second time-Includes information such as repayment amount.

The deposit information (payment history information) is information relating to deposits. For example, deposit source type, deposit type, deposit source name, estimated deposit date, estimated deposit amount, actual deposit date, deposit amount (receipt amount), remarks, etc. Contains information.

The withdrawal information (withdrawal history information) is information regarding withdrawal, and for example, withdrawal source type, withdrawal type, withdrawal destination name, expected withdrawal date, expected withdrawal amount, actual withdrawal date, withdrawal It includes information such as the amount of money (withdrawal amount) and remarks.

<Business flow>
Next, an example of a debt consolidation business flow in the debt customer management system 1 will be described. This debt consolidation business flow is as follows: “1. Acceptance (see FIG. 7)”, “2. Settlement preparation (see FIG. 8)”, “3. Settlement negotiations (see FIG. 9)”, “4. 10))” and “5. Settlement processing (see FIG. 11)”.

(1. Appointment)
As shown in FIG. 7, the person-in-charge accepts a new consultation from a counselor (obligor) by telephone or e-mail (step S1), operates the input unit of the acceptance terminal 31 in the office system 30, and makes a telephone or Information such as a name is input (step S2), hearing and counseling is performed (step S3), and the consultant information is input or updated by operating the input unit of the accepting terminal 31 (step S4).

The processing unit 11 of the cloud service system 10 provides the accepting terminal 31 with information and functions (for example, various screens and function menus) related to input or update of consultant information according to the input operation of the accepting person on the accepting terminal 31. Then, the consultant information input or updated by the accepting terminal 31 is stored in the storage unit 12. In the input (or update) of this consultant information, for example, "list of consultants: consultant basics", "list of consultants: details", "list of consultants: income and expenses", "list of consultants: borrowing status" , "List of consultants: Correspondence policy/important matters", "List of consultants: Required hearing items", "List of consultants: Correspondence/escalation history", etc. Corresponding information is entered by the assignee.

The person in charge of acceptance judges whether there is provisional appointment (step S5), and if it decides not to accept provisional appointment (NO in step S5), re-follows or cancels appointment work (end). .. On the other hand, when it is determined that the temporary appointment is made (YES in step S5), the person in charge of acceptance confirms the interview (step S6), and if the interview desired by the consultant is a telephone interview, the office system 30 accepts the appointment. The consultant information is input or updated by operating the input unit of the terminal 31 (step S7).

Similarly to the 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 consultant information according to the input operation of the person in charge of accepting on the accepting terminal 31. The consultant information provided to the terminal 31 and input or updated by the accepting 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 in the above.

After that, the person in charge of delivery sends the documents (for example, the delegation contract) and the like (step S8), makes a contact with the editorial staff (for example, the contact for explaining how to fill out the documents) (step S9), and confirms the return of the documents. (Step S10). The person in charge will contact the secretary again if the return has not arrived. On the other hand, if the return has arrived, the document is checked (step S11) and a document delivery list of sent or undelivered is created (step S12). If the documents are incomplete, the counselor is contacted. If there is no incompleteness, the teacher confirms the person (interview) by telephone interview (step S13).

On the other hand, when the interview desired by the consultant is the visit interview in step S6, the teacher confirms the person (interview) through the visit interview (step S13). After the interview (after the telephone interview or the visit interview), the teacher determines whether or not to accept the appointment (step S14). The teacher operates the teacher terminal 32 during the telephone interview to retrieve 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 it on the display unit of the teacher terminal 32. , You can see and confirm the displayed consultant information. As a result, the teacher can easily obtain the necessary information, so that the work efficiency can be improved.

After that, if the teacher decides not to accept the appointment (NG in step S14), the person in charge of acceptance determines the possibility of accepting the appointment (step S15), and if there is no possibility of accepting the appointment, the appointment work is canceled. Yes (end). On the other hand, when the teacher determines to accept the appointment (OK in step S14), the person in charge of processing operates the input unit of the processing terminal 33 in the office system 30 to input or update the appointment information (step S16). When the teacher decides to accept the job, the clerk or the like is instructed to send the document (for example, the contract for delegation) if necessary, such as not accepting the required document (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 according to the input operation of the processing person on the processing terminal 33. The appointment information input or updated by the processing terminal 33 is stored in the storage unit 12. When inputting (or updating) this appointment information, for example, "list of consultants: consultant basics", "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 person in charge of processing. It should be noted that part of the appointment information (for example, client information) is inherited from the consultant information.

The accounting staff operates the input unit of the accounting terminal 34 in the office system 30 to input or update the acceptance information as necessary, such as when inputting or updating the 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) related to the input or update of the appointment information in accordance with the input operation of the accounting person on the accounting terminal 34. The appointment information input or updated by the accounting terminal 34 is stored in the storage unit 12. In inputting (or updating) the appointment information, for example, information and functions related to “case information: deposit/withdrawal information” and the like 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 and grasps various kinds of information relating to debt customer management as necessary, for example, when searching for the cause of not having been temporarily accepted (step). S19). The various 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 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 accordance with an input operation of the administrator on the management terminal 35, and stores, for example, a memory. Various pieces of information such as progress confirmation/daily/cumulative number of consultations, number of provisional appointments/rate, number of regular appointments/rate, etc. are read from the department 12 and transmitted to the management terminal 35. As a result, the administrator can easily grasp various kinds of information related to debt customer management, so that business efficiency can be improved. It is also possible to transfer the read information to a separately managed system.

(2. Settlement preparation)
As illustrated in FIG. 8, the person in charge of accepting operates the input unit of the accepting terminal 31 in the office system 30 to supplementally update the pre-accepting information as needed (eg, when updating the pre-accepting information) (step S21).

As the negotiation start, the person in charge of processing operates the input unit of the processing terminal 33 in the office system 30 to create an intervention notice (document) and saves it in the storage unit of the processing terminal 33 (step S22), and thereafter Then, an intervention notice is sent and a transaction history is requested by FAX (step S23). In response to the request from the office, the trader sends the transaction history to the office by fax, mail, mail or the like (step S24). The person in charge of processing receives the transaction history (information) from the trader, operates the input unit of the processing terminal 33 based on the received transaction history, performs recalculation 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) related to the input and update of the debt status in accordance with the input operation of the person in charge of processing 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, information and functions related to, for example, "creditor information: addition of borrower creditor", "creditor information: borrower creditor details", "creditor information: negotiation record", etc. are processed. The information is provided to the terminal 33 and the corresponding information is input by the person in charge of processing.

The accounting staff starts the payment management (monthly loop until reward money is accumulated), operates the input unit of the accounting terminal 34 in the office system 30, and receives the deposit CSV (an example of deposit information) from the internet banking system 22. The information is acquired and loaded into the cloud service system 10 (step S27), and the presence/absence of a deposit is confirmed by looking at the deposit information displayed on the display unit of the accounting terminal 34 based on the deposit CSV (step S28).

If the accounting person determines that there is a deposit (YES in step S28), he/she operates the input unit of the accounting terminal 34 to manage the deposit information (step S29). The negotiation is permitted (step S30). In addition, as a procedure for allocating the full amount of remuneration including a schedule, for example, first, deposit money is accumulated and it is determined whether or not the person has a payment amount. The starter fee + office fee = amount received at the time of appointment, reward = amount received when settling, after accounting for these amounts, the accountant transfers each expense from the deposit account.

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) related to the management of deposit information in accordance with the input operation of the accounting staff 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: deposit/withdrawal information”, “payment management: deposit information search”, etc. are provided to the accounting terminal 34. To be done.

On the other hand, when the accounting person determines that there is no deposit (NO in step S28), the accountant performs a deposit reminder work to the client (step S31). In this deposit reminder operation, the accountant will call the client by telephone if "1.1 times unpaid" and write a warning to the client if "2.2 unpaid". In the case of “3. Not yet paid within 2 weeks after the document was sent”, a notice of resignation was sent, and in the case of “4. No payment even after 1 to 2 weeks from the notice of resignation”, a lawyer Resign with the permission of and send notice of resignation to the client or the contractor.

In response to the aforementioned resignation decision, the person in charge of operation operates the input unit of the processing terminal 33 in the office system 30 to reflect the resignation information (step S32), and disassembles the book concerning the client (step S33).

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 resignation processing in response to the input operation of the processing person on the processing terminal 33. The resignation information input by is stored in the storage unit 12. In the resignation process, for example, "case information: trust status", "creditor information: progress information", "case information: document preparation", "case information: account information", "case information: deposit/withdrawal information", "case" Information: information and functions related to "preparation of settlement statement" are provided to the processing terminal 33, and the corresponding information is input by the person in charge of processing.

The administrator operates the input unit of the management terminal 35 in the office system 30 as necessary when managing the deposit/withdrawal sales information, and is one of various types of information relating to debt customer management. The money/deposit/withdrawal sales information is managed (step S34). The 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 sees and confirms the various 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) relating to deposit/withdrawal/sales sales management in response to an administrator's input operation on the management terminal 35. As an example, the deposit/withdrawal sales information is transmitted to the management terminal 35. In deposit/withdrawal sales management, for example, information and functions related to “account management: account information search” are provided to the management terminal 35.

(3. Settlement negotiations)
As shown in FIG. 9, the person in charge of processing confirms the content of the settlement proposal to the client (step S41) as the start of settlement negotiations (repeating the same work until the entire settlement), and presents the settlement proposal to the trader (creditor). Yes (step S42). The trader also presents the settlement proposal according to the settlement proposal from the office (step S43). The person in charge of processing judges whether or not the negotiation based on the settlement proposal is broken (step S44), and when it is judged that the negotiation is broken (YES in step S44), shifts to court correspondence (step S45).

When the teacher moves to court correspondence (step S45), the teacher starts court correspondence and operates the input unit of the teacher terminal 32 in the office system 30 to manage the trial progress (step S46). In addition, the frequency of the trial itself is low, and the trial management is conducted with a view to bankruptcy revitalization.

The processing unit 11 of the cloud service system 10 provides the teacher terminal 32 with information and functions (for example, various screens and function menus) related to trial progress management according 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, the teacher terminal 32 is provided with information and functions related to “creditor information: information on lawsuits” and the like, and information corresponding to them is input by the teacher.

The accounting staff operates the input unit of the accounting terminal 34 in the office system 30 and manages the court costs according to the court response by the teacher (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 trial accounting management to the accounting terminal 34 according to the input operation of the accounting staff on the accounting terminal 34. The trial accounting information input or updated by 34 is stored in the storage unit 12. In the trial accounting management, for example, information and functions related to “account information: actual cost registration” are provided to the accounting terminal 34, and the corresponding information is input by the accounting staff.

On the other hand, in step S44 described above, when the person in charge of processing determines that the negotiation has not broken down (NO in step S44), it makes a final confirmation to the client (step S48). In the final confirmation, the settlement contents are confirmed to the client, for example, the amount of refund, the date of refund, lump-sum/split in the case of overpayment, and the amount of repayment, the number of repayments, interest, negligence agreements, etc. Be seen.

If the client is not satisfied with the settlement proposal in the final confirmation (NG in step S48), the processing person renegotiates with the trader (step S49). On the other hand, if the client is satisfied with the settlement proposal in the final confirmation (OK in step S48), he or she operates the input unit of the processing terminal 33 in the office system 30 to input or update the settlement information by concluding the settlement ( 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 the settlement conclusion according to the input operation of the person in charge of processing on the processing terminal 33. The settlement information input or updated by is stored in the storage unit 12. In the settlement agreement, for example, "creditor information: progress status", "creditor information: summary information", "case information: document preparation", "case information: account information", "case information: deposit/withdrawal information", etc. Relevant information and functions are provided to the processing terminal 33, and corresponding information is input by the person in charge of processing.

After that, the person in charge of processing prepares and sends the 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). Note that the copy of the settlement document will be sent to the client by email or mail. Further, in the company-wide settlement, the next step does not go until the company-wide settlement is completed, that is, until the remuneration is collected for the entire company. However, in the case of advance settlement (when threatening to send notification of intervention), there are cases where settlement is settled before compensation is accumulated, and there are cases where proxy transfer is started before the entire company is collected.

When the person in charge of processing determines that there is proxy remittance (Yes in step S53), it guides the requester in regard to proxy remittance (step S54). This proxy remittance guide, etc. is sent to the client by e-mail or mail. On the other hand, if it is determined that there is no proxy remittance (No in step S53), the process proceeds to the payment preparation by the accounting person.

The accounting staff operates the input unit of the accounting terminal 34 in the office system 30 to register or update the proxy information (step S55), and when the company-wide repayment is completed, prepares for payment (step S56). Remittance is sent to a business operator (creditor) based on the information on proxy payment (remittance by proxy). Note that this proxy remittance will be described in detail later in (4. Proxy Remittance).

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 proxy management according to the input operation of the accounting staff on the accounting terminal 34. The proxy information input or updated by 34 is stored in the storage unit 12. In the transfer management, for example, "Creditor information: Sorting information", "Case information: Account information", "Case information: Deposit/withdrawal information", "Bank withdrawal processing: Zengin data creation/acquisition", etc. 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, such as when managing the delegation record, and displays the delegation record information, which is one of various types of information relating to debt customer management. Manage (step S57). The proxy service record 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 sees and confirms the information. For example, the manager determines where to take the sales axis (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, function menus, etc.) relating to the proxy management according to the input operation of the management terminal 35 by the administrator. In the proxy transfer management, for example, the management terminal 35 is provided with information and functions related to “management of number of remittances”, “management of proxy transfer conversion rate” and the like.

(4. Transfer by proxy)
As shown in FIG. 10, the client (debtor) deposits money into the proxy account of the office (step S61). The accounting staff operates the input unit of the accounting terminal 34 as the start of proxy remittance (monthly loop until payment is paid), acquires the deposit CSV (an example of deposit information) from the Internet banking system 22, and then stores it in the cloud. It is taken into the service system 10 (step S62), and the presence/absence of deposit is confirmed by looking at the deposit information displayed on the display unit of the accounting terminal 34 based on the deposit CSV (step S63).

When it is determined that there is no deposit (NG in step S63), the accountant performs a deposit reminder work for the client (step S64). In this deposit reminder operation, the accountant will call the client by telephone if "1.1 times unpaid" and write a warning to the client if "2.2 unpaid". In the case of “3. Not yet paid within 2 weeks after the document was sent”, a notice of resignation was sent, and in the case of “4. No payment even after 1 to 2 weeks from the notice of resignation”, a lawyer Resign with the permission of and send notice of resignation to the client or the contractor.

In response to the resignation decision described above, the person in charge of processing operates the input unit of the processing terminal 33 in the office system 30 to reflect the resignation information (step S65) and disassembles the book concerning the client (step S66).

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 resignation processing in response to the input operation of the processing person on the processing terminal 33. The resignation information input by is stored in the storage unit 12. In the resignation process, for example, "case information: trust status", "creditor information: progress information", "case information: document preparation", "case information: account information", "case information: deposit/withdrawal information", "case" Information: information and functions related to "preparation of settlement statement" are provided to the processing terminal 33, and the corresponding information is input by the person in charge of processing.

On the other hand, if the accounting person determines that there is a deposit (OK in step S63), he/she operates the input unit of the accounting terminal 34 to manage the deposit information (step S67) and creates remittance data (step S68). ), the remittance is arranged (step S69), the remitted data is reflected (step S70), and when the company-wide payment is completed (step S71), the process proceeds to the settlement process (step S72). In the remittance arrangement, based on the remittance data, the Internet banking system 22 is instructed to make a total transfer, and the remittance is sent to the business operator (creditor).

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 remittance management in accordance with the input operation of the accounting person on the accounting terminal 34. The remittance information input by is stored in the storage unit 12. Remittance management is related to, for example, "case information: account information", "case information: deposit/withdrawal information", "bank withdrawal processing: creation of remittance data", "bank withdrawal processing: receipt of remitted data", etc. Information and functions are provided to the accounting terminal 34, and 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, such as when managing the delegation record, and displays the delegation record information, which is one of various types of information relating to debt customer management. Manage (step S73). The proxy service record 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 sees and confirms the information. For example, the manager determines where to take the sales axis (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, function menus, etc.) related to the transfer management according to the input operation of the administrator on the management terminal 35. In the proxy transfer management, for example, the management terminal 35 is provided with information and functions related to “management of number of remittances”, “management of proxy transfer conversion rate” and the like.

(5. Settlement processing)
As shown in FIG. 11, the accounting staff operates the input unit of the accounting terminal 34 in the office system 30 to start the settlement procedure, create a business report (step S81), and create a settlement statement ( In step S82, the set of documents is sent to the requester (step S83), and the deposit is settled (step S84).

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) related to deposit settlement in accordance with an input operation of an accounting person on the accounting terminal 34. The deposit information input by 34 is stored in the storage unit 12. In the deposit settlement, for example, information and functions related to “requester information: account information”, “requester information: deposit/withdrawal information”, etc. are provided to the accounting terminal 34, and the corresponding information is provided by the accounting staff. Is entered.

After that, the accounting staff performs filing work such as file discarding (step S85), and operates the input unit of the accounting terminal 34 in the office system 30 to perform business end processing (step S86).

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) related to the business end processing in accordance with the input operation of the accounting person on the accounting terminal 34. The work end information input by 34 is stored in the storage unit 12. In the business end processing, for example, information and functions related to “case information: acceptance status”, “creditor information: progress status”, etc. are provided to the accounting terminal 34, and the corresponding information is input by the accounting officer. It

(Importing deposit/withdrawal information to the cloud service system)
Next, a flow of fetching deposit/withdrawal information from the internet banking system 22 into the cloud service system 10 will be described with reference to FIGS. 12 and 13.

As shown in FIG. 12, API cooperation between the internet banking system 22 and the cloud service system 10 enables the cloud service system 10 to directly receive deposit/withdrawal information (for example, CSV data) from the internet banking system 22.

Regarding deposit processing, the client (debtor) transfers the amount of the agreement to the account (proxy account) designated by the office every month. After confirming the deposit, the accounting staff at the office operates the input unit of the accounting terminal 34 in the office system 30 to directly receive the deposit information (for example, CSV data) from the Internet banking system 22 through the API cooperation in the cloud service system. Take in 10.

The deposit information is deposited data indicating the deposit amount of each debtor who deposits in 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 in the information for each debtor stored in the storage unit 12. That is, the information for each debtor is updated based on the deposit information, or the deposit information is added to the information for each debtor. Note that the reflection includes updating (or inputting) information, adding information (for example, storing the information in association with the information for each debtor), and the like.

Regarding the withdrawal processing, the accounting staff 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 is immediately performed based on the remittance information, and therefore the process directly shifts to the confirmation process. In the confirmation processing, the cloud service system 10 receives withdrawal 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 amount of remittance for each creditor that is remitted 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 remittance data indicating the withdrawal amount for 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 in the information for each debtor stored in the storage unit 12. That is, the information for each debtor is updated based on the withdrawal information. That is, the information for each debtor is updated based on the withdrawal information, or the withdrawal information is added to the information for each debtor.

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

Regarding deposit processing, the client (debtor) transfers the amount of the agreement to the account (proxy account) designated by the office every month. After confirming the payment, the accounting staff at the office operates the input unit of the accounting terminal 34 in the office system 30 to output the payment information (for example, CSV data) from the Internet banking system 22 to the accounting terminal 34, The deposit information is imported from the accounting terminal 34 and imported into the cloud service system 10. The deposit information is the deposited data, as described above.

Regarding the withdrawal processing, the accounting staff of the office operates the input unit of the accounting terminal 34 in the office system 30 to send 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. After the remittance to the creditor is completed, the accounting staff outputs the withdrawal information (for example, CSV data) from the internet banking system 22 to the accounting terminal 34, and the withdrawal information is output from the accounting terminal 34 to the internet banking system 22. Import and import to and confirm withdrawal. Similar to the above, the remittance information is remittance data, and the withdrawal information is remittance completed data.

As described above, there are the direct capture method by API cooperation shown in FIG. 12 and the indirect capture method other than API cooperation shown in FIG. In the direct capture method, deposit/withdrawal information is directly transmitted/received between the cloud service system 10 and the internet banking system 22, whereas in the indirect capture method, it is transmitted/received via the accounting terminal 34. That is, in the indirect capture method, it is necessary to temporarily capture the deposit/withdrawal information from the internet banking system 22 into the accounting terminal 34. Therefore, the indirect import method is a method in which the work efficiency is lower than that of the direct import method. Therefore, in order to improve the work efficiency related to debt consolidation, it is preferable to use the direct capture method by API cooperation.

<Screen related to debt customer management>
Next, a screen regarding debt customer management, that is, a screen displayed on a user terminal (each terminal 31 to 35) used by a user such as a person in charge of acceptance, a teacher, a person in charge of processing, a person in charge of accounting, an administrator will be described. .. The screens of FIGS. 14 to 34 are merely examples, and are not limited. These images are provided from the cloud service system 10 to the user terminal. Also, 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 appointment)
As shown in FIG. 14, when the “consultant list” in the pre-acceptance menu is clicked, a pre-acceptance search screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of acceptance) operates the input unit of the user terminal while looking at the screen, and inputs information in 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 search by entering any one of the consulter number, the consultant name, and the telephone number. You can search for the consultant's name by entering either first name, last name, or kana. Only in the telephone number search, if there is no corresponding number in the target, a new registration screen opens. In addition, you can exclude test inquiries (exclude test email), exclude accepted (exclude items with this appointment date entered) and return documents (exclude items with entered document return date), only temporarily save (temporary saving items) ) Can be used as a search target. Further, it is also possible to search by the acceptance status, 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. It is possible to combine and use each search item, and narrow down by multiple conditions such as the person in charge and the status.

(New registration/edit screen)
As shown in FIG. 15, when “Consultant new 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. A user (for example, a person in charge of acceptance) operates the input unit of the user terminal while looking at the screen, and inputs information in necessary items. As shown in FIG. 15, the new registration/edit screen is for new registration of consultant, acceptance status, income and expenditure, and as shown in FIG. 16, borrowing status, correspondence policy/important matter, correspondence/escalation registration, correspondence/escalation. It has various items such as history. Since this new registration/edit screen cannot be displayed on one screen of the display unit, the user scrolls to see the entire screen.

Although there are items such as first name (last name)/first name (first name) and person in charge in the new registration of consultant (see FIG. 15), first name (last name)/first name (first name), type, advertisement, search word (not shown) Is a required item. Regarding temporary storage, it is possible to store even if the above-mentioned required items have not been input. However, only the name is required.

The appointment status (see FIG. 15) includes items such as provisional appointment date, document return date, appointment date, and end date.

With respect to 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 expenditures other than the above, there is a comment column for each item. There are also items for total income, total expenditure, and deduction surplus (all not shown), and when each of the above items is entered, the amount is automatically calculated (total income = monthly income + income other than the above, Total expenditure = each expenditure item + expenditure other than the above, deducted surplus = total income-total expenditure).

In the borrowing situation (see FIG. 16), there are items such as repayment/remaining bonds and trader name (branch name). When the number of divisions is entered in the division column, the amount of source is displayed in the source column by automatic calculation (source amount=remaining bonds/number of divisions). It is also possible to manually overwrite this amount of resources. The total funding is the expected repayment amount after the settlement, and is the total funding of the borrower with a check in the request target (□). Guarantees, collateral, high-priced products, and court-related supplementary items are entered in the supplementary fields. Total debt, total amount and current repayment amount (upper row) are total number of borrowers, total remaining bond amount and total monthly repayment amount, and total requested debt amount, total amount and current repayment amount (lower row) are subject to request ( □) is the total number of borrowers with a check mark, the total amount of remaining bonds, and the total monthly repayment amount, and the “(non-intervention) repayment amount” is the total repayment amount-request repayment amount.

In the correspondence policy/important items (see FIG. 16), there are items such as a correspondence policy, cost estimation, transfer agency service, and essential transaction, and further, there are respective items in the essential transaction item. Only when the correspondence policy is arbitrarily arranged, the amount is displayed by the automatic calculation in the cost estimation column. The calculation formula is (starting fee + settlement fee) x number of requests + office fees, and it is necessary to set the starting fee and settlement fee in advance. It is also possible to overwrite this cost estimate manually. If the transfer agency service is selected, the total amount of agency fees is automatically calculated, and the amount of the formula of the number of requested objects x agency fees is displayed. It is also possible to manually overwrite this amount. In addition, the amount of money is displayed by the automatic calculation every time in the cost reserve column. The calculation formula is the amount after discount/the number of divisions (rounded by 100 yen). The amount will be displayed automatically in the column of commission + total amount of resources. The calculation formula is the total amount of agency fees + the amount of monthly resources to be requested. There are also items such as the scheduled appointment, the scheduled appointment date, the interview method, and the lawyer in charge of the interview (all not shown).

In the correspondence/escalation registration (see FIG. 16), there are items such as a correspondence date and time and a correspondent. The logged-in user is initially displayed in the correspondent column. If you want to register as another correspondent, select the correspondent from the pull-down menu.

In the correspondence/escalation history (see FIG. 16), the history is displayed in ascending order of the correspondence date and time (old correspondence is at the bottom).

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

The case information creation screen is a screen for linking data before and after the appointment. On this screen, case information/creditor data after the appointment is newly created (this process can be performed only once). Consultant information is carried over to case information (information after acceptance). You can only click once on "Create new incident information". After the case information is created once, the “case information details”, which is a transition button to the case information after the appointment, is displayed. There are some differences in the item name and display format between the consultant information and the case information.

Regarding the creditor of the borrower (see FIG. 18), the registration before acceptance is free text, and the registration after acceptance is selection from the master. On the takeover screen, the processing unit 11 estimates and displays the creditors registered in the creditor master from the registration contents before the appointment. As Example 1, before acceptance: aaa→After acceptance: aaa Co., Ltd., and in Example 2, before acceptance: bbb→After acceptance: Unknown (blank display). If the corresponding creditor is not displayed, select from the existing creditor pull-down or register with the creditor master.

(Top screen)
As shown in FIG. 19, when “TOP” in the post-acceptance menu is clicked, the 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) confirms necessary information by looking at the screen, or inputs information by operating the input unit of the user terminal.

The top screen is a screen for providing deposit/withdrawal schedule information and deposit/withdrawal record information. On this screen, the deposit schedule and the actual results, and the withdrawal schedule and the actual results for the past three days and the past one week from today are listed by the number and the amount. When an arbitrary number of items in the list or the amount is clicked, the screen changes to the detailed screen. As an example, when the planned number “93” of the top screen is clicked, the upper screen in FIG. 19 transits to the detailed screen which is the lower screen in FIG.

(Case information screen)
As shown in FIG. 20, when “incident information” in the post-acceptance menu is clicked, an incident 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) confirms necessary information by looking at the screen, or inputs information by operating the input unit of the user terminal.

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

As shown in FIG. 21, in the customer detail 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 showing the progress status regarding the selected incident information is displayed. The progress page is a tab page for providing the progress so that other departments can cooperate with each other like a message board. On this progress page, the progress status (latest information) for each work is displayed.

As shown in FIG. 22, when the “requester information tab” is clicked, a requester information page showing requester information regarding the selected case information is displayed. The requester information page is a tab page that manages information about the requester (debtor) and interactions with the requester. This client information page displays client information, dialogue records, client account information, and work information. In the client information column, the client's basic information such as name, contact information, and address is recorded. In the dialogue record field, a history of the interaction between the requester and the user (office) is left. In the client account information column, the client's basic remuneration, account information, and information regarding deposit are registered. Based on the information registered here, management of account information and automatic creation of money information are performed. Thereby, the work efficiency can be improved. Information such as the requester's work place and former work place is recorded in the work place column.

As shown in FIG. 23, when the "creditor information tab" is clicked, a creditor information page showing creditor information regarding the selected case information is displayed. The creditor information page is a tab page that provides a list of borrower creditor information regarding creditors who are borrowers of the client (debtor). On this creditor information page, the borrower creditor information, specifically, the debt status/progress status for each borrower creditor information is displayed. As a result, the user can grasp the debt status and progress status of each creditor. When the “reference” button in the list is clicked, the screen transitions to the borrower creditor details page (see FIG. 24).

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

As shown in FIG. 25, when the “document creation tab” is clicked, a document creation page showing document creation information regarding the selected case information is displayed. The document creation page is a tab page for generating a document (template) used for business. On this borrower creditor details page, the borrower creditor information of the document creation target and the document creation column are displayed. By registering a specified document in the document creation field, you can use the data in the system (client name, address, debt status, etc.) to create a document to be used for work with one button.

As shown in FIG. 26, when the “split payment plan tab” is clicked, a split payment page showing split payment information regarding the selected case information is displayed. The split repayment page is a tab page for simulating a repayment plan and creating/printing a repayment plan schedule for the client. On this split payment information page, the split payment plan is displayed. Specifically, when "acquisition of arrangement information of borrower" in the upper screen in FIG. 26 is clicked, a schedule table or a performance table is created as in the lower screen.

As shown in FIG. 27, when the “account information tab” is clicked, an account information page showing the client's account information regarding the selected case information is displayed. The account information page is a tab page for managing client account information. Although account information is displayed on this account information page, it is possible to manage reward allocation and proxy remittance. When a client (debtor) deposits money, the funds are automatically distributed to rewards and proxy remittances.

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

(Creditor information screen)
As shown in FIG. 29, when “creditor information” in the post-acceptance menu is clicked, a creditor 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) confirms necessary information by looking at the screen.

The creditor information screen is a screen for providing creditor information. On this screen, columns for creditor information search and search results are displayed. In the search results, a list of incident information is displayed. When the "confirm" button in the list is clicked, the screen changes to the customer detail screen (see FIG. 21).

(Account management screen)
As shown in FIG. 30, when “account management” in the post-acceptance menu is clicked, an account management screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of accounting) looks at the screen and confirms necessary information.

The account management screen is a screen for providing account management information and confirming how the account information subject has moved as a whole office. On this screen, columns for account information search and search results are displayed. In the search results, a list of incident information is displayed. The account list of the search results can be output in CSV format.

(Payment management screen)
As shown in FIG. 31, when “payment management” in the post-acceptance menu is clicked, a payment management screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of accounting) looks at the screen and confirms necessary information.

The deposit management screen is a screen for providing deposit information and managing the status of deposit (requester deposit, overpayment refund, etc.). On this screen, a column for deposit information search and search results are displayed. In the search results, a list of deposit schedule information and deposit execution information for each case is displayed. With this deposit management screen, it is possible to improve work efficiency such as pursuing non-payment. The deposit list of the search results can be output as CSV.

(Withdrawal management screen)
As shown in FIG. 32, when “withdrawal management” in the post-acceptance menu is clicked, a withdrawal management screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of accounting) looks at the screen and confirms necessary information.

The disbursement management screen is a screen for providing disbursement information and managing the status of disbursement (requester refund, proxy transfer, 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 withdrawal management screen, it is possible to improve business efficiency such as pursuing non-withdrawal. It should be noted that it is possible to output the withdrawal list of the search results as a CSV.

(Bank deposit processing screen)
As shown in FIG. 33, when “Bank deposit processing” in the post-acceptance menu is clicked, a bank deposit processing screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of accounting) views the screen and operates the input unit of the user terminal to input information (for example, select a file).

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

It should be noted that in FIG. 33, with respect to the receipt processing of the deposit information, the deposit information once retrieved from the Internet banking system 22 to the user terminal is transferred to the cloud service system 10 by an indirect capture method other than the above-mentioned API cooperation (see FIG. 13). Although the uploading is taken as an example, when the above-mentioned direct importing method by API cooperation (see FIG. 12) is adopted, by clicking the button, the direct deposit information from the Internet banking system 22 to the cloud service system 10 Can be captured.

(Bank withdrawal screen)
As shown in FIG. 34, when “Bank Withdrawal Processing” in the post-acceptance menu is clicked, a bank withdrawal processing screen is displayed on the display unit of the user terminal. A user (for example, a person in charge of accounting) checks the necessary information by looking at the screen, or inputs information by operating the input unit of the user terminal (for example, selection of a processing target).

The bank withdrawal processing screen is a screen for creating and importing withdrawal information. On this screen, the bank withdrawal processing column and the withdrawal search result are displayed. In the withdrawal search result, the remittance information as the withdrawal instruction information for instructing the bank to withdraw (for example, the case name, the expected withdrawal date, the client name, the creditor name, the withdrawal subject, the withdrawal amount, the processing target Etc.) is displayed in a list. This remittance information (withdrawal instruction information) is information for remitting (withdrawing) the amount of the arrangement from the proxy account of the office to the individual accounts of the plurality of creditors, and is transmitted to the internet banking system 22. It

Regarding the process of importing the remittance information (payment instruction information), as in the case of the deposit information described above, an indirect import method other than API cooperation is used to upload the remittance information from the user terminal to the Internet banking system 22. Alternatively, the remittance information may be directly fetched from the cloud service system 10 to the internet banking system 22 by a direct fetching method based on API cooperation.

Here, the debt consolidation case ends after a settlement has been established between the client (debtor) and the trader (creditor) about six months after the request. It is up to that point that the profession usually acts as an agent for the debtor and acts as a window with the creditor. After that, the debtor makes monthly payments according to the payment plan negotiated between the agent and the creditor. However, as a debtor, he longs for the professional business to continue to serve as a window. The reason for this is that if a lawyer or judicial scrivener enters between the debtor and the creditor, the debtor will not directly communicate with the creditor and the mental burden on the debtor will be reduced. In addition, when the debtor borrows from multiple creditors, the creditor usually makes a transfer to each creditor, but in the case of proxy payment (proxy transfer), the debtor pays all the repayments once a month. There is a point that it does not take time because the scholarship will transfer it to the creditor on your behalf by transferring it to the account of the business office. In addition, the repayment date may differ for each creditor, and there is no need to live after the repayment date. Furthermore, even if there is a delay in the repayment after the settlement, if the repayment is made on behalf of the creditor, the profession will first be contacted, so the contact from the creditor is fundamental. Since there is no need to come to Japan, the mental burden on the debtor can be reduced.

For this reason, the number of requests for debt consolidation cases is increasing at professional offices, but as professional offices increase the number of debtors who request monthly payments (proxy transfer) Because of the shortage and the inability to work, the debtor's request cannot be met. Generally, in debt consolidation cases, due to the nature of the business of managing debt customers and performing special tasks, business processing is complicated, and specialized payment agency operations such as proxy payment require specialized knowledge, Since it is difficult to secure physical personnel to handle the workload, it is required to improve the efficiency of operations related to debt consolidation.

Therefore, in this embodiment, the cloud service system 10 centrally manages information for each debtor regarding debt consolidation cases. The information for each debtor includes various information (for example, debtor information, debtor account information, case information, creditor information, etc.) input by the user's input operation to the user terminal (one of the terminals 31 to 35). The debt information, the negotiation record information, the trial progress information, the trial expense information, the remittance information, etc. are reflected, and further, various information (for example, deposit/withdrawal information) obtained from the external cooperation service system 20 is also reflected. As a result, the user can easily obtain the information for each debtor in which various information is reflected from the cloud service system 10, and thus the efficiency of business relating to debt consolidation can be improved. As a result, even if the number of debtors who request monthly repayment increases, it is possible for the professional business office to prevent the lack of manpower and the inability to work, and to receive a large number of requests to generate profits. Can be raised.

As described above, according to the embodiment, the cloud service system 10 provides the user (office) with information and functions related to debt consolidation. For example, various information for each debtor (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, deposit/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. As a result, the user can easily obtain various kinds of information for each debtor from the cloud service system 10, and thus it is possible to improve work efficiency related to debt consolidation.

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, since the deposit information is automatically reflected in the information for each debtor, the user does not need to perform data input work or import work relating to the deposit information, and the deposit information ( Since it is possible to obtain (paid data), it is possible to improve the efficiency of business related to debt consolidation. Further, since the cloud service system 10 can send the remittance information to the internet banking system 22, the user simply instructs the cloud service system 10 to send the remittance information after confirming the deposit, and the remittance information is sent to the internet banking system 22. Since it becomes possible to easily transmit the debt, it is possible to improve the efficiency of business related to debt consolidation.

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, since the withdrawal information is automatically reflected in the information for each debtor, the user does not need to perform data input work or take-in work relating to the withdrawal information, and the withdrawal information can be easily output from the cloud service system 10. Since it becomes possible to obtain money information (withdrawn data), it is possible to improve work efficiency related to debt consolidation.

<Other Embodiments>
In the above description, the debt customer management system 1 is applied to a system for a debtor from a financial institution, but the invention is not limited to this. For example, a debt caused by a traffic accident or another reason. It can also be applied to a system for persons.

Further, in the above description, various functions are provided in the cloud service system 10, but as the function, for example, a FAX (fax) transmission function can be provided. Normally, the user operates the user terminal to print a notification document or the like from the cloud service system 10 and manually performs FAX transmission to the related companies. However, when the cloud service system 10 is equipped with the FAX transmission function, the cloud service system 10 can directly transmit the notification document or the like to the related companies by FAX. As a result, it is possible to reduce manual labor, erroneous transmission, and cost reduction, and as a result, it is possible to improve work efficiency related to debt consolidation. For example, the cloud service system 10 may be used for an intervention notice (see steps S22 and S23 in FIG. 8), a resignation notice (see resignation due to unpaid money in FIGS. 8 and 10), and a settlement proposal presentation (see step S42 in FIG. 9). It is possible to use the FAX transmission function of.

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

The above-described embodiment 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 embodiment can take the form of a computer program product stored in a computer-usable (for example, computer-readable) storage medium. A computer-usable storage medium is, for example, any device capable of including, storing, transmitting, transmitting, and carrying a program used by a system, a device, a device, or the like. Examples of this storage medium include an electronic medium, a magnetic medium, an optical medium, a magneto-optical medium, an infrared medium, a semiconductor system (or a device or equipment), 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.

Although some embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other 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 the scope of equivalents thereof.

1 debt customer management system 10 cloud service system 11 processing unit 12 storage unit 20 external cooperation service system 21 call center system 22 Internet banking system 30 office system 31 accepting terminal 32 teacher terminal 33 processing terminal 34 accounting terminal 35 management terminal 40 communication network

Claims (7)

A debt customer management system in which a user terminal and a cloud service system are connected via a communication network,
The cloud service system includes a storage unit for storing information relating to debt consolidation associated with the debtor,
The user terminal displays information relating to the debt consolidation,
The cloud service system reflects information on deposit/withdrawal of a proxy account into which the debtor can deposit and withdraw to a creditor, in the debt consolidation information stored in the storage unit. Reflection means for
Means for reimbursing the debt consolidation costs from the proxy account,
Means for reflecting settlement information relating to settlement with each creditor in the debt consolidation information stored by the storage unit;
A debt customer management system, further comprising: means for determining whether or not to carry out settlement negotiations based on the amount of money deposited in the proxy account . The cloud service system is
A means for reflecting case information regarding a debt case for each of the obligors in the information relating to the debt consolidation stored in the storage section;
A means for reflecting creditor information regarding creditors for each of the debtors in the information relating to the debt consolidation stored in the storage unit,
Debt customer management system of claim 1, further comprising the information relating to the debt consolidation stored by the storage unit, and means for reflecting the debt information regarding debt for each of the creditor, the. The user terminal and the cloud service system are connected to an internet banking system via the communication network,
The cloud service system is
The debt customer management system according to claim 2, further comprising means for transmitting, to the Internet banking system, remittance information indicating a remittance amount for each obligee which is remitted from the proxy account for each obligee associated with the obligor. The cloud service system is
4. The debt customer management system according to claim 3, further comprising means for receiving, from the Internet banking system, deposit information indicating a deposit amount for each debtor deposited in a proxy account for each debtor. The cloud service system is
Information relating to the debt consolidation stored in the storage unit includes negotiation record information regarding a negotiation record with each obligor with a creditor, trial progress information regarding a trial progress for each obligor, and a court expense for each obligor. The debt customer management system according to any one of claims 1 to 4, comprising means for reflecting any or all of the court expense information regarding. The user terminal and the cloud service system are connected to an internet banking system via the communication network,
The cloud service system is
From the Internet banking system, means for receiving deposit information indicating the deposit amount for each debtor deposited in the proxy account for each debtor,
Means for transmitting to the internet banking system, remittance information indicating a remittance amount for each obligee of remittance from the proxy account for each obligee of the obligor;
The debt customer management system according to claim 1, further comprising: The cloud service system is
Means for receiving, from the Internet banking system, withdrawal information indicating an amount of withdrawal for each of the creditors, which has been withdrawn from the proxy account for each of the creditors;
Means for reflecting the withdrawal information on the information for each obligor stored by the storage unit,
The debt customer management system according to claim 6, further comprising: