Name matching management device, name matching management method, and name matching management program

Abstract

To provide a name gathering management device, a name gathering management method, and a name gathering management program capable of performing flexible and accurate name gathering.SOLUTION: A name gathering management device performs first determination processing of determining whether or not a total score for each bond ID is less than a value of a name gathering bar with reference to a transfer / deposit control master, performs second determination processing of determining whether or not the total score for each bond ID is equal to or greater than a value of the name gathering bar with reference to the transfer / deposit control master, and based on results of the first determination processing and results of the second determination processing, name gathering results data is generated in which an execution date, a record sequence, name gathering results, the bond ID, a deposit date, and a deposit date sequence are associated with a company account code.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a technology that supports name matching of information based on various services. This technology acquires first user-related information stored in a first service server and second user-related information stored in a second service server for the same person, calculates a first score from the first user-related information and a second score from the second user-related information, and generates a prediction model for calculating the likelihood of the same person using the first and second scores as training data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-33465 Summary of the Invention [Problem to be solved by the invention]

[0004] In the financial industry, which handles credits and other receivables, the process of identifying customers and clearing payments against accounts receivable requires name matching using highly reliable information, and if the information is less reliable, a human judgement must be made at an early stage.

[0005] Furthermore, the methods of name matching and the reliability of each condition vary depending on the financial institution, so a flexible name matching system is required.

[0006] However, conventional systems used by financial institutions have fixed name matching methods, which means they cannot meet the name matching requirements of each financial institution and have low success rates for name matching.

[0007] The present invention has been made in view of the above, and has an object to provide a name merger management device, a name merger management method, and a name merger management program that are capable of performing flexible and accurate name merger. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the object, the name matching management device of the present invention is a name matching management device having a control unit, and is capable of accessing the following: a name matching condition master in which a condition code is associated with a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching; a transfer deposit control master in which a cutoff bar value indicating a failure during name matching, a name matching bar value indicating a success during name matching, and a setting value for a judgment category for multiple matches indicating whether a bond with a higher score should be adopted or whether the name matching should be failed when multiple matches are encountered during name matching; transfer deposit data in which an execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with the company's account code; and bond data in which a customer ID, customer name, account bank name, account branch name, virtual account number, and invoice amount are associated with a bond ID; and the control unit accesses the name matching condition master in which a cutoff bar value indicating a failure during name matching, a name matching bar value indicating a success during name matching, and a setting value for a judgment category for multiple matches when multiple matches are encountered during name matching, and and a calculation unit that calculates a total score for each claim ID based on the name matching detailed data; a first judgment unit that performs a first judgment process that refers to the transfer deposit control master and determines whether the total score for each claim ID is less than the value of the cutoff bar; a second judgment unit that performs a second judgment process that refers to the transfer deposit control master and determines whether the total score for each claim ID is equal to or greater than the value of the name matching bar; and a second generation unit that generates name matching result data that corresponds the execution date, record sequence, name matching result, the claim ID, deposit date, and deposit date sequence to the company's own account code based on the results of the first judgment process and the results of the second judgment process.

[0009] Furthermore, the name matching management method according to the present invention is a name matching management method executed by a name matching management device having a control unit, wherein the name matching management device is capable of accessing a name matching condition master in which a condition code is associated with a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching; a transfer deposit control master in which a cutoff bar value indicating a failure during name matching, a name matching bar value indicating a success during name matching, and a setting value of a judgment category for multiple matches indicating whether to adopt a bond with a higher score or to treat the name matching as a failure when multiple matches occur during name matching; transfer deposit data in which an execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with the company's account code; and bond data in which a customer ID, customer name, account bank name, account branch name, virtual account number, and invoice amount are associated with a bond ID, and the name matching management device executes a control process by referring to the name matching condition master. and a first generation step of generating detailed name matching data based on the transfer deposit data and the bond data, which associates the bond ID with a score corresponding to the condition code of the condition that matches the name matching condition master; a calculation step of calculating a total score for each bond ID based on the name matching detailed data; a first judgment step of performing a first judgment process by referring to the transfer deposit control master and determining whether or not the total score for each bond ID is less than the value of the cutoff bar; a second judgment step of performing a second judgment process by referring to the transfer deposit control master and determining whether or not the total score for each bond ID is equal to or greater than the value of the name matching bar; and a second generation step of generating name matching result data based on the results of the first judgment process and the second judgment process, which associates the execution date, record sequence, name matching result, the bond ID, deposit date, and deposit date sequence with the company's account code.

[0010] a name matching condition master in which a condition code is associated with a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching; a transfer deposit control master in which a value of a cutoff bar indicating a failure during name matching, a value of a name matching bar indicating a success during name matching, and a setting value of a judgment category for multiple matches indicating whether to adopt a bond with a higher score or to treat the name matching as a failure when multiple matches occur during name matching; transfer deposit data in which an execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with a company account code; and bond data in which a customer ID, customer name, account bank name, account branch name, virtual account number, and invoice amount are associated with a bond ID, a calculation step for calculating the total score for each bond ID based on the name matching detailed data; a first determination step for performing a first determination process for referring to the transfer deposit control master and determining whether the total score for each bond ID is less than the value of the cut-off bar; a second determination step for performing a second determination process for referring to the transfer deposit control master and determining whether the total score for each bond ID is equal to or greater than the value of the name matching bar; and a second generation step for generating name matching result data that corresponds the execution date, record sequence, name matching result, the bond ID, deposit date, and deposit date sequence to the company's account code based on the results of the first determination process and the second determination process. [Effects of the Invention]

