Business assistance device, business assistance method, and business assistance program

Abstract

To reduce the burden of monitoring business of a fulfilment state of a previous loan condition.SOLUTION: An extraction unit extracts loan information with the same client identification number added thereto by referring to a storage unit that stores the loan information containing at least client identification number unique to a client to who money, an article or a service is loaned, a loan identification number added unique to each loan case for carrying out a loan, a scheduled completion date of a loan condition, and an unfulfillment reason of a loan condition on the basis of a client identification number contained in new loan application information when new loan application is filed. A determination unit determines whether there is an unfulfillment reason of loan information having a scheduled completion date of a loan condition passed in the extracted loan information. An output control unit controls the output of information enabling a loan when it is determined that the unfulfillment reason is contained in the loan information, and controls the output of information disabling a loan when it is determined that the unfulfillment reason is not contained in the loan information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent Document 1 (JP Patent Publication No. 2023-092435A) discloses a sales promotion support device that manages target budgets and actual results, as well as ongoing cases for achieving the budget. This sales promotion support device has a budget achievement forecast display means that displays information regarding the budget achievement forecast based on the budget and the amount of the ongoing case. In addition, this sales promotion support device has an ongoing case customer display means that displays customers of ongoing cases for which a sales promotion action schedule has not been registered, among the ongoing cases, and a sales promotion action registration means that registers sales promotion actions for the displayed customers. This makes it possible to support efficient sales activities aimed at achieving the budget that the sales representative initially targeted.

[0003] In this Patent Document 1, paragraph 0033 of the specification discloses a "status" that indicates the progress of a case. It discloses that there are various statuses that differ depending on the "case classification." For example, for a "general loan" (e.g., loans and various loans), it discloses that there are stages such as "in negotiation" starting from the date the case occurs, "in the approval process within the financial institution, pending approval application," "approved," and "loaned." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2023-092435 A Summary of the Invention [Problem to be solved by the invention]

[0005] In a business of lending money, goods, or services, for example, specific loan conditions, such as confirmation of required documents or periodic status checks, may be attached to each loan case. The lending institution monitors the fulfillment status of these loan conditions. When the lending institution next extends a new loan to a customer to whom a loan with loan conditions has been extended, the lending institution determines whether or not to grant the new loan based on the fulfillment status of the previously attached loan conditions.

[0006] In the past, in order to determine whether or not to grant a new loan, it was necessary to monitor the fulfillment of the loan conditions attached to the previous loan, and this monitoring work was a burden on the staff in charge, etc.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can reduce the burden of monitoring the fulfillment status of the previous loan conditions. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objective, the business support device of the present invention has an extraction unit that, when a new loan application is made, refers to a memory unit in which loan information including a unique customer identification number of a customer to whom money, goods, or services are loaned, a loan identification number uniquely assigned to each loan case for which a loan is made, a scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions, based on the customer identification number contained in the new loan application information, and extracts loan information to which the same customer identification number is assigned, a determination unit that determines whether or not there is a reason for non-fulfillment in the extracted loan information for loan information for which the scheduled completion date of the loan conditions has passed, and an output control unit that controls the output of information that allows the loan when it is determined that the loan information includes a reason for non-fulfillment, and controls the output of information that does not allow the loan when it is determined that the loan information does not include a reason for non-fulfillment.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention includes an extraction step in which, when a new loan application is made, an extraction unit refers to a memory unit in which loan information including at least a unique customer identification number of a customer to whom money, goods, or services are loaned, a loan identification number uniquely assigned to each loan case for which a loan is made, a scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions is stored, based on the customer identification number included in the new loan application information, and extracts loan information to which the same customer identification number is assigned; a determination step in which a determination unit determines whether or not there is a reason for non-fulfillment in the extracted loan information for loan information for which the scheduled completion date of the loan conditions has passed; and an output control step in which an output control unit controls the output of information that allows the loan when it is determined that the loan information includes a reason for non-fulfillment, and controls the output of information that does not allow the loan when it is determined that the loan information does not include a reason for non-fulfillment.

[0010] In addition, in order to solve the above-mentioned problems and achieve the objective, the business support program of the present invention causes a computer to function as an extraction unit that, when a new loan application is made, refers to a memory unit in which loan information including at least a unique customer identification number of a customer to whom money, goods, or services are loaned, a loan identification number uniquely assigned to each loan case for which a loan is made, the scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions, based on the customer identification number contained in the new loan application information, and extracts loan information to which the same customer identification number is assigned, a determination unit that determines whether or not there is a reason for non-fulfillment in the extracted loan information for loan information for which the scheduled completion date of the loan conditions has passed, and an output control unit that controls the output of information that allows the loan when it is determined that the loan information contains a reason for non-fulfillment, and controls the output of information that does not allow the loan when it is determined that the loan information does not contain a reason for non-fulfillment. Effect of the Invention

