JP7701394B2 - Claim collateral allocation device, claim collateral allocation method, and claim collateral allocation program - Google Patents

Description

The present invention relates to a claim collateral allocation device, a claim collateral allocation method, and a claim collateral allocation program.

Patent Document 1 discloses a configuration in which collateral is allocated to the claims of substantially the same customer who has been registered as a single name, in an order based on a combination of a specific root classification that classifies claims as "specific" or "root" and a good general classification that classifies claims as "good" or "general."

JP 2016-181249 A

However, the invention described in Patent Document 1 above had the problem that it was not possible to automatically allocate claims and collateral according to the type of collateral.

The present invention has been made in consideration of the above problems, and aims to provide a claim security allocation device, claim security allocation method, and claim security allocation program that can automatically allocate claims and collateral in accordance with claim security allocation rules that pre-set attributes of claims and debts, including collateral type.

In order to solve the above-mentioned problems and achieve the object, the receivable collateral allocation device of the present invention is a receivable collateral allocation device equipped with a memory unit and a control unit, the memory unit is equipped with transaction memory means for storing receivable data set by linking the receivable's industry, balance, and unallocated amount, and collateral data set by linking the receivable's industry, collateral type, collateral amount, and unallocated collateral amount, and a collateral type master set by linking the collateral type and collateral classification, and the control unit is equipped with debt allocation means for allocating the collateral data to the receivable data when the collateral data set is stored in the transaction memory means and is linked to the collateral classification based on the collateral type master.

In addition, in the receivable collateral allocation device according to the present invention, when the receivable collateral data in which the receivable type linked to the receivable classification is set based on the receivable type master and stored in the transaction storage means, and when the receivable data in which the same industry as the industry set in the receivable data is set is stored in the transaction storage means, the receivable allocation means allocates the receivable data to the same industry receivable data.

In the receivable collateral allocation device according to the present invention, when the receivable data in which the receivable type linked to the receivable classification is set based on the receivable type master and stored in the transaction storage means, and when the receivable data in which the same industry as the industry set in the receivable data is set is stored in the transaction storage means, the receivable allocation means allocates the receivable data to the same industry receivable data, and when the receivable data in which the unallocated amount is not zero is not stored in the transaction storage means, the receivable data is allocated to the remaining receivable data stored in the transaction storage means in a proportional balance manner.

In addition, in the receivable collateral allocation device according to the present invention, the receivable data is further set with a receivable number linked thereto, and when the receivable data in which the receivable type linked to the receivable classification, which is the receivable, is set based on the receivable type master and stored in the transaction storage means, the receivable allocation means allocates the receivable data to the receivable data in the order of the receivable numbers.

In the claim collateral allocation device according to the present invention, the collateral type master is further set in association with a collateral type ranking, and the control unit is further characterized by including a security measure allocation means for allocating the collateral data to the claim data according to the collateral type ranking when the collateral data in which the collateral type linked to the collateral classification, which is a security measure, is set based on the collateral type master and stored in the transaction storage means.

In the claim collateral allocation device according to the present invention, the storage unit further includes an allocation method master in which industry limitation, industry priority, and balance allocation are set as the industry allocation method for claim preservation, and the collateral data is further set in association with the industry allocation method, and the preservation measure allocation means further sets the collateral type linked to the collateral classification, which is the preservation measure, based on the collateral type master and the allocation method master, and stores the collateral data in which the industry limitation is set as the industry allocation method in the transaction storage means, and also allocates the collateral data to the same industry claim data when the same industry as the industry set in the collateral data is stored in the transaction storage means.

In the claim collateral allocation device according to the present invention, the preservation measure allocation means further allocates the collateral data to the same industry claim data when the collateral type linked to the collateral classification, which is the preservation measure, is set based on the collateral type master and the allocation method master, the industry priority is set as the industry allocation method for the collateral data stored in the transaction storage means, and the same industry claim data, which is the claim data with the same industry set as the industry set in the collateral data, is stored in the transaction storage means, and allocates the collateral data to the same industry claim data when the same industry claim data with the unallocated amount other than 0 is not stored in the transaction storage means, by balance apportionment.

