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

Conventionally, as a system that performs credit management, there is Patent Document 1, for example. In the system of Patent Document 1, a standard credit cost rate acquisition means for acquiring a standard credit cost rate, a standard transaction share acquisition means for acquiring a standard transaction share, and a credit limit calculated according to the credit rating of the customer credit risk rate acquisition means for acquiring a credit risk rate; transaction share calculation means for calculating a transaction share by calculating the standard transaction share*the standard credit cost rate/the credit risk rate; Means for obtaining the business partner's standard appraisal value within the reference period for obtaining the business partner's standard appraisal value within the reference period, which is the amount that is the standard for the business activity of the business partner, and the average collection site, which is the average period for collecting the receivables of the business partner and a credit limit calculation means for calculating a credit limit by calculating the client standard appraisal value within the reference period×the average collection site×the transaction share.

JP-A-2006-92150

However, in Patent Document 1, regarding credit management for each customer in an entire group composed of multiple subgroups (for example, an entire group company composed of multiple companies or an entire company composed of multiple business departments) is not described at all.

The present invention has been made in view of the above, and provides a credit management apparatus, a credit management method, and a credit management method capable of quickly performing credit management for each customer in an entire group composed of a plurality of subgroups. The purpose is to provide a management program.

In order to solve the above-described problems and achieve the object, the present invention provides a credit management device comprising a control unit and a storage unit, and managing credit for each customer in an entire group composed of a plurality of subgroups. wherein the storage unit associates a unified code for identifying the business partner uniformly in the entire group and an individual code for individually identifying the business partner in the plurality of subgroups. Linkage including the registered name identification master, the warning master in which the warning conditions regarding the credit limit and the performance against the planned maintenance rate are set, and the individual code collected for each subgroup and including the credit collateral information for the trading partner data is stored, and the control unit includes setting means for setting the credit limit and planned maintenance rate for each customer in the entire group, and collecting means for collecting the linked data for each subgroup Then, on a monthly basis, referring to the name identification master, the set credit limit amount and plan are calculated using the linked data for each business partner of the entire group, which is a unit of unified code linked to the individual code. monthly processing means for calculating actual results for the maintenance rate; and warning means for referring to the warning master and extracting and outputting warning candidates based on the actual results for the credit limit amount and the planned maintenance rate. Characterized by

Further, according to the present invention, the group consisting of the plurality of subgroups may include a group company consisting of a plurality of companies or a company consisting of a plurality of divisions.

Further, according to the present invention, the credit/debt collateral information includes credit balance, order backlog, debt balance, and collateral amount, and the actual credit limit amount is calculated by (receivable balance+order backlog)/credit limit amount. It is the calculated credit limit rate, and the actual performance against the planned maintenance rate may be the actual maintenance rate calculated by (debt balance + collateral amount)/(receivable balance + order backlog).

Further, in order to solve the above-described problems and achieve the object, the present invention provides an information processing apparatus comprising a control unit and a storage unit, and a group consisting of a plurality of subgroups for each business partner. wherein the storage unit includes a unified code for uniformly identifying the business partner in the entire group and individually identifying the business partner in the plurality of subgroups. A name identification master registered in association with an individual code for doing so, a warning master in which warning conditions regarding performance against the credit limit amount and planned maintenance rate are set, and collected for each subgroup, the individual code and the corresponding business partner a setting step of setting a credit limit amount and a planned maintenance rate for each business partner in the entire group, which is executed by the control unit; a collecting step of collecting the linked data for each of the subgroups; and referring to the name identification master on a monthly basis to collect the linked data for each business partner of the entire group, which is a unified code unit linked to the individual code. is used to calculate the actual results for the set credit limit and planned maintenance rate, and the warning master is referenced to generate warning candidates based on the actual results for the credit limit and planned maintenance rate. and a warning step of extracting and outputting.

