Contract management device, contract management method and contract management program

Abstract

To provide a contract management device, a contract management method and a contract management program which can reduce system development costs, while improving work accuracy and reducing work time.SOLUTION: A contract management device is configured to: on the basis of customer information data, contract information data and a code master, retrieve contract information data corresponding to a customer number inputted into a retrieval condition input field when the customer number is inputted into the retrieval condition input field in the case that a change object item to be inputted is a code; and acquire account transfer basic data before change associated with a pertinent contract ID from the account transfer basic data and cause a monitor to display the data; and update a content of a predetermined item in the account transfer basic data before change associated with the pertinent contract ID, to an input content to be inputted to a change input field.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a technology that allows a mediator system to provide a bulk processing service for multiple trading partner systems without having to register all of the information in the user system in the mediator system. This technology allows for bulk inquiries about contract information and the like distributed across multiple trading partners, and bulk updates of change information such as addresses. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-186978 Summary of the Invention [Problem to be solved by the invention]

[0004] In the financial industry, a large amount of information related to contracts is managed in the course of credit management. This information exists in data tables categorized by attributes. For this reason, in the financial industry, input screens for entering information about contracts are prepared for each category, and input is often performed on a contract-by-contract basis.

[0005] However, in the conventional financial industry systems described above, input screens are prepared for each category and input is done on a contract-by-contract basis, which can lead to users making input errors and unintentionally changing items other than those that are being changed, or the operation can become complicated when there are many contracts to be changed, and input screens needing to be developed each time the number of items to be managed increases.

[0006] The present invention has been made in consideration of the above, and aims to provide a contract management device, a contract management method, and a contract management program that can improve work accuracy and shorten work time while reducing system development costs. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, a contract management device according to the present invention is a contract management device having a control unit, and is capable of accessing a change object management master in which at least an item name, a table name, a column name, an item type, a data length, and a code type are associated with an item number, a code master in which a code value and a code name are associated with a code type, contract information data in which a contract ID is associated with a contract number, a customer number, a contract date, a contract classification code, and a lump-sum payment exclusion flag, basic account transfer data in which a billing suspension flag and a billing suspension reason code are associated with a contract ID, and customer information data in which a customer number is associated with a customer name, and the control unit references the change object management master and, in response to the input change object items, a display control unit that displays on the monitor a search condition input unit in which search conditions can be input and a change input unit in which change instructions can be input; a search unit that, when the input item to be changed is a code and a customer number is input into the search condition input unit, searches the account transfer basic data for the contract information data corresponding to the customer number input into the search condition input unit based on the customer information data, the contract information data and the code master, obtains the account transfer basic data before the change linked to the corresponding contract ID and displays it on the monitor; and an update unit that updates the content of a specified item in the account transfer basic data before the change linked to the corresponding contract ID to the input content input into the change input unit.

[0008] Furthermore, a contract management method according to the present invention is a contract management method executed by a contract management device having a control unit, wherein the contract management device has access to a change object management master in which at least an item name, a table name, a column name, an item type, a data length, and a code type are associated with an item number, a code master in which a code value and a code name are associated with a code type, contract information data in which a contract ID is associated with a contract number, a customer number, a contract date, a contract classification code, and a lump-sum payment exclusion flag, basic account transfer data in which a billing suspension flag and a billing suspension reason code are associated with a contract ID, and customer information data in which a customer number is associated with a customer name, and the contract management device executes the control unit to refer to the change object management master and execute the control unit to ... and a display control step of displaying on the monitor a search condition input section in which search conditions can be input and a change input section in which change instructions can be input; a search step of, when the input item to be changed is a code and a customer number is input into the search condition input section, searching the account transfer basic data for the contract information data corresponding to the customer number input into the search condition input section based on the customer information data, the contract information data and the code master, obtaining the account transfer basic data before the change linked to the corresponding contract ID and displaying it on the monitor; and an update step of updating the contents of specified items in the account transfer basic data before the change linked to the corresponding contract ID to the input contents input into the change input section.

[0009] Furthermore, a contract management program according to the present invention is a contract management program to be executed by a contract management device having a control unit, the contract management device being able to access a change object management master in which at least an item name, a table name, a column name, an item type, a data length, and a code type are associated with an item number, a code master in which a code value and a code name are associated with a code type, contract information data in which a contract ID is associated with a contract number, a customer number, a contract date, a contract classification code, and a lump-sum payment exclusion flag, basic account transfer data in which a billing suspension flag and a billing suspension reason code are associated with a contract ID, and customer information data in which a customer number is associated with a customer name, and the contract management program to be executed by the control unit refers to the change object management master and executes a change control program in accordance with the inputted change object items. and a display control step of displaying on the monitor a search condition input section in which search conditions can be input and a change input section in which change instructions can be input; a search step of, when the input item to be changed is a code and a customer number is input into the search condition input section, searching the account transfer basic data for the contract information data corresponding to the customer number input into the search condition input section based on the customer information data, the contract information data and the code master, obtaining the account transfer basic data before the change linked to the corresponding contract ID from the account transfer basic data and displaying it on the monitor; and an update step of updating the contents of specified items in the account transfer basic data before the change linked to the corresponding contract ID to the input contents input into the change input section. [Effects of the Invention]

