JP2006323532A - Credit deletion device, credit deletion method and credit deletion program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To attain the end batch deletion of a plurality of credits corresponding to payment performed in a batch to a plurality of credits. <P>SOLUTION: A plurality of claim detail data are stored in a claim detail table storage part 13. A total invoice number assignment processing part 17 divides the stored claim detail data into the sets of claim detail data having the same "total unification units", and assigns total invoice numbers to each set, and applies the total invoice numbers assigned to the set including the claim detail data to the claim detail data. A total invoice deletion processing part 20 calculates the total sum of the invoice by adding the claim sum of the claim detail data having the same total invoice numbers for each of total invoice numbers. The total invoice deletion processing part 20 executes the deletion of credits by using all the claim detail data having the total invoice number of the total invoice whose total invoice sum is matched with the sum of payment as the object of deletion. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a claim clearing apparatus, a claim clearing method, and a claim clearing program for clearing a claim corresponding to deposit.

  For example, in Japan, there is a demand that a plurality of billing specifications have the same “summary unit” and they want to be billed collectively. If a system that meets this demand is provided, it is likely that payments will be made collectively for multiple billing details that have been billed at once. It is expected that there will be a desire to “perform all at once”. However, although the Applicants have provided various systems related to the application of claims, they have provided a system that collects billing specifications having the same “summary unit” from a plurality of billing specifications. Therefore, no system has been provided that has a function that meets the demands expected when the system is provided.

Currently, a number of literatures disclose techniques related to the application of receivables corresponding to deposits. For example, there is an accounting processing method and an accounting processing device that store information on accounts receivable to a seller, and cancel the accounts receivable information corresponding to the receipt based on the receipt from the seller. In this case, when receipt schedule information from the seller is received, the accounts receivable information corresponding to the receipt schedule information is erased and reserved. After that, when the deposit corresponding to the deposit schedule information is performed from the seller, the seller information reserved for cancellation is extracted, and the extracted account receivable information is deleted (see, for example, Patent Document 1). .)
JP 2003-263542 A

  However, since the above-mentioned Patent Document 1 does not describe that the plurality of claims corresponding to the deposits made to the plurality of claims are collectively performed, the above-mentioned is expected. I would like to apply all of the multiple receivables that correspond to deposits made to multiple receivables at once. It would be very promising to provide a new system with a function that meets this demand.

  Accordingly, the present invention provides a claims clearing apparatus, a claims clearing method, and claims receivable that can collectively perform a plurality of claims corresponding to a deposit made to a plurality of claims. The purpose is to provide an embedded program.

  The claim clearing apparatus of the present invention is a detailed data storage means (13) for storing a plurality of detailed data having a plurality of items, and a part of the plurality of items of the detailed data is a summary unit for enclosing the detailed data, Each of the detailed data stored in the detailed data storage means is divided into a set of detailed data in which the partial items of the summary unit are the same, and one summary specification number is assigned to each of the sets, and each detailed data Are stored in the detailed data storage means for each summary specification number when the claims are cleared, and the summary specification number (16, 17) for assigning the summary specification number assigned to the set including the specification data in The billing amount of the item data with the same summary line number is added up to determine whether it matches the deposit amount, and all the item data with the summary line number that matches the deposit amount is to be deleted. Creditor clearing processing means for scrubbing receivables (20, 21), characterized by comprising a.

  The claim clearing apparatus of the present invention is a detailed data storage means (13) for storing a plurality of detailed data having a plurality of items, and a part of the plurality of items of the detailed data is a first summary unit for consolidating the detailed data. The detailed data stored in the detailed data storage means is divided into sets of detailed data in which the partial items of the first summary unit are the same, and one first summary specification number is assigned to each set. And a detail grouping means (16) for assigning a first summary detail number assigned to each detail data to a set including the detail data, and one of the partial items as the first summary unit. The item of the section is set as a second summary unit, and each of the detailed data stored in the detailed data storage means is divided into sets of detailed data in which the partial items of the second summary unit are the same. Second summary item number And a second summary wrapping means (17) for assigning a second summary detail number assigned to the set including the detail data to each detail data, and a second summary detail number at the time of clearing the claim Every time, the billing amount of the detail data with the same second summary item number stored in the detail data storage means is summed to determine whether it matches the deposit amount, and the second summary that matches the deposit amount The first receivable application processing means (20) that performs the application of the receivables with all the detailed data assigned with the detailed numbers as the object of application, and the first summary item number are stored in the detailed data storage means. The sum of the billing amount of the detailed data to which the same first summary line number is assigned is judged whether it matches the deposit amount, and all the detailed data to which the first summary line number that matches the deposit amount is deleted Bonds for inclusion A second receivable clearing processing means for the scrubbing (21), characterized by comprising a.

  In the claim clearing method according to the present invention, a part of the plurality of items of the detail data is used as a summary unit for summarizing the detail data, and the plurality of detail data stored in the detail data storage means (13) is stored in the summary unit. The partial items are divided into the same set of detail data, one summary detail number is assigned to each set, and each detail data is assigned the summary detail number assigned to the set including the detail data. At the time of the detailed statement procedure (S201 to S202, S203 to S204) and the retirement of claims, the billing amount of the detailed data to which the same summary specification number stored in the detail data storage means is assigned for each summary specification number. Receivables application processing procedure to determine whether the total amount matches with the deposit amount, and to reconcile the receivable with all the item data with the summary line number that matches the deposit amount as the object of application ( 407～S409, characterized in that it has a S410~S412), the.

  In the claim clearing method according to the present invention, a part of a plurality of items in the detail data is defined as a first summary unit for summarizing the detail data, and each detail data stored in the detail data storage means (13) is the first data. The above-mentioned partial items of one summary unit are divided into the same set of detailed data, and each set is assigned one first summary specification number, and each detailed data is assigned to a set including the detailed data. A first detail summarizing procedure (S201 to S202) for assigning a first summarization detail number, and a part of the part of the first summarization unit as a second summarization unit, the detail data storage Each of the detailed data stored in the means is divided into sets of detailed data in which the partial items of the second summary unit are the same, one second summary specification number is assigned to each set, and each specification The detailed data is included in the data The second detail summarizing procedure (S203 to S204) for assigning the second summarization detail number assigned to the same number stored in the detail data storage means for each second summarization detail number at the time of reversal of bonds The sum of the billing amount of the detail data to which the second summary item number is assigned is judged whether it matches the deposit amount, and all the detail data to which the second summary item number that matches the deposit amount is erased As the first receivable application processing procedure (S407 to S409) for performing the application of the receivable, and the details given the same first summary specification number stored in the detail data storage means for each first summary specification number It is determined whether or not it matches the deposit amount by summing up the billed amounts of data, and all the detailed data assigned with the first summary item number that matches the deposit amount is applied to the application to cancel the second And Kenshokomi procedure (S410~S412), characterized by comprising a.

  The loan clearing program of the present invention uses a plurality of details stored in the detail data storage means (13), with the computer (1) using a part of a plurality of items of the detail data as a summary unit for enclosing the detail data. The data is divided into a set of detailed data in which the partial items of the summary unit are assigned the same detailed data, and a single detailed specification number is assigned to each set, and each detailed data is assigned to a set including the detailed data. The same summary specification number stored in the specification data storage means is assigned for each summary specification number when the summary specification procedure (S201 to S202, S203 to S204) for assigning the summary specification number and receivables are cleared. Judging the amount billed in the item data to determine whether it matches the deposit amount, and deleting all the item data with the summary item number that matches the deposit amount as the object of application Receivable clearing procedure (S407~S409, S410~S412) for performing only, characterized in that to execute a, a.

  The claim clearing program according to the present invention uses each item stored in the detail data storage means (13) in the computer (1), with some items of the detail data as a first summary unit for enclosing the detail data. The detailed data is divided into sets of detailed data in which the partial items of the first summary unit are the same, one first summary specification number is assigned to each set, and the detailed data is included in each detailed data. A first summarization procedure (S201 to S202) for assigning a first summarization detail number assigned to a set, and a part of the one item that is the first summarization unit, a second summarization unit The detailed data stored in the detailed data storage means is divided into sets of detailed data in which the partial items of the second summary unit are the same, and one second summary specification number is assigned to each set. Number of each The second summary wrapping procedure (S203 to S204) for assigning the second summary specification number assigned to the set including the detail data to the data, and for each second summary specification number at the time of clearing the bond, The sum of the billing amount of the detail data to which the same second summary item number stored in the data storage means is added is determined to match the deposit amount, and the second summary item number that matches the deposit amount is given. The first receivable application processing procedure (S407 to S409) for performing the application of the receivable with all the detailed data as the object of application, and the same first stored in the detailed data storage means for each first summary item number It is determined whether the sum of the billing amount of the detail data to which the one summary line number is assigned matches the deposit amount, and all the detail data to which the first summary item number that matches the deposit amount is deleted A second receivable clearing procedure for performing scrubbing receivables Te (S410~S412), characterized in that for the execution.

  It should be noted that “(sign)” referred to in this column only exemplifies a corresponding configuration in a column (the best mode for carrying out the invention) to be described later, and does not indicate any claim in the claims. The interpretation is not limited.

  According to the present invention, a plurality of detailed data is divided into detailed data having the same summary unit (summary unit, first summary unit, second summary unit), and each summary item number (summary item number, first summary item number) is divided. , The second summary specification number). Then, at the time of application for receipt, the sum of the billing amount of the item data to which the summary item number has been assigned is totaled, and the item data to which the summary item number to which the total amount matches the receipt amount is applied to the application. It is carried out. For this reason, it is possible to collectively erase the plurality of detailed data corresponding to the deposits made to the multiple detailed data at once.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

  First, the same “bundling unit” is selected from a plurality of billing specifications, which is a premise of receivable revocation processing in which reversal of a plurality of receivables is collectively performed on a receipt made in a lump for a plurality of receivables of the present invention. ”(In this embodiment, there are“ monthly summary unit ”and“ total summary unit ”).

  Hereinafter, by assigning a monthly invoice number to a billing item having the same “Monthly Summary Unit”, a process for grouping the billing details having the same “Monthly Summary Unit” among a plurality of billing items (hereinafter referred to as “monthly unit”) , Monthly numbering process), and a process that bundles the billing details with the same “total summary unit” by assigning the total invoice number to the billing details with the same “total summary unit” (hereinafter referred to as total) The outline of the numbering process will be described with reference to FIGS. 1 to 3 are diagrams for explaining the outline of the monthly numbering process and the total numbering process in the present embodiment. Note that the total numbering process is a process in which a set of billing details bundled in “monthly summary unit” by the monthly numbering process is further bundled in “total summary unit”.

