JP7768940B2 - Debt management device, debt management method, and debt management program - Google Patents

Description

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

Patent Document 1 discloses a receivables liquidation system that quickly and accurately completes a series of liquidation procedures, including processes such as receivables price adjustments following receivables cancellation, etc.

Japanese Patent Application Laid-Open No. 2005-309697

In accounts receivable management operations, transactions between creditors (individuals, companies, etc. that hold accounts receivable) and debtors may result in updates (transaction updates) to data related to the customer debtor or all accounts receivable linked to a specific contract. For example, a creditor may conduct a transaction with a customer debtor and reach a settlement for all of the customer's accounts receivable, and the accounts receivable management operations will then process the settlement and update the data related to the relevant accounts receivable. In addition, a creditor may write off or accelerate all accounts receivable under a specific contract with the debtor, and the accounts receivable management operations will then process the data related to the relevant accounts receivable and accelerate the credit. In the event of transactions involving multiple accounts receivable as described above, it is possible to automatically process updates to the data related to the relevant accounts receivable in bulk. On the other hand, if the transaction update process (for example, settlement) is canceled due to a violation of the settlement terms, etc., in the accounts receivable management process, it is essential that the cancellations be performed in order, starting with the most recent transaction. This requires the staff member to select the data related to all accounts receivable for which the transaction update process (for example, settlement) was performed, cancel the data related to the selected accounts receivable (transaction cancellation), and revert to the data before the transaction update process (for example, before settlement). When there are many accounts receivable, this increases the staff member's workload, and there is a risk that accounting coordination, foreign currency reporting, etc. will be carried out with incorrect information due to processing omissions.

The present invention has been made in consideration of the above, and aims to provide a receivables management device, receivables management method, and receivables management program that classifies and manages receivables by transaction type, enabling automatic data updating for all data linked to the relevant receivables in one go, thereby improving operational efficiency and reducing the risk of processing omissions.

In order to solve the above-mentioned problems and achieve the object, the claims management device of the present invention includes a claims extraction unit that extracts the transaction type included in claims data designated by a person in charge from claims data including transaction date, claim amount, transaction type, processing sequence number management identification information set in order based on the transaction date and the transaction type, and claim identification information of claims that have been processed corresponding to each of the processing sequence number management identification information; and a batch processing target unit that references a transaction type master that stores, for each transaction type of claims, a batch processing target classification that indicates whether the transaction type is a transaction type that is subject to batch processing, and obtains a batch processing target classification that corresponds to the extracted transaction type. The device is characterized by comprising a classification acquisition unit, a batch processing claims extraction unit which, when the classification to be processed in a batch acquired by the batch processing target classification acquisition unit indicates that the classification to be processed in a batch is the target of batch processing, extracts claims data from the claims data that has the same processing serial number management identification information as the processing serial number management identification information included in the claims data specified by the person in charge, and a batch data processing unit which collectively performs data processing corresponding to the claims data or each of the related data on each of the claims data extracted by the claims extraction unit and each of the related data that has the same claims identification information as each of the claims data extracted by the claims extraction unit .

In addition, in the debt management device of the present invention, the debt data is debt transaction history data showing the transaction history of the debt, the related data is debt log data including the debt recorded amount or waived amount, debt history data including the debt recorded amount, and latest debt data including the debt recorded amount, and the bulk data processing unit generates new debt log data by subtracting the debt recorded amount or the waived amount in the debt log data, deletes each of the debt data extracted by the debt extraction unit, that is, the debt transaction history data, the debt history data, and the latest debt data, and performs data processing in a batch to generate the latest debt history data of the debt identification information of the deleted debt history data as new latest debt data .

Furthermore, in the claim management device according to the present invention, the related data includes the first data, the fourth data, and the fifth data, and the data deletion/update unit references the first data to delete and update the first data including the claim identification information and the transaction history serial number management identification information corresponding to the claim data, references the fourth data to delete and update the fourth data including the claim identification information and the claim history serial number management identification information corresponding to the claim data, and references the fifth data to delete and update the fifth data including the claim identification information corresponding to the claim data.

In addition, in the claims management device of the present invention, the bulk data processing unit compares the processing history identification information contained in the claims data specified by the person in charge with the processing history identification information contained in the claims data extracted by the bulk processing claims extraction unit, selects the claims data with the largest value of the processing history identification information, and starts the data processing from the selected claims data, and further, after generating the new latest claims data, checks the claims data extracted by the claims extraction unit and the claims data extracted by the bulk processing claims extraction unit, and if processing of all of the claims data has not been completed, compares the processing history identification information of the claims data extracted by the claims extraction unit again with the processing history identification information of the claims data extracted by the bulk processing claims extraction unit, excluding the claims data from which the new latest claims data was generated, selects the claims data with the largest value of the processing history identification information, and starts the data processing from the selected claims data.

