JP7651386B2 - CREDIT MANAGEMENT DEVICE, CREDIT MANAGEMENT METHOD, AND CREDIT MANAGEMENT PROGRAM - Google Patents

Description

The present invention relates to a credit management device, a credit management method, and a credit management program.

Systems that perform credit management are known. For example, a user visually checks and extracts data on business partners whose credit limit application deadlines are approaching from all business partner data registered in a core system, and applies for the credit limit for the next application deadline.

JP 2011-198183 A

However, with conventional technology, the application for the next credit limit for the application deadline was made using customer data extracted visually by the user, which could result in missed processing of credit management tasks. In other words, with conventional technology, it was difficult to manage credit management tasks with a high degree of accuracy.

The present invention has been made in consideration of the above problems, and aims to provide a credit management device, a credit management method, and a credit management program that can manage credit management operations with high accuracy.

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 memory unit and manages credit, wherein the memory unit stores a credit management database that associates at least the 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 for 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 extracts the customer identification information with the application deadline being a predetermined period from the current time from the credit management database and the workflow database , and stores the extracted customer identification information and a previous credit limit corresponding to the extracted customer identification information. The system includes an extraction unit that extracts a plurality of new application data including financial statement data, the previous credit limit reference amount, and the previous credit limit amount; a classification unit that classifies the extracted plurality of new application data into individual application data which is the new application data subject to an individual application and collective application data which is the new application data subject to a collective application 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.

The classification unit in the credit management device according to the present invention classifies, among the extracted multiple new application data, the new application data whose business partner status information indicates that the business partner is a suspicious party into the individual application data, and classifies the new application data whose business partner status information indicates that the business partner is not a suspicious party into the collective application data.

The storage unit in the credit management device according to the present invention stores an evaluation point master that associates the thresholds of the financial indicators with the evaluation points, and a limit master that associates the evaluation points with the credit limit base amount, and the credit limit base amount calculation unit identifies, for each of the individual application data and the collective application data, the evaluation points corresponding to the financial indicators 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 base amount corresponding to the evaluation points identified in the limit master as the new credit limit base amount.

The notification unit in the credit management device according to the present invention notifies the application manager identified by the corresponding application manager identification information of the individual application screen of the individual application data, which further includes information indicating the direction of change of the evaluation score relative to the previously determined evaluation score.

The notification unit in the credit management device according to the present invention notifies the application manager identified by the corresponding application manager identification information of a collective application screen including a list of the collective application data.

The notification unit in the credit management device according to 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 input by the applicant based on at least one of the individual application data and the collective application data.

The control unit in the credit management device according to 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 input by the applicant, in the workflow database.

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, the control unit extracts the customer identification information with the application deadline being a predetermined period from the current time from the credit management database and the workflow database , and executes a process for extracting the customer identification information and the application deadline corresponding to the extracted customer identification information. the step of extracting a plurality of new application data including the financial statement data, the previous credit limit reference amount, and the previous credit limit amount, the step of classifying the extracted plurality of new application data into individual application data which is the new application data subject to an individual application and collective application data which is the new application data subject to 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.

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 amount 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 extracts the customer identification information with the application deadline being a predetermined period from the current time from the credit management database and the workflow database , and stores the extracted customer identification information and the financial statement data corresponding to the extracted customer identification information in the credit management database and the workflow database. a step of extracting a plurality of new application data including the customer status information, the previous credit limit reference amount, and the previous credit limit amount; a step of classifying the extracted plurality of new application data into individual application data which is the new application data to be applied individually and collective application data which is the new application data to be applied collectively based on the customer status information; a 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 a 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.

The present invention has the effect of enabling credit management operations to be managed with high accuracy.

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

Below, an embodiment of the credit management device, credit management method, and credit management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

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

The credit management device 100 of this embodiment is a device that manages credit for each business partner. In this embodiment, an example is described in which the business partner is a company.

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, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The credit management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the credit management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

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.

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 works with a mouse to provide 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

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.

The credit management DB 106a is a database for managing credit for each business partner. The credit management DB 106a is a database that at least associates the business partner's 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.

In this embodiment, the credit management DB 106a separates the data and master data, associates and registers these items. In detail, in this embodiment, the credit management DB 106a associates and registers these items using the customer identification information as a key.