The “monthly summary unit” (summary unit, first summary unit) is made up of a part of items in the billing specification. However, in this embodiment, the “monthly summary unit” is the “company” of the billing party, the “payment date” of the payer who pays the price, the “payer” who pays the price, or pays in a lump sum or in cash "Payment terms" such as whether to pay with a bill or bill, "Billing party", "Currency", and "Monthly billing unit item" for which the price is charged. Here, the monthly billing unit item is prepared so that the billing source can create a monthly invoice by batching the billing details as desired by the billing source. Can be arbitrarily selected and set from the items included in. In this embodiment, it is assumed that a sales organization (an organization that sells products), a distribution channel (a route through which products are distributed), and a product department (a department that manufactures products) are combined.
In the monthly numbering process, the same billing details for the company, closing date, payer, payment terms, billing party, currency, and monthly billing numbering items are collected from multiple billing details. Next invoice is created.

The “total summarizing unit” (summarizing unit, second summarizing unit) includes a part of the item of the billing specification which is the “monthly summarizing unit”. However, the “total summarization unit” is a “closing date”, “payer”, “currency”, and “total billing number unit item”. The total invoice numbering unit field is prepared so that the billing source can create a total invoice by batching the billing details as desired by the billing source. Can be arbitrarily selected and selected from the items of the billing details (including items selected and set as the monthly billing number unit items). In this embodiment, the sales organization.
In the total numbering process, a total invoice is created by collecting the same billing details for the due date, payer, currency, and total billing numbering unit items from a plurality of billing details.
The billing source may not set one or both of the monthly billing unit item and the total billing unit unit item.

FIG. 1 is a diagram showing an example of the structure of a company that is charged and pays for the fee. In FIG. 1, it is assumed as follows.
It is assumed that α customer A branch office is a billing destination for the goods purchased by itself (α customer A branch office) and its subordinate organizations (not shown). It is assumed that the α customer B branch office is a billing destination for goods purchased by itself (α customer B branch office) and its subordinate organizations (not shown). It is assumed that the payer of the billing details for which the customer A branch office is billed and the billing details for which the customer B branch is billed is the customer headquarter.

Further, it is assumed that the α customer a sales office is a billing destination for goods purchased by itself (α customer a sales office) and its subordinate organizations (not shown). It is assumed that α customer b sales office is a billing destination for the goods purchased by itself (α customer b sales office) and its subordinate organizations (not shown). It is assumed that the α customer c sales office is a billing destination for the goods purchased by itself (α customer c sales office) and its subordinate organizations (not shown). The billing details for the billing details for the α customer a sales office, the billing details for the α customer b sales location, and the billing details for the α customer c sales location. The payer is assumed to be α customer C branch office.
As described above, in this embodiment, an organization (for example, a branch office or a sales office) that charges a fee may be different from an organization that pays the price (for example, a branch office or a sales office).

  Fig. 2 shows the items necessary for explaining the monthly numbering process and total numbering process (company, closing date, payer, payment terms, billing destination, currency, monthly billing unit item, total billing number) 6 billing details describing the contents of the unit item) are shown.

The following is an overview of the monthly numbering process.
Among the six billing items, each billing item with item numbers “0001” and “0002” has the same “Monthly Summary Unit” (company, closing date, payer, payment terms, billing party, currency, monthly billing). However, the “monthly summary unit” is different from the billing details of the specification numbers “0003” to “0006”. Therefore, as shown in FIG. 2 and FIG. 3, the bill number “M1000” of the monthly bill is assigned to each bill detail with the detail numbers “0001” and “0002”. With this invoice number “M1000”, the invoice details with the item numbers “0001” and “0002” can be collected together.

  Among the six billing specifications, each of the billing numbers with the specification numbers “0003” and “0004” has the same “monthly summary unit”, but the specification numbers “0001”, “0002”, “0005” The “monthly summary unit” is different from each billing specification of “0006”. Therefore, as shown in FIG. 2 and FIG. 3, the billing number “M1001” of the monthly bill is assigned to each billing specification with the detail numbers “0003” and “0004”. With this invoice number “M1001”, the invoice details with the specification numbers “0003” and “0004” can be collected together.

Among the six billing specifications, each of the billing specifications with the specification numbers “0005” and “0006” has the same “monthly summary unit”, but each of the claim specifications with the specification numbers “0001” to “0004” Have different “monthly summary units”. Accordingly, as shown in FIG. 2 and FIG. 3, the bill number “M1002” of the monthly bill is assigned to each bill detail with the detail numbers “0005” and “0006”. By using the invoice number “M1002”, the invoice details with the item numbers “0005” and “0006” can be collected together.
The above is the outline of the monthly numbering process.

