JP5890882B2 - Data collation apparatus, data collation method and program - Google Patents

Description

  The present invention relates to a data collation apparatus that collates deposit data and billing data, and further relates to a data collation method and a data collation program.

  In a company, accounts receivable receivable management is performed to confirm whether or not the money billed in the past has been deposited at a later date by collating the deposit data with the billing data. Some companies check thousands or tens of thousands of matches every month. Since the payment data normally includes data of the transfer person name, it is possible to determine who the payment is from using the transfer person name data. On the other hand, since the billing data includes data indicating who is billed, it is possible to determine which billing data the deposit data corresponds to. If the amounts of the corresponding deposit data and billing data match, the billed amount has been deposited without excess or deficiency, and therefore the corresponding deposit data and billing data are each subjected to an application process.

  In Patent Document 1 below, the name of the depositor in the deposit data is identified, the deposit source code is specified, the invoiced amount is summed at the deposit source, and the deposit amount matches the deposit amount within the transfer fee range. It is described that payment has been completed if the total amount charged does not match the deposit amount, and that each case is verified on a per-invoice basis.

  However, even if the name of the transfer person name is collected, there are cases where there are a plurality of corresponding customers, and the deposit source code cannot be specified. In Patent Document 1, in such a case, a name identification error occurs, and the subsequent verification work must be performed manually.

JP 2006-235795 A

  Therefore, the present invention provides a data collation apparatus, a data collation method, and a program capable of efficiently collating the deposit data with the billing data even when there are a plurality of customers corresponding to the transfer person name of the deposit data. With the goal.

In order to solve the above-described problem, a data collating apparatus according to one aspect of the present invention is provided.
A deposit data table including a plurality of records, a field for storing the transfer person name data, and a field for storing the transfer amount data for each record;
A customer data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing transfer name data;
A billing data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing billing amount data;
, A device for verifying the deposit data and the billing data,
A deposit data extraction means for extracting the data of the transfer person name and the data of the transfer amount for one record included in the deposit data table;
A customer data extraction means for searching the customer data table using the transfer person name data extracted from the payment data table and extracting the data of the customer ID stored in each of the corresponding records;
A billing data extracting means for searching the billing data table using the data of each customer ID extracted from the customer data table, and extracting the data of the billing amount stored in the corresponding record for each customer ID;
Compared to the billing amount data extracted from the billing data table for each customer ID with respect to the transfer amount data extracted from the deposit data table, this is applicable when there is billing amount data that satisfies a predetermined matching condition. Comparing means for performing a record clearing process and comparing with the billing amount data extracted from the billing data table for other customer IDs when there is no billing amount data satisfying a predetermined matching condition;
It comprises.

  According to the present invention, even when there are a plurality of customers corresponding to the transfer person name of the payment data, the transfer amount data extracted from the payment data table and the charge amount data extracted from the charge data table for each customer ID If there is no billing amount data satisfying a predetermined matching condition, the customer can be identified by comparing with the billing amount data extracted for other customer IDs. Can be efficiently verified.

It is a schematic block diagram of the data collation apparatus which concerns on one Embodiment of this invention. It is a figure which shows the data structural example (before collation) of the various data tables which a data collation apparatus can refer. It is a figure which shows the data structural example (after collation) of the various data tables updated by the data collation apparatus. It is a flowchart which shows the operation example of the data collation apparatus which concerns on the said embodiment. It is a flowchart which shows the detail of a matching process in case one customer ID is extracted in S3 of FIG. It is a flowchart which shows the detail of a matching process when multiple customer ID is extracted in S5 of FIG. 4 (I pieces).

  Hereinafter, a data collating apparatus according to an embodiment of the present invention will be described in detail with reference to the drawings.

<1. Configuration of data verification device>
FIG. 1 is a schematic configuration diagram of a data collating apparatus according to an embodiment of the present invention. The data verification device 1 is a computer device that can access a storage medium that stores a deposit data table 11, a customer data table 12, and a billing data table 13.
The data verification device 1 includes a deposit data extraction unit 21, a customer data extraction unit 22, a billing data extraction unit 23, a total value calculation unit 24, a minimum value selection unit 25, a comparison unit 26, and an output unit 27. And an input unit 28. Here, each configuration of the data verification device 1 is illustrated as being included in one computer device, but these configurations are distributed to separate computer devices, and the computer devices operate in cooperation with each other. It is also good.

FIG. 2 is a diagram illustrating a data configuration example (before collation) of various data tables that can be referred to by the data collation apparatus.
FIG. 3 is a diagram illustrating a data configuration example (after verification) of various data tables updated by the data verification device.

<1-1. Deposit Data Table 11>
The deposit data table 11 is created mainly from transfer data sent from a bank. The deposit data table 11 has a plurality of records specified by sequential numbers 111. Each record of the deposit data table 11 includes a field for storing the deposit date 112, a field for storing the transfer person name (Kana) 113, a field for storing the transfer amount 114, and a transfer source account number 115. , A field for storing the transfer source financial institution code 116, a field for storing the transfer source branch code 117, and a field for storing the application information 118. Yes.

  The payment date 112, the transfer person name (Kana) 113, and the transfer amount 114 are information that is usually added in bank transfer. On the other hand, the transfer source account number 115, the transfer source financial institution code 116, and the transfer source branch code 117 are information (arbitrary information) that is arbitrarily added in the bank transfer, and these arbitrary information is stored in the deposit data table 11. Not all records are stored.