In addition, in the claims management device of the present invention, the bulk data processing unit, before processing the data, acquires the maximum value of the processing history identification information linked to the claims identification information contained in the claims data specified by the person in charge, and confirms whether it matches the value of the processing history identification information of the claims data specified by the person in charge , and after completing the confirmation, if the bulk processing target category acquisition unit indicates that the bulk processing target category acquired is subject to bulk processing, it confirms whether the claims data from the claims data having the same processing sequence number management identification information as the processing sequence number management identification information contained in the claims data specified by the person in charge has been extracted by the bulk processing claims extraction unit .

In addition, in the receivables management device of the present invention, the receivables extraction unit refers to the receivables data stored in the memory unit, extracts receivables data linked to the customer specified on the transaction cancellation screen for executing the transaction cancellation process , and is provided with a first output control unit that selectably outputs the extracted receivables data on the transaction cancellation screen , and the batch processing receivables extraction unit refers to the receivables data stored in the memory unit and displays the receivables data including the processing sequence number management identification information extracted by the receivables extraction unit in a selected manner on the transaction cancellation screen.

Furthermore, in the claim management device according to the present invention, the claims in the claim data are monetary claims.

Furthermore, the claim management method of the claim management device according to the present invention includes a claim extraction step in which a claim extraction unit extracts a transaction type included in claim data designated by a person in charge from claim data including transaction date, transaction amount, transaction type, processing sequence number management identification information set in order based on the transaction date and the transaction type, and claim identification information of claims that have been processed corresponding to each of the processing sequence number management identification information; and a lump-processing target classification acquisition unit references a transaction type master in which lump-processing target classifications indicating whether or not a transaction type is a transaction type that is subject to lump-processing are stored for each transaction type of claim, and acquires a lump-processing target classification corresponding to the extracted transaction type. The method includes a classification acquisition step, a classification extraction step in which, when the classification acquisition unit for classification to be processed in a lump sum indicates that the classification to be processed in a lump sum is a classification to be processed in a lump sum, the classification extraction unit for processing in a lump sum extracts, from the classification data, classification data having the same processing sequence number management identification information as the classification data specified by the person in charge, and a classification processing step in which the classification processing unit performs data processing corresponding to the classification data or each of the related data in a lump sum on each of the classification data and each of the related data having the same classification information as the classification data extracted by the classification extraction unit.

In addition, the claims management program of the present invention causes a computer to function as: a claims extraction unit that extracts the transaction type included in claims data specified by a person in charge from claims data including transaction date, transaction amount, transaction type, processing sequence number management identification information set in order based on the transaction date and transaction type, and claim identification information of claims that have been processed corresponding to each of the processing sequence number management identification information; a batch processing target category acquisition unit that references a transaction type master in which, for each transaction type of claims, a batch processing target category indicating whether the transaction type is subject to batch processing is stored, and acquires the batch processing target category corresponding to the extracted transaction type; a batch processing claims extraction unit that, when the batch processing target category acquired by the batch processing target category acquisition unit indicates that the batch processing is subject to batch processing, extracts from the claims data those claims data that have the same processing sequence number management identification information as the processing sequence number management identification information included in the claims data specified by the person in charge; and a batch data processing unit that collectively performs data processing corresponding to each of the claims data extracted by the claims extraction unit and each of the related data that is assigned the same claim identification information as each of the claims data extracted by the claims extraction unit.

By classifying and managing receivables by transaction type, the present invention enables automatic data updating of all data linked to all relevant receivables at once, thereby improving operational efficiency and reducing the risk of processing omissions.