Further, in order to solve the above-described problems and achieve the object, the present invention provides an information processing apparatus comprising a control unit and a storage unit, and a group consisting of a plurality of subgroups for each business partner. wherein the storage unit includes a unified code for uniformly identifying the business partner in the entire group and individually identifying the business partner in the plurality of subgroups A name identification master registered in association with an individual code for doing so, a warning master in which warning conditions regarding performance against the credit limit amount and planned maintenance rate are set, and collected for each subgroup, the individual code and the corresponding business partner a setting step of setting a credit limit amount and a planned maintenance rate for each business partner in the entire group in the control unit; a collection step of collecting the linked data every month, and on a monthly basis, referring to the name identification master and using the linked data in units of business partners of the entire group, which is a unified code unit linked to the individual code. a monthly processing step of calculating actual results for the set credit limit amount and planned maintenance rate; and a warning step for outputting.

Advantageous Effects of Invention According to the present invention, it is possible to quickly perform credit management for each customer in the entire group composed of a plurality of subgroups.

FIG. 1 is a diagram showing an example of an overview of data linkage in a credit management system according to this embodiment. FIG. 2 is a diagram showing an example of a data utilization image (flow at the time of order check) of the credit management system according to the present embodiment. FIG. 3 is a block diagram showing an example of the configuration of the credit management system according to this embodiment. FIG. 4 is a diagram showing a configuration example of a customer master and a name identification master. FIG. 5 is a diagram showing a configuration example of a credit setting master. FIG. 6 is a diagram showing a configuration example of a warning master. FIG. 7 is a flowchart for explaining an outline of the flow of the overall processing of the control unit of the credit management system. FIG. 8 is a diagram showing sample data of linked data and aggregated data. FIG. 9 is a diagram showing a form output example of warning candidates. FIG. 10 is a diagram showing an output example of summarizing warning candidates.

Embodiments of a credit management device, a credit management method, and a credit management program will be described in detail below with reference to the drawings. It should be noted that the present invention is not limited by this embodiment. Specific configurations and operations will be described below.

[1. overview]
Conventionally, the credit limit, credit balance, and collateral are managed for each company of a group company consisting of multiple companies or each business division of a company consisting of multiple business divisions. Overall, it was not possible to visualize the credit limit, credit balance, and collateral ratio for each customer. Even for the same business partner, there is a restriction that each group company or business department manages them with different customer numbers. I had to collect.

In addition, the above checks are performed at the timing of monthly closing, but because it takes time to tabulate, there is a risk of excessive sales to specific business partners and an increase in receivables, insufficient maintenance, and credit limit warnings. Despite this, there were management issues such as delays in implementing countermeasures and the need for time to make credit management decisions.

Therefore, in the credit management system of the present embodiment, a mechanism is constructed in which credit management is performed on a monthly basis for each business partner in a group company or a company that employs a business division system, and candidate destinations within the warning criteria are extracted.

Specifically, in the monthly check of credit management, "name identification information of business partners within the group company and each business department" and "credit collateral information of each business partner by each group company and business department" are aggregated at the end of the month, and the credit balance and coverage rate for each business partner are aggregated. In this way, it has become possible to make a detailed trial calculation of credit capacity by adding debt and collateral information in addition to credit information.

In addition, it is now possible to extract not only borrowers that have exceeded the credit check criteria, but also candidate borrowers that are included in the warning criteria, and it has become possible to take action on credit management issues with a sense of speed. .

In the present embodiment, a group company made up of multiple companies, a company made up of multiple divisions, etc. are collectively referred to as a "group made up of multiple subgroups". In the following explanation, as an example of "a group consisting of a plurality of subgroups", a group company consisting of a plurality of companies will be explained, but the present invention is not limited to this. Needless to say, it can also be applied to a company or the like.

Specifically, in the following, a group company is composed of a head office, a subsidiary A, and a subsidiary B, and the business partners are XX, XX Shoji, and XX Real Estate, as an example.

An outline of a credit management system 100 (also referred to as a “credit management device”) according to the present embodiment will be described with reference to FIGS. 1 and 2. FIG. FIG. 1 is a diagram illustrating an example of an overview of data linkage. FIG. 2 is a diagram showing an example of a data utilization image (flow when checking an order).