The application information 118 is information indicating whether or not the data collation apparatus 1 according to the embodiment has confirmed that the payment data related to the record satisfies a predetermined matching condition with the billing data. As the revocation information 118, for example, information indicating which record in the billing data table 13 satisfies the predetermined matching condition by specifying the sequential number 131 of the billing data table 13 is stored. (See FIG. 3).
Alternatively, binary data (for example, 0 or 1) indicating whether or not it is confirmed that a predetermined matching condition is satisfied for the billing data may be stored as the consumption information 118.

<1-2. Customer Data Table 12>
The customer data table 12 stores information related to the customer of the user who uses the data verification device 1. The customer data table 12 has a plurality of records specified by sequential numbers 121. Each record of the customer data table 12 includes a field for storing a customer ID 122, a field for storing a transfer person name (kana) 123, a field for storing a transfer source account number 125, and a transfer source financial institution. A field for storing the code 126 and a field for storing the transfer source branch code 127 are included.

  Customer ID 122 is a character string assigned to uniquely identify a customer. The transfer person name (kana) 123 may be input by the operator based on the customer name, or may be input by the operator based on past transfer data from the customer. Further, for example, as shown in the first and second records of the customer data table 12, a plurality of transfer person names “A0” and “A1” may be input for the same customer ID “A001”.

  The transfer source account number 125, the transfer source financial institution code 126, and the transfer source branch code 127 are information stored based on the arbitrary information when these arbitrary information has been added in the past transfer from the customer. (See FIG. 3). Even when there are a plurality of records in which the transfer person name (Kana) 123 corresponding to the transfer person name (Kana) 113 of the deposit data table 11 is stored in the customer data table 12, the transfer source account number 125 and the transfer source financial institution code 126 are stored. Alternatively, the customer may be identified based on the transfer source branch code 127.

<1-3. Billing data table 13>
The billing data table 13 stores information on bills sent from the user using the data matching device 1 to the customer. The billing data table 13 has a plurality of records specified by sequential numbers 131. Each record of the billing data table 13 includes a field for storing a billing date 132, a field for storing a customer ID 133, a field for storing a billing amount 134, and a field for storing matter information 135. And a field for storing the application information 136 and a field for storing the partial deposit amount 137.

  The billing date 132 is the date of billing to the customer. The customer ID 133 is a character string corresponding to the customer ID 122 of the customer data table 12. The billing amount 134 is a billing amount to the customer, and stores, for example, the total amount of merchandise price, shipping fee and consumption tax. Or you may memorize | store the detail which shows the breakdown of a claim. The case information 135 is information related to the case that is the subject of the invoice, and for example, information such as the project name and the name of the person in charge on the customer side is stored.

The application information 136 is information indicating whether or not the payment from the customer corresponding to the billing data related to the record has been confirmed by the payment data by the data collating apparatus 1 according to the embodiment. As the application information 136, for example, information indicating which record in the deposit data table 11 satisfies the predetermined matching condition by specifying the sequential number 111 of the deposit data table 11 is stored. (See FIG. 3).
Alternatively, binary data (for example, 0 or 1) indicating whether or not payment has been confirmed may be stored as the application information 136.

  The partial deposit amount 137 is determined when the deposit amount from the customer corresponding to the billing data related to the record is only a part of the bill amount 134 and the remaining amount is scheduled to be deposited at a later date. This is information indicating the amount of money already spent. For example, when a deposit of ¥ 20,000 is confirmed by the deposit data out of the bill amount “¥ 50,000” related to the fourth record of the billing data table 13, the partial deposit amount 137 related to the fourth record of the billing data table 13. As for, the deposited amount “¥ 20,000” is stored.

<1-4. Deposit Data Extraction Unit 21>
Returning to FIG. 1, the deposit data extraction unit 21 has a function of extracting a transfer person name (kana) 113 and a transfer amount 114 for each record included in the deposit data table 11. The deposit data extraction unit 21 can further extract the transfer source account number 115, the transfer source financial institution code 116 or the transfer source branch code 117 for each record included in the deposit data table 11.
Note that in the extraction of data from the deposit data table 11, the data of the record that has been subjected to the application process is not extracted.

<1-5. Customer Data Extractor 22>
The customer data extraction unit 22 has a function of searching the customer data table 12 using the transfer person name (kana) 113 extracted from the deposit data table 11 and extracting the customer ID 122 stored in each corresponding record. If a plurality of records are found as a result of the search, a plurality of customer IDs 122 are extracted correspondingly.
If a plurality of records are found as a result of the search and the transfer source account number 115, transfer source financial institution code 116 or transfer source branch code 117 is extracted from the deposit data table 11, the customer data The extraction unit 22 narrows down the corresponding records in the customer data table 12 using the transfer source account number 115, the transfer source financial institution code 116, or the transfer source branch code 117 extracted from the deposit data table 11, and sets the customer ID 122. Extract.

<1-6. Billing data extraction unit 23>
The billing data extraction unit 23 searches the billing data table 13 using each customer ID 122 extracted from the customer data table 12, and for each customer ID 133 corresponding to each customer ID 122, the bill stored in each corresponding record. It has a function of extracting the amount 134. When a plurality of customer IDs 122 are extracted from the customer data table 12 or when a plurality of invoices are sent to the same customer, a billing amount 134 is extracted from a plurality of records of the billing data table 13. .
It should be noted that in the billing amount extraction, the billing amount of the record for which the entire amount has been applied in the billing data table 13 is not extracted. For the record in which the partial deposit amount 137 is stored, the difference between the billed amount 134 and the partial deposit amount 137 is extracted as the billed amount. For example, from the fourth record of the billing data table 13, ¥ 30,000 obtained by subtracting the partial deposit amount ¥ 20,000 is extracted as the billing amount.

