CREDIT MANAGEMENT DEVICE, CREDIT MANAGEMENT METHOD, AND CREDIT MANAGEMENT PROGRAM

Abstract

To manage credit management work with high accuracy.SOLUTION: An extraction part extracts data for a plurality of new applications from a credit management database. A classification part classifies the extracted data for a plurality of new applications into data for individual applications being data for a new application of an individual application object and data for a collective application being data for new applications of a collective application object on the basis of client state information. A credit limit reference calculation part calculates a new credit limit reference amount being a novel credit limit reference amount in each of the data for individual applications and the data for collective applications on the basis of an evaluation point of a financial index of a client identified by client state information. A notification part notifies a person in charge of applications identified by corresponding person in charge of applications identification information of data for an individual application including the evaluation point and a new credit limit reference amount, and data for a collective application including the evaluation point and the credit limit reference amount.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] There are known systems that perform credit management. For example, a user visually checks and extracts data on customers whose credit limit is about to expire from all customer data registered in a core system, and applies for a credit limit for the next applicable period. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-198183 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, the application for the next credit limit for the application deadline was made using the customer data extracted visually by the user, and there were cases where processing of the credit management work was missed. In other words, in the conventional technology, it was difficult to manage the credit management work with high accuracy.

[0005] The present invention has been made in consideration of the above problems, and has an object to provide a credit management device, a credit management method, and a credit management program that are capable of managing credit management operations with high accuracy. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, a credit management device according to the present invention is a credit management device that includes a control unit and a storage unit and manages credit, the storage unit stores a credit management database that associates at least a customer identification information of a customer, customer status information, financial statement data indicating financial indicators, a previous credit limit which is a currently set credit limit amount, and an application deadline of the previous credit limit amount, and a workflow database in which a plurality of application data are registered that associate at least the customer identification information, application officer identification information, and the previous credit limit base amount which is a credit limit base amount currently set for the customer, and the control unit stores the credit management database and the workflow database. S? the customer identification information having an application deadline a predetermined period from the current time point; and an extraction unit that extracts a plurality of new application data including the extracted customer identification information, the financial statement data, the previous credit limit reference amount, and the previous credit limit amount corresponding to the extracted customer identification information; a classification unit that classifies the extracted plurality of new application data into individual application data that is the new application data to be applied individually and collective application data that is the new application data to be applied collectively, based on the customer status information; a credit limit reference amount calculation unit that calculates a new credit limit reference amount, which is the new credit limit reference amount, for each of the individual application data and the collective application data, based on an evaluation score of the financial indicators of the customer identified by the customer identification information; and a notification unit that notifies the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount, to an application person identified by the corresponding application person identification information.

[0007] In addition, the classification unit in the credit management device of the present invention classifies, among the multiple extracted new application data, the new application data whose business partner status information indicates that the business partner is a suspect customer into the individual application data, and classifies the new application data whose business partner status information indicates that the business partner is not a suspect customer into the bulk application data.

[0008] In addition, the memory unit in the credit management device of the present invention stores an evaluation point master that corresponds the threshold value of the financial indicator with the evaluation point, and a limit master that corresponds the evaluation point with the credit limit reference amount, and the credit limit reference amount calculation unit identifies, for each of the individual application data and the bulk application data, the evaluation point corresponding to the financial indicator represented by the financial statement data of the business partner identified by the business partner identification information from the evaluation point master, and calculates the credit limit reference amount corresponding to the evaluation point identified in the limit master as the new credit limit reference amount.

[0009] In addition, the notification unit in the credit management device of the present invention notifies the application person identified by the corresponding application person identification information of an individual application screen of the individual application data which further includes information indicating the direction of change of the evaluation point relative to the previously identified evaluation point.

[0010] Furthermore, the notification unit in the credit management device according to the present invention notifies the application person identified by the corresponding application person identification information of a collective application screen including a list of the collective application data.

[0011] In addition, the notification unit in the credit management device of the present invention further notifies the corresponding approver of at least one of the individual application data and the collective application data, which further includes the credit limit application amount entered by the application person based on at least one of the individual application data and the collective application data.

[0012] In addition, the control unit in the credit management device of the present invention further includes a registration unit that registers the individual application data and the collective application data, including the credit limit application amount entered by the application person in the workflow database.

[0013] A credit management method according to the present invention is a credit management method that is executed by an information processing device that has a control unit and a storage unit and manages credit, the storage unit stores a credit management database that associates at least a customer identification information of a customer, customer status information, financial statement data indicating financial indicators, a previous credit limit which is a currently set credit limit amount, and an application deadline of the previous credit limit amount, and a workflow database in which a plurality of application data are registered that associate at least the customer identification information, application officer identification information, and the previous credit limit base amount which is a credit limit base amount currently set for the customer, and the credit management database and the workflow database executed by the control unit are stored. S? the step of extracting the customer identification information having an application deadline a predetermined period from the current time from the customer identification information, and extracting a plurality of new application data including the extracted customer identification information, the financial statement data, the previous credit limit reference amount, and the previous credit limit amount corresponding to the extracted customer identification information; the step of classifying the extracted plurality of new application data into individual application data which is the new application data to be applied for an individual application and collective application data which is the new application data to be applied for in a collective application based on the customer status information; the step of calculating a new credit limit reference amount which is the new credit limit reference amount for each of the individual application data and the collective application data based on an evaluation score of the financial indicators of the customer identified by the customer identification information; and the step of notifying the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount, to an application person identified by the corresponding application person identification information.

[0014] A credit management program according to the present invention is a credit management program that is executed by an information processing device that has a control unit and a storage unit and manages credit, the storage unit stores a credit management database that associates at least a customer identification information of a customer, customer status information, financial statement data indicating financial indicators, a previous credit limit which is a currently set credit limit amount, and an application deadline of the previous credit limit amount, and a workflow database in which a plurality of application data are registered that associate at least the customer identification information, application officer identification information, and the previous credit limit base amount which is a credit limit base amount currently set for the customer, and the control unit controls the credit management database and the workflow database. S? and extracting a plurality of new application data including the extracted customer identification information, the financial statement data, the previous credit limit reference amount, and the previous credit limit amount corresponding to the extracted customer identification information; classifying the extracted plurality of new application data into individual application data which is the new application data to be applied for an individual application and collective application data which is the new application data to be applied for a collective application based on the customer status information; calculating a new credit limit reference amount which is the new credit limit reference amount for each of the individual application data and the collective application data based on an evaluation score of the financial indicators of the customer identified by the customer identification information; and notifying the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount to an application person identified by the corresponding application person identification information. Effect of the Invention

[0015] The present invention has the effect of enabling credit management operations to be managed with high accuracy. [Brief description of the drawings]

