JP2007265332A - Method, system and program for negation - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method, a system and a program for negation for efficiently negating a charge and payment while using limited resources. <P>SOLUTION: A control part 21 of a negation system 20 performs pattern development by using records recorded in a payment data storage part 34 and a charge data storage part 33. Then, the control part 21 checks whether or not the generated pattern exceeds capacity of a pattern memory when the generated pattern is stored in the pattern memory 23. Pattern development processing is terminated when the generated pattern exceeds memory capacity and a combination pattern stored in the pattern memory is sorted by using amounts. The control part 21 perform matching by comparing amounts of each combination pattern recorded in the pattern memory 23 with an amount of a record of a negation partner. Then, a negation flag including a negation code is recorded when negation is successfully performed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to collection of accounts receivable, and relates to an application processing method, an application processing system, and an application processing program for verifying billing and depositing and applying them.

  As one of the tasks related to the collection of accounts receivable, the billing data in which the billing contents are written and the payment data in which the payment contents are written are collated, and the billing data is deleted in sequence. This is a common practice. Recently, this work may be performed using a computer. For example, a technique of performing an application using EDI (Electronic Data Interchange) is also disclosed (see, for example, Patent Document 1). In the technique described in this document, the consumption process is automated by carrying the consumption key information around.

  However, EDI may not be used in business relationships. In this case, matching is performed using the date, billing destination information, and payment source information. Then, the consumption process is performed using the billing amount and the deposit amount. However, such billing and depositing are not necessarily made one by one.

Therefore, for the billing details data where the billing destination and the depositing source match, and the billing amount and the deposit amount included in the deposit details data, the amount is summed according to some predetermined patterns and the application process is performed. An apparatus for performing the same has also been studied (see, for example, Patent Document 2). In the technique described in this document, the total amount of payment details data to be applied is matched with the total amount of billing details data for a billing date in a specific period prior to the latest payment date of the payment details data. Then, if the total amount is the same or the difference between the amounts is within a preset error range, the application process is performed.
JP 2001-92913 A (first page) Japanese Patent Laying-Open No. 2004-185588 (first page)

  However, when there are many billing records and deposit records, various patterns can be considered to add them together. In this case, there are a pattern for summing up billing records and a pattern for summing up receipt records. For this reason, if each summation pattern is generated and the collation process between the deposit record and the billing record is performed each time, the calculation load increases. Therefore, it is also possible to generate summation patterns in advance and collate them together. In this case, it is possible to speed up the erase operation. However, when there are a large number of billing records and deposit records, the number of patterns for combining them becomes enormous, and the capacity load of the memory for storing these patterns increases.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide an application processing method and an application process for efficiently matching bills and deposits while using limited resources. It is to provide a write processing system and a consumption processing program.