[0010] According to the present invention, it is possible to improve the accuracy of work and shorten the work time, while reducing the system development costs. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a contract management device according to an embodiment. [Figure 2]FIG. 2 is a diagram showing an example of a change object management master table in the change object management master of the contract management apparatus according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a person in charge master table in the person in charge master of the contract management apparatus according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a code master table in the code master of the contract management apparatus according to the embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a contract information data table in the contract information data of the contract management apparatus according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a contract change schedule data table in the contract change schedule data of the contract management device according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of an account transfer basic data table in the account transfer basic data of the contract management apparatus according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a customer information data table in the customer information data of the contract management apparatus according to the embodiment. [Figure 9] FIG. 9 is a flowchart showing an outline of the processing executed by the contract management device according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a contract-related information batch update screen displayed on the monitor. [Figure 11] FIG. 11 is a diagram showing an example of the contract-related information batch update screen displayed on the monitor after input into the cells for items to be changed. [Figure 12] FIG. 12 is a diagram showing an example of a change target item table that can be used at authority level "5." [Figure 13] FIG. 13 is a diagram showing an example of a change target item table that can be used at authority level "3." [Figure 14] FIG. 14 is a diagram showing an example of a change target item table that can be used at authority level "2." [Figure 15] FIG. 15 is a diagram showing an example of a change target management master table to be referred to in the code update process. [Figure 16] FIG. 16 is a diagram showing an example of a code master table to be referred to in the code update process. [Figure 17] FIG. 17 is a diagram showing an example of a contract-related information batch update screen displayed by the monitor during the code update process. [Figure 18] FIG. 18 is a diagram illustrating an example of an operation permission / prohibition table for each person in charge. [Figure 19] FIG. 19 is a diagram showing an example of a contract-related information batch update screen displayed on the monitor when the batch set button is pressed. [Figure 20] FIG. 20 is a diagram showing an example of the account transfer basic data table before and after updating by the updating unit. [Figure 21] FIG. 21 is a diagram showing an example of a change target management master table to be referred to in the flag update process. [Figure 22] FIG. 22 is a diagram showing an example of a contract-related information batch update screen displayed by the monitor during the flag update process. [Figure 23] FIG. 23 is a diagram showing an example of an operation permission / prohibition table for each person in charge. [Figure 24] FIG. 24 is a diagram showing an example of a contract-related information batch update screen displayed by the monitor during the flag update process. [Figure 25] FIG. 25 is a diagram showing an example of the contract information data table before and after updating by the updating unit. [Figure 26] FIG. 26 is a diagram showing an example of a change target management master table to be referred to in the date update process. [Figure 27] FIG. 27 is a diagram showing an example of a contract-related information batch update screen displayed on the monitor during the date update process. [Figure 28] FIG. 28 is a diagram showing an example of an operation permission / prohibition table for each person in charge. [Figure 29] FIG. 29 is a diagram showing an example of a contract-related information batch update screen displayed by the monitor during the date update process. [Figure 30]FIG. 30 is a diagram showing an example of the contract change schedule data table before and after updating by the updating unit. [Figure 31] FIG. 31 is a diagram showing an example of a change target management master table referred to in the amount update process. [Figure 32] FIG. 32 is a diagram showing an example of the contract-related information batch update screen P1 displayed by the monitor during the amount update process. [Figure 33] FIG. 33 is a diagram showing an example of an operation permission / prohibition table for each person in charge. [Figure 34] FIG. 34 is a diagram showing an example of the contract-related information batch update screen P1 displayed on the monitor during the amount update process. [Figure 35] FIG. 35 is a diagram showing an example of the contract change schedule data table before and after updating by the updating unit. [Figure 36] FIG. 36 is a diagram showing an example of a change target management master table to be referred to in the full-width character update process. [Figure 37] FIG. 37 is a diagram showing an example of a contract-related information batch update screen P1 displayed on the monitor during the full-width character update process. [Figure 38] FIG. 38 is a diagram showing an example of an operation permission / prohibition table for each person in charge. [Figure 39] FIG. 39 is a diagram showing an example of a contract-related information batch update screen displayed on the monitor during the full-width character update process. [Figure 40] FIG. 40 is a diagram showing an example of the contract change schedule data table before and after updating by the updating unit. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of a contract management device, a contract management method, and a contract management program according to the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to these preferred embodiments.