In addition, in the claim collateral allocation device according to the present invention, the preservation measure allocation means is further characterized in that, when the collateral type linked to the collateral classification, which is the preservation measure, is set based on the collateral type master and the allocation method master, and the collateral data for which the balance allocation is set as the industry allocation method is stored in the transaction storage means, the preservation measure allocation means allocates the collateral data to the claim data by balance allocation.

In the claim collateral allocation device according to the present invention, the security measure allocation means is characterized in that, if the collateral data in which the collateral type linked to the collateral classification that is the debt is set based on the collateral type master and is not stored in the transaction storage means, and the collateral data in which the collateral type linked to the collateral classification that is the security measure is set is stored in the transaction storage means, the security measure allocation means allocates the collateral data to the claim data according to the collateral type ranking.

In the claim collateral allocation device according to the present invention, the collateral type master is further set with a linked haircut ratio, and the control unit is further characterized by having an insurance allocation means for allocating the collateral data to the same industry claim data according to the haircut ratio when the collateral data in which the collateral type linked to the collateral classification, which is insurance, is set based on the collateral type master and stored in the transaction storage means, and when same industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction storage means.

In the claim collateral allocation device according to the present invention, the insurance allocation means is characterized in that, based on the collateral type master, if the collateral data in which the collateral type linked to the collateral classification, which is the preservation measure, is set is not stored in the transaction storage means, the collateral data in which the collateral type linked to the collateral classification, which is the insurance, is stored in the transaction storage means, and the same-industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction storage means, the insurance allocation means allocates the collateral data to the same-industry claim data according to the margin.

In the claim collateral allocation device according to the present invention, the control unit is further characterized by having an allocation result acquisition means for acquiring an allocation result including claim collateral allocation data that sets the post-allocation collateral amount for each allocation combination of claim and collateral based on the claim data and the collateral data.

The method of claim collateral allocation according to the present invention is a method of claim collateral allocation to be executed by a claim collateral allocation device having a memory unit and a control unit, the memory unit having transaction memory means for storing claim data set by linking the industry, balance, and unallocated amount of the claim, and collateral data set by linking the industry, collateral type, collateral amount, and unallocated collateral amount of the claim, and a collateral type master set by linking the collateral type and collateral classification, and characterized in that the method includes a debt allocation step executed by the control unit, which allocates the collateral data to the claim data when the collateral data set is stored in the transaction memory means and is linked to the collateral classification that is a debt based on the collateral type master.

The receivable collateral allocation program according to the present invention is a receivable collateral allocation program to be executed by a receivable collateral allocation device having a memory unit and a control unit, the memory unit having a transaction memory means for storing receivable data set by linking the receivable's industry, balance, and unallocated amount, and collateral data set by linking the receivable's industry, collateral type, collateral amount, and unallocated collateral amount, and a collateral type master set by linking the collateral type and collateral classification, and the control unit executes a debt allocation step of allocating the collateral data to the receivable data when the collateral data set is stored in the transaction memory means and is linked to the collateral classification, which is a debt, based on the collateral type master.

The present invention has the effect of reducing the operational burden by eliminating human judgment in allocation. In addition, the present invention has the effect of improving business efficiency and strengthening the risk management system by automating the allocation of claims preservation. In addition, the present invention has the effect of sequentially allocating collateral to claims according to the master settings.

FIG. 1 is a diagram showing an example of a bond collateral allocation process according to the present embodiment. FIG. 2 is a block diagram showing an example of the configuration of a secured claim allocating device according to this embodiment. FIG. 3 is a diagram showing an example of the collateral type master in this embodiment. FIG. 4 is a diagram showing an example of the apportionment method master in this embodiment. FIG. 5 is a flowchart showing an example of the process of the bond collateral allocation device in this embodiment. FIG. 6 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 7 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 8 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 9 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 10 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 11 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 12 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 13 is a diagram showing an example of the bond collateral allocation process in this embodiment. FIG. 14 is a diagram showing an example of the bond collateral allocation process in this embodiment.

An embodiment of 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. Overview]
First, an overview of the present invention will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a bond collateral allocation process in this embodiment.