Specifically, 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 format of these data and masters is not limited to databases or tables. The data structure of these data and masters will be described in detail later.

WFDB106b is a database for managing the workflow in credit management operations. WFDB106b is a database in which multiple application data are registered, which at least correspond to customer identification information, application officer identification information, and the previous credit limit reference amount, which is the credit limit reference amount currently set for the customer.

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

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

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

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.

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

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 new application data by extracting information corresponding to customer identification information whose application deadline is a predetermined period from the present time from the credit management DB 106a and the WFDB 106b.

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 business partner status information.

In detail, the classification unit 102b classifies new application data, among the multiple new application data extracted by the extraction unit 102a, whose business partner status information indicates that the business partner is a suspicious party into individual application data, and classifies new application data whose business partner status information indicates that the business partner is not a suspicious party into collective application data.

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 collective application data, based on the evaluation score of the financial indicators of the business partner identified by the business partner identification information.

The notification unit 102d notifies the application manager identified by the corresponding application manager identification information of 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.

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

Then, when the credit limit application amount is input by the application clerk, 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.

The registration unit 102e assigns a flag indicating approval to the individual application data and collective application data approved by the approver and registers them in the WFDB 106b.

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.

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

Figure 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 Figure 2 at a predetermined timing. In this embodiment, the control unit 102 executes the flow shown in Figure 2 every 24 hours, for example, at night outside business hours, as an example.

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 specified 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, the explanation is given assuming that the present date is June 31, 2021.

Figure 3A is a schematic diagram showing an example of the data configuration of the credit limit data 106a1 contained in the credit management DB 106a. The credit limit data 106a1 is a database that associates parent company codes, company names, credit limits, and application deadlines. In the 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.

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

Returning to FIG. 2, the explanation continues. Next, the extraction unit 102a extracts new application data including the parent company code extracted in step S100 (step S102).

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 reference amount, and previous credit limit amount corresponding to the extracted parent company code from the credit management DB 106a and the WFDB 106b.

Figures 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 WFDB 106b.

Figure 3B is a schematic diagram showing an example of the data configuration of basic application data 106b1. Basic application data 106b1 is a database that associates case numbers, parent company codes, departments 1, staff members 1, departments 2, staff members 2, and statuses. The case number is an identification number for identifying application data and is assigned to each piece of application data. Staff members 1 and 2 are application staff identification information that identifies the application staff members 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. Examples of statuses are "approved", "applied for", and "not yet applied".

Figure 3C is a schematic diagram showing an example of the data configuration of application evaluation point data 106b2. Application evaluation point data 106b2 is a database that registers the case number, the evaluation points of each financial indicator of the business partner company that is the subject of the application based on the application data identified by the case number, and the comparison case number. Figure 3C shows, as examples, the names of each of the following subjects for financial indicators corresponding to the case number: year-on-year sales ratio, interest-bearing debt to monthly sales ratio, equity ratio, current ratio, quick ratio, and fixed ratio.

Figure 3D is a schematic diagram showing an example of the data configuration of application details data 106b3. 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 application details data 106b3 is registered as a total value, which is the overall evaluation point of the evaluation points of the corresponding case numbers in application time evaluation point data 106b2. Figure 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 to the right of the application amount, previous amount, and application deadline correspond to the numbers 1 and 2 to the right of the person in charge shown in the application basic data 106b1 in Figure 3B.

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

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 Figures 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, 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 the 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.

Returning to FIG. 2 for further explanation, the classification unit 102b then 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).

In this embodiment, the classification unit 102b performs classification processing based on the business partner status information registered in the company data 106a2. The business partner status information is information that represents the current status of the business partner. The business partner status information is, for example, at least one of the listed classification, the currently set credit limit threshold amount, and the business caution status.

The classification unit 102b classifies, from among the multiple extracted new application data, new application data whose business partner status information indicates that the business partner is a suspicious party into individual application data. In addition, the classification unit 102b classifies, from among the multiple extracted new application data, new application data whose business partner status information indicates that the business partner is not a suspicious party into collective application data. A suspicious party means that the safety is low. A non-suspicious party means that the safety is high.

Figure 3E is a schematic diagram showing an example of the data configuration of company data 106a2. Company data 106a2 is a database that associates parent company codes, company names, and business partner status information. Company data 106a2 is, for example, a data configuration of 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.

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