[0016] [Figure 1]FIG. 1 is a block diagram showing an example of the configuration of a credit management device. [Diagram 2] FIG. 2 is a diagram illustrating an example of the overall process flow by the credit management device. [Figure 3A] FIG. 3A is a schematic diagram showing an example of a data configuration of limit amount data. [Figure 3B] FIG. 3B is a schematic diagram showing an example of a data configuration of basic application data. [Figure 3C] FIG. 3C is a schematic diagram showing an example of the data configuration of application evaluation point data. [Figure 3D] FIG. 3D is a schematic diagram showing an example of a data configuration of detailed application data. [Figure 3E] FIG. 3E is a schematic diagram showing an example of a data configuration of company data. [Figure 3F] FIG. 3F is a schematic diagram showing an example of the data configuration of the financial statement data. [Figure 3G] FIG. 3G is a schematic diagram showing an example of a data configuration of the evaluation point master. [Figure 3H] FIG. 3H is a schematic diagram showing an example of a data configuration of evaluation point data. [Figure 3I] FIG. 3I is a schematic diagram showing an example of the data configuration of the credit limit master. [Figure 3J] FIG. 3J is a schematic diagram showing an example of a data configuration of basic application data. [Figure 3K] FIG. 3K is a schematic diagram showing an example of the data configuration of application evaluation point data. [Figure 3L] FIG. 3L is a schematic diagram showing an example of the data configuration of detailed application data. [Figure 4A] FIG. 4A is a schematic diagram showing an example of a periodic application screen. [Figure 4B] FIG. 4B is a schematic diagram showing an example of the individual application screen. [Figure 5A] FIG. 5A is a schematic diagram showing an example of a data configuration of basic application data. [Figure 5B] FIG. 5B is a schematic diagram showing an example of the data configuration of the application evaluation point data. [Figure 5C] FIG. 5C is a schematic diagram showing an example of a data configuration of detailed application data. [Figure 6A] FIG. 6A is a schematic diagram of an example of an approval screen for an individual application. [Figure 6B] FIG. 6B is a schematic diagram showing an example of a data configuration of basic application data. [Figure 6C] FIG. 6C is a schematic diagram showing an example of the data configuration of application evaluation point data. [Figure 6D] FIG. 6D is a schematic diagram showing an example of the data configuration of the credit limit master. [Figure 7A] FIG. 7A is a schematic diagram showing an example of a data configuration of basic application data. [Figure 7B] FIG. 7B is a schematic diagram showing an example of a data configuration of detailed application data. [Figure 8A] FIG. 8A is a schematic diagram showing an example of the periodic application screen. [Figure 8B] FIG. 8B is a schematic diagram showing an example of the collective application screen. [Figure 9A] FIG. 9A is a schematic diagram showing an example of a data configuration of basic application data. [Figure 9B] FIG. 9B is a schematic diagram showing an example of a data configuration of detailed application data. [Figure 10A] FIG. 10A is a schematic diagram showing an example of a collective application approval screen 64. [Figure 10B] FIG. 10B is a schematic diagram showing an example of the data configuration of the basic application data. [Figure 10C] FIG. 10C is a schematic diagram showing an example of the data configuration of application evaluation point data. [Figure 10D] FIG. 10D is a schematic diagram showing an example of the data configuration of the credit limit master. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of a credit management device, a credit management method, and a credit management program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the preferred embodiments.

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

[0019] The credit management device 100 of this embodiment is a device that manages credit for each business partner. In this embodiment, a case where the business partner is a company will be described as an example.

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

[0021] The credit 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 credit management device 100 are communicatively connected via any communication path.

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

[0023] 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 cooperates with a mouse to realize a pointing device function. 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.

[0024] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106.

[0025] The storage unit 106 stores, for example, a credit management DB (database) 106a and a WFDB (workflow database) 106b. These masters and data are databases and tables in which various information is registered.

[0026] The credit management DB 106a is a database for managing credit for each business partner. The credit management DB 106a is a database that associates at least the business partner identification information, business partner status information, financial statement data representing financial indicators, the previous credit limit which is the currently set credit limit, and the application deadline of the previous credit limit, for example.

[0027] In this embodiment, the credit management DB 106a stores a plurality of items of data and master data in association with each other. In detail, in this embodiment, the credit management DB 106a stores a plurality of items of data and master data in association with each other using the customer identification information as a key.

[0028] Specifically, the credit management DB 106a includes credit limit data 106a1, company data 106a2, financial statement data 106a3, evaluation point master 106a4, evaluation point data 106a5, and credit limit master 106a6. These data and masters are databases or tables in which various information is registered. The data formats of these data and masters are not limited to databases or tables. The data structures of these data and masters will be described in detail later.

[0029] The WFDB 106b is a database for managing the workflow in the credit management operation. The WFDB 106b is a database in which a plurality of application data items are registered, each of which corresponds to at least the client identification information, the application manager identification information, and the previous credit limit reference amount, which is the credit limit reference amount currently set for the client.

[0030] In this embodiment, the WFDB 106b separates the data and registers these items in association with each other. In detail, in this embodiment, the WFDB 106b registers application data in which these items are associated with each other using client identification information, case number, and the like as keys.

[0031] Specifically, the WFDB 106b includes basic application data 106b1, application evaluation point data 106b2, and detailed application data 106b3. These data are databases or tables in which various information is registered. The data formats of these data and masters are not limited to databases or tables. The data structures of these data and masters will be described in detail later.

[0032] The control unit 102 is a CPU or the like that comprehensively controls the credit management device 100. The control unit 102 has an internal memory for storing control programs such as an OS (operating system), programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0033] In this embodiment, the control unit 102 includes an extraction unit 102a, a classification unit 102b, a credit limit reference amount calculation unit 102c, a notification unit 102d, and a registration unit 102e.

[0034] The extraction unit 102a extracts, from the credit management DB 106a, customer identification information that has a deadline for application that is a predetermined period from the present time. The predetermined period is, for example, two months, but is not limited to this.

[0035] Then, the extraction unit 102a extracts a plurality of new application data including the extracted customer identification information, financial statement data 106a3 corresponding to the extracted customer identification information, the previous credit limit reference amount which is the credit limit reference amount currently set for the customer, and the previous credit limit amount which is the credit limit reference amount currently set for the customer. The extraction unit 102a extracts the new application data by extracting information corresponding to the customer identification information with an application deadline of a predetermined period from the present time from the credit management DB 106a and the WFDB 106b.

[0036] The classification unit 102b classifies the extracted multiple new application data into individual application data, which is new application data for individual applications, and collective application data, which is new application data for collective applications, based on the customer status information.

[0037] In detail, the classification unit 102b classifies new application data among the multiple new application data extracted by the extraction unit 102a, where the business partner status information indicates that the business partner is a suspect customer, into individual application data, and classifies new application data where the business partner status information indicates that the business partner is not a suspect customer into bulk application data.

[0038] The credit limit standard amount calculation unit 102c calculates a new credit limit standard amount, which is a new credit limit standard amount for the next application deadline, for each of the classified individual application data and bulk application data, based on the evaluation score of the financial indicators of the customer identified by the customer identification information.

[0039] The notification unit 102d notifies the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount, to the applicant identified by the corresponding applicant identification information.

[0040] The registration unit 102e registers the individual application data and the collective application data, including the credit limit application amount input by the applicant, in the WFDB 106b.

[0041] Then, when the application amount is input by the applicant, the notification unit 102d further notifies the corresponding approver of at least one of the individual application data and the collective application data, which further includes the input credit limit application amount.

[0042] The registration unit 102e assigns a flag indicating that the individual application data and the collective application data approved by the approver to the individual application data and the collective application data, and registers the data in the WFDB 106b.

[0043] [2. Specific Examples] A specific example of the processing of the credit management device 100 in this embodiment will be described with reference to FIGS. 2 to 10D.