Previously, when financial institutions provided loans to customers, they would allocate collateral to the receivables and avoid and identify the risk of default by allocating the receivables to collateral. In this process, risk receivables were identified by multiplying the amount of collateral allocated to the receivables by a separately set debtor classification (normal/at risk of bankruptcy, etc.). In the past, allocation of receivables to collateral, setting of debtor classifications, and identification of risk receivables were often incorporated into a system as part of the business operations, and the allocation settings were done manually within the system. In addition, traditionally, trading companies have generally treated "accounts receivable" that are expected to be collected (repaid) in the future from business partners as claims, and "accounts payable" that will need to be paid in the future, and "insurance" that is taken out on claims (accounts receivable), as collateral. However, there are unique allocation priorities (which collateral is given priority) for the allocation of claims and collateral, and rules are also established that limit the claims that can be allocated depending on the type of collateral (accounts payable, insurance, etc.). This requires advanced knowledge of allocation judgment, and operators often make incorrect allocations, which has the effect of making it difficult to accurately grasp risk claims in subsequent tasks.

Therefore, in this embodiment, in order to contribute to the achievement of accurate risk assessment, a mechanism is provided that automatically completes the allocation of claims and collateral according to pre-set master data.

As shown in FIG. 1, in this embodiment, a security allocation process is performed for each customer's receivables. Note that security allocation in this embodiment is only performed within the same customer, and allocation to receivables across customers is not performed (customers with different trading partner codes are matched with the same person, and customers with the same matched name are allocated). Also, in this embodiment, when receivables are held by the same customer in the same industry but with different loan items or business locations, each security allocation may be performed by prorating the unsecured balance at the time of allocation.

In other words, as shown in FIG. 1, in this embodiment, collateral is allocated to claims in the same industry as the debt, and unallocated debt is allocated to the claims in proportion to the balance of the remaining unsecured claims (step SA-1).

As shown in FIG. 1, in this embodiment, collateral is allocated to claims in accordance with the industry apportionment method (step SA-2). Here, the priority order of allocation of security measures in this embodiment may be "security measure type" > "industry apportionment method" > "business establishment code" > "collateral guarantee number". Furthermore, the "security measure type" may include, in order of priority, "1. Trade guarantee", "2. Bank guarantee", "3. Fixed term deposit", "4. Securities", "5. Revolving guarantee", "6. Joint guarantee", "7. Real estate", and "8. Other".

The "industry allocation method" may include "1. Industry limited", which allocates only to claims of the same establishment and industry, "2. Industry priority", which allocates preferentially to claims of the same establishment and industry and allocates the balance of unallocated debt to unsecured claims, and "3. Balance allocation", which allocates the unsecured balance. Here, "1. Industry limited" allocates only to claims of the same industry as the industry of the preservation measure, and if the amount of preservation is greater than the amount of the claim, the amount of preservation that exceeds the amount of the claim is not considered as preservation (claims cannot be collected from other industries: not allocated to claims of other industries, etc.). Also, "2. Industry priority" allocates to claims of the same industry as the industry of the preservation measure, and the amount of preservation that exceeds the amount of the claim is allocated to claims of other industries by preservation balance apportionment. The industry allocation method for the transaction guarantee money to be linked to the data may be industry priority. In addition, "3. Pro rata Allocation of Balance" is allocated to all claims that have unsecured amounts. Here, the allocation amount is the pro rata allocation of the unsecured balance at the time of allocation, and is allocated without any consideration of the prioritized industry.

As shown in FIG. 1, in this embodiment, the collateral is allocated to the receivables in accordance with the industry allocation method of "1. Industry Restriction" (step SA-3). Here, in this embodiment, the insurance collateral for each collateral rate is selected on the collateral guarantee input screen by setting the collateral type master, and the collateral rate set in advance in the master is referenced according to the linked collateral type, and the collateral amount is allocated in proportion to the unsecured amount at the time of the insurance security allocation process. Note that the collateral type master can be added, modified, or deleted by the user, and if a collateral rate is to be added, it is added to the collateral type master and the desired rate is set.

