Rental management device, rental management method, and rental management program
The rental management device and method address the issue of overpaid rent by creating data to facilitate prompt settlement, ensuring efficient rent recovery from lessors when lessees cancel contracts.
Patent Information
- Application Number
- JP2023220046
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-12-26
- Publication Date
- 2025-07-08
AI Technical Summary
In rental management systems, when a lessee terminates a rental contract and moves out, the rental management company may overpay the lessor, leading to a need for prompt settlement of the overpaid rent.
A rental management device and method that includes creating payment request data, collection schedule data, and subtraction request data based on rental contract and cancellation information to facilitate prompt settlement of overpaid rent.
Enables prompt settlement of overpaid rent to the lessor when a lessee cancels the rental contract, simplifying the remittance calculation process and reducing waste.
Smart Images

Figure 2025102537000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a rental management device, a rental management method, and a rental management program.
Background Art
[0002] In a rental management system, a rental management company borrows rental properties owned by a lessor (landlord) from the lessor and rents the rental properties to lessees with whom rental contracts are concluded. The rental management company collects rent from the lessees and pays the collected amount to the lessor. As an application related to such rental management, for example, there is one described in Patent Document 1.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] In a rental management system, a rental management company concludes a rental contract with a lessor and a lessee. At this time, the rental management company determines the rent payment method through a management entrustment contract concluded with the lessor. One of the rent payment methods is a delinquency guarantee. The delinquency guarantee is that when the lessee defaults on the rent and fails to pay, the management company advances the rent and pays it to the lessor. That is, the management company pays the rent to the lessor before receiving the rent from the lessee. When the lessee terminates the rental contract of the rental property and then moves out, the rent for the month of termination is the daily prorated amount until the termination date. However, if the management company pays the rent for the month of termination to the lessor and then receives a request for termination of the rental contract from the lessee, the difference between the rent for one month and the daily prorated amount becomes the overpayment amount, and the management company needs to get the lessor to refund the difference.
[0005] The present invention has been made in view of the above problems, and an object thereof is to provide a rental management device, a rental management method, and a rental management program that enable prompt settlement of overpaid rent to the lessor when the lessee notifies of cancellation of the rental management contract.
Means for Solving the Problems
[0006] In order to solve the above-described problems and achieve the object, a rental management device according to the present invention includes a payment request data creation unit that creates payment request data to be paid to the lessor based on a rental contract, a collection schedule data creation unit that creates collection schedule data to be billed to the lessee based on the rental contract, and a subtraction request data creation unit that creates subtraction request data corresponding to the payment request data based on cancellation information from the lessee.
[0007] Further, a rental management method according to the present invention includes steps of creating, by a computer, payment request data to be paid to the lessor based on a rental contract, creating collection schedule data to be billed to the lessee based on the rental contract, and creating subtraction request data corresponding to the payment request data based on cancellation information from the lessee.
[0008] Further, a rental management program according to the present invention causes a computer to execute steps of creating payment request data to be paid to the lessor based on a rental contract, creating collection schedule data to be billed to the lessee based on the rental contract, and creating subtraction request data corresponding to the payment request data based on cancellation information from the lessee.
Effects of the Invention
[0009] The present invention has an effect that when the lessee notifies of cancellation of the rental management contract, overpaid rent can be promptly settled to the lessor.
Brief Description of the Drawings
[0010]
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
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Embodiments for Carrying Out the Invention
[0011] Hereinafter, embodiments of the rental management device, the rental management method, and the rental management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited by this embodiment.
[0012] [Rental Management Device] FIG. 1 is a block diagram showing an example of the configuration of the rental management device.
[0013] In a rental management system, a rental management company borrows rental properties owned by a landlord (lessor) from the landlord and rents out the rental properties to lessees who have signed rental contracts. The rental management company collects rent from the lessees and pays the collected amount to the lessor. In the management entrustment contract concluded between the rental management company and the lessor, a delinquency guarantee is defined as a method of rent payment. The delinquency guarantee is for the management company to advance the rent and pay it to the lessor when the lessee is delinquent in paying the rent and fails to pay. That is, the management company pays the rent to the lessor before receiving the rent from the lessee. Here, when the lessee terminates the rental contract of the rental property and moves out, the rent for the month of termination is the prorated amount up to the termination date. At this time, if the management company pays the rent for the month of termination to the lessor and then receives a request for termination of the rental contract from the lessee, the difference between the rent for one month and the prorated amount becomes the overpayment amount, and the management company needs to get the lessor to refund the difference amount.
[0014] Even when such an event occurs, the rental management device 10 of the present embodiment enables the management company, the landlord, and the lessee to quickly settle the difference amount.
[0015] The rental management device 10 is constructed based on a commercially available desktop personal computer. Note that the rental management device 10 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, and may also be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.
[0016] The rental management device 10 includes a control unit 11, a communication interface unit 12, a storage unit 13, and an input / output interface unit 14. Each part of the rental management device 10 is communicably connected via an arbitrary communication path.
[0017] The communication interface unit 12 is communicably connected to the rental management device 10 to the network 100 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 12 has a function of communicating data with other devices via a communication line. Here, the network 100 has a function of communicably connecting the rental management device 10 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 13 may be stored in the server 200, for example.
[0018] The input / output interface unit 14 has an input device 21 and an output device 22 connected thereto. As the input device 21, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. As the output device 22, in addition to a monitor (including a home television), a speaker or a printer can be used. Note that hereinafter, the input device 21 may be described as a keyboard or a mouse, and the output device 22 may be described as a monitor.
[0019] The storage unit 13 stores various databases, tables, files, and the like. The storage unit 13 records a computer program for giving instructions to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.
[0020] The storage unit 13 stores various types of information related to rental properties. The storage unit 13 stores a rental item master 31, a property master 32, a room master 33, a room rent master 34, a customer master 35, a management entrustment contract master 36, a contract master 37, and a contract rent monthly master 38. Details of the rental item master 31, property master 32, room master 33, room rent master 34, customer master 35, management entrustment contract master 36, contract master 37, and contract rent monthly master 38 will be described later.
[0021] The control unit 11 executes rental management processing based on various data stored in the storage unit 13 as information processing. The control unit 11 includes a payment request data creation unit 41, a collection schedule data creation unit 42, a subtraction request data creation unit 43, a daily rate amount data creation unit 44, and a display control unit 45.
[0022] The payment request data creation unit 41 creates payment request data to be paid to the landlord based on a rental contract concluded among the management company, the landlord, and the tenant. The collection schedule data creation unit 42 creates collection schedule data to be billed to the tenant based on the rental contract. Also, the collection schedule data creation unit 42 creates collection schedule data such as management fees to be billed to the landlord based on the rental contract.
[0023] The subtraction request data creation unit 43 creates subtraction request data corresponding to the payment request data based on the cancellation information from the tenant. Based on the late payment guarantee of the rental contract, before the rent is paid from the tenant to the management company, the management company pays the rent to the landlord. At this time, when the cancellation of the rental contract of the rental property is notified from the tenant, the subtraction request data creation unit 43 creates subtraction request data. Specifically, the subtraction request data created by the subtraction request data creation unit 43 is such that the payment request data created by the payment request data creation unit 41 becomes negative data.
[0024] The daily rate amount data creation unit 44 creates daily rate amount data for the cancellation month based on the cancellation date in the cancellation information. That is, the daily rate amount data creation unit 44 calculates and creates the daily rate amount from the 1st day to the cancellation date in the cancellation month.
[0025] As described above, if, after the management company pays the rent for the cancellation month to the lessor, the lessee requests cancellation of the lease contract, the difference between the rent for one month and the daily rate amount becomes the overpayment amount, and the management company needs to get the lessor to refund the difference. At this time, the payment request data creation unit 41 registers the subtraction request data and the daily rate amount data as payment request data.
[0026] The display control unit 45 causes the monitor as the output device 22 to display the remittance calculation processing screen and the cancellation input screen. The payment request data creation unit 41, the collection schedule data creation unit 42, the subtraction request data creation unit 43, and the daily rate amount data creation unit 44 execute the various processes described above based on the various input information input from the input device 21. The display control unit 45 causes the monitor to display the result of this process.
[0027] [Detailed Configuration of the Storage Unit] FIG. 2 is a diagram showing an example of a rental item master. As shown in FIG. 2, the rental item master manages items to be billed to the lessee or the lessor. For the rental item name corresponding to the rental item code, rent, common expenses, water charges, early cancellation default penalty, and management fees are set in the rental item master.
[0028] FIG. 3 is a diagram showing an example of a property master. As shown in FIG. 3, the property master manages building information. For the property name corresponding to the property code, for example, ABC Mansion is registered in the property master.
[0029] FIG. 4 is a diagram showing an example of a room master. As shown in FIG. 4, the room master manages the rooms of the property. The room number, daily rate denominator (days), and early cancellation notice (months) corresponding to the property code are registered in the room master.
[0030] FIG. 5 is a diagram showing an example of a room rent master. As shown in FIG. 5, the room rent master manages the room rent of a property. For the room rent master, a room number, item code, daily rate calculation fraction classification, daily rate calculation fraction unit code, refund classification, management fee target classification, and daily rate default fine classification are set for the property code.
[0031] FIG. 6 is a diagram showing an example of a customer master. As shown in FIG. 6, the customer master manages the billing destination and payment destination. For the customer master, a customer name and customer type are registered for the customer code.
[0032] FIG. 7 is a diagram showing an example of a management entrustment contract master. As shown in FIG. 7, the management entrustment contract master manages the management entrustment contract with the property owner. For the management entrustment contract master, a property code, property owner code, entrustment form, management fee rate, and remittance date are registered for the management entrustment contract number.
[0033] FIG. 8 is a diagram showing an example of a contract master. As shown in FIG. 8, the contract master manages the lease contract with the lessee. For the contract master, a contractor code, property code, room number, initial contract date, billing form, and contract status code are registered for the contract number.
[0034] FIG. 9 is a diagram showing an example of a monthly contract rent master. As shown in FIG. 9, the monthly contract rent master manages the monthly billing amount of the lessee. For the monthly contract rent master, an item code and billing amount are registered for the contract number.
[0035] [Lease Management Method] A lease management method by the lease management device 10 will be described. In the following description, the lease management company has concluded a management entrustment contract between the property owner and the lessee, and a delinquency guarantee is set as a method of paying the rent. Then, as an example, after the management company pays the rent for the cancellation month to the property owner, if the lessee requests cancellation of the lease contract, the case where the management company refunds the excess amount to the property owner will be described.
[0036] [Remittance Calculation Process] FIG. 10 is a diagram showing an example of data scheduled for collection.
[0037] As shown in FIGS. 1 and 10, the control unit 11 executes billing calculation processing for the borrower. The billing calculation processing creates collection schedule data to be billed to the borrower based on the monthly contract rent master. The collection schedule data outputs the collection schedule data creation classification for the collection schedule Guid, the billing year and month, the current month, the contract number, the billing customer code, the management entrusted contract number, the item code, the amount, the remittance classification, the remittance number, and the remittance status classification. When the billing form in the contract master is the previous rent, the current month is set to the billing year and month + 1.
[0038] FIG. 11 is a diagram showing an example of a remittance calculation processing screen, FIG. 12 is a diagram showing an example of a remittance calculation room work, and FIG. 13 is a diagram showing an example of a remittance calculation contract work.
[0039] As shown in FIGS. 1 and 11, first, the remittance calculation processing is executed on the remittance calculation processing screen. The operator inputs the remittance date and the remittance year and month into the remittance calculation processing screen and executes it. Then, the management entrusted contract to be remitted can be acquired from the remittance date on the remittance calculation processing screen, and the remittance calculation room work shown in FIG. 12 is output. Also, the target contract can be acquired from the remittance calculation room work, and the remittance calculation contract work shown in FIG. 13 is output. The remittance calculation room work shown in FIG. 12 is the room number, the management entrusted contract number, and the entrusted form for the property code. As shown in FIG. 13, the remittance calculation contract work is the room number, the contract number, the contract status code, the management entrusted contract number, and the entrusted form for the property code.
[0040] FIG. 14 is a diagram showing an example of payment request data to be paid to the landlord, FIG. 15 is a diagram showing an example of collection schedule data to be billed to the landlord, FIG. 16 is a diagram showing an example of collection schedule data to be billed to the borrower, and FIG. 17 is a diagram showing an example of collection schedule data after approval.
[0041] Next, payment request data is created from the target collection schedule data. In the remittance calculation process, the target of the collection schedule data for the normal month (lease agreement during occupancy) of the delinquent guarantee property is as follows. 1. The remittance year and month on the remittance calculation process screen match the billing year and month of the collection schedule data (when the billing form in the contract master is "0: previous rent", it is compared with "remittance year and month - 1 month"). 2. The contract number and management entrusted contract number in the remittance calculation contract work match. 3. The contract status code of the contract is "occupying". 4. The remittance classification of the collection schedule data is "1: do". Retrieve the collection schedule data that meets this condition (the collection schedule data with collection schedule Guids KY01 and KY02 is applicable), and create payment request data.
[0042] That is, when the remittance calculation (remittance year and month: November) is executed, the payment request data to the landlord shown in Figure 14 is created. Here, when the entrusted form in the management entrusted contract master is "3: delinquent guarantee", the payment request data to the landlord is created based on the data with the remittance classification of "1: do" in the borrower's collection schedule data. Also, from the created payment request data, the management fee to be billed to the landlord as shown in Figure 15 is calculated, and collection schedule data is created. Here, the remittance number is issued by the execution of the remittance calculation process. As shown in Figure 14, the payment request data to be paid to the landlord is the payee code, item code, amount, contract number, management entrusted contract number, collection schedule Guid, and remittance number for the payment request Guid. Also, as shown in Figure 15, the collection schedule data to be billed to the landlord is the collection schedule data creation classification, billing year and month, current month, contract number, billing counterparty code, management entrusted contract number, item code, amount, remittance classification, remittance number, and remittance status classification for the collection schedule Guid.
[0043] Note that the calculation of the management fee to be billed to the landlord is executed by the following method. Among the payment request data created in the remittance calculation process, it is calculated by multiplying the amount of the item with "management fee calculation target = 1: do" in the room rent master by the "management fee rate" in the management entrusted contract master. (100,000 + 5,000) × 5% = 5,250 (100,000 + 5,000) is the total amount of the payment request Guids of the payment request data for SI01 (¥100,000) and SI02 (¥5,000). 5% is the management fee rate in the management entrustment contract master.
[0044] And, as shown in Figure 16, a remittance number is set in the borrower's scheduled collection data. The scheduled collection data that was the source of the payment request data has the remittance number set, the remittance status classification becomes "1: Calculating", and it is treated as the remittance target. As shown in Figure 16, the scheduled collection data to be billed to the borrower is the scheduled collection data creation classification for the scheduled collection Guid, the billing year and month, the corresponding month, the contract number, the billing customer code, the management entrustment contract number, the item code, the amount, the remittance classification, the remittance number, and the remittance status classification.
[0045] Once the amount is determined by the remittance calculation process, approval of the remittance number "SK01" is performed in the payment request approval input. By this approval process, the remittance status classification of the scheduled collection data changes from "1: Calculating" to "2: Approved". The scheduled collection data after approval shown in Figure 17 is the scheduled collection data creation classification for the scheduled collection Guid, the billing year and month, the corresponding month, the contract number, the billing customer code, the management entrustment contract number, the item code, the amount, the remittance classification, the remittance number, and the remittance status classification.
[0046] [Cancellation Process] As shown in Figure 1, when there is a request for departure due to the cancellation of the lease contract from the borrower, the control unit 11 executes the cancellation process. Figure 18 is a diagram showing an example of the cancellation information input screen.
[0047] As shown in Fig. 18, on the cancellation information input screen, enter the contract number, the cancellation date, and the prorated number of days. Also, on the cancellation information input screen, enter the remittance year and month as the next remittance year and month (2023 / 12) and execute. Then, the corresponding contract case is output and the prorated amount is automatically displayed. That is, for the target case, the amount billed to the borrower in the cancellation month is output as the prorated amount. That is, it is checked whether there is recovery schedule data for the monthly amount (recovery schedule data creation classification = 3: billing calculation) in the cancellation month based on the contract number and cancellation date entered on the cancellation information input screen. Here, the recovery schedule data for the cancellation month refers to the data of the billing year and month of "the month before the cancellation date - 1 month" when the billing form in the contract master is "0: previous rent". If the corresponding recovery schedule data exists, data for subtracting the monthly amount (recovery schedule data creation classification = 12) is created.
[0048] Fig. 19 is a diagram showing an example of departure data, Fig. 20 is a diagram showing an example of recovery schedule data before entering cancellation information, and Fig. 21 is a diagram showing an example of recovery schedule data after entering cancellation information.
[0049] As shown in Fig. 19, the departure data is the contract status code for the contract number, the cancellation application date, the cancellation date, the prorated number of days, the penalty calculation date, the number of penalty days, and the remittance year and month after entering cancellation. And as shown in Fig. 20, the recovery schedule data before entering cancellation information corresponds to the monthly amount data of the recovery schedule data with recovery schedule Guids "KY01", "KY02", and "KY03" in the cancellation month. The recovery schedule data before entering cancellation information has a recovery schedule creation classification of "3: billing calculation".
[0050] On the one hand, as shown in FIG. 21, after the cancellation information is input, the scheduled collection data is changed from the scheduled collection creation category "3: Claim calculation" to the scheduled collection creation category "10: Full amount in cancellation month". And as data to cancel the scheduled collection creation category "10: Full amount in cancellation month", the scheduled collection creation category "12: Minus full amount in cancellation month" (subtraction request data) is created. The scheduled collection data of the scheduled collection creation category "12: Minus full amount in cancellation month" is the scheduled collection data of the scheduled collection Guids "KY05", "KY06", and "KY07". Furthermore, as the daily rate amount data to be billed in the cancellation month, the scheduled collection creation category "8: Cancellation daily rate" (daily rate amount data) is created. The scheduled collection data of the scheduled collection creation category "8: Cancellation daily rate" is the scheduled collection data of the scheduled collection Guids "KY08", "KY09", and "KY10".
[0051] Note that the calculation of the cancellation daily rate is performed by the following method. "Amount in the monthly contract rent master × Number of days in the daily rate for cancellation input ÷ Denominator of the daily rate in the room master" Perform rounding processing on this calculation result with reference to the rounding classification of the daily rate calculation and the daily rate calculation rounding unit code in the room rent master. TK011: Rent 100,000 × 25 ÷ 30 = 83,333.333··· → Rounding down to the nearest yen → ¥83,333 TK012: Common expenses 5,000 × 25 ÷ 30 = ¥4,166.666··· → Rounding down to the nearest yen → ¥4,166 TK013: Water fee 2,000 × 25 ÷ 30 = ¥1,666.666··· → Rounding down to the nearest yen → ¥1,666
[0052] [Remittance calculation process] FIG. 22 is a diagram showing an example of the remittance calculation process screen, FIG. 23 is a diagram showing an example of the remittance calculation process work, and FIG. 24 is a diagram showing an example of the remittance calculation process work for the corresponding property.
[0053] As shown in Fig. 1, the control unit 11 re-executes the remittance calculation process for the house owner and the borrower. As shown in Fig. 12, the remittance calculation process is executed on the remittance calculation process screen. The operator inputs the remittance date and the remittance year and month on the remittance calculation process screen and executes it. Then, the management entrustment contract for the remittance target can be obtained from the remittance date on the remittance calculation process screen, and the remittance calculation room work shown in Fig. 23 is output. Also, the target contract can be obtained from the remittance calculation room work, and the remittance calculation contract work shown in Fig. 24 is output. As shown in Fig. 24, the remittance calculation contract work is changed from the contract status code "2: Occupying" to the contract status code "2: Canceling".
[0054] When the remittance calculation process (remittance year and month: December) is executed, since it corresponds to the "remittance year and month after input of cancellation information" for the input of cancellation information, payment request data is created based on the unremitted data among the recovery schedule data created from the contract cancellation (departure). With this mechanism, it is possible to recover overpayments. Also, since the management fee calculation is performed even if the payment amount is a negative amount, it is possible to refund the excess for the management fee billed to the house owner in the previous month.
[0055] Fig. 25 is a diagram showing an example of the recovery schedule data after the input of cancellation information, and Fig. 26 is a diagram showing an example of the recovery schedule data that is the basis of the payment request data.
[0056] That is, as shown in FIGS. 25 and 26, payment request data is created from the scheduled collection data of the rental property to be targeted. In the remittance calculation process, the target of the scheduled collection data for the normal month (during the occupancy contract) of the property with a delinquency guarantee is the same as that for the November remittance month described above. The target of the scheduled collection data for the cancellation month (during the cancellation contract) is as follows. That is, the departure data is specified from the contract number of the contract data. When the property code and room number in the remittance calculation room work match the property code and room number in the contract data, and the remittance month on the remittance calculation processing screen matches the remittance month after the cancellation input in the departure data, it is determined as the cancellation month. Also, for the remittance in the cancellation month, among the scheduled collection data with the contract number determined as the cancellation month, the scheduled collection data creation classification is "8: Cancellation day rate" or "10: Full amount of cancellation month" or "12: Full amount of cancellation month minus", and the remittance status classification is not "2: Approved", and the scheduled collection data that matches the contract number and management entrusted contract number in the remittance calculation contract work is targeted. Among them, payment request data is created from the details of the remittance target (remittance classification = 1: to be made) to the landlord. Here, as shown in FIG. 26, the scheduled collection data that is the source of the payment request data corresponds to the scheduled collection data with scheduled collection Guids = KY05, KY06, KY08, KY09.
[0057] FIG. 27 is a diagram showing an example of payment request data after the execution of the remittance calculation process, FIG. 28 is a diagram showing an example of scheduled collection data after the execution of the remittance calculation process, and FIG. 29 is a diagram showing an example of the scheduled collection data of the borrower after the execution of the remittance calculation process.
[0058] As shown in FIG. 27, based on the above-described remittance calculation process, payment request data based on the cancellation information is created. The payment request data after the execution of the remittance calculation process is the payee code, item code, amount, contract number, management entrusted contract number, scheduled collection Guid, and remittance number for the payment request Guid. The remittance number is issued by the execution of the remittance calculation process.
[0059] As shown in FIGS. 25 to 27, for example, in item code TK011: rent, the prorated amount for the cancellation month is ¥83,333, but the situation is that ¥100,000 has already been paid in November of the remittance year and month, resulting in an overpayment of ¥16,677. In the remittance calculation for December of the remittance year and month, according to the mechanism where the recovery schedule data of recovery schedule Guids "KY05" and "KY08" is used as the data for the payment request data, the payment amount is "-100,000 + 83,333 = -16,667", and a negative payment for the over-remittance is created, enabling the recovery of the over-remittance amount.
[0060] Also, as shown in FIG. 28, management fees are calculated as the recovery schedule data to be billed to the landlord. The calculation of the management fees to be billed to the landlord is the same as described above.
[0061] And, as shown in FIG. 29, a remittance number is set for the recovery schedule data of the borrower created by inputting cancellation information.
[0062] [Normal cancellation process] In the rental management method by the rental management device 10, the above-mentioned is, as an example, a case where after the management company pays the rent for the cancellation month to the landlord, the tenant requests the cancellation of the rental contract, and the management company has a situation where a refund of the excess amount occurs to the landlord. The case described below is one where the tenant requests the cancellation of the rental contract before the management company pays the rent for the cancellation month to the landlord.
[0063] FIG. 30 is a diagram showing an example of the recovery schedule data after inputting cancellation information, and FIG. 31 is a diagram showing an example of the recovery schedule data of the tenant after inputting cancellation information.
[0064] By executing the above-described remittance calculation process, payment request data is created. With this mechanism, the daily rate amount is calculated. That is, as shown in FIG. 30, if cancellation information has already been input before executing the remittance calculation for November of the remittance year and month, there are recovery schedule data with recovery schedule Guids = KY01, KY02, KY05, KY06, KY08, KY09 (all with remittance numbers not yet numbered) as the source data for creating the payment request data, so it will be remitted at the daily rate amount.
[0065] And as shown in FIGS. 30 and 31, since the remittance numbers for recovery schedule Guids = KY01, KY02 are NULL (not remitted), all data with a remittance classification of "1: Do" will be the data to be remitted in November of the remittance year and month. Recovery schedule Guids = KY01, KY02, KY05, KY06, KY08, KY09 apply. For example, when focusing on item code TK011 (rent), the data to be remitted will be the recovery schedule data shown in FIG. 31. The recovery schedule data creation classifications 10 and 12 are offset, and the remaining ¥83,333 of the recovery schedule data creation classification 8 remains. As a result, only the daily rate for the cancellation month will be paid to the landlord.
[0066] [Operational Effects of the Present Embodiment] The rental management device 10 of the present embodiment includes a payment request data creation unit 41 that creates payment request data to be paid to the landlord based on the rental contract, a recovery schedule data creation unit 42 that creates recovery schedule data to be billed to the tenant based on the rental contract, and a subtraction request data creation unit 43 that creates subtraction request data corresponding to the payment request data based on the cancellation information from the tenant. Therefore, when the landlord (tenant) notifies of the cancellation of the rental management contract, the rent overpaid to the landlord can be promptly settled.
[0067] The rental management device 10 of the present embodiment has a daily rate amount data creation unit 44 that creates daily rate amount data for the cancellation month based on the cancellation date in the cancellation information. Therefore, the rent overpaid to the landlord can be promptly refunded.
[0068] When cancellation information from the borrower is input after the rent has been paid based on the payment request data, the subtraction request data and the daily rate data are registered as the payment request data in the rental management device 10 of this embodiment. Therefore, the simplification of the remittance calculation process can be achieved.
[0069] [Contribution to the Sustainable Development Goals (SDGs) led by the United Nations] According to this embodiment, it is possible to contribute to promoting business efficiency and appropriate business judgment of the enterprise, so it is possible to contribute to Goals 8 and 9 of the SDGs.
[0070] In addition, according to this embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitalization, so it is possible to contribute to Goals 12, 13 and 15 of the SDGs.
[0071] In addition, according to this embodiment, it is possible to contribute to strengthening control and governance, so it is possible to contribute to Goal 16 of the SDGs.
[0072] [Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments.
[0073] For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.
[0074] In addition, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings, they can be arbitrarily changed unless otherwise specified.
[0075] Moreover, with respect to the rental management device 10, each of the illustrated components is functionally conceptual and does not necessarily have to be physically configured as shown in the figure.
[0076] For example, regarding the processing functions provided by the rental management device 10, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing device to execute the processing described in the present embodiment, and is mechanically read by the rental management device 10 as necessary. 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 the RAM and constitutes the control unit in cooperation with the CPU.
[0077] Also, this computer program may be stored in an application program server connected to the rental management device 10 via an arbitrary network, and all or part of it can be downloaded as necessary.
[0078] Also, a program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as 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), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.
[0079] Also, the "program" is a data processing method described in any language or description method, and may be in the form of source code or binary code, etc. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed and configured as a plurality of modules or libraries, or those that achieve their functions in cooperation with other separate programs typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.
[0080] The various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.
[0081] The rental management device 10 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 rental management device 10 may be realized by installing software (including a program or data, etc.) for realizing the processes described in the present embodiment in the device.
[0082] Furthermore, the specific forms of distribution and integration of the devices are not limited to those illustrated, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the functional load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.
Industrial Applicability
[0083] The present invention is useful in various enterprises.
Explanation of Signs
[0084] 10 Rental management device 11 Control unit 12 Communication interface unit 13 Storage unit 14 Input / output interface unit 21 Input device 22 Output device 31 Rental item master 32 Property master 33 Room master 34 Room rent master 35 Supplier master 36 Management entrustment contract master 37 Contract master 38 Contract rent monthly master 41 Payment request data creation unit 42 Collection schedule data creation unit 43 Subtraction request data creation unit 44 Daily rate amount data creation unit 45 Display control unit 100 Network 200 servers
Claims
1. A payment request data creation unit that creates payment request data to be paid to a lessor based on a lease contract; A recovery schedule data creation unit that creates recovery schedule data to be billed to a lessee based on the lease contract; A subtraction request data creation unit that creates subtraction request data corresponding to the payment request data based on cancellation information from the lessee; A lease management device comprising the above.
2. The lease management device according to Claim 1, further comprising a daily rate amount data creation unit that creates daily rate amount data for the month of cancellation based on the cancellation date in the cancellation information. The lease management device according to Claim 1.
3. When cancellation information from the lessee is input after payment of rent based on the payment request data, the subtraction request data and the daily rate amount data are registered as payment request data. The lease management device according to Claim 2.
4. A lease management method executed by a computer, the method comprising: creating payment request data to be paid to a lessor based on a lease contract; creating recovery schedule data to be billed to a lessee based on the lease contract; creating subtraction request data corresponding to the payment request data based on cancellation information from the lessee. The lease management method comprising the above steps.
5. A lease management program for causing a computer to: create payment request data to be paid to a lessor based on a lease contract; create recovery schedule data to be billed to a lessee based on the lease contract; create subtraction request data corresponding to the payment request data based on cancellation information from the lessee. The lease management program for causing the computer to execute the above steps.
Citation Information
Patent Citations
Money transfer management support device, money transfer management support method and money transfer management support program
JP2020004216A
Real estate management device, real estate management method, and real estate management program
JP2023158758A
House rent debt management device, house rent debt management method, and house rent debt management program
JP2023172762A
Lease transaction management and accounting system
US20030139985A1
Rent management device, rent management method, and rent management program
JP2020057086A