Debt management device, debt management method, and debt management program

Abstract

To provide a credit management device or the like, which can automatically cancel transactions of data related to all target credits at once by classifying and managing data related to multiple credits that have undergone transaction update processing, thereby improving business efficiency and reducing the risk of processing omission.SOLUTION: The present embodiment includes: extracting predetermined credit data by referring to credit transaction history data; acquiring, by referring to a transaction kind master, a batch processing target classification that classifies whether the predetermined credit data is subject to batch processing; extracting credit data linked to the predetermined credit data by referring to the credit transaction history data, if the batch processing classification is subject to the batch processing; and updating data linked to the extracted credit data and data linked to the predetermined credit data.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a receivables liquidation system that quickly and accurately completes a series of liquidation procedures, including processing such as receivables price adjustments following receivables cancellation. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-309697 Summary of the Invention [Problem to be solved by the invention]

[0004] In the creditor management process, transactions between creditors (individuals, companies, etc. that hold credit) and debtors may result in updates (transaction updates) to data related to the customer debtor or all credits linked to a specific contract. For example, if a creditor and a customer debtor conduct a transaction and reach a settlement for all credits of that customer, the creditor management process will process the settlement and update the data related to the relevant credit. In addition, a creditor may write off or accelerate all credits of a specific contract to the debtor, and the creditor management process will process the data related to the relevant credit and accelerate the credit. In the case of transactions involving multiple credits such as those described above, it is possible to automatically process the data updates related to the relevant credits in bulk. On the other hand, if the transaction update process (for example, settlement) is canceled due to a violation of the settlement clauses or other reasons, in the accounts receivable management process, it is essential to cancel transactions in order, starting with the most recent transaction. Therefore, the person in charge must select the data related to all accounts receivable for which the transaction update process (for example, settlement) has been performed, cancel the data related to the selected accounts receivable (transaction cancellation), and return to the data before the transaction update process (for example, before settlement).If there are many accounts receivable, this increases the workload of the person in charge, and there is a risk that accounting coordination, foreign currency reporting, etc. will be carried out with incorrect information due to a processing omission.

[0005] 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 classify and manage receivables by transaction type, thereby enabling automatic data update processing for data linked to all target receivables in one go, thereby improving business efficiency and reducing the risk of processing omissions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the debt management device according to the present invention comprises: Among the 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 the claims that have been processed corresponding to each of the processing sequence number management identification information, the transaction type included in the claim data designated by the person in charge is a claim extraction unit for extracting claims; For each transaction type of bond, a transaction type master is referenced, which stores a batch processing target classification indicating whether the transaction type is subject to batch processing or not, and the extracted transaction type is a batch processing target division acquiring unit for acquiring a batch processing target division; When indicating that the claim is a target, the claim data having the same processing serial number management identification information as the processing serial number management identification information included in the claim data designated by the person in charge among the claim data a lump-sum processing claim extraction unit that extracts the claims extracted by the claim extraction unit; a batch data processing unit that 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, in accordance with the bond data or each of the related data; The present invention is characterized by comprising:

[0007] In the debt management device according to the present invention, the claim data is claim transaction history data showing the transaction history of claims, the related data is claim log data including the claim recorded amount or the waived amount, claim history data including the claim recorded amount, and latest claim data including the claim recorded amount, and the batch data processing unit generates new claim log data by subtracting the claim recorded amount or the waived amount from the claim log data, deletes the claim transaction history data, the claim history data, and the latest claim data, which are the claim data extracted by the claim extraction unit, and performs batch data processing to generate the latest claim history data of the claim identification information of the deleted claim history data as new latest claim data; It is characterized by:

[0008] In addition, in the debt management device of the present invention, the related data includes the first data, the fourth data, and the fifth data, and the data deletion and update unit refers to the first data to delete and update the first data including the debt identification information and the transaction history serial number management identification information corresponding to the debt data, refers to the fourth data to delete and update the fourth data including the debt identification information and the debt history serial number management identification information corresponding to the debt data, and refers to the fifth data to delete and update the fifth data including the debt identification information corresponding to the debt data.

