Claim management apparatus, claim management method, and claim management program

Abstract

To improve business efficiency by reducing a risk that processing related to credit management is performed in a state where an application is not approved.SOLUTION: A control unit configured to execute application processing of a workflow related to bond management, and a display unit, wherein application data applied and registered in the application processing and contract data of bond management are accessible, and the application data is associated with information including an application ID for identifying application, a contract ID for identifying bond management contract, and an approval flag indicating an approval status of the application, the contract data is associated with information including a contract ID and a name of a contract target, the control unit displays a management screen for credit management on the display unit, acquires application data when executing processing based on the management screen, determines whether or not the application is in an unapproved state based on an approval flag of the application data, and displays a warning image indicating that the application is in an unapproved state on the management screen in association with the contract data when determining that the application is in the unapproved state.SELECTED DRAWING: Figure 9

Description

[Technical Field]

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

[0002] Conventionally, there is known an approval request confirmation device that displays a message on a monitor when an approval request is made in a workflow (see, for example, Patent Document 1). In this approval request confirmation device, the application content and the approval status such as approved or unapproved are stored in association with each other. When expense input for an approval request in a workflow is performed, the approval request confirmation device displays a warning on the monitor if the approval request is unapproved. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-093954 Summary of the Invention [Problem to be solved by the invention]

[0004] There are cases where processing related to receivables management, such as issuing a reminder letter or a repayment schedule, is carried out when a workflow application has not yet been approved. If processing related to receivables management is carried out when an application has not yet been approved, it can cause confusion in receivables management operations and unnecessary confirmation work related to the application. For example, if a reminder letter is issued when the registered details of a deposit reconciliation have not yet been approved, it may be issued even if the payment has already been made. In order to reduce the issuance of reminder letters, it is necessary to check the approval status of the application on a separate screen, which reduces work efficiency.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a debt management device, a debt management method, and a debt management program that can reduce the risk of debt management processing being carried out without an application being approved, and improve business efficiency. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objective, the receivables management device of the present invention is a receivables management device that has a control unit that executes application processing of a workflow related to receivables management, and a display unit, and is capable of accessing application data, which is data applied for and registered in the application processing, and contract data, which is data related to the receivables management contract, and the application data is associated with information including an application ID that identifies the application, a contract ID that identifies the receivables management contract, and an approval flag that indicates the approval status of the application, and the contract data is associated with information including the contract ID and the name of the contract subject, and the control unit displays a management screen for the receivables management on the display unit, and when processing based on the management screen is executed, acquires the application data and determines whether the application is in an unapproved state based on the approval flag of the application data, and if it is determined that the application is in an unapproved state, displays a warning image on the management screen, corresponding to the contract data, indicating that the application is in an unapproved state.

[0007] In addition, in the receivables management device of the present invention, multiple management screens are provided, and it is possible to further access a screen type master, which is information regarding the type of management screen, and a check master, which is information regarding the transaction details to be checked; the screen type master is associated with information including a screen type ID that identifies the type of management screen and the name of the management screen; the check master is associated with information including the screen type ID and a transaction detail code, which is a code that identifies the transaction details; the application data further includes information regarding the transaction detail code; the control unit may identify the type of management screen displayed on the display unit based on the screen type master, obtain the transaction details corresponding to the identified type of management screen based on the check master, and determine the approval status of the application corresponding to the obtained transaction details based on the application data.

[0008] In addition, in the loan management device according to the present invention, the management screen may include a screen relating to the process of issuing a reminder letter and a screen relating to the process of issuing a repayment schedule.

[0009] In addition, the receivables management method of the present invention is a receivables management method that executes application processing of a workflow related to receivables management, and uses application data, which is data registered in the application processing, and contract data, which is data related to the receivables management contract, and the application data is associated with information including an application ID that identifies the application, a contract ID that identifies the receivables management contract, and an approval flag that indicates the approval status of the application, and the contract data is associated with information including the contract ID and the name of the contract subject, and a receivables management device equipped with a control unit displays a management screen for the receivables management on a display unit, and when processing based on the management screen, acquires the application data, determines whether the application is in an unapproved state based on the approval flag of the application data, and if it is determined that the application is in an unapproved state, associates it with the contract data and displays a warning image indicating that the application is unapproved on the management screen.