[0011] The present invention can reduce the burden of monitoring the status of fulfillment of previous loan conditions. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing a system configuration of a task support system according to an embodiment, and a hardware configuration of a task support device operated by an approver. [Diagram 2] FIG. 2 is a diagram illustrating an example of the approval request item table. [Diagram 3] FIG. 3 is a diagram showing an example of the opinion and comment table. [Figure 4] FIG. 4 is a diagram illustrating an example of the decision condition table. [Diagram 5] FIG. 5 is a diagram illustrating an example of the default condition table. [Figure 6] FIG. 6 is a diagram illustrating an example of the status case table. [Figure 7] FIG. 7 is a diagram illustrating an example of the status master. [Figure 8] FIG. 8 is a diagram showing a flow of the approval request item registration process (step S1) in the business support device. [Figure 9] FIG. 9 is a diagram showing the flow of application processing (step S2), approval processing (step S3), and decision condition registration processing (step S4) in the business support device. [Figure 10] FIG. 10 is a diagram showing a flow of the status update process (step S5) and the condition fulfillment confirmation process (step S6) in the task support device. [Figure 11] FIG. 11 is a diagram for explaining the operation of registering a new loan application. [Figure 12] FIG. 12 is a diagram for explaining the operation of registering a reason for default when registering a new loan application. [Figure 13] FIG. 13 is a diagram showing an example of the status case table before a new loan case is registered. [Figure 14] FIG. 14 is a diagram showing the status case table updated by registering a new loan case. [Figure 15] FIG. 15 shows how other loan applications for the same customer are searched for when a new loan application is made. [Figure 16]Figure 16 shows how, when a new loan application is made, it is detected that a reason for default has been registered for another loan application (previous loan application) for the same customer, and therefore the loan for the new loan application is approved (no loan error occurs). [Figure 17] FIG. 17 is a diagram showing how the status of the case table is updated to "approval in progress" indicating that the new loan case is waiting for approval by the approver because the new loan case does not result in a loan error. [Figure 18] FIG. 18 shows how other loan applications for the same customer are searched for when a new loan application is submitted. [Figure 19] Figure 19 shows how, when a new loan application is made, it is detected that no reason for default has been registered for another loan application (previous loan application) for the same customer, and therefore the loan for the new loan application is not approved (loan error). [Figure 20] FIG. 20 is a diagram showing a state in which the status information in the status case table is not updated from the previous status of "accepting" because a loan error has occurred in a new loan case. [Figure 21] FIG. 21 is a diagram showing how an approver selects a loan application in the "approval" status that he or she wishes to approve. [Figure 22] FIG. 22 shows how the status of the status case table is updated from "approval in progress" to "approved" as a result of approval by the approver. [Figure 23] FIG. 23 is a diagram showing how approval conditions are attached, if necessary, to a new loan application that has been approved. [Figure 24] FIG. 24 is a diagram showing how status information on the decision conditions set by the approver is registered in the status case table. [Diagram 25] FIG. 25 is a diagram showing the status case table before the person in charge fulfills the approval conditions imposed by the approver. [Figure 26] FIG. 26 is a diagram for explaining the registration of the completion of the fulfillment of the approval condition set by the approver. [Figure 27] FIG. 27 is a diagram showing how the status of the approval condition in the status case table is updated from "not reported" to "completion reported" upon registration of the completion of fulfillment of the approval condition. [Figure 28] FIG. 28 shows the status management screen and the status management table before the approver confirms the approval conditions. [Figure 29] FIG. 29 is a diagram showing how an approver confirms the completion of the fulfillment of the decision conditions and registers the completion date of the decision conditions in the decision conditions table. [Diagram 30] Figure 30 shows how, when an approver registers the completion date of a decision condition, the status of the decision condition in the status case table is updated from "Completion reported" to "Completed," and the display of the condition preparation corresponding to the decision condition that has become "Completed" is hidden on the status management screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] A business support system according to an embodiment of the present invention will be described in detail below with reference to the drawings. Note that the embodiment described below is an example in which the present invention is applied to a business support system that supports a money lending business. The present invention can also be applied to other business support systems that support, for example, the lending of goods or services, and is not limited to the following embodiment.

[0014] (overview) For example, in loan approval work, for large loans to corporations or repeated working capital, there are many cases where loan conditions such as confirmation of necessary documents or regular status checks are set by the sales staff before the loan is approved and executed. The contents of the set loan conditions are diverse.

[0015] Loans made when the loan conditions set for each loan case are not fulfilled are equivalent to fraudulent loans, and will be pointed out during inspections or audits. In addition, additional loans to customers who do not fulfill the loan conditions set must be prevented. In addition, if the management of loan conditions is not performed properly, measures must be taken to address the non-fulfillment of loan conditions.

[0016] For this reason, financial institutions need to monitor whether loan conditions are being met within the designated deadlines and, if not, the reasons for such non-compliance. However, such monitoring work places a burden on the staff.

[0017] For this reason, in the business support device of the embodiment, the status of the loan conditions is managed and displayed on the screen by both the grantor and the person in charge, thereby preventing the inconvenience of non-fulfillment of the loan conditions being overlooked. In addition, for customers with loan terms that have expired and have not been fulfilled, unless the reason for the default is registered, an error (loan not granted) will be displayed when applying for a loan from another lender, preventing further fraudulent lending.

[0018] (Hardware configuration) As shown in Fig. 1, the business support system of the embodiment is configured by connecting a business support device 1a of a financial institution staff member who applies for a loan request (loan request) and a business support device 1b of an approver of the financial institution who examines and approves the requested loan request, so that they can communicate with each other via a network 50. Each of the business support devices 1a and 1b operates based on a business support program stored in a storage unit 2, and when operated by the staff member, performs application processing for the loan request, and when operated by the approver, performs approval processing for the requested request.

[0019] In other words, the business support device of the embodiment operates as business support device 1a based on the business support program when operated by a person in charge, and operates as business support device 1b based on the business support program when operated by an approver. Note that, hereinafter, the business support device 1a and the business support device 1b may be collectively referred to as the business support device 1.