[0044] In this embodiment, the case where the business partner is a company will be described as an example. Also, the case where a parent company code, which is the identification information of a company, is used as the business partner identification information will be described as an example. Also, in this embodiment, the structures of the database, master, and data used in this embodiment will be described in a simplified manner. The actual structures of these databases, master, and data are more complicated, but the parts that are not directly related to the present invention will be shown in a simplified manner.

[0045] Fig. 2 is a diagram showing a flow for explaining an example of the overall processing flow by the credit management device 100 in this embodiment. For example, the control unit 102 of the credit management device 100 executes the flow shown in Fig. 2 at predetermined timings. In this embodiment, the control unit 102 executes the flow shown in Fig. 2 every 24 hours, for example, at night outside business hours, as an example.

[0046] The extraction unit 102a checks the application deadline in the credit management DB 106a and the WFDB 106b, and extracts the parent company code for which the application deadline is a predetermined period from the present (step S100). For example, the control unit 102 extracts the parent company code for which the application deadline is two months from the present. In this flow, it is assumed that the present date is June 31, 2021.

[0047] 3A is a schematic diagram showing an example of the data configuration of credit limit data 106a1 included in credit management DB 106a. Credit limit data 106a1 is a database that associates parent company codes, company names, credit limits, and application deadlines. In credit limit data 106a1, the previous credit limit base amount, which is the currently set credit limit base amount, and the application deadline of the credit limit base amount are registered in association with each other for each parent company code, which is customer identification information.

[0048] In this case, the extraction unit 102a extracts parent company codes with an application deadline of August 31, 2021, which is two months from the present, from the limit amount data 106a1. The extraction unit 102a may also extract parent company codes with an application deadline of two months from the present from the WFDB 106b, the specific data configuration of which will be described later.

[0049] Returning to Fig. 2, the description will continue. Next, the extraction unit 102a extracts new application data including the parent company code extracted in step S100 (step S102).

[0050] For example, the extraction unit 102a generates new application data for each parent company code by extracting the extracted parent company code and the financial statement data 106a3, previous credit limit base amount, and previous credit limit amount corresponding to the extracted parent company code from the credit management DB 106a and the WFDB 106b.

[0051] 3B to 3D are schematic diagrams showing an example of the data configuration of basic application data 106b1, application evaluation point data 106b2, and detailed application data 106b3 contained in the WFDB 106b.

[0052] 3B is a schematic diagram showing an example of the data configuration of the basic application data 106b1. The basic application data 106b1 is a database that associates a case number, a parent company code, a department 1, a person in charge 1, a department 2, a person in charge 2, and a status. The case number is an identification number for identifying application data, and is assigned to each piece of application data. Person in charge 1 and person in charge 2 are application person identification information that identifies the application person in charge of the business partner company identified by the corresponding parent company code. The status refers to the status in the approval flow of the application data identified by the corresponding case number. The status is, for example, "approved", "applied for", "not applied for", etc.

[0053] Fig. 3C is a schematic diagram showing an example of the data configuration of the application evaluation point data 106b2. The application evaluation point data 106b2 is a database that registers the case number, the evaluation points of each financial indicator of the business partner of the application target by the application data identified by the case number, and the comparison case number. Fig. 3C shows the names of each of the items of the financial indicators corresponding to the case number, such as sales year-on-year ratio, interest-bearing debt to monthly sales ratio, equity ratio, current ratio, quick ratio, and fixed ratio, as examples.

[0054] FIG. 3D is a schematic diagram showing an example of the data configuration of the application details data 106b3. The application details data 106b3 is a database that associates a case number, an evaluation point, a credit limit reference amount, an application amount 1, a previous amount 1, an application deadline 1, an application amount 2, a previous amount 2, and an application deadline 2. The evaluation point of the application details data 106b3 is registered as a total value, which is a total evaluation point of the evaluation points of the corresponding case numbers in the application evaluation point data 106b2. FIG. 3D also shows a state in which the previous credit limit reference amount, which is the credit limit reference amount currently set for the business partner, and the application deadline of the previous credit limit reference amount are registered as the credit limit reference amount and application deadline corresponding to the case number. The application amount means the application amount of the credit limit. The previous amount is the credit limit amount set last time. The numbers 1 and 2 written to the right of the application amount, previous amount, and application deadline correspond to the numbers 1 and 2 written to the right of the person in charge shown in the basic application data 106b1 in FIG. 3B.

[0055] 3B to 3D, the WFDB 106b is composed of, for example, basic application data 106b1, application evaluation point data 106b2, and detailed application data 106b3. In the WFDB 106b, for each application data identified by a case number, a parent company code, a person in charge which is application person identification information, a previous credit limit reference amount which is the credit limit reference amount currently set for a business partner, and the like are registered in association with each other.

[0056] As described above, the extraction unit 102a extracts parent company codes with an application deadline two months from the present from the WFDB 106b or the credit management DB 106a. The following description assumes that the credit management DB 106a and WFDB 106b in the state shown in Figs. 3A to 3D are used. In this case, the extraction unit 102a extracts parent company codes "5678901234", "6789012345", "7890123456", and "8901234567" with an application deadline of August 31, 2021, which is two months from the present. The extraction unit 102a then extracts the financial statement data 106a3, previous credit limit reference amount, and previous credit limit amount corresponding to the extracted parent company codes, the newly assigned case number, and the extracted parent company codes from the credit management DB 106a and WFDB 106b, thereby generating new application data for each parent company code. As a result, in the WFDB 106b, a row of new application data to which a new case number has been assigned is registered in the application basic data 106b1, application evaluation point data 106b2, and application detailed data 106b3. Details of the new application data will be described later.

[0057] Returning to Fig. 2, the explanation will be continued. Next, the classification unit 102b classifies the new application data extracted in step S102 into individual application data which is new application data for individual applications and collective application data which is new application data for collective applications, based on the business partner status information of the company identified by the parent company code (step S104).

[0058] In this embodiment, the classification unit 102b executes the classification process based on the customer status information registered in the company data 106a2. The customer status information is information that represents the current status of the customer. The customer status information is, for example, at least one of the listed classification, the currently set credit limit standard amount, and the business caution status.

[0059] The classification unit 102b classifies new application data, among the extracted multiple new application data, whose business partner status information indicates that the customer is a suspicious customer, into individual application data. In addition, the classification unit 102b classifies new application data, among the extracted multiple new application data, whose business partner status information indicates that the customer is not a suspicious customer, into collective application data. A suspicious customer means that the customer is low in security. A non-suspicious customer means that the customer is highly secure.

[0060] 3E is a schematic diagram showing an example of the data configuration of company data 106a2. Company data 106a2 is a database in which parent company codes, company names, and business partner status information are associated with each other. Company data 106a2 is, for example, at least one of company data 106a21, company data 106a22, and company data 106a23. Classification unit 102b executes classification processing using at least one of company data 106a21, company data 106a22, and company data 106a23.

[0061] Company data 106a21 is a database that associates parent company codes, company names, and listing classifications, which are business partner status information.

[0062] When using listing classification as customer status information, the classification unit 102b classifies new application data including a parent company code corresponding to the listing classification "unlisted" in the company data 106a21 into individual application data. On the other hand, the classification unit 102b classifies new application data including a parent company code corresponding to the listing classification "listed" in the company data 106a21 into collective application data.

