History data management device, history data management method, and history data management program

Abstract

To provide a history data management device excellent in flexibility and versatility by allowing a user to arbitrarily set timing for acquiring history data in a master in loan examination work.SOLUTION: The history data management apparatus includes: a master in which a case status of a creation timing of history data is registered; an application acquisition unit that acquires the latest application data and stores the application data in the storage unit when a loan examination application is made; a history registration unit that determines whether or not the case status of a transition source is registered in the master when the case status of the application data transitions, and if the case status of the transition source is registered, stores the application data as history data in the storage unit; and a difference check unit that refers to the history data and the application data stored in the storage unit, and displays and outputs a difference item with respect to a comparison source case status and a comparison destination case status specified for a target case according to an operation of an operator on a confirmation screen.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a history data management device, a history data management method, and a history data management program. [Background technology]

[0002] For example, in loan screening, paperless and electronic systems are becoming more common, and rapid screening is required, so historical data of application data is managed and discrepancies in the application data are checked. Conventional systems related to loan screening include, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7227722 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above Patent Document 1, historical data is created only once for each of the loan screening processes, namely, "preliminary screening," "main screening," and "contract," and the timing for creating historical data is fixed, resulting in a lack of flexibility and versatility.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a history data management device, a history data management method, and a history data management program that are highly flexible and versatile by allowing users to arbitrarily set the timing for acquiring history data in the master in loan screening operations. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a history data management device having a memory unit and a control unit, wherein the memory unit stores a master in which the case status at the time of creation of the history data is registered, and the control unit is characterized by comprising: an application acquisition means for acquiring the latest application data when an application for loan screening is made and storing it in the memory unit; a history registration means for determining whether the case status from which the transition occurs is registered in the master when the case status of the application data changes, and if so, storing the application data in the memory unit as history data; and a difference confirmation means for displaying and outputting the difference items by referring to the history data stored in the memory unit and the application data for the case status of the comparison source and the case status of the comparison target specified for the target case in accordance with the operator's operation on a confirmation screen.

[0007] According to another aspect of the present invention, the difference confirmation means may display a selection screen on the confirmation screen for selecting the case status of the comparison source and the case status of the comparison target in response to a predetermined operation by the operator.

[0008] According to another aspect of the present invention, the control unit may include a master maintenance unit that sets data of the master in response to an operation by an operator on a master maintenance screen.

[0009] According to another aspect of the present invention, the application data may include at least a case number, a history sequence number, a case status, an updater, and an update date.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a historical data management method executed by a historical data management device having a memory unit and a control unit, wherein the memory unit stores a master in which the case status at the time the historical data is created is registered, and the method includes an application acquisition process executed by the control unit to acquire the latest application data and store it in the memory unit when an application for loan screening is made, a history registration process to determine whether the case status from which the transition occurs is registered in the master when the case status of the application data changes, and if so, to store the application data as historical data in the memory unit, and a difference confirmation process to display and output the difference items for the case status of the comparison source and the case status of the comparison target specified for the target case in accordance with the operator's operation on a confirmation screen, by referring to the historical data stored in the memory unit and the application data.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a history data management program to be executed by a history data management device having a memory unit and a control unit, wherein the memory unit stores a master in which the case status at the time of creating the history data is registered, and the control unit has the following features: an application acquisition process in which, when an application for loan screening is received, the latest application data is acquired and stored in the memory unit; a history registration process in which, when the case status of the application data changes, it is determined whether the case status from which the transition occurred is registered in the master, and if so, the application data is stored in the memory unit as history data; and a difference confirmation process in which, on a confirmation screen, in response to operator operation, for the case status of the target case, the history data stored in the memory unit and the application data are specified for the case status of the comparison source and the case status of the comparison target, and the difference items are displayed and output by referring to the history data and the application data. [Effects of the Invention]