[0011] The present invention has the effect of enabling flexible and accurate name matching. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a name identification management device according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a name merge condition master table in the name merge condition master of the name merge management device according to the embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a transfer deposit control master table in the transfer deposit control master of the name identification management device according to the embodiment. [Figure 4] FIG. 4 is a flowchart illustrating an outline of the processing executed by the name identification management device according to the embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a transfer deposit file import screen that the display control unit of the name identification management device according to the embodiment causes to be displayed on the monitor during the transfer deposit file import process. [Figure 6] FIG. 6 is a diagram showing an example of a transfer deposit data table in the transfer deposit data according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a temporary receipt data table in temporary receipt data according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a transfer deposit confirmation screen that the display control unit of the name matching management device according to the embodiment causes the monitor 114 to display during the name matching check implementation process. [Figure 9] FIG. 9 is a flowchart showing the details of the transfer deposit confirmation process. [Figure 10] FIG. 10 is a diagram illustrating an example of a name matching condition table in the name matching conditions. [Figure 11] FIG. 11 is a diagram showing an example of a transfer deposit data table in the transfer deposit data according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a bond data table in the bond data according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a detailed name merge data table in the detailed name merge data according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an outline of a method for calculating the total points calculated for each bond ID by the calculation unit of the name identification management device according to the embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of the name merge result data table for the name merge result data when the name merge fails. [Figure 16] FIG. 16 is a diagram illustrating an example of a name merge result data table in the name merge result data when the name merge is successful, which is generated by the second generation unit of the name merge management apparatus according to the embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the name merge data table in the name merge detailed data other than the details updated to the name merge result data. [Figure 18] FIG. 18 is a diagram illustrating an example of a total result table calculated for each bond ID at implementation level "2" by the calculation unit of the name identification management device according to the embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of a name merge result data table in the name merge result data when the name merge is successful, which is generated at implementation level "2" by the second generation unit of the name merge management apparatus according to the embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the name merge result data table for the name merge result data when name merge fails at implementation level "2." [Figure 21] FIG. 21 is a diagram showing an example of a name-merge result data table for name-merge result data in the case where there are multiple relevant loans with a total score equal to or greater than the name-merge bar when name-merge is successful at implementation level "2." [Figure 22] FIG. 22 is a diagram showing an example of a name-merge result data table for name-merge result data in the case where there are multiple relevant loans with a total score equal to or greater than the name-merge bar when name-merge fails at implementation level "2." [Figure 23] FIG. 23 is a diagram for explaining the association of the name identification result data, the provisional receipt data, and the transfer deposit data before the execution of the deposit reconciliation process. [Figure 24]FIG. 24 is a diagram showing an example of a lump-sum deposit reconciliation screen that the display control unit of the name identification management device according to the embodiment causes the monitor to display during the deposit reconciliation process. [Figure 25] FIG. 25 is a diagram showing an example of the temporary receipt data table for temporary receipt data after the deposit clearing process has been executed. [Figure 26] FIG. 26 is a diagram for explaining the association of the name identification result data, the provisional receipt data, and the transfer deposit data before the execution of the deposit reconciliation process. [Figure 27] FIG. 27 is a diagram showing an example of a temporary receipt list screen that the display control unit of the name identification management device according to the embodiment causes to be displayed on the monitor during the deposit reconciliation process. [Figure 28] FIG. 28 is a diagram showing an example of an individual deposit reconciliation screen that the display control unit of the name identification management device according to the embodiment causes the monitor to display during the deposit reconciliation process. [Figure 29] FIG. 29 is a diagram showing an example of the temporary receipt data table for temporary receipt data after the deposit clearing process has been executed. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, a name identification management apparatus, a name identification management method, and a name identification management program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the present embodiment.

[0014] [1. Configuration] An example of the configuration of a name identification management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a name identification management device.

[0015] 1 is a commercially available desktop personal computer. Note that the name identification management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0016] The name matching management 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 name matching management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0017] The communication interface unit 104 communicatively connects the name identification management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the name identification management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may also be stored in the server 200, for example.

[0018] 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 cooperation with a mouse. 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.

[0019] The memory unit 106 stores various databases, tables, files, etc. The memory 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 memory unit 106 may 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 a name matching condition master 106a, a transfer deposit control master 106b, transfer deposit data 106c, and bond data 106d. Details of the transfer deposit data 106c and the bond data 106d will be described later.

[0020] The name identification condition master 106a stores a condition code in association with a name identification condition name, an implementation level, and a target flag.

[0021] 2 is a diagram showing an example of a name matching condition master table in the name matching condition master 106a. In the first row of the name matching condition master table T1 shown in FIG. 2, a condition code "1" is stored in association with a name matching condition name "Name Matching," an implementation level "1," a target flag "1," and a score "6." The implementation level and score can be changed as appropriate by the user via the input device 112.

[0022] The transfer deposit control master 106b stores, in association with each other, the value of the cutoff bar, which indicates a failure during name matching, the value of the name matching bar, which indicates a success during name matching, and the setting value of the judgment category for multiple matches, which indicates whether to accept the claim with the highest score or to treat the name matching as a failure when multiple matches occur during name matching.

[0023] Figure 3 is a diagram showing an example of a transfer deposit control master table in the transfer deposit control master 106b. As shown in Figure 3, the first row of the transfer deposit control master table T2 stores a corresponding cutoff bar of "5," a name matching bar of "10," and a multiple match judgment category of "1." Here, the multiple match judgment category can be set by the user via the input device 112 by selecting either judgment category "1," which accepts bonds with high scores, or judgment category "2," which indicates a name matching failure. Furthermore, the values of the cutoff bar and name matching bar can be changed as appropriate by the user via the input device 112.

[0024] The details of the transfer data 106c and the bond data 106d will be described later.

[0025] Returning to FIG. 1, the description of the configuration of the name identification management device 100 will continue. The control unit 102 is a CPU or the like that comprehensively controls the name identification management 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 based on these stored programs. The control unit 102 includes an import unit 102a, a first generation unit 102b, a calculation unit 102c, a first determination unit 102d, a second determination unit 102e, a second generation unit 102f, a deposit reconciliation processing unit 102g, an extraction unit 102h, and a display control unit 102i.

[0026] The import unit 102a imports, line by line, the file specified by the user via the input device 112 in the import file cell K3, and updates the transfer deposit data. In this case, the import unit 102a generates temporary receipt data according to the number of transfer deposit data imported.

[0027] The first generation unit 102b refers to the name matching condition master 106a and performs a name matching check based on the transfer deposit data 106c and the bond data 10d to generate name matching detailed data that associates the company's account code with the execution date, record SEQ, condition code of the condition that matches the name matching condition master 106a, name matching SEQ, bond ID, and score corresponding to the condition code of the condition that matches the name matching condition master 106a.

[0028] The calculation unit 102c refers to the name identification condition master 106a and calculates the total points for each bond ID based on the name identification detailed data generated by the first generation unit 102b.

[0029] The first determination unit 102d determines whether or not there is a record of a bond whose total points is less than the cutoff bar, which is a first threshold value, for each record of the bond ID in the name aggregation detailed data.

[0030] The second determination unit 102e determines whether or not the total score is equal to or greater than the second threshold value, ie, the name identification bar, and whether or not there is one record of the corresponding bond, for each record of the name identification detailed data for each bond ID.