In this embodiment, the allocation calculation or classification amount calculation may be performed during monthly night processing, when the registration button on the claim details input screen is pressed, when the deletion button on the claim details list screen is pressed, or when the registration button on the collateral guarantee input screen is pressed. Also, in this embodiment, the calculation process is not performed when claim data is linked on a daily basis.

2. Configuration
An example of the configuration of the secured claim allocating device 100 according to this embodiment will be described with reference to Fig. 2 to Fig. 4. Fig. 2 is a block diagram showing an example of the configuration of the secured claim allocating device 100 according to this embodiment.

As shown in FIG. 2, the secured claim allocation device 100 is a commercially available desktop personal computer. Note that the secured claim allocation 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 secured claim allocation device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the secured claim allocation 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 secured claim allocation 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 secured claim allocation 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).

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 touch panel), 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 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 records computer programs that work with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The memory 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, or an optical disk. The memory unit 106 includes a transaction database 106a, a collateral type master 106b, and an allocation method master 106c.

The transaction database 106a stores transaction data. Here, the transaction data may include customer data, name data, claim data, same industry claim data, security data, and claim security allocation data. Furthermore, the transaction database 106a may store claim data that is set by linking the industry (type) of claim, the balance, and the unallocated amount, as well as security data that is set by linking the industry of claim, the security type, the security amount, and the unallocated security amount. Here, the claim data may be set by linking it to the claim number. Furthermore, the security data may be set by linking it to the industry apportionment method.

The collateral type master 106b is a master that links and sets the collateral type and the collateral classification. Here, the collateral type master 106b may be linked and set with the collateral type ranking. The collateral type master 106b may also be linked and set with the margin.

Here, an example of the collateral type master 106b in this embodiment will be described with reference to FIG. 3. FIG. 3 is a diagram showing an example of the collateral type master 106b in this embodiment.

As shown in FIG. 3, in this embodiment, the collateral type master 106b is configured to link the collateral type, collateral classification, and the margin.

Returning to FIG. 2, the allocation method master 106c is a master that sets the industry allocation method for claim preservation. Here, the allocation method master 106c may set industry restriction, industry priority, and balance allocation as the industry allocation method for claim preservation.

Here, an example of the allocation method master 106c in this embodiment will be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the allocation method master 106c in this embodiment.

As shown in FIG. 4, the allocation method master 106c in this embodiment may be a code master in which the industry allocation method for claim preservation is set.

Returning to FIG. 2, the control unit 102 is a CPU or the like that provides overall control of the secured claim allocation device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs. In terms of functional concept, the control unit 102 includes a registration unit 102a, a debt allocation unit 102b, a conservation measure allocation unit 102c, an insurance allocation unit 102d, and an allocation result acquisition unit 102e.

The registration unit 102a registers various data including transaction data. Here, the registration unit 102a may register the transaction data in the transaction database 106a. The registration unit 102a may also perform master setting.

The debt allocation unit 102b allocates the collateral data in which the collateral type linked to the collateral classification, which is the debt, is set to the debt data. Here, when the collateral data in which the collateral type linked to the collateral classification, which is the debt, is set based on the collateral type master 106b, is stored in the transaction database 106a, the debt allocation unit 102b may allocate the collateral data to the debt data. In addition, when the collateral data in which the collateral type linked to the collateral classification, which is the debt, is set based on the collateral type master 106b, is stored in the transaction database 106a, and the same industry debt data, which is the debt data in which the industry set to the same industry as the industry set to the collateral data, is stored in the transaction database 106a, the debt allocation unit 102b may allocate the collateral data to the same industry debt data. In addition, when collateral data in which a collateral type linked to a collateral classification, which is a debt, is set based on the collateral type master 106b and same-industry claim data, which is claim data in which the same industry as the industry set in the collateral data is set, is stored in the transaction database 106a, the debt allocation unit 102b may allocate the collateral data to the same-industry claim data, and when the same-industry claim data in which the unallocated amount is not 0 is not stored in the transaction database 106a, the debt allocation unit 102b may allocate the collateral data to the remaining claim data stored in the transaction database 106a in a balance apportionment manner. In addition, when collateral data in which a collateral type linked to a collateral classification, which is a debt, is stored in the transaction database 106a based on the collateral type master 106b, the debt allocation unit 102b may allocate the collateral data to the claim data in order of claim number.