[0012] According to the present invention, by allowing the user to arbitrarily set the timing for acquiring historical data in the master in loan screening operations, it is possible to provide a historical data management device, a historical data management method, and a historical data management program that are highly flexible and versatile. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an example of a basic scheme for loan screening operations. [Figure 2] FIG. 2 is a diagram for explaining the "case status." [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of the history data management device according to this embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of the case status master. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of the history data creation item status master. [Figure 6A] FIG. 6A is a diagram showing an example of the history registration process in this embodiment. [Figure 6B] FIG. 6B is a diagram showing an example of the history registration process in this embodiment. [Figure 7A] FIG. 7A is a diagram showing an example of the history registration process in this embodiment. [Figure 7B] FIG. 7B is a diagram showing an example of the history registration process in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the difference confirmation process in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the difference confirmation process in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the difference confirmation process in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0015] [1. Overview] First, an overview of the present invention will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a basic scheme for a loan screening process. As shown in Fig. 1, in a loan screening process, (1) when a customer applies for a loan, (2) a preliminary screening is conducted, and if there are any deficiencies in the application, the application is rejected, but if there are no deficiencies in the application, the preliminary screening is deemed to be successful, (3) a main screening is conducted, and if there are any deficiencies in the application, the application is rejected, but if there are no deficiencies in the application, the main screening is deemed to be successful, (4) a loan contract is concluded, and (5) the loan is executed.

[0016] In Patent Document 1, historical data was created only once for each of the review processes, namely, "preliminary review," "main review," and "contract." This meant that the timing for creating historical data was fixed, resulting in a lack of flexibility and versatility.

[0017] This invention focuses on the item "case status" which manages the progress of the review, and allows users to arbitrarily set the timing of acquiring historical data in the master on a case status basis. This allows the timing of acquiring historical data to be further subdivided, enabling historical data to be used more efficiently in business, and making it possible to provide a system with excellent flexibility and versatility.

[0018] Figure 2 is a diagram for explaining the "case status." The "case status" will be explained with reference to Figure 2. The history data management device uses the "case status" to manage the progress of the review. The case status is linked to the review process and progresses in accordance with the progress of the data.

[0019] Project status master (project status code, project status name) as shown in Figure 2 By setting this, users can determine the case status according to their work. Figure 2 (A) shows an example of pattern (1) where there is one approver at each step. Figure 2 (B) shows an example of pattern (2) where there are two approvers at each step.

[0020] The above case (1) can be handled with the function of Patent Document 1. However, in the above case (2), if the data at the time of approval is managed as historical data and it is desired to use it for comparison work in a later process, the function of Patent Document 1 would incur development costs to acquire the historical data.

[0021] The history data management device of the present invention can be widely applied to all financial institutions that perform loan screening operations.

[0022] [2. Configuration] An example of the configuration of the history data management device 100 according to this embodiment will be described with reference to Fig. 3 etc. Fig. 3 is a block diagram showing an example of the configuration of the history data management device 100 according to this embodiment.

[0023] The history data management device 100 is a commercially available desktop personal computer. Note that the history data management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0024] The history data management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in the history data management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0025] The communication interface unit 104 communicatively connects the history data management device 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 a communication line. Here, the network 300 has a function of connecting the history data management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0026] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0027] The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 stores computer programs that cooperate with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 may 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, or an optical disk. The memory unit 106 includes a case status master 106a, a history data creation case status master (master) 106b, an application file 106c, and a history file 106d. FIG. 4 shows an example of the configuration of the case status master 106a. FIG. 5 shows an example of the configuration of the history data creation case status master 106b.

[0028] The case status master 106a can be configured as a table in which case status codes and case status names are registered in association with each other, as shown in Fig. 4. The case status master 106a is referenced when converting case status codes and case status names. In the example shown in the figure, the first line shows the case status code "101" and the case status name "pre-reception."

[0029] The historical data creation case status master 106b is a master for setting the timing of creating historical data, and as shown in Fig. 5, case status codes for the timing of creating historical data are registered. In the example shown in Fig. 5, the case status codes "104: Pre-approval (1)", "106: Pre-approval (2)", "204: Final approval (1)", and "206: Final approval (2)" are set. Conventionally, when an case status transition occurs, it is determined whether the transition source case status is "pre-approval" or "final approval", and if so, historical data is created. However, in this embodiment, when an case status transition occurs, the historical data creation case status master 106b is referenced to determine whether the transition source case status exists in the historical data creation case status master 106b, and if so, historical data is created.