[0013] [1. Configuration] An example of the configuration of a contract management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a contract management device.

[0014] 1 is a commercially available desktop personal computer. Note that the contract 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.

[0015] The contract 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 contract management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0016] The communication interface unit 104 communicatively connects the contract 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 the communication line. Here, the network 300 has a function of connecting the contract 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). Note that the data stored in the memory unit 106 may also be stored in the server 200, for example.

[0017] 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 home television), a speaker, or a printer. The input device 112 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 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0018] The storage unit 106 stores various databases, tables, files, and the like. The storage 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 storage 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 storage unit 106 stores a change target management master 106a, a staff member master 106b, a code master 106c, contract information data 106d, contract change schedule data 106e, account transfer basic data 106f, and customer information data 106g.

[0019] The change object management master 106a stores an item number in association with an item name, a table name, a column name, an item type, a data length, a code type, and an execution authority level of a person in charge.

[0020] 2 is a diagram showing an example of a change object management master table in the change object management master 106a. As shown in the first row of the change object management master table T1 shown in Fig. 2, the item number "1" is associated with the item name "contract category code", the table name "contract information data", the column name "contract category code", the item type "code", the data length "NULL", the code type "1005", and the executable authority level "2".

[0021] The person in charge master 106b stores the person in charge ID in association with the person in charge name and the authority level for each item.

[0022] 3 is a diagram showing an example of a person in charge master table in the person in charge master 106b. As shown in the first row of the person in charge master table T2 in Fig. 3, the person in charge ID "3000" is stored in association with the person in charge name "Taro Tanaka" and the authority level "5".

[0023] The code master 106c stores code types in association with code values ​​and code names.

[0024] 4 is a diagram showing an example of a code master table in the code master 106c. As shown in the first row of the code master table T3 shown in Fig. 4, the code type "1005" is stored in association with the code value "1" and the code name "Leaving work."

[0025] The contract information data 106d stores a contract ID in association with a contract number, a customer number, a contract date, a contract classification code, and a lump-sum payment exclusion flag.

[0026] 5 is a diagram showing an example of a contract information data table in the contract information data 106d. As shown in the first row of the contract information data table T4 shown in Fig. 5, the contract ID "10001" is stored in association with the contract number "00100-10001," the customer number "100," the contract date "2022 / 10 / 1," the contract classification code "1," and the lump-sum payment exclusion flag "TRUE."

[0027] The contract change schedule data 106e stores a contract ID in association with a scheduled date, a scheduled additional amount (amount of a predetermined item), and remarks.

[0028] Figure 6 is a diagram showing an example of a contract change schedule data table in the contract change schedule data 106e. As shown in the first row of the contract change schedule data table T5 shown in Figure 6, a scheduled date of "NULL" and a scheduled additional amount of "100000" are stored in association with the contract ID "10001." Similarly, as shown in the second row of the contract change schedule data table T5 shown in Figure 6, a scheduled date of "2023 / 3 / 10" and a remark "contract change scheduled due to XX" are stored in association with the contract ID "10002."

[0029] The basic account transfer data 106f stores a contract ID in association with a billing suspension flag and a billing suspension reason code.

[0030] Figure 7 is a diagram showing an example of an account transfer basic data table in the account transfer basic data 106f. As shown in the first row of the account transfer basic data table T6 shown in Figure 7, a billing stop flag of "FALSE" and a billing stop reason code of "NULL" are associated with the contract ID "10001." Similarly, as shown in the second row of the account transfer basic data table T6, a billing stop flag of "TRUE" and a billing stop reason code of "1" are associated with the contract ID "10002."

[0031] The customer information data 106g stores customer numbers that identify customers in association with customer names.

[0032] 8 is a diagram showing an example of a customer information data table in the customer information data 106g. As shown in the customer information data table T7 shown in Fig. 8, the customer number "100" is stored in association with the customer name "Suzuki Ichiro."

[0033] Returning to FIG. 1, the description of the configuration of the contract management device 100 will continue. The control unit 102 is a CPU or the like that performs overall control of the contract 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 processes based on these stored programs. The control unit 102 includes a display control unit 102a, a determination unit 102b, a search unit 102c, and an update unit 102d.

[0034] The display control unit 102a displays a contract-related information batch update screen on the monitor 114, where search conditions can be entered according to the items to be changed. The display control unit 102a refers to the change target management master 106a and the person in charge master 106b, and displays a search condition input section where search conditions can be entered, and a change input section where change instructions can be entered.