In the credit management system 100 according to the present embodiment, as shown in FIG.・Collaboration (acquisition) of order backlog data, collateral/guarantee data, business partner data, etc., can be aggregated by the entire group company.

The credit balance can be calculated by credit balance=credit limit amount-(receivable balance+order balance). For example, if the credit limit is 10 million yen, the balance of receivables is 6 million yen, and the order balance is 3 million yen, the credit balance is 1 million yen.

In the credit management system 100 of the present embodiment, as shown in FIG. 2, first, the credit limit and planned maintenance rate are set (1). Next, each accounting system 400 is aggregated (referring to the balance of receivables, the amount of money deposited, etc.) on a monthly basis (base date), and the credit limit for the entire group is updated (2). By extracting warning candidate destinations in order to check whether or not they have given unreasonable credit, it is possible to review the credit limit and the like (3).

[2. composition]
An example of the configuration of a credit management system (credit management device) 100 according to this embodiment will be described with reference to FIG. FIG. 3 is a block diagram showing an example of the configuration of the credit management system 100. As shown in FIG. In the following explanation, the unit of all amounts is "1,000 yen", and description of the unit is omitted.

The credit management system 100 is a commercially available desktop personal computer. Note that the credit management system 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. It may be an information processing device.

The credit management system 100 includes a control section 102 , a communication interface section 104 , a storage section 106 and an input/output interface section 108 . Each unit included in the credit management system 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the credit management system 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 another device via a communication line. Here, the network 300 connects the credit management system 100, the accounting system 400 of each company that constitutes the server 200 and group companies (for example, the head office, subsidiary A, subsidiary B), etc. so that they can communicate with each other. It has a function, and is, for example, the Internet or a LAN (Local Area Network). The credit management system 100 can collect (acquire) credit collateral information about the company's business partners from the accounting system 400 via the communication interface unit 104 and the network 300 . Data such as various masters described later 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 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that realizes a pointing device function in cooperation with a mouse. In the following description, 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 stores a computer program for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

The storage unit 106 includes, for example, a customer master 106a, a name identification master 106b, a credit setting master 106c, a warning master 106d, cooperation data 106e, and total data 106f. FIG. 4 is a diagram showing a configuration example of the customer master 106a and the name identification master 106b. FIG. 5 is a diagram showing a configuration example of the credit setting master 106c. FIG. 6 is a diagram showing a configuration example of the warning master 106d.

The customer master 106a is a master for managing customers individually in each company. In FIG. 4, the customer master 106a for each of the head office, subsidiary A, and subsidiary B is shown. The customer master 106a, as shown in FIG. 4, is composed of a table or the like in which, for example, a KEY, which is an individual code used individually by each company to identify a customer, is associated with the company name of the customer and registered. can do.

In the example of the customer master 106a shown in FIG. 4, between the head office and the subsidiary A, XX is managed with KEY "200", XX commercial business with KEY "300", and XX real estate with KEY "400". , all KEYs are common. In contrast, Subsidiary B manages XX with KEY "202", XX Commercial with KEY "302", and XX real estate with KEY "402". In this way, even though the business partner is the same, if different KEYs are used between companies to manage business partners, it is not possible to aggregate linked data for each business partner. For this purpose, a name identification master 106b is required for grouping business partners (so-called name identification) by assigning the same code.

The name identification master 106b is a master for managing business partners in a unified manner throughout the group companies. As shown in FIG. 4, the name identification master 106b includes, for example, a company code for identifying companies that make up a group company, a uniform code for identifying a business partner that is used uniformly throughout the group companies, and a KEY. , a table or the like in which the company names of business partners are registered in association with each other.

In the name identification master 106b of FIG. 4, the head office, the subsidiary A, and the subsidiary B all share the unified code "100000001" for XX, the unified code for XX Shoji "100000002", and the unified code "100000003" for XX real estate. , it can be said that business partners are grouped together by assigning the same code to the same business partners (so-called name identification).