[0010] In addition, the receivables management program of the present invention is a receivables management program for causing a receivables management device equipped with a control unit to execute a receivables management method for executing application processing of a workflow related to receivables management, and uses application data, which is data registered in the application processing, and contract data, which is data related to the receivables management contract, and the application data is associated with information including an application ID that identifies the application, a contract ID that identifies the receivables management contract, and an approval flag that indicates the approval status of the application, and the contract data is associated with information including the contract ID and the name of the contract subject, and causes the receivables management device to display a management screen for the receivables management on a display unit, and when processing based on the management screen is executed, acquire the application data, determine whether the application is in an unapproved state based on the approval flag of the application data, and if it is determined that the application is in an unapproved state, associate it with the contract data and display a warning image indicating that the application is unapproved on the management screen. [Effects of the Invention]

[0011] The present invention has the effect of reducing the risk that processing related to credit management will be carried out without an application being approved, thereby improving business efficiency. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a claim management device. [Figure 2] FIG. 2 is a diagram illustrating an example of the screen type master. [Figure 3] FIG. 3 is a diagram illustrating an example of the check master. [Figure 4] FIG. 4 is a diagram illustrating an example of application data. [Figure 5] FIG. 5 is a diagram illustrating an example of contract data. [Figure 6] FIG. 6 is a diagram illustrating an example of a workflow application. [Figure 7] FIG. 7 is a diagram showing an example of a process for issuing a reminder letter. [Figure 8]FIG. 8 is a diagram showing an example of a repayment schedule issuing process. [Figure 9] FIG. 9 is a flowchart showing an example of the bond management process. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of a claim management device, a claim management method, and a claim 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.

[0014] [1. Configuration] An example of the configuration of a claim management device 100 according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the configuration of a claim management device.

[0015] The claim management device 100 is a device that executes processes related to claim management. Specifically, the claim management device 100 executes, for example, application processes for workflows related to claim management, processes for issuing reminders, and processes for issuing repayment schedules.

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

[0017] The bond management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the bond management device 100 is connected to each other so that they can communicate with each other via any communication path.

[0018] The communication interface unit 104 communicatively connects the claim 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 claim 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). The data stored in the memory unit 106 may also be stored in the server 200, for example.

[0019] 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 (display unit) 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0020] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0021] The storage unit 106 stores various masters and various data. Specifically, the storage unit 106 stores a screen type master 121, a check master 122, application data 123, contract data, etc. The various masters and various data will be explained below. Note that if there are overlapping items among the items included in the various masters and various data, some of the explanations for the overlapping items will be omitted.

[0022] FIG. 2 is a diagram showing an example of a screen type master. The screen type master 121 is data used to identify the type of management screen related to credit management that is displayed on the display unit 114. Examples of management screens include a screen related to the issuance process of a reminder letter and a screen related to the issuance process of a repayment schedule, but the management screen is not limited to these screens and can be any screen related to credit management. As shown in FIG. 2, the screen type master 121 includes items for a screen type ID and a screen type name, and these items are associated with each other. The screen type ID is a number for identifying the type of management screen. The screen type name is the name of the management screen.

[0023] FIG. 3 is a diagram showing an example of a check master. The check master 122 is data on transaction details to be checked depending on the type of management screen. The check master 122 includes items for a screen type ID and a transaction content code, and these items are associated with each other. The screen type ID is the same as the screen type master 121. The transaction content code is a code for identifying the transaction content. The transaction content code is also written with the name of the transaction content.

[0024] FIG. 4 is a diagram showing an example of application data. Application data 123 is data registered as an application during workflow application processing. Application data 123 is generated during workflow application, which will be described later. Application data 123 includes the following items: application ID, transaction content code, contract ID, and approval status, and these items are associated with each other. The transaction content code is the same as that of check master 122. The application ID is a number used to identify the application. The contract ID is a number used to identify the contract. The approval status is an approval flag that determines whether the application has been approved or not. When the approval flag is "0", the application is not approved, and when the approval flag is "1", the application is approved. The approval status is also indicated as either not approved or approved.

[0025] FIG. 5 is a diagram showing an example of contract data. Contract data 124 is data related to a contract for credit management. Contract data 124 includes items of contract ID and contract holder name, and these items are associated with each other. The contract ID is the same as in application data 123. The contract holder name is the name of the contract holder.