[0063] Company data 106a22 is a database that associates parent company codes, company names, and currently set credit limit reference amounts, which are supplier status information.

[0064] When the credit limit reference amount is used as the customer status information, the classification unit 102b classifies new application data including a parent company code corresponding to a credit limit reference amount equal to or greater than the threshold representing a large credit borrower in the company data 106a22 into individual application data. On the other hand, the classification unit 102b classifies new application data including a parent company code corresponding to a credit limit reference amount less than the threshold representing a large credit borrower, i.e., a small credit borrower, into collective application data.

[0065] The company data 106a23 is a database that associates parent company codes, company names, and currently set business situation caution flags, which are business partner situation information. The business situation caution flag is information that indicates whether the business situation of a company requires caution or does not require caution.

[0066] When using business caution status as business partner status information, the classification unit 102b classifies new application data including a parent company code corresponding to the business situation caution flag "needed" in the company data 106a23 into individual application data. On the other hand, the classification unit 102b classifies new application data including a parent company code corresponding to the business situation caution flag "not required" in the company data 106a23 into collective application data.

[0067] The classification unit 102b may perform classification processing using at least two or more of the listed category, the currently set credit limit reference amount, and the business caution status as customer status information. In this case, two or more of the company data 106a21, the company data 106a22, and the company data 106a23 may be combined and used for classification processing. The classification unit 102b may also perform classification processing using other customer status information.

[0068] Continuing the description, returning to Fig. 2, next, the control unit 102 executes the processes of steps S108 to S128 for the individual application data (step S106: Yes, step S116: Yes).

[0069] The credit limit standard amount calculation unit 102c calculates the evaluation score of the business partner company identified by the parent company code included in each individual application data (step S106: Yes) (step S108). The evaluation score is the evaluation score of the financial indicators of the business partner company.

[0070] Then, the credit limit base amount calculation unit 102c calculates a new credit limit base amount, which is a new credit limit base amount for the next application deadline, based on the calculated evaluation points (step S110).

[0071] The credit limit standard amount calculation unit 102c uses the credit management DB 106a to calculate the evaluation points and new credit limit standard amount of the supplier identified by the parent company code included in the individual application data.

[0072] 3F to 3H are schematic diagrams showing examples of the data configurations of financial statement data 106a3, evaluation point master 106a4, evaluation point data 106a5, and credit limit master 106a6 included in credit management DB 106a.

[0073] FIG. 3F is a schematic diagram showing an example of the data configuration of the financial statement data 106a3. The financial statement data 106a3 represents data on financial indicators of a business partner company. In this embodiment, the financial statement data 106a3 represents financial indicator data from the most recent settlement closest to the current time. For example, the financial statement data 106a3 is a database that associates parent company codes, accounting periods, account names, and amounts. FIG. 3F shows an example of data on financial indicators from the most recent settlement of parent company code "5678901234".

[0074] Fig. 3G is a schematic diagram showing an example of the data configuration of the evaluation point master 106a4. The evaluation point master 106a4 is a database in which the name of a financial indicator, a threshold, and an evaluation point are associated with each other. Fig. 3G shows a range represented by an upper limit and a lower limit as a threshold for each financial indicator.

[0075] 3H is a schematic diagram showing an example of the data configuration of evaluation point data 106a5. Evaluation point data 106a5 is a database in which parent company codes, company names, and evaluation points are associated with each other.

[0076] The credit limit reference amount calculation unit 102c identifies, for each individual application data, the evaluation points corresponding to the financial indicators represented by the financial statement data 106a3 of the company identified by the parent company code, which is the supplier identification information, from the evaluation point master 106a4.

[0077] Specifically, for example, for a company with parent company code "5678901234", the credit limit base amount calculation unit 102c uses the evaluation point master 106a4 to identify the evaluation point for each item of the financial indicator included in the financial statement data 106a3 shown in FIG. 3F. In detail, the credit limit base amount calculation unit 102c identifies the evaluation point "10" from the evaluation point master 106a4 as the evaluation point corresponding to the current ratio "101.2%". Similarly, the credit limit base amount calculation unit 102c identifies the evaluation point "10" from the evaluation point master 106a4 as the evaluation point corresponding to the quick ratio "120.2%". Similarly, the credit limit base amount calculation unit 102c identifies the evaluation point "10" from the evaluation point master 106a4 as the evaluation point corresponding to the fixed ratio "99.2%".

[0078] Then, the credit limit reference amount calculation unit 102c calculates the total value of the evaluation points identified for each of these financial indicator items as the overall evaluation point for the parent company code "5678901234" and registers it in the evaluation point data 106a5 (see FIG. 3H).

[0079] Then, the credit limit base amount calculation unit 102c calculates a new credit limit base amount, which is a new credit limit base amount for the next application deadline, using the calculated evaluation points and the credit limit master 106a6.

[0080] 3I is a schematic diagram showing an example of the data configuration of credit limit master 106a6. Credit limit master 106a6 is a database in which ratings, evaluation points, and credit limit base amounts are associated with each other.

[0081] The credit limit reference amount calculation unit 102c calculates the credit limit corresponding to the evaluation points calculated for each parent company code, that is, each individual application data, in the credit limit master 106a6 as a new credit limit reference amount.

[0082] Specifically, for example, the credit limit standard amount calculation unit 102c calculates "35,000,000" as the new credit limit standard amount for the parent company code "5678901234" with an evaluation score of "75". The credit limit standard amount calculation unit 102c also calculates "21,000,000" as the new credit limit standard amount for the parent company code "6789012345" with an evaluation score of "59". The credit limit standard amount calculation unit 102c also calculates "25,000,000" as the new credit limit standard amount for the parent company code "7890123456" with an evaluation score of "65". Similarly, the credit limit standard amount calculation unit 102c calculates "30,000,000" as the new credit limit standard amount for the parent company code "8901234567" with an evaluation score of "72".

[0083] Returning to Fig. 2, the description will continue. Then, the credit limit base amount calculation unit 102c registers the individual application data including the evaluation score calculated in step S108 and the new credit limit base amount calculated in step S110 in the WFDB 106b (step S112).

[0084] 3J to 3L are schematic diagrams showing an example of the WFDB 106b in which the individual application data 30 including the evaluation points and the new credit limit reference amount is registered.

[0085] Fig. 3J is a schematic diagram showing an example of the data configuration of basic application data 106b1 in which individual application data 30 is registered. Fig. 3K is a schematic diagram showing an example of the data configuration of application evaluation point data 106b2 in which individual application data 30 is registered. Fig. 3L is a schematic diagram showing an example of the data configuration of detailed application data 106b3 in which individual application data 30 is registered.

[0086] As shown in Figures 3J to 3L, individual application data 30 is registered for each case number in the basic application data 106b1, application evaluation point data 106b2, and application detail data 106b3, which correspond to the case number, parent company code, department 1, person in charge 1, department 2, person in charge 2, status, evaluation point corresponding to the subject name of the financial indicator, comparison case number, calculated evaluation point, and credit limit base amount which is the calculated new credit limit base amount.

[0087] At this point in time, the credit limit base amount calculation unit 102c registers the individual application data 30 with the status set to "not applied for."