[0020] The hardware configurations of the business support device 1a and the business support device 1b will be described based on the business support device 1b operated by the approver. Note that since the configuration of the business support device 1a is the same as that of the business support device 1b, please refer to the description of the business support device 1b below.

[0021] The business support device 1b includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0022] The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive). The storage unit 2 stores a business support program that performs application processing for a request for approval case or approval processing for an applied request for approval case according to the operation of an operator who is a person in charge or an approver, as described above. The storage unit 2 also stores a request for approval case table 11, an opinion / comment table 12, a decision condition table 13, a default condition table 14, a status case table 15, and a status master 16.

[0023] In the approval case table 11, in order to identify each approval case, approval case information is stored which is associated with an approval case global unique identifier (approval case GUID) which is uniquely assigned to each approval case as shown in Figure 2, and a customer global unique identifier (customer GUID) which is uniquely assigned to each customer of each approval case.

[0024] In order to identify a request for approval to which a reason for non-compliance is attached, the opinion / comment table 12 stores opinion / comment information associated with the request for approval GUID and the reason for non-compliance, etc. attached to a specific request for approval, as shown in Figure 3.

[0025] As shown in Figure 4, the decision condition table 13 stores decision condition information in which the request GUID, decision condition GUID, expected completion date, registration date, registered user ID, completion report date, completion report user ID, and completion date are associated with each other to recognize the decision status.

[0026] The default condition table 14 is a table into which the decision condition information that is not fulfilled at the time of application for the approval request is copied from the decision condition table 13, and stores the default condition information including the approval request case GUID, decision condition GUID, original decision condition GUID, scheduled completion date, registration date, registered user ID, completion report date, completion report user ID, and completion date, as shown in Figure 5.

[0027] When the decision condition information is copied from the decision condition table 13 to the default condition table 14, the decision condition GUID stored in the decision condition table 13 is stored in the original decision condition GUID of the default condition table 14. In addition, a new decision condition GUID is assigned and stored for the default condition table 14 as the decision condition GUID of the default condition table 14.

[0028] In order to make it possible to identify the status indicating the progress of each process for each approval request case for each customer, the status case table 15 stores status information in which the customer GUID, case GUID, purpose category, status, and completion flag are associated with each other, as shown in Fig. 6. In the "case GUID" of this status case table 15, the approval request case GUID of the approval request case or the decision condition GUID of the decision condition is input.

[0029] In Fig. 6, the purpose category of "1" indicates that the status of the customer GUID and the approval case GUID is for an "approval case." Also, the purpose category of "2" indicates that the status of the customer GUID and the approval case GUID is for "preparation of conditions."

[0030] In the status master 16, as shown in FIG. 7, the status name for each status of each objective category is registered (stored).

[0031] The business support devices 1a, 1b are capable of sharing various information in the tables 11-15 and the status master 16 of each other's devices. That is, the business support device 1a for the person in charge can access various information in the tables 11-15 and the status master 16 of the business support device 1b for the approver, and the business support device 1b for the approver can access various information in the tables 11-15 and the status master 16 of the business support device 1a for the person in charge.

[0032] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, and thereby functions as a display control unit 21, an extraction unit 22, a discrimination unit 23, an output control unit 24, and a data generation unit 25, as shown in FIG. 1.

[0033] The display control unit 21 displays, via the output device 7, various screens such as a case registration screen, an opinion / comment screen, a status management screen, an application / approval screen, and a decision condition management input screen, which will be described later.

[0034] In this example, when a new loan application is made, the extraction unit 22 refers to the memory unit (various tables stored in the memory unit 2) that stores loan information including the unique customer identification number (customer GUID) of the customer to whom monetary financing (lending) is being provided, the loan identification number (approval case GUID) uniquely assigned to each loan case for which a loan is made, the planned completion date of the loan conditions (planned completion date shown in Figures 4 and 5), and the reason for non-fulfillment of the loan conditions (reason for non-fulfillment in Figure 3), based on the customer identification number contained in the new loan application information, and extracts loan information that has the same customer identification number.

[0035] The determination unit 23 determines whether or not there is a reason for default for any piece of loan information extracted whose scheduled completion date of the loan conditions has passed.

[0036] When the output control unit 24 determines that the loan information includes a reason for default, it controls the output of information that allows the loan (=updates the status in the status case table 15 in FIG. 6 to a loan available status).In addition, when the output control unit 24 determines that the loan information does not include a reason for default, it controls the output of information that does not allow the loan (=maintains the status in the status case table 15 in FIG. 6 as loan unavailable).

[0037] The loan information stored in the memory unit (each table) includes status information indicating the processing progress of each loan case (see Figure 6). When the determination unit 23 determines that the loan information contains a reason for default, the output control unit 24 updates the status information of the loan information to status information that allows the loan. Also, when the determination unit 23 determines that the loan information does not contain a reason for default, the output control unit 24 does not update the status information of the loan information, but maintains the previous status information that does not allow the loan.

[0038] Specifically, the "previous status information" is the status information of "accepting." When the determination unit 23 determines that the loan information includes a reason for default, the output control unit 24 updates the status information of the loan information from "accepting" to "approval pending," which indicates that the loan information is waiting for a decision by the approver on whether or not to grant the loan.

[0039] In addition, if the judgment unit 23 determines that the loan information does not include a reason for default, the output control unit 24 does not update the status information of the loan information, but maintains the status information as ``accepting.''