The following is an overview of the total numbering process.
Among the six billing specifications, each of the billing specifications with the item numbers “0001” to “0004” has the same “total summary unit” (closing date, payer, currency, total billing number unit item). The “total summary unit” is different from each billing specification of the specification numbers “0005” and “0006”. Therefore, as shown in FIG. 2 and FIG. 3, the bill number “T100” of the total bill is numbered and assigned to each billing specification of “0001” to “0004”. With this invoice number “T100”, the invoice details of the item numbers “0001” to “0004” can be made together.

Among the six billing specifications, each of the billing specifications with the specification numbers “0005” and “0006” has the same “total summarizing unit”, but the respective claiming specifications with the specification numbers “0001” to “0004” “Total summary unit” is different. Therefore, as shown in FIG. 2 and FIG. 3, the bill number “T101” of the total bill is assigned to each bill number with the detail numbers “0005” and “0006”. With the invoice number “T101”, the invoice details with the item numbers “0005” and “0006” can be collected together.
The above is the outline of the total numbering process.

Next, an outline of a claim clearing process (collective claim clearing process) in which a plurality of claims are collectively erased with respect to a deposit made for a plurality of claims will be described with reference to FIG. . FIG. 4 is a diagram for explaining the outline of the collective bond cancellation process in the present embodiment.
As shown in FIG. 4A, the total amount of all the billing details of the payer who matches the transfer requester who made the deposit is compared with the deposit amount. If, as a result of the comparison, the total amount of all the billing details of the payer that matches the transfer requester who made the payment matches the deposit amount, all the billing details of the payer are subject to application, Do the erase.

  If, as a result of the comparison, the total amount of all invoice details of the payer that matches the transfer requester who made the payment does not match the receipt amount, all the invoices from which the total invoice originated The total invoice amount (hereinafter referred to as the total invoice amount) is obtained, and the total invoice amount of the total invoice is compared with the receipt amount. As a result of comparison, if the total invoice amount and the receipt amount of any of the total invoices match, all the billing details that are the source of the matching total invoices will be subject to the cancellation, and Do.

  As a result of the comparison, if the deposit amount does not match the total invoice amount of any total invoice, the total amount of all the invoice items that are the basis of the monthly invoice (hereinafter, The monthly invoice amount is calculated, and the monthly invoice amount of the monthly invoice is compared with the receipt amount. As a result of comparison, if the monthly invoice amount and the deposit amount of any monthly invoice match, all the billing statements that are the source of the matching monthly invoice will be subject to retirement, Do the erase.

As a result of the comparison, if the deposit amount does not match the monthly invoice amount of any monthly invoice, the application target is not automatically specified. In this case, the operator manually selects the billing details to be erased for the deposit amount.
The above is the outline of the collective bond clearing process.

  Further, the outline of the collective bond cancellation process described above will be described based on a specific example. The billing details for which “α customer headquarters” is the payer are only the billing details of the item numbers “1001” to “1006”, and each of these billing items includes the monthly billing shown in FIG. The invoice number and the total invoice number are assigned by assigning the monthly invoice number by the above-mentioned monthly numbering process, and the total invoice number is assigned by the above-mentioned total numbering process. Suppose that It is assumed that the transfer client who made the deposit is “α customer headquarters”.

When the deposit amount is “7500”, it is as follows.
The total amount of money “7500” (= 1000 + 500 + 2000 + 1000 + 1000 + 2000) is obtained by adding up the amounts of all the billing details (invoice details of the specification numbers “1001” to “1006”) of the payer that matches the transfer requester. Compare the deposit amount “7500” with the total amount “7500” of all billing details of the payer that matches the transfer requester, and the two match, so all the payers that match the transfer requester The details (the billing details of the item numbers “1001” to “1006”) are to be erased, and are erased.

When the deposit amount is “3000”, it is as follows.
The total amount “7500” is obtained by adding the amounts of all the billing details (billing details of the detail numbers “1001” to “1006”) of the payer that matches the transfer requester. Compare the deposit amount “3000” with the total amount “7500” of all the billing details of the payer that matches the transfer requester, and the two do not match. Process.

The total amount (total invoice amount) “4500” is obtained by adding the amounts of all the invoice details (invoice details of the item numbers “1001” to “1004”) that are the basis of the total invoice of the total invoice number “T201”. (= 1000 + 500 + 2000 + 1000). Also, the total amount (total invoice amount) is obtained by adding the amounts of all the billing details (the billing details of the specification numbers “1005” and “1006”) that are the basis of the total bill of the total bill number “T202”. “3000” (= 1000 + 2000) is obtained. The deposit amount “3000” is compared with the total invoice amount “4500” of the total invoice of the total invoice number “T201”, and the total invoice amount “3000” and the total invoice number “T202” are compared. The total invoice amount “3000” is compared.
Since the total invoice amount “3000” of the total invoice of the total invoice number “T202” matches the deposit amount “3000”, all the invoice details that are the basis of the total invoice of the total invoice number “T202” (A billing specification with the item numbers “1005” and “1006”) is the object of the deletion and is deleted.

When the deposit amount is “1500”, it is as follows.
The total amount “7500” is obtained by adding the amounts of all the billing details (billing details of the detail numbers “1001” to “1006”) of the payer that matches the transfer requester. Compare the deposit amount "1500" with the total amount "7500" of all billing details of the payer that matches the transfer requester. Process.

The total amount (total invoice amount) “4500” is obtained by adding the amounts of all the invoice details (invoice details of the item numbers “1001” to “1004”) that are the basis of the total invoice of the total invoice number “T201”. " Also, the total amount (total invoice amount) is obtained by adding the amounts of all the billing details (the billing details of the specification numbers “1005” and “1006”) that are the basis of the total bill of the total bill number “T202”. Find “3000”. The deposit amount “1500” is compared with the total invoice amount “4500” of the total invoice of the total invoice number “T201”, and the total invoice amount “1500” and the total invoice number “T202” are compared. The total invoice amount “3000” is compared.
Since the deposit amount “1500” does not match the total invoice amount of any total invoice, the billing details are deleted in units of monthly invoices.

Total amount (monthly invoice amount) by summing up the amounts of all billing items (invoice details with item numbers “1001” and “1002”) that became the basis of the monthly invoice with monthly invoice number “M2000” ) "1500" (= 1000 + 500) is obtained. Also, the total amount (monthly billing) is summed up for the sum of the amounts of all billing details (detailed billing details “1003” and “1004”) that are the basis of the monthly bill with the monthly bill number “M2001”. Document amount) “3000” (= 2000 + 1000) is obtained. Also, the total amount (monthly billing) is added to the sum of the amounts of all billing details (detailed billing details “1005” and “1006”) from which the monthly bill with the monthly bill number “M2002” is based. Document amount) “3000” (= 1000 + 2000) is obtained.
The deposit amount “1500” is compared with the monthly invoice amount “1500” of the monthly invoice number “M2000”, and the monthly amount of the deposit amount “1500” and the monthly invoice number “M2001” is compared. The monthly invoice amount “3000” of the invoice is compared, and the deposit amount “1500” is compared with the monthly invoice amount “3000” of the monthly invoice number “M2002”.
Since the monthly invoice amount “1500” matches the monthly invoice amount “1500” of the monthly invoice number “M2000”, the monthly invoice number “M2000” becomes the source of the monthly invoice All the billing details (the billing details with the specification numbers “1001” and “1002”) are subject to the deletion and are deleted.

