JP2000268119A - System and method for credit erasure processing - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently perform the collation processing of a transferred money amount and a amount claimed even in the case that the transferred money amount and the billed money amount do not match. SOLUTION: The transferred money amount included in the transfer data of one item of a client and the total amount claimed of the unpaid ones (credit data) of billing data generated for respective details to the client are collated (S103), and when they do not match, collation is performed by an unpaid bill unit to the client (S105). In non-matching, when there are the prescribed number or less of unpaid bills, collation with the total amount claimed for which plural bills are combined is performed (S108) and the collation with the total amount claimed for which the plural details included in one bill are combined is performed (S111) at the time of non-matching. When there are more than the prescribed number of the unpaid bills, the credit data to the client are sectioned by a mouth unit, the collation with the cumulative amount claimed of the month is performed (S114) and the collation is performed by the month unit at the time of non-matching (S116). In matching, the pertinent credit data are erased.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a receivable clearing system and, more particularly, to a method for efficiently matching a transfer amount and a bill amount from a customer notified by a financial institution such as a bank.

[0002]

2. Description of the Related Art In a general business transaction, when a company sells a product or provides a service in response to a request (also referred to as an "order") from a customer, the company charges for the order. Issue an invoice to the customer. The customer transfers the billed amount described in the bill to a designated financial institution, for example, a designated bank account by a designated payment date. Upon receipt of the transfer notice from the bank, the company that has requested the payment confirms whether or not the customer has made the payment as invoiced and the transfer amount included in the transfer notice and the copy of the issued invoice or the invoice data displayed on the screen. A check is made by going together. Then, the invoice data whose payment has been confirmed are deleted. Generally, unpaid data among invoice data is particularly referred to as receivable data. Conventionally, however, the receivable clearing process of applying the receivable data in the invoice database based on such a transfer notice has been performed manually.

Conventionally, invoices are issued in units of specification items. However, there are few cases in which bills for a plurality of specification items (or simply referred to as “specifications”) are collectively billed as one bill. Absent. The specification is, for example, a unit of an item described in a bill, such as a cost for a failed component or a cost for a component replacement operation in a maintenance management company. Each order also corresponds to each item. If the remittance amount is the same as the invoice amount in one invoice, the matching process is also very simple, but the depositor always transfers the invoice amount at the face value of the invoice, that is, the total amount in the invoice. Not limited to this, you can transfer several months of invoices at once, transfer only the shortfall of payment due to incorrect transfer amount, etc., or transfer only a part of the order amount included in one invoice In some cases, they may be transferred.

[0004]

As described above, the transfer amount does not always match the billed amount,
Conventionally, the transferred amount is matched with the invoice amount in each invoice, and when they do not match, the invoice amount of multiple invoices is tried to accumulate, or several orders in the invoice are I had to do the matching process while trying to add the billing amount. As described above, the burden on the person has been increased due to the complicated receivable clearing process.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to perform a matching process between a transfer amount and a bill amount even when the transfer amount does not match the bill amount in the bill. An object of the present invention is to provide a receivable clearing system and a receivable clearing method that can be performed efficiently.

[0006]

In order to achieve the above-mentioned object, a claim clearing processing system according to the present invention comprises:
Or matching the transfer amount transferred by the customer to the invoice issued to claim the invoice amounts of a plurality of items with the receivable data which is the unpaid billing data of the customer, In the receivable clearing processing system for clearing, a billing database that registers billing data including customer identification information, bill number, billing amount for each statement, and a customer included in the transfer data notified from the financial institution A billing data automatic reconciliation processing means for matching the remittance amount with the receivables data of the customer registered in the requisition database and automatically applying the receivables data. The automatic clearing processing means combines the transfer amount included in one transfer data with the charge amount of one of a plurality of unpaid bills for the customer. Is intended to butted against the total claim amount was determined by cause I.

[0007] The automatic billing data processing means, if the plurality of invoices are matched by the total billing amount and there is no invoice combination that matches the transfer amount, the one payment data And the total invoice amount obtained by combining the transfer amount included in the above with the invoice amount of one of the receivables data or the invoice data of any of the receivables data in the receivable data of a plurality of items included in any one invoice Is to associate with.