[0040] Furthermore, when the approver determines whether or not a loan can be granted, the extraction unit 22 extracts loan information that includes status information of "approval pending" from the loan information stored in the storage unit 2. In this case, when the approver determines that a loan can be granted based on the extracted loan information, the output control unit 24 updates the status information of "approval pending" attached to the extracted loan information to status information of "approved" indicating that the loan has been approved by the approver.

[0041] Furthermore, when approval conditions are specified by the approver for loan information updated to the status information of "approved", the data generation unit 25 generates approval condition information including the same customer identification information as the customer identification information included in the loan information updated to the status information of "approved", and the status information of the approval conditions specified by the approver. The output control unit 24 stores the generated approval condition information in the memory unit 2 (status case table 15).

[0042] The data generating unit 25 also generates decision condition information to which is added the completion report date input when the person in charge fulfills the decision condition specified by the approver. The output control unit 24 updates the status information of the decision condition information in the status case table 15 from "not reported" specified by the approver to "completion reported".

[0043] Furthermore, when the approver confirms that the person in charge has fulfilled the decision conditions, the data generation unit 25 adds the completion date of the decision conditions entered by the approver to the decision condition information in the status case table 15. The output control unit 24 updates the status information of the decision condition information from "Completion reported" to "Completed", which indicates that the fulfillment of the decision conditions has been completed. Furthermore, the output control unit 24 indicates the completion of the fulfillment of the decision conditions by non-output control of the output of the decision condition information including the status information of "Completion reported" to the output device (output device 7).

[0044] (Support operation for monitoring the status of fulfillment of loan conditions) In this embodiment of the business support system, in step S1 shown in FIG. 8, the business support device 1a for the person in charge performs a process of filing a request for approval of a loan, and in step S2 shown in FIG. 9, performs a request for approval process for the filed request.

[0045] The approver operates the approver's business support device 1b to perform approval processing for the requested decision-making matter in step S3 shown in FIG. 9, and to register the approval conditions in step S4.

[0046] When the approver approves the request (and registers the approval conditions), the status information for the request is updated in the business support device 1a for the person in charge, as shown in step S5 in Fig. 10. Also, if the approver has set (registered) approval conditions, the person in charge will report completion to indicate that the approval conditions have been fulfilled when the set approval conditions have been fulfilled. As a result, the status information for the request for approval for which approval conditions have been set is updated to "completion reported" in the business support device 1a for the person in charge.

[0047] The approver's business support device 1b determines whether the fulfillment of the set decision condition is completed based on whether the status information has been updated to "reported completion". If the status information has been updated to "reported completion", the approver's business support device 1b performs a condition fulfillment confirmation process in step S6 of FIG. 10 to update the status information from "reported completion" to "completed".

[0048] In the case of the business support system of the embodiment, the control unit 3 of each of the business support devices 1a and 1b functions as the display control unit 21 to the data generation unit 25 shown in Fig. 1 based on the business support program stored in the storage unit 2, and executes the processing of each step described above. Note that in this example, the display control unit 21 to the data generation unit 25 are described as being realized by software based on the business support program, but a part or all of the display control unit 21 to the data generation unit 25 may be configured by hardware to execute the processing of each step.

[0049] (Step S1) Specifically, in step S1, a process for issuing a request for approval of a request for approval applied for by a person in charge is first performed. In this process for issuing a request for approval of a request for approval, the person in charge operates the business support device 1a for the person in charge to specify the display of a case registration screen. As a result, the display control unit 21 displays the case registration screen illustrated in FIG. 11(a) via the output device 7.

[0050] This case registration screen has input fields for the branch number, customer number, approval case number, and various case information. The person in charge inputs the branch number of the branch that is applying for approval of the approval case, and the customer number. The data generation unit 25 automatically assigns an approval case GUID, generates a customer GUID based on the input customer number, and registers it in the approval case table 11 together with various case information.

[0051] Fig. 11(b) shows the approval case table 11 before the new approval case GUID and customer GUID are registered. When the new approval case GUID and customer GUID are generated by the data generation unit 25, the new approval case GUID and customer GUID are registered (stored) in the approval case table 11 by adding the new approval case information to the existing approval case information as shown in Fig. 11(c).

[0052] Figure 11 (b) shows an example in which a customer with a customer GUID of "0001-00035313" has previously received a loan with an approval case GUID of "0000-00000002", and this same customer has now requested a loan, so a approval case GUID of "0000-00000003" corresponding to this new request is generated and registered (stored) in approval case table 11.

[0053] Furthermore, when the person in charge has an opinion or comment on a new loan application, the person in charge operates the business support device 1a for the person in charge to specify display of the opinion / comment screen. As a result, the display control unit 21 displays the opinion / comment screen exemplified in FIG. 12(a) via the output device 7.

[0054] As an example, when loan conditions were set for the same customer who requested a new loan at the time of the previous loan and these loan conditions were not fulfilled, there may be a valid reason for the non-fulfillment of the loan conditions. In such a case, the person in charge inputs the reason for the non-fulfillment (or comment information) in the opinion / comment screen shown in FIG. 12(a).

[0055] When a reason for default is entered on the opinion / comment screen, the data generation unit 25 registers (stores) the reason for default in the opinion / comment table 12. Fig. 12(b) shows the opinion / comment table 12 before the reason for default is registered, and Fig. 12(c) shows the opinion / comment table 12 in a state in which a new reason for default has been registered by adding a new record to the record of the previous reason for default.