The credit setting master 106c is a master for setting the credit limit amount and planned maintenance rate for each business partner for the entire group company. The credit setting master 106c, as shown in FIG. 5, includes, for example, a unified code, the company name of the customer, the reference date for monthly aggregation, and the credit limit for the customer for the entire group company. The credit limit amount and the planned maintenance rate, which is the target maintenance rate for the credit against the customer of the entire group company, can be registered in association with each other and configured in a table or the like.

In the example shown in FIG. 5, the first line contains the unified code "100000001", the company name "XX", the reference date "2019/3/31", the credit limit "70,000", and the planned maintenance rate "60". %”, the second line is the uniform code “100000002”, the company name “XX Trading”, the reference date “2019/3/31”, the credit limit “4,000”, and the planned maintenance rate “50%”, The third line has the unified code "100000003", the company name "XX real estate", the reference date "2019/3/31", the credit limit "20,000", and the planned maintenance rate "40%". .

The warning master 106d specifies warning conditions based on the credit limit rate, which is the actual result for the set credit limit amount, and the actual maintenance rate, which is the actual result for the set planned maintenance rate, and extracts warning candidates. is the master. As shown in FIG. 6, the warning master 106d can be composed of, for example, a table or the like in which warning codes, names as warning contents, and warning condition data are associated and registered.

In the example shown in FIG. 6, the first line is the warning code "001", the name "credit limit exceeded", the warning condition "credit limit rate>100%", and the second line is the warning code "002", the name "credit limit warning", condition "credit limit rate > 80% and credit limit rate ≤ 100%", the third line is warning code "101", name "planned maintenance failure", warning condition "actual maintenance rate > planned maintenance rate ', the fourth line has a warning code of '102' and a name of 'insufficient actual maintenance'.

The linked data 106e is data for managing credit/debt collateral information (claim amount, order backlog, debt amount, and collateral amount) for each business partner of each company that constitutes a group company. The linkage data 106e includes, for example, a company code, a key, a business partner company name, a monthly processing reference date, a credit balance that is the balance of a claim to a business partner of a company that constitutes a group company, and a group Order backlog, which is the amount of services or products provided by the companies that make up the company that have been ordered from business partners but have not yet been provided or delivered to business partners, and the number of companies that make up the group It may include the debt balance, which is the balance of the debt to the business partner, and the collateral amount, which is the amount of collateral (for example, the amount of guarantee) taken from the business partner by the companies that make up the group company (Fig. 8 reference).

The aggregated data 106f is data for monthly management of the credit limit rate, maintenance rate, and the like for each business partner for the entire group company set in the credit setting master 106c. More specifically, the aggregated data 106f uses the linked data 106e on a monthly basis for the credit limit amount and planned maintenance rate for each business partner for the entire group company set in the credit setting master 106c, and group This data is used to calculate the credit limit rate and actual maintenance rate for each customer in the entire company and to determine whether or not it corresponds to a warning candidate.

The aggregated data 106f includes, for example, a unified code, a reference date, a company name of a business partner, a credit limit amount that is the credit limit for business partners in the entire group companies, and a credit limit rate that is the actual credit limit amount. , the planned maintenance rate, which is the target maintenance rate of the claims for the business partners of the entire group company, the actual maintenance rate, which is the actual performance of the planned maintenance rate, and the credit collateral information (credit amount, order backlog, debt amount and collateral amount) (see FIG. 8). The data of the credit setting master 106c is written as the data of the unified code, company name, reference date, credit limit amount, and planned maintenance rate.

The credit limit interest rate can be calculated by credit limit rate=(receivable balance+order balance)/credit limit amount. The actual maintenance rate can be calculated by the actual maintenance rate = (debt balance + collateral amount) / (receivable balance + order backlog).

Returning to FIG. 3 , the control unit 102 is a CPU or the like that comprehensively controls the credit management system 100 . The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute.

The control unit 102 functionally and conceptually includes a setting unit 102a, a collection unit 102b, a monthly processing unit 102c, and a warning unit 102d.