[0031] The second generation unit 102f generates name merge result data indicating that the name merge was unsuccessful. When the first determination unit 102d determines that the record is for a bond whose predetermined bond ID in the name merge detail data is less than the cutoff bar, the second generation unit 102f references the transfer deposit data 106c and generates name merge result data including a record for which the name merge was unsuccessful. Furthermore, when the second determination unit 102e determines that the record is for a bond whose predetermined bond ID in the name merge detail data is equal to or greater than the name merge bar and for which one record has been generated, the second generation unit 102f references the transfer deposit data 106c and generates name merge result data including a record for which the name merge was successful.

[0032] The deposit reconciliation processor 102g updates only those records in the name merge result data for which the name merge result is "success" to suspense data in bulk, based on the name merge result data, suspense data, and transfer deposit data. The deposit reconciliation processor 102g also identifies the deposit SEQ and deposit date in the name merge result data from the deposit SEQ and deposit date in the suspense receipt data, and updates the suspense receipt data by identifying the reconciled amount from the transaction amount of the transfer deposit data based on the company's account code, execution date, and record SEQ in this name merge result data.

[0033] The extraction unit 102h extracts records (details) for which the name matching has failed and the settlement has not been completed, based on the name matching result data, the provisional receipt data, and the transfer deposit data.

[0034] The display control unit 102i displays a transfer deposit file import screen that is displayed on the monitor 114 during the transfer deposit file import process by the name identification management device 100. The display control unit 102i also displays a transfer deposit confirmation screen P2 on the monitor 114.

[0035] [2. Name matching process executed by the name matching management device] Next, a description will be given of the name merging process executed by the name merging management device 100. FIG.

[0036] As shown in FIG. 4, first, the name identification management device 100 performs a transfer deposit file import process for importing transfer deposit data (step S1).

[0037] 5 is a diagram showing an example of a transfer deposit file import screen that the display control unit 102i causes to be displayed on the monitor 114 during the transfer deposit file import process. As shown in FIG. 5, the display control unit 102i causes the name matching management device 100 to display a transfer deposit file import screen P1 on the monitor 114 during the transfer deposit file import process.

[0038] 5, the transfer deposit file import screen P1 includes an execution date cell K1 in which the execution date can be input, a company account code cell K2 in which the company account code can be input, and an import file cell K3 in which the address of the transfer deposit data file can be input. Furthermore, the transfer deposit file import screen P1 includes a cancel button B1 for issuing a cancellation instruction, an execute button B2 for issuing an execution instruction, and a close button B3 for issuing an instruction to close the transfer deposit file import screen P1.

[0039] 5, when the user enters data into the execution date cell K1, company account code cell K2, and import file cell K3 via the input device 112 and presses the execute button B2, the import unit 102a imports the file specified by the user entering data into the import file cell K3 via the input device 112, line by line, and updates the transfer deposit data. In this case, the import unit 102a generates temporary receipt data according to the number of transfer deposit data imported.

[0040] 6 is a diagram showing an example of a transfer deposit data table for transfer deposit data. As shown in the transfer deposit data table T3 in FIG. 6, the company's account code is stored in association with the execution date, record SEQ (sequence), transaction amount, transfer request code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit SEQ (sequence). Specifically, the first row of the transfer deposit data table T3 stores the company's account code "1" in association with the execution date "2023 / 1 / 10," record SEQ "1," transaction amount "100,500," transfer requester name "Tanaka Taro," sending bank name "Bank A," sending branch name "Head Office," transfer destination account number "2000001," deposit date "2023 / 1 / 10," and deposit SEQ "1."

[0041] Figure 7 is a diagram showing an example of a suspense receipt data table for suspense receipt data. As shown in the suspense receipt data table T4 in Figure 7, the deposit date is associated with the deposit sequence (SEQ), deposit amount, deposit route, reconciled amount, and reconciliation completion flag. Specifically, the first row of the suspense receipt data table T4 shown in Figure 7 associates the deposit date "2023 / 1 / 10" with the deposit sequence "1," the deposit amount "100,500," the deposit route "2: Transfer deposit," the reconciled amount "0," and the reconciliation completion flag "0."

[0042] Returning to FIG. 4, the description of step S2 and subsequent steps will be continued. In step S2, the name matching management device 100 performs a name matching process to identify the target credit data based on the transfer deposit data, and executes a transfer deposit confirmation process to update the results of the name matching process to name matching result data.

[0043] FIG. 8 is a diagram showing an example of a transfer deposit confirmation screen that the display control unit 102i causes the monitor 114 to display during the name merge check implementation process. As shown in FIG. 8, the display control unit 102i causes the monitor 114 to display a transfer deposit confirmation screen P2. The transfer deposit confirmation screen P2 includes an execution date cell K10 in which an execution date can be entered and a company account code cell K11 in which a company account code can be entered. Furthermore, the transfer deposit confirmation screen P2 includes a cancel button B1 for issuing a cancellation instruction, an execute button B2 for issuing an execution instruction, and a close button B3 for issuing an instruction to close the transfer deposit file import screen P1. As shown in FIG. 8, when the user enters "2023 / 1 / 10" in the execution date cell K1 and "1" in the company account code cell K11 via the input device 112 and then presses the execute button B2, the name merge management device 100 executes the transfer deposit confirmation process.

[0044] [Details of the transfer payment confirmation process] Here, the details of the transfer confirmation process in step S2 will be described below. Fig. 9 is a flowchart showing the details of the transfer confirmation process.

[0045] As shown in FIG. 9, first, the import unit 102a acquires the name collation condition master 106a (step S11), and acquires the transfer deposit control master 106b (step S12).

[0046] Next, the first generating unit 102b sets the variable and the implementation level to 1 (step S13).

[0047] Thereafter, the first generation unit 102b refers to the name matching condition master 106a and performs a name matching check based on the transfer deposit data 106c and the bond data 10d to generate name matching detailed data that associates the company's account code with the execution date, record SEQ, condition code of the condition that matches the name matching condition master 106a, name matching SEQ, bond ID, and score corresponding to the condition code of the condition that matches the name matching condition master 106a (step S14).

[0048] FIG. 10 is a diagram showing an example of a name matching condition table for name matching conditions. The name matching condition table T5 shown in FIG. 10 indicates details of the name matching conditions when the first generation unit 102b refers to the name matching condition master 106a and generates detailed name matching data based on the transfer deposit data and the credit data. Specifically, as shown in FIG. 10, the name matching condition table T5 stores name matching conditions and matching conditions in association with No. For example, the first row of the name matching condition table T5 stores No. "1" in association with the name matching condition "Name matching" and the matching condition "Transfer deposit data. Transfer requester name in kana = credit data. Customer name in kana (0-padded to the 10th digit)."