[0056] When the approval case information is registered in the approval case table 11 in this manner, the data generation unit 25 registers the customer GUID, approval case GUID, purpose category, status information, and completion flag corresponding to the approval case of the new loan request in the status case table 15. Figure 13(b) shows the status case table 15 before this information is registered, and Figure 14(b) shows the status case table 15 after this information is registered.

[0057] The record with the customer GUID of "0001-00035313" and the case GUID of "0000-00000003" shown in Fig. 14(b) corresponds to a new loan request approval case. In this case, since it is a new approval case, the data generation unit 25 sets the purpose category to "1: approval case" and the status information to "1: pending". At this stage, the loan approval has not been completed, so the completion flag is set to "0: incomplete".

[0058] The status of each such approval request case can be confirmed on the status management screen. That is, when the display of the status management screen is specified by the person in charge, the display control unit 21 refers to each record in the status case table 15, and displays the purpose category, status information, and number of records whose completion flag is other than "1: Completed" on the status management screen.

[0059] FIG. 13(a) is an example of a status management screen displayed with reference to the status case table 15 (FIG. 13(b)) before the status case information corresponding to the above-mentioned new approval case is registered. In the example of the status case table 15 shown in FIG. 13(b), the only record with a completion flag other than "1: Completed" (= completion flag is "0: Incomplete") is a record with a customer GUID of "0001-00353136" and an approval case GUID of "0100-00000012". The purpose category of this record is "2: Preparation for conditions" and the status information is "3: Not yet reported (in progress)". Therefore, the display control unit 21 displays "Preparation for conditions", "Not yet reported (in progress)", and "1 case" in the display columns for purpose category, status, and number of cases on the status management screen, as shown in FIG. 13(a).

[0060] In contrast, as shown in Fig. 14(b), when status case information corresponding to the above-mentioned new approval request case is registered in the status case table 15, one record with a completion flag of "0: incomplete" is added. Therefore, as shown in Fig. 14(a), the display control unit 21 displays "1: Approval request case", "1: Accepting", and "1 case" in the display columns for purpose category, status information, and number of cases on the status management screen based on the status case information of the newly added approval request case.

[0061] (Step S2) Next, in step S2, the business support device 1a for the person in charge processes the application for the issued approval request case as shown in Fig. 9. When processing this application, the person in charge operates the input device 6 to specify the display of the application / approval screen. When this display specification is made, the display control unit 21 displays, via the output device 7, the application / approval screen showing the approval request application information corresponding to the issued approval request case as exemplified in Fig. 15(a). The person in charge operates the "Apply" button on this application / approval screen.

[0062] When the "Apply" button on the application / approval screen is operated, the extraction unit 22 refers to the approval request case table 11 as shown in Fig. 15(b) and extracts approval requests with the same customer GUID as the customer submitting the current approval request. The example in Fig. 15(b) is an example in which approval requests with approval request case GUIDs of "0000-00000002" and "0000-00000003", which are assigned the same customer GUID of "0001-00035313", are extracted.

[0063] At the same time, as shown in FIG. 16(a), the data generation unit 25 refers to the approval condition table 13 based on the customer GUID of the customer currently submitting the approval request, and detects approval condition information for a "different approval request case" of the customer currently submitting the approval request, in which the set approval condition has not been fulfilled even though the scheduled completion date for the approval condition has passed. Then, the data generation unit 25 generates a record of non-fulfilled condition information by setting the decision condition GUID (0100-00000012) of the decision condition information detected from the decision condition table 13, where the set decision condition has been non-fulfilled, to the "original decision condition GUID (0100-00000012)", the approval case GUID to "0000-00000003" of the approval case for which an approval request is being made this time, and the decision condition GUID to a new "0200-00000099", and adds and registers the record in the non-fulfilled condition table 14 as shown in Figures 16(b) and 16(c).

[0064] In other words, when there is an approval request case for the same customer as the customer submitting the current approval request and for which the approval conditions have been defaulted, the data generation unit 25 generates a new record of default condition information by adding the new approval condition GUID (0200-00000099) and the approval condition GUID of the approval request case for which the approval conditions have been defaulted, which is the "original approval condition GUID (0100-00000012)", to the approval case GUID (0000-00000003) of the current approval request case, and registers it by adding it to the default condition table 14, as shown in Figures 16(b) and 16(c).

[0065] (If a reason for non-compliance is added) In addition, the determination unit 23 refers to the opinion / comment table 12 shown in Fig. 16(d) to determine whether or not a reason for non-performance has been assigned to the current approval request item. In this example, the reason for non-performance assigned to the current approval request item (approval request item GUID: 0000-00000003) is the same reason for non-performance assigned to another approval request item (approval request item GUID: 0000-00000002) of the same customer.

[0066] In other words, if the reason for non-fulfillment of the current approval request is detected by referring to the opinion / comment table 12, it means that the approval conditions set for other approval requests of the same customer are not fulfilled, but there is a valid reason for the non-fulfillment. Therefore, the current approval request can be submitted for approval.

[0067] When the reason for non-performance attached to the current approval request item is detected in this way, the data generation unit 25 updates the status information of the currently applied status item information in the status item table 15, in which the customer GUID is "0001-00035313" and the approval request item GUID is "0000-00000003", from "1: Accepting" to "11: Approval in progress" as shown in Figures 17(b) and 17(d). As a result, when the status management screen is displayed, the display control unit 21 updates the status of the approval request item from "Accepting" shown in Figure 17(a) to "Approval in progress" as shown in Figure 17(c) and displays it.