[0035] The determination unit 102b determines whether the item type associated with the item number input into the change target item cell K1 is code. The determination unit 102b also determines whether the user has finished the contract management operation via the input device 112. The determination unit 102b also determines whether the item type associated with the item number input into the change target item cell is date update. The determination unit 102b also determines whether the item type associated with the item number input into the change target item cell is amount update. The determination unit 102b also determines whether the item type associated with the item number input into the change target item cell is full-width character update.

[0036] When the item to be changed is a code and a customer number is entered in the search condition input section, the search unit 102c searches for contract information data 106d corresponding to the customer number entered in the search condition input section based on the customer information data 106g, contract information data 106d, and code master 106c, and obtains the pre-change account transfer basic data 106f linked to the corresponding contract ID from the account transfer basic data 106f and displays it on the monitor 114.

[0037] The update unit 102d updates the contents of the predetermined items in the pre-change basic account transfer data 106f linked to the relevant contract ID to the input contents input to the change input unit.

[0038] [2. Processing performed by the contract management device] Next, a description will be given of the processing executed by the contract management device 100. Fig. 9 is a flowchart showing an outline of the processing executed by the contract management device 100.

[0039] As shown in FIG. 9, first, the display control unit 102a causes the monitor 114 to display a contract-related information batch update screen on which search conditions can be input according to the items to be changed (step S1).

[0040] Fig. 10 is a diagram showing an example of a contract-related information bulk update screen displayed on the monitor 114. The contract-related information bulk update screen P1 shown in Fig. 10 includes a change target item cell K1 for inputting the items to be changed, a confirm button B1 for confirming the inputted change target items, a register button B2 for registering the update contents, and a cancel button B3 for canceling the update contents.

[0041] Returning to FIG. 9, the description of step S2 and subsequent steps will be continued. In step S2, the determination unit 102b determines whether the item type associated with the item No. input into the change target item cell K1 is a code.

[0042] FIG. 11 is a diagram showing an example of the contract-related information bulk update screen P1 displayed on the monitor 114 after input into the change target item cell. As shown in FIG. 11, the determination unit 102b references the change target management master 106a and determines whether the item type associated with the item number input into the change target item cell K1 is code. In the case shown in FIG. 11, the determination unit 102b determines that the item type is code (direct debit_billing suspension reason code) because the numeric value input into the change target item cell K1 is "7." In this case, the display control unit 102a displays the item name corresponding to the item of the numeric value input into the change target item cell K1 on the contract-related information bulk update screen P1.

[0043] Here, the change target items that can be entered into the change target item cell K1 are set according to the authority level of the person in charge. Specifically, the display control unit 102a refers to the person in charge master 106b and the change target management master 106a, and makes it possible to display change target items that are linked to a change target item level that is equal to or higher than the authority level of the person in charge.

[0044] FIG. 12 is a diagram showing an example of a change target item table that can be used at authority level "5." FIG. 13 is a diagram showing an example of a change target item table that can be used at authority level "3." FIG. 14 is a diagram showing an example of a change target item table that can be used at authority level "2." Note that FIG. 12 shows the case of Tanaka Taro, who has person in charge ID "3000," FIG. 13 shows the case of Yamada Jiro, who has person in charge ID "3010," and FIG. 14 shows the case of Sato Hanako, who has person in charge ID "4400."

[0045] As shown in the change target item table T8 in Fig. 12, the change target item table T9 in Fig. 13, and the change target item table T10 in Fig. 14, the display control unit 102a references the person in charge master 106b and the change target management master 106a, and makes it possible to display change target items that are linked to a change target item level that is equal to or higher than the person in charge's authority level. For example, when the contract management device 100 is started up or activated, the display control unit 102a requests input of the person in charge ID of the person in charge, and displays the change target items based on the input result.

[0046] Returning to FIG. 9, the description of step S2 and subsequent steps will be continued. In step S2, if the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is code (step S2: Yes), the contract management device 100 proceeds to step S3. On the other hand, if the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is not code (step S2: No), the contract management device 100 proceeds to step S5.

[0047] In step S3, the contract management device 100 executes a code update process for updating the code.

[0048] [2.1 Item Type: Code Update Process Overview] Here, the code update process will be described in detail. FIG. 15 is a diagram showing an example of a change target management master table T1 referenced in the code update process. FIG. 16 is a diagram showing an example of a code master table T3 referenced in the code update process. FIG. 17 is a diagram showing an example of a contract-related information batch update screen P1 displayed by the monitor 114 in the code update process. FIG. 18 is a diagram showing an example of an operation permission table for each person in charge. Note that, in the code update process, as shown in the operation permission table T11 shown in FIG. 18, the persons in charge "Taro Tanaka" and "Jiro Yamada" are operable (updateable), while the person in charge "Hanako Sato" is not operable (updateable). In other words, even if the person in charge "Hanako Sato" enters the item number "7" in the change target item cell K1, the display control unit 102a does not display the item name on the monitor 114, but displays a warning, for example, a warning indicating lack of authority, on the monitor 114.

