JP7064540B2 - Substitute payment information management device, substitute payment information management method, and substitute payment information management program - Google Patents

Description

The present invention relates to a substitute payment information management device, a substitute payment information management method, and a substitute payment information management program.

Patent Document 1 describes that when a claim arising from a seller is handed over, the price is transferred to a financial institution account designated by the seller. In this way, the acquisition of the original claim held by the creditor (seller) by a third party is called subrogation repayment, and the third party incurs a reimbursement claim.

Japanese Patent No. 6674578

Subrogation repayment occurs not only in the scene of selling goods but also in the scene of leasing real estate. The lessor of a real estate property (for example, the lessor of real estate or its management company) receives a request from the lessor or an accident report when the lessee has a delinquency (also called an "accident" in the field). , The rent guarantee company of the lessee (hereinafter, also referred to simply as "guarantee company") may make a substitute payment. Such subrogation payments are made based on a rent guarantee contract with the real estate lessor or its management company.

If a substitute payment is made, the lessee must pay the substitute payment to the guarantee company. However, the lessee often pays the lessor without doing so. The reason is that the account to which the rent is usually paid (that is, the account designated by the management company) is used for the transfer. When such a situation occurs, the lessor will receive the deposit of the substitute payment from the guarantee company and the deposit paid by the lessee (duplicate deposit).

In the event of a double deposit or when such a situation is about to occur, the management company should contact the guarantee company and inform them that the substitute payment is no longer required (information that the substitute payment is unnecessary). become. Here, at the stage where the payment of the substitute payment has not been confirmed, it is possible to take measures such as withdrawing the request for the substitute payment. On the other hand, if the substitute payment has been paid, the income and expenditure can be matched by refunding the substitute payment instead of withdrawing the request for the substitute payment.

On the other hand, the guarantee company often manages that reimbursement claims against the lessee will be generated when the request for subrogation payment is received. Therefore, the guarantee company manages both the payment (debt) of the substitute payment to the management company and the receivables (credit) to the lessee, but obtains the information that does not require the substitute payment from the management company. For the first time, new management efforts will be required depending on what to do with debt and receivables. If an employee manually implements such new management effort, one of the debt or the receivable will not be cleared, and as a result, for example, if the receivable is not cleared, the subrogation payment to the lessor will be made. It may notify (reminder) the repayment. Here, as a situation peculiar to this industry, the guarantor company urges the lessee to pay the rent promptly (as the person himself / herself) even though he / she has been delinquent. Efforts are required to avoid the troubles between the three parties (trouble between the lessee and the guarantee company or the trouble between the lessee and the management company) that occur in the above, and to keep the lessee in a good mood. Therefore, as a guarantee company, if the substitute payment is no longer necessary, especially if the management company makes a duplicate payment even if the substitute payment has been paid, the claim to the lessee will be promptly and accurately made. It is required to cancel.

The present invention has been made in view of the above-mentioned problems (requests), and even when subrogation payment becomes unnecessary, it is possible to accurately manage both debts and receivables without any trouble. It is an object of the present invention to provide a subrogation payment information management device, a subrogation payment information management method, and a subrogation payment information management program that can be performed.

In order to solve the above-mentioned problems and achieve the object, the substitute payment information management device according to the present invention is a substitute payment information management device provided with a control unit for managing information related to the substitute payment. The control unit updates the payment management data updating means for updating the payment management data regarding the payment status of the substitute payment based on the substitute payment unnecessary information, and the claim management data regarding the claims that may be generated by the substitute payment based on the substitute payment unnecessary information. It is characterized by having a means for updating credit management data.

Further, in the substitute payment information management device according to the present invention, the payment management data updating means generates payment schedule application data for applying the substitute payment before payment based on the substitute payment unnecessary information. The payment management data is updated, and the claim management data updating means generates the claim clearing data for clearing the claim that was scheduled to be generated by the substitute payment based on the substitute payment unnecessary information. It is characterized by updating the credit management data.

Further, in the subrogation payment information management device according to the present invention, when the payment management data updating means has a plurality of subrogation payments before payment, the payment schedule application data is the payment schedule amount of the plurality of subrogation payments. It is characterized by generating payment schedule application data containing information about the total amount.

Furthermore, in the subrogation payment information management device according to the present invention, the payment management data updating means generates payment schedule application data including information on the total amount of the payment schedule amount of the plurality of subrogation payments for each subrogation payment requester. It is characterized by doing.