[0088] Continuing the explanation by returning to Fig. 2, the notification unit 102d notifies the individual application data 30 to the application person identified by the corresponding application person identification information (step S114).

[0089] That is, when the control unit 102 creates new application data such as the individual application data 30 or the collective application data described later, it notifies the application person in charge represented by "Person in Charge 1" or "Person in Charge 2" included in the new application data. In detail, the notification unit 102d transmits a list of the created new application data such as the individual application data 30 or the collective application data described later to the address of the application person in charge via the network 300.

[0090] In this way, new application data for business partners who are companies with parent company codes with a deadline for application after a certain period of time is automatically created by the control unit 102, and classified into individual application data 30 and collective application data, and notified to the person in charge of application. This reduces the risk of missed processing in credit management operations.

[0091] FIG. 4A is a schematic diagram showing an example of a regular application screen 50 displayed on the monitor of the personal computer of "Yamada Taro," an applicant. The regular application screen 50 includes, for example, a list of new application data created by the control unit 102 of the credit management device 100. The applicant selects one piece of new application data for the application from the displayed list of new application data. Here, the explanation will be continued assuming a scene in which one piece of individual application data 30A has been selected.

[0092] Returning to Fig. 2, the description will continue. If the individual application data 30 is selected (step S116: Yes), the process proceeds to step S118.

[0093] In step S118, the notification unit 102d notifies the person in charge of application of the individual application screen of the individual application data 30 selected in step S116 (step S118).

[0094] In addition, the notification unit 102d may notify the application person identified by the corresponding application person identification information of the individual application screen 52 of the individual application data 30 which further includes information indicating the direction of change in the evaluation score relative to the previously identified evaluation score.

[0095] In detail, the notification unit 102d compares each of the financial indicator item names and total evaluation points calculated in step S108 with the corresponding financial indicator item names and total evaluation points currently set for the corresponding parent company code. If the evaluation point is higher than the currently set evaluation point, information indicating an up arrow is added to each evaluation point. If the evaluation point is the same, information indicating a sideways arrow is added, and if the evaluation point is lower, information indicating a down arrow is added. Note that the addition of information indicating the direction of change may be performed by the credit limit reference amount calculation unit 102c.

[0096] The notification unit 102d then notifies the individual application screen 52 of the individual application data 30, which includes information indicating these change directions, to the application person identified by the corresponding application person identification information.

[0097] Fig. 4B is a schematic diagram showing an example of an individual application screen 52. As shown in Fig. 4A, assume that individual application data 30A for a company name "EEEEE" with case number "101" is selected by "Yamada Taro", who is in charge of application. In this case, the notification unit 102d generates an individual application screen 52 including the selected individual application data 30A, and notifies the individual application screen 52 to the address of "Yamada Taro", who is in charge of application. Therefore, for example, the individual application screen 52 shown in Fig. 4B is displayed on the monitor of the personal computer of "Yamada Taro", who is in charge of application.

[0098] 4B, individual application screen 52 includes a parent company code which is the supplier identification information of selected individual application data 30A, financial indicator data included in financial statement data 106a3 which indicates the supplier's financial indicators, the previous credit limit reference amount, the previous credit limit amount, an evaluation score for the financial indicator, a new credit limit reference amount which is the new credit limit reference amount, and an arrow which is change information which indicates the direction of change in the evaluation score relative to the previous evaluation score. Individual application screen 52 also includes an input field 52A for credit limit application amount which is the credit limit to be applied for this time in individual application data 30A.

[0099] Therefore, the application officer can make a new credit application for a business partner that is a company with a parent company code for which the application deadline is a specified period of time by inputting the minimum items required for a credit application (e.g., credit limit amount) without having to manually input a large number of items required for a credit application.

[0100] The individual application screen 52 also includes financial statement data 106a3 indicating the financial indicators of the customer, the previous credit limit reference amount, the previous credit limit amount, data on the financial indicators, the evaluation score of the financial indicator, a new credit limit reference amount which is the new credit limit reference amount, an arrow which is change information indicating the direction of change in the evaluation score from the previous evaluation score, etc. Therefore, the person in charge of application can easily set the credit limit application amount by referring to this information.

[0101] The person in charge of application enters the credit limit application amount in the input field 52A and presses the apply button to make an application request for individual application data 30A including the credit limit application amount.

[0102] Returning to Fig. 2, the description will be continued. The registration unit 102e then receives the individual application data 30A including the credit limit application amount and the application request signal from the applicant (step S120). The registration unit 102e registers the credit limit application amount included in the received individual application data 30A in the corresponding individual application data 30A in the application details data 106b3.

[0103] 5A to 5C are schematic diagrams showing an example of the data configuration of the basic application data 106b1, the application evaluation point data 106b2, and the detailed application data 106b3 registered in the individual application data 30 including the credit limit application amount input by the application clerk. As shown in Figs. 5A to 5C, the individual application data 30A for case number "101" has the credit limit application amount "15,000,000" input by the application clerk "Yamada Taro", who is clerk 1, registered as application amount 2. Furthermore, upon receiving the application request, the registration unit 102e changes the status in the individual application data 30A to "application in progress".

[0104] Returning to Fig. 2, the explanation will be continued. The notification unit 102d notifies the corresponding approver of the approval screen for the individual application of the individual application data 30A for which the credit limit application amount has been registered and requested in step S122 (step S124). For example, the control unit 102 pre-stores approver identification information for each parent company code. The notification unit 102d then identifies the approver identification information corresponding to the parent company code included in the individual application data 30A for which the request has been made, and notifies the address of the approver identified by the identified approver identification information of the approval screen for the individual application of the individual application data 30 via the network 300 (step S124).

[0105] For this reason, for example, an individual application approval screen 54 shown in Fig. 6A is displayed on the monitor of the approver's personal computer. The notification unit 102d may display a list of multiple new application data (individual application data 30 and collective application data) applied for by the application staff on the monitor of the approver's personal computer. Then, when the approver selects one piece of new application data, individual application data 30, an individual application approval screen 54 for the selected individual application data 30 may be displayed on the monitor.

[0106] 6A, the approval screen 54 for an individual application includes a parent company code which is the supplier identification information of the individual application data 30A, financial indicator data included in the financial statement data 106a3 which indicates the supplier's financial indicators, the previous credit limit reference amount, the previous credit limit amount, the evaluation score of the financial indicator, a new credit limit reference amount which is the new credit limit reference amount, and an arrow which is change information which indicates the direction of change of the evaluation score from the previous evaluation score. The individual application screen 52 also includes the credit limit amount currently applied for in the individual application data 30A.

[0107] Therefore, the approver can check the items necessary to confirm a credit application for a business partner that is a company with a parent company code for which the application deadline is a specified period later, on a single approval screen 54, without having to separately check a large number of items required to confirm the credit application.

[0108] Furthermore, the individual application approval screen 54 includes financial indicator data included in the financial statement data 106a3 showing the financial indicators of the business partner, the previous credit limit reference amount, the previous credit limit amount, the financial indicator data, the evaluation score of the financial indicator, the new credit limit reference amount which is the new credit limit reference amount, an arrow which is change information showing the change direction of the evaluation score from the previous evaluation score, etc. Therefore, by referring to this information, the approver can easily determine whether or not to approve the credit limit application amount.