FIG. 1 is a diagram showing an example of the configuration of a business support device according to this embodiment. FIG. 2 is a diagram showing an example of bond transaction history data according to this embodiment. FIG. 3 is a diagram showing an example of the latest bond data according to this embodiment. FIG. 4 is a diagram showing an example of the credit history data according to this embodiment. FIG. 5 is a diagram showing an example of the bond log data according to this embodiment. FIG. 6 is a diagram showing an example of contract data according to this embodiment. FIG. 7 is a diagram showing an example of customer data according to this embodiment. FIG. 8 is a diagram showing an example of the transaction type master according to this embodiment. FIG. 9 is a diagram showing an example of the transaction content master according to this embodiment. FIG. 10 is a diagram showing an example of data before the execution of processing, for explaining a specific example of processing in this embodiment. FIG. 11 is a diagram showing an example of a screen for explaining a specific example of processing in this embodiment. FIG. 12 is a diagram showing an example of a screen for explaining a specific example of processing in this embodiment. FIG. 13 is a diagram showing an example of a screen and an example of a master for explaining a specific example of processing in this embodiment. FIG. 14 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. FIG. 15 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. FIG. 16 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. FIG. 17 is a diagram showing an example of data after processing is performed, for explaining a specific example of processing in this embodiment.

Embodiments of a debt management device, debt management method, and debt management program according to the present invention are described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[1. Configuration]
An example of the configuration of a business support device 100 according to this embodiment (including the debt management device of the present invention) will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the business support device 100.

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

The business assistance device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the business assistance device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the business support 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 the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the business support 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). Note that the data stored in the memory unit 106 may also be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, 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 computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk.

The memory unit 106 stores bond transaction history data 106a (corresponding to the first data of the present invention), latest bond data 106b (corresponding to the fifth data of the present invention), bond history data 106c (corresponding to the fourth data of the present invention), bond log data 106d (corresponding to the third data of the present invention), contract data 106e, customer data 106f, transaction type master 106g (corresponding to the second master of the present invention), and transaction content master 106h, etc.

As shown in Figure 2, the bond transaction history data 106a holds a snapshot of information related to bond transactions at the time of the transaction history serial number management identification information (transaction history SEQ) that manages the transaction history for each bond identification information (bond ID) used to identify the bond. The bond transaction history data 106a stores bond identification information (e.g., bond ID, etc.), transaction history serial number management identification information that manages the bond transaction history (e.g., transaction history SEQ, etc.), bond history serial number management identification information that manages the bond history (e.g., bond history SEQ, etc.), transaction type identification information that identifies the transaction type (e.g., transaction type code), transaction content identification information (e.g., transaction content code), transaction date, transaction amount, customer identification information (e.g., customer ID, etc.), contract identification information (e.g., contract ID, etc.), processing serial number management identification information that identifies the bond processing (e.g., processing SEQ, etc.), and bond processing history identification information (e.g., bond log ID, etc.).

As shown in Figure 3, the latest claim data 106b holds the latest data for each claim identification information (claim ID). The latest claim data 106b stores the claim identification information, claim history serial number management identification information, claim accounting date, claim accounting amount, settlement classification (e.g., settlement flag, etc.) that distinguishes whether or not the claim is settled, and new claim identification information newly assigned to the claim (e.g., new claim ID, etc.).

As shown in Figure 4, the claim history data 106c holds a snapshot of claim information at the time of the claim history serial number management identification information (claim history SEQ) for each claim identification information (claim ID). The claim history data 106c stores the claim identification information, claim history serial number management identification information, claim accounting date, claim accounting amount, settlement classification, new claim identification information, etc.

As shown in Figure 5, the receivables log data 106d is used to sequentially record receivables processing (including cancellation processing) and add and manage data. The receivables log data 106d stores processing history identification information, transaction cancellation classification (e.g., transaction cancellation flag, etc.) that distinguishes whether or not a transaction is canceled, processing history identification information that was the source of the transaction cancellation processing (e.g., transaction cancellation source receivables log ID, etc.), receivables identification information, transaction history serial number management identification information, receivables history serial number management identification information, transaction type identification information, transaction content identification information, transaction date, transaction amount, receivables amount recorded, amount received, amount appropriated, amount waived, etc.

Contract data 106e, as shown in Figure 6, is used to manage contracts. Contract data 106e stores contract identification information, customer identification information, etc.

Customer data 106f, as shown in Figure 7, is used to manage customers. Customer data 106f stores customer identification information and customer names.

As shown in Figure 8, the transaction type master 106g is used to manage transaction types. The transaction type master 106g stores transaction type identification information, transaction type name, and cancellation unit classification (e.g., processing sequence number unit cancellation flag) that distinguishes whether or not to execute cancellation processing in units of processing sequence number management identification information.

The transaction content master 106h, as shown in Figure 9, is used to manage transaction content. The transaction content master 106h stores transaction content identification information, transaction type name, etc.

Returning to Figure 1, the control unit 102 is a CPU or the like that provides overall control of the business assistance device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