[0068] (If no reason for non-compliance is given) On the other hand, if the reason for non-fulfillment of the approval conditions is not added to the current approval request, the current approval request is for a customer whose approval conditions have been non-fulfilled without a valid reason, so the request becomes an unapprovable approval request and the status information in the status case table 15 is not updated.

[0069] That is, as shown in FIG. 18(a), an application for approval of the current approval request is made, and as shown in FIG. 18(b), approval request information including the approval request GUID of the same customer as the customer of the current approval request is detected from approval request table 11.

[0070] 19(a), in the decision condition table 13, there exists decision condition information in which the decision condition is not fulfilled even after the scheduled completion date for the same customer as the current approval request case, and based on this decision condition information, non-fulfillment condition information corresponding to the current approval request case is generated and stored in the non-fulfillment condition table 14, as shown in Fig. 19(b) and Fig. 19(c). Then, the discrimination unit 23 refers to the opinion / comment table 12 based on the approval request case GUID of this non-fulfillment condition information, but it is assumed that the reason for non-fulfillment is not registered, as shown in Fig. 19(d).

[0071] If the reason for default is not registered, it means that the settlement conditions set for the previous loan to the same customer as the current request case have not been fulfilled. Therefore, it is not desirable to provide further loans while the settlement conditions remain in default.

[0072] In this case, the data generating unit 25 maintains the status in the status case table 15 as the same "1: Accepting" before and after the registration of the status case information shown in Figures 20(b) and 20(c). As a result, even when the status management screen is displayed, the display control unit 21 maintains the display of the status as "Accepting" as shown in Figures 20(a) and 20(c).

[0073] In this way, when the reason for non-fulfillment is not registered in the opinion / comment table 12, the status information in the status case table 15, which indicates the progress of the client's request for approval, is maintained at "Accepted", thereby indicating that a non-fulfillment condition exists for the client. This eliminates the need to periodically monitor the fulfillment of the conditions.

[0074] (Step S3) Next, in step S3, the approver uses the approver's business support device 1b to carry out approval processing for the approval request submitted by the person in charge as described above. Specifically, when the approver specifies display of a status management screen, the display control unit 21 displays the status management screen shown in Fig. 21(a) via the output device 7. In the example shown in Fig. 21(a), it can be seen that there is "one" approval request with a status of "approval in progress."

[0075] Therefore, the approver selects the "approval pending" approval request case on the status management screen. This causes the display control unit 21 to refer to the status case table 15 shown in Fig. 21(b) and reads out status case information with the purpose category of "1: approval request case" and the status information of "11: approval pending." Then, the display control unit 21 displays, via the output device 7, an application approval screen in which approval request application information including the read out status case information is displayed in a specified area, as shown in Fig. 21(c).

[0076] The display of "Under approval" on the application approval screen means that the customer of the request has no defaulted approval conditions. In other words, as described above, when the reason for default is not registered in the opinion / comment table 12, the business support system of the embodiment maintains the status information of the status case table 15, which indicates the progress of the request for approval of the customer, as "Under approval", indicating that the customer has defaulted approval conditions. Therefore, by checking the status of "Under approval" displayed on the application approval screen, the approver can recognize that the customer of the request has no defaulted approval conditions, and can move smoothly to approval processing without periodically monitoring the status of condition fulfillment.

[0077] When an approval request item that is "in approval" is approved by an approver, the data generation unit 25 updates the status information of the approved status item information from "11: in approval" to "21: approved," as shown in Figures 22(b) and 22(d). As a result, the "in approval" status of the approval request item on the status management screen shown in Figure 22(a) is changed by the display control unit 21 to "approved," as shown in Figure 22(c), and displayed.

[0078] (Step S4) Next, if necessary, the approver can register decision conditions at the time of approval (decision conditions registration process). When registering decision conditions, the approver performs a designation operation to display the decision conditions management input screen. When this designation operation is performed, the display control unit 21 of the approver's business support device 1b displays the decision conditions management input screen shown in FIG. 23(a) via the output device 7.

[0079] The approver inputs the registration user ID, the registration date of the approval condition, the expected completion date of the approval condition, and the approval condition information into this approval condition management input screen, and operates the "Register" button. Note that the items of the completion report user ID, the completion report date, and the completion date on this approval condition management input screen are items that are input by the person in charge who fulfilled the approval condition via the person in charge's business support device 1.

[0080] When the "Register" button is operated, the data generation unit 25 generates a new record of decision condition information for the decision conditions of the approved approval request case, and registers it in the decision condition table 13 as shown in Figures 23(b) and 23(c). The record in the fourth row of Figure 23(c) is the newly generated record of decision conditions. In this example, since the approval request case GUID of the approved approval request case is "0000-00000003", the newly generated decision condition information is assigned the decision request case GUID of "0000-00000003", and the approval request case that is the subject of this decision condition is clarified.

[0081] The decision condition GUID is newly generated and assigned. The expected completion date, registration date, and registered user ID of this decision condition information are inputted from the expected completion date, registration date, and registered user ID inputted via the decision condition management input screen shown in FIG. 23(a), respectively.

[0082] Furthermore, when the "Register" button shown in Fig. 23(a) is operated, the data generation unit 25 generates a new record of status case information for the decision-making conditions, and adds and registers it in the status case table 15, as shown in Figs. 24(b) and 24(d). The record at the bottom of Fig. 24(d) is the newly added record of status case information for the decision-making conditions. In this example, the customer GUID entered is "0001-00035313", which is the customer GUID of the customer of the corresponding approval request case.