Further, in the subrogation payment information management device according to the present invention, the control unit generates billing data based on the subrogation payment unnecessary information to generate billing data regarding the billing to the subrogation payment requester according to the subrogation payment after payment. It is characterized by further including means.

Further, in the substitute payment information management device according to the present invention, the substitute payment is the substitute payment related to the rent guarantee contract with the real estate lessor or the management company thereof, and the substitute payment unnecessary information is the real estate lessor. Or, it is characterized by information on duplicate payments from the lessee from the management company.

Further, the substitute payment information management method according to the present invention is a substitute payment information management method for managing information related to substitute payment, which is executed in an information processing apparatus provided with a control unit, and is executed by the control unit. The payment management data update step for updating the payment management data regarding the payment status of the substitute payment based on the substitute payment unnecessary information, and the claim for updating the claim management data regarding the claims that may be generated by the substitute payment based on the substitute payment unnecessary information. It is characterized by including a management data update step.

Further, the substitute payment information management program according to the present invention is a substitute payment information management program for managing information related to substitute payment, which is executed in an information processing apparatus provided with a control unit, and is executed by the control unit. To update the payment management data update step for updating the payment management data regarding the payment status of the substitute payment based on the substitute payment unnecessary information, and to update the claim management data regarding the receivables that may be generated by the substitute payment based on the substitute payment unnecessary information. It is characterized by including a credit management data update step.

According to the present invention, even when subrogation payment becomes unnecessary, it is possible to accurately manage both debts and receivables without any trouble.

FIG. 1 is a block diagram showing an example of a configuration of a substitute payment information management system including a substitute payment information management device according to an embodiment of the present invention. FIG. 2 is a flowchart showing a processing procedure of the substitute payment information management method executed by the substitute payment information management device 100 in the substitute payment information management system 1000 of FIG. FIG. 3 is a diagram schematically showing a configuration example of subrogation payment request data that can be received in step S210 of FIG. FIG. 4 is a diagram schematically showing a configuration example of payment schedule data generated in step S220 of FIG. FIG. 5 is a diagram schematically showing a configuration example of the bond data generated in step S230 of FIG. FIG. 6 is a diagram schematically showing a configuration example of duplicate deposit data generated in step S250 of FIG. FIG. 7 is a flowchart of a subroutine showing details of the duplicate deposit process in step S270 of FIG. FIG. 8 is a diagram schematically showing the configuration of payment management data including payment schedule application data generated in step S274 of FIG. 7. FIG. 9 is a diagram schematically showing the structure of the claim management data including the claim clearing data generated in step S275 of FIG. 7. FIG. 10 is a diagram schematically showing the structure of billing data generated in step S277 of FIG. 7. FIG. 11 is a diagram showing a state in which a record of receivables clearing data is added to the receivables management data shown in FIG. 9 for the receivables data that are not subject to the duplicate deposit processing.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. Constitution]
An example of the configuration of the substitute payment information management system including the substitute payment information management device according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of a configuration of a substitute payment information management system including a substitute payment information management device according to an embodiment of the present invention.

The substitute payment information management system 1000 shown in FIG. 1 includes a substitute payment information management device 100 as an information processing device, a server 200, and a network 300 for communicably connecting the substitute payment information management device 100 and the server 200. There is.

The substitute payment information management device 100 is an information processing device for managing information related to the substitute payment, and is composed of, for example, a commercially available desktop personal computer. One subrogation payment information management device 100 is installed in, for example, a department (for example, an accounting department) that manages debts and receivables based on subrogation payment in a rent guarantee company. The substitute payment information management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, tablet personal computer, or the like. It may be a portable information processing device. Further, a plurality of subrogation payment information management devices 100 may be installed in the subrogation payment information management system 1000, and one subrogation payment information can be obtained by synchronizing between the plurality of subrogation payment information management devices 100. It may function as a management device 100.

The subrogation payment information management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the subrogation payment information management device 100 is connected so as to be communicable via an arbitrary communication path.

The communication interface unit 104 connects the substitute payment information management device 100 to the network 300 so as to be communicable via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of connecting the substitute payment information management device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like. Therefore, the communication interface unit 104 receives information and the like from other information processing devices (for example, information processing devices of the lessor (management company) and the trading bank) via the network 300 or via the network 300 and the server 200. In addition to being able to do so, it is also possible to output predetermined information to a predetermined information processing device (for example, an information processing device of a lessor (management company) or a lessee).