In terms of functional concept, the control unit 102 comprises a history output unit 102a (including the first output control unit of the present invention) and a transaction cancellation processing unit 102b (including the claims extraction unit, batch processing target category acquisition unit, batch processing claims extraction unit, data update unit, third data update unit, data deletion update unit, data addition update unit, and second output control unit of the present invention).

The history output unit 102a prompts the user to specify a customer ID in area MA1 of the transaction cancellation screen MA and press the display button MA2 (see Figure 11). The history output unit 102a then references the bond transaction history data 106a, extracts records linked to the specified customer ID, displays them selectably in area MA3 of the transaction cancellation screen MA in ascending order of bond log ID from the top, and activates the transaction cancellation processing unit 102b (see Figure 12).

The transaction cancellation processing unit 102b performs the following steps (11) to (16) as the process for extracting claims to be processed collectively.
(11) With the record of the specified customer ID displayed on the monitor 114 in area MA3 of the transaction cancellation screen MA by the history output unit 102a, the user is prompted to check the column name “Transaction Target” of the debt to be subject to the cancellation process and specify the debt.
(12) The bond transaction history data 106a is referenced to obtain the record corresponding to the specified bond.
(13) Based on the transaction type code of the bond record acquired in (12), the transaction type master 106g is referenced and the processing SEQ unit cancellation flag "TRUE" or "FALSE" corresponding to the transaction type code is acquired.
(14) If the processing SEQ unit cancellation flag acquired in (13) is "TRUE", the processing SEQ is acquired from the bond record acquired in (12), the bond transaction history data 106a is referenced, all records containing the same processing SEQ are acquired, and the column name "Transaction Target" of the record corresponding to the acquired record is checked and displayed on the transaction cancellation screen MA. Note that if the acquired processing SEQ unit cancellation flag is "FALSE", the process of (14) is not executed and the process proceeds to (15).
(15) With the column name "Transaction Target" on the transaction cancellation screen MA of (11) or (14) checked, press the execute button MA4.
(16) The bond transaction history data 106a is referenced, and the record of the bond with a check mark in the column name "Transaction Target" on the transaction cancellation screen MA is obtained, and an error check is performed.

The transaction cancellation processing unit 102b performs (21) as a claim selection process for one record from the records obtained in (12) or (14) above (if multiple claims are checked, they are processed in descending order of the claim log ID value), and then performs (22) to (25) as an error check.
(21) Among the records acquired in (12) or (14) above, the record with the largest value of the bond log ID is selected.
(22) Refer to the bond transaction history data 106a, obtain the record with the largest bond log ID corresponding to the bond ID of the record selected in (21), and check whether it matches the record selected in (21). Note that the larger the value of the bond log ID, the newer the record.
(23) If the processing SEQ unit cancellation flag acquired in (13) is "TRUE", refer to the bond transaction history data 106a and confirm whether a check is set in the column name "Transaction Target" on the transaction cancellation screen MA for all records including the processing SEQ of the bond acquired in (14). Note that if the processing SEQ unit cancellation flag is "FALSE", the check in (23) is not performed.
(24) If (22) and (23) cannot be confirmed due to discrepancies or other reasons, an error message will be displayed on the transaction cancellation screen MA.
(25) If all of (22) and (23) are confirmed, the cancellation process will begin.

The transaction cancellation processing unit 102b performs steps (31) to (36) as cancellation processing for each record for which the error check has been completed.
(31) Refer to the credit log data 106d, obtain a record containing the credit log ID of the credit record for which the error check has been completed, assign a new credit log ID and store it in the column named "credit log ID", and since this is data updated by the transaction cancellation process, set "TRUE" to the column named "transaction cancellation flag" and store a value relative to the credit amount of the record in the obtained credit log data 106d (if it is a positive value, the value with the corresponding negative sign attached, if it is a negative value, the value meaning positive).For the other columns of the credit log data 106d, store the value of the record in the obtained credit log data 106d as is in the corresponding column, and store and update the record of so-called canceled transfer data (red slip) in the credit log data 106d.
(32) With reference to the bond transaction history data 106a, extract the record containing the bond ID and transaction history SEQ of the bond record for which the error check has been completed, delete the extracted record, and update the bond transaction history data 106a.
(33) With reference to the claim history data 106c, extract the record containing the claim ID and claim history SEQ of the claim record for which the error check has been completed, delete the extracted record, and update the claim history data 106c.
(34) The latest bond data 106b is referenced, a record including the bond ID of the bond record for which the error check has been completed is extracted, the extracted record is deleted, and the latest bond data 106b is updated.
(35) Refer to the claim history data 106c after processing in (33) to see if there is a record containing the claim ID of the claim record for which the error check has been completed, and if there is, extract the record with that claim ID and the maximum claim history SEQ. Store the value of the extracted record in the corresponding column of the latest claim data 106b, generate the latest claim data 106b, add and update the latest claim data 106b, and terminate the cancellation process. Note that, when referring to the claim history data 106c after processing in (33), if there is no record containing the claim log ID of the claim record for which the error check has been completed, terminate the cancellation process.
(36) If there are multiple records acquired in (12) or (14) above, after the cancellation process is completed, return to the process in (21) except for the record of the bond for which the cancellation process has been completed, and perform a series of processes from error check to cancellation process. This process is repeated until the cancellation process is completed for all the records acquired in (12) or (14) above.