[0030] The application file 106c stores the latest application data submitted in the loan screening. Here, the application data may include the latest project information data, the latest applicant information data, the latest property information data, the latest funding information data, etc.

[0031] The latest case information data is basic data on the application contents, and may include items such as case number, history sequence, reception store, case status, updater, and update date.

[0032] The latest applicant information data is data relating to the applicant, and may include items such as case number, history sequence, related party classification, nationality, and previous year's annual income.

[0033] The latest property information data is data relating to the property, and may include items such as the case number, history sequence, property sequence, and address.

[0034] The latest fund information data is data related to funds, and may include items such as case number, history SEQ, product SEQ, and remittance account.

[0035] The history file 106d stores application data submitted during loan screening as history data. The history data may include case information history data, applicant information history data, property information history data, and funding information history data. The history data has the same items as the application data.

[0036] The control unit 102 is a CPU or the like that performs overall control of the history data 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 operations based on these stored programs.

[0037] The control unit 102 is configured to be able to access the case status master 106a, the history data creation case status master 106b, the application file 106c, the history file 106d, etc. stored in the memory unit 106. Note that the case status master 106a, the history data creation case status master 106b, the application file 106c, the history file 106d, etc. may be provided in other locations (for example, the server 200) as long as they are accessible by the control unit 102.

[0038] The control unit 102 conceptually includes a request acquisition unit 102a, a history registration unit 102b, a difference confirmation unit 102c, and a master maintenance unit 102d.

[0039] The application acquisition unit 102a executes an application registration process and acquires application data when an application for loan screening is received. Here, the application acquisition unit 102a may register (store) the acquired application data in the application file 106c. Here, the application acquisition unit 102a may overwrite and save the acquired application data on the (existing) application data stored in the application file 106c. Furthermore, when a process that triggers an advance in the case status (e.g., pressing a button) is performed, the application acquisition unit 102a updates the case status of the application data in response to the operation of the updater.

[0040] The history registration unit 102b executes the history registration process, and when the case status of the application data changes, it refers to the history data creation case status master 106b to determine whether the case status from which the transition occurs is registered, and if it is registered, it registers the application data as history data in the history file 106d.

[0041] The difference confirmation unit 102c, for example, in response to the operation of an operator on the data difference confirmation screen (see Figure 8) displayed on the monitor 114, references the application data in the application file 106c and the application data in the history file 106d for the specified comparison source case status and comparison target case status for the target case, and displays and outputs the difference items.

[0042] The difference confirmation unit 102c may display a comparison source / destination case selection screen (see Figure 10) for selecting the comparison source case status and the comparison destination case status in response to a predetermined operation by the operator on the data difference confirmation screen (for example, pressing the search button).

[0043] The master maintenance unit 102d performs editing such as inputting, adding, and changing data in the case status master 106a and the history data creation case status master 106b in response to, for example, an operator (user) operation on a master maintenance screen (not shown) displayed on the monitor 114. In this way, the operator can arbitrarily set the data in the case status master 106a and the history data creation case status master 106b.

[0044] The screen display control unit 102e controls the display of various screens (for example, a master maintenance screen, a data discrepancy confirmation screen, a comparison source / destination case selection screen, etc.) displayed on the monitor 114 and the inputs thereto.

[0045] [3. Specific Examples] A specific example of the processing by control unit 102 of history data management device 100 according to this embodiment will be described with reference to Fig. 3 to Fig. 10. Fig. 6A to Fig. 10 are diagrams for explaining a specific example of the processing by control unit 102 of history data management device 100 according to this embodiment.

[0046] (History registration process) A specific example of the history registration process will be described with reference to Figures 6A to 7B. The history registration unit 102b executes the history registration process, and when the case status of the application data changes, it refers to the history data creation case status master 106b to determine whether the case status of the transition source is registered, and if it is registered, it registers the application data as history data in the history file 106d.