In order to solve the above-mentioned problem, the invention described in claim 1 includes a billing data storage unit that records a billing record that includes a billing amount, a deposit data storage unit that records a deposit record that includes a deposit amount, and an application A pattern memory control means for recording a pattern used for the verification, and a billing record and a deposit record are collated and erased, wherein the control means is set based on the memory capacity of the pattern memory Generating a summation pattern by combining either the billing record or the deposit record until reaching the specified reference number, and performing a pattern development process recorded in the pattern memory, and the amount of the summation pattern recorded in the pattern memory Is calculated, sorted in descending order of the amount, and collated with records that have not been subjected to pattern expansion processing When matching is performed sequentially, a step of performing a collation process for recording an erase flag in the element record constituting the sum pattern is performed, and all sum patterns recorded in the pattern memory are collated. However, when the record which cannot be erase | eliminated remains, it makes it a summary to repeat the said pattern expansion | deployment process and collation process using the remaining record.

  The invention according to claim 2 is the application processing method according to claim 1, wherein the billing record and the deposit record each include data on the billing date and the deposit date, and the billing record or the same deposit date on the same billing date. Each deposit group is used to form a group, and the pattern development process and the collation process are executed for each group.

  According to a third aspect of the present invention, in the application processing method according to the first or second aspect, the pattern development processing compares the number of billing records with the number of deposit records, and records either bill records or deposit records. The gist is to generate a summation pattern using the larger number of records and record the summation pattern in the pattern memory until the reference number is reached.

  The invention described in claim 4 includes a billing data storage unit that records a billing record that includes a billing amount, a depositing data storage unit that records a depositing record that includes a depositing amount, and a pattern memory that records a pattern used for application. The control unit is used to check the billing record against the deposit record and perform the cancellation, and the control unit bills until reaching the reference number set based on the memory capacity of the pattern memory. A combination pattern is generated by combining either the record or the deposit record, and a pattern development process recorded in the pattern memory is calculated, and the sum of the sum pattern recorded in the pattern memory is calculated. Sorting in order, matching is performed sequentially with records that have not been subjected to pattern expansion processing, and matching is performed. In this case, there is provided a means for performing a collation process for recording an extinguishing flag in an element record constituting the summation pattern, and even if all summation patterns recorded in the pattern memory are collated, the summation pattern is erased. When there is no record left, the gist is to repeat the pattern development process and the matching process using the remaining record.

  According to a fifth aspect of the present invention, there is provided a billing data storage unit for recording a billing record including a billing amount, a depositing data storage unit for recording a depositing record including a deposit amount, and a pattern memory for recording a pattern used for application. The control means uses the control means to check the billing record and the deposit record, and cancels the control means until the control means reaches the reference number set based on the memory capacity of the pattern memory. A combination pattern is generated by combining either the record or the deposit record, and a pattern development process recorded in the pattern memory is calculated, and the sum of the sum pattern recorded in the pattern memory is calculated. Sorting in order, matching is performed sequentially with records that have not been subjected to pattern expansion processing, and matching is performed. In this case, even if all the sum patterns recorded in the pattern memory are collated, they are erased even if they are made to function as a means for performing a collation process for recording an extinction flag in the element record constituting the sum pattern. When there is no record left, the gist is to repeat the pattern development process and the matching process using the remaining record.

(Function)
According to the invention described in claim 1, 4, or 5, a summation pattern is generated by combining either the billing record or the deposit record until the reference number set based on the memory capacity of the pattern memory is reached. Perform pattern development processing to be recorded in the memory. Then, the amounts of the summed patterns recorded in the pattern memory are calculated, rearranged in the descending order of the amounts, and collation processing with records that have not been subjected to pattern development processing is sequentially executed. And when it matches, the collation process which records a consumption flag in the element record which comprises this summation pattern is performed. Even if all the combined patterns recorded in the pattern memory are collated, if records that cannot be erased remain, the pattern development process and the collation process are repeated using the remaining records. Thereby, even when various summation patterns are generated, it is possible to perform elimination while considering the capacity of the pattern memory.

  According to the second aspect of the present invention, groups are configured using the same billing record or the same deposit date deposit record, and the pattern development process and the collation process are executed for each group. Usually, there are cases where bills of the same period are collected or paid separately, and by adding them together, the efficiency of application can be improved.

  According to the third aspect of the present invention, a summation pattern is generated using the record with the larger number of records, either the billing record or the deposit record, and the summation pattern is recorded in the pattern memory until the reference number is reached. As a result, the efficiency of erasure can be improved by adding together the records with the larger number of records.

  According to the present invention, it is possible to efficiently match billing and payment while using limited resources.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. The present embodiment will be described as an application processing method, an application processing system, and an application processing program that are used in the case of erasing a bill related to accounts receivable and payment. As shown in FIG. 1, in this embodiment, an application process is performed using a financial institution system 10 and an application processing system 20.

  The consumption processing system 20 is a computer system that executes a consumption process. The consumption processing system 20 includes a control unit 21, a data storage unit, an input unit 25, an output unit 26, a communication unit, and the like configured by a control unit such as a CPU, a RAM, and a ROM. A keyboard or pointing device is used for the input unit 25. A display or a printer is used as the output means. The consumption processing system 20 is connected to the financial institution system 10 via a network and performs communication.

  The control unit 21 of the consumption processing system 20 performs various data management processing for performing the consumption processing. This control unit performs processing described later (pattern development processing, matching processing, pattern development processing, processing for repeating matching processing, and the like). By executing the application processing program for that purpose, the control unit 21 performs a deposit data registration unit 211, a first application processing unit 212, a pattern development unit 213, and a second application processing unit 214 as shown in FIG. Function. The control unit 21 includes a start value memory 22 and a pattern memory 23.

  Here, the deposit data registration means 211 gives a supplier code to the transfer data received by firm banking. The first application processing unit 212 executes the application process by collating the entire billing record and the deposit record. The pattern development unit 213 performs a pattern development process for generating a pattern for performing summation cancellation. The second application processing means 214 performs an application process for partially summing up the billing record and the deposit record and collating them.

  In the start value memory 22, data relating to the start value of the decrement used for subtracting the record from the total pattern when generating the summation pattern is recorded. The initial value of this start value is set to “1”. On the other hand, in the pattern memory 23, data relating to the combined pattern used for collation is recorded.