When using listing classification as trading partner 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.

Company data 106a22 is a database that associates parent company codes, company names, and the currently set credit limit standard amount, which is customer status information.

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 in the company data 106a22 that is equal to or greater than the threshold amount representing a large credit borrower, 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 in the company data 106a22 that is less than the threshold amount representing a large credit borrower, i.e., a small credit borrower, into bulk application data.

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

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 "required" 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.

The classification unit 102b may perform classification processing using at least two 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.

Returning to FIG. 2, the explanation will continue. Next, for the individual application data (step S106: Yes, step S116: Yes), the control unit 102 executes the processes of steps S108 to S128.

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

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

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

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

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

Figure 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 that associates the name of a financial indicator item with a threshold value and an evaluation point. Figure 3G shows a range represented by an upper limit value and a lower limit value as a threshold value for each financial indicator item.

Figure 3H is a schematic diagram showing an example of the data configuration of evaluation point data 106a5. Evaluation point data 106a5 is a database that associates parent company codes, company names, and evaluation points.

For each individual application data, the credit limit standard amount calculation unit 102c identifies 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 business partner identification information, from the evaluation point master 106a4.

Specifically, for example, for a company with parent company code "5678901234", the credit limit standard calculation unit 102c uses the evaluation point master 106a4 to identify the evaluation point for each item of the financial indicators included in the financial statement data 106a3 shown in FIG. 3F. In detail, the credit limit standard 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 standard calculation unit 102c identifies the evaluation point "10" from the evaluation point master 106a4 as the evaluation point corresponding to the current ratio "120.2%". Similarly, the credit limit standard 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%".

The credit limit reference amount calculation unit 102c then 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 Figure 3H).

Then, the credit limit base amount calculation unit 102c uses the calculated evaluation points and the credit limit master 106a6 to calculate the new credit limit base amount, which is the new credit limit base amount for the next application deadline.

Figure 3I is a schematic diagram showing an example of the data configuration of the credit limit master 106a6. The credit limit master 106a6 is a database that associates ratings, evaluation points, and credit limit base amounts.

The credit limit standard amount calculation unit 102c calculates the limit amount corresponding to the evaluation points calculated for each parent company code, i.e., each individual application data, in the limit amount master 106a6 as the new credit limit standard amount, which is the new credit limit standard amount.

Specifically, for example, the credit limit standard amount calculation unit 102c calculates "35,000,000" as the new credit limit standard amount for 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 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 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 parent company code "8901234567" with an evaluation score of "72".

Returning to FIG. 2, the explanation will be continued. Then, the credit limit reference amount calculation unit 102c registers the individual application data, including the evaluation score calculated in step S108 and the new credit limit reference amount calculated in step S110, in the WFDB 106b (step S112).

Figures 3J to 3L are schematic diagrams showing an example of a WFDB 106b in which individual application data 30 including evaluation points and new credit limit base amounts is registered.

Figure 3J is a schematic diagram showing an example of the data configuration of basic application data 106b1 in which individual application data 30 has been registered. Figure 3K is a schematic diagram showing an example of the data configuration of application time evaluation point data 106b2 in which individual application data 30 has been registered. Figure 3L is a schematic diagram showing an example of the data configuration of detailed application data 106b3 in which individual application data 30 has been registered.

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

At this point, the credit limit reference amount calculation unit 102c registers the individual application data 30 with the status set to "not applied for."

Returning to FIG. 2, the explanation continues. The notification unit 102d notifies the individual application data 30 to the application person identified by the corresponding application person identification information (step S114).

That is, when the control unit 102 creates new application data such as the individual application data 30 or the collective application data described below, it notifies the application staff represented by "Staff Member 1" or "Staff Member 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 below to the address of the application staff via the network 300.

In this way, new application data for business partners who are companies with parent company codes whose application deadline is a specified period later is automatically created by the control unit 102, and is classified into individual application data 30 and collective application data, and notified to the person in charge of application. This reduces the risk of missing out on processing credit management work.

Figure 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 application clerk. 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 application clerk selects one piece of new application data for which an application is to be made from the displayed list of new application data. Here, the explanation will continue assuming a situation in which one piece of individual application data 30A has been selected.