[0008] The billing data automatic reconciliation processing means, if the number of unpaid invoices issued to the customer remains in a predetermined number or more, converts the customer's receivable data into a predetermined comparatively. Grouping by large unit, 1
In this case, the transfer amount included in the transfer data of the case is combined with the total charge amount obtained by combining the charge amounts of any of the groups.

[0009] Further, the billing data automatic reconciliation processing means, if the number of unpaid bills issued to the customer remains more than a predetermined number, converts the receivable data of the customer to a predetermined comparatively. Grouping by large unit, 1
The transfer amount included in the transfer data of each case is matched with the amount charged in each group.

According to another aspect of the present invention, there is provided a method for processing a claim for receivables, which includes the transfer amount transferred by a customer to an invoice issued for claiming one or a plurality of specifications and the unpaid billing data of the customer. By matching with certain credit data,
In the receivables clearing system for clearing the relevant receivables data, the transfer amount from the customer included in one transfer data notified by the financial institution and the number of unpaid invoices for the customer The method includes a combined bill attaching step of matching the total bill amount obtained by combining the bill amounts of any of the bills.

If there is no combination of invoices matching the transfer amount as a result of the matching by the plurality of invoices matching step, the transfer amount included in one transfer data and one of the transfer amounts Of the plurality of items of claim data included in the invoice, or a total amount of money obtained by combining the amount of claims of any one of the claims data. .

If the number of unpaid invoices issued to the customer is equal to or greater than a predetermined number, the customer's receivable data is grouped into predetermined relatively large units, and one Transfer amount included in the transfer data of
The method includes a combination group matching step of matching the total charge amount obtained by combining the charge amounts of any of the groups.

If the number of unpaid invoices issued to the customer is equal to or greater than a predetermined number, the customer's receivable data is grouped in a predetermined relatively large unit, and one Transfer amount included in the transfer data of
The method includes a group assigning step of matching a billing amount in each group.

[0014]

Preferred embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is an overall configuration diagram showing an embodiment of a claim clearing processing system according to the present invention. The accounting system 1 of a certain company issues a bill to a customer (customer) 2 according to the provided goods and service contents. Customer 2
The amount of money stated in the bill is transferred to an account of a predetermined financial institution, for example, a designated bank 3. By transmitting the transfer data, the bank 3 notifies the billing company that the customer 2 has received the payment. The accounting system 1 of the company clears the corresponding billing data by matching the transfer amount included in the transfer data with the unpaid billing data by a subsystem called a loan clearing processing system. FIG.
2 shows this process and the flow of data.

In FIG. 1, the accounting system 1 has a transfer data reception processing unit 4, a billing data generation processing unit 5, a billing data automatic clearing processing unit 6, a bill issuing processing unit 7, and a billing data management unit 8. ing. The transfer data reception processing unit 4
The transfer data sent from the bank 3 is received and stored in the transfer data storage unit 9. Billing data generation processing unit 5
Generates billing data in accordance with the occurrence of an order requiring billing and the like, and registers the billing data in the billing database 10. The billing data automatic clearing processing unit 6 matches the transfer amount from the customer 2 included in the transfer data with the unpaid billing data of the customer 3 registered in the billing database 10, that is, the receivable data. By doing so, it executes the receivable clearing process of clearing the receivable data. Invoice issuance processing unit 7
Generates a bill for each customer based on unclaimed billing data registered in the billing database 10. Since the claim clearing process is automatically performed by the billing data automatic clearing unit 6, the billing data management unit 8 checks the contents of the processing, and the billing data automatic clearing unit 6 cannot handle the unusual cases. This is a means for enabling the credit clearing process based on a transfer or the like to be performed manually.

FIG. 2 is a diagram showing an example of data registration in the transfer data storage unit 9 in the present embodiment. Since the transfer data notified from the bank 3 includes the payment date, the transfer amount, the name of the transferee corresponding to the customer name, the bank code, and the like, the transfer data storage unit 9 stores the transfer data reception processing unit 4 The transfer data is provided with an identifiable transfer number and is sequentially stored.