[0049] As shown in Figure 17, when a user inputs the number "7" as the item number into the change target item cell K1 via the input device 112 and presses the confirm button B1, the display control unit 102a refers to the change target management master 106a and the person in charge master 106b, and displays a search condition input section R1 in which search conditions can be entered, and a change input section R2 in which change instructions can be entered.

[0050] The search condition input section R1 includes a customer number cell K2 in which the customer number, which is a search condition, can be entered, a pre-change cell H1 in which the date can be entered, and a display button B4 for instructing the display of data that matches the search conditions.The display control section 102a appropriately changes and displays the GUI (Graphical User Interface), position, and input content of various cells included in the search condition input section R1 in the item cell K1 to be changed according to the item number.

[0051] The following describes a case where the user inputs a customer number into customer number cell K2 via input device 112 and presses display button B4. In this case, the search unit 102c refers to the customer information data 106g and contract information data 106d, searches for contract information data 106d that corresponds to the customer number "100: Suzuki Ichiro" entered into customer number cell K2 of the search condition input information, and acquires the pre-change basic account data linked to the corresponding contract ID.

[0052] Thereafter, the search unit 102c displays the information change table Q1 corresponding to the account transfer basic data 106f indicating the state of the acquired account basic data before the change in the change input section R2 of the contract related information batch update screen P1.

[0053] The change input section R2 includes a changed cell K3 for inputting the numerical value of the changed cell in the information change table Q1, a batch set button B5 for inputting the numerical values ​​entered in the changed cell K3 all at once, an add row button B6 for adding a row by adding a contract ID in the information change table Q1, and a delete row button B7 for deleting a row by deleting a contract ID in the information change table Q1.

[0054] When the user inputs a predetermined numerical value into the changed cell K3 via the input device 112 and then presses the set all at once button B5, the display control unit 102a reflects and displays the numerical value of the changed cell K3 in the cells of the changed spread of the information change table Q1.

[0055] 19 is a diagram showing an example of the contract-related information bulk update screen P1 displayed on the monitor 114 when the bulk set button B5 is pressed. As shown in Fig. 19, when the user inputs a predetermined number, for example, "10," into the post-change cell K3 via the input device 112 and then presses the bulk set button B5, the display control unit 102a reflects and displays the number "10" and "No applicable account" of the post-change cell K3 all at once in the cells of the post-change spread of the information change table Q1.

[0056] Next, when the user presses the registration button B2 via the input device 112, the update unit 102d updates the billing suspension reason code of the account transfer basic data 106f linked to each contract ID acquired by the search unit 102c to "10".

[0057] Fig. 20 is a diagram showing an example of the account transfer basic data table T6 before and after updating by the update unit 102d. In Fig. 20, the upper row shows the account transfer basic data table T6 before the update, and the lower row shows the account transfer basic data table T6 after the update.

[0058] 20, the update unit 102d collectively updates the billing suspension reason code of the account transfer basic data 106f linked to each contract ID acquired by the search unit 102c to "10." This allows the user to update all at once. After the code update process in step S3, the contract management device 100 returns to step S4 in FIG.

[0059] Returning to FIG. 9, the description of step S4 and subsequent steps will be continued. In step S4, the determination unit 102b determines whether or not the user will end the contract management operation via the input device 112. If the determination unit 102b determines that the user will end the contract management operation via the input device 112 (step S4: Yes), the contract management device 100 ends this processing. On the other hand, if the determination unit 102b determines that the user will not end the contract management operation via the input device 112 (step S4: No), the contract management device 100 returns to step S1.

[0060] In step S5, the determination unit 102b determines whether the item type associated with the item number input into the change target item cell K1 is flag update. If the determination unit 102b determines that the item type associated with the item number input into the change target item cell K1 is flag update (step S5: Yes), the contract management device 100 proceeds to step S6. On the other hand, if the determination unit 102b determines that the item type associated with the item number input into the change target item cell K1 is not flag update (step S5: No), the contract management device 100 proceeds to step S7.

[0061] In step S6, the contract management device 100 executes a flag update process for updating the flag.

[0062] [2.2 Overview of flag update process] Here, the flag update process will be described in detail. Fig. 21 is a diagram showing an example of a change target management master table referenced in the flag update process. Fig. 22 is a diagram showing an example of a contract-related information batch update screen P1 displayed by the monitor 114 in the flag update process. Fig. 23 is a diagram showing an example of an operation possibility table for each person in charge. Note that in the flag update process in Fig. 21, as shown in the operation possibility table T21 shown in Fig. 23, the person in charge "Tanaka Taro" can operate (can update), while "Yamada Jiro" and "Sato Hanako" cannot operate (cannot update).