Returning to FIG. 2, the explanation will continue. If individual application data 30 is selected (step S116: Yes), proceed to step S118.

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

The notification unit 102d may notify the application manager identified by the corresponding application manager 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.

In detail, the notification unit 102d compares each of the financial indicator subject names and overall evaluation points calculated in step S108 with the corresponding financial indicator subject names and overall evaluation points currently set for the corresponding parent company code. Then, if the evaluation point is higher than the currently set evaluation point, information representing an up arrow is assigned to each evaluation point, if the evaluation point is the same, information representing a sideways arrow is assigned, and if the evaluation point is lower, information representing a down arrow is assigned. Note that the assignment of information representing the direction of change may be performed by the credit limit standard amount calculation unit 102c.

Then, the notification unit 102d notifies the application person identified by the corresponding application person identification information of the individual application screen 52 of the individual application data 30, which includes information indicating these change directions.

Figure 4B is a schematic diagram showing an example of an individual application screen 52. As shown in Figure 4A, assume that individual application data 30A for company name "EEEEE" with case number "101" is selected by "Yamada Taro", the application person in charge. 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", the application person in charge. Therefore, for example, the individual application screen 52 shown in Figure 4B is displayed on the monitor of the personal computer of "Yamada Taro", the application person in charge.

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

As a result, applicants can make new credit applications for business partners that are companies with parent company codes whose application deadline is 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.

The individual application screen 52 also includes financial statement data 106a3 showing the financial indicators of the business partner, the previous credit limit base amount, the previous credit limit amount, data on the financial indicators, the evaluation score of the financial indicators, a new credit limit base amount which is the new credit limit base amount, and an arrow which is change information showing the direction of change in the evaluation score relative to the previous evaluation score. Therefore, the person in charge of application can easily set the credit limit application amount by referring to this information.

The application person inputs the credit limit application amount in input field 52A and presses the application button to make an application request for individual application data 30A including the credit limit application amount.

Returning to FIG. 2 for further explanation, the registration unit 102e then receives from the applicant individual application data 30A including the credit limit application amount and the application request signal (step S120). The registration unit 102e registers the credit limit application amount included in the received individual application data 30A to the corresponding individual application data 30A in the application detail data 106b3.

Figures 5A to 5C are schematic diagrams showing an example of the data configuration of basic application data 106b1, application evaluation point data 106b2, and application detail data 106b3 registered in individual application data 30, including the credit limit application amount entered by the applicant. As shown in Figures 5A to 5C, in individual application data 30A for case number "101", the credit limit application amount "15,000,000" entered by application person 1, "Yamada Taro", is registered as application amount 2. Furthermore, when the registration unit 102e accepts an application request, it changes the status in individual application data 30A to "application in progress".

Returning to FIG. 2 for further explanation, 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).

For this reason, for example, the 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/or bulk application data) applied for by the application staff on the monitor of the approver's personal computer. Then, when the approver selects individual application data 30, which is one piece of new application data, the individual application approval screen 54 for the selected individual application data 30 may be displayed on the monitor.

As shown in FIG. 6A, the approval screen 54 for an individual application includes the 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 represents the supplier's financial indicators, the previous credit limit base amount, the previous credit limit amount, the evaluation score of the financial indicator, the new credit limit base amount which is the new credit limit base amount, and an arrow which is change information indicating the direction of change in the evaluation score relative to the previous evaluation score. The individual application screen 52 also includes the credit limit amount currently applied for in the individual application data 30A.

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 after a specified period of time on a single approval screen 54, without having to separately check a large number of items required to confirm the credit application.

The individual application approval screen 54 also includes financial indicator data contained in the financial statement data 106a3 representing the financial indicators of the business partner, the previous credit limit base amount, the previous credit limit amount, the financial indicator data, the evaluation score for the financial indicator, the new credit limit base amount which is the new credit limit base amount, and an arrow which is change information showing the direction of change in the evaluation score relative to the previous evaluation score. Therefore, by referring to this information, the approver can easily determine whether or not to approve the credit limit application amount.

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

Returning to FIG. 2, the explanation 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.

Figures 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 limit master 106a6 after the processing of step S128 is performed by the registration unit 102e.

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 limit master 106a6. Therefore, as shown in FIG. 6D, the 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.

Returning to FIG. 2, the explanation will continue. On the other hand, for the batch 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.

