Program, Billing Management Device, Billing Management Method, and Server

Abstract

To provide a technology relating to a program and a billing management device that enables appropriate discovery of a combination of multiple billing information items corresponding to deposit information. [Solution] The computer executes a billing data acquisition process that acquires billing data including the billing amount, a deposit data acquisition process that acquires deposit data including the deposit amount, a search request acquisition process that acquires a search request for corresponding billing data which is billing data corresponding to the deposit data, a threshold acquisition process that acquires from the user a threshold set for the difference between the total billing amount obtained by adding up the billing amounts of the corresponding billing data and the total deposit amount obtained by adding up the deposit amounts of the deposit data in response to the search request, and a search process that searches the billing data for corresponding billing data whose difference satisfies the threshold based on the billing data, deposit data, and threshold.

Description

Technical Field

[0001] The present invention relates to a program, a billing management device, a billing management method, and a server.

Background Art

[0002] In commercial transactions, settlement by transfer may be performed. For example, in business-to-business transactions, there is a settlement method called deferred payment in which an invoice is issued from the seller after the provision of goods or services, and the buyer makes a payment to settle the transaction. The payment is made through an institution that conducts fund transfers, such as a bank. As part of the accounting operations, the seller associates the billing data with the payment data corresponding to the billing data, and performs an operation called reconciliation to make the associated payment data and billing data into data for which billing and payment have been completed.

[0003] In commercial transactions, there may be cases where multiple invoices are issued from the same seller to the same buyer. The buyer may settle the transaction by transferring the total amount of the multiple invoices to the seller's bank account or the like in one lump sum. In this case, a data matching program that accurately associates the billing data with the payment data and enables reconciliation processing is disclosed in Patent Document 1.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the data matching program described in Patent Document 1, a consumption tax error caused by differences in the handling of consumption tax between the seller and the buyer and a fee error caused by fees charged by banks or the like are preset. In this program, when associating claim data with payment data, an error adjustment process is performed. If the error is within a preset range, the total claim amount and the total payment amount are set to the same amount and offset processing is performed.

[0006] However, even when a consumption tax error or a fee error is preset, for example, if the error setting is inappropriate, the process of associating claim data with payment data is not performed appropriately. An inappropriate error setting means that a common error is set for all buyers and it is not possible to correspond to individual buyers. In this case, the user needs to review the consumption tax error and fee error set for all buyers and then execute the process of associating the data again in the program. Since such a review procedure is necessary, it is considered that a combination of a plurality of claim data corresponding to the payment data cannot be found sufficiently appropriately, and furthermore, the convenience of the user is slightly reduced.

[0007] Therefore, an object of the present invention is to provide a program, a claim management device, a claim management method, and a server that can appropriately find a combination of a plurality of claim information corresponding to payment information.

Means for Solving the Problems

[0008] A program according to an aspect of the present invention causes a computer to execute a claim data acquisition process for acquiring claim data including a claim amount, a payment data acquisition process for acquiring payment data including a payment amount, a search request acquisition process for acquiring a search request for corresponding claim data that is claim data corresponding to the payment data, a threshold acquisition process for acquiring from a user a threshold provided for a difference between a total claim amount obtained by summing the claim amounts of the corresponding claim data and a total payment amount obtained by summing the payment amounts of the payment data in response to the search request, and a search process for searching for corresponding claim data whose difference satisfies the threshold from the claim data based on the claim data, the payment data, and the threshold.

[0009] According to this aspect, when a computer acquires a search request, a threshold value provided for the difference between the total claim amount and the total payment amount is acquired by threshold value acquisition processing. Since the acquisition of the threshold value is performed after the search request, for example, when an appropriate combination of corresponding claim data, which is claim data corresponding to payment data, and the payment data is not found in a single search process, a search request can be acquired again to acquire a new threshold value. Thereby, it becomes possible to change the threshold value, and it becomes possible to sufficiently and appropriately find combinations of a plurality of claim data corresponding to the payment data.

[0010] The program in the above aspect may further cause the computer to execute selection information acquisition processing for acquiring, from among the claim data, first selection information indicating the claim data used in the search process, and, from among the payment data, second selection information indicating the payment data used in the search process.

[0011] According to this aspect, the user can pre-select the claim data and payment data necessary for searching for the corresponding claim data. Thereby, for example, it becomes possible to exclude claim data or payment data having specific amounts during the search, and it becomes possible to appropriately perform the search for the corresponding claim data.

[0012] In the above aspect, the search process searches for at least one or more candidates of the corresponding claim data that satisfy the threshold value, and the program causes the computer to execute result screen generation processing for generating screen information of a search result screen in which at least one or more candidates of the corresponding claim data are displayed separately from each other, and designation processing for acquiring, from the user, information designating one candidate of the corresponding claim data from among at least one or more candidates of the corresponding claim data through the search result screen.

[0013] As a result, when at least one or more candidate claim data are found in the search process, it becomes possible for the user to grasp the candidates. Since the user can select an appropriate combination from the candidates, it becomes possible to appropriately perform the search for combinations.

[0014] In the above aspect, the computer is further caused to execute an extraction process of extracting duplicate claim data in which the claim amounts of each of the claim data are the same, and the search process may search for corresponding claim data including the duplicate claim data.

[0015] As a result, when claim data with the same claim amount is repeatedly included in the claim data, the claim data is extracted as duplicate claim data. Since there is a high possibility that the buyer will make a lump-sum payment for the duplicate claim data, it becomes possible to appropriately perform the search for combinations by searching for corresponding claim data that includes the duplicate claim data.