The claim clearing apparatus having the function of realizing the monthly numbering process, the total numbering process, and the collective claim clearing process outlined above will be described with reference to FIG. FIG. 5 is a functional block diagram showing the function of the claim clearing apparatus in the present embodiment.
5 includes a slip table storage unit 11, a parent-child master database 12, a billing details table storage unit 13, a deposit details table storage unit 14, a billing data processing unit 15, and a monthly bill number numbering process. Unit 16, total invoice number numbering processing unit 17, payment details registration unit 18, payer application processing unit 19, total invoice application processing unit 20, and monthly invoice application processing unit 21 have.

  The slip table storage unit 11 stores accounting slip information (slip data), an example of which is shown in FIG. FIG. 6 is a diagram showing an example of the contents stored in the slip table storage unit 11. Items of the slip table stored in the slip table storage unit 11 shown in FIG. 6 include “company”, “fiscal year”, “accounting slip number”, “billing item number”, “sales organization”, “distribution channel”. , "Production Department", "Payer", "Payment Terms", "Billing Party", "Billing Date", "Item", "Net Amount (Voucher Currency)", "Tax Amount (Voucher Currency)", and "Currency" There is.

The item "Company" stores the billing source of the accounting slip, the item "Fiscal year" stores the fiscal year, the item "Accounting slip number" stores the number of the accounting slip, and the item "Billing line number" The item number (number assigned to each item when commodities of a plurality of items are purchased with one accounting slip) is stored.
The item “sales organization” stores information indicating the department in the invoicing company that sold the item of the item, and the item “distribution channel” stores information indicating the route through which the item of item is distributed in the market. In the item “product department”, information indicating the department in the billing company that manufactured the item of the item is stored.

The item “payer” stores information on the payer who pays for the accounting slip, and the item “payment conditions” stores the conditions for paying the price (for example, whether to pay in cash or bills). The item “billing destination” stores information on the billing destination to be charged, and the item “billing date” stores the date when the accounting slip is billed.
The item “item” stores the item of the item purchased in the item, and the item “net value (slip currency)” stores the price excluding the tax amount required to purchase the item item. The “tax amount (slip currency)” stores a tax amount related to the price required to purchase the product of the item in the specification, and the item “currency” stores the slip currency of the specification.

  The parent-child master database 12 stores the closing date of each period (from the valid start date to the valid end date) for each set of payer and billing party, an example of which is shown in FIG. In the example illustrated in FIG. 7, the closing dates of the period “2004/01/01 to 2004/12/31” in the billing destination “α customer A branch” of the payer “α customer head office” are “5, 15, 25”. Is. However, multiple deadlines can be set.

  The billing details table storage unit 13 stores information on billing details (billing details data) to be bundled by the monthly numbering process and the total numbering process, an example of which is shown in FIG. FIG. 8 is a diagram showing an example of the contents stored in the billing details table storage unit 13. The items of the billing details table stored in the billing details table storage unit 13 shown in FIG. 8 include “company”, “fiscal year”, “accounting slip number”, “billing details number”, “payer”, “payment conditions”. ”,“ Billing address ”,“ Item ”,“ Net value (slip currency) ”,“ Tax amount (slip currency) ”,“ Currency ”,“ Monthly billing number unit item ”,“ Total bill number unit item ” , “Conclusion date”, “Monthly invoice number”, and “Total invoice number”.

  Billing details table items "Company", "Fiscal year", "Accounting slip number", "Billing detail number", "Payer", "Payment terms", "Billing party", "Item", "Net value (slip “Currency)”, “Tax amount (slip currency)”, and “Currency”, respectively, the company, fiscal year, accounting slip number, billing of the slip data that is the basis of the billing detail data stored in the slip table storage unit 11 The item number, payer, payment condition, billing destination, item, net amount (slip currency), tax amount (slip currency), and currency are stored.

  The item “monthly billing numbering unit item” stores a combination of the sales organization, distribution channel, and product department of the slip data that is the basis of the billing details data. The item “total billing number unit item” stores the sales organization of the slip data that is the basis of the billing details data. The item “closing date” stores the closing date extracted from the parent-child master database 12 using the payer, billing destination, and billing date of the billing details data. The item “monthly invoice number” stores a monthly invoice number assigned to the billing detail data by the monthly numbering process. The item “total invoice number” stores the total invoice number assigned and assigned to the billing detail data by the total numbering process.

  The deposit details table storage unit 14 stores information on deposits (payment details data) transferred by the payer, an example of which is shown in FIG. FIG. 9 is a diagram showing an example of the contents stored in the deposit table storage unit 14. Items of the deposit table stored in the deposit table storage unit 14 shown in FIG. 9 include “deposit notification number”, “transfer requester name”, “payment amount”, “currency”, and “applied flag”.

  The item “payment notification number” stores a number (payment notification number) assigned to the deposit. In the item “transfer requester name”, the name of the transfer requester who requested the deposit (transfer requester name) is stored, and in this embodiment, the transfer requester matches the above payer name as the transfer requester name. Shall be used. In the item “deposit amount”, the deposited amount is stored. The item “currency” stores the type of the deposited currency. The item “applied flag” is a flag for indicating whether or not a claim (billing details data) has been applied to the deposit. If the receivable (billing details data) has not been applied to the deposit, “0” is stored in the item “applied flag”. Further, when the credit (billing details data) is erased for the deposit, “1” is stored in the item “signed off flag”. In addition, as described above, the item “applied flag” is not automatically applied if there is no match with the deposit amount in the payer unit, total invoice unit, or monthly invoice unit. In order to perform the manual application, the operator can specify the receipt details data for which the claims (billing details data) have not been applied to the receipt.

  The billing data processing unit 15 sequentially extracts the slip data stored in the slip table storage unit 11. The billing data processing unit 15 uses the payer, billing destination, and billing date to match the payer and billing destination included in the retrieved slip data stored in the parent / child master database 12 and retrieve the slip The closing date is extracted from the data including the billing date included in the data in the valid period (from the valid start date to the valid end date). Further, the billing data processing unit 15 selects the closing date immediately after the billing date of the retrieved slip data from the retrieved closing dates. In the example of FIG. 7, the closing date immediately after the billing date is 15 days if the billing date is 10 days and 5 days if it is 27 days.

  The billing data processing unit 15 stores the new billing details data in the billing details table in the billing details table storage 13 using the contents of the retrieved slip data and the selected closing date.