Various databases, tables, files, and the like are stored in the storage unit 106. A computer program (including the program of the present invention) for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded in the storage unit 106. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) / ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used. Further, various data used for carrying out the program of the present invention are stored in the storage unit 106 so that they can be written / read.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). In addition to the keyboard, mouse, and microphone, the input device 112 can use a monitor that realizes a pointing device function in cooperation with the mouse.

The control unit 102 is a CPU or the like that comprehensively controls the substitute payment information management device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

Further, the configuration of the storage unit 106 and the control unit 102 will be described in detail with reference to FIG.

As shown in FIG. 1, the storage unit 106 includes a substitute payment unnecessary information storage area 106a, a payment management data storage area 106b, a credit management data storage area 106c, and a billing data storage area 106d. Further, the storage unit 106 may include other masters and data storage areas.

Substitution payment unnecessary information storage area 106a, payment management data storage area 106b, claim management data storage area 106c, billing data storage area 106d store substitute payment unnecessary information, payment management data, claim management data, and billing data, respectively. It is an area for this purpose, and each data is held so that it can be output as needed.

As shown in FIG. 1, the control unit 102 includes a plurality of modules. In the example shown in FIG. 1, the control unit 102 includes a payment management data update unit 102a, a claim management data update unit 102b, and a billing data generation unit 102c.

The payment management data update unit 102a is a module that functions as a payment management data update means for updating payment management data related to the payment status of subrogation payment based on the substitute payment unnecessary information. The claim management data update unit is a module that functions as a claim management data update means for updating claim management data relating to claims that may be generated by substitute payment based on the above-mentioned information that does not require subrogation payment. The billing data generation unit 102c is a module that functions as a function of generating billing data relating to a billing to a subrogation payment requester according to the subrogation payment after payment based on the subrogation payment unnecessary information. The functions of each part include the functions for realizing the processing contents described later.

[2. process]
Next, the substitute payment information management method executed in the substitute payment information management system 1000 shown in FIG. 1 will be exemplified.

FIG. 2 is a flowchart showing a processing procedure of the substitute payment information management method executed by the substitute payment information management device 100 in the substitute payment information management system 1000 of FIG. Generally, the process shown in FIG. 2 updates the payment management data when the information that the subrogation payment is unnecessary (information that the subrogation payment is unnecessary) is acquired when managing the information related to the subrogation payment. , The claim management data is updated, and most of this processing is executed by the control unit 102 of the subrogation payment information management device 100. In the following, the substitute payment is the substitute payment related to the rent guarantee contract with the real estate lessor or its management company, and the information that does not require the substitute payment is the information regarding the duplicate payment from the lessee from the real estate management company. This will be described with an example of the case where.

In FIG. 2, first, in step S210, it waits for the substitute payment request information to be acquired. Subrogation payment requests are usually made by the lessor or its management company to the lessee's rent guarantee company when the lessee is in arrears. The subrogation payment request information is not limited to an explicit request for subrogation payment, but may be a notification that the lessee has a delinquent payment (accident), or a subrogation payment including a list of the lessee who has been delinquent. It may be the reception of request data or the like. FIG. 3 is a diagram schematically showing a configuration example of subrogation payment request data that can be received in step S210 of FIG. As shown in FIG. 3, the substitute payment request data includes information for identifying the lessee who has been delinquent (for example, the contract key and the contractor's name), information on the substitute payment request amount, and information on the billing month. Is preferable. The subrogation payment request amount is usually the same as the delinquent amount. Then, when the substitute payment request information is acquired (Yes in step S210), the process proceeds to step S220.

In step S220, payment schedule data in a predetermined format is generated based on the subrogation payment request information acquired in step S210. The payment schedule data generated here is payment schedule data related to the payment amount corresponding to the subrogation payment request amount. The generated payment schedule data is saved as a new record in the payment management data. If the subrogation payment request information acquired in step S210 conforms to the format of the payment schedule data, it may be used as it is or after being arbitrarily processed. Further, when there are a plurality of lessees (contractors) who have been delinquent in the substitute payment request information, it is preferable to calculate the total amount of the substitute payment request amount and generate one payment schedule data.

FIG. 4 is a diagram schematically showing a configuration example of payment schedule data generated in step S220 of FIG.