FIG. 3 is a diagram showing an example of a data structure of billing data registered in the billing database 10 in the present embodiment. In the present embodiment, one record of billing data is generated for each order. Each billing data is associated with a customer code, which is identification information of a customer to be billed, a bill number for billing the billed amount of the order, and detailed items such as parts cost and replacement work cost. Item number, expected payment date of the item,
The billing amount and balance of the statement are included as item data. The same value is set for the customer code, the bill number, and the expected payment date of billing data to be billed with the same bill. In the remaining amount, the amount of the invoiced amount that has not been paid is written. Therefore, the billing data with the remaining amount of 0 indicates that payment has been made. In the present embodiment,
Since the billing data is formed for each order, it is possible to easily perform the application for each order.

FIG. 4 is a diagram showing an example of the contents of the customer master 11 in the present embodiment. In the customer master 11, information on a customer who can be a billing destination is registered in advance. As shown in FIG. 4, a transferor name, a customer code, a closing date, a customer name, and an address are set for each customer. Since the name of the transferee is specified in the transfer data notified from the bank 3 as information for specifying the customer, each data is registered in order to correspond to the customer code included in the billing data. I have. The customer name and address are used as information to be printed on the bill.

FIG. 5 is a diagram showing an example of a format of a bill issued in the present embodiment. There is no feature in the bill itself issued in the present embodiment, and it is sufficient that information similar to general information is printed. That is, the date of issuance of the invoice, the destination (customer) and address for specifying the issuance destination, the invoice number, the due date, the amount of the invoice, and the item name and amount of the order to be invoiced in this invoice are printed. Of these, the due date corresponds to the expected payment date of the billing data. The item title is an item of item, and is uniquely associated with the item number specified in the billing data by master data (not shown). The billing amount is the total value of the amounts of the respective subject lines. The bill issuing processor 7 collects unclaimed billing data registered in the billing database 10 for each customer to generate a bill,
A billing database 1 for billing data to be billed
The invoice number to be printed on the invoice is written in the invoice number at 0.

Next, a description will be given of a claim data clearing process performed by the automatic billing data clearing section 6 in the present embodiment with reference to a flowchart shown in FIG.

In the present embodiment, the matching process performed at the time of the reconciliation process includes matching by customer unit, matching by bill unit, matching by combination of bills,
Processing contents of matching by combination of specifications (receivable data), matching by month total and matching by monthly total are provided, and a predetermined matching process is performed stepwise and according to the data amount. And
In particular, in the present embodiment, the billing amount to be matched with the transfer amount included in one transfer data is calculated by summing the billing amounts of a plurality of bills or the billing amount included in one bill. Since the calculation is performed automatically while combining and summing the billing amounts, it is possible to efficiently perform a complicated matching process when the transfer amount is not the same as the billing amount in one invoice according to the manual operation. It can be carried out. The reconciliation process including the characteristic matching process will be described first with respect to the customer-based matching process.

The automatic billing data clearing section 6 reads out the unprocessed transfer data stored in the transfer data storage section 9 (step 101), and obtains the transfer person name specified in the transfer data to the customer master 11. The customer code is converted based on the customer code (step 102). Then, matching based on the credit data for the customer is performed as follows (step 103). First, the unpaid billing data of the customer registered in the billing database 10, that is, the billing amounts of the claim data are totaled. Then, the transfer amount specified in the transfer data being processed is matched with the calculated total amount, and as a result, if they match, the respective claim data constituting the total amount, that is, the receivables to the customer By setting all remaining data to 0, the corresponding billing data is cleared (step 10).
4,113). In this way, by matching the transfer amount with the total invoice amount of the receivable data of the customer 2, it is possible to efficiently perform the clearing process in the case where the customer 2 makes a lump-sum transfer of unpaid payments, for example. Can be done.

It should be noted that if there is no credit data of the customer to be processed, it means that payment has been made even though no claim has been made. Defect information indicating that effect is set, or recorded as a defect transfer data in a separate database.