[0063] As shown in Figure 22, when a user inputs the number "2" as the item number into the change target item cell K1 via the input device 112 and presses the confirm button B1, the display control unit 102a refers to the change target management master 106a and displays a search condition input section R1 where search conditions can be entered and a change input section R2 where change instructions can be entered.

[0064] The search condition input section R1 includes a customer number cell K2 in which a customer number, which is a search condition, can be input, and a before-change check box K4.

[0065] 22, when the user presses the add row button B6 via the input device 112, the search unit 102c displays the flag change table Q2. Then, when the user enters a desired contract ID, for example, "10003," in the contract ID field of the flag change table Q2 via the input device 112 and presses the enter key or the like, the search unit 102c searches for contract information corresponding to the contract ID, and displays on the monitor 114 the state of the lump-sum payment exclusion flag of the contract information data before the change that is linked to the corresponding contract number, for example, in a blank state, as shown in FIG.

[0066] Thereafter, when the user selects a check box after the change in the flag change table Q2 via the input unit 112, the search unit 102c reflects the check mark in the check box after the change.

[0067] 24 is a diagram showing an example of a contract-related information batch update screen P1 displayed in the flag update process by the monitor 114. As shown in FIG. 24, when the user selects a check box after the change in the flag change table Q2 via the input unit 112, the search unit 102c reflects a check mark in the check box after the change.

[0068] Thereafter, when the user selects the changed checkbox in the flag change table Q2 via the input unit 112 and presses the registration button B2, the update unit 102d updates the value of a specified item for the pre-change contract information data linked to the relevant contract number to the value of the contents of the changed checkbox in the flag change table Q2 inputted into the change input unit R2.

[0069] Fig. 25 is a diagram showing an example of the contract information data table T4 before and after updating by the updating unit 102d. In Fig. 25, the upper part shows the contract information data table T4 before updating, and the lower part shows the contract information data table T4 after updating.

[0070] 25, the update unit 102d updates a predetermined item in the pre-update contract information data table T4 linked to the relevant contract number, specifically the lump-sum payment exclusion flag "FALSE," to the value "TRUE" of the checkbox content after the change in the flag change table Q2 inputted into the change input unit R2. After the flag update process in step S6, the contract management device 100 proceeds to step S4 in FIG.

[0071] Returning to FIG. 9, the description of step S7 and subsequent steps will be continued. In step S7, the determination unit 102b determines whether the item type linked to the item number input in the change target item cell K1 is date update. If the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is date update (step S7: Yes), the contract management device 100 proceeds to step S8. On the other hand, if the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is not date update (step S7: No), the contract management device 100 proceeds to step S9.

[0072] In step S8, the contract management device 100 executes a date update process to update the date.

[0073] [2.3 Overview of date update process] Here, the date update process will be described in detail. Fig. 26 is a diagram showing an example of a change target management master table T1 referenced in the date update process. Fig. 27 is a diagram showing an example of a contract-related information batch update screen P1 displayed by the monitor 114 in the date update process. Fig. 28 is a diagram showing an example of an operation possibility table for each person in charge. Note that in the date update process in Fig. 28, as shown in the operation possibility table T31 shown in Fig. 28, the people in charge "Tanaka Taro", "Yamada Jiro", and "Sato Hanako" are operable (updatable).

[0074] 27, when the user inputs the desired dates and times "2023 / 3 / 1" and "2023 / 3 / 31" into pre-change cells H1, which allow input of dates via the input device 112, and presses the display button B4, the search unit 102c searches the scheduled contract change data 106e for contract change data corresponding to the dates and times "2023 / 3 / 1" to "2023 / 3 / 31" input into pre-change cells H1, and obtains the pre-change scheduled contract change data linked to the dates and times "2023 / 3 / 1" to "2023 / 3 / 31." The search unit 102c then displays a scheduled change table Q3, which shows the pre-change state of the obtained scheduled contract change data, in the change input section R2 of the contract-related information batch update screen P1.

[0075] Thereafter, the display control unit 102a displays the date and time that the user inputs via the input device 112 into the post-change cell of each contract ID in the scheduled change table Q3.

[0076] 29 is a diagram showing an example of a contract-related information batch update screen P1 displayed during the date update process on the monitor 114. As shown in Fig. 29, the display control unit 102a displays the dates and times "2023 / 4 / 10" and "2023 / 5 / 10" that the user entered via the input device 112 into the post-change cells for each contract ID in the scheduled change table Q3.

[0077] Next, when the user presses the registration button B2 via the input device 112, the update unit 102d updates the scheduled date and time for the pre-change contract information data corresponding to the date and time of the specified period from "2023 / 3 / 10" to "2023 / 4 / 10" and "2023 / 5 / 10" entered in the post-change cells of each contract ID.