[0049] Figure 11 is a diagram showing an example of a transfer deposit data table for transfer deposit data. The transfer deposit data table T10 shown in Figure 11 stores the company's account code in association with the execution date, record SEQ (sequence), transaction amount, transfer request code, transferor name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit SEQ (sequence). Note that the transfer deposit data table T10 is similar to the transfer deposit data table T3 in Figure 6 described above, so a detailed description will be omitted.

[0050] Figure 12 is a diagram showing an example of a claim data table in claim data. As shown in Figure 12, claim data table T11 stores a claim ID in association with a customer ID, a customer name in kana, the account bank name, the account branch name, a virtual account number, and a claim amount. Specifically, the first row of claim data table T11 stores a claim ID "100001" in association with a customer ID "100," a customer name in kana "Tanaka Taro," the account bank name "Bank A," the account branch name "Fukuoka Branch," a virtual account number "2000001," and a claim amount "100,500."

[0051] Figure 13 is a diagram showing an example of a detailed name merge data table in the detailed name merge data. As shown in Figure 13, the detailed name merge data table T12 stores the company's account code in association with an execution date, a record SEQ (sequence), a condition code, a merge SEQ (sequence), a bond ID, and points. Specifically, the first row of the detailed name merge data table T12 stores the company's account code "1" in association with the execution date "2023 / 1 / 10", a record SEQ "1", a condition code "1: name merge", a merge SEQ "1", a bond ID "100001", and points "6".

[0052] In this way, the first generation unit 102b generates detailed merge data for each bond ID that matches the merge conditions (see detailed merge data table T12 in Figure 13) based on the merge condition master 106a (the merge condition master table T1 shown in Figure 2 and the merge match condition table T5 in Figure 10), the transfer deposit data 106c (see the transfer deposit data table T10 in Figure 11), and the bond data 106d (see the bond data table T11 in Figure 12). Note that in Figures 11 and 12, different hatching is used to represent each item that matches the merge conditions.

[0053] Next, the calculation unit 102c refers to the name identification condition master 106a and calculates the total points for each bond ID based on the name identification detailed data generated by the first generation unit 102b.

[0054] FIG. 14 is a diagram showing a schematic overview of a method for calculating the total points for each bond ID by the calculation unit 102c.

[0055] 14, the calculation unit 102c refers to the name-merge condition master 106a and generates a total result data table T13 that calculates the total score for each bond ID based on the name-merge detailed data table T12 generated by the first generation unit 102b. Specifically, in the case of bond ID "10001," the calculation unit 102c adds up the scores in the first and ninth rows of the name-merge detailed data table T12 to calculate a total score of "12" for the bond ID "100001." Similarly, if there is a duplicate bond ID in the name-merge detailed data table T12, the calculation unit 102c adds up the scores for, for example, bond ID "100003" to calculate a total score of "9."

[0056] Returning to FIG. 9, the description of step S15 and subsequent steps will be continued. In step S15, the first determination unit 102d determines whether or not there is a record of a bond whose total point is less than the first threshold, which is the cutoff bar, for each record of the bond ID in the name merger detailed data. If the first determination unit 102d determines that there is a record of a bond whose total point is less than the first threshold, which is the cutoff bar (step S15: Yes), the name merger management device 100 proceeds to step S16. On the other hand, if the first determination unit 102d determines that there is no record of a bond whose total point is less than the first threshold, which is the cutoff bar (step S15: No), the name merger management device 100 proceeds to step S17.

[0057] In step S16, the second generating unit 102f generates the name identification result data as a name identification failure.

[0058] FIG. 15 is a diagram illustrating an example of the name merge result data table for the name merge result data when the name merge fails.

[0059] 15, when the first determination unit 102d determines that the bond ID "100002" in the total result data table T13 is a record of a bond below the cutoff bar (total points < 5), the second generation unit 102f references the transfer deposit data 106c and generates name merge result data including a record of name merge failure. Specifically, the second generation unit 102f references the transfer deposit data 106c, and obtains the deposit date and deposit SEQ based on the company's account code, execution date, and record SEQ, and generates a name merge result data table T14 in which the name merge result item for bond ID "100002" is set to "merge failure." More specifically, the second generation unit 102f generates the name matching result data table T14 by associating the execution date "2023 / 1 / 10", record SEQ "2", name matching result "2: Failed", bond ID " ", deposit date "2023 / 1 / 10", and deposit SEQ "2" with the company's account code "1". Note that the bond ID is left blank (blank) because the name matching failed. Furthermore, the deposit date and deposit SEQ are items to be linked to the provisional receipt data when canceling the deposit, as described below. After step S16, the name matching management device 100 returns to the main routine of Figure 4.

[0060] Returning to FIG. 9, the description of step S17 and subsequent steps will be continued. In step S17, the second determination unit 102e determines, for each record of each bond ID in the name merge detailed data, whether the total score is equal to or greater than the second threshold value, the name merge bar, and whether one record exists for the corresponding bond. If the second determination unit 102e determines that the total score is equal to or greater than the second threshold value, the name merge bar, and whether one record exists for the corresponding bond (step S17: Yes), the name merge management device 100 proceeds to step S18. On the other hand, if the second determination unit 102e determines that the total score is equal to or greater than the second threshold value, the name merge bar, and whether one record exists for the corresponding bond (step S17: No), the name merge management device 100 proceeds to step S19.

[0061] In step S18, the second generating unit 102f generates the name identification result data as a result of successful name identification.

[0062] FIG. 16 is a diagram showing an example of the name merge result data table in the name merge result data generated by the second generating unit 102f when the name merge is successful.

[0063] As shown in FIG. 16, if the second determination unit 102e determines that the bond ID "100001" in the total result data table T13 is equal to or greater than the name matching bar (total score ≧10) and that the corresponding bond is a record for a bond for which one record has been generated, the second generation unit 102f references the transfer deposit data 106c and generates name matching result data including a record for which name matching was successful. Specifically, the second generation unit 102f references the transfer deposit data 106c and, based on the company's account code, execution date, and record sequence, obtains the deposit date and deposit sequence, and incorporates the record for which the name matching result field for the bond ID "100001" is determined to be successful into the name matching result data table T14 (see FIG. 15) to generate an updated name matching result data table T15. After step S18, the name matching management device 100 returns to the main routine of FIG. 4.

