JP2004133514A - Credit erasure processor, credit erasure processing method, computer program and record medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a credit erasure processing method capable of performing an erasure process for a credit automated by a computer or the like even if a charge claiming destination does not coincide with a payment source. <P>SOLUTION: A server 1 comprises: a calculation control part 10; a bill detail master 11a; a money reception detail master 12a; a customer master 13; an erasure procedure master 14; a transfer fee master 15; an erasure process program storage part 16; a RAM 17 storing an erasure process program; a communication part 18 communicating with the outside; a temporary bill detail master 11b; and a temporary money reception detail master 12b. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a debt clearing apparatus, a debt clearing method, a computer program, and a recording medium.
[0002]
[Prior art]
The receivable clearing process for receivables and other receivables is performed by matching the billing statement data issued to the billing party with the receipt statement data concerning the deposit obtained from a financial institution when a deposit is received, and then comparing these data (such as the amount). Including), it is determined that there is a payment for the request, and the above-mentioned receivable clearing process is performed.
[0003]
The data to be matched for such reconciliation are as follows: billing date ≦ payment date, whether the amounts match, whether the billing party and the payment source (payment source) match, Further, there is a case such as whether or not the same number as the number (billing number) assigned to the billing statement is present in the payment statement data.
[0004]
[Problems to be solved by the invention]
Of the above items, items such as whether billing date ≤ payment date and whether the same number as the number given to the billing statement are present in the payment statement data are automatically matched to some extent using a computer. You can also.
[0005]
However, even if there is no problem in matching these items, it is not always the case that the above-mentioned reconciliation processing may be executed. For example, even if the same number as the billing number is in the payment details data, if the billing destination and the payment source (payment source) are different, the application process cannot be performed.
[0006]
As described above, regarding the payment, the billing destination and the payment source (payment source) may not always match. For example, a typical case is that another company (for example, a group company) related to the billing party pays for it.
[0007]
The present invention has been made in view of the above-described circumstances. Even when the billing party and the payment source (payment source) do not match as described above, the association is performed between the billing destination and the payment source (payment source). The present invention provides an apparatus or a method capable of performing a receivable reconciliation process.
[0008]
At the same time, a computer program and a recording medium that can execute such a method are also proposed at the same time.
[0009]
[Means for Solving the Problems]
The configuration according to the present invention includes:
In a receivable clearing apparatus in which a receivable clearing process is performed based on both data specified in the reconciliation process between the billing party and the payment source entered in the billing detail data and the payment detail data, respectively. ,
A billing destination master in which the billing destination and the payment source are associated with each other including a case where the billing destination and the payment source are different is provided in the means for storing data,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and The basic feature is that the receivables clearing process is performed based on the billing detail data and the payment detail data described in (1).
[0010]
According to the above configuration, a specific person (including an individual or a corporation) related to the billing party can be registered in advance in the billing destination master, and the registered person is thereby set as a billing party as a payment source. Will be associated with Therefore, even when a payment is made from a payment source that does not exist in the billing party when the aforesaid calculation means performs the reconciliation processing, it is associated with the billing party of the specific billing statement data by referring to the billing party master. Since it is clear that the billing destination has been set, the associated billing destination is specified from the top entry source in the payment detail data, and the corresponding billing detail data is extracted. Based on the billing statement data and the payment statement data having such a correspondence, the above-mentioned calculating means performs the claim clearing process. Of course, even in the case where the billing party is the payment source, the claim clearing process can be performed by setting a flag in the billing party master and referring to the same as in claim 3 described later.
[0011]
The structure of the claim clearing apparatus of claim 2 is different from that of claim 1 in that, when a grouped company or the like becomes a billing party, a specific person representing the group pays (payment source). ) Is defined so that payment (payment) for the above-mentioned request can be made. In other words, one or more grouped billing destinations and one payment source are associated with each other and registered in the billing destination master, thereby making it possible.
[0012]
The configuration of the claim clearing processing device according to claim 3 stipulates exceptions to the claim clearing processing when payment is made by grouping registration as described above. That is, as described above, one or more grouped billing destinations and one payment source are registered in the billing destination master in association with each other, so that a payment source different from the billing destination included in the billing statement data is registered. According to the configuration of claim 2, even if payment is made by the above, the calculation means refers to the billing destination master, and can specify the billing destination associated with the top deposit source in the payment details data, so that the corresponding billing is performed. The statement data is extracted, and the receivable clearing process is performed based on the corresponding statement statement data and payment statement data. However, if the payment source is always fixed as a specific person in such a group, if the billing party is for some reason, it becomes necessary to become the payment source and make a transfer etc. In this case, it becomes impossible to extract the billing detail data and the payment detail data in correspondence with each other by referring to the billing destination master, and perform the receivable clearing process. For example, if the transfer was urgently required, and the transfer was not made by a specific person registered in the bill-to master, and the transfer was made directly by yourself. Despite the fact, it will not be possible to apply for receivables. Therefore, even if a specific person in the group is registered as a payment source in the billing destination master, the billing destination is to make a payment (such as a transfer) to the other party (ie, billing destination = payment). In the case of the original case), the receivables can be cleared.
[0013]
As a more specific configuration, one or a plurality of grouped billing destinations and one payment source are associated with each other and registered in the billing destination master, and a flag indicating that the billing destination and the payment source may coincide with each other is set. Is provided in the billing destination master, and when the flag is set, when the billing destination of the billing detail data matches the deposit source of the payment detail data, the flag is referred to by the arithmetic means, The present invention is characterized in that the receivables clearing process is performed based on both the detailed data in which the billing party and the payment source match.
[0014]
The configurations of claims 4 to 6 define and define the configuration of the above-described apparatus as a configuration of a method.
[0015]
The configuration of claim 4 corresponds to the device configuration of claim 1, and more specifically,
A receivable reconciliation processing method in which receivable reconciliation processing is performed on the basis of both data specified in the matching process between the billing party and the payment source entered in the billing detail data and the payment detail data, respectively. ,
The association between the billing party and the payment source including the case where the billing party and the payment source are different is registered in the billing destination master,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and Is characterized in that a claim clearing process is performed based on the billing statement data and the payment statement data.
[0016]
The configuration of the method according to claim 5 corresponds to the configuration of the device according to claim 2, and more specifically, one or a plurality of grouped billing destinations and one payment source are associated with each other. It is characterized in that it is registered in the bill-to master.
[0017]
Further, the configuration of the method according to claim 6 corresponds to the configuration of the device according to claim 3, and more specifically, one or a plurality of grouped billing destinations and one payment source are associated with each other. In addition to being registered in the bill-to master, the bill-to master is provided with a flag that may match the bill-to and the payment source, and if the flag is set, the bill-to When the payment source of the payment details data matches, the flag is referred to by the above-mentioned calculating means, and the receivable clearing process is performed based on both the specification data where the billing party and the payment source match. And
[0018]
On the other hand, the configuration of claim 7 to claim 9 specifies a program executable by the computer in order to make the computer execute the method defined in claim 4 to claim 6.
[0019]
That is, as a configuration for solving the above-mentioned problem, a computer that can execute each of the processes defined in claims 4 to 6 using a configuration of the computer and that can be read and executed by the computer. Disclose about the program. Needless to say, these configurations may be provided not only as a computer program but also as a configuration of a recording medium storing a program having a similar function (claim 10), as described later. In this case, the computer may be a general-purpose computer including the configuration of the central processing unit, or may include a dedicated machine or the like dedicated to a specific process. There is no particular limitation as long as it is accompanied.
[0020]
When such a program for causing the computer to execute each of the above processes is read out by the computer, the same process as any one of the processes defined in claims 4 to 6 is executed.
[0021]
In addition, by executing the computer program using existing hardware resources, the method of the present invention as a new application can be easily executed on existing hardware. Further, by recording such a computer program on the above-mentioned recording medium, the computer program can be easily distributed and sold as a software product. In addition, the configuration of the recording medium may be the configuration of an internal storage device such as a RAM or a ROM or the configuration of an external storage device such as a hard disk, in addition to the above-described format. If it does, it goes without saying that it is included in the recording medium defined in the present invention.
[0022]
The function of executing a part of the processing described in claims 7 to 9 may be a function incorporated in a computer (a function incorporated in a computer as hardware). (The functions may be realized by an operating system or another application program incorporated in the computer.) The program may include an instruction to call or link a function performed by the computer. good.
[0023]
This is because a part of each processing defined in claims 7 to 9 is substituted by a part of a function achieved by, for example, an operating system, and a program or a module for realizing the function is not included. Although not directly recorded, if some of the functions of the operating system that achieve those functions are called or linked, the configuration is substantially the same.
[0024]
In addition to being used by itself, the program described above can be recorded on a recording medium, distributed or sold, and transmitted by communication or the like, as described later, and can be transferred.
[0025]
Among them, the configuration of the computer program according to claim 7 is a configuration corresponding to the configuration of claim 4, and the specific configuration is as follows.
A computer program for causing a computer to execute a claim clearing process on the basis of both data specified in the matching process between the billing party and the depositing source, which are entered in the billing detail data and the deposit detail data, respectively. ,
By executing the computer program,
A registration process for associating the billing party and the payment source including a case where the billing destination and the payment source are different is received by the billing destination master,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and Is characterized in that a claim clearing process is performed based on the billing statement data and the payment statement data.
[0026]
The configuration of claim 8 is a configuration corresponding to the configuration of claim 5, and more specifically, one or more grouped billing destinations and one payment source are associated with each other and registered in the billing destination master. A computer program characterized by being performed.
[0027]
The configuration of claim 9 is a configuration corresponding to the configuration of claim 6, and more specifically, one or a plurality of grouped billing destinations and one payment source are associated with each other, and At the same time, the billing destination master is provided with a flag in which the billing destination and the payment source may match, and if the flag is set, the billing destination of the billing detail data and the payment When the payment source matches, the flag is referred to by the calculating means, and the claim clearing process is performed based on both detailed data in which the billing destination and the payment source match.
[0028]
Further, as described above, the configuration of claim 10 specifies a computer-readable recording medium in which the computer program according to any one of claims 6 to 9 is stored. That is, these computer programs are stored in a recording medium, and can be used as a transaction target or actually executed.
[0029]
The computer that executes the method or the program (or the program read from the recording medium) or the computer that configures the system may have one configuration (such as a stand-alone computer), but is not limited thereto. Instead, the network is composed of a plurality of computers (such as a plurality of servers) constituting a network, and the processing performed in each of the above steps is distributed (if necessary, through an appropriate communication configuration) to these computers. May be set in the program so that the program is executed.
[0030]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is an explanatory diagram showing an outline of an embodiment of the present invention. In this example, the company provided with the server 1 is the headquarters of the group, and the company in the group provided with the terminals 3x to 3z connected to the server 1 sells or sells goods or services to any of the customers A to G. Are provided and these customers are billed. Then, each customer uses one of their own terminals 4a to 4g to make a transfer request to the depositor bank that has a transaction with these customers, and furthermore the host of the bank that has a transaction with the controlling company from the bank. Transfer processing is performed on (2). Thereafter, based on the billing statement data possessed by the group company regarding the billing and the receipt statement data sent from the host 2 side, the server 1 performs the processing of clearing the receivables (such as accounts receivable). This is illustrated by this figure.
[0031]
Here, the fact that the three group companies are enclosed in squares indicates that the group is the headquarters company, and the customers A to C, which are billing destinations, are also enclosed in squares, which will be described later. As shown in FIG. 9, when the billing destination is any of the customers A to C, a transfer request for the bill is always made by the customer A (accurately, a transfer request is issued from the customer A to the depositor bank). Transfer processing is performed by the receiving bank in accordance with the transfer to the host 2 of the house bank of the controlling company; payment processing with the customer A as the receiving source by grouping). As shown in FIG. 9, when the billing destination is any of the customers E to G, the transfer request may be made by the customer G, and each of E to G is also surrounded by a square. Customers E to G who are billed In some cases, a transfer request may be made by the customer G to the receiving bank in response to a request to each of the customers E to G, or may be issued by the customers E and F themselves. Based on those transfer requests, the transfer source bank performs a transfer process to the host 2 of the bank of the controlling company; a payment process using the customer G or the customer EF itself as a payment source by grouping and special setting. )It is shown that. When the customer D becomes a billing party, the transfer request is made by the customer D according to FIG. This will be described later.
[0032]
2 to 6 show the functional block configuration in the server 1 of the supervising company and the flow of processing in these functional blocks in the case of the framework configuration shown in FIG.
[0033]
As shown in these drawings, the server 1 includes an arithmetic control unit 10 composed of a CPU, a billing statement master 11a composed of a hard disk drive, a payment statement master 12a, a customer master 13, an application procedure master 14, A transfer fee master 15, a clearing processing program storage section 16, a RAM 17 for storing the clearing processing program to be read and executed by the arithmetic and control unit 10, and an external communication. And a communication unit 18 for performing the communication.
[0034]
In addition, the temporary billing statement master 11b and the temporary receipt statement master 12b shown in these drawings are configured using the hard disk drive or the RAM 17. By executing the reconciliation processing program in the arithmetic and control unit 10, the billing statement data of a specific group company to be reconciled in the billing statement master 11 a is extracted and stored in the temporary billing statement master 11 b. Temporary storage of billing statement data stored for the clearing process, and payment statement data addressed to a specific group company to be cleared in the payment statement master 12a are extracted and stored in the temporary payment statement master 12b. It functions as a temporary storage unit for the payment details data stored for the application processing.
[0035]
As shown in FIG. 2, in the server 1, the billing statement data sent to the customers A to G from the billing source terminals 3 x, 3 y and 3 z of the group company is arithmetically controlled via the communication unit 18. These are sent to the unit 10 and are further stored in the billing statement master 11a by the arithmetic and control unit 10. Similarly, the server 1 transfers funds from these depositor banks to the host 2 at the bank of the supervising company based on the transfer request made by the customers A, D, and EG for the requests of the group companies. The processing is performed, and the payment statement data addressed to each of the group companies sent from the host 2 is transferred to the arithmetic and control unit 10 via the communication unit 18, and they are further processed by the arithmetic and control unit 10. Stored in the receipt details master 12a. It should be noted that the host 2 is registered in a customer registration master (not shown) provided in the host 2 with data of the supervising company and its group companies that have a business relationship with the bank and receive the provision of this service. The payment statement data transferred from the host 2 is extracted and sent to the supervising company (in some cases, to each group company).
[0036]
Next, as shown in FIG. 3, a grouping table that defines who makes a transfer as a payment source for a bill to customers A to G, which are grouped as shown in FIGS. 9 and 28 described below, is registered. The customer master 13 (as will be described later, the customer master 13 includes, in addition to this table, setting items such as a clearing pattern, a commission adjustment setting, and a deemed clearing setting by the controlling company or a group company). Then, the calculation control unit 10 narrows down the billing statement data and the payment statement data to be applied, and stores them in the temporary billing statement master 11b and the temporary payment statement master 12b, respectively. With the above processing, the narrowing-down processing for the billing party and the payment source is performed. The process of narrowing down the subject will be described later.
[0037]
Further, in FIG. 4, as shown in FIG. 28 described later, together with the grouping table, of the 17 clearing patterns described later, clearing patterns selected and set by the supervising company or its group company, commission adjustment settings, and deemed clearing With reference to the customer master 13 in which transfer settings and the like are registered, the calculation control unit 10 refers to a clearing procedure master 14 storing 17 clearing patterns themselves and a transfer fee master 15 storing transfer fees. Then, based on the billing statement data and the payment statement data stored in the temporary billing statement master 11b and the temporary receipt statement master 12b, both data to be applied for further refining are narrowed down. In other words, a narrowing-down process is performed on the corresponding data that further narrows which data is in a corresponding relationship from both the billing detail data and the payment detail data extracted by the narrowing-down process on the subject. The process of narrowing down the correspondence data will also be described later.
[0038]
FIG. 5 shows that the calculation control unit 10 performs the matching and clearing processing of the billing statement data and the payment statement data which are in correspondence with each other in the above-described narrowing down processing, and the processing results are stored in the temporary billing statement master 11b and the temporary billing statement master 11b. The state stored in the receipt details master 12b is shown.
[0039]
FIG. 6 shows that the arithmetic and control unit 10 updates the billing statement data and the deposit statement data accumulated in the billing statement master 11a and the receipt statement master 12a by the reconciliation and reconciliation processing. This shows a state in which the processing has been executed.
[0040]
FIG. 7 is a flowchart showing a procedure for registering a setting item for reconciliation / application in the customer master 13 of the server 1 by the supervising company or the group company.
[0041]
First, for the purpose of narrowing down the billing party and the entity of the payment source, setting and registration (grouping and special setting) of customers A to G of the group company as to where payment is made for billing to those persons are performed. (Step S101).
[0042]
Subsequent processes are settings for narrowing down the corresponding data.
[0043]
First, an operator of the supervising company or a group company selects an arbitrary clearing pattern from among 17 patterns described later (the 17 patterns are stored in the clearing procedure master 14), and registers the clearing pattern to the customer master 13. Is performed (step S102).
[0044]
Then, the operator of the supervising company or the group company selects whether or not to adjust the bank transfer fee at the time of the reconciliation / clearing process, and if the fee is adjusted, also inputs the amount. In response, the server 1 checks whether fee adjustment is performed (step S103).
[0045]
If the commission adjustment is not performed (step S103; N), the process jumps to step S105.
[0046]
Conversely, when the fee adjustment is performed (step S103; Y), the setting of performing the fee adjustment in the customer master 13 and the amount of the fee for the adjustment are set (step S104).
[0047]
Next, the operator of the controlling company or group company, even if there is a discrepancy in the amount during the reconciliation / applying process, executes the reconciliation assuming that the reconciliation was successful. When performing deemed clearing, also enter the amount range. In response, the server 1 checks whether or not to perform the deemed clearing (step S105).
[0048]
Here, if the deemed clearing is not performed (step S105; N), the process ends.
[0049]
Conversely, when the deemed clearing is performed (Step S105; Y), the setting of performing the deemed clearing on the customer master 13 and the range of the difference amount (the deemed difference amount) to which the deemed clearing is performed are set ( Step S106).
[0050]
On the other hand, FIG. 8 is a flowchart showing the processing procedure of the loan clearing process by the narrowing down process of the billing party and the payment source from FIG. 3 to FIG. 6 and the narrowing down process of the corresponding data.
[0051]
Usually, the customer side determines the closing date and pays the payment on the 20th, 25th, 30th, etc. of the month, the next month, or the month after the month. Therefore, in the application processing program on the server 1 side, the end of the month is set as the receivable application processing date, and the arithmetic control unit 10 checks whether or not the processing due date has arrived (step S201). However, the processing date can be set arbitrarily, for example, every day or every few days.
[0052]
Here, when the due date has not arrived (step S201; N), the processing by the clearing processing program ends. On the other hand, when the due date has arrived (step S201; Y), whether the billing statement data and the receipt statement data that have not been processed yet to be compared and applied as shown in FIG. It is checked whether it is (Step S202).
[0053]
If both data are not present in each of the masters 11a and 12a (step S202; N), the processing by the clearing processing program ends. However, since this program is started at least every day (may be every several hours), the process starts again from the step S201.
[0054]
Conversely, when both data are present in the respective masters 11a and 12a (step S202; Y), the arithmetic control unit 10 refers to the customer master 13 (step S203), and narrows down the billing party and the payment source. [Drawing destination = the process of extracting both data of the payment source (to be applied to the drawing)] is performed. (Step S204).
[0055]
After that, in step S205, it is checked whether or not the subsequent processing from step S206 to step S215 (the narrowing down processing for the corresponding data) has been performed on all the data extracted by the narrowing down processing (step S205). ). When all of these processes have been completed (step S205; Y), the process by the reconciliation processing program ends.
[0056]
On the other hand, if the above processing is not completed (step S205; N), one or a plurality of payment detail data of an arbitrary group company and the billing party = payment source or the billing party = grouping are performed on these data. It is determined whether or not the processing from step S207 to step S214 has been performed based on all the clearing patterns selected and registered in the customer master 13 out of the 17 patterns with the billing statement data relating to the specific customer. A check is made (step S206). As will be described later, if the corresponding billing statement data and payment statement data cannot be cleared by the processing from step S207 to step S213 (step S214; N), the process returns to step S206 and returns to the customer master 13 The processing from step S207 to step S213 is newly performed according to the reconciliation pattern registered next.
[0057]
However, even if all the clearing patterns selected and registered in the customer master 13 cannot clear the corresponding billing statement data and payment statement data (N in step S214 and Y in step S206). Case), the inability to process is displayed on any of the screens of the server 1 or the screens of the billing source terminals 3x to 3z (step S216), and the process returns to the step S205, where the corresponding new billing statement data and payment are received. The narrowing-down process for the corresponding data from step S206 to step S215 is performed on the detailed data.
[0058]
In addition, in the above-mentioned step S206, when the application processing using the application pattern registered next in the customer master 13 is not completed (step S206; N), in the order of the application patterns registered in the master 13, The processing from step S207 to step S214 is performed.
[0059]
In that case, first, it is checked whether the commission adjustment is set in the customer master 13 (step S207).
[0060]
When the commission adjustment is not set in the customer master 13 (step S207; N), it is further checked whether or not the deemed application is set in the customer master 13 (step S208).
[0061]
If the deemed clearing is not set in the customer master 13 (step S208; N), the clearing pattern registered in the customer master 13 is read from the clearing procedure master 14 by the arithmetic control unit 10 and read. Then, the corresponding billing statement data and payment statement data are cleared (step S209). In this case, in the subsequent process of determining whether or not to apply in step S214, the sum of the deposit amounts described in the optional receipt details data and the amount of the invoices described in the claim detail data in a predetermined range based on the application pattern are determined. Whether or not to apply is determined by whether or not the sum matches.
[0062]
In the step S208, when the deemed application is set in the customer master 13 (step S208; Y), the application pattern and the deemed difference registered in the customer master 13 are referred to, and Based on the read-out application pattern, the application processing of the corresponding billing statement data and payment statement data is performed (step S210). Even if there is a difference between the sums of the amounts described in both data, if the difference is within the range of the above-mentioned deemed difference, it is treated as rejectable in the rejection determination process of step S214.
[0063]
In step S207, when the fee adjustment is set in the customer master 13 (step S207; Y), it is further checked whether or not the deemed clearing is set in the customer master 13 (step S211).
[0064]
When the deemed application is not set in the customer master 13 (step S211; N), the application pattern registered in the customer master 13 and the item of the priority transfer fee are referred to, and Based on the read-out payment pattern and the transfer fee amount read from the transfer fee master 15, the corresponding billing detail data and payment detail data are cleared (step S212). Even when there is a difference in the sum of the amounts of money described in both data, if the difference is the amount of money corresponding to the transfer fee, it is treated as clearable in the clearing / non-clearability determination process in step S214.
[0065]
In the above step S211, if the deemed application is set in the customer master 13 (step S211; Y), the items of the application pattern, the assumed difference and the priority transfer fee registered in the customer master 13 are referred to. Based on the clearing pattern read from the clearing procedure master 14 and the transfer fee amount read from the transfer fee master 15, the clearing process of the corresponding billing detail data and payment detail data is performed (step). S213). Even if there is a difference in the sum of the amounts of money described in both data, if the difference is a difference between the range of the deemed difference and the amount corresponding to the transfer fee, it is determined whether or not the application in step S214 is applicable. It is treated as clearable in the judgment process.
[0066]
As a result of performing the clearing process in steps S209, S210, S212 and S213, it is checked whether clearing is possible in the process (step S214), and clearing of both data is impossible. If there is (Step S214; N), the process returns to Step S206, and the clearing process from Step S207 to Step S213 is repeated based on the next clearing pattern registered in the customer master 13. .
[0067]
If both data can be cleared (step S214; Y), the results of the clearing process are stored in the temporary billing statement master 11b and the temporary receipt statement master 12b as shown in FIG. 5 (step S215). ). Thereafter, the process returns to the step S205, and it is checked whether or not a narrowing-down process for the corresponding data from the step S206 to the step S215 has been performed on the extracted all billing detail data and all the payment detail data (step S205). .
[0068]
If the processing from step S206 to step S215 has not been performed on the extracted all billing statement data and all payment statement data (step S205; N), the processing from step S206 to step S215 is repeated. Conversely, if the processing from step S206 to step S215 has been performed on all the billing statement data and all the payment statement data (step S205; Y), the clearing processing by the clearing processing program ends there.
[0069]
Finally, although not shown in this figure, when the reconciliation processing by the reconciliation processing program is completed, the billing statements stored in the temporary billing statement master 11b and the temporary receipt statement master 12b as shown in FIG. Based on the data and payment detail data clearing processing, the billing detail data and payment detail data stored in the billing detail master 11a and the payment detail master 12a are updated as if the receivable clearing process has been completed.
[0070]
FIG. 9 shows an example of a state in which a grouping table is set and registered in the customer master 13 which specifies who will make a payment as a payment source for the grouped customers A to G (see FIG. 28 differs from the case of the customer D).
[0071]
As shown in the figure, if bills are issued to customers A to C as billing destinations, payment for the bills (payment source) is always made on behalf of customer A (the billing destination is a customer). A is not a substitute payment).
[0072]
If billing is made to customers E to G as billing destinations, payment for the billing (payment source) is usually made on behalf of customer G, but this grouping table contains an application range flag. If it is set, the customer who is the billing destination (customers E and F in the drawing) can pay as a special case (it will be recognized as a payment source).
[0073]
In the example of FIG. 9, the customer D is set as the billing destination and the payment source, and the application range flag is set. This indicates a state where the above-described grouping is not set. I have.
[0074]
Next, 17 examples of the clearing patterns stored in the clearing procedure master 14 will be described with reference to FIGS.
[0075]
In this example, the payment amount and the billing amount are checked with respect to the payment detail data and the billing detail data to be cleared according to the following rules while extracting and rearranging the data.
[0076]
First, FIG. 10 shows an example of the payment statement data and the billing statement data which have been extracted based on the narrowing-down process for the billing party and the payment source entity based on FIG. 9 described above. The following examples of the erase patterns shown in FIGS. 11 to 27 will be described. Here, the billing destination of the billing detail data is the customers A to D. However, by referring to the grouping table of the customer master 13, all the payments are made by the customer A (that is, the payment source is all the customer A). (See FIG. 28), and all payment sources that have actually entered the server 1 as payment details data are customer A data as shown in the drawing. Note that, here, the customer D is different from FIG.
[0077]
Pattern 1 (see FIG. 11)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). At this time, of the N payment details data, based on the date with the latest payment date, the billing date among the target billing details data is the amount to be cleared of the data before the payment date acquired above. Is calculated. This is the first pattern rule for checking the amount of money based on the calculated total amount of deposit and the total amount of invoices to be applied. In the example of FIG. 11, the data of the black shaded line is erased.
[0078]
Pattern 2 (see FIG. 12)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing target billing date up to the last day of the previous month is calculated. This is a rule to check the amount based on the calculated total amount of the deposit and the total amount of the invoice to be applied. In the example of FIG. 12, when the application processing is performed on 2008/08/31, the data of the black shaded line is applied.
[0079]
Pattern 3 (see FIG. 13)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing target billing amount up to the last day of the month before the billing date is calculated. This is a rule to check the amount based on the calculated total amount of the deposit and the total amount of the invoice to be applied. In the example of FIG. 13, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0080]
Pattern 4 (see FIG. 14)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing date for the previous month is calculated for the billing date. This is a rule to check the amount based on the calculated total amount of the deposit and the total amount of the invoice to be applied. In the example of FIG. 14, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0081]
Pattern 5 (see FIG. 15)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). Based on the processing date (server 1 date) of the target billing detail data, the total amount of the billing target billing amount for the month before the billing date is calculated. This is a rule to check the amount based on the calculated total amount of the deposit and the total amount of the invoice to be applied. In the example of FIG. 15, when the application process is performed on 2008/08/31, the data of the black shaded line is applied.
[0082]
Pattern 6 (see FIG. 16)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). At this time, based on the latest payment date among the N pieces of payment detail data, the billing date of the target billing detail data is set to a date before the payment date acquired above, and Is a rule to check the amount while adding the invoice amount to be applied in order from the oldest data. (If there are multiple data with the same invoice date, the invoice amount to be applied is added from the smaller amount) . An amount check is performed based on the calculated total amount of the deposit and the total amount of the invoice to be applied. The check of the money amount is performed until the matching is performed or until the money amount exceeds the error range (the deemed difference amount and / or the addition amount of the transfer amount) that allows the application. In the example of FIG. 16, when the application processing is performed on 2008/08/31, the data of the black shaded line is applied.
[0083]
Pattern 7 (see FIG. 17)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). At this time, based on the latest payment date among the N pieces of payment detail data, the billing date is set to the data before the payment date obtained above, and the billing number is set. This is a rule for checking the amount while adding the billing amount to be applied in ascending order. An amount check is performed based on the calculated total amount of the deposit and the total amount of the invoice to be applied. The check of the amount is performed until the matching is completed or the error exceeds the error range allowing the application as described above. In the example of FIG. 17, when the application processing is performed on 2008/08/31, the data of the black shaded line is applied.
[0084]
Pattern 8 (see FIG. 18)
With respect to the payment details data and billing details data to be applied, the total amount of N pieces of payment details data is calculated for the target billing destination (code) or payment source (code). At this time, out of the N payment details data, based on the date of the latest payment, the scheduled collection date of the target billing details data is a data before the payment date acquired as described above. Calculate the sum of the amounts. This is a rule to check the amount based on the calculated total amount of the deposit and the total amount of the invoice to be applied. In the example of FIG. 18, the data of the black shaded line is erased.
[0085]
Pattern 9 (see FIG. 19)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). At this time, the billing detail data is the total amount of the billing amount to be applied for all data whose billing date is before the payment date. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 19, the data of the black shaded line is erased.
[0086]
Pattern 10 (see FIG. 20)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing target billing date up to the last day of the previous month is calculated. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 20, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0087]
Pattern 11 (see FIG. 21)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing target billing amount up to the last day of the month before the billing date is calculated. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 21, when the application processing is performed on 2008/08/31, the data of the black shaded line is applied.
[0088]
Pattern 12 (see FIG. 22)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). Based on the processing date (server 1 date) in the target billing detail data, the total amount of the billing date for the previous month is calculated for the billing date. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 22, when the application processing is performed on 2002/08/31, the data of the black shaded line is applied.
[0089]
Pattern 13 (see FIG. 23)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). Based on the processing date (server 1 date) of the target billing detail data, the total amount of the billing target billing amount for the month before the billing date is calculated. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 23, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0090]
Pattern 14 (see FIG. 24)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). This is a rule for checking the amount of data to be applied, in order from the data with the oldest billing date, to the data with the billing date before the payment date in the target billing detail data. (If there are a plurality of data with the same billing date, the data to be applied for is charged from the data with the smaller amount). The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 24, when the reconciliation process is performed on 2008/08/31, the data of the black shaded line is reconciled.
[0091]
Pattern 15 (see FIG. 25)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). This is a rule that checks the amount of data to be applied while increasing the invoice amount to be applied to data in which the invoice date is before the payment date in the order from the lowest invoice number in the invoice details data to be processed. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 25, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0092]
Pattern 16 (see FIG. 26)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). At this time, the billing detail data is the total amount of the billing target for application for all data whose scheduled collection date is before the payment date. The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 26, the data of the black shaded line is erased.
[0093]
Pattern 17 (see FIG. 27)
For the payment details data and billing details data to be applied, for the billing destination (code) or payment source (code) to be processed, the data of one payment detail data is set in order from the oldest payment date. (If there are a plurality of data with the same payment date, start with the data with the lowest item number). Among the billing details data to be processed, the billing date is a rule that checks the data to be cleared for one billing detail data in order from the data with the oldest billing date to the data before the payment date (billing) If there are multiple data with the same date, check from the data with the smaller billing amount for clearing). The check of the amount is performed until the target billing statement data matches or the check of all the payment statement data is completed. In the example of FIG. 27, when the reconciliation processing is performed on 2002/08/31, the data of the black shaded line is reconciled.
[0094]
The above-mentioned clearing pattern is stored as data in the clearing procedure master 14 as described above. Then, in the customer master 13, it is possible to assign priorities to up to five patterns (of course, it is possible to increase the number of patterns or to reduce the number of patterns less than 5). ing. The data is read out by the arithmetic and control unit 10 in accordance with the above order registered in the customer master 13. At the time of the clearing process, the data is read out in steps S209, S210, S212, and S213 in FIG. This is done using patterns.
[0095]
(Example)
Next, an embodiment of the present invention will be described with reference to FIGS.
[0096]
FIG. 28 shows a setting example of each item in the customer master 13 in this embodiment. In this example, the customers B, C, and D are set to group the customer A in the customer master 13. The clearing flags set in the clearing range are set for the customers B to D. Therefore, for billing to these customers, the billing is paid to each billing source on behalf of the customer A. (Deposited) or paid (deposited) by themselves.
[0097]
When the billing destination is the customer A, the pattern 17 is used with the highest priority as the application pattern, the pattern 12 is used next, and three more priority patterns are registered in order. Similarly, as the clearing pattern for the customer B, the pattern 14 is used with the highest priority, the pattern 17 is used next, and three more priority patterns are registered in order. As the application pattern for the customer C, the pattern 2 is used with the highest priority, the pattern 17 is used next, and three more priority patterns are registered in order. As for the consumption pattern relating to the customer D, the pattern 1 is used with the highest priority, the pattern 10 is used next, and three more priority patterns are registered in order.
[0098]
On the other hand, the fee adjustment is set to “use” in each case, and the amounts of the prioritized fees are all “higher amounts”. FIG. 29 shows the contents of the transfer fee data stored in the transfer fee master 15, according to which the "high amount" starts from 420 yen, and if the calculation does not fit, 315 yen , 210 yen and 105 yen in this order.
[0099]
In addition, the deemed application is set to “use”, and the deemed difference is in the range of “−10 to 10 yen”.
[0100]
As described above, when the contents of the customer master 13, the clearing procedure master 14, and the transfer fee master 15 are set, as shown in FIG. FIG. 5 shows an example of corresponding billing statement data and payment statement data when payment is made (that is, customers A to D become billing destinations), and thereafter, payment is made with the customer A as the payment source.
[0101]
Here, since the narrowing-down process for the subject has already been completed, the narrowing-down process for the corresponding data for narrowing down which data has a corresponding relationship is performed. The date when this process was performed is August 4, 2002.
[0102]
First, in the receivable clearing process by the arithmetic and control unit 10, the process is performed in order from the first of the above-mentioned payment detail data.
[0103]
1. The setting of the customer master 13 is referred to from the payment source (code) of the payment details data to be processed. In the example of FIG. 30, since the payment source is customer A, the customer master 13 refers to the setting of customer A.
[0104]
1- (1) By setting the clearing range of the customer master 13 shown in FIG. 28, the billing statement data to be cleared is extracted. In the example of FIG. 30, the clearing range flag (*) is not set in the clearing range of the billing destination A in the customer master 13 (FIG. 28). This indicates that the billing statement data in which A is set in the payment source (code) is the data to be cleared. In the example shown in the figure, all the billing detail data of six cases are to be processed.
[0105]
Supplement: If the clearing range flag (*) is set in the clearing range of the billing destination A in the customer master 13, billing detail data in which A is set in the billing destination (code), that is, from the top Only three billing statement data are targeted.
[0106]
By setting the application pattern, the corresponding billing statement data is further narrowed down. In the example of the above figure, the first clearing pattern of the billing destination A in the customer master 13 is set to 17 (FIG. 28). The clearing pattern 17 narrows the clearing target billing detail data to the first billing detail data with the oldest billing date as shown in the example of FIG. 27 described above. Here, the data to be collated is determined.
[0107]
Next, a flow of checking each amount will be described.
[0108]
2. Check the deposit amount and billed amount. In the processing described above, the data is narrowed down to the data shown in FIG.
[0109]
2- (1) Check whether the total amount of money to be processed is the total amount of money to be processed.
In the example of FIG. 31, the total deposit amount of 14,680 yen and the total charge amount of 20,000 yen are not equal.
[0110]
2- (2) Next, a judgment is made in the transfer fee adjustment (confirm the setting of the transfer fee adjustment in the customer master 13).
In the billing destination A of the customer master 13, the transfer fee adjustment is used (FIG. 28). Therefore, it is checked whether the difference between the billing amount meter and the deposit amount meter is the amount registered in the transfer fee master 15. In the above example, the transfer fee is not adjusted because the difference is 5,320 yen.
[0111]
2- (3) Next, a decision is made in the deemed clearing (confirmation of the clearing setting only in the customer master 13).
In the billing destination A of the customer master 13, the deemed clearing is used. Accordingly, the difference is calculated in order from the highest amount registered in the transfer fee master 15 by applying to the formula of the total amount of the invoice- (the total amount of the deposit + the transfer fee), and the difference is determined as the adjustment range of the deemed application. Check inside. In the above example, no matter how much the transfer fee amount registered in the transfer fee master 15 is adjusted, it does not fall within the deemed clearing adjustment range (between -10 and 10 yen).
Invoice amount total-(deposit amount total + transfer fee) = difference calculated by
2,0000 yen-(14,680 yen + 420 yen) = Difference 4,900 yen
[0112]
Next, the transfer fee adjustment is not performed, and only the deemed application adjustment is confirmed. In the above example, of course, this does not fall within the adjustment range of the deemed clearing.
Invoice amount total-(deposit amount total amount) = Difference calculated by
2,0000 yen-(14,680 yen) = balance 5,320 yen
[0113]
Supplement: If both the transfer fee adjustment and the deemed clearing are not used, the checks in 2- (2) and (3) above are not performed. Therefore, unless the total amount of deposit is equal to the total amount of billing, no application matching is performed.
[0114]
By checking up to this point, data that cannot be cleared is determined to be a clearing unmatch.
[0115]
However, in the clearing pattern 17, if the clearing cannot be matched with the first billing detail data with the oldest billing date, the rule is to check the amount with the next oldest billing detail data. Therefore, the next check is made with the data shown in FIG.
[0116]
That is, based on the data shown in FIG. 32, by sequentially checking from the above 2- (1), it is possible to confirm that it is within the adjustment range by confirming 2- (3).
Invoice amount total-(deposit amount total + transfer fee) = difference calculated by
15,000 yen-(14,680 yen + 315 yen) = Difference 5 yen
[0117]
The adjustment range of the deemed clearing is between -10 and 10 yen, so it is within the range. Therefore, it is determined that the matching is clear. In the application pattern 17, thereafter, the next payment specification data is checked sequentially with the payment specification data with the oldest billing date in the same manner as described above, but all the application unmatches are determined.
[0118]
3. Change the application pattern and check.
In the example of “checking the amount of money to be paid and the amount of money to be charged”, the pattern 12 is set after the application pattern 17 (FIG. 28). Therefore, the clearing pattern 12 will be performed.
[0119]
In the confirmation processing up to the “check of the deposit amount and the bill amount”, the data shown in FIG. 33 has not been applied.
[0120]
Therefore, when the billing statement data corresponding to the clearing pattern 12 is narrowed down, the result is further as shown in FIG.
[0121]
The clearing pattern 12 is a rule for confirming the total amount obtained by adding the billing detail data of the previous month on the basis of the processing date. Therefore, the above-mentioned “2. Check of the amount of money paid and the amount of money charged” is performed with a total amount of money 79,580 yen and a total amount of money 80,000 yen.
[0122]
If the data of FIG. 34 is checked in order from 2- (1), it is determined that the matching is clear by confirming 2- (2).
Invoice amount total = (deposit amount total + transfer fee)
80,000 yen = (79,580 yen + 420 yen)
[0123]
As described above, the application is automatically performed based on various conditions set in the customer master 13.
[0124]
In this embodiment described above, the processing result as shown in FIG. 35 is finally automatically processed.
[0125]
As described above, according to the configuration of the present embodiment, even when the billing party and the payment source (payment source) do not match, the association is performed between them, and the receivable clearing process is automated by a computer or the like. Will be able to do. Further, from both the billing detail data and the payment detail data extracted by the narrowing-down process relating to such an entity, which data is in correspondence with each other is further narrowed down according to a reconciliation processing procedure using some predetermined application patterns. Since the narrowing down process for the corresponding data is performed, the computer automatically performs the loan clearing process.
[0126]
It should be noted that the method for retiring a loan according to the present invention is not limited to the above-described embodiment, and it goes without saying that various changes can be made without departing from the spirit of the present invention.
[0127]
【The invention's effect】
As described above, according to the claim clearing processing apparatus, the claim clearing processing method, the computer program, and the recording medium according to claims 1 to 10 of the present invention, the billing party and the payment source (payment source) are Even if they do not match, it is possible to obtain an excellent effect that it is possible to perform the association between them and automate the processing by a computer or the like to perform the reconciliation processing of the receivables.
[Brief description of the drawings]
FIG. 1 is an explanatory diagram showing an outline of an embodiment of the present invention.
FIG. 2 is an explanatory diagram showing a functional block configuration in a managing company server 1 and a processing flow in the block configuration.
FIG. 3 is an explanatory diagram showing a functional block configuration in a server 1 of the controlling company and a processing flow in the block configuration.
FIG. 4 is an explanatory diagram showing a functional block configuration in the server 1 of the controlling company and a processing flow in the block configuration.
FIG. 5 is an explanatory diagram showing a functional block configuration in the server 1 of the controlling company and a processing flow in the block configuration.
FIG. 6 is an explanatory diagram showing a functional block configuration in the server 1 of the controlling company and a processing flow in the block configuration.
FIG. 7 is a flowchart showing a registration procedure of a setting item for reconciliation / application in the customer master 13 of the server 1 by a supervising company or a group company.
FIG. 8 is a flowchart showing a processing procedure of a debt clearing process by a narrowing process relating to a billing party and a payment source entity and a narrowing process relating to corresponding data in FIGS. 3 to 6;
FIG. 9 is an explanatory diagram showing an example of a state of setting and registering a grouping table in the customer master 13 which defines who will make a payment as a payment source for grouped customers A to G;
FIG. 10 is an explanatory diagram showing an example of payment statement data and billing statement data that have been extracted based on the narrowing-down process for the billing party and the payment source entity based on FIG. 9;
FIG. 11 is an explanatory diagram showing an example of an application pattern 1;
FIG. 12 is an explanatory diagram showing an example of a consumption pattern 2;
FIG. 13 is an explanatory diagram showing an example of an application pattern 3;
FIG. 14 is an explanatory diagram showing an example of a clearing pattern 4;
FIG. 15 is an explanatory diagram showing an example of an application pattern 5;
FIG. 16 is an explanatory diagram showing an example of an application pattern 6;
FIG. 17 is an explanatory diagram showing an example of an application pattern 7;
FIG. 18 is an explanatory diagram showing an example of a consumption pattern 8.
FIG. 19 is an explanatory diagram showing an example of an application pattern 9;
FIG. 20 is an explanatory diagram showing an example of an application pattern 10;
FIG. 21 is an explanatory diagram showing an example of a consumption pattern 11;
FIG. 22 is an explanatory diagram showing an example of an application pattern 12;
FIG. 23 is an explanatory diagram showing an example of an application pattern 13;
FIG. 24 is an explanatory diagram showing an example of an application pattern 14;
FIG. 25 is an explanatory diagram showing an example of an application pattern 15;
FIG. 26 is an explanatory diagram showing an example of an application pattern 16;
FIG. 27 is an explanatory diagram showing an example of a consumption pattern 17;
FIG. 28 is an explanatory diagram showing a setting example of each item in the customer master 13 in one embodiment of the present invention.
FIG. 29 is an explanatory diagram showing a setting example of a transfer fee master 15 in the configuration of the embodiment.
FIG. 30 shows the corresponding billing statement data and deposit statement data when billing is made to customers A to D from each group company led by the supervising company, and thereafter payment is made with customer A as the payment source. It is explanatory drawing which shows an example of.
FIG. 31 is an explanatory diagram showing a state in which narrowing-down has been performed according to the initially set erase pattern 17;
FIG. 32 is an explanatory diagram showing a state where the next billing statement data is read out when the application cannot be cleared in the first amount check.
FIG. 33 is an explanatory diagram showing an example of unapplied billing statement data and payment statement data remaining after processing by the reconciliation pattern 17 is completed.
FIG. 34 is an explanatory diagram showing a state in which narrowing down has been performed according to the next consumption pattern 12;
FIG. 35 is an explanatory diagram showing a final processing result in the configuration of the present embodiment.
[Explanation of symbols]
1 server
2 Host
3x-3z Billing source terminal
4a-4g customer terminal
10 Operation control unit
11a Billing item master
11b Temporary billing item master
12a Receipt details master
12b Temporary receipt details master
13 Customer Master
14 Application procedure master
15 Transfer fee master
16 Clearing program storage
17 RAM
18 Communication unit