Specifically, the billing data processing unit 15 retrieves each of the items “company”, “fiscal year”, “accounting slip number”, and “billing detail number” in the billing detail table in the billing detail table storage unit 13. Stores the company, fiscal year, accounting slip number, and billing item number of the slip data. Further, the billing data processing unit 15 stores the payer, the payment condition, and the billing destination of the extracted slip data in each of the items “payer”, “payment condition”, and “billing destination” of the billing details table. . Further, the billing data processing unit 15 stores the items of the slip data extracted in each of the items “item”, “net amount (slip currency)”, “tax amount (slip currency)”, and “currency” of the billing details table. Stores the net amount (slip currency), tax amount (slip currency), and currency.
Further, the billing data processing unit 15 links the sales organization, distribution channel, and product department of the extracted slip data, and stores information linked to the item “monthly billing number unit item” in the billing details table. For example, if the sales organization is “A1”, the distribution channel is “B1”, and the manufacturing department is “C1”, the billing data processing unit 15 is linked to the item “monthly billing numbering unit item” in the billing details table. Information “A1B1C1” is stored.
Further, the billing data processing unit 15 stores the sales organization of the extracted slip data in the item “total billing number unit item” of the billing details table.
Further, the billing data processing unit 15 stores the selected closing date extracted from the parent-child master database 12 in the item “closing date” of the billing specification table.
The monthly invoice number and the total invoice number of the billing details data stored in the billing details table in the billing details table storage unit 13 after processing by the billing data processing unit 15 are respectively “-(blank)”. It is.

  Based on the “monthly summary unit”, the monthly invoice number numbering processing unit 16 uses the same “monthly summary unit” for each billing detail data stored in the billing details table in the billing details table storage unit 13. Grouped into billing details data with That is, the monthly invoice number numbering processing unit 16 converts each billing detail data stored in the billing detail table into the company, the closing date, the payer, the payment terms, the billing destination, the currency, and the monthly bill numbering. Each unit item is grouped into the same billing details data.

  The monthly invoice number numbering processing unit 16 assigns a monthly invoice number (the same number to each invoice data having the same “monthly summary unit”) to each group that has been grouped. , By checking this number, it is possible to grasp the billing details data grouped based on the “Monthly Summary Unit”). As a method of numbering monthly invoice numbers, for example, the monthly invoice number that was assigned immediately before is stored in a storage unit (not shown), and the stored monthly invoice number is counted by one. The increased value is used as the current monthly invoice number, and the monthly invoice number stored in the storage unit (not shown) is updated to the value after counting up.

  The monthly invoice number assignment processing unit 16 converts the monthly invoice number of each invoice detail data stored in the invoice details table into the monthly invoice number assigned to the group including the invoice details data. , Update the billing details data. The total invoice number of the invoice details data stored in the invoice details table in the billing details table storage unit 13 after processing by the monthly invoice number numbering processing unit 16 is “-(blank)”. .

  Based on the “total summary unit”, the total invoice numbering processing unit 17 charges each bill detail data stored in the bill detail table in the bill detail table storage unit 13 with the same “total summary unit”. Group into detailed data. That is, the total invoice number numbering processing unit 17 converts each billing detail data stored in the billing detail table into billing detail data having the same closing date, payer, currency, and total billing number unit item. Group.

  The total invoice number numbering processing unit 17 assigns a total invoice number to each group that has been grouped (the same number is assigned to each billing detail data having the same “total summary unit”). Number of the billing details data collected in a batch based on the “total summarization unit”. As a method of numbering the total invoice number, for example, the total invoice number numbered immediately before is stored in a storage unit (not shown), and the stored total invoice number is counted up by one. Is the current total invoice number, and the total invoice number stored in the storage unit (not shown) is updated to the value after counting up.

  The total invoice number numbering processing unit 17 converts the total invoice number of each billing item data stored in the billing item table into a total invoice numbered in the group including the billing item data, Update line item data.

  When receiving the deposit information including at least the name of the transfer requester, the deposit amount and the type of currency from the bank terminal via the network (not shown), the deposit details registration unit 18 gives a deposit notification number to the deposit information, and receives the deposit details table. The deposit notification number assigned to the item “deposit notification number” in the deposit detail table in the storage unit 14 is stored, and the received “payment request name”, “deposit amount”, and “currency” are respectively stored in the received deposit information. Stores the name of the transfer client, deposit amount, and currency type included. It should be noted that the application completion flag of the receipt details data stored in the receipt details table in the receipt details table storage 14 after processing by the receipt details registration unit 18 is “0 (unapplied)”.

The payer application processing unit 19 sequentially extracts the payment details data stored in the payment details table in the payment details table storage unit 14, and the applied flag of the extracted payment details data is “0 (unapplied). Is determined.
The payer application processing unit 19 uses the payer and the currency to make a transfer request for the received payment details data when the application completed flag of the extracted payment details data is “0 (unapplied)”. The billing statement table in the billing statement table storage unit 13 is searched for billing statement data in which the payer and the currency match the person name (payer) and the currency.
The payer application processing unit 19 calculates the billing amount of the billing item data by adding the net amount (slip currency) and tax amount (slip currency) for each billing item data for all the billing item data found by searching. To do. The payer application processing unit 19 adds up the amounts calculated for each billing detail data found by searching to obtain a total amount.

The payer application processing unit 19 compares the deposit amount of the deposit details data as a target with the calculated total amount.
If the two match as a result of the comparison, the payer application processing unit 19 erases all the billing details data that matches the transfer requester name (payer) and the currency of the target receipt details data. Determine the billing details data to be included. Then, the payer application processing unit 19 stores the net amount (slip currency) for all the billing details data determined to be erased, stored in the billing details table in the billing details table storage unit 13. Each of the tax amount (slip currency) is set to “0” and the receivable (billing details data) is deleted. Further, the payer application processing unit 19 sets “1 (applied)” to the application completion flag of the payment details data that is stored in the payment details table in the payment details table storage unit 14. Update to
If the result of the comparison indicates that the two do not match, the payer application processing unit 19 sets the target receipt details data (the retrieved receipt details data, and the cleared flag is “0 (unapplied) ) ”Is output to the total invoice application processing unit 20.

The total invoice application processing unit 20 uses the payer and the currency, the payment requester name (payer) and the currency of the payment details data input from the payer application processing unit 19, the payer and The billing statement data in the billing statement table storage unit 13 is found by searching for the billing statement data that matches the currency.
The total invoice clearing processing unit 20 adds up the net amount (slip currency) and the tax amount (slip currency) of the billing item data for each billing item data found by the search to obtain the billing amount of the billing item data. . Then, the total invoice application processing unit 20 adds the invoice amount of each invoice detail data having the same total invoice number for each total invoice number, and totals the total invoice for the total invoice number. Ask for the book amount.

The total invoice application processing unit 20 compares the total invoice amount of each total invoice with the payment amount of the payment details data input from the payer application processing unit 19. If there is a total invoice in which the total invoice amount matches the receipt amount of the receipt item data, the invoice item data having the total invoice number of the total invoice is determined as the billing item data to be cleared. Then, the total invoice clearing processing unit 20 calculates the net amount (slip currency) for all billing details data determined to be erased stored in the billing details table in the billing details table storage unit 13. ) And tax amount (slip currency) are set to “0”, and the receivable (billing details data) is deleted. However, if there are a plurality of total invoices whose total invoice amount matches the deposit amount of the receipt details data, the smaller total invoice number is determined as the total invoice to be erased. Further, the total invoice application processing unit 20 sets the application flag of the payment details data stored in the payment details table in the payment details table storage unit 14 to “1 (applied)”. Update to
If there is no total invoice whose total invoice amount matches the deposit amount of the receipt details data as a result of the comparison, the total invoice application processing portion 20 receives the receipt details data inputted from the payer application processing portion 19. The data is output to the monthly bill application processing unit 21.

The monthly invoice application processing unit 21 uses the payer and the currency to pay the transfer requester name (payer) and the currency of the payment details data input from the total invoice application processing unit 20. The billing statement data in the billing statement table storage unit 13 is found by searching for the billing statement data having the same person and currency.
The monthly invoice application processing unit 21 adds the net amount (slip currency) and the tax amount (slip currency) of the billing item data to the billing amount of the billing item data for each of the billing item data found by searching. Ask. Then, the monthly invoice application processing unit 21 adds the invoice amount of each invoice detail data having the same monthly invoice number for each monthly invoice number, and calculates the monthly invoice number. Find the monthly invoice amount for the invoice.

  The monthly invoice application processing unit 21 compares the monthly invoice amount of each monthly invoice with the receipt amount of the receipt details data input from the total invoice application processing unit 20. If there is a monthly invoice whose monthly invoice amount matches the receipt amount in the receipt line data, the billing line data with the monthly invoice number of that monthly invoice is determined as the billing line data to be cleared . Then, the monthly bill cancellation processing unit 21 calculates the net amount (slip) for all the billing details data determined to be erased, stored in the billing details table in the billing details table storage 13. Each of the currency) and the tax amount (slip currency) is set to “0”, and the credit (billing details data) is deleted. However, if there are a plurality of monthly invoices whose monthly invoice amounts match the deposit amount of the receipt details data, the smaller monthly invoice number is determined as the monthly invoice to be erased. Further, the monthly invoice application processing unit 21 sets “1 (applied already completed) in the receipt details data of the target receipt details data stored in the receipt details table in the receipt details table storage unit 14. ) ".