The payment schedule data shown in FIG. 4 is created according to the substitute payment request data shown in FIG. 3, and a plurality of contractors are combined into one. As shown in FIG. 4, the payment schedule data includes information for specifying the payment destination (that is, the subrogation payment request source) (for example, the management company code and the management company name), information on the payment amount, and information on the payment date. include. The payment date may be the payment month if it is managed monthly.

Subsequently, in step S230, the claim data in a predetermined format is generated based on the substitute payment request information acquired in step S210. The claim data generated here is the claim data related to the reimbursement claim acquired based on the subrogation repayment request. The generated bond data is stored as a new record in the bond management data. If the substitute payment request information acquired in step S210 conforms to the format of the claim data, it may be used as it is or after being arbitrarily processed.

FIG. 5 is a diagram schematically showing a configuration example of the bond data generated in step S230 of FIG.

The claim data shown in FIG. 5 is created according to the substitute payment request data shown in FIG. As shown in FIG. 5, the claim data includes information for identifying the lessee who has been delinquent (for example, the contract key and the contractor's name), information on the amount of receivables, and information on the number of months of delinquency. The amount of receivables is usually the same as the amount of delinquency. Here, the reimbursement claim is a claim acquired based on a substitute repayment request, and is preferably managed as being generated by the completion of repayment. Therefore, as shown in FIG. 5, it is preferable that the claim data further includes information regarding the reimbursement claim occurrence date. The reimbursement claim generation date may be the reimbursement receivable generation month when it is managed monthly. The claim data may include a flag regarding the presence or absence of repayment completion or a flag regarding the presence or absence of the reimbursement claim, instead of the information regarding the date of occurrence of the reimbursement claim.

In steps S210 to S230 described above, when the subrogation payment request information is acquired, the payment schedule data (data related to the debt) and the bond data are automatically generated, and the payment management data and the bond management data are updated. It will be. The generated payment schedule data and receivable data are configured to be able to accept arbitrary editing (correction or processing) by the user.

After that, in step S240, it is determined whether or not the duplicate deposit information has been acquired. Duplicate deposit means that the lessee deposits the delinquent amount related to the substitute payment request (regardless of whether the guarantee company has deposited the payment amount) to the management company that is the lessor. Therefore, the duplicate deposit information corresponds to the information that does not require subrogation payment for the guarantee company. Duplicate deposit information is not limited to explicit notification of duplicate deposits, but may be notification that there was a deposit from a lessee who was delinquent, or duplicates including a list of lessees who had duplicate deposits. It may be the reception of payment report data or the like. Then, if the duplicate deposit information is not acquired (No in step S240), the process proceeds to step S280 described later, while if the duplicate deposit information is acquired (Yes in step S240), the process proceeds to step S250. ..

In step S250, duplicate deposit data in a predetermined format is generated based on the duplicate deposit information acquired in step S240. The duplicate deposit data generated here is data related to the duplicate deposit amount. If the duplicate deposit information acquired in step S240 conforms to the format of the duplicate deposit data, it may be used as it is or after being arbitrarily processed. FIG. 6 is a diagram schematically showing a configuration example of duplicate deposit data generated in step S250 of FIG. As shown in FIG. 6, the duplicate deposit data may include information identifying the lessee who made the duplicate deposit (for example, the contract key and the contractor's name), information on the duplicate deposit amount, and information on the deposit month. preferable. The amount of duplicate deposits is usually the same as the amount of delinquency. As shown in FIG. 6, the duplicate deposit data preferably includes information that identifies the payment request source (that is, the management company).

Then, in step S260, it is determined whether or not to start the duplicate deposit processing. Details of the duplicate deposit processing will be described later in step S270. The start of this duplicate deposit process can be executed at any time, for example, it is performed at a predetermined time on a daily basis, but it may be performed monthly instead, and the duplicate deposit process is performed by the user. It may be started based on the instruction of. If the duplicate deposit process is not started (No in step S260), the process returns to step S210 and waits for the acquisition of the substitute payment request information and the acquisition of the duplicate deposit information. On the other hand, when starting the duplicate deposit process, the process proceeds to step S270.

FIG. 7 is a flowchart of a subroutine showing details of the duplicate deposit process in step S270 of FIG.

In the duplicate deposit process of step S270, first, in step S271, the duplicate deposit data generated in step S260 is read out. Subsequently, in step S272, one substitute payment request source (for example, "Kyobashi real estate") is specified from the duplicate deposit data read in step S271.

Then, in step S273, it is determined whether or not there is a record for the amount for which the subrogation payment has not been paid (record for the subrogation payment unpaid portion) for the duplicate payment data regarding the specified subrogation payment requesting source. There may be one record or a plurality of records for which the subrogation payment has not been paid.

Whether or not the subrogation payment has been completed can be determined, for example, as follows. First, based on the information (for example, contract key and contractor name) that identifies the lessee who had the duplicate payment included in the duplicate payment data (Fig. 6), refer to the credit management data (Fig. 5) and delinquent payment. Determines if there is a record that matches the information that identifies the lessee (eg, contract key and contractor name), followed by payment management data (Figure) based on the information that identifies the lessee that matched. With reference to 4), it is determined whether or not the payment date (scheduled payment date) has passed in the corresponding record. Instead, if the date of occurrence of the reimbursement claim or its flag is managed in the claim management data (Fig. 5), information indicating that the substitute payment has not been paid should be obtained from this information. You may do it. The method of discrimination is not limited to the above example, and any method can be adopted.

Then, as a result of the determination in step S273, if there is a substitute payment unpaid portion, the process proceeds to the application process of steps S274 to S275, while if there is no substitute payment unpaid portion, the application process of steps S274 to S275 is performed. Is skipped and the process proceeds to step S276.

If there is an unpaid subrogation payment (Yes in step S273), first, in step S274, payment schedule application data is generated. The payment schedule application data generated here is payment schedule application data related to the amount of the payment amount corresponding to the amount of the subrogated payment unpaid amount with a negative sign. The generated payment schedule application data is saved as a new record in the payment management data. If there are multiple lessees (contractors) with duplicate payments (that is, if there are multiple records for unpaid subrogation payments), the total amount of payments with a negative sign is added. It is preferable to calculate and generate one payment schedule application data.

FIG. 8 is a diagram schematically showing the configuration of payment management data including payment schedule application data generated in step S274 of FIG. 7. The payment management data shown in FIG. 8 is a payment schedule cancellation including information on the amount of the payment management data shown in FIG. 4, as a result of the processing of step S274, in which the total of the duplicate deposit amounts in FIG. Indicates that one record of the included data has been added. In this way, by adding the payment schedule application data to the payment management data, it is possible to delete all or part of the substitute payment amount included in the existing payment schedule data.

In the following step S275, the receivable data is cleared in the same manner as the clearing of the payment schedule data in step S274. Specifically, receivables clearing data is generated. The receivables clearing data generated here is receivables clearing data relating to the amount of the reimbursement receivables with a negative sign. The generated receivables clearing data is stored as a new record in the receivables management data. It is preferable to manage the claim data that is paired with the claim clearing data by using, for example, a flag indicating the dunning status so that the dunning based on the reimbursement claim is not performed.

FIG. 9 is a diagram schematically showing the structure of the claim management data including the claim clearing data generated in step S275 of FIG. 7. The bond management data shown in FIG. 9 is the bond clearing data including information on the amount of the duplicate deposit amount shown in FIG. 6 with a negative sign as a result of the processing of step S275 with respect to the bond management data shown in FIG. It shows the state where two records have been added. In this way, by adding the claim clearing data to the claim management data, it is possible to clear all or part of the reimbursement claim amount included in the existing claim data. As shown in FIG. 9, when there is receivable data that is not the target of the receivables clearing data, it is preferable to manage the date of occurrence of the reimbursement receivables or its flag, and on the other hand, it is the target of the receivables clearing data. It is preferable that the claim data is managed according to a preset method such as changing the date of occurrence of the reimbursement claim or its flag to Null. Then, the process proceeds to step S276.

In step S276, it is determined whether or not there is a record for which the subrogation payment has been paid (a record for the subrogation payment has been completed). Since this discrimination method is the same as the discrimination method in step S273, the description thereof will be omitted. Subrogation payment The number of paid records may be one or multiple. As a result of the determination in step S276, if there is a substitute payment paid amount, the process proceeds to the application process of step S277, while if there is no substitute payment payment amount, the application process of step S277 is skipped. , Step S278.

Subrogation payment If there is a paid portion (Yes in step S276), in step S277, billing data is generated. The billing data generated here is billing data including a billing amount information (credit) equal to the payment amount of the paid subrogation payment.

FIG. 10 is a diagram schematically showing the structure of billing data generated in step S277 of FIG. 7. In the billing data shown in FIG. 10, of the total of the duplicate deposit amounts included in the duplicate deposit data shown in FIG. 6, the total payment amount of the subrogated payment has been 150,000 yen, which is the same amount. Is included as billing amount information. The billing data generated in this way is used for billing (refund request) to the management company of the substitute payment requesting source specified in step S272. The reason why the billing data is generated when the subrogation payment has been paid is that the management company has already received the payment from both the lessee who was delinquent and the guarantee company. This is because by accepting refunds from the management company (treating it as if there was no subrogation payment request) and canceling the reimbursement claim against the lessee, troubles that may occur with the lessee can be prevented. If there are multiple lessees (contractors) with duplicate payments (that is, if there are multiple records for which the substitute payment has been made), the total amount of payment is calculated and one billing data is provided. It is preferable to generate. If there is no subrogation payment payment, billing data with zero billing amount information or Null may be generated, whereby a record of completion of duplicate payment processing on the day may be left. Then, the process proceeds to step S278.

After that, in step S278, it is determined whether or not there is another substitute payment request source for the duplicate deposit data read in step S271. As a result of this determination, if there is another subrogation payment request source (Yes in step S278), the process returns to step S272, one subrogation payment request source is specified, and the series of processes of steps S274 to S277 described above is performed. To execute. On the other hand, if there is no other subrogation payment request source, it is determined that the processing for all the duplicate deposit data has been completed, the processing shown in FIG. 7 is completed, the process returns to the processing shown in FIG. 2, and the step is performed. Proceed to the process of S280.

In step S280, it is determined whether or not the remaining claims have been collected. The remaining receivables correspond to the receivables (receivables to the contractor B) that are not subject to the double deposit processing shown in FIG. 9 and the receivables (refunds) to the management company related to the billing data shown in FIG. As a result of the determination, if the collection has not been made (No in step S280), the process returns to step S240 in order to wait for the acquisition of the duplicate deposit information. On the other hand, if these receivables are collected (Yes in step S280), appropriate application data is created (step S290). The created application data is added as a new record to the payment management data, the receivables management data, and the billing data as needed. For example, when the lessee makes a deposit in response to a reminder based on the receivables, the receivables clearing data is generated and added as a new record (see FIG. 11). As a result, all income and expenditures will be the same for the repayment amount requested for subrogation repayment. Then, this process is completed.

As described in detail above, according to the series of processes of the subrogation payment information management method shown in FIG. 2, when managing the information related to the subrogation payment, the payment management regarding the payment status of the subrogation payment is based on the information that does not require the subrogation payment. The data is updated (step S274) (payment management data updating means), and the claim management data relating to the claims that may be generated by the subrogation payment is updated based on the subrogation payment unnecessary information (step S275) (credit management data updating means). ). Specifically, the payment management data is updated and the payment management data is updated by generating payment schedule application data for applying the subrogation payment before payment based on the subrogation payment unnecessary information (step S274). Based on the subrogation repayment unnecessary information, the claim management data is updated by generating the claim clearing data for clearing the claim that was scheduled to be generated by the subrogation repayment (step S275). As a result, even when subrogation payment becomes unnecessary, both debt and receivable can be accurately managed without the user's trouble. In addition, as a result of reducing the user's labor and realizing high-speed processing, the time lag after acquiring the substitute payment unnecessary information is shortened, so that troubles with the user can be less likely to occur.