[0009] In addition, in the debt management device according to the present invention, The batch data processing unit is a The bond data Included in Processing history identification information and the claims data extracted by the batch processing claims extraction unit Included in The processing history identification information is compared, and the bond data having the largest value of the processing history identification information is selected. said data processing and then After generating the new latest bond data, The claim data extracted by the claim extraction unit and the claim data extracted by the batch processing claim extraction unit are checked, and if processing of all of the claim data has not been completed, New latest bond data was generated The claim data is removed, and the processing history identification information of the claim data extracted by the claim extraction unit is compared with the processing history identification information of the claim data extracted by the batch processing claim extraction unit, and the claim data having the largest value of the processing history identification information is selected. The data processing It is characterized by starting.

[0010] In addition, in the debt management device according to the present invention, 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, The above-mentioned bond data specified by the person in charge After the confirmation is completed, When the batch processing target category acquired by the batch processing target category acquisition unit indicates that the batch processing target category is a target for batch processing, 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 It is characterized by confirming.

[0011] In the claim management device according to the present invention, the claim extraction unit Refer to the bond data stored in the memory unit, To process the reversal of a transaction Specify on the transaction cancellation screen The credit data linked to the customer is Extract, The extracted bond data is output to the transaction cancellation screen in a selectable manner. a first output control unit, wherein the batch processing claim extraction unit Refer to the bond data stored in the memory unit, The invention is characterized by comprising a second output control unit that displays the bond data including the processing sequence number management identification information extracted by the bond extraction unit on the transaction cancellation screen in a selected mode.

[0012] In the claim management device according to the present invention, the claim in the claim data is a monetary claim.

[0013] Furthermore, the present invention Debt management device The receivables management method is as follows: Among the claims 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 claims that have been processed corresponding to each of the processing sequence number management identification information, the transaction type included in the claim data designated by the person in charge is identified. The claim extraction step and the batch processing target classification acquisition unit For each transaction type of bond, a transaction type master is referenced, which stores a batch processing target classification indicating whether the transaction type is subject to batch processing or not, and the extracted transaction type is a lump-sum processing target classification acquisition step of acquiring a lump-sum processing target classification; and a lump-sum processing claim extraction unit determining whether the lump-sum processing target classification acquired by the lump-sum processing target classification acquisition unit is a lump-sum processing target classification. When indicating that the claim is a target, the claim data having the same processing serial number management identification information as the processing serial number management identification information included in the claim data designated by the person in charge among the claim data a lump-sum processing claim extraction step for extracting the claims; The system has a bulk data processing step in which a bulk data processing unit collectively performs data processing corresponding to each of the claim data 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 attached.

[0014] In addition, the receivables management program according to the present invention comprises: The computer is configured to identify the transaction type included in the bond data designated by the person in charge among the bond data including the 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 the bond identification information of the bond that has been processed corresponding to each of the processing sequence number management identification information. a claim extraction unit for extracting claims; For each transaction type of bond, a transaction type master is referenced, which stores a batch processing target classification indicating whether the transaction type is subject to batch processing or not, and the extracted transaction type is a batch processing target division acquiring unit for acquiring a batch processing target division; When indicating that the claim is a target, the claim data having the same processing serial number management identification information as the processing serial number management identification information included in the claim data designated by the person in charge among the claim data a lump-sum processing claim extraction unit that extracts the claims extracted by the claim extraction unit; The debt extraction unit functions as a bulk data processing unit that collectively performs data processing corresponding to each of the debt data and each of the related data that has the same debt identification information as each of the debt data extracted by the debt extraction unit. [Effects of the Invention]

[0015] The present invention has the effect of classifying and managing receivables by transaction type, thereby enabling automatic data updating processing for all data linked to the relevant receivables in one go, thereby improving business efficiency and reducing the risk of processing omissions. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a business support device according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of bond transaction history data according to this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of the latest bond data according to this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of the credit history data according to this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of the bond log data according to this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of contract data according to this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of customer data according to this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the transaction type master according to this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the transaction content master according to this embodiment. [Figure 10] 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. [Figure 11] FIG. 11 is a diagram showing an example of a screen for explaining a specific example of processing in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a screen for explaining a specific example of processing in this embodiment. [Figure 13] 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. [Figure 14]FIG. 14 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 16] FIG. 16 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of data after processing is performed, for explaining a specific example of processing in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