Further, as shown in FIG. 1, the application processing system 20 includes a master data storage unit 32, a deposit data storage unit 34, and a billing data storage unit 33.
Master data such as company information, supplier information, bank information, and product information is recorded in the master data storage unit 32. When using the consumption processing system 20, the user first performs master maintenance and registers basic information in the master data storage unit 32. In this embodiment, supplier information is used in this. In the master data storage unit 32, as supplier information, for each supplier, the supplier name, supplier name, supplier code, supplier address, destination bank name / code, bank branch name / code, account number Data items such as account names are recorded. This supplier code is a code given to each supplier in order to collate the deposit record with the billing record.

  The billing data storage unit 33 records billing records for accounts receivable from business partners. The billing record includes the business partner name and business partner code with the sales date, billing closing date, billing date, scheduled payment date, slip number and transaction details (product code, product name, quantity received, quantity, unit price, amount, total amount and Data field for recording data items such as total amount). In the present embodiment, the total amount is used as a billing amount and is applied. In addition, each billing record includes a consumption flag field. In the application flag field, an application flag is recorded when the application is completed. This application flag includes a unique application code that can identify the receipt record that has been applied. The billing record registered in the billing data storage unit 33 is sent to the business partner as electronic data or forms.

  In the deposit data storage unit 34, a deposit record related to the transfer from the business partner is recorded for the billing. This deposit record is recorded when transfer data is acquired from the financial institution system 10. This deposit record includes a date, deposit amount, transfer requester name, destination bank information, and the like. Further, each deposit record includes a supplier code field and an application flag field. In this supplier code field, the supplier code assigned when the supplier name in the supplier information matches the transfer requester name in the transfer data is recorded. In the application flag field, an application flag is recorded when the application is completed. This application flag is configured to include a common application code in order to identify the request record that has been applied.

A processing procedure for performing the consumption process using the consumption processing system 20 configured as described above will be described with reference to FIGS.
(Grant customer code)
The requested business partner transfers the money from the destination bank to the destination bank. Then, the control unit 21 of the application processing system 20 acquires transfer data from the financial institution system 10 of the destination bank. In the present embodiment, the deposit data registration unit 211 of the control unit 21 receives the transfer data by firm banking. Then, the deposit data registration means 211 of the control unit 21 records the transfer data in the deposit data storage unit 34. Further, the payment data registration unit 211 compares the customer name of the customer information recorded in the master data storage unit 32 with the name of the transfer requester of the transfer data acquired from the financial institution system 10. If they match, the deposit data registration unit 211 assigns the supplier code registered in the master data storage unit 32 to the deposit record in the deposit data storage unit 34.