Further, according to the process of FIG. 2, when there are a plurality of substitute payments before payment, the payment schedule application data including information on the total amount of the payment schedule payments of the plurality of substitute payments is used as the payment schedule application data. Generated (steps S271, S274). Since batch processing is possible in this way, debt can be managed collectively. In particular, it is effective when the number of properties to be managed is large or when there are many lessees who tend to be delinquent, and the time and effort of the user can be significantly reduced.

Further, according to the process of FIG. 2, payment schedule application data including information on the total amount of the payment schedule amount of the plurality of subrogation payments is generated for each subrogation payment request source (steps S271, S272, S274). As a result, it is possible to accurately manage the debt for each subrogation repayment requester.

Further, according to the process of FIG. 2, based on the subrogation payment unnecessary information, billing data regarding the billing to the subrogation payment requester according to the subrogation payment after payment is generated (step S277) (billing data generation means). .. This makes it possible to avoid troubles with the user.

Further, according to the process of FIG. 2, the substitute payment is the substitute payment related to the rent guarantee contract with the real estate lessor or its management company, and the substitute payment unnecessary information is the real estate lessor or its management. Information about duplicate deposits from the lessee from the company. As described above, the present invention is particularly effective in the technical field in which debts and receivables should be accurately managed in a contract between three companies.