If the total billing amount does not match the transfer amount, the next step of matching the bill unit is performed (step 105). Here, first, the claim amount of the customer registered in the billing database 10 is calculated for each bill based on the bill number. The billing amount calculated here should be the same as the billing amount printed on each bill. Then, the transfer amount specified in the transfer data being processed and the calculated billing amounts are matched. At this time, referring to the scheduled payment date of each bill, matching is performed in order from the old bill. If there is a matching bill due to this match,
By setting the remaining amount of the billing data constituting the billing amount to 0, the corresponding billing data is cleared (step 10).
6, 113).

Here, if there is no charge amount that matches the transfer amount, the process proceeds to the next matching process. In the present embodiment, different processes are performed according to the number of unpaid bills. . For example, when the number of unpaid invoices is three or less, the process shifts to a matching process by combining invoices (steps 107 and 108).

First, since the billing amount of each bill has been determined in the above processing, three bills are selected from the old bill. Here, the combination of the invoices will be described with reference to FIG. 7. Since the matching process for each invoice has been completed in step 105, the combination of the three invoices is as shown in FIG. There are four ways. Note that there is one combination in the case of two sheets. In the present embodiment, since it is basically to match and erase from the oldest one, matching is performed in the order of the combination shown in FIG. It is not limited. The billing amount associated with the transfer amount in this process is, for example, the total value of the billing amounts of the invoice 1 and the invoice 2 if the order is 2. Therefore, if the transfer amount and the total billing amount of any combination match by matching, the remaining credit data constituting the matching total billing amount is set to 0 to clear the corresponding loan data ( Steps 109 and 113).

If there are many unpaid invoices in the matching process based on the combination of invoices, the number of combinations due to the invoices may become enormous. Although the number of branch points is set to three or less in advance, the number is not limited to this number and may be four or more as a result of considering the system load and the like.

Here, if there is no charge amount equal to the transfer amount, matching is performed by a combination of the credit data (details) constituting the oldest unpaid bill (step 1).
11). However, if the number of statements (number of claim data) making up the invoice is large, for the same reason as in the case of the matching process by combining the invoices, the invoice is excluded from the processing in this case, Next, the old unpaid bill is processed. If any of the unpaid bills includes four or more statements, it is determined that the automatic clearing process could not be performed on the transfer data, and a predetermined process is performed (step 118). Here, the predetermined processing is, for example, to set defect information indicating that to the transfer data in the transfer data storage unit 9 or to record the transfer data in a separate database as the defect transfer data. Thereby, it can be suggested that the clearing process for the transfer data is manually processed through the billing data management unit 8.

First, the oldest bill for the customer is selected by comparing the expected payment dates of each bill. Here, the combination of specifications will be described with reference to FIG. 8. As shown in FIG. 8, there are seven combinations of three specifications. There are three combinations in the case of two specifications. The billing amount associated with the transfer amount in this process is, for example, the total value of the billing amounts of the statement 1 and the statement 2 if the order is 4. Therefore, if the transfer amount and the invoice amount of a single statement or the total invoice amount of any combination of the statements match by matching, the remaining balance of the receivable data constituting the matched invoice amount is set to zero. To clear the corresponding credit data (steps 112 and 11)
3). As described above, according to the present embodiment, it is possible to perform the reconciliation in detail units.

Here, if there is no charge amount that matches the transfer amount, matching is performed using a combination of the credit data (specification) that constitutes the next oldest unpaid bill. If there is no combination that matches the transfer amount in any of the unpaid bills, it is determined that the automatic clearing process cannot be performed on the transfer data, and a predetermined process is performed (step 118). ). The predetermined processing here may be the same as described above.

The order in which the associations are performed is not limited to the order shown in FIG. For example, if the basis is to erase more specifications, the order of performing the matching shown in FIG. 8 is reversed.