[0064] Returning to FIG. 9, the description of step S19 and subsequent steps will be continued. In step S19, the second determination unit 102e determines whether the current name merge variable.implementation level is the maximum value of the implementation level of the name merge condition master 106a (variable.implementation level = name merge condition master 106a.implementation level). Specifically, the second determination unit 102e determines whether the current name merge variable.implementation level is the maximum value of the implementation level of the name merge condition master 106a, for example, implementation level "2" (see the name merge condition master table T1 in FIG. 2). If the second determination unit 102e determines that the current name merge variable.implementation level is the maximum value of the implementation level of the name merge condition master 106a (step S19: Yes), the name merge management device 100 proceeds to step S21. On the other hand, if the second determination unit 102e determines that the current name merge variable.implementation level is not the maximum value of the implementation level of the name merge condition master 106a (step S19: No), the name merge management device 100 proceeds to step S20.

[0065] In step S20, the first generation unit 102b adds 1 to the current name matching variable.implementation level. For example, if the current name matching variable.implementation level is "1", the first generation unit 102b changes the current name matching variable.implementation level to "2" by adding "1". After step S20, the name matching management device 100 returns to step S14. In this case, the name matching management device 100 performs the processes of steps S15 to S18 according to the name matching variable.implementation level "2".

[0066] Here, an overview of the name merge check according to the name merge variable implementation level "2" will be described. Fig. 17 is a diagram showing an example of the name merge data table in the name merge detailed data other than the details updated to the name merge result data.

[0067] As shown in Figure 17, the first generation unit 102b generates detailed merge data for each bond ID that matches the merge conditions for the details of the transfer deposit data 106c other than the details updated in the merge result data, based on the merge condition master 106a (the merge condition master table T1 shown in Figure 2 and the merge match condition table T5 in Figure 10), the transfer deposit data 106c (see the transfer deposit data table T10 in Figure 11), and the bond data 106d (see the bond data table T11 in Figure 12). That is, the first generation unit 102b generates detailed merge data table T21 by adding records with condition code "5: invoice amount" to the records of the above-mentioned detailed merge data table T12 (see Figure 13).

[0068] Next, the calculation unit 102c refers to the name identification condition master 106a and calculates the total points for each bond ID based on the name identification detailed data generated by the first generation unit 102b at implementation level "2."

[0069] FIG. 18 is a diagram showing an example of a total result table calculated by the calculation unit 102c for each bond ID at implementation level "2."

[0070] 18, in the case of bond ID "10001," the calculation unit 102c calculates a total score of "13" for bond ID "100003" by adding up the scores in the second, seventh, and ninth rows of the detailed name-merger data table T21. Similarly, if there is a duplicate bond ID in the detailed name-merger data table T21, the calculation unit 102c adds up the scores for bond ID "100004," for example, to calculate a total score of "10."

[0071] At the name matching implementation level "2", the first judgment unit 102d checks for details of failed name matching using the first threshold, which is the cutoff bar, but details that fall below the cutoff bar have already been created (updated) as records of the name matching result data, and there are no targets, so detailed explanations are omitted.

[0072] Thereafter, if the second judgment unit 102e judges that the total score for each bond ID in the name matching detailed data other than those that have been updated in the name matching result data is equal to or greater than the second threshold value, the name matching bar, and that one record of the corresponding bond has been generated, the second generation unit 102f generates the name matching result data as a successful name matching.

[0073] FIG. 19 is a diagram showing an example of the name merge result data table in the name merge result data when the name merge is successful, which is generated by the second generating unit 102f at implementation level "2."

[0074] 19, when the second determination unit 102e determines that the bond ID "100005" in the name merge detail data table T22 is equal to or greater than the name merge bar (total score ≧ 10) and that the corresponding bond is a record of a bond with only one record (details), the second generation unit 102f references the transfer deposit data 106c and generates name merge result data including a record of successful name merge. Specifically, the second generation unit 102f references the transfer deposit data 106c and obtains the deposit date and deposit SEQ based on the company's account code, execution date, and record SEQ, and incorporates the record for which the name merge result field for bond ID "100005" is determined to be successful into the name merge result data table T15 (see FIG. 16) and updates it to generate a name merge result data table T23. More specifically, the second generation unit 102f generates the name merge result data table T23 by associating the execution date "2023 / 1 / 10", record SEQ "4", name merge result "1: Success", bond ID "100005", deposit date "2023 / 1 / 10", and deposit SEQ "4" with the company's account code "1". After step S23, the name merge management device 100 returns to the main routine of FIG. 4.

[0075] Returning to FIG. 9, the description of step S21 and subsequent steps will be continued. In step S21, the second determination unit 102e determines whether or not there is a record in the name merge result data for each bond ID in the name merge detailed data other than those that have been updated, in which the total score is less than the second threshold value, the name merge bar (total score<name merge bar). If the second determination unit 102e determines that there is a record in which the total score is less than the second threshold value, the name merge bar (step S21: Yes), the name merge management device 100 proceeds to step S22. On the other hand, if the second determination unit 102e determines that there is no record in which the total score is less than the second threshold value, the name merge bar (step S21: No), the name merge management device 100 proceeds to step S23.

[0076] In step S22, the second generating unit 102f generates the name identification result data as a name identification failure.

[0077] FIG. 20 is a diagram showing an example of the name merge result data table for the name merge result data when name merge fails at implementation level "2."

[0078] 20, when the second determination unit 102e determines that the bond ID "100006" in the name merge detail data table T22 is a record of a bond whose total points is less than the name merge bar (total points < 10), the second generation unit 102f references the transfer deposit data 106c and generates name merge result data including a record of name merge failure. Specifically, the second generation unit 102f references the transfer deposit data 106c and obtains the deposit date and deposit SEQ based on the company's account code, execution date, and record SEQ, and incorporates the record whose name merge result field for bond ID "100006" is set to "merger failure" into the name merge result data table T23 (see FIG. 19) and updates it to generate a name merge result data table T24. More specifically, the second generation unit 102f generates the name matching result data table T24 by associating the execution date "2023 / 1 / 10", record SEQ "5", name matching result "2: Failed", bond ID " ", deposit date "2023 / 1 / 10", and deposit SEQ "5" with the company's account code "1". Note that the bond ID is left blank (blank) because the name matching failed. Furthermore, the deposit date and deposit SEQ are items to be linked to the provisional receipt data when canceling the deposit, as described below. After step S22, the name matching management device 100 returns to the main routine of Figure 4.