In the above-described embodiment, the case of generating the clearing data has been described as an example of updating the payment management data and the credit management data, but instead of generating the clearing data, the existing payment to be the target is described. Scheduled data or bond data may be deleted. Further, regarding the claim management data, an example in which the date of occurrence of the reimbursement claim or its flag is used has been described with reference to FIGS. 5, 9, and 11, but the claim management data does not have to include such information. .. Further, the duplicate deposit data as shown in FIG. 6 does not have to include the information if the payment request source can be specified.

[3. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed may be performed manually, or all the processes described as being performed manually may be performed. Alternatively, a part can be automatically performed by a known method.

In addition, processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in this specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the substitute payment information management device 100 and the substitute payment information management system 1000, each component shown in the figure is functional and conceptual, and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the subrogation payment information management device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the substitute payment information is required. It is read mechanically by the management device 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the substitute payment information management device 100 via an arbitrary network (for example, network 300), and all or a part thereof may be stored as needed. It is also possible to download.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Probe Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disc), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium". Therefore, a recording medium containing a program for executing the processing described in the present specification also constitutes the present invention.

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for specific configurations and reading procedures for reading the recording medium in each apparatus shown in the embodiment, installation procedures after reading, and the like.

Various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the substitute payment information management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which an arbitrary peripheral device is connected. Further, the substitute payment information management device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present specification on the device.