Hereinafter, the billing data registration process performed by the claim clearing apparatus 1 whose function has been described with reference to FIGS. 5 to 9 will be described with reference to FIG. FIG. 10 is a flowchart showing the flow of the billing details data registration process executed by the claim clearing apparatus 1.
First, the billing data processing unit 15 pays attention to the first record of the slip table in the slip table storage unit 11 (step S101).

  The billing data processing unit 15 determines whether or not slip data is stored in the record of interest (step S102). If it is determined that the slip data is stored in the record of interest (S102: YES), the process proceeds to step S103. On the other hand, if it is determined that the slip data is not stored in the record of interest (S102: NO), the billing details data is created for all the slip data stored in the slip table, The process of FIG. 10 is terminated.

  The billing data processing unit 15 uses the payer, billing destination, and billing date of the slip data to store the payer and billing destination included in the slip data of the record of interest stored in the parent-child master database 12. From the data that includes the billing date included in the slip data of the record of interest that is in the valid period (from the valid start date to the valid end date) The closing date immediately after the billing date of the slip data of the record being selected is selected (step S103).

Subsequently, the billing data processing unit 15 stores the new billing details data in the billing details table in the billing details table storage unit 13 using the contents of the slip data of the record of interest and the selected closing date. (Step S104), the process proceeds to Step S105. The billing data processing unit 15 pays attention to the next record in the slip table in the slip table storage unit 11 (step S105), and returns to the processing of step S102.
Through the above processing, billing details data for each of the slip data in the slip table in the slip table storage unit 11 is created, and the created billing details data is stored in the billing details table in the billing details table 13.

  Furthermore, the monthly numbering process and the total numbering process performed by the claim clearing apparatus 1 whose functions are described with reference to FIGS. 5 to 9 will be described with reference to FIG. FIG. 11 is a flowchart showing the flow of the monthly numbering process and the total numbering process executed by the bond clearing apparatus 1.

  Based on the “monthly summary unit”, the monthly invoice number numbering processing unit 16 uses the same “monthly summary unit” for each billing detail data stored in the billing details table in the billing details table storage unit 13. It is grouped into billing details data with (Company, Closing Date, Payer, Payment Terms, Billing Party, Currency, Monthly Billing Number Unit Item), and a monthly invoice number is assigned to each grouped group. Numbering is performed (step S201).

  For example, a monthly grouping table for storing a company, a closing date, a payer, a payment condition, a billing destination, a currency, a monthly billing number unit item, and a monthly bill number is prepared. The monthly invoice number numbering processing unit 16 sequentially refers to the records in the billing details table, and the company, the closing date, the payer, the payment terms, the billing destination, the billing details data stored in the referenced record, Searches whether the combination of the currency and monthly billing unit items already exists in the monthly grouping table. Only when there is not, a new monthly invoice number is assigned and the company of the target billing details data , Closing date, payer, payment condition, billing destination, currency, monthly bill numbering unit item, and numbered monthly bill number are newly stored in the monthly grouping table.

  The monthly invoice number numbering processing unit 16 includes, in step S201, the monthly invoice number of each invoice data stored in the invoice details table in the invoice details table storage unit 13 including the invoice data. The monthly invoice number assigned to is stored (step S202).

For example, the monthly invoice number numbering processing unit 16 sequentially pays attention to the records of the billing details table in the billing details table storage unit 13, searches the above-mentioned monthly grouping table, and selects the record of interest. Find data with company, closing date, payer, payment terms, billing party, currency, and monthly billing unit fields in the stored billing line data, and retrieve the monthly invoice number from the found data . Then, the monthly invoice number numbering processing unit 16 stores the monthly invoice number extracted from the monthly assembling table in the monthly invoice number of the invoice detail data of the record of interest.
The above steps S201 and S202 are processing steps relating to the monthly numbering process.

  Based on the “total summary unit”, the total invoice number numbering processing unit 17 converts each bill detail data stored in the bill detail table in the bill detail table storage unit 13 to the same “total summary unit” (closing date). , Payer, currency, total invoice numbering unit items), and the total invoice number is assigned to each group that has been grouped (step S203).

  For example, a total grouping table for storing a closing date, a payer, a currency, a total bill numbering unit item, and a total bill number is prepared. The total invoice number numbering processing unit 17 sequentially refers to the records of the billing details table, and the due date, payer, currency, and total billing unit field of the billing details data stored in the referenced record If there is no such group already in the total grouping table, and only if there is not, a new total invoice number is assigned, and the due date, payer, currency, and total invoice number of the target invoice line data The unit item and the total invoice number assigned are newly stored in the total grouping table.

  The total invoice number numbering processing unit 17 calculates the total invoice number of each billing specification data stored in the billing specification table in the billing specification table storage unit 13 for the set including the billing specification data in step S203. The billing details data is updated to the total bill number assigned in step S204.

For example, the total invoice number numbering processing unit 17 sequentially looks at the records of the billing details table in the billing details table storage unit 13, searches the above total grouping table, and stores them in the record of interest. The data having the due date, the payer, the currency, and the total bill numbering unit items of the billing details data is found, and the total bill number is extracted from the found data. Then, the total invoice number numbering processing unit 17 sets the total invoice number of the invoice detail data of the record of interest to the total invoice number extracted from the total assembling table, and updates the invoice detail data.
The above steps S203 and S204 are processing steps relating to the total numbering process.
When actually billing, the billing details data stored in the billing details table in the billing details table storage unit 13 is used, and the billing details data having the same monthly invoice number are batched. To make a monthly bill. Further, each billing detail data stored in the billing details table in the billing details table storage unit 13 is used, and billing details data having the same total bill number are collectively billed as a total bill.

Hereinafter, the registration process of the deposit details data performed by the claim clearing apparatus 1 whose function has been described with reference to FIGS. 5 to 9 will be described with reference to FIG. FIG. 12 is a flowchart showing a flow of a registration process for deposit details data executed by the claim clearing apparatus 1.
First, the payment details registration unit 18 determines whether or not payment information has been received from a terminal such as a bank via a network (not shown) (step S301). If no deposit information has been received (S301: NO), the process returns to step S301 and waits for receipt of deposit information. On the other hand, if the deposit information is received (S301: YES), the process proceeds to step S302.

  The receipt description registration unit 18 assigns a receipt notification number to the received receipt information, stores the receipt notification number assigned to the item “deposit receipt number” in the receipt details table in the receipt details table storage unit 14, and stores the item “ In the “transfer requester name”, “deposit amount”, and “currency”, the transfer requester name, deposit amount, and currency type included in the received deposit information are stored (step S302). It should be noted that the application completion flag of the receipt details data stored in the receipt details table in the receipt details table storage 14 after processing by the receipt details registration unit 18 is “0 (unapplied)”.

Hereinafter, the collective bond clearing process performed by the claim clearing apparatus 1 whose function has been described with reference to FIGS. 5 to 9 will be described with reference to FIG. FIG. 13 is a flowchart showing the flow of the collective bond clearing process executed by the bond clearing apparatus 1.
The payer application processing unit 19 pays attention to the first record of the payment details table in the payment details table storage unit 14 (step S401), and proceeds to the processing of step S402.

  The payer application processing unit 19 determines whether or not the deposit details data is stored in the record of interest (step S402). If it is determined that the deposit details data is stored in the record of interest (S402: YES), the process proceeds to step S403. On the other hand, if it is determined that the deposit details data is not stored in the record of interest (S402: NO), all the deposit details data stored in the deposit details table are processed in the collective bond cancellation process of FIG. The process of FIG. 13 is terminated.

  The payer application processing unit 19 determines whether the receipt details data stored in the record of interest is receipt details data for which the receivable (billing details data) corresponding to the receipt details data has not yet been applied. Is determined by the completed flag (step S403). If the applied flag is “0 (unapplied)”, it is determined that the corresponding claim (billing details data) has not been cleared (S403: YES), step S404. Proceed to the process. On the other hand, if the application completed flag is “1 (application completed)”, it is determined that the corresponding account (billing details data) has already been applied (step S403: NO). The process proceeds to S413.