[0026] Next, referring again to Figure 1, the control unit 102 will be described. The control unit 102 is a CPU or the like that performs overall control of the claim 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.

[0027] The control unit 102 performs information processing, such as processing related to credit management, based on various masters and various data stored in the storage unit 106 .

[0028] A specific example of the processing executed by the control unit 102 will be described in detail below in [2. Specific Example of Processing].

[0029] [2. Specific examples of processing] Here, specific examples of processing executed by the claim management device 100 will be described with reference to Figs. 6 to 9. Fig. 6 is a diagram showing an example of a workflow application. Fig. 7 is a diagram showing an example of a reminder letter issuance processing. Fig. 8 is a diagram showing an example of a repayment schedule issuance processing. Fig. 9 is a flowchart showing an example of claim management processing.

[0030] As shown in Fig. 6, in the workflow application process, the claim management device 100 performs input based on a predetermined input screen and then registers the data, thereby generating application data 123. Specifically, in Fig. 6, as workflow applications, for example, an application for processing related to clearing of deposit, an application for processing related to early full repayment, and an application for processing related to partial early repayment are performed in that order.

[0031] When the receivable management device 100 executes an application for processing related to a deposit reconciliation, it displays a deposit reconciliation input screen on the display unit 114. The deposit reconciliation input screen includes a field for inputting a temporary receipt ID, a field for inputting the amount of the temporary receipt, a field for inputting a contract ID, and a field for inputting the amount to be reconciled. The temporary receipt ID is a number for identifying the temporary receipt. When each field on the deposit reconciliation input screen is input via the input device 112 and the register button on the screen is operated, the control unit 102 of the receivable management device 100 generates application data 123 based on each input field. The generated application data 123 contains, for example, data in which the application ID is "1," the transaction content code is "100: Deposit reconciliation," the contract ID is "10001," and the approval status is "0: Unapproved," and these are associated with each other.

[0032] Next, when the claim management device 100 executes an application for processing related to early repayment, it displays an early repayment input screen on the display unit 114. The early repayment input screen includes a field for entering a contract ID and a field for entering an early repayment date. When each field on the early repayment input screen is entered via the input device 112 and the register button on the screen is operated, the control unit 102 of the claim management device 100 generates application data 123 based on each entered field. In this case, the generated application data 123 is added to the application data 123 generated in the application processing for deposit reconciliation. The generated application data 123 contains, for example, an application ID of "2," a transaction content code of "200: Early repayment," a contract ID of "10002," and an approval status of "0: Unapproved," and these are associated data.

[0033] After this, when the claim management device 100 executes an application for processing related to partial advance repayment, it displays a partial advance repayment input screen on the display unit 114. The partial advance repayment input screen includes a field for inputting a contract ID, a field for inputting the advance repayment date, and a field for inputting the advance amount. When each field on the partial advance repayment input screen is input via the input device 112 and the register button on the screen is operated, the control unit 102 of the claim management device 100 generates application data 123 based on each input field. In this case, the generated application data 123 is added to the application data 123 generated in the application processing for deposit reconciliation and early repayment. The generated application data 123 is data in which, for example, the application ID is "3," the transaction content code is "300: partial advance," the contract ID is "10003," and the approval status is "0: not approved," and these are associated with each other.

[0034] In this way, the claim management apparatus 100 generates the application data 123 shown in FIG. 4 by executing the application process of the workflow related to claim management.

[0035] Next, processing based on the management screen will be described with reference to Figures 7 and 8. For example, when the debt management device 100 executes the dunning notice issuance processing shown in Figure 7, it displays a dunning notice issuance screen as the management screen. The dunning notice issuance screen includes input fields for entering specified extraction conditions and display fields for displaying contract data. The control unit 102 of the debt management device 100 extracts contract data 124 using the input fields on the dunning notice issuance screen as extraction conditions, and displays the extracted contract data 124 in the display fields of the dunning notice issuance screen. Then, when the execute button on the screen is operated, the control unit 102 of the debt management device 100 displays a warning image on the dunning notice issuance screen if there is contract data 124 for which the application has not been approved. The warning image includes a message indicating that there is a contract for which the application has not been approved, and a message indicating the contract ID and transaction content code of the corresponding contract data 124.