[0083] In addition, the newly created approval condition GUID "0100-00000013" (see Figure 23(c)) is entered as the case GUID. In addition, the purpose category becomes "2: Condition preparation" and the status becomes "1: Not reported (not arrived)" (see Figure 7).

[0084] By adding new status case information for the decision-making conditions in this way, when the status management screen is displayed, the display control unit 21 will display a status management display indicating that there is "one" decision-making condition (purpose category: condition preparation) with a status of "unreported (not arrived)", as shown in Figures 24(a) and 24(c).

[0085] (Step S5) Next, as shown in Fig. 25(a) and Fig. 25(b), when the person in charge fulfills the decision conditions set by the approver, he / she operates the business support device 1a for the person in charge to specify the fulfilled decision conditions in order to register the fulfillment details. When this specification is made, the display control unit 21 of the business support device 1 for the person in charge displays a decision conditions management input screen corresponding to the specified decision conditions via the output device 7, as shown in Fig. 26(a). The person in charge enters the completion report user ID of the person in charge who will make the completion report and the completion report date of the decision conditions into this decision conditions management input screen, and operates the "Register" button.

[0086] When the "Register" button is operated, the data generation unit 25 of the business support device 1a for the person in charge enters the completion report user ID and the completion report date of the decision condition entered by the person in charge via the decision condition management input screen into the completion report user ID input field and the completion report date input field of the decision condition in the record of the target decision condition information in the decision condition table 13, as shown in the bottom row record (record in the fourth column) of Figures 26(b) and 26(c), respectively.

[0087] Furthermore, when the "Register" button is operated, the data generation unit 25 of the business support device 1a for the person in charge updates the status information of the record of the relevant status case information at the bottom row in the status case table 15 from "1: Not reported (not yet arrived)" to "11: Reported (not yet arrived)" as shown in Figures 27(b) and 27(d). As a result, when the status management screen is displayed, the display control unit 21 updates the status of the approval condition for which completion of fulfillment has been reported to "Reported (not yet arrived)" and displays it as shown in Figures 27(a) and 27(c).

[0088] (Step S6) Next, when the fulfillment of the decision condition is reported in this way, the approver confirms and completes the decision condition (condition fulfillment confirmation process). FIG. 28(b) shows the status case table 15 in which the status information has been updated by the report of the completion of the fulfillment, and FIG. 28(a) shows the status management screen reflecting this updated content. When the approver confirms the fulfillment content, the approver operates the approver's business support device 1b and specifies the decision condition for which the completion of the fulfillment has been reported. As a result, the display control unit 21 of the approver's business support device 1b displays, via the output device 7, the decision condition management input screen corresponding to the decision condition for which the completion of the fulfillment has been reported, as exemplified in FIG. 29(a). At this stage, the approver inputs the date on which the fulfillment was confirmed as the "completion date" into the decision condition management input screen shown in FIG. 29(a) and operates the "register" button.

[0089] When the “Register” button is operated, the data generation unit 25 inputs the completion date entered by the approver via the decision condition management input screen into the target decision condition information (in this example, the bottommost decision condition information) in the decision condition table 13, as shown in Figures 29(b) and 29(c).

[0090] In addition, when the “Register” button is operated, the data generation unit 25 updates the status information of the target status case information (in this example, the status case information at the bottom row) in the status case table 15 from “11: Reported (not yet arrived)” to “40: Completed,” as shown in Figures 30(b) and 30(d).

[0091] In the case of the business support system of the embodiment, the display control unit 21 hides the status management information marked "40: Completed" from the status management screen. The status management information marked "40: Completed" may be displayed on the status management screen. Therefore, when the status management screen is displayed, the status management information marked "40: Completed" is not displayed on the status management screen, as shown in Figs. 30(a) and 30(c).

[0092] This makes it possible to prevent the status management screen from becoming cluttered due to the display of "Completed" status management information.

[0093] (Effects of the embodiment) As is clear from the above description, the business support system according to the embodiment can provide the following effects.

[0094] 1. It will be no longer necessary to periodically monitor the fulfillment of conditions.

[0095] 2. When the fulfillment status of conditions is centrally managed using spreadsheet software, conventionally, it was necessary for the manager, such as the examiner, to inform the person in charge of a customer who has an unfulfilled condition that there is an unfulfilled condition. However, in the case of the business support system of the embodiment, the fulfillment status of conditions can be shared, so it is not necessary to inform the person in charge of a customer who has an unfulfilled condition that there is an unfulfilled condition.

[0096] 3. It will no longer be necessary for approvers to check whether there are any conditions that cannot be fulfilled when approving a request for approval.

[0097] In the above embodiment, the business support device 1a for the person in charge and the business support device 1b for the approver communicate with each other to share various information in each of the tables 11-15 to support the loan business. Alternatively, a business support program, each of the tables 11-15, and the status master 16 may be provided on a server device on a predetermined network, the business support program may be operated as a so-called Web application program, and the business support device 1a for the person in charge and the business support device 1b for the approver may access this server device and operate based on the business support program. Even in this case, the same effect as described above can be obtained.

[0098] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, and can therefore contribute to Goals 8 and 9 of the SDGs.

[0099] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of Goals 12, 13, and 15 of the SDGs.