[0079] In step S23, the second determination unit 102e determines whether there are records for each bond ID in the name merge detailed data other than those that have been updated in the name merge result data in which there are multiple matching bonds with a total score equal to or greater than the name merge bar, and whether there are any records in which the setting value of the multiple matching judgment category in the transfer deposit control master 106b is "1." If the second determination unit 102e determines that there are any records in which the setting value of the multiple matching judgment category in the transfer deposit control master 106b is "1" (step S23: Yes), the name merge management device 100 proceeds to step S24. On the other hand, if the second determination unit 102e determines that there are no records in which the setting value of the multiple matching judgment category in the transfer deposit control master 106b is "1" (step S23: No), the name merge management device 100 proceeds to step S25.

[0080] In step S24, the second generation unit 102f generates name matching result data by considering the record with the higher score as a successful name matching among the records for each bond ID in the name matching detailed data that have not been updated in the name matching result data, where there are multiple corresponding bonds whose total score is equal to or greater than the name matching bar.

[0081] FIG. 21 is a diagram showing an example of a name-merge result data table for name-merge result data in the case where there are multiple relevant loans with a total score equal to or greater than the name-merge bar when name-merge is successful at implementation level "2."

[0082] 21, when the second determination unit 102e determines that there are multiple bond IDs "100003" and "100004" for record SEQ "3" in the detailed name merge data table T22, the second generation unit 102f refers to the transfer deposit data 106c, adopts the one with the higher score, and generates name merge result data including a record for which name merge was successful. Specifically, the second generation unit 102f refers to the transfer deposit data 106c, and obtains the deposit date and deposit SEQ based on the company's account code, execution date, and record SEQ, and incorporates the record for which the name merge result field for bond ID "100005" is determined to be successful into the name merge result data table T24 (see FIG. 20) and updates it to generate a name merge result data table T25. More specifically, the second generation unit 102f generates the name merge result data table T25 by associating the execution date "2023 / 1 / 10", record SEQ "3", name merge result "1: Success", bond ID "100003", deposit date "2023 / 1 / 10", and deposit SEQ "3" with the company's account code "1". After step S24, the name merge management device 100 returns to the main routine of FIG. 4.

[0083] In step S25, the second generation unit 102f generates name matching result data for records for each bond ID in the name matching detailed data other than those that have been updated to the name matching result data by the second judgment unit 102e, by treating the record with the higher score as a name matching failure among records that have multiple corresponding bonds with a total score equal to or greater than the name matching bar.

[0084] FIG. 22 is a diagram showing an example of a name-merge result data table for name-merge result data in the case where there are multiple relevant loans with a total score equal to or greater than the name-merge bar when name-merge fails at implementation level "2."

[0085] 22, when the second determination unit 102e determines that there are multiple bond IDs "100003" and "100004" for record SEQ "3" in the name merge detail data table T22, the second generation unit 102f refers to the transfer deposit data 106c, adopts the one with the higher score, and generates name merge result data including a record of name merge failure. Specifically, the second generation unit 102f refers to the transfer deposit data 106c, and obtains the deposit date and deposit SEQ based on the company's account code, execution date, and record SEQ, and incorporates the record for bond ID "100006" with the name merge result field set to "merge failure" into the name merge result data table T24 (see FIG. 20) and updates it to generate a name merge result data table T26. More specifically, the second generation unit 102f generates the name merge result data table T26 by associating the execution date "2023 / 1 / 10", record SEQ "3", name merge result "2: Failed", bond ID "100003", deposit date "2023 / 1 / 10", and deposit SEQ "3" with the company's account code "1". After step S22, the name merge management device 100 returns to the main routine of FIG. 4.

[0086] In this way, the name matching management device 100 performs a name matching process to identify the target credit data based on the transfer deposit data, and executes a transfer deposit confirmation process to update the results of the name matching process into name matching result data.

[0087] Returning to FIG. 4, the description of step S3 and subsequent steps will be continued. In step S3, the name matching management device 100 executes a payment reconciliation process in which the payment is reconciled collectively for the details for which the name matching was successful, and the payment is reconciled manually for the details for which the name matching failed. After step S3, the name matching management device 100 ends this process.

[0088] First, we will explain the lump-sum payment reconciliation process for details for which name identification was successful. Fig. 23 is a diagram illustrating the association of the name matching result data, temporary receipt data, and transfer deposit data before the execution of the deposit reconciliation process. Fig. 24 is a diagram showing an example of a lump-sum deposit reconciliation screen that the display control unit 102i causes the monitor 114 to display during the deposit reconciliation process. Fig. 25 is a diagram showing an example of a temporary receipt data table for the temporary receipt data after the execution of the deposit reconciliation process.

[0089] As shown in Figure 24, we will explain the case where the user enters "2023 / 01 / 10" into the execution date cell K10 and "1" into the company's account code cell K11 on the lump-sum deposit reconciliation screen P3 via the input device 112, and then presses the execute button B2. In this case, as shown in Figures 23 and 25, the deposit reconciliation processing unit 102g updates the temporary receipt data table T4 only for records in the name merge result data table T26 that have a name merge result of "1: successful" based on the name merge result data table T26, the temporary receipt data table T4, and the transfer deposit data table T3 (Figures 23 to 25). Specifically, the deposit reconciliation processing unit 102g identifies records in the name merge result table T26 that have a name merge result of "1: successful" based on the deposit date and deposit sequence in each of the temporary receipt data table T4 and the transfer deposit data table T3, and then identifies the reconciled amount from the transfer deposit data table T3 based on the company's account code, execution date, and record sequence in the name merge result data, and updates the temporary receipt data table T4.

[0090] For example, the deposit reconciliation processing unit 102g identifies the deposit SEQ "1" and deposit date "2023 / 1 / 10" in the name identification result data table T26 from the deposit SEQ "1" and deposit date "2023 / 1 / 10" in the suspense receipt data table T4, and then identifies the reconciled amount "100,500" from the transaction amount "100,500" in the transfer deposit data table T3 based on the company's account code "1," execution date "2023 / 1 / 10," and record SEQ "1" in this name identification result data table T26, and updates the suspense receipt data table T4. In this case, the deposit reconciliation processing unit 102g updates the reconciliation completion flag in the suspense receipt data table T4 to "1."

[0091] As a result, the name identification management device 100 can perform payment settlement processing in a lump sum for details for which name identification has been successfully performed.

[0092] Next, we will explain the payment settlement process for details for which name matching has failed. Fig. 26 is a diagram illustrating the association of name matching result data, suspense receipt data, and transfer deposit data before the execution of the deposit reconciliation process. Fig. 27 is a diagram showing an example of a suspense receipt list screen that the display control unit 102i causes the monitor 114 to display during the deposit reconciliation process. Fig. 28 is a diagram showing an example of an individual deposit reconciliation screen that the display control unit 102i causes the monitor 114 to display during the deposit reconciliation process. Fig. 29 is a diagram showing an example of a suspense receipt data table in the suspense receipt data after the execution of the deposit reconciliation process.