[0047] Figures 6A and 6B show patterns in which historical data is not created. In Figures 6A and 6B, the left side shows application data and the right side shows historical data. Figure 6A shows the case before the case status progresses, and Figure 6B shows the case after the case status progresses.

[0048] In Figure 6A, the case status of the application data is "Waiting for final settlement." When the process to advance the case status is performed, the case status of the application data transitions to "Final Approval (1)," as shown in Figure 6B. Referring to the history data creation case status master 106b in Figure 5, the case status from which the transition occurred, "203: Waiting for final settlement," is not registered, so the history data is not updated, as shown in Figure 6B.

[0049] 7A and 7B show patterns for creating history data. In Fig. 7A and Fig. 7B, the left side shows application data and the right side shows history data. Fig. 7A shows the case before the case status progresses, and Fig. 7B shows the case after the case status progresses.

[0050] In Figure 7A, the case status of the application data is "Final Approval (1)." When a process to advance the case status is performed, the case status of the application data transitions to "Final Approval (2)," as shown in Figure 7B. Referring to the history data creation case status master 106b in Figure 5, the case status "204: Final Approval (1)" from which the transition occurs is not registered, so history data is created (updated) as shown in Figure 7B.

[0051] (Difference confirmation process) A specific example of the difference confirmation process will be described with reference to Figures 8 to 10. For example, in response to an operator's operation on a data difference confirmation screen (see Figure 8) displayed on the monitor 114, the difference confirmation unit 102c references the application data in the application file 106c and the application data in the history file 106d for the specified comparison source case status and comparison target case status for the target case, and displays and outputs the difference items.

[0052] 8 is a diagram showing an example of the display of the data discrepancy confirmation screen 400. The data discrepancy confirmation screen 400 includes fields for specifying the case number, the comparison source case status, and the comparison target case status, a search button "···", a difference display button, and a difference item display area (No., name of the differing item, item content (comparison source case status), item content (comparison target case status)).

[0053] When you specify the case number, source case status, and target case status and press the Display Differences button, the historical data or application data for the specified source case status and target case status for the specified case number will be referenced, and the difference items will be displayed in the difference item display area.

[0054] In the case of historical data, data is retrieved from the history file 106d that holds each historical data based on the case number and history sequence held in the historical data of the selected case status. In the case of historical data, this means that when selecting a case status other than "Latest Status" is selected above.

[0055] In the case of the latest data, the data is acquired from the application file 106c that holds the latest data. In the case of the latest data, this means that "latest status" is selected in the above case status selection.

[0056] In the example shown in Figure 8, when the case number "224000001", the source case status "Latest Status", and the target case status "Pre-approval (2)" are specified and the display differences button is pressed, in the case of Figure 7B above, the "Latest Status" is "Formal Approval (2)" of the billing data (SEQ4), and "Pre-approval (2)" is SEQ2 of the historical data, SEQ4 of the billing data and SEQ2 of the historical data are compared, and the difference item display area of ​​Figure 8 displays No. "1", the differing item name "Annual Income", item content (source case status) "6000000", item content (target case status) "4000000", No. "2", the differing item name "Address", item content (source case status) "Tokyo...", and item content (target case status) "Osaka...".

[0057] When the search button "···" in Figure 8 is pressed, a previous case status selection screen 500 for selecting the case status, as shown in Figure 10, is displayed, and the comparison source case status and the comparison target case status in Figure 8 can be selected.

[0058] The data source for the next case status selection screen 500 is the case information history data of the history data, and in the example of FIG. 7B, it is acquired from the case information history data shown in FIG.

[0059] The previous case status selection screen 500 shown in Figure 10 displays No., case status, updater, and update date. By obtaining case information history data and displaying the "case status," "updator," and "update date" on the screen, it is possible to see when, who updated, and from what status. In addition to the case information history data, the latest status of the billing data can also be selected as a fixed value so that not only historical data but also the latest data can be used for comparison (row No. 4 in the example shown in Figure 10). The example in Figure 8 shows that "No. 4 (latest status)" is selected as the "comparison source case status" and "No. 2 (pre-approval (2))" is selected as the "comparison target case status" on the previous case status selection screen 500 shown in Figure 10.