[0016] In the above aspect, the computer is further caused to execute a fee acquisition process of acquiring from the user the amount of the deposit fee associated with each of the payers for making a deposit, and the search process may search for corresponding claim data based on a threshold value including the amount of the deposit fee associated with the payer.

[0017] According to this aspect, it becomes possible to acquire the fee for each buyer, and by performing the search based on the acquired fee, it becomes possible to appropriately perform the search for combinations.

[0018] Further, the claim management method according to another aspect of the present invention includes: obtaining claim data including a claim amount; obtaining payment data including a payment amount; obtaining a search request for corresponding claim data which is claim data corresponding to the payment data; obtaining, from a user, a threshold value provided for a difference between a total claim amount obtained by summing the claim amounts of the corresponding claim data and a total payment amount obtained by summing the payment amounts of the payment data according to the search request; and searching the claim data for corresponding claim data whose difference satisfies the threshold value based on the claim data, the payment data, and the threshold value.

[0019] Further, the claim management apparatus according to another aspect of the present invention includes: a claim data acquisition unit that acquires claim data including a claim amount; a payment data acquisition unit that acquires payment data including a payment amount; a search request acquisition unit that acquires a search request for corresponding claim data which is claim data corresponding to the payment data; a threshold value acquisition unit that acquires, from a user, a threshold value provided for a difference between a total claim amount obtained by summing the claim amounts of the corresponding claim data and a total payment amount obtained by summing the payment amounts of the payment data according to the search request; and a search unit that searches the claim data for corresponding claim data whose difference satisfies the threshold value based on the claim data, the payment data, and the threshold value.

[0020] Further, the server according to another aspect of the present invention includes: a data transmission unit that transmits claim data including a claim amount and payment data including a payment amount to a terminal capable of communicating with the server; and a program transmission unit that transmits to the terminal a program which causes the terminal to execute a search request acquisition process for acquiring a search request for corresponding claim data which is claim data corresponding to the payment data, a threshold value acquisition process for acquiring, from a user, a threshold value provided for a difference between a total claim amount obtained by summing the claim amounts of the corresponding claim data and a total payment amount obtained by summing the payment amounts of the payment data according to the search request, and a search process for searching the claim data for corresponding claim data whose difference satisfies the threshold value based on the claim data, the payment data, and the threshold value.

[0021] According to this aspect, based on the program transmitted from the server to the terminal, the terminal performs a search process. Thereby, while reducing the server load due to the search process, it is possible to appropriately perform the search of the corresponding claim data.

Effects of the Invention

[0022] According to the present invention, it is possible to provide a program, a claim management device, a claim management method, and a server that can appropriately discover combinations of a plurality of claim information corresponding to payment information.

Brief Description of the Drawings

[0023]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Mode for Carrying Out the Invention

[0024] A preferred embodiment of the present invention will be described with reference to the accompanying drawings. In each figure, those with the same reference numerals have the same or similar configurations.

[0025] The first embodiment will be described. FIG. 1 shows a schematic diagram of a claim management system 10 according to the first embodiment. The claim management system 10 includes a claim management device 100 and user terminals 200a, 200b, 200c. The claim management device 100 and the user terminals 200a, 200b, 200c can communicate with a bank system 300 through a network N. The number of user terminals may be more than that shown in FIG. 1. Also, hereinafter, the individual user terminals 200a, 200b, 200c will be described as the user terminal 200 without distinguishing them.

[0026] The claim management device 100 is a device for providing a service that manages a user's claim information by allowing the user to access from the user terminal 200 through a web browser or the like and perform information transmission and reception. The claim management device 100 is an information processing device having a computer that performs predetermined processing by executing a predetermined program, and is, for example, a server device.

[0027] Information for operating the claim management device 100 on the web browser is transmitted from the claim management device 100 to the user terminal 200. The information for operation is, for example, information regarding a program operating on the web browser or a screen displayed on the web browser.

[0028] The user terminal 200 is an electronic device used by the user, and here it is assumed to be a personal computer. Note that the user terminal 200 may be a tablet terminal or a smartphone.

[0029] The bank system 300 is a bank system that manages deposits to the user. The claim management device 100 acquires deposit data indicating a deposit to the user's account through the bank system 300. Note that in FIG. 1, only one bank system 300 is shown, but this does not mean that there is only one bank system connectable to the claim management device 100. There may be a bank system that manages each account for each user of the claim management device 100. Also, the entity that manages the deposit data is not limited to a bank and may be any person who performs a fund transfer.

[0030] In the billing management system 10, the billing management device 100 acquires billing data from the user terminal 200 and deposit data from the bank system 300. The user performs billing management based on this billing data and deposit data. Also, the billing management device 100 may acquire deposit data for the user through a system other than the bank system 300. For example, when the deposit is made by electronic money, the billing management device 100 may acquire the deposit data by electronic money through the system that manages the electronic money. Note that the deposit data may be acquired by the user terminal 200 and transmitted to the billing management device 100.

[0031] Referring to FIG. 2, each part of the billing management device 100 will be described. The billing management device 100 includes a communication unit 101, a storage unit 102, and a control unit 103. The functions of each part of the billing management device 100 can be realized in the billing management device 100 by using a storage area such as a memory or by the processor executing a program stored in the storage area.