(Consumption processing)
Next, the application processing system 20 executes an application process for billing and payment. This process is performed using a billing record and a deposit record to which the same transaction code is assigned.

  First, the control unit 21 of the application processing system 20 calculates the total amount of deposit as shown in FIG. 2 (step S1-1). Specifically, the first application processing unit 212 of the control unit 21 extracts the receipt record to which the supplier code to be applied is assigned from the receipt data storage unit 34, and calculates the deposit amount of the extracted receipt record. Add up.

  Next, the control unit 21 calculates the total amount charged (step S1-2). Specifically, the first application processing unit 212 of the control unit 21 extracts the charge record to which the supplier code to be applied is assigned from the charge data storage unit 33, and calculates the charge amount of the extracted charge record. Add up.

  Next, the control unit 21 checks whether or not the total deposit amount calculated in step S1-1 matches the total bill amount calculated in step S1-2 (step S1-3). Here, when both match (in the case of “YES” in step S1-3), the control unit 21 performs the erase operation (step S1-4). Specifically, the first application processing unit 212 of the control unit 21 assigns a common application code to the payment record recorded in the payment data storage unit 34 and the charge record recorded in the charge data storage unit 33. Then, the application flag including this application code is recorded.

  On the other hand, when the total amounts do not match (in the case of “NO” in step S1-3), the control unit 21 calculates a monetary range including the adjustment amount (step S1-5). Specifically, the first application processing unit 212 of the control unit 21 adds or subtracts the adjustment amount considering the transfer fee to the charge amount with respect to the charge amount. Here, the adjustment amount is an amount range that the customer can tolerate even when the deposit amount is different from the charge amount. The adjustment amount data and the adjustment amount data are held in the first application processing unit 212. For example, when the adjustment amount is “1000 yen”, the total amount charged is “33000 yen” and the amount range is “32000 to 34000 yen”.

  And the control part 21 confirms whether the money_receiving | payment total amount calculated in step S1-1 is contained in the money amount range calculated in step S1-5 (step S1-6). Here, when it is included in this amount range (in the case of “YES” in step S1-6), the control unit 21 performs the elimination (step S1-4). In this case as well, a common application code is assigned to all deposit records and billing records, and an application flag including this application code is recorded.

  On the other hand, when it is not included in the amount range (in the case of “NO” in step S1-6), the control unit 21 compares each billed amount with the total deposit amount (step S1-7). Specifically, the first application processing unit 212 of the control unit 21 compares the total deposit amount calculated in step S <b> 1-1 with the amount of each billing record recorded in the billing data storage unit 33. Here, if there is a match (in the case of “YES” in step S1-8), the control unit 21 performs the erase operation (step S1-4). In this case, the first application processing unit 212 assigns an application code common to the matched billing record and all the deposit records, and records the application flag including the application code.

On the other hand, if there is no match (in the case of “NO” in step S1-8), the control unit 21 compares each billed amount including the adjustment amount with the total deposit amount (step S1-9). ). Specifically, the first application processing unit 212 of the control unit 21 generates, for each billing record, an amount range obtained by adding or subtracting the adjustment amount to each billing amount recorded in the billing data storage unit 33. Then, the amount range in which the adjustment amount is adjusted is compared with the total deposit amount calculated in step S1-1. Here, when there is what is included in the amount range (in the case of “YES” in step S1-10), the control unit 21 performs the application (step S1-4). In this case, the first application processing unit 212 assigns an application code common to the matched billing record and all the deposit records, and records the application flag including the application code.

  On the other hand, when there is nothing included in the amount range (in the case of “NO” in step S1-10), the control unit 21 compares each deposit amount with the total amount charged (step S1-11). . Specifically, the first application processing unit 212 of the control unit 21 compares the total charge calculated in step S1-2 with the amount of each deposit record recorded in the deposit data storage unit 34. Here, if there is a match (in the case of “YES” in step S1-12), the control unit 21 performs the erase operation (step S1-4). In this case, the first application processing unit 212 assigns an application code common to the matched deposit record and all billing records, and records an application flag including the application code.

  On the other hand, if they do not match (in the case of “NO” in step S1-12), the control unit 21 compares each deposit amount including the adjustment amount with the total amount charged (step S1-13). Specifically, the first application processing unit 212 of the control unit 21 generates a deposit amount range obtained by adding or subtracting the adjustment range to the deposit amount recorded in the deposit data storage unit 34 for each deposit record. Then, the deposit amount range in which the adjustment amount is adjusted is compared with the charge total amount calculated in step S1-2. Here, when there is what is included in the amount range (in the case of “YES” in step S1-14), the control unit 21 performs the elimination (step S1-4). In this case, the first application processing unit 212 assigns an application code common to the matched deposit record and all billing records, and records an application flag including the application code.

  On the other hand, when it is not included in the amount range (in the case of “NO” in step S1-14), the control unit 21 performs a summing-up application process (step S1-15). This total consumption process will be described with reference to FIGS.