Claims (10)

In a receivable clearing apparatus in which a receivable clearing process is performed based on both data specified in the reconciliation process between the billing party and the payment source entered in the billing detail data and the payment detail data, respectively. ,
A billing destination master in which the billing destination and the payment source are associated with each other including a case where the billing destination and the payment source are different is provided in the means for storing data,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and Wherein the claim clearing process is performed based on the billing detail data and the payment detail data. 2. The claim clearing apparatus according to claim 1, wherein one or more grouped billing destinations and one payment source are registered in the billing destination master in association with each other. One or more grouped billing destinations and one payment source are associated and registered in the billing destination master, and a flag indicating that the billing destination and the payment source may match is provided in the billing destination master. When the flag is set, when the billing destination of the billing statement data and the deposit source of the receipt statement data match, the flag is referred to by the calculating means, and the billing party and the deposit source match. 3. The claim clearing apparatus according to claim 2, wherein the claim clearing process is performed based on both of the detailed data. A receivable reconciliation processing method in which receivable reconciliation processing is performed on the basis of both data specified in the matching process between the billing party and the payment source entered in the billing detail data and the payment detail data, respectively. ,
The association between the billing party and the payment source including the case where the billing party and the payment source are different is registered in the billing destination master,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and Wherein the claim clearing process is performed based on the billing detail data and the payment detail data. 5. The method according to claim 4, wherein one or a plurality of grouped billing destinations and one payment source are registered in the billing destination master. One or a plurality of grouped billing destinations and one payment source are associated with each other and registered in the billing destination master, and the billing destination master is provided with a flag in which the billing destination and the payment source may coincide with each other. When the flag is set and the billing destination of the billing statement data and the deposit source of the receipt statement data match, the flag is referred to by the arithmetic means and the billing party and the deposit source are The claim clearing processing method according to claim 5, wherein the claim clearing processing is performed based on both the detailed data in which the two match. A computer program for causing a computer to execute a claim clearing process on the basis of both data specified in the matching process between the billing party and the depositing source, which are entered in the billing detail data and the deposit detail data, respectively. ,
By executing the computer program,
A registration process for associating the billing party and the payment source including a case where the billing destination and the payment source are different is received by the billing destination master,
The calculating means for performing the above-mentioned matching process refers to the billing destination master, specifies the billing destination associated with the top payment source in the payment details data, extracts the corresponding billing details data, and A receivable clearing process based on the billing detail data and the payment detail data. 8. The computer program according to claim 7, wherein one or more grouped billing destinations and one payment source are registered in the billing destination master in association with each other. One or a plurality of grouped billing destinations and one payment source are associated with each other and registered in the billing destination master, and the billing destination master is provided with a flag in which the billing destination and the payment source may coincide with each other. When the flag is set and the billing destination of the billing statement data and the deposit source of the receipt statement data match, the flag is referred to by the arithmetic means and the billing party and the deposit source are 9. The computer program according to claim 8, wherein the receivable clearing process is performed on the basis of the two detailed data items that match. A computer-readable recording medium storing the computer program according to any one of claims 7 to 9.

Images