[0020] The business assistance device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the business assistance device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0021] The communication interface unit 104 communicably connects the business assistance 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 business assistance 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 be stored in the server 200, for example.

[0022] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0023] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. 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, an optical disk, etc.

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

[0025] As shown in Figure 2, the bond transaction history data 106a holds a snapshot of information related to bond transactions at the time of 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 a 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 transaction history of the bond (e.g., transaction history SEQ, etc.), bond history serial number management identification information that manages the history of the bond (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.).

[0026] The latest claim data 106b holds the latest data for each claim identification information (claim ID), as shown in Fig. 3. The latest claim data 106b stores the claim identification information, claim history serial number management identification information, claim recording date, claim recording 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.).

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

[0028] The credit log data 106d is used to sequentially record credit processing (including cancellation processing) and to add and manage data, as shown in Fig. 5. The credit 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., credit log ID of the transaction cancellation source, etc.), credit identification information, transaction history serial number management identification information, credit history serial number management identification information, transaction type identification information, transaction content identification information, transaction date, transaction amount, credit amount, deposit amount, appropriated amount, and waived amount, etc.

[0029] The contract data 106e is used to manage contracts, as shown in Fig. 6. The contract data 106e stores contract identification information, customer identification information, and the like.

[0030] The customer data 106f is used to manage customers, as shown in Fig. 7. The customer data 106f stores customer identification information and customer names.

[0031] The transaction type master 106g is used to manage transaction types, as shown in Figure 8. The transaction type master 106g stores transaction type identification information, transaction type name, and cancellation unit classification (e.g., processing sequence unit cancellation flag) that classifies whether or not cancellation processing is to be performed in units of processing sequence number management identification information.

[0032] The transaction content master 106h is used to manage transaction content, as shown in Fig. 9. The transaction content master 106h stores transaction content identification information, transaction type name, and the like.

[0033] 1, the control unit 102 is a CPU or the like that performs overall control of the business support 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.

[0034] 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, bulk processing target category acquisition unit, bulk 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).

[0035] 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 FIG. 11). The history output unit 102a then refers to 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 FIG. 12).