(Total application processing)
First, the control unit 21 of the consumption processing system 20 sorts the records to be consumed by date and amount (step S2-1). Specifically, the pattern development means 213 of the control unit 21 rearranges the receipt records and bill records recorded in the deposit data storage unit 34 and the bill data storage unit 33 by date and amount.

  Next, the control unit 21 compares the number of records recorded in the deposit data storage unit 34 and the billing data storage unit 33 (step S2-2). Specifically, the pattern development means 213 of the control unit 21 counts the number of billing records recorded in the billing data storage unit 33 and the number of deposit records recorded in the deposit data storage unit 34, and compares the two. To do.

  Then, the control unit 21 performs pattern development on the data having the larger number of records (step S2-3). When the number of deposit records is large (in the case of “deposit” in step S2-3), the pattern development means 213 performs pattern development using the deposit records recorded in the deposit data storage unit 34 (step S2-4). On the other hand, when the number of billing records is large (in the case of “billing” in step S2-3), the pattern development unit 213 performs pattern development using the billing record recorded in the billing data storage unit 33 (step S2-5). ).

In the present embodiment, four records dated to 1 day, 3 records dated to 2 days, etc. are recorded in the data memory unit having a large number of records in the billing data memory unit 33 or the deposit data memory unit 34. Assuming that Therefore, the pattern development unit 213 groups the records recorded in the data storage unit for each date. Here, the first date is the first group, and the second date is the second group. Then, for each date (group), the items are rearranged in descending order. As a result, a table 510 shown in FIG. 6 is generated. First, a summation pattern is generated focusing on the record (old month record) of the oldest date (here, the first group dated 1 day). Here, for explanation, a table 520 in which the identifier (sequence number: SEQ) shown in FIG. 6 is assigned to each record is generated.

(Pattern development processing)
Next, the pattern development process will be described with reference to FIG. In this process, the control unit 21 of the consumption processing system 20 generates a grand total pattern for this group (step S3-1). Specifically, the pattern development unit 213 of the control unit 21 adds up the amounts of the records in this group to generate a table 530 including the total pattern shown in FIG.

  Next, the control unit 21 generates a pattern by partially combining the records of this group. Here, the pattern development unit 213 generates a pattern obtained by subtracting n records from the total pattern. Therefore, first, the pattern development means 213 of the control unit 21 performs initial setting of the reduction number n (step S3-2). In this case, “1” is set as the subtraction number n using the initial value recorded in the start value memory 22.

  And the control part 21 produces | generates a pattern (n missing pattern) using the set reduction | decrease n (step S3-3). Specifically, the pattern development unit 213 generates a “one missing” pattern in which records are extracted one by one. Here, the same number of patterns as the number of records is generated. In this case, the pattern development unit 213 calculates the total value of the SEQs constituting the sum pattern, and forms the pattern so that the smaller total value comes first.

  Next, the control unit 21 checks whether or not the capacity of the pattern memory 23 is exceeded (step S3-4). Specifically, when the generated pattern is stored in the pattern memory 23, the pattern development unit 213 checks whether the capacity of the pattern memory 23 is less than the capacity. Here, it is determined by comparing the total number of generated patterns with the recordable number set in advance in the pattern memory 23. If the memory capacity is exceeded (“NO” in step S3-4), the pattern development process is terminated. In this case, the reduction number n recorded in the start value memory 22 is updated. Thus, next time, pattern development is resumed from the subtraction number n recorded in the start value memory 22.

  On the other hand, when the memory capacity is not exceeded (“YES” in step S3-4), the pattern development unit 213 records the generated summation pattern in the pattern memory 23 (step S3-5). In this case, the pattern development unit 213 sums the amounts (billed amounts or deposit amounts) of the records constituting the generated pattern and records them in the pattern memory 23 together with this amount. Here, the table 540 to which the “1 missing” pattern shown in FIG. 7 is added is recorded.

  Next, the control part 21 changes the reduction number n (step S3-6). Specifically, the pattern development unit 213 sets a value (n + 1) obtained by adding “1” to the reduction number n as the reduction number n in order to generate the next n missing pattern.

  And the control part 21 judges whether a pattern production | generation is further possible (step S3-7). Specifically, it is determined whether or not the set reduction number n exceeds “number of records−2”. When the subtraction number n is “number of records−1”, it is a pattern composed of individual records, and therefore it is not added up. If the reduction n exceeds “number of records−2” by repeating pattern development (in the case of “NO” in step S3-7), the pattern generation processing is terminated.