[0100] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0101] [Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0102] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0103] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0104] Furthermore, with regard to the business support system, each of the components shown in the figures is merely a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0105] For example, the processing functions of the business support system, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support system as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD. This computer program is executed by being loaded into a RAM, and constitutes the control unit 3 in cooperation with the CPU.

[0106] In addition, the business support program of this business support system may be stored in another server device connected to the business support system via any network, and it is also possible to download all or part of it as needed.

[0107] The business support program for executing the process described in the present embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0108] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that achieves its function by working with a separate program, such as an OS. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading a recording medium in the business support system shown in the embodiment, as well as the installation procedure after reading.

[0109] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

[0110] The business support system may be configured with an information processing device such as a known personal computer device or a workstation, or may be configured with an information processing device connected to any peripheral device. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0111] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0112] The present invention is suitable for application to the lending business, which lends money, goods, services, and the like. [Explanation of symbols]

[0113] 1 Business support equipment 1a Work support equipment for personnel 1b Approver's work support device 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 11 Approval Case Table 12 Opinion / Comment Table 13 Approval Condition Table 14. Default Condition Table 15 Status Case Table 16 Status Master 21 Display control unit 22 Extraction part 23 Discrimination part 24 Output control section 25 Data Generation Division

Claims

1. an extraction unit which, when a new loan application is made, refers to a memory unit in which loan information including at least a unique customer identification number of a customer to whom a loan of money, goods, or services is made, a loan identification number uniquely assigned to each loan case in which a loan is made, a scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions, based on the customer identification number included in the new loan application information, and extracts loan information to which the same customer identification number is assigned; A determination unit that determines whether or not there is a reason for default for the loan information extracted, the loan information being past the scheduled completion date of the loan conditions; an output control unit that controls the output of information that allows the loan when it is determined that the loan information includes the reason for default, and controls the output of information that does not allow the loan when it is determined that the loan information does not include the reason for default; A business support device having the above configuration.

2. The loan information stored in the storage unit includes status information indicating the progress of processing for each loan item, the output control unit updates the status information of the loan information to status information that allows loaning when the determination unit determines that the loan information includes the reason for default, and does not update the status information of the loan information and maintains the previous status information that does not allow loaning when the determination unit determines that the loan information does not include the reason for default; 2. The business support device according to claim 1,

3. The previous status information was "accepting" status information, when the determination unit determines that the loan information includes the reason for default, the output control unit updates the "accepting" status information of the loan information to "approval pending" status information indicating that the approver is waiting for a decision on whether the loan can be granted, and when the determination unit determines that the loan information does not include the reason for default, the output control unit does not update the status information of the loan information and maintains the "accepting" status information; 3. The business support device according to claim 2,

4. The extraction unit extracts loan information including the status information of "approval" from the loan information stored in the storage unit when the approver determines whether or not the loan is approved, when the approver determines that the loan is possible based on the extracted loan information, the output control unit updates the status information of "approval in progress" attached to the extracted loan information to status information of "approval completed" indicating that the loan information has been approved by the approver; 4. The business support device according to claim 3,

5. a data generating unit that generates approval condition information including a customer identification number that is the same as the customer identification number included in the loan information updated to the status information of "approved" and status information of the approval condition specified by the approver when the approver specifies approval conditions for the loan information updated to the status information of "approved", The output control unit stores the generated decision condition information in the storage unit.

5. The business support device according to claim 4,

6. the data generation unit generates the decision-making condition information to which a completion report date inputted when the decision-making condition specified by the approver is fulfilled by a person in charge is added; the output control unit updates the status information of “not yet reported” specified by the approver in the decision condition information to status information of “completed report”; 6. The business support device according to claim 5,

7. the data generation unit adds a completion date of the approval condition input by the approver to the approval condition information when the approval condition is confirmed by the approver by the person in charge; the output control unit updates the status information of the decision condition information of "completion reported" to status information of "completed" indicating that the fulfillment of the decision condition has been completed, and controls the output of the decision condition information including the status information of "completion reported" to an output device to indicate the completion of the fulfillment of the decision condition; 7. The business support device according to claim 6,

8. an extraction step in which, when a new loan application is made, the extraction unit refers to a storage unit in which loan information including at least a unique customer identification number of a customer to whom money, goods, or services are loaned, a loan identification number uniquely assigned to each loan case in which a loan is made, a scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions, based on the customer identification number included in the new loan application information, and extracts loan information to which the same customer identification number is assigned; A determination step in which a determination unit determines whether or not there is a reason for default for the loan information whose scheduled completion date of the loan condition has passed in the extracted loan information; an output control step in which, when it is determined that the loan information includes the reason for default, the output control unit controls the output of information that allows the loan, and, when it is determined that the loan information does not include the reason for default, the output control unit controls the output of information that does not allow the loan; A business support method having the above-mentioned features.

9. Computer, an extraction unit which, when a new loan application is made, refers to a memory unit in which loan information including at least a unique customer identification number of a customer to whom a loan of money, goods, or services is made, a loan identification number uniquely assigned to each loan case in which a loan is made, a scheduled completion date of the loan conditions, and a reason for non-fulfillment of the loan conditions, based on the customer identification number included in the new loan application information, and extracts loan information to which the same customer identification number is assigned; A determination unit that determines whether or not there is a reason for default for the loan information extracted, the loan information being past the scheduled completion date of the loan conditions; functioning as an output control unit that, when it is determined that the loan information contains the reason for default, controls the output of information that allows the loan, and, when it is determined that the loan information does not contain the reason for default, controls the output of information that does not allow the loan; A business support program that features:

Images