[0060] As described above, according to this embodiment, there are provided a master in which the case status at the time of creating the historical data is registered, an application acquisition unit 102a which, when an application for loan screening is made, acquires the latest application data and stores it in the memory unit, a history registration unit 102b which, when the case status of the application data changes, determines whether the case status from which the transition occurs is registered in the master, and if so, stores the application data in the memory unit as historical data, and a difference confirmation unit 102c which, on the confirmation screen, in response to the operator's operation, refers to the historical data and the application data stored in the memory unit for the case status of the comparison source and the case status of the comparison target specified for the target case, and displays and outputs the differences.Therefore, by allowing the user to arbitrarily set the timing of acquiring historical data in the master in the loan screening process, it is possible to provide a system which is highly flexible and versatile.

[0061] [4. 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.

[0062] 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.

[0063] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0064] 5. 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.

[0065] 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.

[0066] 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.

[0067] Furthermore, with regard to the history data management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0068] For example, all or any part of the processing functions of the history data management device 100, particularly the processing functions performed by the control unit 102, 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 history data management device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

[0069] This computer program may also be stored in an application program server connected to the history data management device 100 via any network, and all or part of it may be downloaded as needed.

[0070] 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.

[0071] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of 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 this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0072] The various databases stored in the memory unit 106 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.

[0073] The history data management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The history data management device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0074] 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]

[0075] The present invention is useful in the financial industry, which performs loan screening operations. [Explanation of symbols]

[0076] 100 History data management device 102 Control section 102a Application Acquisition Department 102b History registration section 102c Difference Checking Section 102d Master Maintenance Department 102e Screen display control unit 104 Communication interface unit 106 Storage section 106a Case Status Master 106b History data creation matter status master 106c Application File 106d History File 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A history data management device including a storage unit and a control unit, The storage unit includes: The master data that contains the project status at the time of creating the historical data is stored. The control unit application acquisition means for acquiring the latest application data when an application for loan examination is made and storing the data in the storage unit; a history registration means for determining whether or not a transition source case status is registered in the master when the case status of the application data changes, and if so, storing the application data as history data in the storage unit; a difference confirmation means for displaying and outputting, on a confirmation screen, difference items for a specified case status of a comparison source and a specified case status of a comparison target in response to an operation by an operator, by referring to the history data stored in the storage unit and the application data; A history data management device comprising:

2. The historical data management device according to claim 1, characterized in that the difference confirmation means displays a selection screen on the confirmation screen for selecting the case status of the comparison source and the case status of the comparison target in response to a predetermined operation by an operator.

3. The control unit 3. The historical data management device according to claim 1, further comprising a master maintenance means for setting the master data in response to an operation by an operator on a master maintenance screen.

4. 3. The history data management device according to claim 1, wherein the application data includes at least a case number, a history sequence number, a case status, an updater, and an update date.

5. A history data management method executed by a history data management device having a storage unit and a control unit, The storage unit includes: The master data that contains the project status at the time of creating the historical data is stored. Executed in the control unit: an application acquisition step of acquiring the latest application data and storing it in the storage unit when an application for loan examination is received; a history registration step of determining whether or not the case status of the transition source is registered in the master when the case status of the application data transitions, and if so, storing the application data as history data in the storage unit; a difference confirmation step of displaying and outputting, on a confirmation screen, difference items between a comparison source case status and a comparison target case status specified for the target case in response to an operator's operation, by referring to the history data stored in the storage unit and the application data; A history data management method comprising:

6. A history data management program to be executed by a history data management device having a storage unit and a control unit, The storage unit includes: The master data that contains the project status at the time of creating the historical data is stored. The control unit an application acquisition step of acquiring the latest application data and storing it in the storage unit when an application for loan examination is received; a history registration step of determining whether or not the case status of the transition source is registered in the master when the case status of the application data transitions, and if so, storing the application data as history data in the storage unit; a difference confirmation step of displaying and outputting, on a confirmation screen, difference items between a comparison source case status and a comparison target case status specified for the target case in response to an operator's operation, by referring to the history data stored in the storage unit and the application data; A historical data management program for running the program.

Images