<1-7. Total value calculation unit 24>
The total value calculation unit 24 has a function of calculating the total value of the charge amount 134 for each customer ID 133 using the charge amount 134 extracted from the charge data table 13.

<1-8. Minimum value selection unit 25>
The minimum value selection unit 25 has a function of selecting the minimum value of the charge amount 134 for each customer ID 133 using the charge amount 134 extracted from the charge data table 13. The selection of the minimum value is performed by, for example, comparing the billing amount 134 related to two records among a plurality of records storing data of a certain customer ID 133, and comparing the lower billing amount 134 with the uncompared record of the customer ID 133. It is possible to use a known method, for example, repeating the comparison with the billing amount 134 related to No. 1 until there are no more uncompared records.

<1-9. Comparison unit 26>
The comparison unit 26 compares the transfer amount 114 extracted from the payment data table 11 with the charge amount 134 extracted from the charge data table 13 for each customer ID 133. 11 and the billing data table 13 have a function of performing a clearing process on the corresponding records. As a result of the comparison, when the transfer amount 114 and the charge amount 134 do not satisfy the predetermined matching condition, the transfer amount 114 and the charge amount 134 extracted from the charge data table 13 are compared.

  Here, the predetermined matching condition to be satisfied when the transfer amount 114 and the charged amount 134 are compared is, for example, a condition that the difference between them is ¥ 0 or an amount equivalent to the transfer fee. For example, when seven types of transfer fees, ¥ 210, ¥ 315, ¥ 420, ¥ 525, ¥ 630, ¥ 735, and ¥ 840, are assumed, one of these transfer fees is subtracted from the charged amount 134. When the value is equal to the transfer amount 114, a predetermined matching condition can be satisfied.

  When the total value calculation unit 24 calculates the total value of the charged amount 134 for each customer ID 133, the comparing unit 26 compares the total value with the transfer amount 114. When the total value is smaller than the transfer amount 114, the charge amount 134 for the customer ID and the transfer amount 114 are not compared any more, and the charge amount 134 and the transfer amount 114 for other customer IDs are compared. .

  When the minimum value selection unit 25 selects the minimum value of the charge amount 134 for each customer ID 133, the comparison unit 26 compares the minimum value with the transfer amount 114. If the minimum value is larger than the transfer amount 114, the charge amount 134 for the customer ID is not compared with the transfer amount 114, and the charge amount 134 for the other customer ID is compared with the transfer amount 114. .

  The comparison unit 26 stores the transfer source account number 115, the transfer source financial institution code 116 or the transfer source branch code 117 of the deposit data table 11 in the customer data table 12.

<1-10. Output unit 27>
The output unit 27 outputs a result or outputs a customer list when no corresponding record exists in the customer data extraction unit 22.
In addition, the output unit 27 outputs a result when there are a plurality of records in which the charge amount 134 satisfying a predetermined matching condition with respect to the transfer amount 114 exists in the comparison unit 26 or when there is no record at all. Or, output the request data consumption candidate list.

<1-11. Input unit 28>
The input unit 28 accepts designation of a customer and billing data by an operator's operation from the customer list and application candidate list output by the output unit 27.

<2. Operation of data verification device>
FIG. 4 is a flowchart showing an operation example of the data collating apparatus according to the embodiment. The data collating apparatus 1 is a program that realizes the functions of the deposit data extraction unit 21, the customer data extraction unit 22, the billing data extraction unit 23, the total value calculation unit 24, the minimum value selection unit 25, and the comparison unit 26 described above. By reading the module from the computer-readable storage medium and executing it, the following steps are performed.

<2-1. S1>
First, the deposit data extraction unit 21 extracts a transfer person name (kana) 113 and a transfer amount 114 from one record included in the deposit data table 11 (S1).
For example, in FIG. 2, when deposit data is extracted from the first record of the deposit data table 11, “A0” is extracted as the transfer person name (Kana) 113 and “¥ 90,000” is extracted as the transfer amount 114.
In addition, when extracting the deposit data from the second record of the deposit data table 11, “B” is extracted as the transfer person name (kana) 113 and “¥ 39,580” is extracted as the transfer amount 114.

<2-2. S2>
Next, the customer data extraction part 22 searches the customer data table 12 using the transfer person name (kana) 113 extracted from the payment data table 11 (S2).

<2-3. S3>
In S <b> 2, when the customer data table 12 is searched using the transfer person name (kana) 113, if there is one corresponding record, one customer is specified. Therefore, the customer data extraction unit 22 extracts the customer ID 122 stored in the record (S3).
For example, when “A0” is extracted as the transfer person name (kana) 113 from the deposit data table 11, “A001” is extracted as the customer ID 122 from the first record of the customer data table 12.

<2-4. S4>
In S <b> 2, when the customer data table 12 is searched using the transfer person name (kana) 113 and there are a plurality of corresponding records, the deposit data extraction unit 21 transfers the record to the record in the deposit data table 11. It is determined whether or not arbitrary information such as a source account number 115, a transfer source financial institution code 116, and a transfer source branch code 117 is stored (S4).

<2-5. S5>
In S4, when arbitrary information is not memorize | stored in the payment data table 11, the customer data extraction part 22 extracts customer ID122 memorize | stored in the relevant record of the customer data table 12 (S5).
For example, when “B” is extracted as the transfer person name (kana) 113 from the deposit data table 11, “B001”, “B002”, “B003” as the customer ID 122 from the third to fifth records of the customer data table 12. Are extracted.
Note that the number of customer IDs 122 extracted in S5 is I, and in the following description, each customer ID is identified by a natural number i (where the maximum value of i is an integer I of 2 or more).