On the other hand, when further pattern generation is possible (in the case of “YES” in step S3-7)
The pattern development unit 213 generates a pattern using the set “n” (step S3-3). For example, when generating a “two missing” pattern, a table 550 to which six patterns are added is generated as shown in FIG.

If the memory capacity is exceeded in step S3-4, or if all patterns are generated in step S3-7, the process returns to the original process (FIG. 3).
And the control part 21 sorts the summation pattern stored in the pattern memory 23 using money (step S2-6). Specifically, the pattern development means 213 rearranges them in descending order using the total amount of each sum pattern. In this case, in the case of the same amount, rearrangement is performed so as to maintain the original ranking. As a result, the developed summed patterns are rearranged as shown in a table 560 shown in FIG.

  Next, as shown in FIG. 5, the control unit 21 of the consumption processing system 20 performs collation (step S4-1). Specifically, the second application processing unit 214 of the control unit 21 takes out the summation patterns recorded in the pattern memory 23 in the sort order, and compares the sum of each summation pattern with the sum of the record of the counterpart of the appreciation. When the pattern is developed using the deposit record, matching with each billing record is performed, and when the pattern is developed using the billing record, matching with each deposit record is performed. The summed pattern used for matching is deleted from the pattern memory 23.

  When matching is possible using the sum pattern recorded in the pattern memory 23 (in the case of “YES” in step S4-2), a consumption flag is recorded for the record included in this sum pattern (step S4). -3). In this case, the second application processing unit 214 assigns an application code common to the records constituting the matched sum pattern and the counterpart record, and records an application flag including the application code. When all the records recorded in any of the data storage units are erased (in the case of “YES” in step S4-4), the erase process is terminated. On the other hand, if there are still unerased records (in the case of “NO” in step S4-4), the process returns to the comparison of the number of records (step S2-2), and the pattern generation is performed again from the beginning.

  In addition, when the matching cannot be performed using the sum pattern recorded in the pattern memory 23 (in the case of “NO” in step S4-2), the second consumption processing unit 214 is not used for the consumption. It is confirmed whether or not the used summation pattern remains in the pattern memory 23 (step S4-5).

  If unused summation patterns still remain ("YES" in step S4-5), collation is performed using this summation pattern (step S4-1). In this case, the sum pattern including the record to which the consumption flag has already been assigned by the previous matching is not used.

  On the other hand, even if the total sum pattern recorded in the pattern memory 23 is used, if there are still unerased records (in the case of “NO” in step S4-5), is there an unexpanded pattern? It is confirmed whether or not (step S4-6). Specifically, the second consumption processing unit 214 of the control unit 21 determines whether or not there is a reduction number n that cannot be developed due to the capacity of the pattern memory 23 in the pattern development process shown in FIG. To do. Specifically, it is determined whether or not the reduction number n recorded in the start value memory 22 has reached “number of records−2”.