The setting unit 102a, for example, according to the operator's operation on an input screen (not shown) displayed on the monitor 114, sets the unified code, company name, standard Set the date, credit limit, and planned maintenance rate.

The collection unit 102b collects the linked data 106e, which is credit collateral information for each company, from the accounting systems 400 of the head office, subsidiary A, and subsidiary B. The collection of the linked data 106e may be performed at the end of the month when monthly processing (monthly check) is performed, or may be performed at shorter intervals and updated to the latest data.

The monthly processing unit 102c performs monthly processing, and on a monthly basis (base date), refers to the name identification master 106b, and is a unified code unit linked to the KEY, which is an individual code. , and using the linked data 106e, the credit limit and the planned maintenance rate set by the setting unit 102a are calculated.

The warning unit 102d refers to the warning master 106d, extracts and outputs warning destination candidates based on the credit limit amount and the planned maintenance rate results of the aggregated data 106f.

The receivables/debts collateral information includes receivables balance, order backlog, debt balance, and collateral amount. The record of the maintenance rate may be the actual maintenance rate calculated by (outstanding debt + collateral amount)/(receivable balance + order backlog). The credit/debt collateral information is not limited to the credit balance, order balance, debt balance, and collateral amount, and other information may be used. Also, the actual credit limit amount and planned maintenance rate are not limited to the credit limit interest rate and the actual maintenance rate, and other actual values may be used, such as the credit reserve.

[3. Concrete example]
A specific example of processing of the control unit 102 of the credit management system 100 according to the present embodiment will be described with reference to FIGS. 3 to 10. FIG. FIG. 7 is a flow chart for explaining an overview of the overall processing flow of the control unit 102 of the credit management system 100. As shown in FIG.

With reference to FIG. 7, an outline of the overall processing flow of the control unit 102 of the credit management system 100 will be described. In FIG. 7, the setting unit 102a, for example, according to the operator's operation on an input screen (not shown) displayed on the monitor 114, sets the credit limit amount for each business partner of the entire group company in the credit setting master 106c. and the planned maintenance rate, etc. are set (step S1).

The collection unit 102b collects the linked data 106e, which is credit collateral information of each business partner for each company, from the accounting systems 400 of the companies (for example, the head office, the subsidiary A, and the subsidiary B) that constitute the group company ( step S2).

The monthly processing unit 102c refers to the name identification master 106b on a monthly basis (base date), and collects linked data 106e in units of business partners of the entire group company, which are units of uniform codes linked to KEY, which is an individual code. is used to calculate the credit limit set by the setting unit 102a and the actual results for the planned maintenance rate to create total data 106f (step S3).

The warning unit 102d refers to the warning master 106d, extracts and outputs warning destination candidates based on the actual credit limit amount and planned maintenance rate in the aggregated data 106f (step S4).

Next, referring to the configuration examples of the master in FIGS. 4 to 6 and the sample data in FIGS. 8 to 10,
A specific example of processing of the control unit 102 of the credit management system 100 will be described. FIG. 8 is a diagram showing sample data of linked data and aggregated data.

In the following explanation, using the data examples of the customer master 106a, the name identification master 106b, and the warning master 106d shown in FIGS. A case of creating aggregated data 106f will be described.

In the example of the linked data 106e shown in FIG. 8, for the head office of the company code "100", the first line contains the KEY "200", the company name "XX", the reference date "2019/3/31", and the balance of receivables " 10,000", order backlog "5,000", debt balance "8,000", collateral amount "12,000", the second line is KEY "300", company name "XX Shoji", reference date " 2019/3/31”, the balance of receivables “500”, the balance of orders received “3,000”, the balance of obligations “500”, and the collateral amount “1,000”.

For subsidiary A with company code "101", the third line contains KEY "200", company name "XX", reference date "2019/3/31", balance of receivables "12,000", order backlog "2, 000", debt balance "7,000", collateral amount "0", 4th line is KEY "400", company name "XX real estate", reference date "2019/3/31", receivables balance "10, 000", order backlog "5,000", debt balance "0", and collateral amount "10,000".