[0093] The provisional receipt list screen P4 shown in Figure 27 includes a company account code cell K21 in which the company's account code can be entered, a deposit route code cell K22 in which the deposit route code can be entered, an import date cell K23 in which the import date can be entered, an incomplete check box K24 that extracts records with an incomplete reconciliation completion flag, and a completed check box K25 that extracts records with a completed reconciliation completion flag.

[0094] When the user enters "1" in the company account code cell K21, "2" in the deposit route code cell K22, and "2023 / 1 / 10" in the import date cell K23 via the input device 112, and then selects the incomplete check box K24, the extraction unit 102h extracts records (details) for which name matching has failed and reconciliation has not been completed, based on the name matching result data, temporary receipt data, and transfer deposit data. At this time, the display control unit 102i displays the detail table Q1 corresponding to the extraction result extracted by the extraction unit 102h on the temporary receipt list screen P4. In this case, when the user selects the detail F1 to be reconciled in the detail table Q1 via the input device 112, the display control unit 102i transitions to the individual deposit reconciliation processing screen P5 (FIG. 27 → FIG. 28).

[0095] Thereafter, when the user presses the execute button B2 via the input device 112, the deposit reconciliation processing unit 102g obtains the transfer deposit data based on the company's account code, import date, and record SEQ, and identifies the target provisional receipt data based on the deposit date and deposit SEQ of the transfer deposit data, and updates the provisional receipt data table T4.

[0096] 29, the deposit reconciliation processor 102g identifies the deposit SEQ "2" and deposit date "2023 / 1 / 10" in the name identification result data table T26 from the deposit SEQ "2" and deposit date "2023 / 1 / 10" in the suspense receipt data table T4, and then identifies the reconciled amount "130,250" from the transaction amount "130,250" in the transfer deposit data table T3 based on the company's account code "1," execution date "2023 / 1 / 10," and record SEQ "2" in this name identification result data table T26, and updates the suspense receipt data table T4. In this case, the deposit reconciliation processor 102g updates the reconciliation completion flag in the suspense receipt data table T4 to "1."

[0097] This allows the name identification management device 100 to manually perform payment reconciliation processing for details for which name identification has failed.

[0098] According to the embodiment described above, the second generation unit 102f generates name matching result data that associates the execution date, record sequence and name matching result, bond ID, deposit date and deposit date sequence with the company's own account code based on the result of the first judgment process by the first judgment unit 102d and the result of the second judgment process by the second judgment unit 102e, thereby enabling flexible and accurate name matching.

[0099] Furthermore, according to the embodiment, when the second generation unit 102f determines by the second judgment unit 102e that the total score for the name matching detailed data is equal to or greater than the value of the name matching bar and that the relevant debt is one item, the second generation unit 102f generates name matching result data with the total score being equal to or greater than the value of the name matching bar and the relevant debt being one item as successful name matching, and therefore, by being able to flexibly change the name matching method, the success rate of name matching can be improved.

[0100] Furthermore, according to the embodiment, when the second generation unit 102f determines that the total score for the detailed name matching data is less than the value of the cutoff bar by the first judgment unit 102d, the second generation unit 102f generates name matching result data by treating the details whose total score is determined to be less than the value of the cutoff bar as a name matching failure, and therefore, by being able to flexibly change the name matching method, the success rate of name matching can be improved.

[0101] Furthermore, according to the embodiment, when the second generation unit 102f determines by the second judgment unit 102e that the total score for the name matching detailed data is equal to or greater than the value of the name matching bar and that the relevant receivable has multiple details, the name matching result data is generated as a name matching success or failure depending on the setting value of the judgment category for multiple matches in the transfer deposit control master 106b, so that it can be flexibly adapted to the name matching requirements of each company.

[0102] Furthermore, according to the embodiment, the deposit reconciliation processing unit 102g performs the deposit reconciliation process by storing the reconciled amount in the provisional receipt data only for details for which the name matching result was successful, based on the transfer deposit data 106c, the name matching result data, and the provisional receipt data, so that deposit reconciliation can be performed all at once for deposit details for which the name matching was successful and which have a high degree of reliability.

[0103] Furthermore, according to the embodiment, the deposit reconciliation processing unit 102g stores the reconciled amount of the details for which the name matching has failed in the provisional receipt data and performs the deposit reconciliation process based on the details for which the name matching has failed extracted by the extraction unit 102h and the receivables data 106d corresponding to the specified record sequence, import date and deposit customer name, so that the deposit reconciliation process can be performed by manually specifying the deposit details for which the name matching has failed.

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

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

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

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

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

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

[0110] Furthermore, with regard to the name identification management 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.

[0111] For example, all or any part of the processing functions of the name identification management 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 name identification management 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.

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

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

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

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

[0116] The name matching management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The name matching management 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.

[0117] 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]

[0118] The present invention is useful for businesses in industries that perform settlement of accounts receivable by identifying customers. [Explanation of symbols]

[0119] 100 Name matching management device 102 Control section 102a Intake section 102b First generation unit 102c Calculation section 102d First Judgment Section 102e Second judgment unit 102f Second generation unit 102g Payment Reconciliation Processing Unit 102h Extraction part 102i Display Control Unit 104 Communication interface unit 106 Storage section 106a Name matching condition master 106b Transfer deposit control master 106c Transfer deposit data 106d Bond Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A name identification management device including a control unit, a name matching condition master in which a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching are associated with a condition code; a transfer deposit control master in which the value of a cutoff bar indicating a failure in name matching, the value of a name matching bar indicating a success in name matching, and a setting value of a judgment category for multiple matches indicating whether to adopt the receivable with the highest score or to treat the receivable as a name matching failure when multiple matches are made; Transfer deposit data in which the execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with the company's account code; Debt data in which a customer ID, a customer name, a bank name, a branch name, a virtual account number, and a claim amount are associated with the debt ID; is accessible to The control unit a first generation unit that refers to the name matching condition master and generates name matching detailed data based on the transfer deposit data and the bond data, in which the bond ID and a score corresponding to the condition code of the condition that matches the name matching condition master are associated; a calculation unit that calculates a total score for each of the bond IDs based on the detailed name identification data; a first determination unit that performs a first determination process that refers to the transfer deposit control master and determines whether or not the total points for each bond ID are less than the value of the cutoff bar; a second determination unit that performs a second determination process that refers to the transfer deposit control master and determines whether or not the total score for each bond ID is equal to or greater than the value of the name identification bar; a second generation unit that generates name identification result data in which the execution date, record sequence, name identification result, the bond ID, deposit date, and deposit date sequence are associated with the company's own account code based on the result of the first determination process and the result of the second determination process; Equipped with The second generation unit When the second determination unit determines that the total score for the detailed name identification data is equal to or greater than the value of the name identification bar and that the relevant bond is one item, it generates the name identification result data by determining that the total score is equal to or greater than the value of the name identification bar and that the relevant bond is one item as successful name identification; when the first determination unit determines that the total score for the detailed name identification data is less than the value of the cutoff bar, the details for which the total score is less than the value of the cutoff bar are deemed to be name identification failures and the name identification result data is generated; A name matching management device characterized by the above.