On the other hand, in step 107, when there are four or more unpaid bills, it is assumed that there are a lot of credit data, and the amount of the claim data in the credit data is collected in a relatively large unit, for example, a month unit. A matching process is performed (step 114). That is, the customer's credit data in the billing database 10 is divided into groups on a monthly basis, and the total billed amount in each group is determined. Months may be separated according to the calendar,
In the present embodiment, the month is delimited by the closing date set in the customer master 11. Each credit data can be easily grouped by comparing the closing date with the scheduled payment date. Then, as shown in FIG. 9, the oldest month (n months ago) of the total billed amount per month is matched with the transfer amount. If they do not match, the sum of the billing amount of n months ago and (n-1) months ago is matched with the transfer amount. As a result of matching in this order, if there is a billing amount that matches the transfer amount, the remaining balance of the claim data that constitutes the matching billing amount is set to 0 to clear the corresponding claim data. (Steps 115 and 113).

As described above, the number of unpaid bills issued to a certain customer 2 is a predetermined number (here, four).
In the case where there is more than this, the efficiency of the matching process is improved by roughly grouping the credit data by grouping the details (credit data) in units of months that will be equal to or more than the number of details to be claimed in each invoice. I tried to. In addition,
The order of performing the association is not limited to the order shown in FIG. For example, if the basis is to erase more specifications, the order of performing the matching shown in FIG. 9 is reversed.

If any of the combinations shown in FIG. 9 does not match the transfer amount, a monthly matching process is performed (step 116). In this case, similarly to the matching process based on the month-to-date total, the customer's receivable data is divided into groups on a monthly basis, and the sum of the invoice amounts in each group is obtained. Then, as shown in FIG. 10, the billing amount for each month and the transfer amount are compared without accumulating the billing amount in monthly units. As shown in FIG. 10, in the present embodiment, matching is performed sequentially from the oldest month. As a result of matching in this order, if there is a billing amount that matches the transfer amount, the remaining amount of the billing data that constitutes the matching billing amount is set to 0 so that the corresponding billing data is cleared. (Steps 117 and 113).

Here, if none of the billed amounts on a monthly basis match the transfer amount, it is determined that the automatic clearing process could not be performed on the transfer data, and a predetermined process is performed (step 117). , 118). The predetermined processing here may be the same as described above.

As described above, no matter what unit the customer 2 collects or divides and transfers the payment, the unit of the association is used to collect the billing amounts of a plurality of invoices, Since the reconciliation with the remittance amount is performed at the level of the billing statement, the human load required for the clearing process can be minimized.

It should be noted that the transfer data recorded in step 118 is manually cleared from a terminal (not shown) or the like via the billing data management unit 8.
In particular, in the present embodiment, whether or not payment has been made is indicated by a balance instead of a flag, so that it is possible to correspond to only a part of each statement.

Although the unit to be combined when the number of unpaid invoices is four or more has been determined in advance as a month, the present invention is not limited to this. Good.

Further, in the present embodiment, the matching process performed at the time of the clearing process is executed in the order according to the flow shown in FIG. 6, but the system may be executed without executing all of them. Some processes may be omitted in consideration of the load and the contents of the order, or the order of execution may be different from that in FIG.

[0041]

According to the present invention, even if a customer makes a lump-sum transfer of a plurality of bills, for example, in arrears, the amount of the transfer and the sum of the bills of the plurality of bills are combined. Since the matching is performed automatically, an efficient matching process can be performed. As a result, it is possible to reduce the human load involved in the receivable clearing process when the transfer amount included in one transfer data does not match the charge amount of one bill.

Further, even if the customer does not make a payment for the face value of the bill, for example, it is possible to match the transfer amount with the bill amount obtained by combining the receivable data of each item included in one bill. Since the processing is performed automatically, the application can be performed in detail units.

When the number of unpaid invoices issued to the customer is equal to or more than a predetermined number, the customer's receivable data is grouped in a predetermined relatively large unit, and one Transfer amount included in the transfer data of
The billing amount in each group or the total billing amount obtained by combining the billing amounts of any one group is matched, so if the matching results in matching, the reconciliation process can be made more efficient. it can.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of a claim clearing processing system according to the present invention.

FIG. 2 is a diagram illustrating an example of data registration in a transfer data storage unit according to the present embodiment.

FIG. 3 is a diagram illustrating a data configuration example of billing data registered in a billing database according to the present embodiment.

FIG. 4 is a diagram showing an example of contents of a customer master in the present embodiment.