[0032] The communication unit 101 controls communication between the billing management device 100 and the outside including the user terminal 200 and the bank system 300 through the network N.

[0033] The storage unit 102 stores various types of information used in the processing of the billing management device 100. The storage unit 102 includes a user DB (database) 1021, a customer DB 1022, a billing DB 1023, and a deposit DB 1024. Also, the storage unit 102 stores a program that enables the user terminal 200 to operate the processing of the billing management device 100 through the user terminal 200 and a program that causes the user terminal 200 to execute processing on a web browser.

[0034] Referring to FIGS. 3 to 5, the data in the customer DB 1022, the invoice DB 1023, and the payment DB 1024 will be described. The customer data, invoice data, and payment data to be described hereinafter are all data of a certain user. The respective data of the customer DB 1022, the invoice DB 1023, and the payment DB 1024 are associated with and stored for each individual user managed by the user DB 1021, for example, by the user name and user ID.

[0035] Referring to FIG. 3, the customer data stored in the customer DB 1022 will be described. The customer information shown in FIG. 3 has items of "customer code", "customer name", "commission bearer", and "commission amount". In the item of "customer code", an identification code for identifying the customer is stored. In the item of "customer name", the name of the customer is stored. In the item of "commission bearer", the bearer of the commission at the time of payment is stored, for example, as "own company" or "customer". In the item of "commission amount", when the commission bearer is "own company", the commission is stored. When the commission bearer is "customer", as shown by the blank in FIG. 3, it is stored that there is no commission. Alternatively, 0 may be stored as the commission.

[0036] Note that the items of the customer data stored in the customer DB 1022 may have other items than those shown here. For example, the corporate number of the customer or the information of the person in charge of the customer may be stored.

[0037] Referring to FIG. 4, the invoice data stored in the invoice DB 1023 will be described. The invoice information shown in FIG. 4 has items of "customer code", "customer name", "invoice date", and "invoice amount". In the item of "invoice date", the date on which the invoice was issued is stored. In the item of "invoice amount", the invoice amount is stored. The items of the invoice data stored in the invoice DB 1023 may have other items than those shown here. The invoice data may include data of items such as "sales date", "scheduled date", "invoice classification", "outstanding invoice amount", etc.

[0038] Referring to FIG. 5, the payment data stored in the payment DB 1024 will be described. The customer information shown in FIG. 5 has items of "transfer requester name", "payment date", and "payment amount". In the item of "transfer requester name", the name of the person stored in the bank system 300 is stored as the transfer requester. In the item of "payment date", the date on which the payment was made is stored. In the item of "payment amount", the payment amount is stored. The items of the payment data stored in the payment DB 1024 may have other items other than those shown here. The payment data may include data of items such as "payment classification", "bank code", "bank name", "remaining payment amount", etc.

[0039] The control unit 103 controls data acquisition from the bank system 300, data transmission to the user terminal 200, etc. The control unit 103 has a data acquisition unit 1031, a data transmission unit 1032, a program transmission unit 1033, a collation processing unit 1034, and a screen information generation unit 1035.

[0040] The data acquisition unit 1031 acquires the billing data for each user from the user terminal 200. The acquired billing data is stored in the billing DB 1023 for each user. The data acquisition unit 1031 acquires the billing data, for example, by acquiring the billing data from the user's core system or by acquiring a file including the billing data from the user terminal 200. Also, the data acquisition unit 1031 may acquire the billing data by acquiring the billing data included as an attached file in an email sent by the user.

[0041] Also, the data acquisition unit 1031 acquires the payment data for each user from the bank system 300. The data acquisition unit 1031 acquires the account information of the user from the bank system 300 using, for example, a reference API. The acquired payment data is stored in the payment DB 1024 for each user. Note that the data acquisition unit 1031 may acquire the payment data from the user terminal 200.

[0042] The data transmission unit 1032 transmits the user's billing data and payment data to the user terminal 200 in response to an operation from the user terminal 200.

[0043] The program transmission unit 1033 transmits a program to the user terminal 200 that enables the control unit 204, which will be described later, to execute processing on the user terminal 200. The program is transmitted, for example, as a script that operates on a web browser.

[0044] The matching processing unit 1034 performs the batch write-off processing, which will be described later, based on the billing data in the billing DB 1023 and the payment data in the payment DB 1024. The matching processing unit 1034 searches for the billing data corresponding to the payment data, for example, by a search method using a genetic algorithm.

[0045] The screen information generation unit 1035 generates information on the screen to be displayed on the user terminal 200. The generated screen information is transmitted to the user terminal 200 and displayed on the user terminal 200. Note that the screen information is information used when the user terminal 200 displays a screen, and can adopt any format such as HTML format, XML format, text format, etc.

[0046] With reference to FIG. 6, each part of the user terminal 200 will be described. The user terminal 200 includes a communication unit 201, a storage unit 202, a display unit 203, and a control unit 204. The functions of each part of the user terminal 200 can be realized in the user terminal 200 by using a storage area such as a memory or by the processor executing a program stored in the storage area.

[0047] The communication unit 201 controls communication between the user terminal 200 and an external device including the claim management device 100 and the bank system 300 via the network N. The storage unit 202 stores various types of information used for processing in the user terminal 200. The display unit 203 is a device that displays the information processed by the user terminal 200 in a recognizable manner to the user. The display unit 203 is a display of a computer or a tablet terminal. Note that the display unit 203 may be provided as a separate device connectable to the user terminal 200.