If there is an unexpanded pattern (in the case of “YES” in step S4-6), the pattern expansion is performed again using the subtraction number n recorded in the start value memory 22, so that step S3- in FIG. Return to 3. In this case, a summation pattern is generated using a record recorded in the deposit data storage unit 34 or the billing data storage unit 33 and not yet applied with an application flag.

  On the other hand, when no undeveloped pattern remains (in the case of “NO” in step S4-6), it is confirmed whether or not the entire process has been completed (step S4-7). That is, when the pattern development for each date group is completed, but the entire process is not completed (in the case of “NO” in step S4-7), the remaining records as in the table 570 shown in FIG. Are combined into one to perform a clearing process (step S4-8). In this case, the group for each date is canceled. Then, a new SEQ is assigned to all records that have been recorded in the deposit data storage unit 34 or the billing data storage unit 33 and have not yet been deleted. Then, the number of records not yet erased in the deposit data storage unit 34 and the billing data storage unit 33 is compared, and the consumption process is performed from step S2-3 shown in FIG. 3 using these records. On the other hand, if the entire process has been completed (in the case of “YES” in step S4-7), the application process is terminated.

As described above, according to the present embodiment, the following effects can be obtained.
In the above embodiment, the control unit 21 generates a pattern (n missing pattern) using the set reduction number n (step S3-3). If the memory capacity is not exceeded, the pattern development unit 213 records the generated summation pattern in the pattern memory 23 (step S3-5). Thereby, collation can be performed collectively using the summation pattern recorded in the pattern memory 23.

  In the above embodiment, when the pattern memory 23 exceeds the memory capacity, the pattern development process is terminated. In this case, the reduction number n recorded in the start value memory 22 is updated. Thereby, next time, the pattern development can be restarted from the subtraction number n recorded in the start value memory 22. When the number of records is large, the number of ways of combining the summation patterns becomes enormous. Even in this case, the summing pattern can be developed in a limited resource (memory capacity) and the consumption process can be performed. When pattern development is resumed, a combined pattern is generated using a record recorded in the deposit data storage unit 34 or the billing data storage unit 33 and not yet applied with an application flag. As a result, the consumption process can be performed using the narrowed records.

  In the above embodiment, the control unit 21 develops a pattern of data having a larger number of records (step S2-3). As a result, the records divided in various forms can be collectively processed.

  In the above embodiment, the pattern development unit 213 groups the records recorded in the data storage unit for each date. Here, the data is rearranged in descending order for each date (group). As a result, it is possible to preferentially erase old records (old moon records) and records with large amounts.

  Further, when generating a pattern (n missing pattern) using the subtraction number n (step S3-3), the control unit 21 forms the pattern so that the one with the smallest total value of the SEQ that constitutes the combined pattern comes first. To do. And the control part 21 sorts the summation pattern stored in the pattern memory 23 using money (step S2-6). In this case as well, old records and records with large amounts can be deleted preferentially.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the records recorded in the billing data storage unit 33 or the deposit data storage unit 34 are rearranged in descending order of amount for each date (group). A combined pattern is generated for each group and recorded in the pattern memory 23. Alternatively, when the pattern development of a specific group is completed, the pattern development of the next group may be sequentially performed until the capacity of the pattern memory 23 is reached.

  In the above embodiment, the number of records recorded in the deposit data storage unit 34 and the billing data storage unit 33 is compared (step S2-2). Then, the control unit 21 performs pattern development on the data having the larger number of records (step S2-3). The determination of the target for pattern development is not limited to this method. For example, it may be fixed to either deposit or billing, or may be determined for each business partner. In this case, the type of pattern expansion is registered in the supplier master. And the control part 21 of the consumption processing system 20 determines the direction of pattern development based on the supplier code which performs a consumption process. Thereby, a total pattern can be produced | generated according to the tendency (lump sum payment or installment payment) of a business partner.

  In the above embodiment, the number of records recorded in the deposit data storage unit 34 and the billing data storage unit 33 is compared (step S2-2), and the control unit 21 develops the pattern development of the data with the larger number of records. Perform (step S2-3). In this case, both patterns may be developed. In this case, for example, a deposit data pattern memory and a billing data pattern memory are prepared, and the developed total pattern is stored in these patterns. In the case of using the pattern memory, the distribution of the pattern memory is determined according to the number of records, and each pattern development is performed using the allocated memory capacity. As a result, the application can be performed using a variety of additional patterns.

  In the above embodiment, the control unit 21 of the consumption processing system 20 performs collation (step S4-1). Specifically, the second application processing unit 214 of the control unit 21 compares the amount of each sum pattern recorded in the pattern memory 23 with the amount of the record of the application partner. In this case, the adjustment amount can be adjusted.