[0078] 30 is a diagram showing an example of the contract change schedule data table T5 before and after updating by the update unit 102d. In Fig. 30, the upper row shows the contract change schedule data table T5 before the update, and the lower row shows the contract change schedule data table T5 after the update.

[0079] 30, the update unit 102d updates the scheduled date and time "2023 / 3 / 10" in the pre-change contract change schedule data table T5 that corresponds to the date and time of the specified period to "2023 / 4 / 10" and "2023 / 5 / 10" that are entered in the post-change cells of each contract ID. After the date update process in step S8, the contract management device 100 proceeds to step S4 in FIG.

[0080] Returning to FIG. 9, the description of step S9 and subsequent steps will be continued. In step S9, the determination unit 102b determines whether the item type linked to the item number input in the change target item cell K1 is amount update. If the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is flag update (step S9: Yes), the contract management device 100 proceeds to step S10. On the other hand, if the determination unit 102b determines that the item type linked to the item number input in the change target item cell K1 is not flag update (step S9: No), the contract management device 100 proceeds to step S11.

[0081] In step S10, the contract management device 100 executes an amount update process for updating the amount.

[0082] [2.4 Overview of Amount Update Processing] Here, the amount update process will be described in detail. Fig. 31 is a diagram showing an example of a change target management master table referenced in the amount update process. Fig. 32 is a diagram showing an example of a contract-related information batch update screen P1 displayed by the monitor 114 in the amount update process. Fig. 33 is a diagram showing an example of an operation possibility table for each person in charge. In the amount update process in Fig. 33, as shown in the operation possibility table T41 shown in Fig. 33, the people in charge "Tanaka Taro", "Yamada Jiro", and "Sato Hanako" can operate (can update).

[0083] 32, when the Add Row button B6 is pressed, the display control unit 102a displays a contract change schedule table Q4. Thereafter, the user enters a desired contract ID, for example, "10002," into the contract ID field of the flag change table Q2 via the input device 112 and presses the Enter key or the like. In this case, the search unit 102c searches the contract information data 106d for contract information corresponding to the contract ID and acquires the pre-change contract information data 106d linked to the corresponding contract number. The search unit 102c then displays on the monitor 114 the contract change schedule table Q4, which shows the pre-change state of the acquired contract information data 106d.

[0084] Thereafter, when the user inputs the planned additional amount into the post-change cell K12 via the input unit 112, the display control unit 102a displays the planned additional amount in the post-change cell K12.

[0085] 34 is a diagram showing an example of the contract-related information batch update screen P1 displayed during the amount update process by the monitor 114. As shown in FIG. 34, when the user inputs "123,456,789,012,345" into the post-change cell K12 via the input unit 112, the display control unit 102a displays "123,456,789,012,345" in the post-change cell K12.

[0086] Thereafter, when the user presses the registration button B2 via the input unit 112, the update unit 102d updates the planned additional amount (amount of a specified item) for the pre-change contract change planned data 106e linked to the corresponding contract number to the amount "123,456,789,012,345" entered in the post-change cell K12.

[0087] Fig. 35 is a diagram showing an example of the contract change schedule data table T5 before and after updating by the update unit 102d. In Fig. 35, the upper row shows the contract change schedule data table T5 before the update, and the lower row shows the contract change schedule data table T5 after the update.

[0088] 35, the update unit 102d updates the planned additional amount (amount of a predetermined item) in the pre-change contract change plan data table T5 linked to the relevant contract number to the amount "123,456,789,012,345" entered in the post-change cell K12. After the amount update process in step S10, the contract management device 100 proceeds to step S4 in FIG.

[0089] Returning to FIG. 9, the description of step S11 and subsequent steps will be continued. In step S11, the determination unit 102b determines whether the item type associated with the item number input into the change target item cell K1 is full-width character update. If the determination unit 102b determines that the item type associated with the item number input into the change target item cell K1 is full-width character update (step S11: Yes), the contract management device 100 proceeds to step S12. On the other hand, if the determination unit 102b determines that the item type associated with the item number input into the change target item cell K1 is not full-width character update (step S11: No), the contract management device 100 ends this process.

[0090] In step S6, the contract management device 100 executes a full-width character update process for updating full-width characters.

[0091] [2.5 Overview of full-width character update processing] Here, the full-width character update process will be described in detail. Fig. 36 is a diagram showing an example of a change target management master table referenced in the full-width character update process. Fig. 37 is a diagram showing an example of a contract-related information batch update screen P1 displayed by the monitor 114 in the full-width character update process. Fig. 38 is a diagram showing an example of an operation possibility table for each person in charge. Note that in the full-width character update process in Fig. 38, as shown in the operation possibility table T51 shown in Fig. 38, the people in charge, "Tanaka Taro," "Yamada Jiro," and "Sato Hanako," are operable (updatable).