[0048] The control unit 204 includes a data acquisition unit 2041, a search request acquisition unit 2042, a threshold acquisition unit 2043, a search unit 2044, a selection information acquisition unit 2045, a result screen generation unit 2046, a designation unit 2047, an extraction unit 2048, and a fee acquisition unit 2049. Each unit of the control unit 204 is realized, for example, by a program transmitted from the claim management device 100 and executed in the web browser of the user terminal 200. The processing of the control unit 204 is executed using the processor of the user terminal 200. Note that each unit of the control unit 204 may be realized by a dedicated application program instead of a general-purpose web browser.

[0049] The data acquisition unit 2041 acquires claim data and deposit data associated with the user from the claim management device 100.

[0050] The search request acquisition unit 2042 acquires an input of a search request by the user through the screen displayed on the display unit 203. The search request acquisition unit 2042 acquires a search request, for example, when a button on the screen is selected by the user. Here, the search request is information in which the user instructs to search for corresponding claim data, which is claim data corresponding to the deposit data, from the claim data. By specifying the corresponding claim data for the deposit data, the write-off of the corresponding claim data becomes possible.

[0051] The threshold acquisition unit 2043 acquires a threshold provided for the difference between the total claim amount obtained by summing the claim amounts of the corresponding claim data and the total payment amount obtained by summing the payment amounts of the payment data. When a search request is acquired, the threshold acquisition unit 2043 causes the display unit 203 to display a screen for acquiring the threshold. The threshold acquisition unit 2043 acquires the threshold by receiving an input from the user through the screen.

[0052] The difference is caused, for example, by a consumption tax error resulting from a difference in the handling of consumption tax between the user and the customer, or a fee error resulting from a fee charged by a bank or the like. The threshold may be acquired by acquiring thresholds for each of the consumption tax error and the fee error. Alternatively, the threshold may be acquired as a single threshold that includes the consumption tax error, the fee error, or other errors.

[0053] Based on the claim data, the payment data, and the threshold, the search unit 2044 searches for claim data for which the difference between the total claim amount and the total payment amount satisfies the threshold as the corresponding claim data. The search unit 2044 performs the search for the corresponding claim data by, for example, a search method using a genetic algorithm.

[0054] The selection information acquisition unit 2045 acquires from the user first selection information indicating the claim data used in the search process among the claim data and second selection information indicating the payment data used in the search process among the payment data. The selection information acquisition unit 2045 causes the display unit 203 to display, for example, a screen including check boxes for each data in accordance with the payment data and the claim data. The selection information acquisition unit 2045 acquires the first selection information or the second selection information based on the input to the check boxes for each data.

[0055] When a plurality of candidates for sets of corresponding claim data are found, the result screen generation unit 2046 causes the display unit 203 to display a screen on which the user can check the plurality of candidates and select any one of the candidates.

[0056] The designated unit 2047 receives an input for the user to select a candidate through a screen where the user can view a plurality of candidates of the corresponding claim data set.

[0057] The extraction unit 2048 extracts repetitive claim data where the claim amounts of each claim data are the same. The extraction unit 2048 performs the extraction of the repetitive claim data, for example, when the search request acquisition unit 2042 receives an input indicating that the repetitive claim data is to be extracted from the user.

[0058] The fee acquisition unit 2049 acquires from the user the amount of the deposit fee associated with each customer. The fee acquisition unit 2049 causes the user to display the management screen of the customer DB 1022 and receives an input of the fee through the management screen. The input fee is stored in the customer DB 1022 in association with the customer.

[0059] With reference to FIG. 7, the write-off process in the claim management system 10 will be described. At the same time, reference will be made to FIGS. 8 to 12 as appropriate for the description. It is assumed that the user has logged in to the cloud service provided by the claim management apparatus 100 through the user terminal 200, and the claim management apparatus 100 is displaying an operation screen.

[0060] In step S701, in response to an operation by the user, a request for a batch write-off screen is transmitted from the user terminal 200 to the claim management apparatus 100.

[0061] In step S702, the screen information generation unit 1035 generates information on the batch write-off screen 800 shown in FIG. 8. When generating the batch write-off screen 800, the screen information generation unit 1035 refers to the claim DB 1023 and the deposit DB 1024 to acquire the claim data and the deposit data associated with the user. Further, the screen information generation unit 1035 refers to the customer DB 1022 to acquire the fee associated with the customer.

[0062] On the batch cancellation screen 800, a batch cancellation button 801 and a matching result column 802 are displayed. In the matching result column 802, the billing data by customer is shown as the billing information, and the payment data by customer is shown as the payment information. In the "quantity" item of the billing information and the payment information, the billing quantity and the payment quantity for each customer are respectively stored.

[0063] In the matching result column 802, an item "match" is provided. In the item "match", information indicating whether the billed amount and the paid amount match is displayed as a result of the matching process by the matching processing unit 1034. In the example of FIG. 8, for the billing data where the "customer name" is Company B, Company C, and Company D, the corresponding payment data is matched, and it is determined that both amounts match. When the batch cancellation button 801 is selected by the user, a request for the cancellation process of the matching billing data and payment data is sent to the billing management device 100.

[0064] In step S703, the screen information generation unit 1035 sends the information of the batch cancellation screen 800 to the user terminal 200.

[0065] In step S704, a request for batch cancellation is sent to the billing management device 100 by the user's selection of the batch cancellation button 801.