For subsidiary B with company code "102", the fifth line contains KEY "202", company name "XX", reference date "2019/3/31", balance of receivables "14,000", order backlog "1, 000", debt balance "2,000", collateral amount "10,000", line 6 is KEY "402", company name "XX real estate", reference date "2019/3/31", receivables balance " 0", order backlog "8,000", debt balance "5,000", and collateral amount "0".

Next, the creation of the tabulated data 106f shown in FIG. 8 from the linked data 106e shown in FIG. 8 will be described. In the following, we will explain in the order of aggregation for business partners "xx", "xx commercial", and "xx real estate" for the entire group company.

First, in FIG. 8, the monthly processing unit 102c puts the unified code, company name, reference date, credit limit amount, and planned maintenance rate of the credit setting master 106c shown in FIG. data.

(1. Aggregation of business partners “XX”)
Referring to the name identification master 106b in FIG. 4, the unified code for the supplier "XX" is "100000001", and the KEYs corresponding to the unified code "100000001" are "200" and "202".

The monthly processing unit 102c uses the keys "200" and "202" from the linked data 106e to extract the data of the balance of receivables, the balance of orders, the balance of debts, and the amount of collateral in the first, third, and fifth lines. Acquired, receivable balance (36,000 = 10,000 + 12,000 + 14,000), order backlog (8,000 = 5,000 + 2,000 + 1,00), debt balance (17,000 = 8,000 + 7,000 + 2,000) ) and collateral amount (13,000=12,000+0+1,000), and writes the result of the totalization to the first line of the totalized data 106f.

Next, the monthly processing unit 102c calculates credit limit rate = (balance of receivables "36,000" + order backlog "8,000")/credit limit amount "70,000" = 62.9%, Actual maintenance rate = (balance of debt "17,000" + collateral amount "13,000") / balance of receivables "36,000" + order backlog "8,000")) = 68.2%, one line write in the eyes

(2. Aggregation of business partner “XX Shoji”)
Referring to the name identification master 106b in FIG. 4, the unified code for the business partner "XX Trading" is "100000002", and the keys associated with the unified code "100000002" are "300" and "302".

The monthly processing unit 102c acquires data on the balance of receivables, the outstanding order balance, the outstanding balance of debts, and the amount of collateral in the second row from the linked data 106e using KEYs "300" and "302" as keys, and obtains the balance of receivables (500 ), order backlog (3,000), debt balance (500), and collateral amount (1,000) are written in the second line (in this case, since only one hit is found, they are written as they are).

Next, the monthly processing unit 102c calculates the credit limit rate = (balance of receivables "500" + order backlog "3,000")/credit limit "4,000" = 87.5%. Write rate = (debt balance "500" + collateral amount "1,000")/(receivable balance "500" + order backlog "3,000") = 42.9% in the second line.

(3. Aggregation of business partners “XX real estate”)
Referring to the name identification master 106b in FIG. 4, the unified code for the client "XX real estate" is "100000003", and the KEYs associated with the unified code "100000003" are "400" and "402".

The monthly processing unit 102c acquires data on the receivables balance, the order backlog, the debts balance, and the amount of collateral in the 4th and 6th rows from the linkage data 106e using KEYs "400" and "402" as keys, and obtains the receivables balance. (10,000 = 10,000 + 0), order backlog (13,000 = 5,000 + 8,000), debt balance (5,000 = 0 + 5,000), collateral amount (10,000 = 10,000 + 0) and write the total result to the third line.

Next, the monthly processing unit 102c calculates credit limit rate = (balance of receivables "10,000" + order backlog "13,000")/credit limit amount "20,000" = 115.0%, Actual maintenance rate = (outstanding debt "5,000" + collateral amount "10,000") / (outstanding receivable "10,000" + order backlog "13,000") = 65.2% is written in the third line. .

(4. Extraction of Warning Candidates)
The warning unit 102d refers to the warning master 106d shown in FIG. 6 and extracts warning candidates based on the credit limit rate and the actual maintenance rate of the aggregated data 106f aggregated by the monthly processing unit 102c.