[0036] For example, when the receivable management device 100 executes the repayment schedule issuance process shown in Figure 8, it displays a repayment schedule issuance screen as a management screen. The repayment schedule issuance screen includes input fields for entering specified extraction conditions and display fields for displaying contract data. The control unit 102 of the receivable management device 100 extracts contract data 124 using the input fields on the repayment schedule issuance screen as extraction conditions, and displays the extracted contract data 124 in the display fields of the repayment schedule issuance screen. Then, when the execute button on the screen is operated, the control unit 102 of the receivable management device 100 displays a warning image on the repayment schedule issuance screen if there is contract data 124 for which the application has not been approved. The warning image includes a message indicating that there is a contract for which the application has not been approved, and a message indicating the contract ID and transaction content code of the corresponding contract data 124.

[0037] Next, an example of processing based on the management screens shown in Figures 7 and 8 will be described with reference to Figure 9. When the control unit 102 of the receivables management device 100 displays the management screen on the display unit 114, it acquires the contract data 124 and the check master 122 (step S1). Next, the control unit 102 determines whether there are any details to be processed (contract IDs of the contract data 124) (step S2). Specifically, in step S2, the control unit 102 acquires the contract IDs of the contract data 124 that meet the extraction conditions entered on the management screen and sets them as the contract IDs to be processed. Therefore, taking the contract data 124 shown in Figures 7 and 8 as an example, the contract IDs to be processed are "10001", "10002", and "10003".

[0038] When the control unit 102 determines that there is a contract ID to be processed (step S2: Yes), it determines whether there is a transaction content code corresponding to the management screen based on the acquired check master 122 (step S3). In step S3, for example, if the management screen is a repayment schedule issuance screen, the control unit 102 determines that there are "200: Early repayment" and "300: Partial advance" as transaction content codes in the check master 122 (step S3: Yes).

[0039] If the control unit 102 determines that a transaction content code is present, it determines based on the application data 123 whether or not there is application data 123 that has a transaction content code corresponding to the contract ID and whose approval status is "unapproved" (step S4). If the control unit 102 determines that application data 123 is present in step S4 (step S4: Yes), it acquires the corresponding application data 123 (step S5). In step S5, for example, if the management screen is the repayment schedule issuance screen, the control unit 102 acquires application IDs "2" and "3" whose transaction content codes correspond to "200: early repayment" and "300: partial advance" and whose approval status is "0: unapproved." Furthermore, the control unit 102 counts the number of application IDs acquired in step S5 as the number of acquired applications.

[0040] After executing step S5, the control unit 102 adds the contract ID and transaction content code displayed in the warning image as message details (step S6). After executing step S6, the control unit 102 determines that the contract ID to be processed has been processed, and proceeds to step S2 again. The control unit 1023 repeatedly executes steps S2 to S7 until there are no more contract IDs to be processed. By processing steps S2 to S7, for example, when the management screen is a repayment schedule issuance screen, the control unit 102 can determine the approval status of the application for six combination patterns obtained by multiplying three contract IDs by two transaction content codes.

[0041] If the control unit 102 determines in step S3 that the transaction content code is not present (step S3: No), or if it determines in step S4 that the application data 123 is not present (step S4: No), the control unit 102 proceeds to step S7.

[0042] If the control unit 102 determines in step S2 that there is no contract ID to be processed (step S2: No), it determines whether the number of application IDs acquired from the application data 123 is 1 or more (step S8). If the control unit 102 determines that the number of acquired IDs is 1 or more (step S8: Yes), it displays a warning image on the management screen together with message details (step S9) and ends the processing based on the management screen. On the other hand, if the control unit 102 determines that the number of acquired IDs is not 1 or more (step S8: No), it does not display a warning image and ends the processing based on the management screen.

[0043] As described above, according to this embodiment, if a workflow application has not been approved, a warning image can be displayed on the management screen. Therefore, by displaying the warning image, it is possible to reduce the risk that processing related to credit management will be carried out when the application has not been approved. Furthermore, it is possible to reduce unnecessary work, such as the work of checking the approval status of the application, thereby improving work efficiency.