The preservation measure allocation unit 102c allocates the security data in which the security type linked to the security classification, which is the preservation measure, is set to the claim data. Here, when the security data in which the security type linked to the security classification, which is the preservation measure, is set based on the security type master 106b, is stored in the transaction database 106a, the preservation measure allocation unit 102c may allocate the security data to the claim data according to the security type ranking. In addition, when the security data in which the security type linked to the security classification, which is the preservation measure, is set based on the security type master 106b and the allocation method master 106c, and the industry limitation is set as the industry allocation method, is stored in the transaction database 106a, the preservation measure allocation unit 102c may allocate the security data to the same industry claim data in which the industry set in the security data is set. In addition, the preservation measure allocation unit 102c may allocate the collateral data to the same industry claim data when a collateral type linked to a collateral classification, which is a preservation measure, is set based on the collateral type master 106b and the allocation method master 106c, and when collateral data in which industry priority is set as the industry allocation method is stored in the transaction database 106a, and when same industry claim data, which is claim data in which the same industry as the industry set in the collateral data, is set, is stored in the transaction database 106a, the preservation measure allocation unit 102c may allocate the collateral data to the same industry claim data, and when no same industry claim data in which the unallocated amount is not zero is stored in the transaction database 106a, the collateral data to the remaining claim data stored in the transaction database 106a by balance apportionment. In addition, when a collateral type linked to a collateral classification that is a security measure is set based on the collateral type master 106b and the allocation method master 106c, and when collateral data for which balance allocation is set as the industry allocation method is stored in the transaction database 106a, the security measure allocation unit 102c may allocate the collateral data to the receivable data by balance allocation. In addition, when collateral data for which a collateral type linked to a collateral classification that is a debt is set based on the collateral type master 106b, and when collateral data for which a collateral type linked to a collateral classification that is a security measure is set is stored in the transaction database 106a, the security measure allocation unit 102c may allocate the collateral data to the receivable data according to the collateral type ranking.

The insurance allocation unit 102d allocates the collateral data in which the collateral type linked to the collateral classification, which is insurance, is set to the claim data. Here, when the collateral data in which the collateral type linked to the collateral classification, which is insurance, is set based on the collateral type master 106b, is stored in the transaction database 106a, and the same industry claim data, which is the claim data in which the industry type set to the collateral data is set, is stored in the transaction database 106a, the insurance allocation unit 102d may allocate the collateral data to the same industry claim data according to the margin. Also, when the collateral data in which the collateral type linked to the collateral classification, which is a conservation measure, is not stored in the transaction database 106a, the collateral data in which the collateral type linked to the collateral classification, which is insurance, is stored in the transaction database 106a, and the same industry claim data, which is the claim data in which the industry type set to the collateral data is set, is stored in the transaction database 106a, the insurance allocation unit 102d may allocate the collateral data to the same industry claim data according to the margin.

The allocation result acquisition unit 102e acquires the allocation result. Here, the allocation result acquisition unit 102e may acquire the allocation result including claim collateral allocation data that sets the post-allocation collateral amount for each allocation combination of claim and collateral based on the claim data and the collateral data. The allocation result acquisition unit 102e may also output (display or print out) the allocation result.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Credit security allocation processing]
An example of the bond collateral allocation process in this embodiment will now be described with reference to Fig. 5. Fig. 5 is a flow chart showing an example of the process of the bond collateral allocation device 100 in this embodiment.

As shown in FIG. 5, the debt allocation unit 102b determines, based on the collateral type master 106b, whether or not collateral data in which a collateral type linked to a collateral classification that is a debt is set is stored in the transaction database 106a (step SB-1).

If the debt allocation unit 102b determines that collateral data in which a collateral type linked to the debt collateral classification is set is not stored in the transaction database 106a (step SB-1: No), it transitions the process to step SB-3.

On the other hand, if the debt allocation unit 102b determines that collateral data in which a collateral type linked to the debt collateral classification is set is stored in the transaction database 106a (step SB-1: Yes), it transitions the process to step SB-2.