For each piece of collective application data (step S106: No), the credit limit standard amount calculation unit 102c calculates the evaluation points of the business partner companies identified by the parent company codes included in the collective application data 32 (step S130). The credit limit standard amount calculation unit 102c calculates 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 for the evaluation points in the individual application data 30.

Next, the credit limit standard amount calculation unit 102c calculates a new credit limit standard amount, which is the new credit limit standard amount for the next application deadline, based on the evaluation score calculated in step S130 (step S132). The credit limit standard amount calculation unit 102c uses the credit management DB 106a to calculate the evaluation score 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 for the new credit limit standard amount for the individual application data 30.

Then, the credit limit standard amount calculation unit 102c registers the bulk application data, including the evaluation points calculated in step S130 and the new credit limit standard amount calculated in step S132, in the WFDB 106b (step S134).

Figures 7A and 7B are schematic diagrams showing an example of a WFDB 106b in which bulk application data 32 including evaluation points and new credit limit base amounts is registered.

Figure 7A is a schematic diagram showing an example of the data structure of basic application data 106b1 in which collective application data 32 is registered. Figure 7B is a schematic diagram showing an example of the data structure of detailed application data 106b3 in which collective application data 32 is registered.

As shown in Figures 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. Note that, 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 similarly registered for the application time evaluation score data 106b2 for each case number.

At this point, the credit limit reference amount calculation unit 102c registers the bulk application data 32 with the status set to "not applied for."

Returning to FIG. 2, the explanation continues. The notification unit 102d notifies the batch application data 32 to the application person identified by the corresponding application person identification information (step S114).

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

In this way, new application data for companies with parent company codes whose application deadline is a specified period 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 missing out on processing credit management work.

Figure 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 which an application is to be made from the displayed list of new application data. Here, the explanation will continue assuming a situation in which the bulk application data 32 has been selected.

Returning to FIG. 2, the explanation continues. If batch application data 32 is selected (step S116: No), proceed to step S136.

In step S136, the notification unit 102d notifies the application manager of the batch application screen for the batch application data 32 selected in step S116 (step S136).

Figure 8B is a schematic diagram showing an example of a collective application screen 62. As shown in Figure 8A, assume that collective application data 32 is selected by "Yamada Taro", 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", the person in charge of application. Therefore, for example, the collective application screen 62 shown in Figure 8B is displayed on the monitor of the personal computer of "Yamada Taro", the person in charge of application.

As shown in FIG. 8B, the bulk application screen 62 displays a list of bulk application data 32 corresponding to the applicant "Yamada Taro." The bulk application screen 62 has a simpler display than the individual application screen 52, and is configured to allow a list of new application data classified into the bulk application data 32 to be viewed all at once. In addition, the bulk 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 bulk application data 32.

As a result, applicants can make new credit applications in bulk for business partners with parent company codes whose application deadline is a specified period from now 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.

The batch application screen 62 also displays a list of multiple new application data for which the application staff member is responsible. The batch application screen 62 also includes some of the items of financial indicators included in the financial statement data 106a3 that represent the financial indicators of the business partner, as well as evaluation points. Therefore, by referring to this information, the application staff member can easily set the credit limit application amount for multiple new application data classified into the batch application data 32.

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

Returning to FIG. 2 for further explanation, the registration unit 102e then receives from the applicant the batch application data 32 including the credit limit application amount and the application request signal (step S138). The registration unit 102e registers the credit limit application amount included in the received batch application data 32 to the corresponding batch application data 32 in the application detail data 106b3 (step S140).

Figures 9A and 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 entered by the application staff. As shown in Figures 9A and 9B, the batch application data 32 for case number "111" has the credit limit application amount "9,000,000" entered by the application staff member "Yamada Taro", who is staff member 1, registered as application amount 1. Similarly, the credit limit application amount "11,000,000" entered by the main application staff member "Yamada Taro", who is staff member 1, registered as application amount 2. Furthermore, when the registration unit 102e accepts an application request, it changes the status in the batch application data 32 to "application in progress".

Returning to FIG. 2 for further explanation, 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).

For this reason, for example, a bulk application approval screen 64 as 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 bulk application data 32) applied for by the application staff on the monitor of the approver's personal computer. Then, when the approver selects a single piece of new application data, the bulk application data 32, the bulk application approval screen 64 for the selected bulk application data 32 may be displayed on the monitor.