[0044] Furthermore, according to this embodiment, the approval status of an application can be determined based on the type of management screen and the transaction content, so that transactions that require checking can be selected and the approval status of the application can be determined.

[0045] Furthermore, according to this embodiment, the management screen can be applied to a screen related to the process of issuing reminder letters (reminder letter issuance screen) and a screen related to the process of issuing repayment schedules (repayment schedule issuance screen), and therefore a warning image can be displayed on these screens.

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

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

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

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

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

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

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

[0053] For example, all or any part of the processing functions of the claim 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 processing described in this embodiment, and is mechanically read by the claim 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.

[0054] In addition, this computer program may be stored in an application program server connected to the claim management device 100 via any network, and all or part of it may be downloaded as needed.

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

[0056] 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 program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by cooperating with other programs, such as an OS. Note that the specific configurations and reading procedures for reading a recording medium in each device shown in the embodiments, as well as the installation procedures after reading, can use well-known configurations and procedures.

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

[0058] The claim 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 claim management device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

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

[0060] The present invention is useful in the industry that handles credit management. [Explanation of symbols]

[0061] 100 Debt management device 102 Control section 104 Communication interface unit 106 Storage section 108 Input / Output Interface Section 112 Input Device 114 Output device (display section) 121 Screen Type Master 122 Check Master 123 Application Data 124 Contract Data 200 servers 300 Network

Claims

1. A claim management device comprising a control unit that executes application processing for a workflow related to claim management, and a display unit, The application data is data registered in the application process, and the contract data is data related to the credit management contract. The application data is associated with information including an application ID for identifying the application, a contract ID for identifying the contract for the claim management, and an approval flag indicating the approval status of the application, The contract data is associated with information including the contract ID and the name of the contract subject, The control unit displaying a management screen for the credit management on the display unit; When executing a process based on the management screen, the application data is acquired; determining whether the application is in an unapproved state based on the approval flag of the application data; When it is determined that the application is in an unapproved state, the debt management device displays a warning image indicating that the application is unapproved on the management screen in association with the contract data.

2. A plurality of management screens are provided, The screen type master, which is information about the type of the management screen, and the check master, which is information about the transaction content to be checked, can be further accessed. The screen type master is associated with information including a screen type ID that identifies the type of the management screen and a name of the management screen, The check master is associated with information including the screen type ID and a transaction content code that is a code for identifying the transaction content, The application data further includes information on the transaction content code, The control unit Identifying the type of the management screen displayed on the display unit based on the screen type master; Acquire transaction details corresponding to the identified type of management screen based on the check master; 2. The claim management device according to claim 1, wherein the approval status of the application corresponding to the acquired transaction content is determined based on the application data.

3. 3. The debt management device according to claim 2, wherein the management screen includes a screen relating to the issuance of a demand letter and a screen relating to the issuance of a repayment schedule.

4. A claim management method for executing application processing of a workflow related to claim management, Application data, which is data applied for and registered in the application process, and contract data, which is data related to the contract for the credit management, are used, The application data is associated with information including an application ID for identifying the application, a contract ID for identifying the contract for the claim management, and an approval flag indicating the approval status of the application, The contract data is associated with information including the contract ID and the name of the contract subject, Displaying the management screen for the credit management on a display unit, When executing a process based on the management screen, the application data is acquired; determining whether the application is in an unapproved state based on the approval flag of the application data; A debt management method executed by a debt management device equipped with a control unit, in which, if it is determined that an application is in an unapproved state, a warning image indicating that the application is unapproved is displayed on the management screen in association with the contract data.

5. A claim management program for causing a claim management device having a control unit to execute a claim management method for executing application processing of a workflow related to claim management, Application data, which is data applied for and registered in the application process, and contract data, which is data related to the contract for the credit management, are used, The application data is associated with information including an application ID for identifying the application, a contract ID for identifying the contract for the claim management, and an approval flag indicating the approval status of the application, The contract data is associated with information including the contract ID and the name of the contract subject, Displaying the management screen for the credit management on a display unit, When executing a process based on the management screen, the application data is acquired; determining whether the application is in an unapproved state based on the approval flag of the application data; A debt management program that causes the debt management device to execute the following: if it determines that an application is unapproved, display a warning image indicating that the application is unapproved on the management screen, in association with the contract data.

Images