2. Specific examples of processing
A specific example of the process executed by the business support device 100 configured as described above will be described in detail with reference to Figures 11 to 17. Note that the transaction cancellation screen MA shows a part of the transaction cancellation screen.

As a premise, the transaction type "9: Settlement" for claim log ID "1103" will be canceled, and the person in charge will carry out the process. In this example, the transaction type "9: Settlement" for claim log ID "1103" being canceled is a transaction type that is calculated by adjusting the balance of "800,000 yen" for claim log ID "201" for claim ID "1001" and "400,000 yen" for claim log ID "202" for claim ID "1002" (total of 1,200,000 yen) to the agreed amount (remaining amount) of "990,000 yen" upon settlement. This adjustment is carried out by setting the total of "1,200,000 yen" to the agreed amount (remaining amount) of "990,000 yen" (see Figure 10).

The person in charge enters customer ID "12345" in area MA1 of the transaction cancellation screen MA, which is already displayed on monitor 114, and presses display button MA2 (see Figure 11).

The history output unit 102a then references the bond transaction history data 106a in Figure 10, extracts records containing customer ID "12345", displays them in area MA3 in ascending order of bond log ID from the top, and activates the transaction cancellation processing unit 102b (see Figure 12).

Next, the person in charge checks the column name "Transaction Target" of the record displayed in area MA3, which contains the bond ID "1003" of the bond to be canceled (see Figure 13).

The transaction cancellation processing unit 102b references the bond transaction history data 106a, obtains the record containing the specified bond ID "1003", obtains the transaction type code "9" from the obtained record, and references the transaction type master 106g to obtain the processing SEQ unit cancellation flag "TRUE" (see Figure 13).

Because the processing SEQ unit cancellation flag is "TRUE", the transaction cancellation processing unit 102b obtains processing SEQ "5" from the record containing the obtained bond ID "1003", references the bond transaction history data 106a, obtains the records for bond log ID "1101" and bond log ID "1102" that contain processing SEQ "5", and checks the column name "Transaction Target" on the transaction cancellation screen MA corresponding to the records for bond log ID "1101" and bond log ID "1102" to display them (see Figure 13).

Next, the person in charge confirms that the check mark has been set in the "Transaction Target" column name in area MA3 of the transaction cancellation screen MA, and presses the execute button MA4.

The transaction cancellation processing unit 102b then references the bond transaction history data 106a and obtains the records for bond log ID "1101," bond log ID "1102," and bond log ID "1103."

The transaction cancellation processing unit 102b selects the record with the largest credit log ID "1103" from the acquired records with credit log ID "1101," credit log ID "1102," and credit log ID "1103," and begins error checking.

(1) Error check The transaction cancellation processing unit 102b acquires the bond ID "1003" of the record with the acquired bond log ID "1103," references the bond transaction history data 106a, and acquires the maximum value "1103" of the bond log ID of the record containing the bond ID "1003." Since the maximum value "1103" of the acquired bond log ID matches the bond log ID "1103" of the selected bond to be processed, it is confirmed that this is the most recent transaction.

Next, since the processing SEQ unit cancellation flag is "TRUE," the transaction cancellation processing unit 102b references the bond transaction history data 106a and obtains the record bond log ID "1101," bond log ID "1102," and bond log ID "1103" that contain the processing SEQ "5" corresponding to the obtained transaction type code "9." It compares these with bonds that have a check mark in the column name "Transaction Target" in area MA3 of the transaction cancellation screen MA, and confirms that all are checked. It then ends the error check and begins the cancellation processing.