The payer application processing unit 19 uses the payer and the currency, the payer name and the currency, the payer and the currency, and the transfer requester name (payer) of the payment details data stored in the record of interest. The billing statement data in the billing statement table storage unit 13 is found by searching for the billing statement data with the same.
The payer application processing unit 19 calculates the billing amount of the billing item data by adding the net amount (slip currency) and tax amount (slip currency) for each billing item data for all the billing item data found by searching. To do. The payer application processing unit 19 adds up the calculated billing amount (net amount (slip currency) + tax amount (slip currency)) of each billing detail data found by searching to obtain a total amount (step S404).

  The payer application processing unit 19 compares the deposit amount of the deposit detail data stored in the record of interest with the total amount obtained in step S404, and determines whether or not both match ( Step S405). If it is determined that they match (S405: YES), the process proceeds to step S406. On the other hand, if they do not match (S405: NO), the process proceeds to step S407.

  The payer application processing unit 19 converts all the billing details data that matches the transfer requester name (payer) and currency of the receipt details data stored in the record of interest into the billing details data to be erased. decide. Then, the payer application processing unit 19 stores the net amount (slip currency) for all the billing details data determined to be erased, stored in the billing details table in the billing details table storage unit 13. Each of the tax amount (slip currency) is set to “0” and the receivable (billing details data) is deleted. Further, the payer application processing unit 19 sets the application flag of the receipt details data stored in the record of interest in the receipt details table in the receipt details table storage unit 14 to “1 (applied)”. (Step S406). Then, the process proceeds to step S413.

The total invoice application processing unit 20 uses the payer and the currency, the payer and the currency to the transfer requester name (payer) and the currency of the receipt details data stored in the record of interest. The billing statement data in the billing statement table storage unit 13 is found by searching for the billing statement data that matches the.
The total invoice clearing processing unit 20 adds up the net amount (slip currency) and the tax amount (slip currency) of the billing item data for each billing item data found by the search to obtain the billing amount of the billing item data. . Then, the total invoice application processing unit 20 adds the invoice amount of each invoice detail data having the same total invoice number for each total invoice number, and totals the total invoice for the total invoice number. A book amount is obtained (step S407).

For example, a total invoice amount table for storing the total invoice number and the total invoice amount is prepared.
The total invoice clearing processing unit 20 sequentially refers to the records in the billing details table, and the payer and the currency of the billing details data stored in the referenced record are the transfer requester name (payment of the receipt details data). If it matches the person and currency, the billing amount of billing statement data is calculated by adding the net amount (slip currency) and tax amount (slip currency) of the billing statement data.
The total invoice application processing unit 20 searches the total invoice amount table for the total invoice number stored in the referenced record, and if there is, the total invoice number. Is added to the total invoice amount corresponding to. If not, the total invoice number of the invoice detail data stored in the record referenced in the total invoice amount table and the invoice amount calculated by the invoice detail data are newly added.

  The total invoice application processing unit 20 compares the total invoice amount of each total invoice with the receipt amount of the receipt details data stored in the record of interest, and is stored in the record of interest. It is determined whether or not there is a total invoice whose total invoice amount matches the deposit amount of the receipt details data (step S408). If there is a matching total bill (S408: YES), the process proceeds to step S409. On the other hand, if there is no matching total bill (S408: NO), the process proceeds to step S410.

  The total invoice application processing unit 20 erases the invoice line data having the total invoice number of the total invoice whose total invoice amount matches the receipt amount of the receipt line data stored in the record of interest. Determine the target billing item data. Then, the total invoice clearing processing unit 20 calculates the net amount (slip currency) for all billing details data determined to be erased stored in the billing details table in the billing details table storage unit 13. ) And tax amount (slip currency) are set to “0”, and the receivable (billing details data) is deleted. However, if there are a plurality of total invoices whose total invoice amount matches the deposit amount of the receipt details data, the smaller total invoice number is determined as the total invoice to be erased. Further, the total invoice application processing unit 20 sets the application flag of the payment details data stored in the payment details table in the payment details table storage unit 14 to “1 (applied)”. (Step S409). Then, the process proceeds to step S413.

The monthly invoice application processing unit 21 uses the payer and the currency, the payer name and the currency of the payment details data stored in the record of interest, the payer and The billing statement data in the billing statement table storage unit 13 is found by searching for the billing statement data that matches the currency.
The monthly invoice application processing unit 21 adds the net amount (slip currency) and the tax amount (slip currency) of the billing item data to the billing amount of the billing item data for each of the billing item data found by searching. Ask. Then, the monthly invoice application processing unit 21 adds the invoice amount of each invoice detail data having the same monthly invoice number for each monthly invoice number, and calculates the monthly invoice number. A monthly invoice amount of the invoice is obtained (step S410).

For example, a monthly invoice amount table for storing a monthly invoice number and a monthly invoice amount is prepared.
The monthly invoice application processing unit 21 sequentially refers to the records of the billing details table, and the payer and currency of the billing details data stored in the referenced record are the transfer requester name ( If it matches the payer) and the currency, the billing amount of the billing item data is calculated by adding the net amount (slip currency) and the tax amount (slip currency) of the billing item data.
The monthly invoice application processing unit 21 searches the monthly invoice amount table for the monthly invoice number of the invoice detail data stored in the referenced record, and if there is, The billing amount calculated by the billing details data is added to the monthly bill amount corresponding to the next bill number. If not, the monthly invoice number of the billing details data stored in the record referenced in the monthly billing amount table and the billing amount calculated by the billing details data are newly added.

  The monthly invoice application processing unit 21 compares the monthly invoice amount of each monthly invoice with the receipt amount of the receipt details data stored in the record of interest, and the record of interest It is determined whether or not there is a monthly invoice whose monthly invoice amount matches the amount of money in the receipt details data stored in (Step S411). If there is a matching monthly bill (S411: YES), the process proceeds to step S412. On the other hand, if there is no matching monthly bill (S411: NO), the process proceeds to step S413.

  The monthly invoice application processing unit 21 has the monthly invoice number of the monthly invoice whose monthly invoice amount matches the incoming amount of the receipt details data stored in the record of interest. The data is determined as the billing item data to be cleared. Then, the monthly bill cancellation processing unit 21 calculates the net amount (slip) for all the billing details data determined to be erased, stored in the billing details table in the billing details table storage 13. Each of the currency) and the tax amount (slip currency) is set to “0”, and the credit (billing details data) is deleted. However, if there are a plurality of monthly invoices whose monthly invoice amounts match the deposit amount of the receipt details data, the smaller monthly invoice number is determined as the monthly invoice to be erased. Further, the monthly invoice application processing unit 21 sets “1 (applied already completed) in the receipt details data of the target receipt details data stored in the receipt details table in the receipt details table storage unit 14. ”” (Step S412). Then, the process proceeds to step S413.

  The payer application processing unit 19 pays attention to the next record in the payment details table in the payment details table storage unit 14 (step S413), and proceeds to the processing of step S402.

  As explained above, according to the present embodiment, the billing data having the same “total summary unit” is assigned with a total invoice number, and the billing detail data having the same “monthly summary unit”. A monthly invoice number is assigned and assigned. And when clearing a claim (invoice item data) for the receipt, the sum of the invoice amount of each invoice item data with the same total invoice number (the total invoice number of the total invoice number) If the total invoice amount) matches the deposit amount, the billing details data of the total invoice number is determined as the object of application. Also, if the sum of the invoice amount of each invoice data with the same monthly invoice number (the monthly invoice amount of the monthly invoice with that monthly invoice number) matches the receipt amount, The billing item data of the next invoice number is determined as the object to be cleared. Therefore, when there is a deposit for a total invoice created from the bill detail data having the same “total summarization unit”, it is possible to perform a batch clearing of a claim (billing detail data) for the deposit. In addition, when there is a receipt for a monthly invoice created from the billing details data with the same “Monthly Summary Unit”, it is possible to perform a batch reversal of claims (billing details data) for the receipt. Become.