Then, based on the collateral type master 106b, if same-industry claim data, which is claim data set with the same industry as the industry set in the collateral data set with the collateral type linked to the collateral classification that is the debt, is stored in the transaction database 106a, the debt allocation unit 102b allocates the collateral data to the same-industry claim data, and if there is no same-industry claim data with an unallocated amount other than 0 stored in the transaction database 106a after allocation, the debt allocation unit 102b allocates the collateral data to the remaining claim data stored in the transaction database 106a in proportion to the balance (step SB-2).

Then, the security measure allocation unit 102c determines, based on the collateral type master 106b, whether collateral data in which a collateral type linked to a collateral classification that is a security measure is set is stored in the transaction database 106a (step SB-3).

Then, if the security measure allocation unit 102c determines that collateral data in which a collateral type linked to a security measure, which is a collateral classification, is set is not stored in the transaction database 106a (step SB-3: No), it transitions the process to step SB-5.

On the other hand, if the security measure allocation unit 102c determines that collateral data in which a collateral type linked to a security measure, which is a collateral classification, is set is stored in the transaction database 106a (step SB-3: Yes), it transitions the process to step SB-4.

Then, the preservation measure allocation unit 102c allocates the collateral data in which the collateral type linked to the collateral classification, which is the preservation measure, is set to the claim data (step SB-4).

Then, based on the collateral type master 106b, the insurance allocation unit 102d determines whether collateral data in which a collateral type linked to the collateral classification, which is insurance, is set is stored in the transaction database 106a, and whether same-industry claim data, which is claim data in which the same industry as the industry set in the collateral data is set, is stored in the transaction database 106a (step SB-5).

Then, if the insurance allocation unit 102d determines that the collateral data in which the collateral type linked to the collateral classification, which is insurance, is set is not stored in the transaction database 106a, or that the same industry claim data in which the same industry as the industry set in the collateral data is set is not stored in the transaction database 106a (step SB-5: No), the processing proceeds to step SB-7.

On the other hand, if the insurance allocation unit 102d determines that collateral data in which a collateral type linked to a collateral classification that is insurance is set is stored in the transaction database 106a, and that same-industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction database 106a (step SB-5: Yes), it transitions the process to step SB-6.

Then, based on the collateral type master 106b, the insurance allocation unit 102d allocates the collateral data in which the collateral type linked to the collateral classification, which is insurance, to the same industry bond data according to the margin (step SB-6).

Then, the allocation result acquisition unit 102e acquires the allocation result including the claim collateral allocation data that sets the post-allocation collateral amount for each allocation combination of claim and collateral based on the claim data and collateral data stored in the transaction database 106a (step SB-7), and ends the process.

Here, an example of the secured claim allocation process in this embodiment will be described with reference to Figures 6 to 14. Figures 6 to 14 are diagrams showing an example of the secured claim allocation process in this embodiment.

As shown in FIG. 6, in this embodiment, the customer data of the customer and the name data that sets the range of entities (subsidiaries, etc.) that are considered to be the same customer are registered in the transaction database 106a when the user inputs a customer summary, the claim data of the claim linked to the customer is registered in the transaction database 106a when the user inputs the claim details, and the collateral data of the collateral linked to the customer is registered in the transaction database 106a when the user inputs the collateral guarantee.

As shown in FIG. 7, in this embodiment, automatic allocation of claims and collateral is performed as a batch process in accordance with the allocation rules. That is, as shown in FIG. 7, in this embodiment, collateral data of the collateral classification, which is a debt, is allocated to claims in the same industry as the debt. Here, as shown in FIG. 7, in this embodiment, the claim data with claim number: 5 is in the same industry as the claim data with claim number: 1, but allocation is performed in the order of claim numbers, starting with the claim data with claim number: 1. As shown in FIG. 8, in this embodiment, since there is a remainder in the unallocated collateral amount set in the collateral data, automatic allocation is also applied to the claim data with claim number: 5, which is in the same industry as the claim data with claim number: 1.