(2) Cancellation Processing (2-1) The transaction cancellation processing unit 102b references the bond log data 106d and acquires a record containing the bond log ID "1103" for which the error check has been completed. In order to create a record of the bond log data 106d for cancellation, the transaction cancellation processing unit 102b assigns a bond log ID and stores "3001" in the column name "bond log ID," stores "TRUE" in the column name "transaction cancellation flag" because this data is updated by the transaction cancellation processing, stores "-990,000" corresponding to the recorded bond amount "990,000" in the record of the acquired bond log data 106d, and stores the values of the record containing the bond log ID "1103" in the bond log data 106d as is in the other columns, creates a record of the bond log data 106d for cancellation, stores it in the bond log data 106d, and updates it (see 2-1 in FIG. 14).

(2-2) The transaction cancellation processing unit 102b references the bond transaction history data 106a, extracts records containing the bond ID "1003" and transaction history SEQ "1", deletes the extracted records, and updates the bond transaction history data 106a (see 2-2 in Figure 14).

(2-3) The transaction cancellation processing unit 102b references the claim history data 106c, extracts records containing the claim ID "1003" and the claim history SEQ "1", deletes the extracted records, and updates the claim history data 106c (see 2-3 in Figure 14).

(2-4) The transaction cancellation processing unit 102b references the latest bond data 106b, extracts the record containing the bond ID "1003", deletes the extracted record, and updates the latest bond data 106b (see 2-4 in Figure 14).

(2-5) After processing (2-3) above (after deleting the record containing the bond ID "1003" and the bond history SEQ "1"), the transaction cancellation processing unit 102b references the bond history data 106c and checks whether a record containing the bond ID "1003" exists. Since no record exists, the transaction cancellation processing is terminated (see 2-5 in Figure 14).

The transaction cancellation processing unit 102b selects the record with the largest credit log ID "1102" from the acquired records with credit log ID "1101" and credit log ID "1102", excluding the record with credit log ID "1103" for which cancellation processing has been completed.

The transaction cancellation processing unit 102b references the bond transaction history data 106a, obtains the bond ID "1002" contained in the record with the bond log ID "1102", and performs the same processing as the error check described above in (1).

The transaction cancellation processing unit 102b references the claim log data 106d, obtains the transaction history SEQ "4" and claim history SEQ "2" linked to the claim log ID "1102", and performs the above processes (2-1) to (2-4) (see 2-1 to 2-4 in Figure 15).

(2-6) After the completion of the above (2-3) process (after deleting the record containing the bond ID "1002" and the bond history SEQ "2"), the transaction cancellation processing unit 102b references the bond history data 106c to confirm whether a record containing the bond ID "1002" exists. Since a record containing the bond ID "1002" exists, the transaction cancellation processing unit 102b references the bond history data 106c after the completion of the above (2-3) process, obtains the latest record containing the bond ID "1002" (the bond history SEQ has the maximum value) and the bond history SEQ "1", stores the value of the obtained record in the corresponding column of the latest bond data 106b, generates a new record of the latest bond data 106b, updates and adds it to the latest bond data 106b, and terminates the cancellation processing (see 2-5 in Figure 15).

The transaction cancellation processing unit 102b excludes the debt log ID "1103" and debt log ID "1102", for which cancellation processing has been completed, and selects the debt log ID "1101", for which cancellation processing has not been performed.

The transaction cancellation processing unit 102b references the bond transaction history data 106a, obtains the bond ID "1001" contained in the record with the bond log ID "1101," and performs the same processing as (1) an error check and (2) cancellation processing for the above bond log ID "1102," and then terminates the processing (see 2-1 to 2-5 in Figure 16).

As a result of the above cancellation process, the table state of each data after processing is completed will be as shown in Figure 17. Compare the table state before processing shown in Figure 10 with the table state in Figure 17.

For the bond transaction history data 106a, the automatically selected bond ID "1003" transaction history SEQ "1," bond ID "1002" transaction history SEQ "4," and bond ID "1001" transaction history SEQ "4" were deleted, and data was deleted for all transactions classified (grouped) as the bond log ID "1103" transaction type "9: Settlement" that were the subject of this cancellation, and the data was updated. As a result, the bond transaction history data 106a has reverted to the data before the processing of bond log ID "1103" transaction type "9: Settlement."