[0109] The approver approves the individual application data 30A by pressing the approval button.

[0110] Returning to Fig. 2, the description will be continued. Then, the registration unit 102e receives the individual application data 30A including the approval signal from the approver (step S126). The registration unit 102e changes the status included in the received individual application data 30A to "approved" (step S128). Then, this routine ends.

[0111] 6B and 6C are schematic diagrams showing an example of the data configuration of the basic application data 106b1, the application evaluation point data 106b2, and the credit limit master data 106a6 after the processing of step S128 is performed by the registration unit 102e.

[0112] The registration unit 102e sets the status of the individual application data 30A to "approved" (see FIG. 6B). Furthermore, when each of the individual application data 30 is approved by the above process, the registration unit 102e associates the approved credit limit application amount with the parent company code of the approved individual application data 30, registers the approved credit limit application amount as the credit limit, and associates the new application deadline in the credit limit master 106a6. Therefore, as shown in FIG. 6D, the credit limit master 106a6 is in a state where the company name, the newly set credit limit, and the application deadline of the credit limit are associated with the parent company code and registered.

[0113] 2 to continue the explanation. On the other hand, for the collective application data classified in step S104 (step S106: No, step S116: No), the control unit 102 executes the processes of steps S130 to S134, step S114, step S116, and steps S136 to S146.

[0114] For each of the collective application data (step S106: No), the credit limit standard amount calculation unit 102c calculates (step S130) the evaluation points of the business partner companies identified by the parent company codes included in the collective application data 32. The credit limit standard amount calculation unit 102c may calculate the evaluation points of the companies identified by the parent company codes included in the collective application data 32 in the same manner as the calculation process of the evaluation points for the individual application data 30.

[0115] Next, the credit limit standard amount calculation unit 102c calculates a new credit limit standard amount, which is a new credit limit standard amount for the next application deadline, based on the evaluation points calculated in step S130 (step S132). The credit limit standard amount calculation unit 102c uses the credit management DB 106a to calculate the evaluation points and new credit limit standard amount of the business partner identified by the parent company code included in the collective application data. The credit limit standard amount calculation unit 102c may calculate the new credit limit standard amount for the collective application data in the same manner as the calculation process of the new credit limit standard amount for the individual application data 30.

[0116] Then, the credit limit base amount calculation unit 102c registers the lump-sum application data including the evaluation points calculated in step S130 and the new credit limit base amount calculated in step S132 in the WFDB 106b (step S134).

[0117] 7A and 7B are schematic diagrams showing an example of the WFDB 106b in which the collective application data 32 including the evaluation points and the new credit limit reference amount is registered.

[0118] Fig. 7A is a schematic diagram showing an example of the data configuration of basic application data 106b1 in which collective application data 32 is registered. Fig. 7B is a schematic diagram showing an example of the data configuration of detailed application data 106b3 in which collective application data 32 is registered.

[0119] 7A and 7B, in the basic application data 106b1 and the detailed application data 106b3, the batch application data 32 that associates the case number, parent company code, department 1, person in charge 1, department 2, person in charge 2, status, calculated evaluation score, the calculated new credit limit reference amount which is the credit limit reference amount, etc. is registered for each case number. Although not shown, the batch application data 32 that includes the evaluation score corresponding to the subject name of the financial indicator and the comparison case number is also registered for the application time evaluation score data 106b2 in the same manner for each case number.

[0120] At this point, the credit limit base amount calculation unit 102c registers the batch application data 32 with the status set to "not applied for."

[0121] Returning to Fig. 2, the description will continue. The notification unit 102d notifies the application person identified by the corresponding application person identification information of the batch application data 32 (step S114).

[0122] That is, when the control unit 102 creates new application data such as the individual application data 30 or the collective application data 32, it notifies the application person represented by "Person in Charge 1" or "Person in Charge 2" included in the new application data. In detail, the notification unit 102d transmits a list of the created new application data such as the individual application data 30 or the collective application data 32 to the address of the application person via the network 300.

[0123] In this way, new application data for companies with parent company codes whose application deadline is a predetermined time later is automatically created by the control unit 102, and is classified into individual application data 30 and collective application data 32 and notified to the person in charge of application. This reduces the risk of missed processing in credit management operations.

[0124] 8A is a schematic diagram showing an example of a regular application screen 50 displayed on the monitor of the personal computer of "Yamada Taro", an applicant. The regular application screen 50 includes, for example, a list of new application data created by the control unit 102 of the credit management device 100. The applicant selects one piece of new application data for the application target from the displayed list of new application data. Here, the explanation will be continued assuming a scene in which the collective application data 32 has been selected.

[0125] Returning to Fig. 2, the explanation will continue. If collective application data 32 is selected (step S116: No), the process proceeds to step S136.

[0126] In step S136, the notification unit 102d notifies the person in charge of applications of the collective application screen of the collective application data 32 selected in step S116 (step S136).

[0127] Fig. 8B is a schematic diagram showing an example of a collective application screen 62. As shown in Fig. 8A, a scene is assumed in which collective application data 32 is selected by "Yamada Taro", who is the person in charge of application. In this case, the notification unit 102d generates a collective application screen 62 including the selected collective application data 32, and notifies the collective application screen 62 to the address of "Yamada Taro", who is the person in charge of application. Therefore, for example, the collective application screen 62 shown in Fig. 8B is displayed on the monitor of the personal computer of "Yamada Taro", who is the person in charge of application.

[0128] As shown in Fig. 8B, the collective application screen 62 displays a list of collective application data 32 corresponding to the applicant "Yamada Taro". The collective application screen 62 has a simpler display than the individual application screen 52, and is configured to enable a list of new application data classified into the collective application data 32 to be viewed all at once. In addition, the collective application screen 62 includes an input field 62A for the credit limit application amount, which is the credit limit amount to be applied for this time, for each collective application data 32.

[0129] Therefore, application personnel can make new credit applications in one go for business partners that are parent company codes with an application deadline after a specified period of time by inputting the minimum items required for a credit application (e.g., credit limit amount) without having to manually input a large number of items required for a credit application.

[0130] In addition, the collective application screen 62 shows a list of multiple new application data for which the application person is responsible. In addition, the collective application screen 62 includes some of the items of financial indicators included in the financial statement data 106a3 that show the financial indicators of the business partners, evaluation points, etc. Therefore, the application person can easily set the credit limit application amount for multiple new application data classified into the collective application data 32 by referring to this information.

[0131] The person in charge of application enters the credit limit application amount in the input field 62A and presses the apply button to make an application request for collective application data 32 including the credit limit application amount.

[0132] Returning to Fig. 2, the description will be continued. The registration unit 102e then receives the lump-sum application data 32 including the credit limit application amount and the application request signal from the applicant (step S138). The registration unit 102e registers the credit limit application amount included in the received lump-sum application data 32 in the corresponding lump-sum application data 32 of the application detail data 106b3 (step S140).