<2-6. S6>
In S <b> 4, when arbitrary information is stored in the deposit data table 11, the deposit data extraction unit 21 extracts the arbitrary information, and using the arbitrary information, the customer data extraction unit 22 stores the arbitrary information in the customer data table 12. The corresponding records are narrowed down (S6).

  In S6, when narrowing down to one record as a result of narrowing down using arbitrary information, the customer data extracting unit 22 extracts the customer ID 122 stored in the record (S3). Here, as an example of narrowing down to one record, a case where the same transfer source account number 125 as the transfer source account number 115 stored in the deposit data table 11 is stored in the customer data table 12 is considered. .

  In S6, as a result of narrowing down using arbitrary information, if narrowed down to a plurality of records, or if narrowing down is not possible, the customer data extraction unit 22 selects a plurality of corresponding data in the customer data table 12. The customer ID 122 stored in the record is extracted (S5). As an example of narrowing down to a plurality of records, the same data as the transfer source financial institution code 116 or the transfer source branch code 117 stored in the deposit data table 11 is stored in the plurality of records in the customer data table 12. Is stored in the memory. As an example of the case where narrowing down is not possible, a case where arbitrary information such as the transfer source account number 125, the transfer source financial institution code 126, and the transfer source branch code 127 is not stored in the customer data table 12 is considered.

<2-7. S7>
In S6, when there is no corresponding record as a result of narrowing down using arbitrary information, the customer data extraction unit 22 controls the output unit 27 to output the result and the customer list (S7). ). As an example of the case where the corresponding record disappears, it is conceivable that the data of the arbitrary information stored in the customer data table 12 is old and does not accurately reflect the customer's bank information.

  As the customer list output by the output unit 27, for example, the search result of the customer data table 12 using the transfer person name (Kana) 113 in S2 may be output, or the entire customer list may be output. When the operator designates one customer in the customer list by operating the input unit 28, the customer data extraction unit 22 extracts the customer ID 122 of the customer (S3). Further, the operator may specify a plurality of customers in the customer list by operating the input unit 28, and the customer data extraction unit 22 may extract the customer IDs 122 of the plurality of customers (S5). ).

<2-8. S8>
In S2, when the customer data table 12 is searched using the transfer person name (kana) 113 and the corresponding record does not exist, the customer data extraction unit 22 outputs the result and the customer list. The output unit 27 is controlled (S8). As the customer list, for example, an all customer list is output. When the operator designates one customer in the customer list by operating the input unit 28, the customer data extraction unit 22 extracts the customer ID 122 of the customer (S3). Further, the operator may specify a plurality of customers in the customer list by operating the input unit 28, and the customer data extraction unit 22 may extract the customer IDs 122 of the plurality of customers (S5). ).

<2-9. S100>
When one customer ID 122 is extracted by the customer data extracting unit 22 in S3, the billing data extracting unit 23 extracts the billing amount 134 for the customer ID 133 corresponding to the customer ID 122, and the total value calculating unit 24 However, for the customer ID 133, the total value of the billing amount 134 is calculated, and the comparison unit 26 compares the billing amount 134 with the transfer amount 114 (S100). Details of this processing will be described later.

<2-10. S200>
When a plurality of customer IDs 122 are extracted by the customer data extracting unit 22 in S5, the billing data extracting unit 23 extracts the billing amount 134 for each customer ID 133 corresponding to each customer ID 122, and the total value calculating unit 24 However, for each customer ID 133, the total value of the billing amount 134 is calculated, the minimum value selection unit 25 selects the minimum value of the billing amount 134 for each customer ID 133, and the comparison unit 26 selects these billing amounts 134 and The transfer amount 114 is compared (S200). Details of this processing will be described later.

<2-11. S9>
When the transfer amount 114 is compared with the invoice amount 134 by S100 or S200, and one record (in one set) in the invoice data table 13 that satisfies a predetermined matching condition with respect to the above record in the deposit data table 11 is specified In step S9, the comparison unit 26 performs an application process on the corresponding records in the deposit data table 11 and the billing data table 13.
The application process is performed, for example, by storing application information 118 in the deposit data table 11 and storing application information 136 in the billing data table 13.

  For example, in S100, when it is confirmed that the deposit data related to the first record in the deposit data table 11 corresponds to the bill data related to the first and second records in the bill data table 13, as shown in FIG. As described above, the sequential number “1, 2” of the corresponding billing data table 13 is stored as the application information 118 related to the first record of the deposit data table 11. Further, the sequential number “1” of the deposit data table 11 is stored as the application information 136 relating to the first and second records of the billing data table 13.

  In S200, when it is confirmed that the deposit data related to the second record of the deposit data table 11 corresponds to the bill data related to the seventh and eighth records of the bill data table 13, as shown in FIG. As described above, the sequential number “7, 8” of the corresponding billing data table 13 is stored as the application information 118 related to the second record of the deposit data table 11. Further, the sequential number “2” of the deposit data table 11 is stored as the application information 136 relating to the seventh and eighth records of the billing data table 13.