2. The name identification management device according to claim 1, The second generation unit When the second determination unit determines that the total score for the name matching detailed data is equal to or greater than the value of the name matching bar and that the relevant receivables have multiple details, the name matching result data is generated as a name matching success or failure according to the setting value of the multiple matching judgment category in the transfer deposit control master. A name matching management device characterized by the above.

3. 3. The name identification management device according to claim 2, The second generation unit When the total score for the name matching detailed data is equal to or greater than the value of the name matching bar, the relevant receivables are multiple details, and the setting value of the judgment category for multiple matches in the transfer deposit control master is name matching success, the second judgment unit generates the name matching result data as the name matching result data, regarding the details with the higher total score as name matching success, the second judgment unit, when the total score for the name matching detailed data is equal to or greater than the value of the name matching bar, the relevant receivables are multiple details, and the setting value of the judgment category for multiple matches in the transfer deposit control master is name matching failure, generates the details with the higher total score as the name matching result data as name matching failure; A name matching management device characterized by the above.

4. The name identification management device according to claim 3, The control unit a payment reconciliation processing unit that performs payment reconciliation processing by storing the reconciled amount of a line item for which the name matching result was successful based on the transfer payment data, the name matching result data, and the provisional receipt data, in the provisional receipt data; A name matching management device characterized by the above.

5. The name identification management device according to claim 4, an extraction unit that extracts details for which name identification has failed from the name identification result data; The extraction unit Extracting the details for which the name matching has failed and the bond data corresponding to the specified record sequence, the import date, and the name of the customer receiving the payment; The deposit reconciliation processing unit Based on the details for which name matching has failed extracted by the extraction unit and the credit data corresponding to the specified record sequence, import date, and deposit customer name, storing the cleared amount of the details for which name matching has failed in the provisional receipt data and performing a deposit clearing process; A name matching management device characterized by the above.

6. A name identification management method executed by a name identification management device having a control unit, The name identification management device a name matching condition master in which a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching are associated with a condition code; a transfer deposit control master in which the value of a cutoff bar indicating a failure in name matching, the value of a name matching bar indicating a success in name matching, and a setting value of a judgment category for multiple matches indicating whether to adopt the receivable with the highest score or to treat the receivable as a name matching failure when multiple matches are made; Transfer deposit data in which the execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with the company's account code; Debt data in which a customer ID, a customer name, a bank name, a branch name, a virtual account number, and a claim amount are associated with the debt ID; is accessible to Executed by the control unit, a first generation step of generating detailed name merge data by referring to the name merge condition master and based on the transfer deposit data and the bond data, in which the bond ID and a score corresponding to the condition code of the condition matching the name merge condition master are associated; a calculation step of calculating a total score for each of the bond IDs based on the detailed name identification data; a first determination step of performing a first determination process of referring to the transfer deposit control master and determining whether or not the total points for each bond ID are less than the value of the cut-off bar; a second determination step of performing a second determination process of referring to the transfer deposit control master and determining whether or not the total score for each bond ID is equal to or greater than the value of the name identification bar; a second generation step of generating name identification result data in which execution dates, record sequences, name identification results, the bond IDs, deposit dates, and deposit date sequences are associated with the company's own account codes based on the results of the first determination process and the second determination process; Including, The second generating step If the second determination step determines that the total score for the detailed name identification data is equal to or greater than the value of the name identification bar and that the relevant claim is one item, the total score is equal to or greater than the value of the name identification bar and the relevant claim is one item, and generates the name identification result data, assuming that the name identification is successful; When the first determination step determines that the total score for the detailed name identification data is less than the value of the cutoff bar, the details for which the total score is less than the value of the cutoff bar are deemed to be name identification failures and the name identification result data is generated. A name matching management method characterized by the above.

7. A name identification management program to be executed by a name identification management device having a control unit, The name identification management device a name matching condition master in which a name matching condition name, an implementation level, a target flag, and a score indicating the reliability of the name matching are associated with a condition code; a transfer deposit control master in which the value of a cutoff bar indicating a failure in name matching, the value of a name matching bar indicating a success in name matching, and a setting value of a judgment category for multiple matches indicating whether to adopt the receivable with the highest score or to treat the receivable as a name matching failure when multiple matches are made; Transfer deposit data in which the execution date, record sequence, transaction amount, transfer requester code, transfer requester name, sending bank name, sending branch name, transfer destination account number, deposit date, and deposit sequence are associated with the company's account code; Debt data in which a customer ID, a customer name, a bank name, a branch name, a virtual account number, and a claim amount are associated with the debt ID; is accessible to To cause the control unit to execute a first generation step of generating detailed name merge data by referring to the name merge condition master and based on the transfer deposit data and the bond data, in which the bond ID and a score corresponding to the condition code of the condition matching the name merge condition master are associated; a calculation step of calculating a total score for each of the bond IDs based on the detailed name identification data; a first determination step of performing a first determination process of referring to the transfer deposit control master and determining whether or not the total points for each bond ID are less than the value of the cut-off bar; a second determination step of performing a second determination process of referring to the transfer deposit control master and determining whether or not the total score for each bond ID is equal to or greater than the value of the name identification bar; a second generation step of generating name identification result data in which execution dates, record sequences, name identification results, the bond IDs, deposit dates, and deposit date sequences are associated with the company's own account codes based on the results of the first determination process and the second determination process; Including, The second generating step If the second determination step determines that the total score for the detailed name identification data is equal to or greater than the value of the name identification bar and that the relevant claim is one item, the total score is equal to or greater than the value of the name identification bar and the relevant claim is one item, and generates the name identification result data, assuming that the name identification is successful; When the first determination step determines that the total score for the detailed name identification data is less than the value of the cutoff bar, the details for which the total score is less than the value of the cutoff bar are deemed to be name identification failures and the name identification result data is generated. A name matching management program that features:

Images