[0133] 9A-9B are schematic diagrams showing an example of the data configuration of the registered basic application data 106b1 and detailed application data 106b3 of the batch application data 32 including the credit limit application amount input by the application staff. As shown in FIG. 9A and FIG. 9B, the batch application data 32 of the case number "111" has the credit limit application amount "9,000,000" input by the application staff "Yamada Taro" who is the staff 1 registered as application amount 1. In addition, by the same process, the credit limit application amount "11,000,000" input by the main application staff "Yamada Taro" who is the staff 1 registered as application amount 2. In addition, when the registration unit 102e accepts the application request, it changes the status in the batch application data 32 to "application in progress".

[0134] Returning to Fig. 2, the explanation will be continued. The notification unit 102d notifies the corresponding approver of the approval screen for the batch application of the batch application data 32 for which the credit limit application amount has been registered and requested in step S138 (step S142). For example, the control unit 102 pre-stores approver identification information for each parent company code. The notification unit 102d then identifies the approver identification information corresponding to the parent company code included in the batch application data for which the request has been made, and notifies the address of the approver identified by the identified approver identification information of the batch application approval screen for the batch application data 32 via the network 300 (step S142).

[0135] For this reason, for example, a collective application approval screen 64 shown in Fig. 10A is displayed on the monitor of the approver's personal computer. The notification unit 102d may display a list of multiple new application data (individual application data 30 and collective application data 32) applied for by the application staff on the monitor of the approver's personal computer. Then, when the approver selects the collective application data 32, which is one piece of new application data, the collective application approval screen 64 for the selected collective application data 32 may be displayed on the monitor.

[0136] 10A, the batch application approval screen 64 displays a list of batch application data 32. The batch application approval screen 64 has a simpler display than the individual application approval screen 54, and is configured to allow a list of new application data classified into the batch application data 32 to be viewed all at once.

[0137] Therefore, the approver can check the items required to confirm a credit application for a business partner that is a company with a parent company code for which the application deadline is a specified period later, on a single bulk application approval screen 64, without having to separately check a large number of items required to confirm the credit application.

[0138] In addition, the batch application approval screen 64 displays a list of the batch application data 32. Therefore, the approver can approve or disapprove the list of new application data classified as the batch application data 32 all at once.

[0139] For example, the approver approves the collective application data 32 by pressing an approval button.

[0140] Returning to Fig. 2, the description will be continued. Then, the registration unit 102e receives the collective application data 32 including the approval signal from the approver (step S144). The registration unit 102e changes the status included in the received collective application data 32 to "approved" (step S146). Then, this routine ends.

[0141] 10B to 10D are schematic diagrams showing an example of the data configuration of the basic application data 106b1, the application evaluation point data 106b2, and the credit limit master data 106a6 after the processing of step S146 has been performed by the registration unit 102e.

[0142] The registration unit 102e sets the status of the approved collective application data 32 to "approved" (see FIG. 10B). Furthermore, when each of the collective application data 32 is approved by the above process, the registration unit 102e registers the approved credit limit application amount as the credit limit in association with the parent company code of the approved collective application data 32, and registers the new application deadline in association with the parent company code in the credit limit master 106a6. Therefore, as shown in FIG. 10D, the credit limit master 106a6 is in a state where the company name, the newly set credit limit, and the application deadline of the credit limit are registered in association with the parent company code.

[0143] As described above, the credit management device 100 of this embodiment includes the control unit 102 and the storage unit 106. The storage unit 106 stores the credit management DB 106a and the WFDB 106b. The credit management DB 106a is a database that associates at least the supplier identification information (parent company code) of the supplier, supplier status information, financial statement data 106a3 that indicates financial indicators, the previous credit limit that is the currently set credit limit, and the application deadline of the previous credit limit. The WFDB 106b is a database that registers a plurality of application data that associates at least the supplier identification information (parent company code), application person identification information, and the previous credit limit reference amount that is the currently set credit limit reference amount for the supplier.

[0144] The control unit 102 includes an extraction unit 102a, a classification unit 102b, a credit limit reference amount calculation unit 102c, and a notification unit 102d. The extraction unit 102a extracts from the credit management DB 106a customer identification information (parent company code) with a deadline for application a predetermined period from the present time, and extracts a plurality of new application data including the extracted customer identification information (parent company code), financial statement data 106a3 corresponding to the extracted customer identification information, the previous credit limit reference amount, and the previous credit limit amount. The classification unit 102b classifies the extracted plurality of new application data into individual application data 30, which is new application data for individual applications, and collective application data 32, which is new application data for collective applications, based on customer status information. The credit limit standard amount calculation unit 102c calculates a new credit limit standard amount, which is a new credit limit standard amount for the next application deadline, based on the evaluation score of the customer identified by the customer identification information (company code) for each of the individual application data 30 and the collective application data 32. The notification unit 102d notifies the application person identified by the corresponding application person identification information of the individual application data 30 including the evaluation score of the financial indicators and the new credit limit standard amount, and the collective application data 32 including the evaluation score and the credit limit standard amount.

[0145] In this way, the credit management device 100 of this embodiment automatically extracts new application data for the currently set application deadline a predetermined period before the deadline, and automatically classifies the data into individual application data 30 and collective application data 32. Then, the credit management device 100 calculates a new credit limit base amount, which is a new credit limit base amount for the next application deadline, based on the evaluation score of the supplier identified by the supplier identification information (company code), and notifies the individual application data 30 and collective application data 32, which include the evaluation score and the new credit limit base amount, to the person in charge of application.

[0146] Therefore, the credit management device 100 of this embodiment can prevent applicants and approvers from missing processing credit management tasks for business partners that are companies with parent company codes for which the application deadline is after a predetermined period of time.

[0147] Therefore, the credit management device 100 of this embodiment can manage the credit management work with high accuracy.

[0148] In addition, the credit management device 100 of this embodiment automatically extracts new application data for the currently set application deadline a predetermined period before the application deadline, and notifies the application person of the individual application data 30 and bulk application data 32 into which the new application data is classified.

[0149] Therefore, in addition to the above-mentioned effects, the credit management device 100 of this embodiment can visualize the credit status of business partners and improve the work efficiency of applicants and approvers.

[0150] Furthermore, the credit management device 100 of this embodiment automatically extracts new application data for the application deadline a predetermined period before the currently set application deadline, and automatically classifies the data into individual application data 30 and collective application data 32 based on the supplier status information. Then, the individual application data 30 and the collective application data 32 are notified to the person in charge of application.

[0151] Therefore, the application staff can process new application data of caution-required customers such as large clients and caution-required customers as individual application data 30, and process new application data of caution-required customers such as good clients and small clients as bulk application data 32. Therefore, the application staff can focus on reviewing the individual application data 30, and reduce the burden on the bulk application data 32 by applying for them in bulk.

[0152] Furthermore, the credit management device 100 can manage the new application data by classifying the new application data into individual application data 30 and collective application data 32. Therefore, in addition to the above effects, the credit management device 100 of this embodiment can reduce the burden on the user and prevent opportunity loss in credit operations while maintaining the accuracy of credit management.

[0153] Furthermore, the credit management device 100 notifies the application clerk of the individual application screen 52. By visually checking the individual application screen 52, the application clerk can make a new credit application for a business partner that is a company with a parent company code with an application deadline after a predetermined period of time by inputting the minimum items required for a credit application (e.g., credit limit amount) without manually inputting a large number of items required for a credit application. Therefore, the credit management device 100 of this embodiment can improve business efficiency.