<2-12. S10>
The comparison unit 26 (a) is a case where the transfer source account number 115, the transfer source financial institution code 116, or the transfer source branch code 117 is stored in the record for performing the transfer process of the deposit data table 11, and (B1) The transfer source account number 125, the transfer source financial institution code 126 or the transfer source branch code 127 is not stored in the corresponding record of the customer data table 12, or (b2) different from the data of the deposit data table 11 If there is, the transfer source account number 115, transfer source financial institution code 116 or transfer source branch code 117 of the deposit data table 11 is stored in the corresponding record of the customer data table 12 (S10).
Here, the corresponding record in the customer data table 12 means a record in the customer data table 12 in which the data of the customer ID 122 corresponding to the customer ID 133 stored in the record that performs the consumption process of the billing data table 13 is stored. When there are a plurality of such records, the data of the transfer person name (Kana) 123 corresponding to the transfer person name (Kana) 113 stored in the record for which the deposit process of the deposit data table 11 is performed is further stored. It may be limited to records in the customer data table 12.

  For example, “A001” is stored as the customer ID 133 in the first and second records for performing the clearing process of the billing data table 13, and the corresponding customer ID 122 is stored in the first and second records of the customer data table 12. It is remembered. Further, “A0” is stored as the transfer person name (kana) 113 in the first record for performing the application data saving process, and the corresponding transfer person name (kana) 123 is stored in the first record of the customer data table 12. Stored in the record. Therefore, as shown in FIG. 3, in the first record of the customer data table 12, the transfer source account number “1234567” and the transfer source financial institution code “ "0003" and the transfer source branch code "246" are stored.