As shown in FIG. 9, in this embodiment, the security data of the security classification, which is a preservation measure, is assigned to the claim data by industry restriction. That is, as shown in FIG. 9, in this embodiment, the security data of security number 1 is assigned to the claim data of claim number 5 by industry restriction. As shown in FIG. 10, in this embodiment, the security data of security number 3 is assigned to the claim data of claim number 3 by industry priority. As shown in FIG. 11, in this embodiment, the security data of security number 4 is assigned to the claim data of claim numbers 2-5, which have unallocated amounts, by balance allocation. As shown in FIG. 12, in this embodiment, the security data of security number 2 is assigned to the claim data of claim number 5 of the same industry by industry priority, but as a result of the search by industry/business establishment, there is no relative claim, so the remaining security data of security number 2 is assigned to the claim data of claim numbers 2-5, which have unallocated amounts, by balance allocation.

And, as shown in FIG. 13, in this embodiment, the collateral data with collateral number 5 in the insurance collateral classification is assigned to the collateral data with collateral number 3 in the same industry.

As shown in FIG. 14, in this embodiment, the automatic claim collateral allocation result is obtained, which includes the claim data after allocation, the collateral data after allocation, and the claim collateral allocation data in which the post-allocation collateral amount is set for each combination of claim and collateral.

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

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

In addition, with regard to the secured claim allocation 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 secured claim allocation 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 secured claim allocation 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. The 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 secured claim allocation device 100 via any network, and may be downloaded in whole or in part 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 Blu-ray (registered trademark) Disc, and a 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 website provision.

The secured claim allocation 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 secured claim allocation device 100 may also 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.

The present invention is useful not only in the financial industry, but also in the trading industry, which does business with a variety of business companies and needs to understand the risks posed by its business partners, as well as in industries such as the wholesale and manufacturing industries, which place importance on credit management operations.

REFERENCE SIGNS LIST 100 Claim security allocation device 102 Control unit 102a Registration unit 102b Debt allocation unit 102c Security measure allocation unit 102d Insurance allocation unit 102e Allocation result acquisition unit 104 Communication interface unit 106 Storage unit 106a Transaction database 106b Security type master 106c Allocation method master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (14)