[0036] The transaction cancellation processing unit 102b performs the following steps (11) to (16) as the batch processing target claims extraction processing. (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 bond to be subject to the cancellation process and specify the bond. (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 obtained in (12), the transaction type master 106g is referenced and the processing sequence unit cancellation flag "TRUE" or "FALSE" corresponding to the transaction type code is obtained. (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) (11) or (14) Press the Execute button MA4 with the column name "Transaction Target" checked on the transaction cancellation screen MA. (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.

[0037] The transaction cancellation processing unit 102b performs (21) as a bond selection process for one record from the records obtained in (12) or (14) above (if multiple bonds are checked, they are processed in descending order of the bond log ID value), and then performs (22) to (25) as an error check. (21) Among the records obtained in (12) or (14) above, select the record with the maximum value of the credit log ID. (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 it is. (23) If the processing sequence 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 sequence of the bond acquired in (14). Note that if the processing sequence unit cancellation flag is "FALSE", the check in (23) is not performed. (24) If confirmation of (22) and (23) cannot be made due to discrepancies, etc., 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.

[0038] 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 the 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 that will be 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 other columns in 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) The bond transaction history data 106a is referenced, and the record containing the bond ID and transaction history SEQ of the bond record for which the error check has been completed is extracted, the extracted record is deleted, and the bond transaction history data 106a is updated. (33) The bond history data 106c is referenced, and the record containing the bond ID and bond history SEQ of the bond record for which the error check has been completed is extracted, the extracted record is deleted, and the bond history data 106c is updated. (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) The bond history data 106c after processing in (33) is referenced to check whether a record exists that includes the bond ID of the bond record for which the error check has been completed, and if so, the record with that bond ID and the maximum bond history SEQ is extracted. The value of the extracted record is stored in the corresponding column of the latest bond data 106b, the latest bond data 106b is generated, and the latest bond data 106b is added and updated, and the cancellation process is terminated. Note that, when the bond history data 106c after processing in (33) is referenced, if no record exists that includes the bond log ID of the bond record for which the error check has been completed, the cancellation process is terminated. (36) If there are multiple records acquired in (12) or (14) above, after the cancellation process is completed, the process returns to (21) except for the record of the bond for which the cancellation process has been completed, and a series of processes from error check to cancellation process are performed. This process is repeated until the cancellation process is completed for all the records acquired in (12) or (14) above.

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

[0040] As a premise, the transaction type "9: Settlement" with the claim log ID "1103" will be cancelled, and the person in charge will carry out the process. Note that in this embodiment, the transaction type "9: Settlement" with the claim log ID "1103" to be cancelled is a transaction in which the balance "800,000 yen" of the claim log ID "201" with the claim ID "1001" and the balance "400,000 yen" of the claim log ID "202" with the claim ID "1002" totaling "1,200,000 yen" to an agreed amount (remaining amount) of "990,000 yen" upon the settlement, and records relating to the claim log ID "1103" with the claim log ID "1101" with the claim ID "1001" and the claim log ID "1102" with the claim ID "1002" are stored in each data (see FIG. 10).

[0041] The person in charge or the like specifies the customer ID "12345" in the area MA1 of the transaction cancellation screen MA that is displayed in advance on the monitor 114, and presses the display button MA2 (see FIG. 11).

[0042] The history output unit 102a then refers to the bond transaction history data 106a in Figure 10, extracts records containing the customer ID "12345", displays them in area MA3 in order of lowest bond log ID from the top so that they can be selected, and activates the transaction cancellation processing unit 102b (see Figure 12).

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

[0044] The transaction cancellation processing unit 102b refers to 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 refers to the transaction type master 106g to obtain the processing SEQ unit cancellation flag "TRUE" (see Figure 13).

[0045] Since 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 with 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 with bond log ID "1101" and bond log ID "1102" and displays them (see Figure 13).

[0046] Next, the person in charge confirms the receivables that have a check mark set in the column name "Transaction Target" in area MA3 of the transaction cancellation screen MA, and presses the execute button MA4.

[0047] Then, the transaction cancellation processing unit 102b refers to the bond transaction history data 106a and acquires the records of the bond log ID "1101", the bond log ID "1102" and the bond log ID "1103".

[0048] The transaction cancellation processing unit 102b selects the record with the largest bond log ID "1103" from the acquired records with bond log ID "1101," bond log ID "1102," and bond log ID "1103," and starts error checking.

[0049] (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 bond log ID value "1103" of the record containing the bond ID "1003." Since the acquired maximum bond log ID value "1103" matches the bond log ID "1103" of the selected bond to be processed, it is confirmed that this is the most recent transaction.

[0050] Next, since the processing SEQ unit cancellation flag is "TRUE", the transaction cancellation processing unit 102b refers to the bond transaction history data 106a and obtains the record bond log ID "1101", bond log ID "1102" and bond log ID "1103" which contain the processing SEQ "5" corresponding to the obtained transaction type code "9", and compares them with bonds which have a check mark in the column name "Transaction target" in area MA3 of the transaction cancellation screen MA, confirms that all are checked, terminates the error check and starts the cancellation processing.

[0051] (2) Cancellation process (2-1) The transaction cancellation processing unit 102b references the bond log data 106d and acquires the 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 process, stores "-990,000" corresponding to the bond posted amount "990,000" of the record of the acquired bond log data 106d, and stores the values ​​of the record containing the bond log ID "1103" of 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 Figure 14).

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

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

[0054] (2-4) The transaction cancellation processing unit 102b refers to 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 FIG. 14).

[0055] (2-5) The transaction cancellation processing unit 102b refers to the claim history data 106c after the processing of (2-3) above (after deleting the record containing the claim ID "1003" and the claim history SEQ "1") and checks whether a record containing the claim ID "1003" exists. Since no record exists, the cancellation processing is terminated (see 2-5 in Figure 14).

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

[0057] The transaction cancellation processing unit 102b refers to the bond transaction history data 106a, acquires the bond ID "1002" contained in the record with the bond log ID "1102", and performs the same processing as the error check in (1) above.

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

[0059] (2-6) After the completion of the processing in (2-3) above (after deleting the record containing the bond ID "1002" and the bond history SEQ "2"), the transaction cancellation processing unit 102b refers to the bond history data 106c and confirms whether a record containing the bond ID "1002" exists. Since a record containing the bond ID "1002" exists, the transaction cancellation processing unit 102b refers to the bond history data 106c and obtains the latest record containing the bond ID "1002" (the bond history SEQ has the maximum value), the record containing 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 ends the cancellation processing (see 2-5 in Figure 15).

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

[0061] The transaction cancellation processing unit 102b refers to the bond transaction history data 106a, obtains the bond ID "1001" contained in the record of the bond log ID "1101", performs processing similar to (1) error check and (2) cancellation processing for the above bond log ID "1102", and terminates the processing (see 2-1 to 2-5 in Figure 16).

[0062] As a result of the above cancellation process, the table state of each data after the process is completed is as shown in Fig. 17. The table state before the process shown in Fig. 10 is compared with the table state in Fig. 17.

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

[0064] 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 (the data in claim history SEQ "1" for claim ID "1003," the data in claim history SEQ "2" for claim ID "1002," and the data in claim history SEQ "2" for claim ID "1001") were deleted, and the data deleted by the processing of claim log ID "1103" and transaction type "9: Settlement" (the data in claim history SEQ "1" for claim ID "1002" and the data in claim history SEQ "1" for claim ID "1001") were added, and the data was updated to the latest claim history SEQ data prior to the processing of claim log ID "1103" and transaction type "9: Settlement." As a result, latest claim data 106b has returned to the data prior to the processing of claim log ID "1103" and transaction type "9: Settlement."

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

[0066] The credit log data 106d has been updated by adding additional 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. As a result, it is recorded that the credit log data 106d has been updated with the cancellation processing performed on data linked to all transactions classified (grouped) with credit log ID "1103" and transaction type "9: Settlement." In addition, the recorded amount of the claim for claim log ID "3001" in claim log data 106d is stored as "-990,000 yen", canceling the settlement amount, the waived amount for claim log ID "3002" is stored as "-400,000 yen", canceling the amount waived due to settlement, and the waived amount for claim log ID "3003" is stored as "-800,000 yen", canceling the amount waived due to settlement, and the data has returned to the state before processing for claim log ID "1103" transaction type "9: Settlement".

[0067] 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, and due to the nature of the cancellation process of settlement and other processing of claims, data consistency would be lost if the cancellation process was not performed on all claims that have undergone settlement and other processing. However, this cancellation process can be performed automatically, which makes it possible to improve business efficiency and reduce the risk of processing omissions.

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

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

[0070] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

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

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

[0074] Furthermore, with regard to the task support device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0075] For example, all or any part of the processing functions of the business support device 100, particularly the processing functions performed by the control unit, may be implemented 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. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0076] This computer program may be stored in 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.

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

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

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