Furthermore, the specific form of distribution / integration of the device is not limited to that shown in the figure, and all or part of the device may be functionally or physically in any unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is particularly useful in managing information regarding subrogation payments, especially when there are duplicate deposits.

100 Substitute payment information management device 102 Control unit 102a Payment management data update unit 102b Claim management data update unit 102c Billing data generation unit 104 Communication interface unit 106 Storage unit 106a Substitution payment unnecessary information storage area 106b Payment management data storage area 106c Credit management data Storage area 106d Billing data storage area 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network 1000 Substitute payment information management system

Claims (8)

It is a substitute payment information management device equipped with a control unit for managing information related to substitute payment.
The control unit
Payment management data update means for updating payment management data related to the payment status of subrogation payment based on information that does not require subrogation payment, and
A substitute repayment information management device comprising: a claim management data updating means for updating the claim management data relating to the claims that may be generated by the substitute repayment based on the substitute repayment unnecessary information. The payment management data update means
The payment management data is updated by generating payment schedule application data for canceling the subrogation payment before payment based on the subrogation payment unnecessary information.
The means for updating the credit management data is
The first aspect of claim 1, wherein the claim management data is updated by generating the claim clearing data for clearing the claim that was scheduled to be generated by the substitute payment based on the substitute payment unnecessary information. Substitute payment information management device. The payment management data update means
Claim 2 is characterized in that, when there are a plurality of subrogation payments before payment, the payment schedule application data including information on the total amount of the payment schedule amounts of the plurality of subrogation payments is generated as the payment schedule application data. Subrogation payment information management device described in. The payment management data update means
The subrogation payment information management device according to claim 3, wherein payment schedule application data including information on the total amount of the payment schedule of the plurality of subrogation payments is generated for each subrogation payment request source. The control unit
3 . _ The subrogation payment information management device according to any one of the items. The subrogation payment is a subrogation payment related to a rent guarantee contract with the real estate lessor or its management company.
The subrogation payment unnecessary information is information regarding duplicate payments from the lessor of the real estate or the lessee from the management company thereof.
The substitute payment information management device according to any one of claims 1 to 5. It is a subrogation payment information management method for managing information related to subrogation payment, which is executed in an information processing device equipped with a control unit.
Executed in the control unit,
Payment management data update step to update payment management data related to payment status of subrogation payment based on subrogation payment unnecessary information,
A method for managing subrogation payment information, which comprises a receivables management data update step for updating receivables management data related to receivables that may be generated by subrogation repayment based on the subrogation repayment unnecessary information. A subrogation payment information management program for managing information related to subrogation payment, which is executed in an information processing device equipped with a control unit.
To be executed in the control unit
Payment management data update step to update payment management data related to payment status of subrogation payment based on subrogation payment unnecessary information,
A subrogation payment information management program comprising a receivables management data update step for updating receivables management data related to receivables that may be generated by subrogation repayment based on the subrogation repayment unnecessary information.

Images