The customer "XX" in the first row of the aggregated data 106f has a credit limit rate of "62.9%" and an actual maintenance rate of "68.2%", so it does not correspond to the warning conditions of the warning master 106d.

The credit limit rate for the client "XX Trading" in the second row of the aggregated data 106f is "87.5%" and the actual security rate is "42.9%". Since "actual maintenance rate (42.9%)>planned maintenance rate (50%)", which is the warning condition of "planned maintenance failure" of the warning code "101" of the warning master 106d, corresponds to "planned maintenance failure ” as a warning candidate. In addition, it corresponds to the warning condition "credit limit rate (87.5%) > 80% and credit limit rate (87.5%) ≤ 100%" of "credit limit warning" with warning code "102" in the warning master 106d. Therefore, it is extracted as a warning candidate for "credit limit warning".

The third line of the total data 106f, "XX real estate", has a credit limit rate of "115.0%" and an actual maintenance rate of "65.2%", so the warning code of the warning master 106d is "001". , the warning condition "credit limit rate (115.0%) > 100%" for "credit limit exceeded" is extracted as a warning candidate for "credit limit exceeded".

FIG. 9 is a diagram showing a form output example of warning candidates output by the warning unit 102d. The output example of the warning form shows the determination result of the warning candidate for each business partner of the group company and the breakdown of the companies that make up the group company. As for "XX commercial", since it is "unachieved planned maintenance", as countermeasures, it is conceivable to request restraint of transactions or additional security deposit. As for "XX commercial", since it is a "credit limit warning", as a countermeasure, it is conceivable to apply for change of the credit limit amount.

As for "XX real estate", since it is "exceeding the credit limit", as a countermeasure, it is conceivable to apply for transaction restraint or credit limit change. In this way, it is possible to quickly take measures to secure credit.

FIG. 10 is a diagram showing an output example summarizing warning candidates output by the warning unit 102d. In the example shown in FIG. 10, the forms in the form shown in FIG. 9 are summarized based on the number of cases.

As described above, according to the present embodiment, a unified code for uniformly identifying suppliers in the entire group is associated with individual codes for individually identifying suppliers in a plurality of subgroups. a name identification master 106b registered in the system; a warning master 106d in which warning conditions for the credit limit and the performance against the planned maintenance rate are set; data 106e, a setting unit 102a that sets the credit limit and planned maintenance rate for each business partner in the entire group, a collection unit 102b that collects the linked data 106e for each subgroup, and a name identification master on a monthly basis. With reference to 106b, monthly processing to calculate the actual results for the set credit limit and planned maintenance rate using the linked data 106e for each business partner of the entire group, which is a unified code unit linked to an individual code. section 102c, and the warning section 102d that extracts and outputs a warning candidate based on the credit limit amount and the planned maintenance rate, referring to the warning master 106d. It is possible to quickly manage credit for each business partner in the entire group.

A group consisting of multiple sub-groups includes a group company consisting of multiple companies or a company consisting of multiple divisions. It is possible to quickly perform credit management for each customer in the entire company composed of business divisions.