1 is a schematic diagram of a system according to an embodiment of the present invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the pattern expansion | deployment of one Embodiment of this invention. Explanatory drawing of the pattern expansion | deployment of one Embodiment of this invention. Explanatory drawing of the pattern expansion | deployment of one Embodiment of this invention. Explanatory drawing of the pattern expansion | deployment of one Embodiment of this invention.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 20 ... Consumption processing system, 21 ... Control part, 211 ... Deposit data registration part, 212 ... First consumption processing means, 213 ... Pattern expansion means, 214 ... Second consumption processing means, 22 ... Start value memory, 23 ... pattern memory, 33 ... billing data storage unit, 34 ... deposit data storage unit.

Claims (5)

A billing record using a billing data storage unit that records a billing record that includes a billing amount, a depositing data storage unit that records a depositing record that includes a depositing amount, and a pattern memory control unit that records a pattern used for application And a receipt record to check against,
The control means is
Performing a pattern development process of generating a combined pattern by combining either a billing record or a deposit record until a reference number set based on the memory capacity of the pattern memory is reached, and recording it in the pattern memory;
Calculate the sum of the patterns recorded in the pattern memory, rearrange them in the descending order of the amounts, and sequentially execute the matching process with the record that has not been subjected to the pattern development process,
In the case of matching, a step of performing a collation process for recording a consumption flag in an element record constituting this sum pattern is executed,
Even if all the sum patterns recorded in the pattern memory are collated, if there are still records that are not erased, the pattern development processing and collation processing are repeated using the remaining records. Application processing method. The billing record and the deposit record contain data about the billing date and the deposit date,
Each group consists of a billing record with the same billing date or a deposit record with the same deposit date,
2. The application processing method according to claim 1, wherein the pattern development process and the collation process are executed for each group. The pattern development process compares the number of billing records with the number of deposit records,
3. A summation pattern is generated using a record having a larger number of bill records or deposit records, and the summation pattern is recorded in the pattern memory until the reference number is reached. Application method described in 1. A billing record using a billing data storage unit that records a billing record that includes a billing amount, a depositing data storage unit that records a depositing record that includes a depositing amount, and a pattern memory control unit that records a pattern used for application And a deposit record to check against
The control means is
Means for performing a pattern development process of generating a summation pattern by combining either a billing record or a deposit record until a reference number set based on a memory capacity of the pattern memory is reached, and recording it in the pattern memory;
Calculate the sum of the patterns recorded in the pattern memory, rearrange them in the descending order of the amounts, and sequentially execute the matching process with the record that has not been subjected to the pattern development process,
A means for performing a matching process for recording a consumption flag in an element record constituting the summing pattern when matched,
Even if all the sum patterns recorded in the pattern memory are collated, if there are still records that are not erased, the pattern development processing and collation processing are repeated using the remaining records. Application processing system. A billing record using a billing data storage unit that records a billing record that includes a billing amount, a depositing data storage unit that records a depositing record that includes a depositing amount, and a pattern memory control unit that records a pattern used for application And a deposit record to check against
The control means;
Means for performing a pattern development process of generating a summation pattern by combining either a billing record or a deposit record until a reference number set based on a memory capacity of the pattern memory is reached, and recording it in the pattern memory;
Calculate the sum of the patterns recorded in the pattern memory, rearrange them in the descending order of the amounts, and sequentially execute the matching process with the record that has not been subjected to the pattern development process,
In the case of matching, it is made to function as a means for performing a collation process for recording a consumption flag in an element record constituting this sum pattern,
Even if all the sum patterns recorded in the pattern memory are collated, if there are still records that are not erased, the pattern development processing and collation processing are repeated using the remaining records. Consumption processing program to be performed.

Images