Loan management device, loan management method, and loan management program
The loan management device and method address inefficiencies in determining case status changes by using a control unit and transition destination control master to automate case status transitions, enhancing screening efficiency and reducing review duplication.
Patent Information
- Application Number
- JP2023034543
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-03-07
- Publication Date
- 2025-10-22
- Estimated Expiration
- 2043-03-07
AI Technical Summary
Existing loan management systems struggle to automatically determine the destination of case status changes during operations like approval, return, or withdrawal, leading to complex screening work inefficiencies and duplication of reviews.
A loan management device and method that includes a control unit capable of accessing case data, a case status master, and a case status transition destination control master to automatically determine the transition destination of a case based on its current status and operation type, reducing duplication of reviews.
Enables efficient management of complex screening processes by automatically determining case status transitions, reducing duplication and improving business efficiency.
Smart Images

Figure 0007758696000001 
Figure 0007758696000002 
Figure 0007758696000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a loan management device, a loan management method, and a loan management program. [Background technology]
[0002] In the financial industry, loan screening procedures involve multiple stages, and each stage is handled by a different department and position, so it is necessary to properly manage the case status.
[0003] Previously, the case status would change with each operation, including approval, return, and withdrawal, and the destination of each case status was determined individually, making it difficult to respond to changes in business flow.
[0004] Patent document 1 describes a system for supporting loan operations, which includes a data recording means for recording loan application data related to loan applications, a progress status acquisition means for acquiring information indicating the progress of loan operations, a status information recording means for recording status information corresponding to the progress status information acquired by the progress status acquisition means in the database in association with the corresponding loan application data, an inquiry request receiving means for receiving an inquiry request for status information specifying the loan application data to be inquired from a terminal capable of communicating with the system, and a status sending means for reading from the database the status information recorded in association with the loan application data specified in the inquiry request received by the inquiry request receiving means, and sending it to the terminal that sent the inquiry request. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-279180 Summary of the Invention [Problem to be solved by the invention]
[0006] The system in Patent Document 1 centrally manages loan operations at financial institutions, enabling each branch of the financial institution and credit guarantee institution to grasp the progress of loan operations, but it cannot automatically determine the destination of the case status for each operation of approval, return, or withdrawal of the review, nor can it avoid duplication of reviews.
[0007] The present invention has been made in consideration of the above problems, and aims to provide a loan management device, a loan management method, and a loan management program that can automatically determine the destination of a case after an operation based on a combination of the case's current status and the type of operation, thereby enabling appropriate management of complex screening work and reducing duplication of screening. [Means for solving the problem]
[0008] In order to solve the above-mentioned problems and achieve the objectives, the loan management device of the present invention is a loan management device that has a control unit and is able to access case data including case number and case status, approval history data including case status history, a case status master in which case status names and case status codes are linked, and a case status transition destination control master in which case statuses and transition destination case statuses corresponding to operation type codes are linked and stored, and the control unit is characterized by having a case status transition destination determination unit that determines the transition destination status of the case by referring to the transition destination control master based on the case, status, and operation type code selected on the case search screen.
[0009] In addition, the loan management device of the present invention is characterized in that the control unit includes a project data creation unit that creates the project data and an approval history creation unit that creates the approval history data, and the project data creation unit updates the project status of the project data to the project transition destination status determined by the project status transition destination determination unit, and the approval history creation unit adds the project transition destination status determined by the project status transition destination determination unit to the status history.
[0010] In addition, in the loan management device of the present invention, the case status transition destination control master stores a previous case status reference flag, and the case status transition destination determination unit obtains the previous case status from the approval history data and determines the case transition destination status by referring to the transition destination control master based on the case, status, operation type code and previous case status selected on the case search screen.
[0011] In addition, the loan management method of the present invention is a loan management method executed by a loan management device equipped with a control unit, wherein the loan management device has access to case data including case number and case status, approval history data including case status history, a case status master linking case status names with case status codes, and a case status transition destination control master linking and storing case statuses corresponding to operation type codes, and includes a case status transition destination determination step executed by the control unit, which determines the case's transition destination status by referring to the transition destination control master based on the case, status, and operation type code selected on the case search screen.
[0012] In addition, the loan management program of the present invention is a loan management program to be executed by a loan management device equipped with a control unit, wherein the loan management device is capable of accessing case data including case number and case status, approval history data including case status history, a case status master in which case status names and case status codes are linked, and a case status transition destination control master in which case statuses and transition destination case statuses corresponding to operation type codes are linked and stored, and is characterized in that it includes a case status transition destination determination step to be executed by the control unit, which determines the transition destination status of the case by referring to the transition destination control master based on the case, status, and operation type code selected on the case search screen. [Effects of the Invention]
[0013] According to the present invention, it is possible to automatically determine the transition destination of a case after an operation, thereby enabling the appropriate management of complex review work and reducing duplication of reviews. [Brief explanation of the drawings]
[0014] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a loan management apparatus according to the present embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the case status master. [Figure 3] FIG. 3 is a diagram illustrating an example of the case status transition destination control master. [Figure 4] FIG. 4 is a diagram showing the flow of transition of the case status. [Figure 5] FIG. 5 is a diagram illustrating an example of the case data and the approval history data. [Figure 6] FIG. 6 is a diagram showing an example of processing on the case search screen. [Figure 7] FIG. 7 is a diagram showing an example of processing on the case search screen. [Figure 8]FIG. 8 is a diagram showing an example of rewriting of the case data and approval history data after the transition destination status is determined on the case search screen. [Figure 9] FIG. 9 is a diagram illustrating an example of the case data and the approval history data. [Figure 10] FIG. 10 is a diagram showing an example of processing on the case search screen. [Figure 11] FIG. 11 is a diagram showing an example of processing on the case search screen. [Figure 12] FIG. 12 is a diagram illustrating an example of approval history data. [Figure 13] FIG. 13 is a diagram showing an example of rewriting of the case data and approval history data after the transition destination status is determined on the case search screen. [Figure 14] FIG. 14 is a flowchart showing the loan management method according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0015] Hereinafter, embodiments of a loan management device, a loan management method, and a loan management program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.
[0016] [1. Configuration] An example of the configuration of the loan management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the configuration of the loan management device 100 according to this embodiment.
[0017] The loan management device 100 is constructed based on a commercially available desktop personal computer. Note that the loan management device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may also be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.
[0018] The loan management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the loan management device 100 are connected to each other so as to be able to communicate with each other via any communication path.
[0019] The communication interface unit 104 communicatively connects the loan management apparatus 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the loan management apparatus 100 and the server apparatus 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the memory unit 106 may also be stored in the server apparatus 200, for example.
[0020] An input device 400 and an output device 500 are connected to the input / output interface unit 108. The output device 500 may be a monitor (including a home television), a speaker, or a printer. The input device 400 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. In the following, the output device 500 may be referred to as the monitor 500, and the input device 400 may be referred to as the keyboard 400 or the mouse 400.
[0021] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.
[0022] The storage unit 106 stores, for example, case data 106a, approval history data 106b, case status master 106c, case status transition destination control master 106d, and the like.
[0023] The project data 106a is data related to projects for which loan screening is being conducted. The project data 106a stores project information including the project number, project status related to the latest screening status of the project, etc., as shown in an example in FIG.
[0024] The approval history data 106b is history data on the approval status of loan screening. As shown in an example in Figure 5, the approval history data 106b stores information including customer information including the case number, SEQ numbers corresponding to operations, and case statuses for each operation.
[0025] The case status master 106c stores case status names and case status codes in the examination of cases, as shown in an example in FIG.
[0026] The case status transition destination control master 106d stores information that determines the transition destination of the case after an operation. As shown in an example in Fig. 3, the case status transition destination control master 106d stores the case status before the operation, i.e., before the transition, in association with the operation type code, the previous case status, and the transition destination case status.
[0027] The control unit 102 is a CPU or the like that comprehensively controls the loan management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.
[0028] The control unit 102 conceptually includes, in terms of functions, an item data creation unit 102a, an approval history data creation unit 102b, an item status transition destination determination unit 102c, and the like.
[0029] The case data creation unit 102a creates case data 106a including case information including a case number and a case status related to the latest review status of the case. The case data creation unit 102a also updates the case status of the case data 106a to a case transition destination status determined by the case status transition destination determination unit 102c, which will be described later.
[0030] The approval history data creation unit 102b creates approval history data 106b including customer information including the case number, SEQ numbers corresponding to operations, and case statuses for each operation. The approval history data creation unit 102b also adds the case transition destination status determined by the case status transition destination determination unit 102c to the status history.
[0031] The case status transition destination determination unit 102c determines the transition destination status of the case by referring to the transition destination control master 106d based on the case, the case status, and the operation type code. Also, the case status transition destination determination unit 102c determines the transition destination status of the case by referring to the transition destination control master 106d based on the case, the case status, the operation type, and the previous case status acquired from the approval history data 106b.
[0032] [2. Processing] 2 to 14, specific examples of processing executed by the loan management device 100 will be described. There are two types of loan screening: a simple preliminary screening and a detailed main screening, each of which has a case status. The following describes the transition of the preliminary screening case status as an example.
[0033] Figure 4 shows the flow of case status transitions. In the preliminary screening, the status first becomes (1-1. Pre-accepted), and once approval is confirmed in the operation, the status transitions to (2-1. Pre-accepted by headquarters). In the status (2-1. Pre-accepted by headquarters), there are three types of operations: return, withdrawal, and input of external communication results. In the case of return, the status transitions to (1-2. Pre-rejection (1)), in the case of withdrawal, the status transitions to (2-6. Pre-withdrawal), and in the case of input of external communication results, the status transitions to (2-2. Pre-screening in progress). Here, pre-rejection (1) is the state in which the loan application has been returned by the agent.
[0034] In the status (2-2. Under preliminary review), there are three types of operations: withdrawal, additional review, and application. In the case of withdrawal, the status will change to (2-6. Pre-withdrawal), in the case of additional review, the status will change to (2-3. Under preliminary additional review), and in the case of application, the status will change to (2-4. Awaiting preliminary approval).
[0035] In the status (2-4. Awaiting preliminary approval), there are four types of operations: withdrawal, return, and approval / disapproval. If withdrawn, the status will change to (2-6. Pre-withdrawal), if returned, the status will change to (2-5. Pre-rejection (2)), and if approved / disapproved, the status will change to (2-7. Pre-approval / disapproval). Here, Pre-rejection (2) is the state in which the review results have been returned by the review department staff.
[0036] In the status (2-7. Pre-approval / rejection), there are two types of operations: withdrawal and reply. In the case of withdrawal, the status will change to (2-6. Pre-withdrawal), and in the case of reply, the status will change to (2-8. Pre-reply given (approval / rejection)).
[0037] In the status (2-3. Under preliminary additional review), there are two types of operations: withdrawal and confirmation. If withdrawn, the status will change to (2-6. Pre-withdrawal), and if confirmed, the status will change to (2-4. Awaiting preliminary approval).
[0038] In the status of (2-5. Preliminary Return (2)), there are three types of operations: Withdrawal, Return, and Application. In the case of Withdrawal, the status will change to (2-6. Preliminary Withdrawal), in the case of Return, the status will change to (1-2. Preliminary Return (1)), and in the case of Application, the status will change to (2-4. Waiting for Preliminary Approval).
[0039] In the status (2-6. Pre-Withdrawal), there is only one type of operation, "Cancel Withdrawal", but the status destination is determined by the type of the previous case status. If the previous status was (2-1. Pre-Received by Headquarters), (2-2. Pre-Review in Progress), (2-3. Pre-Additional Review in Progress), (2-4. Awaiting Pre-Approval) or (2-5. Pre-Return (2)), the status will transition to (2-1. Pre-Received by Headquarters), and in the case of (2-7. Pre-Approval) and (2-8. Pre-Response (Approval)), the status will transition to (2-7. Pre-Approval).
[0040] Next, the processing when the case status transition destination determining unit 102c determines the case status transition destination without referring to the previous case status and when it determines the case status transition destination by referring to the previous case status will be described separately.
[0041] First, a case will be described in which the case status transition destination determination unit 102c determines the case status transition destination without referring to the previous case status. Figures 6 and 7 are diagrams showing an example of processing on the case search screen. An operator searches for each case and inputs an operation using the case search screens MA-1 to MA-4 shown in Figures 6 and 7.
[0042] The case search screen MA-1 displays the number of cases currently under review by case status, and by selecting and clicking the case status for the operation you want to perform, you will be taken to the case search screen MA-2. On the case search screen MA-1, "Awaiting pre-approval" is selected, and by clicking this, the case search screen MA-2 will display the case status, case number, customer information, etc. for all cases awaiting pre-approval.
[0043] When you select and click on the desired project on the Project Search screen MA-2, you will be taken to the Project Search screen MA-3. On the Project Search screen MA-3, you can enter the operation for the selected project. On the Project Search screen MA-3, the Approve command for the project operation is clicked.
[0044] When you select and click an operation on the case search screen MA-3, you will be taken to the case search screen MA-4. On the case search screen MA-4, the status (awaiting pre-approval) has been approved and transitioned to (pre-approval), so the number of pre-approved cases is displayed as 1.
[0045] The case status transition destination determination unit 102c acquires the latest case status of the case selected on the case search screens MA-1 and MA-2 from the case data 106a and the approval history data 106b (see FIG. 14, S1). FIG. 5 is a diagram showing an example of the case data 106a-1 and the approval history data 106b-1.
[0046] The case status transition destination determination unit 102c determines the transition destination status of the case by referring to the transition destination control master 106d based on the latest case status of the case and the operation type code entered on the case search screen MA-3 (see FIG. 14, S4).
[0047] In Fig. 5, the latest case status of case number 222-000002 is 106: Waiting for preliminary approval, and the operation type code is Approval. In the case status transition destination control master 106d shown as an example in Fig. 3, there are four columns with the transition source case status of 106: Waiting for preliminary approval. When the operation type code is Approval among these, the transition destination case status is 109: Pre-approval, and therefore the case status transition destination determination unit 102c determines the transition destination of case number 222-000002 to be 109: Pre-approval. Note that when the transition source case status is 106: Waiting for preliminary approval and the operation type code is 8: Approval, the previous case status is "0: FALSE" (see Fig. 14, S2: No), and therefore the case status transition destination determination unit 102c determines the transition destination based on the combination of the case status and the operation type code without referencing the previous case status.
[0048] After determining the destination case status, the case data creation unit 102a updates the case status of the case data 106a-1 to the destination case status determined by the case status transition destination determination unit 102c (see FIG. 14, S5), and the approval history creation unit 102c adds the destination case status determined by the case status transition destination determination unit 103c to the approval history data 106b-1 (see FIG. 14, S6). FIG. 8 is a diagram showing an example of the updated case data 106a-2 and approval history data 106b-2. In the updated case data 106a-2, the case status has been updated from "106: Awaiting Preliminary Review" to "109: Preliminary Approval," and in the approval history data 106b-2, a column for the case status "109: Preliminary Approval" has been added as SEQ4.
[0049] The loan management device 100 according to this embodiment can automatically determine the transition destination of a project based on a combination of the project status and the operation type code. This also makes it possible to adapt the system without modifying the program even when the business flow changes due to the merger or closure of branches or departments. Furthermore, because the transition destination can be determined simply by setting the master data, rapid operation can be achieved.
[0050] Next, a case will be described in which the case status transition destination determination unit 102c determines the case status transition destination by referring to the previous case status. Figures 10 and 11 are diagrams showing an example of processing on the case search screen. The operator searches for each case and inputs operations using the case search screens MB-1 to MB-4 shown in Figures 10 and 11.
[0051] The case search screen MA-1 displays the number of cases currently under review by case status, and by selecting and clicking the case status for the operation you want to perform, you will be taken to the case search screen MB-2. On the case search screen MB-1, "Pre-withdraw" is selected, and by clicking this, the case search screen MB-2 will display the case status, case number, customer information, etc. for all pre-withdrawn cases.
[0052] When you select and click on the target project on the Project Search Screen MB-2, you will be taken to the Project Search Screen MB-3. On the Project Search Screen MB-3, you enter the operation for the selected project. On the Project Search Screen MB-3, the command to cancel withdrawal for the project operation has been clicked.
[0053] When you select and click an operation on the matter search screen MB-3, you will be taken to the matter search screen MB-4. On the matter search screen MB-4, the (pre-withdrawn) status has been released and transitioned to the (pre-received by headquarters) status, so the number of pre-received by headquarters is displayed as 1 and the number of pre-withdrawn is displayed as 1.
[0054] The case status transition destination determination unit 102c acquires the latest case status of the case selected on the case search screens MA-1 and MA-2 from the case data 106a and the approval history data 106b (see FIG. 14, S1). FIG. 9 is a diagram showing an example of the case data 106a'-1 and the approval history data 106b'-1.
[0055] The case status transition destination determination unit 102c determines the transition destination status of the case by referring to the transition destination control master 106d based on the latest case status of the case, the operation type code entered on the case search screen MA-3, and the previous case status obtained from the approval history data 106b'-1 (see Figure 14, S4). Figure 12 is an example of the approval history data 106b'-1, which consists of four SEQs, with SEQ4 being the latest status and SEQ3 being the previous status. The case status transition destination determination unit 102c obtains 106: Waiting for preliminary approval as the previous status.
[0056] In Figure 9, the latest case status of case number 222-000003 is 108: Withdrawn in advance, the previous case status is 106: Awaiting preliminary approval, and the operation type code is Withdrawal Cancelled. In the case status transition destination control master 106d shown as an example in Figure 3, there are seven columns for the transition source case status 108: Withdrawn in advance, and all of the operation type codes are Withdrawal Cancelled. Because the previous case status is TRUE (see Figure 14, S-2: Yes), the previous case status is acquired (see Figure 14, S3). Since the transition source case status is 108: Withdrawn in advance, the operation type code is Withdrawal Cancelled, and the previous case status is 106: Awaiting preliminary approval, and the transition destination case status is 103: Headquarters Pre-Received, the case status transition destination determination unit 102c determines the transition destination of case number 222-000003 to be 103: Headquarters Pre-Received.
[0057] After determining the destination case status, the case data creation unit 102a updates the case status of the case data 106a'-1 to the case destination status determined by the case status transition destination determination unit 102c (see FIG. 14, S5), and the approval history creation unit 102c adds the case destination status determined by the case status transition destination determination unit 103c to the approval history data 106b'-1 (see FIG. 14, S6). FIG. 12 is a diagram showing an example of the updated case data 106a'-2 and approval history data 106b'-2. In the updated case data 106a'-2, the case status has been updated from "108: Withdrawn in advance" to "103: Received in advance by headquarters," and a column for the case status "103: Received in advance by headquarters" has been added as SEQ5 in the approval history data 106b'-2.
[0058] The loan management device 100 according to this embodiment can automatically determine the transition destination of a case based on a combination of the case status, operation type code, and previous case status. This also allows the system to respond without program modification even when the business flow changes due to the merger or closure of branches or departments. Furthermore, because the transition destination can be determined simply by setting the master data, rapid operation can be achieved. Furthermore, because the transition destination is determined based on the previous case status, unnecessary re-examinations can be reduced, improving business efficiency.
[0059] [3. 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, thereby contributing to the achievement of SDGs Goals 8 and 9.
[0060] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.
[0061] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.
[0062] 4. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.
[0063] 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.
[0064] Furthermore, 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 can be changed as desired unless otherwise specified.
[0065] Furthermore, with regard to the loan management device 100, the components shown in the drawings are functional concepts, and do not necessarily have to be physically configured as shown in the drawings.
[0066] For example, all or any part of the processing functions of the loan management device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, 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 loan management device 100 as needed. That is, a computer program for providing 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 (Hard Disk Drive). The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.
[0067] This computer program may be stored in an application program server connected to the loan management apparatus 100 via any network, and may be downloaded in whole or in part as needed.
[0068] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or 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.
[0069] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.
[0070] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.
[0071] The loan management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device connected to any peripheral device. The loan management device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.
[0072] 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 configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]
[0073] The present invention can be used in the financial industry, such as non-banks, online banks, and banks. [Explanation of symbols]
[0074] 100 Loan management device 102 Control section 102a Project Data Creation Department 102b Overapproval History Data Creation Department 102c Matter status transition destination determination unit 104 Communication interface unit 106 Storage section 106a Project Data 106b Approval history data 106c Case Status Master 106d Matter status transition destination control master 108 Input / Output Interface Section 200 servers 300 Network 400 Input Device 500 output devices
Claims
1. A loan management device including a control unit, Case data, including case number and case status; Approval history data including a status history indicating the approval status of the loan review for the project; A matter status master in which matter status names and matter status codes are linked, A matter status transition destination control master in which a matter status and a transition destination matter status corresponding to an operation type code are linked and stored; is accessible to The control unit an item status transition destination determination unit that determines the transition destination status of the item by referring to the item status transition destination control master based on the item, status, and operation type code selected on the item search screen; A loan management device comprising:
2. The control unit a case data creation unit that creates the case data; an approval history creating unit that creates the approval history data; Equipped with the case data creation unit updates the case status of the case data to the case transition destination status determined by the case status transition destination determination unit; the approval history creation unit adds the case transition destination status determined by the case status transition destination determination unit to a status history. The loan management device according to claim 1 .
3. The case status transition destination control master stores a previous case status reference flag, the matter status transition destination determination unit acquires the previous matter status from the approval history data, and determines the transition destination status of the matter by referring to the matter status transition destination control master based on the matter, status, operation type code, and previous matter status selected on the matter search screen; The loan management device according to claim 1 .
4. A loan management method executed by a loan management device including a control unit, The loan management device Case data, including case number and case status; Approval history data including a status history indicating the approval status of the loan review for the project; A matter status master in which matter status names and matter status codes are linked, A matter status transition destination control master in which a matter status and a transition destination matter status corresponding to an operation type code are linked and stored; is accessible to Executed by the control unit, an issue status transition destination determination step for determining the transition destination status of the issue by referring to the issue status transition destination control master based on the issue, status, and operation type code selected on the issue search screen; A loan management method comprising:
5. A loan management program to be executed by a loan management device having a control unit, The loan management device Case data, including case number and case status; Approval history data including a status history indicating the approval status of the loan review for the project; A matter status master in which matter status names and matter status codes are linked, A matter status transition destination control master in which a matter status and a transition destination matter status corresponding to an operation type code are linked and stored; is accessible to To cause the control unit to execute an issue status transition destination determination step for determining the transition destination status of the issue by referring to the issue status transition destination control master based on the issue, status, and operation type code selected on the issue search screen; A loan management program comprising:
Citation Information
Patent Citations
Loan business support system and method of doing loan business
JP2002279180A
Enterprise credit rating system and enterprise credit rating program
JP2005134938A
Financing examination support system and its method
JP2009134375A
Workflow improvement system, workflow improvement method, and workflow improvement program
JP2010146091A
Work flow system, work flow system management method, and work flow system management program
JP2010231625A