A claim collateral allocation device comprising a memory unit and a control unit,
The storage unit is
a transaction storage means for storing claim data that is set by linking the business type, balance, and unallocated amount of a claim, and security data that is set by linking the business type, security type, security amount, and unallocated security amount of the claim;
A collateral type master that associates the collateral type and the collateral classification;
Equipped with
The control unit is
a debt allocation means for allocating the security data to the claim data when the security data, in which the security type linked to the security classification, which is a debt, is set based on the security type master, is stored in the transaction storage means;
A claim collateral allocation device comprising: The debt allocation means includes:
The claim collateral allocation device described in claim 1, characterized in that when the collateral data in which the collateral type linked to the collateral classification of the debt is set based on the collateral type master is stored in the transaction memory means, and when same-industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction memory means, the collateral data is allocated to the same industry claim data. The debt allocation means includes:
A claim collateral allocation device as described in claim 2, characterized in that when the collateral data in which the collateral type linked to the collateral classification of the debt is set based on the collateral type master is stored in the transaction memory means, and when the same industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction memory means, the collateral data is allocated to the same industry claim data, and when the same industry claim data in which the unallocated amount is not zero is not stored in the transaction memory means, the collateral data is allocated to the remaining claim data stored in the transaction memory means in a balance pro rata manner. The bond data is
In addition, the bond number is linked and set,
The debt allocation means includes:
The claim collateral allocation device described in claim 1, characterized in that when the collateral data in which the collateral type linked to the collateral classification of the debt is set based on the collateral type master is stored in the transaction memory means, the collateral data is allocated to the claim data in order of the claim number. The collateral type master data includes:
In addition, the priority of collateral types is set in a linked manner.
The control unit is
a security measure allocation means for allocating the security data to the claim data in accordance with the security type ranking when the security data in which the security type linked to the security classification, which is a security measure, is set based on the security type master in the transaction storage means;
2. The claim collateral allocation device according to claim 1, further comprising: The storage unit is
As the industry apportionment method for credit preservation, an apportionment method master that sets industry restriction, industry priority, and balance apportionment,
Further comprising:
The security data includes
Furthermore, the industry apportionment method is set in a linked manner,
The security measure allocation means includes:
Further, the claim collateral allocation device as described in claim 5 is characterized in that, based on the collateral type master and the allocation method master, the collateral type linked to the collateral classification, which is the preservation measure, is set, and the collateral data in which the industry limitation is set as the industry allocation method is stored in the transaction memory means, and in addition, when same-industry claim data, which is the claim data in which the same industry as the industry set in the collateral data, is set, the collateral data is allocated to the same industry claim data. The security measure allocation means
The claim collateral allocation device as described in claim 6, further characterized in that, when the collateral type linked to the collateral classification, which is the preservation measure, is set based on the collateral type master and the allocation method master, and the collateral data in which the industry priority is set as the industry allocation method is stored in the transaction storage means, and when same-industry claim data, which is the claim data in which the same industry as the industry set in the collateral data, is stored in the transaction storage means, the collateral data is allocated to the same-industry claim data, and when the same-industry claim data in which the unallocated amount is not zero is not stored in the transaction storage means, the collateral data is allocated to the remaining claim data stored in the transaction storage means by balance apportionment. The security measure allocation means
The claim collateral allocation device of claim 6 further comprises a collateral type that is linked to the collateral classification, which is the preservation measure, based on the collateral type master and the allocation method master, and when the collateral data in which the balance allocation is set as the industry allocation method is stored in the transaction memory means, the collateral data is allocated to the claim data by balance allocation. The security measure allocation means
The claim collateral allocation device described in claim 5, characterized in that if the collateral data in which the collateral type linked to the collateral classification which is the debt is set based on the collateral type master is not stored in the transaction memory means, and the collateral data in which the collateral type linked to the collateral classification which is the conservation measure is stored in the transaction memory means, the collateral data is allocated to the claim data according to the collateral type ranking. The collateral type master data includes:
Furthermore, the hook thread is set in a linked manner,
The control unit is
an insurance allocation means for allocating the collateral data to the same industry claim data according to the premium rate when the collateral data in which the collateral type linked to the collateral classification, which is insurance, is set based on the collateral type master and stored in the transaction storage means, and when same industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction storage means;
6. The claim collateral allocation device according to claim 5, further comprising: The insurance allocation means includes:
The claim collateral allocation device described in claim collateral allocation claim, characterized in that if, based on the collateral type master, the collateral data in which the collateral type linked to the collateral classification which is the conservation measure is set is not stored in the transaction memory means, and the collateral data in which the collateral type linked to the collateral classification which is the insurance is set is stored in the transaction memory means, and the same industry claim data in which the same industry as the industry set in the collateral data is set is stored in the transaction memory means, the collateral data is allocated to the same industry claim data in accordance with the haircut rate. The control unit is
an allocation result acquisition means for acquiring an allocation result including claim security allocation data in which a post-allocation security amount is set for each allocation combination of claim and security based on the claim data and the security data;
12. The claim collateral allocation device according to claim 1, further comprising: A method for allocating collateral to a claim to be executed by a collateral allocation device having a memory unit and a control unit, comprising:
The storage unit is
a transaction storage means for storing claim data that is set by linking the business type, balance, and unallocated amount of a claim, and security data that is set by linking the business type, security type, security amount, and unallocated security amount of the claim;
A collateral type master that associates the collateral type and the collateral classification;
Equipped with
Executed in the control unit:
a debt allocation step of allocating the security data to the claim data when the security data in which the security type linked to the security classification, which is a debt, is set based on the security type master and is stored in the transaction storage means;
A method for allocating collateral to a claim, comprising: A bond collateral allocation program to be executed by a bond collateral allocation device having a memory unit and a control unit,
The storage unit is
a transaction storage means for storing claim data that is set by linking the business type, balance, and unallocated amount of a claim, and security data that is set by linking the business type, security type, security amount, and unallocated security amount of the claim;
A collateral type master that associates the collateral type and the collateral classification;
Equipped with
In the control unit,
a debt allocation step of allocating the security data to the claim data when the security data in which the security type linked to the security classification, which is a debt, is set based on the security type master and is stored in the transaction storage means;
A bond collateral allocation program for executing the above.

Images