FIG. 5 is a diagram showing an example of a format of a bill issued in the present embodiment.

FIG. 6 is a flowchart illustrating a process of clearing credit data according to the present embodiment.

FIG. 7 is a diagram showing a combination of bills to be matched in the present embodiment.

FIG. 8 is a diagram showing a combination of specifications for performing matching in the present embodiment.

FIG. 9 is a diagram showing a combination of months for performing matching in the present embodiment.

FIG. 10 is a diagram showing months in which matching is performed in the present embodiment.

[Explanation of symbols]

1 accounting system, 2 customers (customers), 3 banks, 4
Transfer data reception processing unit, 5 billing data generation processing unit,
6 automatic billing data processing unit, 7 bill issuing processing unit, 8 billing data management unit, 9 transfer data storage unit, 1
0 Billing database, 11 Customer master.

Claims (8)

[Claims] 1. Matching the transfer amount transferred by a customer to an invoice issued to claim the invoice amount of one or a plurality of items with credit data which is unpaid billing data of the customer. In the receivables clearing system for clearing the relevant receivables data, a billing database in which billing data including customer identification information, invoice number, and billing amount are registered for each statement, and a transfer notified by a financial institution Claim data automatic clearing processing means for matching the transfer amount from the customer included in the data and the credit data of the customer registered in the billing database, and automatically clearing the corresponding credit data, The billing data automatic clearing processing means includes a transfer amount included in one transfer data and a billing amount of any of a plurality of unpaid bills for the customer. Receivable clearing processing system for causing butted against the total charge amount was determined by combining the amount billed book. 2. The billing data automatic clearing processing means, as a result of matching by a total billing amount of a plurality of bills, if there is no combination of bills matching the transfer amount,
By combining the transfer amount included in one transfer data with the charge amount of one bond data or the charge amount of any bond data among the bond data of a plurality of items included in any one invoice 2. The receivable clearing system according to claim 1, wherein the calculated total billing amount is matched. 3. The billing data automatic reconciliation processing means, when the number of unpaid bills issued to the customer is equal to or greater than a predetermined number, stores the customer's receivable data in a predetermined comparatively. 2. The method according to claim 1, wherein the grouping is performed in large units, and a transfer amount included in one transfer data and a total charge amount obtained by combining the charge amounts of any of the groups are matched. Receivable clearing system. 4. The billing data automatic reconciliation processing means, if there are more than a predetermined number of unpaid bills issued to the customer, converts the customer's receivable data into a predetermined relatively 2. The receivable clearing system according to claim 1, wherein the receivables are grouped in large units, and a transfer amount included in one transfer data and a charge amount in each group are matched. 5. Matching the transfer amount transferred by the customer to the invoice issued to claim the invoice amount of one or a plurality of items with the credit data which is unpaid billing data of the customer. In the receivable clearing system for clearing the relevant receivables data, the amount of the transfer from the customer included in one transfer data notified by the financial institution and the number of unpaid A receivables reconciliation processing method, comprising: a reconciliation invoice attaching step of reconciling a total invoice amount obtained by combining the invoice amounts of any one of the invoices. 6. As a result of matching at the matching step with a plurality of bills, if there is no combination of bills that matches the transfer amount, the transfer amount included in one transfer data and one of the transfer amounts A matching step of matching a claim amount of one claim data among a plurality of claim data included in the invoice or a total bill amount obtained by combining the claim amounts of any of the claim data. 6. The method for claim clearing processing according to claim 5, wherein 7. If the number of unpaid bills issued to the customer remains equal to or greater than a predetermined number, the customer's receivables data is grouped in a relatively large predetermined unit, and one 6. The receivable receivable according to claim 5, further comprising a combination group matching step of matching the transfer amount included in the transfer data of the first step with the total charge amount obtained by combining the charge amounts of any one of the groups. Processing method. 8. If there is more than a predetermined number of unpaid invoices issued to the customer, the customer's receivable data is grouped into predetermined relatively large units, and one 6. The receivable clearing method according to claim 5, further comprising a group assigning step of associating the transfer amount included in the transfer data with the charge amount in each group.