[4. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Or partly can be done automatically by a known method.

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

Also, with respect to the credit management system 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions of the credit management system 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment, and the credit management system as necessary. 100 mechanically read. That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving instructions to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

Also, this computer program may be stored in an application program server connected to the credit management system 100 via any network, and it is possible to download all or part of it as necessary. be.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Blu-ray (registered trademark) Disc, etc. shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single structure, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, the installation procedure after reading, and the like.

The various databases stored in the storage unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks. It stores programs, tables, databases, files for web pages, and so on.

Further, the credit management system 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 arbitrary peripheral devices are connected. Further, the credit management system 100 may be implemented by installing software (including programs, data, etc.) that implements the processing described in the present embodiment in the device.

Furthermore, the specific form of distribution and integration of the device is not limited to the one shown in the figure, and all or part of it can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

100 credit management system (credit management device)
102 Control unit 102a Setting unit 102b Collection unit 102c Monthly processing unit 102d Warning unit 104 Communication interface unit 106 Storage unit 106a Customer master 106b Name identification master 106c Credit setting master 106d Warning master 106e Cooperation data 106f Total data 108 Input/output interface unit 112 Input device 114 output device 200 server 300 network
400 accounting system

Claims (5)

A credit management device comprising a control unit and a storage unit and managing credit for each customer in an entire group composed of a plurality of subgroups,
The storage unit contains
a name identification master registered by associating a unified code for uniformly identifying the business partner in the entire group with an individual code for individually identifying the business partner in the plurality of subgroups;
A warning master that sets warning conditions for performance against the credit limit and planned maintenance rate,
Linked data collected for each of the subgroups and including the individual code and credit collateral information for the business partner;
is stored and
The control unit
setting means for setting a credit limit amount and a planned maintenance rate for each business partner in the entire group;
collecting means for collecting the linked data for each of the subgroups;
On a monthly basis, referring to the name identification master, the credit limit amount and planned maintenance rate set above are calculated using the above linked data for each business partner of the entire group, which is a unified code unit linked to the individual code. monthly processing means for calculating the actual results for
warning means for extracting and outputting a warning candidate based on the credit limit and the planned maintenance rate calculated by the monthly processing means by referring to the warning master;
A credit management device comprising: 2. The credit management apparatus according to claim 1, wherein the group consisting of a plurality of subgroups includes a group company consisting of a plurality of companies or a company consisting of a plurality of divisions. The credit/debt collateral information includes credit balance, order backlog, debt balance, and collateral amount,
The track record for the credit limit is a credit limit rate calculated by (receivable balance + order backlog) / credit limit,
3. The credit management apparatus according to claim 1, wherein the performance for the planned maintenance rate is a performance maintenance rate calculated by (debt balance + collateral amount)/(receivable balance + order backlog). . A credit management method for managing credit for each customer in an entire group composed of a plurality of subgroups, which is executed by an information processing device including a control unit and a storage unit,
The storage unit contains
a name identification master registered by associating a unified code for uniformly identifying the business partner in the entire group with an individual code for individually identifying the business partner in the plurality of subgroups;
A warning master that sets warning conditions for performance against the credit limit and planned maintenance rate,
Linked data collected for each of the subgroups and including the individual code and credit collateral information for the business partner;
is stored and
executed by the control unit;
a setting step of setting a credit limit and a planned maintenance rate for each customer across the group;
a collecting step of collecting the linked data for each of the subgroups;
On a monthly basis, referring to the name identification master, the credit limit amount and planned maintenance rate set above are calculated using the above linked data for each business partner of the entire group, which is a unified code unit linked to the individual code. a monthly processing step for calculating performance for
a warning step of referring to the warning master and extracting and outputting a warning candidate based on the credit limit and the planned maintenance rate calculated in the monthly processing step ;
A credit management method comprising: A credit management program for managing credit for each customer in an entire group composed of a plurality of subgroups, which is executed by an information processing device including a control unit and a storage unit,
The storage unit contains
a name identification master registered by associating a unified code for uniformly identifying the business partner in the entire group with an individual code for individually identifying the business partner in the plurality of subgroups;
A warning master that sets warning conditions for performance against the credit limit and planned maintenance rate,
Linked data collected for each of the subgroups and including the individual code and credit collateral information for the business partner;
is stored and
In the control unit,
a setting step of setting a credit limit and a planned maintenance rate for each customer across the group;
a collecting step of collecting the linked data for each of the subgroups;
On a monthly basis, referring to the name identification master, the credit limit amount and planned maintenance rate set above are calculated using the above linked data for each business partner of the entire group, which is a unified code unit linked to the individual code. a monthly processing step for calculating performance for
a warning step of referring to the warning master and extracting and outputting a warning candidate based on the credit limit and the planned maintenance rate calculated in the monthly processing step ;
A credit management program for executing

Images