[0066] In step S705, the matching processing unit 1034 adds information indicating that it has been cancelled to the billing data and the payment data in the billing DB 1023 and the payment DB 1024. Thereby, it is recorded that the cancellation of the corresponding billing data and payment data has been performed.

[0067] In step S706, the screen information generation unit 1035 generates the information of the batch cancellation screen 800 after batch cancellation. As shown in FIG. 9, on the batch cancellation screen 800 after batch cancellation, information including the billing information and the payment information for which the cancellation is not completed is shown.

[0068] In step S707, the screen information generation unit 1035 transmits the information of the batch cancellation screen 800 after batch cancellation to the user terminal 200.

[0069] In step S708, a request for an individual cancellation screen is transmitted to the claim management apparatus 100 by selection of an individual selection button 901 on the user terminal 200 on which the batch cancellation screen 800 after batch cancellation is displayed.

[0070] In step S709, the screen information generation unit 1035 generates the information of the individual cancellation screen 1000 shown in FIG. 10. The individual cancellation screen 1000 is a screen that displays more detailed claim data and payment data regarding the customer associated with the individual selection button 901.

[0071] In generating the individual cancellation screen 1000, the screen information generation unit 1035 acquires the claim data and payment data associated with the user from the claim DB 1023 and the payment DB 1024.

[0072] On the individual cancellation screen 1000, an individual cancellation button 1001, a claim total display column 1002, a claim information display column 1003, and a payment total display column 1004 are displayed.

[0073] In the claim total display column 1002, information regarding the whole of the individual claim data is shown. In the claim information display column 1003, the individual claim data is shown. In the "selection" item in the claim information display column 1003, a box for selecting whether or not each claim data is to be the target of cancellation is displayed. In FIG. 10, the data in the 1st to 3rd rows and the 5th row and subsequent rows of the claim information display column 1003 are selected as the cancellation targets. The data in the 4th row of the claim information display column 1003 is excluded from the cancellation targets and selected. The state of each box is selected by the user, and the information indicating the selection state is acquired by the selection information acquisition unit 2045.

[0074] In the total deposit display column 1004, information regarding the entirety of individual deposit data is shown. In the deposit information display column 1005, individual deposit data is shown. Regarding the "selection" item in the total deposit display column 1004, it is the same as in the claim information display column 1003.

[0075] In the total deposit display column 1004, a simulation button 10041 is arranged. By the user selecting the simulation button 10041, a search request for exploring the combination of claim data and deposit data is acquired by the user terminal 200.

[0076] In step S710, the program transmission unit 1033 acquires a program for individual write-off processing from the storage unit 102. By the program for individual write-off processing, the processing of each part of the control unit 204 in the user terminal 200 is defined.

[0077] In step S711, the screen information generation unit 1035 and the program transmission unit 1033 transmit the screen information and program of the individual write-off screen 1000 to the user terminal 200.

[0078] In step S712, the user terminal 200 receives a request to search for corresponding claim data, which is the claim data corresponding to the deposit data, through the individual write-off screen 1000. Specifically, the search request acquisition unit 2042 of the user terminal 200 acquires a search request by the user's selection of the simulation button 10041 through the individual write-off screen 1000 displayed on the display unit 203.

[0079] In step S713, as shown in FIG. 11, the threshold acquisition unit 2043 pops up and displays a threshold input screen 1100 on the individual write-off screen 1000. The threshold input screen 1100 has a check button 1101 and a fee error input field 1102 regarding fee error, and a check button 1103 and a consumption tax error input field 1104 regarding consumption tax error.

[0080] The user operates the user terminal 200 to select the check buttons 1101 and 1103 and input values into the handling fee error input field 1102 and the consumption tax error input field 1104. When the "Execute" button on the threshold input screen 1100 is selected by the user, the threshold acquisition unit 2043 acquires the input handling fee error and consumption tax error according to the selection state of the check button 1101. The threshold acquisition unit 2043 acquires the sum of the acquired handling fee error and consumption tax error as the threshold. In FIG. 11, the threshold is 1,050 yen. Note that the check button 1101 may be displayed by screen transition instead of in a pop-up format. Also, information on the amount set in common for all customers may be pre-displayed in the handling fee error input field 1102. This information on the handling fee error is included, for example, in the screen information transmitted from the claim management device 100.

[0081] In step S714, the search unit 2044 searches for corresponding claim data based on the claim data, payment data, and threshold selected as the search target.

[0082] In step S715, as shown in FIG. 12, the search unit 2044 displays the search results on the individual cancellation screen 1000.

[0083] A series of search processes and result displays will be described with reference to FIGS. 10 to 12. In FIG. 10, it is shown that there were payments of "9,560" yen on "2020 / 11 / 02" and "7,559" yen on "2020 / 11 / 09" from a customer whose "remittance requester name" is "A Co., Ltd.". All of these payments are the payment data to be searched. Also, in FIG. 10, the data in the 1st to 3rd rows and the 5th row and subsequent rows of the claim information display column 1003 are selected as the search target.

[0084] Through the search process, claim data corresponding to the total payment amount of "17,119" yen is searched. At this time, the search unit 2044 searches for claim data such that the error between the corresponding claim data and the payment amount is within "1,050" yen. As a result of the search, the claim data in the first row and the fifth row of the claim information display column 1003 is found as the corresponding claim data that satisfies the conditions. For example, since the total of the claim data in the third row and the fifth row of the claim information display column 1003 is "15,000" yen, it does not meet the threshold, and these claim data do not become the corresponding claim data.