If a plurality of records in the customer data table 12 correspond to a subsequent search using the transfer person name (kana) 113 by the customer data extraction unit 22 by the processing of S10, the transfer source account number 115, the transfer source financial institution code It is possible to narrow down by 116 or the transfer source branch code 117.
It should be noted that the processing of S10 is not possible when narrowing down to one record as a result of narrowing down using arbitrary information such as the transfer source account number 115, the transfer source financial institution code 116, and the transfer source branch code 117 (S6 to S5 or It may be performed at the time of transition to S7.

<3. Details of S100>
FIG. 5 is a flowchart showing details of the matching process when one customer ID is extracted in S3 of FIG.

<3-1. S102>
When one customer ID 122 is extracted by the customer data extraction unit 22 in S3 of FIG. 4, the billing data extraction unit 23 searches the billing data table 13 using the customer ID 133 corresponding to the customer ID 122, For the customer ID 133, the billing amount 134 stored in each corresponding record is extracted (S102). When a plurality of invoices have been sent to the same customer, a billing amount 134 is extracted from a plurality of records in the billing data table 13.

<3-2. S103>
Next, the total value calculation unit 24 calculates the total value of the charge amount 134 for the customer ID 133 using the charge amount 134 extracted from the charge data table 13 (S103).

<3-3. S104, S105>
Next, the comparison unit 26 compares the total amount of the billing amount 134 calculated by the total value calculation unit 24 with the transfer amount 114 (S104).

  When the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, there is one record in the billing data table 13 that satisfies the predetermined matching condition with respect to the record in the deposit data table 11 (1 Therefore, the process of S100 is terminated.

  If the total amount of the billing amount 134 is smaller than the transfer amount 114, the record in the deposit data table 11 is considered not to be deposit data related to the billing data for the customer ID 133, so error information is output (S105). , S100 ends. Alternatively, the process returns to S8 in FIG. 4 to select the customer again.

  If the total value of the billing amount 134 is larger than the transfer amount 114, the record in the deposit data table 11 is considered to be deposit data related to a part of the billing data for the customer ID 133, and the process proceeds to the next S109. The comparison with the billing amount 134 for the customer ID 133 is continued.

<3-4. S109>
If the total value of the billing amount 134 is larger than the transfer amount 114, the total value calculation unit 24 calculates the total value of the billing amount 134 for the customer ID 133 only for billing data that has not yet been partially deposited. (S109). For example, billing data that has been partially deposited as in the fourth record of the billing data table 13 is excluded here, and the total value is calculated. This is because matching with billing data that has been partially deposited may not be suitable for automatic processing.

<3-5. S110, S111>
Next, the comparison unit 26 compares the total amount of the charge amount 134 (of the charge data that has not been partially deposited) calculated by the total value calculation unit 24 with the transfer amount 114 (S110).

  When the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, there is one record in the billing data table 13 that satisfies the predetermined matching condition with respect to the record in the deposit data table 11 (1 Therefore, the process of S100 is terminated.

  If the total value of the billing amount 134 is smaller than the transfer amount 114, the record in the deposit data table 11 is not considered to be deposit data related to the billing data for the customer ID 133, so error information is output (S111). , S100 ends. Alternatively, the process returns to S8 in FIG. 4 to select the customer again.

  If the total value of the billing amount 134 is larger than the transfer amount 114, the record in the deposit data table 11 is considered to be deposit data related to a part of the billing data for the customer ID 133, and the process proceeds to the next S112. The comparison with the billing amount 134 for the customer ID 133 is continued.

<3-6. S112, S113>
When the total value of the charge amount 134 is larger than the transfer amount 114, the comparison unit 26 determines the charge amount 134 and the transfer amount 114 (of the charge data that has not been partially deposited) for the customer ID 133 as the charge data. A comparison is made for each record in the table 13 (invoice units) (S112).
When there is a record in which the charged amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, the comparison unit 26 stores the sequential number 131 related to the record as matching data in a predetermined storage device ( S113).

<3-7. S114, S115>
Next, the total value calculation unit 24 calculates the total value of the billing amount 134 (of the billing data that has not been partially deposited) for each item information 135 for the customer ID 133, and the comparison unit 26 calculates the calculated item. The total value of the charged amount 134 for each information 135 is compared with the transfer amount 114 (S114).
When there is case information 135 in which the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, the comparison unit 26 sets the sequential number 131 related to the record storing the case information 135. Is stored as matching data in a predetermined storage device (S115).

  For example, as shown in the first to third records of the billing data table 13, the total billing amount for the customer ID “A001” is ¥ 130,000, the minimum value is ¥ 30,000, the billing amount for each record is ¥ 60,000, ¥ 30,000 and ¥ 40,000, both of which do not match the transfer amount “¥ 90,000” associated with the first record of the deposit data table 11, but are associated with the first and second records storing “U” as the case information 135 The total amount charged is ¥ 90,000, which matches the transfer amount. Therefore, a set of sequential numbers “1, 2” related to the record storing “U” as the case information 135 is stored as matching data as satisfying a predetermined matching condition.

<3-8. S118>
Next, the comparison unit 26 refers to the coincidence data stored in the processes of S113 and S115 described above, and determines the number of coincidence data (S118).
If there is one matching data, one record (one set) of the billing data table 13 satisfying a predetermined matching condition for the above record in the deposit data table 11 is specified, so the processing of S100 Exit.

<3-9. S119>
If there is a plurality of matching data, or if there is no matching data, the comparison unit 26 controls the output unit 27 to output the result and the request data consumption candidate list (S119). As the application candidate list, for example, when there are a plurality of matching data, a set of a plurality of records corresponding to the matching data in the billing data table 13 is output. Alternatively, when there is no matching data, all records for the customer ID 133 in the billing data table 13 are output.

  Further, when the data for the partial deposit amount 137 is stored in the record for the customer ID 133 in the billing data table 13, the comparison unit 26 sets the data for the partial deposit amount 137 among the records for the customer ID 133. The output unit 27 may be controlled so as to output all records stored as “consumption candidates list”. This is because the billing data that has been partially deposited is excluded in the processing of S109 to S114.

  When the operator designates one (one set) in the application candidate list by operating the input unit 28, the record of the billing data table 13 is specified as one (one set). The process of S100 is terminated. Further, the operator may return to S8 in FIG. 4 and perform the customer selection again without specifying from the application candidate list.

  In the comparison process described above, the comparison process may be omitted if the same billing amount as that of the already completed comparison process is used as a comparison target. For example, if there is no record having the data of the partial deposit amount 137 for the customer, the comparison process in S109 and 110 is omitted because the same billing amount as the comparison process in S103 and S104 that has already been completed is used as a comparison target. You may do it.

<4. Details of S200>
FIG. 6 is a flowchart showing details of the matching process when a plurality (I) of customer IDs are extracted in S5 of FIG.

<4-1. S201>
When a plurality of customer IDs 122 are extracted by the customer data extraction unit 22 in S5 of FIG. 4, in order to compare the charged amount 134 and the transferred amount 114 for each of the I customer IDs, A natural number i for identifying each corresponding customer ID 133 is set to 1 (S201).
The following processes in S202 to S216 are performed for one customer ID specified by the natural number i, and the same process is repeated for the next customer ID every time 1 is added to the natural number i in S217. For example, the processing of S202 to S216 is performed for the customer ID “B001” when i = 1, the customer ID “B002” when i = 2, and the customer ID “B003” when i = 3.

<4-2. S202>
In S202, the billing data extraction unit 23 searches the billing data table 13 using the customer ID 133 identified by the natural number i, and extracts the billing amount 134 stored in each corresponding record for the customer ID 133. . When a plurality of invoices have been sent to the same customer, a billing amount 134 is extracted from a plurality of records in the billing data table 13.

<4-3. S203>
Next, the total value calculation unit 24 calculates the total value of the charge amount 134 for the customer ID 133 using the charge amount 134 extracted from the charge data table 13 (S203).

<4-4. S204, S205>
Next, the comparison unit 26 compares the total amount of the charged amount 134 calculated by the total value calculating unit 24 with the transfer amount 114 (S204).

  When the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, there is one record in the billing data table 13 that satisfies the predetermined matching condition with respect to the record in the deposit data table 11 (1 In the billing data table 13, the set of sequential numbers 131 related to the record in which the customer ID 133 is stored is stored as matching data in a predetermined storage device (S205). The comparison for ID 133 is terminated, and the process proceeds to S216 described later.

If the total amount of the billing amount 134 is smaller than the transfer amount 114, the record of the deposit data table 11 is not considered to be deposit data related to the billing data for the customer ID 133, so the comparison for the customer ID 133 is terminated. Then, the process proceeds to S216 described later.
For example, as shown in the fourth record of the billing data table 13, when the total value of the billing amount (difference from the partial deposit amount) for the customer ID “B001” is ¥ 30,000, the second record of the deposit data table 11 Since the transfer amount “¥ 39,580” related to is not normally considered, the comparison for the customer ID 133 is terminated.

  If the total value of the billing amount 134 is larger than the transfer amount 114, the record in the depositing data table 11 may be depositing data related to a part of the billing data for the customer ID 133, and the process proceeds to the next S206. The comparison with the billing amount 134 for the customer ID 133 is continued.

<4-5. S206>
Next, the minimum value selection unit 25 selects the minimum value of the charge amount 134 for the customer ID 133 using the charge amount 134 extracted from the charge data table 13 (S206).

<4-6. S207, S208>
Next, the comparison unit 26 compares the minimum value of the charged amount 134 selected by the minimum value selecting unit 25 with the transfer amount 114 (S207).

  When the minimum value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, the record of the billing data table that satisfies the predetermined matching condition with respect to the record of the deposit data table 11 sets the minimum value. Since it is specified as the stored record, the sequential number 131 related to the record storing the minimum value is stored as matching data in a predetermined storage device (S208), and the comparison for the customer ID 133 is finished. The process proceeds to S216 described later.

When the minimum value of the charge amount 134 is larger than the transfer amount 114, the record of the receipt data table 11 is not considered to be receipt data related to the claim data for the customer ID 133, so the comparison for the customer ID 133 is finished. Then, the process proceeds to S216 described later.
For example, as shown in the fifth record of the billing data table 13, when the minimum value of the billing amount for the customer ID “B002” is “¥ 90,000”, the transfer amount “¥” related to the second record of the deposit data table 11 Since it is unlikely that “39,580” will be deposited (unless it is a partial deposit), the comparison for the customer ID 133 is terminated.

  When the minimum value of the billing amount 134 is smaller than the transfer amount 114, the record in the deposit data table 11 may be deposit data related to other billing data for the customer ID 133, and the process proceeds to the next S209. The comparison with the billing amount 134 for the customer ID 133 is continued.

<4-7. S209>
When the minimum value of the billing amount 134 is smaller than the transfer amount 114, the total value calculation unit 24 calculates the total value of the billing amount 134 for the customer ID 133 only for billing data that has not been partially deposited yet. (S209).

<4-8. S210, S211>
Next, the comparison unit 26 compares the total amount of the billing amount 134 calculated by the total value calculation unit 24 (for billing data that has not been partially deposited) with the transfer amount 114 (S210).

  When the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, there is one record in the billing data table 13 that satisfies the predetermined matching condition with respect to the record in the deposit data table 11 (1 In the billing data table 13, the sequential number 131 related to the record in which the customer ID 133 is stored is stored as matching data in a predetermined storage device (S211), and the customer The comparison for ID 133 is terminated, and the process proceeds to S216 described later.

  If the total amount of the billing amount 134 is smaller than the transfer amount 114, the record of the deposit data table 11 is not considered to be deposit data related to the billing data for the customer ID 133, so the comparison for the customer ID 133 is terminated. Then, the process proceeds to S216 described later.

  If the total value of the billing amount 134 is larger than the transfer amount 114, the record in the deposit data table 11 may be deposit data related to a part of the billing data for the customer ID 133. Going forward, the comparison with the billing amount 134 for the customer ID 133 is continued.

<4-9. S212, S213>
Next, the comparison unit 26 compares the billing amount 134 (of billing data that has not yet been partially deposited) and the transfer amount 114 for the customer ID 133 for each record of the billing data table 13 (invoice units). (S212).
When there is a record in which the charged amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, the comparison unit 26 stores the sequential number 131 related to the record as matching data in a predetermined storage device ( S213).

<4-10. S214, S215>
Next, the total value calculation unit 24 calculates the total value of the billing amount 134 (of the billing data that has not been partially deposited) for each item information 135 for the customer ID 133, and the comparison unit 26 calculates the calculated item. The total value of the charged amount 134 for each information 135 is compared with the transfer amount 114 (S214).
When there is case information 135 in which the total value of the billing amount 134 satisfies a predetermined matching condition with respect to the transfer amount 114, the comparison unit 26 sets the sequential number 131 related to the record storing the case information 135. Are stored as matching data in a predetermined storage device (S215).

For example, as shown in the sixth to eighth records of the billing data table 13, the sum of the billing amount for the customer ID “B003” is ¥ 60,000, the minimum value is ¥ 20,000, and the billing amount for each record is ¥ 20,000. Yes, both are not the same as the transfer amount “¥ 39,580” related to the second record of the deposit data table 11, but the total value of the charged amounts related to the seventh and eighth records storing “Z” as the case information 135 Is ¥ 40,000, and the value obtained by subtracting the transfer fee ¥ 420 from this ¥ 40,000 matches the transfer amount “¥ 39,580”. Therefore, a set of sequential numbers “7, 8” related to the record in which “Z” is stored as the case information 135 is stored as matching data, assuming that a predetermined matching condition is satisfied.
This completes the comparison for the customer ID 133 and proceeds to S216.

<4-11. S216, S217>
In S216, it is determined whether or not the natural number i for identifying each customer ID has reached the maximum value I.
When the natural number i has reached the maximum value I, the comparison between the charge amount 134 and the transfer amount 114 is completed for the customer IDs 133 corresponding to all the customer IDs 122 extracted by the customer data extraction unit 22. The process proceeds to S218.
When the natural number i has not reached the maximum value I, the billing amount 134 and the transfer amount 114 are compared with the next customer ID 133, and 1 is added to the natural number i (S217), and the above-described processing of S202 to S216 is performed. repeat.

<4-12. S218>
In S218, the comparison unit 26 refers to the matching data stored in the above-described processing of S205, S208, S211, S213, and S215, and determines the number of matching data.
If there is only one matching data, one record (one set) of the billing data table 13 satisfying a predetermined matching condition with respect to the above record in the deposit data table 11 is specified. Exit.

<4-13. S219>
If there is a plurality of matching data, or if there is no matching data, the comparison unit 26 controls the output unit 27 to output the result and the request data consumption candidate list (S219). As the application candidate list, for example, when there are a plurality of matching data, a set of a plurality of records corresponding to the matching data in the billing data table 13 is output.

  When the operator designates one (one set) in the application candidate list by operating the input unit 28, the record of the billing data table 13 is specified as one (one set). The process of S200 is terminated.

  In the comparison process described above, the comparison process may be omitted if the same billing amount as that of the already completed comparison process is used as a comparison target. For example, when there is no record having the data of the partial deposit amount 137 for the customer, the comparison processing in S209 and S210 is performed because the same billing amount as the comparison processing in S203 and S204 that has already been completed is compared. You may do it.

<5. Effect of the above embodiment>
According to the above embodiment, even when there are a plurality of customers corresponding to the transfer person name of the deposit data (S5), the transfer amount 114 data extracted from the deposit data table 11 and the billing data table 13 for each customer ID. The data of the billing amount 134 extracted is compared (S202 to S216), and when there is no data of the billing amount 134 that satisfies the predetermined matching condition with the data of the transfer amount 114, it is extracted for another customer ID. By comparing with the data of the billing amount 134 (S217), the customer can be specified, so that the payment data and the billing data can be efficiently verified.

  In addition, according to the above embodiment, the total value calculated by the total value calculation unit 24 is compared with the transfer amount 114 (S204, S210). Since the comparison with respect to the customer ID is terminated without making a comparison with, the comparison process can be simplified.

  Further, according to the above embodiment, the minimum value selected by the minimum value selection unit 25 is compared with the transfer amount 114 (S207), and when the minimum value is greater than the transfer amount 114, Since the comparison for the customer ID is completed without making a comparison, the comparison process can be simplified.

  Moreover, according to the said embodiment, even when a some customer corresponds by the search based on a transfer person name, customer ID can be narrowed down based on the financial institution code, branch code, or account number of the transfer origin ( S6).

  Further, according to the above embodiment, since the transfer source financial institution code, branch code or account number is stored in the customer data table 12 (S10), subsequent narrowing down can be facilitated.

DESCRIPTION OF SYMBOLS 1 ... Data collation apparatus, 11 ... Deposit data table, 12 ... Customer data table, 13 ... Billing data table, 21 ... Deposit data extraction part, 22 ... Customer data extraction part, 23 ... Billing data extraction part, 24 ... Total value calculation , 25 ... Minimum value selection part, 26 ... Comparison part, 27 ... Output part, 28 ... Input part, 111 ... Sequential number, 112 ... Payment date, 113 ... Transfer person name (Kana), 114 ... Transfer amount, 115 ... Transfer Original account number, 116 ... Transfer source financial institution code, 117 ... Transfer source branch code, 118 ... Transfer information, 121 ... Sequential number, 122 ... Customer ID, 123 ... Transfer name (Kana), 125 ... Transfer source account number, 126: Transfer source financial institution code, 127: Transfer source branch code, 131 ... Sequential number, 132 ... Billing date, 133 ... Customer ID, 134 ... Billing , 135 ... case information, 136 ... clearing information, 137 ... part payment amount

Claims (5)

A deposit data table including a plurality of records, a field for storing the transfer person name data, and a field for storing the transfer amount data for each record;
A customer data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing transfer name data;
A billing data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing billing amount data;
, A device for verifying the deposit data and the billing data,
Payment data extraction means for extracting the transfer person name data and the transfer amount data for one record included in the payment data table;
A customer data extracting means for searching the customer data table using the transfer person name data extracted from the deposit data table, and extracting the data of the customer ID stored in the corresponding record;
A billing data extracting means for searching the billing data table using customer ID data extracted from the customer data table, and extracting billing amount data stored in a corresponding record for the customer ID;
Minimum value selecting means for selecting the minimum value of the billing amount for the customer ID using the billing amount data extracted from the billing data table;
When the data of the customer ID is extracted from the customer data table, the transfer amount data extracted from the deposit data table is compared with the minimum value of the billing amount selected for the customer ID,
When the minimum value of the charge amount is smaller than the transfer amount, the charge amount data extracted from the charge data table is used to calculate the total value of the charge amount for the customer ID ,
A means for comparing the transfer amount extracted from the deposit data table with the total amount of the billing amount calculated for the customer ID, and performing a corresponding record application process if they match,
A data collating apparatus comprising: In claim 1,
In the means for performing the application process, when the total value of the charged amount is larger than the transfer amount, the total value calculating unit calculates the total value of the charged amount for each item information for the customer ID, When the total value of the calculated billing amount for each item information is compared with the transfer amount, and there is item information such that the total value of the charged amount for each item information matches the transfer amount, A data verification device that performs the process of clearing records of matching item information. A deposit data table including a plurality of records, a field for storing the transfer person name data, and a field for storing the transfer amount data for each record;
A customer data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing transfer name data;
A billing data table having a plurality of records, each field including a field for storing customer ID data, and a field for storing billing amount data;
, A device for verifying the deposit data and the billing data,
Payment data extraction means for extracting the transfer person name data and the transfer amount data for one record included in the payment data table;
A customer data extracting means for searching the customer data table using the transfer person name data extracted from the deposit data table, and extracting the data of the customer ID stored in the corresponding record;
A billing data extracting means for searching the billing data table using customer ID data extracted from the customer data table, and extracting billing amount data stored in a corresponding record for the customer ID;
Minimum value selecting means for selecting the minimum value of the billing amount for the customer ID using the billing amount data extracted from the billing data table;
When the data of the customer ID is extracted from the customer data table, the transfer amount data extracted from the deposit data table is compared with the minimum value of the billing amount selected for the customer ID,
When the minimum value of the charge amount is smaller than the transfer amount, the charge amount data extracted from the charge data table is used to calculate the total value of the charge amount for each item information for the customer ID ,
Means for comparing the transfer amount extracted from the deposit data table and the total amount of the charge amount for each item information calculated for the customer ID, and performing a process of clearing the record of the corresponding item information if they match When,
A data collating apparatus comprising: In any one of Claims 1 thru | or 3,
In the billing data extraction means, with respect to the corresponding record for the customer ID, for the record in which the partial deposit amount is stored, the difference between the billing amount and the partial deposit amount is extracted as billing amount data. apparatus. In any one of Claims 1 thru | or 4,
The data collating apparatus, including a case where a value obtained by subtracting a transfer fee from the billing amount matches the transfer amount when the means for performing the application process matches.

Images