[0154] Furthermore, the credit management device 100 notifies the approver of the individual application approval screen 54. By visually checking the individual application approval screen 54, the approver can check the items required to confirm the credit application for a business partner that is a company with a parent company code with an application deadline after a predetermined period of time, on one approval screen 54, without having to separately check a large number of items required to confirm the credit application. Therefore, the credit management device 100 of this embodiment can improve business efficiency.

[0155] Furthermore, the credit management device 100 notifies the person in charge of applications of the collective application screen 62. The collective application screen 62 displays a list of the collective application data 32 corresponding to the person in charge of applications.

[0156] Therefore, by visually checking the collective application screen 62, the person in charge of application can make a new credit application for a business partner that is a company with a parent company code with an application deadline after a predetermined period of time, by inputting the minimum items required for a credit application (for example, the credit limit amount) without manually inputting a large number of items required for a credit application. Therefore, the credit management device 100 of this embodiment can improve business efficiency.

[0157] Furthermore, the credit management device 100 notifies the approver of the batch application approval screen 64. Therefore, the approver can easily check the items required to confirm the credit application by visually checking the batch application approval screen 64. Therefore, the credit management device 100 of this embodiment can improve business efficiency.

[0158] [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 goals 8 and 9 of the SDGs.

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

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

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

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

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

[0164] Moreover, with regard to the credit management device 100, the components shown in the figures are merely conceptual functional elements, and the device does not necessarily have to be physically configured as shown in the figures.

[0165] For example, the processing functions of the credit management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the credit management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0166] In addition, this computer program may be stored in an application program server connected to the credit management device 100 via any network, and it is also possible to download all or part of it as necessary.

[0167] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "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.

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

[0169] The various databases etc. stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

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

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

[0172] 100 Credit management device 102 Control section 106 Storage section 102a Extraction part 102b Classification section 102c Credit limit standard amount calculation department 102d Notification Department 102e Registration Department

Claims

1. A credit management device that includes a control unit and a storage unit and manages credit, The storage unit is a credit management database that associates at least the following: customer identification information of a customer; customer status information; financial statement data indicating financial indicators; a previous credit limit that is a currently set credit limit; and an application deadline of the previous credit limit; a workflow database in which a plurality of application data items are registered, the application data items being associated with at least the customer identification information, the application person identification information, and the previous credit limit reference amount, which is the credit limit reference amount currently set for the customer; Remember, The control unit is an extraction unit that extracts, from the credit management database and the workflow database, the customer identification information for which the application deadline is a predetermined period from the present time, and extracts a plurality of new application data including the extracted customer identification information, the financial statement data corresponding to the extracted customer identification information, the previous credit limit base amount, and the previous credit limit amount; a classification unit that classifies the extracted multiple new application data into individual application data that is the new application data to be applied for individually and collective application data that is the new application data to be applied for collectively, based on the customer status information; a credit limit standard amount calculation unit that calculates a new credit limit standard amount, which is a new credit limit standard amount, based on the evaluation score of the financial indicators of the customer identified by the customer identification information for each of the individual application data and the collective application data; a notification unit that notifies the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount to an application person identified by the corresponding application person identification information; A credit management device comprising:

2. The classification unit is Among the extracted multiple pieces of new application data, The new application data, which indicates that the business partner status information is a watchdog business partner, is classified into individual application data; classifying the new application data, which indicates that the business partner status information is a non-suspect business partner, into the batch application data; The credit management device according to claim 1.

3. The storage unit is an evaluation point master in which the thresholds of the financial indicators and the evaluation points are associated with each other; a credit limit master in which the evaluation points and the credit limit reference amount are associated with each other; Remember, The credit limit reference amount calculation unit For each of the individual application data and the collective application data, the evaluation point corresponding to the financial indicator represented by the financial statement data of the business partner identified by the business partner identification information is identified from the evaluation point master; Calculating the credit limit standard amount corresponding to the specified evaluation point in the credit limit master as the new credit limit standard amount; 3. The credit management device according to claim 1 or 2.

4. The notification unit is notifying the application person in charge identified by the corresponding application person identification information of an individual application screen of the individual application data, which further includes information indicating a direction of change of the evaluation point from the previously specified evaluation point; The credit management device according to any one of claims 1 to 3.

5. The notification unit is notifying the application person identified by the corresponding application person identification information of a collective application screen including a list of the collective application data; The credit management device according to any one of claims 1 to 4.

6. The notification unit is further notifying a corresponding approver of at least one of the individual application data and the collective application data, further including a credit limit application amount input by the applicant based on at least one of the individual application data and the collective application data; The credit management device according to any one of claims 1 to 5.

7. The control unit is a registration unit that registers the individual application data and the collective application data, including the credit limit application amount input by the person in charge of application, in a workflow database; The credit management device according to claim 6, further comprising:

8. A credit management method executed by an information processing device that manages credit and that includes a control unit and a storage unit, The storage unit includes: a credit management database that associates at least the following: customer identification information of a customer; customer status information; financial statement data indicating financial indicators; a previous credit limit that is a currently set credit limit; and an application deadline of the previous credit limit; a workflow database in which a plurality of application data items are registered, the application data items being associated with at least the customer identification information, the application person identification information, and the previous credit limit reference amount, which is the credit limit reference amount currently set for the customer; is stored, Executed by the control unit, extracting, from the credit management database and the workflow database, the customer identification information for which the application deadline is a predetermined period from the present time, and extracting a plurality of new application data including the extracted customer identification information, the financial statement data corresponding to the extracted customer identification information, the previous credit limit base amount, and the previous credit limit amount; A step of classifying the extracted multiple new application data into individual application data which is the new application data to be applied for individually and collective application data which is the new application data to be applied for collectively based on the customer status information; calculating a new credit limit standard amount, which is a new credit limit standard amount, for each of the individual application data and the collective application data, based on the evaluation score of the financial indicators of the customer identified by the customer identification information; notifying the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount to an applicant person identified by the corresponding applicant person identification information; A credit management method comprising:

9. A credit management program executed by an information processing device that manages credit, the information processing device comprising a control unit and a storage unit, The storage unit includes: a credit management database that associates at least the following: customer identification information of a customer; customer status information; financial statement data indicating financial indicators; a previous credit limit that is a currently set credit limit; and an application deadline of the previous credit limit; a workflow database in which a plurality of application data items are registered, the application data items being associated with at least the customer identification information, the application person identification information, and the previous credit limit reference amount, which is the credit limit reference amount currently set for the customer; is stored, In the control unit, extracting, from the credit management database and the workflow database, the customer identification information for which the application deadline is a predetermined period from the present time, and extracting a plurality of new application data including the extracted customer identification information, the financial statement data corresponding to the extracted customer identification information, the previous credit limit base amount, and the previous credit limit amount; A step of classifying the extracted multiple new application data into individual application data which is the new application data to be applied for individually and collective application data which is the new application data to be applied for collectively based on the customer status information; calculating a new credit limit standard amount, which is a new credit limit standard amount, for each of the individual application data and the collective application data, based on the evaluation score of the financial indicators of the customer identified by the customer identification information; notifying the individual application data including the evaluation score and the new credit limit reference amount, and the collective application data including the evaluation score and the credit limit reference amount to an applicant person identified by the corresponding applicant person identification information; A credit management program to implement the above.

Images