[0085] In FIG. 12, the individual write-off screen 1000 is updated so that the searched corresponding claim data is in a selected state. Specifically, the individual write-off screen 1000 is updated so that the selection of claim data other than the corresponding claim data is canceled. Also, the differences within the error range are respectively displayed in the consumption tax error column of the claim total display column 1002, the consumption tax error column of the payment total display column 1004, and the fee column.

[0086] In step S716, in response to the user's selection of the individual write-off button 1001, the user terminal 200 sends a request for individual write-off to the claim management device 100. This request includes information indicating the corresponding claim data and payment data.

[0087] In step S717, the verification processing unit 1034 adds information indicating that it has been written off to the corresponding claim data and payment data in the claim DB 1023 and the payment DB 1024 based on the obtained corresponding claim data and payment data.

[0088] Through the above steps, individual write-off processing is performed on the claim data that could not be written off in the batch write-off processing, and it becomes possible to perform write-off based on partial payment data.

[0089] Another example of the write-off process in the claim management device 100 will be described with reference to FIGS. 13 and 14. FIG. 13 is a diagram showing another procedure of the write-off process in the claim management device 100. FIG. 13 shows the processing after the transmission of the request on the individual write-off screen. The processing from steps S1301, S1302, S1304, and S1306 to S1311 is the same as each processing described after S708 in FIG. 7.

[0090] The write-off process in FIG. 13 is different from the write-off process in FIG. 7 in that it has steps S1303 and S1305.

[0091] In step S1303, the screen information generation unit 1035 acquires information regarding the fee from the customer DB 1022. For example, when Company A is the customer (payer), based on the customer data in FIG. 3, information indicating that the company bears a fee of 440 yen is acquired as the information regarding the fee.

[0092] In step S1305, the screen information generation unit 1035 and the program transmission unit 1033 transmit the screen information of the individual write-off screen 1000, the information regarding the fee, and the program to the user terminal 200.

[0093] FIG. 14 shows the individual write-off screen 1000 and the threshold input screen 1100 when the information regarding the fee is transmitted. In this case, in the registered fee display column 1402 of the threshold input screen 1100, the fee set for each customer is displayed in a state where it is pre-entered based on the information regarding the fee. In FIG. 14, the registered fee "440" of Company A is displayed in the registered fee display column 1402.

[0094] When the check button 1401 is selected, the search unit 2044 searches for the claim data while considering the registered fee. For example, in FIG. 14, the search unit 2044 searches for a combination of claim data that matches "9,560 + 7,559 + 440 = 17,559 yen".

[0095] In addition, by preliminarily displaying the fees for each customer in the registered fee display column 1402, when the fees are stored for each customer, the input burden on the user can be reduced. The user can change the value in the fee error input column 1102 as needed. When the user changes the value, the user terminal 200 may transmit the information on the changed value to the billing management device 100. Based on the information from the user terminal 200, the billing management device 100 may update the information on the fees in the customer DB 1022.

[0096] In addition, in FIG. 14, a check box 1403 corresponding to the display of "Quick Search" is provided. When the check box 1403 is selected, the search unit 2044 sorts the billing data by the billing date and selects the initial candidates for the corresponding billing data based on the billing date. The search unit 2044 performs the search process while using the selected initial candidates. In this case, the corresponding billing data can be discovered in a shorter time.

[0097] Another example of the reconciliation process in the billing management device 100 will be described with reference to FIGS. 15 to 17. FIG. 15 is a diagram showing another procedure of the reconciliation process in the billing management device 100. FIG. 15 shows the processes after the transmission of the request for the individual reconciliation screen. The processes of steps S1501 to S1507, S1510, and S1511 are the same as the respective processes described after S708 in FIG. 7.

[0098] The reconciliation process in FIG. 15 is different from the reconciliation process in FIG. 7 in that it has steps S1508 and S1509.

[0099] In step S1508, when there are a plurality of sets of corresponding billing data, the result screen generation unit 2046 displays the search results on the individual reconciliation screen 1000 so that the user can select them.

[0100] For example, in the billing information display column 1003 of the individual reconciliation screen 1000 shown in FIG. 16, there are two sets of billing data with a total amount of "18,000" yen, namely, the sets in the first row and the fifth row, and the sets in the first row, the sixth row, and the seventh row.

[0101] If search processing is performed in this case, the above two sets can be corresponding claim data. In this case, as shown in FIG. 17, the result screen generation unit 2046 displays, on the individual cancellation screen 1000, a screen including the combination candidate display screen 1700 as the search result screen.

[0102] The corresponding claim data is displayed in a distinguishable state on the combination candidate display screen 1700. Selection buttons 1701 and 1702 are provided on the combination candidate display screen 1700 so as to be able to receive input from the user. The user designates a set of corresponding claim data that the user considers appropriate from a plurality of sets of corresponding claim data displayed separately from each other by selecting the selection buttons 1701 and 1702.

[0103] In step S1509, the designation unit 2047 acquires the selection result by the user based on the input to any of the selection buttons 1701 and 1702. When any of the selection buttons 1701 and 1702 is selected and the confirmation button at the bottom of the combination candidate display screen 1700 is selected, the designation unit 2047 acquires, as the selection result, the claim data corresponding to the selected selection button. For example, the designation unit 2047 acquires, by the selection and confirmation of the selection button 1701, information that the combination of the first line and the fifth line of the claim data has been designated by the user as the corresponding claim data. The subsequent individual cancellation process is performed for the designated corresponding claim data.