As shown in FIG. 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.

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 of time later, on a single batch application approval screen 64, without having to separately check a large number of items required to confirm the credit application.

The bulk application approval screen 64 also displays a list of bulk application data 32. This allows the approver to approve or disapprove the list of new application data classified as bulk application data 32 all at once.

For example, the approver approves the batch application data 32 by pressing the approval button.

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

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

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 associates the approved credit limit application amount with the parent company code of the approved collective application data 32, registers the approved credit limit application amount as the credit limit, and associates the new application deadline in the limit master 106a6. Therefore, as shown in FIG. 10D, the 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.

As described above, the credit management device 100 of this embodiment includes a control unit 102 and a memory unit 106. The memory unit 106 stores a credit management DB 106a and a WFDB 106b. The credit management DB 106a is a database that at least corresponds the client identification information (parent company code), client status information, financial statement data 106a3 representing financial indicators, the previous credit limit amount which is the currently set credit limit amount, and the application deadline of the previous credit limit amount. The WFDB 106b is a database in which multiple application data are registered that at least corresponds the client identification information (parent company code), application officer identification information, and the previous credit limit base amount which is the credit limit base amount currently set for the client.

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 current time, and extracts a plurality of new application data including the extracted customer identification information (parent company code), the 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 business partner identified by the business partner 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 staff identified by the corresponding application staff 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.

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 application deadline, and automatically classifies it into individual application data 30 and collective application data 32. Then, the credit management device 100 calculates the new credit limit base amount, which is the new credit limit base amount for the next application deadline, based on the evaluation score of the business partner identified by the business partner 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.

Therefore, the credit management device 100 of this embodiment can prevent applicants and approvers from missing out on credit management tasks for business partners that are companies with parent company codes for which the application deadline is a specified period of time later.

Therefore, the credit management device 100 of this embodiment can manage credit management operations with high accuracy.

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 applicant of the individual application data 30 and the collective application data 32 into which the new application data has been classified.

Therefore, in addition to the above 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.

The credit management device 100 of this embodiment also automatically extracts new application data for the currently set application deadline a predetermined period before the application deadline, and automatically classifies the data into individual application data 30 and collective application data 32 based on business partner status information. The credit management device 100 then notifies the person in charge of application of the individual application data 30 and the collective application data 32.

Therefore, the application staff can process new application data for clients who need to be careful, such as large clients or clients with caution, as individual application data 30, and process new application data for clients who do not need to be careful, such as good clients or 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.

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

The credit management device 100 also notifies the application staff of the individual application screen 52. By visually checking the individual application screen 52, the application staff 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 later 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.

The credit management device 100 also notifies the approver of the approval screen 54 for the individual application. By visually checking the approval screen 54 for the individual application, 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 for which the application deadline is a specified period of time later, on a single 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.

The credit management device 100 also notifies the applicant of the batch application screen 62. The batch application screen 62 displays a list of the batch application data 32 corresponding to the applicant.

Therefore, by visually checking the batch application screen 62, the applicant 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 later 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. Therefore, the credit management device 100 of this embodiment can improve business efficiency.

The credit management device 100 also notifies the approver of the batch application approval screen 64. Therefore, the approver can easily check the items necessary 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.

[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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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.

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 a known method.

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.

Furthermore, with regard to the credit management device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

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 on a non-transient computer-readable recording medium that contains 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 is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a portable DVD (registered trademark) or Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

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

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on 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.

100 Credit management device 102 Control unit 106 Storage unit 102a Extraction unit 102b Classification unit 102c Credit limit reference amount calculation unit 102d Notification unit 102e Registration unit

Claims (9)

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 that is the object of an individual application and collective application data that is the new application data that is the object of a collective application 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 an application person identified by the corresponding application person identification information of 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;
A credit management device comprising: The classification unit includes:
Among the extracted multiple pieces of new application data,
The new application data, which indicates that the business partner status information is a suspicious business partner, is classified into individual application data;
classifying the new application data, which indicates that the business partner status information is not a cautionary business partner, into the batch application data;
The credit management device according to claim 1. 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;
The credit management device according to claim 1 or 2. 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. 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. 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. 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: A credit management method 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,
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: 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