The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and various design changes can be made as long as they are described in the claims.
For example, in the above embodiment, both the monthly numbering process and the total numbering process are always executed, but only the monthly numbering process is executed, only the total numbering process is executed, and the monthly numbering is performed. The execution of both the processing and the total numbering processing may be made selectable by the operator of the billing source, and only the processing selected by the operator may be executed.
Furthermore, the item “Monthly Summary Unit” may be a combination of items other than the above-described embodiment, and the item “Total Summary Unit” may be a combination of items other than the above-described embodiment. Needless to say.

  A program for realizing the functions of each processing unit described above is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed to perform the above-described various processes. Also good. The “computer system” here includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system provided with a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built in the computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

The figure for demonstrating the outline | summary of the monthly numbering process and total numbering process of this invention. The figure for demonstrating the outline | summary of the monthly numbering process and total numbering process of this invention. The figure for demonstrating the outline | summary of the monthly numbering process and total numbering process of this invention. The figure for demonstrating the outline | summary of the lump sum cancellation process of this invention. The functional block diagram which shows the function of the claim cancellation apparatus in embodiment of this invention. The figure which shows an example of the slip table memory | storage part of FIG. The figure which shows an example of the parent-child master database of FIG. The figure which shows an example of the claim details table memory | storage part of FIG. The figure which shows an example of the payment details table memory | storage part of FIG. The flowchart which shows the flow of the registration process of the billing details data which the bond cancellation apparatus of FIG. 5 performs. The flowchart which shows the flow of the monthly numbering process and the total numbering process which the loan application apparatus of FIG. 5 performs. The flowchart which shows the flow of the registration process of the payment details data which the bond application apparatus of FIG. 5 performs. The flowchart which shows the flow of the collective bond cancellation process which the bond cancellation apparatus of FIG. 5 performs.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Claim clearing apparatus 11 Slip table memory | storage part 12 Parent-child master database 13 Billing details table memory | storage part 14 Payment details table memory | storage part 15 Billing data processing part 16 Monthly invoice number numbering processing part 17 Total invoice number numbering processing part 18 Payment Details Registration Unit 19 Payer Application Processing Unit 20 Total Invoice Application Processing Unit 21 Monthly Invoice Application Processing Unit

Claims (6)

Detailed data storage means for storing a plurality of detailed data having a plurality of items;
A set of detailed data in which a part of the plurality of items of the detail data is a summary unit for enclosing the detail data, and each detail data stored in the detail data storage means is the same as the partial item of the summary unit. And a grouping means for assigning a summary line number assigned to a set including the detail data to each detail data, and assigning a summary line number to each detail data,
When receivables are cleared, for each summary item number, the amount charged for the item data with the same summary item number stored in the item data storage means is summed to determine whether it matches the deposit amount. A receivables application processing means for performing the application of receivables with all the detailed data with a summary item number that matches the amount as the object of application;
A claim clearing apparatus characterized by comprising: Detailed data storage means for storing a plurality of detailed data having a plurality of items;
A part of a plurality of items of the detail data is defined as a first summary unit for summarizing the detail data, and each of the detail data stored in the detail data storage means is the same as the partial item of the first summary unit. The first specification is divided into sets of detail data, each of which is assigned one first summary specification number, and each detail data is assigned the first summary specification number assigned to the set including the detail data. A means of binding;
Further, some of the items that are the first summary unit are set as second summary units, and each of the detailed data stored in the detailed data storage means is the part of the second summary unit. The items are divided into sets of the same detail data, and each group is assigned one second summary detail number, and each detail data is assigned the second summary detail number assigned to the set including the detail data. A second detailing means for:
Whether the total amount charged for the detailed data to which the same second summary item number stored in the detail data storage means is added and matched with the deposit amount for each second summary item number at the time of application of the bond A first receivable application processing means for determining and recognizing the receivable for all the detailed data assigned with the second summary item number that matches the deposit amount;
For each first summary item number, it is determined whether the amount charged for the item data with the same first summary item number stored in the detail data storage means matches the deposit amount. A second receivable application processing means for applying the receivable as the application object for all the detailed data to which the matching first summary item number is assigned;
A claim clearing apparatus characterized by comprising: A part of a plurality of items in the detail data is a summary unit for summarizing the detail data, and a plurality of detail data stored in the detail data storage means are grouped into the same detail data in which the some items in the summary unit are the same. A grouping procedure for assigning one summary line number to each group and assigning each summary data the summary line number assigned to the set including the detail data;
When receivables are cleared, for each summary item number, the amount charged for the item data with the same summary item number stored in the item data storage means is summed to determine whether it matches the deposit amount. Receivables application processing procedure for applying the receivables with all the item data with the summary item number matching the amount as the object of application,
A method for clearing claims. A part of the plurality of items of the detail data is defined as a first summary unit for summarizing the detail data, and each detail data stored in the detail data storage means is the same as the one item of the first summary unit. Dividing into data sets, assigning a first summary detail number to each set, and assigning the first summary detail number assigned to each detail data to the set including the detail data Procedure and
Further, some of the items that are the first summary unit are set as second summary units, and each of the detailed data stored in the detailed data storage means is the part of the second summary unit. The items are divided into sets of the same detail data, and each group is assigned one second summary detail number, and each detail data is assigned the second summary detail number assigned to the set including the detail data. A second detailing procedure to:
Whether the total amount charged for the detailed data to which the same second summary item number stored in the detail data storage means is added and matched with the deposit amount for each second summary item number at the time of application of the bond A first receivable application processing procedure for determining and reversing the receivable for all the detailed data assigned with the second summary line number that matches the deposit amount,
For each first summary item number, it is determined whether the amount charged for the item data with the same first summary item number stored in the detail data storage means matches the deposit amount. A second receivables application processing procedure for applying the receivables with all the detailed data assigned with the matching first summary line number as the object of application;
A method for clearing a claim characterized by comprising: On the computer,
A part of a plurality of items in the detail data is a summary unit for summarizing the detail data, and a plurality of detail data stored in the detail data storage means are grouped into the same detail data in which the some items in the summary unit are the same. A grouping procedure for assigning one summary line number to each group and assigning each summary data the summary line number assigned to the set including the detail data;
When receivables are cleared, for each summary item number, the amount charged for the item data with the same summary item number stored in the item data storage means is summed to determine whether it matches the deposit amount. Receivables application processing procedure for applying the receivables with all the item data with the summary item number matching the amount as the object of application,
Receivable clearing program characterized by having On the computer,
A part of the plurality of items of the detail data is defined as a first summary unit for summarizing the detail data, and each detail data stored in the detail data storage means is the same as the one item of the first summary unit. Dividing into data sets, assigning a first summary detail number to each set, and assigning the first summary detail number assigned to each detail data to the set including the detail data Procedure and
Further, some of the items that are the first summary unit are set as second summary units, and each of the detailed data stored in the detailed data storage means is the part of the second summary unit. The items are divided into sets of the same detail data, and each group is assigned one second summary detail number, and each detail data is assigned the second summary detail number assigned to the set including the detail data. A second detailing procedure to:
Whether the total amount charged for the detailed data to which the same second summary item number stored in the detail data storage means is added and matched with the deposit amount for each second summary item number at the time of application of the bond A first receivable application processing procedure for determining and reversing the receivable for all the detailed data assigned with the second summary line number that matches the deposit amount,
For each first summary item number, it is determined whether the amount charged for the item data with the same first summary item number stored in the detail data storage means matches the deposit amount. A second receivables application processing procedure for applying the receivables with all the detailed data assigned with the matching first summary line number as the object of application;
Receivable clearing program characterized by having

Images