[0104] Another example of the cancellation process in the claim management apparatus 100 will be described with reference to FIGS. 18 to 21. FIG. 18 is a diagram showing another procedure of the cancellation process in the claim management apparatus 100. FIG. 18 shows the process after the transmission of the request for the individual cancellation screen. The processes from step S1801 to S1807 and from S1810 to S1812 are the same as the respective processes described after S708 in FIG. 7.

[0105] The cancellation process in FIG. 18 is different from the cancellation process in FIG. 7 in that it has steps S1808 and S1809.

[0106] In step S1808, the extraction unit 2048 acquires an extraction request for claim data that is repeatedly stored and extracts the claim data. For example, assume a case where claim data with a claim amount of "2,000" yen is repeatedly stored as shown in the individual write-off screen 1000 of FIG. 19.

[0107] In this case, as shown in FIG. 20, the extraction unit 2048 acquires an extraction request for claim data (repeated claim data) that is repeatedly stored through the setting button 2001 corresponding to the display "Prioritize repeated claim amounts" on the threshold input screen 1100. The extraction unit 2048 may display the setting button 2001 so that it is included in the threshold input screen 1100, or may display it as another screen.

[0108] In step S1809, the search unit 2044 preferentially searches for corresponding claim data with respect to the claim data that is repeatedly stored. Specifically, the search unit 2044 searches for corresponding claim data such that the claim data that is repeatedly stored is included in the corresponding claim data.

[0109] FIG. 21 shows the individual write-off screen 1000 after the search. In the claim information display column 1003, there are sets with a total claim amount of "18,000" yen, namely, the sets in the first, third, and fifth rows, and the sets in the first to fourth rows and the sixth row.

[0110] As a result of the search unit 2044 preferentially searching for corresponding claim data with respect to the claim data that is repeatedly stored, the sets of claim data in the first to fourth rows and the sixth row that include the claim data with a claim amount of "2,000" yen that is repeatedly stored are displayed as the corresponding claim data. On the other hand, the set including the claim data with a claim amount of "8,000" yen is not regarded as the corresponding claim data. Thereby, by performing the search so that the repeated claim data with a high possibility that the customer will make a lump-sum payment is included in the corresponding claim data, the search for the corresponding claim data can be appropriately performed.

[0111] Another example of the cancellation process in the claim management device 100 will be described with reference to FIG. 22. FIG. 22 is a diagram showing another procedure of the cancellation process in the claim management device 100. In FIG. 22, the processes after the transmission of the request on the individual cancellation screen are shown.

[0112] The processes from step S2201 to S2206 and from S2210 to S2212 are the same as the respective processes described after S708 in FIG. 7. Note that in step S2203, the program transmission unit 1033 acquires a program for managing the individual cancellation screen in the user terminal 200, and it is not necessarily required to acquire a program that enables the search process by the user terminal 200.

[0113] In the process shown in FIG. 22, in step S2207, a search process request and a threshold value are transmitted from the user terminal 200 to the claim management device 100. In step S2208, the collation processing unit 1034 searches for the corresponding claim data. In step S2209, the collation processing unit 1034 transmits the search result to the user terminal 200.

[0114] In this way, the search process may be executed in the user terminal 200 or may be executed in the claim management device 100. Also, for processes other than the search process, processes that do not need to be executed by the control unit 204 in the user terminal 200 can be executed in the claim management device 100.

[0115] The embodiments described above are for facilitating the understanding of the present invention and are not for limiting and interpreting the present invention. Each element included in the embodiments and its conditions, etc. are not limited to those exemplified and can be changed as appropriate. Also, it is possible to partially replace or combine the configurations shown in different embodiments.

Explanation of Reference Numerals

[0116] 10…Claim management system, 100…Claim management device, 101…Communication unit, 102…Memory unit, 103…Control unit, 200, 200a, 200b, 200c…User terminal, 201…Communication unit, 202…Memory unit, 203…Display unit, 204…Control unit, 300…Bank system, 2041…Data acquisition unit, 2042…Search request acquisition unit, 2043…Threshold acquisition unit, 2044…Search unit, 2045…Selection information acquisition unit, 2046…Result screen generation unit, 2047…Designation unit, 2048…Extraction unit, 2049…Fee acquisition unit

Claims

1. A computer is caused to perform: a data acquisition process of acquiring a plurality of claim data including a claim destination and a claim amount and a plurality of payment data including a payment source and a payment amount; a batch offset process of identifying a set of payment data and claim data in which the first total claim amount, which is the total amount of claim amounts of a plurality of claim data for a first claim destination, matches the first total payment amount, which is the total amount of payment amounts of a plurality of payment data from a first payment source corresponding to the first claim destination, and performing offset; after the batch offset process, based on an operation from a user, a screen generation process of generating information of a screen that displays information of a plurality of claim data for a second claim destination and a plurality of payment data from a second payment source corresponding to the second claim destination, which have not been offset by the batch offset process, among the plurality of claim data and the plurality of payment data; a search request acquisition process of acquiring, through the screen, a search request that is information instructing to search for at least one corresponding claim data to be offset, corresponding to at least one payment data selected from the plurality of payment data from the second payment source, from the plurality of claim data for the second claim destination; when the search request is acquired, a first threshold acquisition process of acquiring a first threshold from the user for the difference between the second total claim amount obtained by summing the claim amounts of the at least one corresponding claim data and the second total payment amount obtained by summing the payment amounts of the at least one selected payment data; an individual offset process of identifying the at least one corresponding claim data so that the difference is within the range of the first threshold, and performing offset of a set of the at least one selected payment data and the identified at least one corresponding claim data; A program for causing the above to be executed.