[0080] 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 the information processing device to which any peripheral device is connected. The business support device 100 may be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

[0081] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

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

[0083] 100 Business support equipment 102 Control section 102a History output section 102b Transaction cancellation processing unit 104 Communication interface unit 106 Storage section 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 Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A claim extraction unit that extracts the 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 said transaction date and said transaction type, and claim identification information of claims that have been processed corresponding to each of said 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:

2. 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,

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

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

5. The claim extraction unit a first output control unit that refers to the bond data stored in the storage unit, extracts bond data associated with a customer designated on a transaction cancellation screen for executing a transaction cancellation process, and selectably outputs the extracted bond data on the transaction cancellation screen; Equipped with The batch processing claim extraction unit a second output control unit that refers to the bond data stored in a storage unit and displays the bond data including the processing sequence number management identification information extracted by the bond extraction unit on the transaction cancellation screen in a selected mode; 5. The claim management device according to claim 1, further comprising:

6. The claim in the claim data is a monetary claim; 6. The debt management device according to claim 5,

7. 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 lump-processing target category acquisition step in which the lump-processing target category acquisition unit references a transaction type master in which lump-processing target categories indicating whether or not a transaction type is subject to lump-processing for each transaction type of receivables are stored, and acquires a lump-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.

8. A 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

Images