For latest claim data 106b, the claim history SEQ data linked to all transactions classified (grouped) under claim log ID "1103" and transaction type "9: Settlement" that were subject to cancellation (claim history SEQ "1" data for claim ID "1003," claim history SEQ "2" data for claim ID "1002," and claim history SEQ "2" data for claim ID "1001") was deleted, and the data deleted by processing claim log ID "1103" and transaction type "9: Settlement" (claim history SEQ "1" data for claim ID "1002" and claim history SEQ "1" data for claim ID "1001") was added, updating the data to the latest claim history SEQ data prior to processing claim log ID "1103" and transaction type "9: Settlement." As a result, latest claim data 106b has reverted to the data prior to processing claim log ID "1103" and transaction type "9: Settlement."

For claim history data 106c, the claim history SEQ data linked to all transactions classified (grouped) under claim log ID "1103" and transaction type "9: Settlement" that were subject to cancellation (claim history SEQ "1" data for claim ID "1003", claim history SEQ "2" data for claim ID "1002", and claim history SEQ "2" data for claim ID "1001") was deleted and the data was updated. As a result, claim history data 106c has reverted to the data before processing for claim log ID "1103" and transaction type "9: Settlement".

The credit log data 106d has been updated with the addition of cancellation log data (data for credit log IDs "3001," "3002," and "3003") that was created during the transaction processing (cancellation processing 2-1) performed on all transactions classified (grouped) with credit log ID "1103" and transaction type "9: Settlement" that were subject to cancellation. This records that cancellation processing has been performed on data linked to all transactions classified (grouped) with credit log ID "1103" and transaction type "9: Settlement." In addition, "-990,000 yen" is stored in the recorded amount of the claim for claim log ID "3001" in claim log data 106d, canceling the settlement amount; "-400,000 yen" is stored in the waived amount for claim log ID "3002", canceling the amount waived through settlement; and "-800,000 yen" is stored in the waived amount for claim log ID "3003", canceling the amount waived through settlement, returning to the data before processing for claim log ID "1103" transaction type "9: Settlement."

As described above, according to this embodiment, by classifying and managing settlement and other processing of claims, it becomes possible to manage all claims that have undergone settlement and other processing on the system. Due to the nature of the cancellation process of settlement and other processing of claims, if the cancellation process is not performed on all claims that have undergone settlement and other processing, data consistency will be lost. However, this cancellation process can be performed automatically, which improves business efficiency and reduces the risk of processing omissions.

[3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

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

Furthermore, with regard to the business support device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the business support device 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, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

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

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes 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-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) 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. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known structures and procedures.

The various databases stored in the memory unit 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 business support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The business support device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform 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 may be implemented in any combination, or embodiments may be implemented selectively.

The present invention is useful in industries that perform debt management operations, such as debt collection businesses (servicers) and financial institutions.

100 Business support device 102 Control unit
102a History output unit
102b Transaction cancellation processing unit 104 Communication interface unit 106 Storage unit
106a Bond transaction history data
106b Latest bond data
106c Credit history data
106d Credit log data
106e Contract Data
106f Customer Data
106g Transaction type master
106h Transaction content master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (8)