[0092] As shown in FIG. 37, when the user inputs "5" for the contract change schedule notes into the change target item cell K1 via the input device 112, the display control unit 102a displays the pre-change cell K21 in the change input section R2.

[0093] Thereafter, when the user inputs "contract change schedule" in the change input section R2 via the input device 112 and presses the display button B4, the search unit 102c searches the contract change schedule data 106e for contract change schedule data 106e that corresponds to the "contract change schedule" input in the pre-change cell K21, and acquires the pre-change contract change schedule data 106e. The search unit 102c then displays the contract change schedule table Q5 for the acquired pre-change contract change schedule data 106e in the change input section R2 of the contract-related information batch update screen P1.

[0094] Fig. 39 is a diagram showing an example of the contract-related information batch update screen P1 displayed in the full-width character update process by the monitor 114. As shown in Fig. 39, when the user presses the register button B2 with the post-change cells in the contract change schedule table Q4 left blank via the input device 112, the update unit 102d initializes and updates the notes "Contract change scheduled due to XX" and "Contract change scheduled due to △△" for the pre-change contract information data that correspond to the contract change schedule notes.

[0095] Fig. 40 is a diagram showing an example of the contract change schedule data table T5 before and after updating by the update unit 102d. In Fig. 40, the upper row shows the contract change schedule data table T5 before the update, and the lower row shows the contract change schedule data table T5 after the update.

[0096] 40, the update unit 102d initializes and updates the notes "Contract change planned due to XX" and "Contract change planned due to △△" for the pre-change contract change plan data 106e that corresponds to the contract change plan notes. After the full-width character update process, the contract management device 100 proceeds to step S4 in FIG.

[0097] According to the embodiment described above, when the user presses the registration button B2 via the input device 112, the update unit 102d updates the billing suspension reason code of the account transfer basic data 106f linked to each contract ID acquired by the search unit 102c to "10", thereby improving work accuracy and shortening work time while reducing system development costs.

[0098] Furthermore, according to the embodiment, the update unit 102d updates a specified item in the pre-update contract information data table T4 linked to the relevant contract number, specifically the lump-sum payment exclusion flag "FALSE", to the value of the changed checkbox content in the flag change table Q2 input into the change input unit R2, so that updating can be done with a simple operation.

[0099] Furthermore, according to the embodiment, the update unit 102d updates the scheduled date and time in the pre-change contract change schedule data table T5 that corresponds to the date and time of the specified period to the date and time entered in the post-change cell for each contract ID, so that all the dates and times can be updated to the desired date and time in one go.

[0100] Furthermore, according to the embodiment, the update unit 102d updates the amount of a specified item for the pre-change contract change schedule data 106e linked to the relevant contract number to the amount entered in the post-change cell K12, thereby enabling updating with a simple operation.

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

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

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

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

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

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

[0107] Furthermore, with regard to the contract 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.

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

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

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

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

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

[0113] The contract 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 to which any peripheral device is connected. The contract 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.

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

[0115] The present invention is useful in the financial industry, which performs credit management operations. [Explanation of symbols]

[0116] 100 Contract management device 102 Control section 102a Display control unit 102b Judgment section 102c Search Section 102d Update Department 104 Communication interface unit 106 Storage section 106a Management Master to be Changed 106b Personnel Master 106c Code Master 106d Contract information data 106e Contract change schedule data 106f Account Transfer Basic Data 106g Customer Information Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

[Claim 1] A contract management device including a control unit, A change target management master in which at least item names, table names, column names, item types, data lengths, and code types are associated with item numbers; A code master in which code values ​​and code names are associated with code types; Contract information data in which the contract ID is associated with the contract number, customer number, contract date, contract classification code, and lump-sum payment exclusion flag; Account transfer basic data in which a billing suspension flag and a billing suspension reason code are associated with a contract ID; Customer information data in which customer numbers are associated with customer names, is accessible to The control unit a display control unit that refers to the change target management master and displays on a monitor a search condition input unit in which search conditions corresponding to the change target items to be input and a change input unit in which change instructions can be input; a search unit that, when the input item to be changed is a code and a customer number is input to the search condition input unit, searches the basic account transfer data for the contract information data corresponding to the customer number input to the search condition input unit based on the customer information data, the contract information data, and the code master, and obtains the basic account transfer data before the change that is linked to the relevant contract ID and displays it on the monitor; an update unit that updates the contents of predetermined items in the basic account transfer data before the change associated with the relevant contract ID to the input contents input to the change input unit; To have A contract management device comprising:

Images