2. The program according to claim 1, wherein the first threshold includes a threshold related to a fee and a threshold related to a consumption tax.

3. The program according to claim 1 or 2, wherein the first threshold acquisition process acquires the first threshold from the user after presenting a predetermined threshold candidate stored in a storage unit of the computer to the user.

4. The program according to any one of claims 1 to 3, in the individual offset process, when there are a plurality of combinations of the at least one corresponding claim data for which the difference is within the range of the first threshold, The computer is caused to generate screen information of a search result screen on which the plurality of combinations are displayed so as to be distinguishable from each other; and acquire, from the user, information for designating one combination among the plurality of combinations through the search result screen. A program for further causing the computer to execute the processes. **Claim 5** A method executed by a computer, the method comprising: acquiring a plurality of claim data including a claimant and a claim amount, and a plurality of payment data including a payer and a payment amount; identifying a set of the payment data and the claim data in which a first total claim amount, which is a total amount of the claim amounts of the plurality of claim data to a first claimant, matches a first total payment amount, which is a total amount of the payment amounts of the plurality of payment data from a first payer corresponding to the first claimant, and performing a batch write-off; after the batch write-off, generating screen information of a screen for displaying information on a plurality of claim data to a second claimant, which has not been written off by the batch write-off, among the plurality of claim data and the plurality of payment data, and information on a plurality of payment data from a second payer corresponding to the second claimant, based on an operation by the user; acquiring, through the screen, a search request which is information for instructing to search for at least one corresponding claim data to be written off, corresponding to at least one payment data selected from the plurality of payment data from the second payer, from the plurality of claim data to the second claimant; when the search request is acquired, acquiring, from the user, a first threshold value for a difference between a second total claim amount obtained by summing the claim amounts of the at least one corresponding claim data and a second total payment amount obtained by summing the payment amounts of the at least one selected payment data; and identifying the at least one corresponding claim data so that the difference is within the range of the first threshold value, and performing an individual write-off of a set of the at least one selected payment data and the identified at least one corresponding claim data. A claim management method including the above. **Claim 6** A data acquisition unit that acquires a plurality of claim data including a claimant and a claim amount, and a plurality of payment data including a payer and a payment amount. Among the plurality of claim data and the plurality of payment data, a batch write-off unit that identifies a set of claim data and payment data in which a first total claim amount, which is the total amount of claim amounts of the plurality of claim data to a first payee, matches a first total payment amount, which is the total amount of payment amounts of the plurality of payment data from a first payer corresponding to the first payee, and performs batch write-off; After the batch write-off, based on an operation from a user, a screen information generation unit that generates information on a screen that displays information on a plurality of claim data to a second payee and a plurality of payment data from a second payer corresponding to the second payee, which were not written off by the batch write-off, among the plurality of claim data and the plurality of payment data; A search request acquisition unit that acquires, through the screen, a search request that is information instructing to search for at least one corresponding claim data to be written off, corresponding to at least one payment data selected from the plurality of payment data from the second payer, from the plurality of claim data to the second payee; When the search request is acquired, a first threshold value acquisition unit that acquires a first threshold value for a difference between a second total claim amount obtained by summing the claim amounts of the at least one corresponding claim data and a second total payment amount obtained by summing the payment amounts of the at least one selected payment data from a user; A claim management apparatus comprising: an individual write-off processing unit that identifies the at least one corresponding claim data so that the difference is within the range of the first threshold value, and performs individual write-off of a set of the at least one selected payment data and the identified at least one corresponding claim data.

7. A server, A data transmission unit that transmits a plurality of claim data including claim amounts and a plurality of payment data including payment amounts to a terminal capable of communicating with the server; A program transmitted to the terminal, On the terminal, A data acquisition process of acquiring a plurality of claim data including a payee and a claim amount and a plurality of payment data including a payer and a payment amount; A batch write-off process of identifying a set of claim data and payment data in which a first total claim amount, which is the total amount of claim amounts of the plurality of claim data to a first payee, matches a first total payment amount, which is the total amount of payment amounts of the plurality of payment data from a first payer corresponding to the first payee, and performing write-off; After the above batch write-off process, based on an operation from the user, among the plurality of claim data and the plurality of payment data, information on a screen for displaying information on the plurality of claim data to a second payee and the plurality of payment data from a second payer corresponding to the second payee, which were not written off by the batch write-off process, is generated by a screen generation process; A search request acquisition process for acquiring, through the screen, a search request that is information instructing to search for at least one corresponding claim data to be written off, corresponding to at least one payment data selected from the plurality of payment data from the second payer, from the plurality of claim data to the second payee; When the search request is acquired, a first threshold acquisition process for acquiring from the user a first threshold for the difference between a second total claim amount obtained by summing the claim amounts of the at least one corresponding claim data and a second total payment amount obtained by summing the payment amounts of the at least one selected payment data; An individual write-off process for specifying the at least one corresponding claim data so that the difference is within the range of the first threshold, and performing a write-off of a set of the at least one selected payment data and the specified at least one corresponding claim data; A program transmission unit that transmits, to the terminal, a program for causing the above to be executed; A server comprising the above.

Images