a claim extraction unit that extracts the transaction type included in the claim data designated by the person in charge from claim data including transaction date, transaction amount, transaction type, processing sequence number management identification information set in order based on the transaction date and the transaction type, and claim identification information of the claim that has been processed corresponding to each of the processing sequence number management identification information ;
a batch processing target classification acquisition unit that references a transaction type master that stores a batch processing target classification indicating whether or not a transaction type is subject to batch processing for each transaction type of receivables, and acquires a batch processing target classification corresponding to the extracted transaction type ;
a lump-sum processing claims extraction unit that extracts claims data having the same processing sequence number management identification information as the processing sequence number management identification information included in the claims data designated by the person in charge when the lump-sum processing target category acquired by the lump-sum processing target category acquisition unit indicates that the lump-sum processing target category is a target for lump-sum processing ;
a batch data processing unit that collectively performs data processing corresponding to each of the claim data extracted by the claim extraction unit and each of the related data to which the same claim identification information as that of each of the claim data extracted by the claim extraction unit is assigned, in accordance with the claim data or each of the related data;
A debt management device comprising: The bond data is bond transaction history data indicating a transaction history of the bond,
the related data being claim log data including the amount of claims recorded or waived, claim history data including the amount of claims recorded, and latest claim data including the amount of claims recorded;
The batch data processing unit
generating new debt log data by subtracting the debt recorded amount or the waived amount from the debt log data;
deleting the bond transaction history data, the bond history data, and the latest bond data, which are the bond data extracted by the bond extraction unit;
performing data processing in a lump sum to generate the latest credit history data of the credit identification information of the deleted credit history data as new latest credit data;
2. The claim management device according to claim 1, The batch data processing unit
comparing the processing history identification information included in the claims data specified by the person in charge with the processing history identification information included in the claims data extracted by the batch processing claims extraction unit, selecting the claims data with the largest value of the processing history identification information, and starting the data processing from the selected claims data;
Furthermore, after generating the new latest claim data, the claim data extracted by the claim extraction unit and the claim data extracted by the lump-sum processing claim extraction unit are checked, and if processing of all of the claim data has not been completed, the claim data from which the new latest claim data was generated is excluded, and the processing history identification information of the claim data extracted by the claim extraction unit and the processing history identification information of the claim data extracted by the lump-sum processing claim extraction unit are compared again, and the claim data with the largest value of the processing history identification information is selected, and the data processing is started from the selected claim data.
3. The claim management device according to claim 2. The batch data processing unit
Before the data processing,
Obtaining the maximum value of the processing history identification information linked to the bond identification information included in the bond data specified by the person in charge , and confirming whether it matches the value of the processing history identification information of the bond data specified by the person in charge ;
After the confirmation is completed, if the batch processing target category acquired by the batch processing target category acquisition unit indicates that the acquired batch processing target category is subject to batch processing, it is confirmed whether the batch processing claim extraction unit has extracted, from the claim data, the claim data having the same processing sequence number management identification information as the processing sequence number management identification information included in the claim data designated by the person in charge .
4. The claim management device according to claim 3 . The claim extraction unit
a first output control unit that refers to the bond data stored in the storage unit, extracts the bond data associated with the customer designated on the transaction cancellation screen for executing the transaction cancellation process , and selectably outputs the extracted bond data on the transaction cancellation screen ;
The batch processing claim extraction unit
A claim management device as described in any one of claims 1 to 4, characterized in that it is provided with a second output control unit that refers to the claim data stored in the memory unit and displays the claim data including the processing sequence number management identification information extracted by the claim extraction unit in a selected format on the transaction cancellation screen. The claim in the claim data is a monetary claim;
6. The claim management device according to claim 5 , a claim extraction step in which the claim extraction unit extracts the transaction type included in the claim data designated by the person in charge from claim data including transaction date, claim amount, transaction type, processing sequence number management identification information set in order based on the transaction date and the transaction type, and claim identification information of the claim that has been processed corresponding to each of the processing sequence number management identification information ;
a batch processing target category acquisition step in which the batch processing target category acquisition unit references a transaction type master in which a batch processing target category indicating whether or not a transaction type of a bond is subject to batch processing is stored, and acquires a batch processing target category corresponding to the extracted transaction type ;
a lump-sum processing claims extraction step in which, when the lump-sum processing claims extraction unit indicates that the lump-sum processing target category acquired by the lump-sum processing target category acquisition unit is a target for lump-sum processing, the lump-sum processing claims extraction unit extracts, from the claims data, claims data having the same processing sequence number management identification information as the processing sequence number management identification information included in the claims data designated by the person in charge ;
a batch data processing step in which a batch data processing unit collectively performs data processing corresponding to each of the bond data and each of the related data to which the same bond identification information as that of each of the bond data extracted by the bond extraction unit is assigned, on the bond data or each of the related data;
A claim management method for a claim management device having the above structure . Computer,
a claim extraction unit that extracts the transaction type included in the claim data designated by the person in charge from claim data including transaction date, claim amount, transaction type, processing sequence number management identification information set in order based on the transaction date and the transaction type, and claim identification information of the claim that has been processed corresponding to each of the processing sequence number management identification information ;
a batch processing target classification acquisition unit that references a transaction type master that stores a batch processing target classification indicating whether or not a transaction type is subject to batch processing for each transaction type of receivables, and acquires a batch processing target classification corresponding to the extracted transaction type ;
a lump-sum processing claims extraction unit that extracts claims data having the same processing sequence number management identification information as the processing sequence number management identification information included in the claims data designated by the person in charge when the lump-sum processing target category acquired by the lump-sum processing target category acquisition unit indicates that the lump-sum processing target category is a target for lump-sum processing ;
a batch data processing unit that collectively performs data processing corresponding to each of the claim data extracted by the claim extraction unit and each of the related data to which the same claim identification information as each of the claim data extracted by the claim extraction unit is attached,
A debt management program that functions as a