Rental management device, rental management method, and rental management program

JP7939931B2Active Publication Date: 2026-10-22OBIC CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023220046
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-12-26
Publication Date
2026-10-22
Estimated Expiration
2043-12-26

Smart Images

  • Figure 0007939931000001
    Figure 0007939931000001
  • Figure 0007939931000002
    Figure 0007939931000002
  • Figure 0007939931000003
    Figure 0007939931000003
Patent Text Reader

Abstract

To provide a rental management device capable of promptly settling overpaid rent to a landlord when a tenant notifies the landlord of the cancellation of a rental management contact, a rental management method, and a rental management program.SOLUTION: A rental management device comprises: a payment request data creation unit which creates payment request data to be paid to a landlord on the basis of a rental contract; a collection schedule data creation unit which creates collection schedule data to be billed to a tenant on the basis of the rental contract; and a deduction request data creation unit which creates deduction request data corresponding to the payment request data on the basis of cancellation information from the tenant.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

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 lender (property owner) from the lender, and leases the rental properties to tenants who have signed a rental contract. The rental management company collects rent from the tenants, and pays the collected amount to the lender. 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

PROBLEM TO BE SOLVED BY THE INVENTION

[0004] In the rental management system, a rental contract is concluded between the rental management company, the lender, and the tenant. At this time, the rent payment method is stipulated by the management entrustment contract concluded between the rental management company and the lender. One of the rent payment methods is delinquency guarantee. The delinquency guarantee is a system in which, when a tenant falls behind on rent and leaves it unpaid, the management company advances the rent and pays it to the lender. That is, the management company pays the rent to the lender before the rent is paid by the tenant. When the tenant cancels the rental contract for the rental property and then moves out, the rent for the cancellation month is the prorated amount up to the cancellation date. However, if the tenant submits a request to cancel the rental contract after the management company has paid the rent for the cancellation month to the lender, the difference between the one-month rent and the prorated amount becomes an overpaid amount, and the management company will need to have the lender refund the difference.

[0005] The present invention has been made in view of the above problems, and aims to provide a rental management device, a rental management method, and a rental management program that enable the landlord to promptly settle any overpaid rent when the tenant notifies the landlord of the termination of the rental management contract. [Means for solving the problem]

[0006] To solve the above-mentioned problems and achieve the objectives, the rental management device according to the present invention comprises: a payment request data creation unit that creates payment request data to be paid to the landlord based on the rental agreement; a collection schedule data creation unit that creates collection schedule data to be billed to the tenant based on the rental agreement; and a deduction request data creation unit that creates deduction request data corresponding to the payment request data based on termination information from the tenant.

[0007] Furthermore, the rental management method according to the present invention includes the steps of: creating payment request data to be paid to the landlord based on the rental agreement, which is executed by a computer; creating collection schedule data to be billed to the tenant based on the rental agreement; and creating deduction request data corresponding to the payment request data based on termination information from the tenant.

[0008] Furthermore, the rental management program according to the present invention causes a computer to perform the following steps: create payment request data to be paid to the landlord based on the rental agreement; create collection schedule data to be billed to the tenant based on the rental agreement; and create deduction request data corresponding to the payment request data based on termination information from the tenant. [Effects of the Invention]

[0009] This invention has the effect of enabling landlords to quickly settle any overpaid rent when a tenant notifies them of the termination of a rental management contract. [Brief explanation of the drawing]

[0010] [Figure 1]Figure 1 shows an example of the configuration of a rental management system. [Figure 2] Figure 2 shows an example of a rental item master. [Figure 3] Figure 3 shows an example of a property master. [Figure 4] Figure 4 shows an example of a room master. [Figure 5] Figure 5 shows an example of a room rent master data. [Figure 6] Figure 6 shows an example of a customer master data. [Figure 7] Figure 7 shows an example of a management outsourcing contract master. [Figure 8] Figure 8 shows an example of a contract master. [Figure 9] Figure 9 shows an example of a monthly master data set for contracted rents. [Figure 10] Figure 10 shows an example of data to be collected. [Figure 11] Figure 11 shows an example of a remittance calculation processing screen. [Figure 12] Figure 12 shows an example of a workroom setup in a remittance calculation room. [Figure 13] Figure 13 shows an example of a remittance calculation contract work. [Figure 14] Figure 14 shows an example of payment request data to be paid to the landlord. [Figure 15] Figure 15 shows an example of the data to be collected from the landlord. [Figure 16] Figure 16 shows an example of the data to be collected from the tenant. [Figure 17] Figure 17 shows an example of data to be collected after approval. [Figure 18] Figure 18 shows an example of a screen for entering cancellation information. [Figure 19] Figure 19 shows an example of move-out data. [Figure 20] Figure 20 shows an example of data to be collected before entering cancellation information. [Figure 21] Figure 21 is a diagram illustrating an example of scheduled collection data after cancellation information is entered. [Figure 22] Figure 22 is a diagram illustrating an example of a remittance calculation processing screen. [Figure 23] Figure 23 is a diagram illustrating an example of a remittance calculation processing worksheet. [Figure 24] Figure 24 is a diagram illustrating an example of a remittance calculation processing worksheet for the corresponding property. [Figure 25] Figure 25 is a diagram illustrating an example of scheduled collection data after cancellation information is entered. [Figure 26] Figure 26 is a diagram illustrating an example of scheduled collection data that serves as the source of payment request data. [Figure 27] Figure 27 is a diagram illustrating an example of payment request data after execution of remittance calculation processing. [Figure 28] Figure 28 is a diagram illustrating an example of scheduled collection data after execution of remittance calculation processing. [Figure 29] Figure 29 is a diagram illustrating an example of lessee's scheduled collection data after execution of remittance calculation processing. [Figure 30] Figure 30 is a diagram illustrating an example of scheduled collection data after cancellation information is entered. [Figure 31] Figure 31 is a diagram illustrating an example of lessee's scheduled collection data after cancellation information is entered. [Modes for Carrying Out the Invention]

[0011] Below, embodiments of the rental management apparatus, rental management method, and rental management program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by these embodiments.

[0012] [Rental Management Apparatus] Figure 1 is a block diagram illustrating an example of the configuration of the rental management apparatus.

[0013] In a rental management system, a rental management company leases rental properties owned by landlords and leases them to tenants who have signed rental agreements. The rental management company collects rent from tenants and pays the collected amount to the landlord. The management contract between the rental management company and the landlord stipulates a rent guarantee as a method of rent payment. The rent guarantee means that if the tenant defaults on rent payments, the management company will pay the rent to the landlord on their behalf. In other words, the management company pays the rent to the landlord before the tenant pays it. Now, if the tenant terminates the rental agreement and moves out, the rent for the month of termination will be calculated on a pro-rata basis up to the termination date. In this case, if the tenant requests termination of the rental agreement after the management company has paid the rent for the month of termination to the landlord, the difference between the full month's rent and the pro-rata amount will be an overpayment, and the management company will need to get the difference refunded by the landlord.

[0014] The rental management device 10 of this embodiment enables the management company, the landlord, and the tenant to quickly settle the difference even if such an event occurs.

[0015] The rental management device 10 is built on a commercially available desktop personal computer. However, the rental management device 10 is not limited to being built on a stationary information processing device such as a desktop personal computer; it may also be built on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0016] The rental management device 10 comprises 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 connected to communicate via any communication path.

[0017] The communication interface unit 12 connects 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 the function of communicating data with other devices via a communication line. Here, the network 100 has the function of connecting the rental management device 10 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). The data stored in the storage unit 13 may be stored in, for example, the server 200.

[0018] The input / output interface unit 14 is connected to an input device 21 and an output device 22. The input device 21 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. The output device 22 can be a monitor (including a home television), speaker, or printer. In the following description, the input device 21 may be referred to as a keyboard or mouse, and the output device 22 as a monitor.

[0019] The storage unit 13 stores various databases, tables, and files. The storage unit 13 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0020] The storage unit 13 stores various information related to rental properties. The storage unit 13 stores the rental item master 31, property master 32, room master 33, room rent master 34, business partner master 35, management consignment contract master 36, contract master 37, and monthly contract rent master 38. Details of the rental item master 31, property master 32, room master 33, room rent master 34, business partner master 35, management consignment contract master 36, contract master 37, and monthly contract rent master 38 will be described later.

[0021] The control unit 11 performs rental management processing based on various data stored in the storage unit 13 as part of its information processing. The control unit 11 includes a payment request data creation unit 41, a collection schedule data creation unit 42, a deduction request data creation unit 43, a daily rate 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 the lease agreement concluded between 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 lease agreement. The collection schedule data creation unit 42 also creates collection schedule data, such as management fees, to be billed to the landlord based on the lease agreement.

[0023] The deduction request data creation unit 43 creates deduction request data corresponding to the payment request data based on the termination information from the tenant. When the management company pays the rent to the landlord before the tenant pays the rent to the management company based on the rent guarantee of the lease agreement, and at this time the tenant notifies the management company of the termination of the lease agreement for the rental property, the deduction request data creation unit 43 creates deduction request data. Specifically, the deduction request data created by the deduction request data creation unit 43 is a negative version of the payment request data created by the payment request data creation unit 41.

[0024] The daily rate data creation unit 44 creates daily rate data for the cancellation month based on the cancellation date in the cancellation information. In other words, the daily rate data creation unit 44 calculates and creates the daily rate for the month of cancellation from the 1st to the cancellation date.

[0025] As mentioned above, if the tenant requests termination of the lease agreement after the management company has paid the rent for the month of termination to the landlord, the difference between the full month's rent and the prorated amount will be an overpayment, and the management company will need to get the difference refunded by the landlord. At this time, the payment request data creation unit 41 registers the deduction request data and the prorated amount data as payment request data.

[0026] The display control unit 45 displays the remittance calculation processing screen and the cancellation input screen on the monitor, which serves as the output device 22. The payment request data creation unit 41, the collection schedule data creation unit 42, the deduction request data creation unit 43, and the daily amount data creation unit 44 each execute the various processes described above based on the various input information received from the input device 21. The display control unit 45 displays the results of these processes on the monitor.

[0027] [Detailed configuration of the memory unit] Figure 2 shows an example of a rental item master. As shown in Figure 2, the rental item master manages the items that are billed to tenants and landlords. In the rental item master, the rental item names for the rental item codes are set as rent, common area maintenance fee, water charge, prorated cancellation fee, and management fee.

[0028] Figure 3 shows an example of a property master. As shown in Figure 3, the property master manages building information. In the property master, for example, "ABC Mansion" is registered as the property name for a property code.

[0029] Figure 4 shows an example of a room master. As shown in Figure 4, the room master manages the rooms in a property. The room master registers the room number for each property code, the daily rate denominator (days), and the notice period for termination (months).

[0030] Figure 5 shows an example of a room rent master. As shown in Figure 5, the room rent master manages the room rent for a property. The room rent master has the following entries for each property code: room number, item code, daily calculation fractional part category, daily calculation fractional part unit code, refund category, management fee category, and daily penalty category.

[0031] Figure 6 shows an example of a customer master database. As shown in Figure 6, the customer master database manages billing and payment recipients. The customer master database registers the customer name and customer type for each customer code.

[0032] Figure 7 shows an example of a property management contract master. As shown in Figure 7, the property management contract master manages property management contracts with landlords. The property management contract master registers the property code, landlord code, contract type, management fee rate, and payment date for each property management contract number.

[0033] Figure 8 shows an example of a contract master. As shown in Figure 8, the contract master manages lease agreements with tenants. The contract master registers the tenant code, property code, room number, initial contract date, billing type, and contract status code for each contract number.

[0034] Figure 9 shows an example of a monthly contract rent master. As shown in Figure 9, the monthly contract rent master manages the monthly billing amount for tenants. The monthly contract rent master registers the item code for the contract number and the billing amount.

[0035] [Rental property management methods] This section describes the rental management method using the rental management device 10. In the following description, the rental management company has entered into a management consignment agreement with the landlord and the tenant, and a rent guarantee is set as the method of rent payment. As an example, the section describes a case where, after the management company has paid the rent for the month of termination to the landlord, the tenant requests termination of the rental agreement, and the management company is required to refund the excess amount to the landlord.

[0036] [Remittance calculation process] Figure 10 shows an example of data to be collected.

[0037] As shown in Figures 1 and 10, the control unit 11 performs billing calculation processing for the tenant. The billing calculation processing creates collection schedule data to be billed to the tenant based on the monthly contract rent master. The collection schedule data outputs the collection schedule data creation category, billing year and month, applicable month, contract number, billing customer code, management consignment contract number, item code, amount, remittance category, remittance number, and remittance status category for the collection schedule GUID. If the billing method in the contract master is advance rent, the applicable month is set to billing year and month + 1.

[0038] Figure 11 shows an example of a remittance calculation processing screen, Figure 12 shows an example of a remittance calculation room work, and Figure 13 shows an example of a remittance calculation contract work.

[0039] As shown in Figures 1 and 11, first, the remittance calculation process is executed on the remittance calculation processing screen. The operator enters the remittance date and remittance year and month on the remittance calculation processing screen and executes it. Then, the management consignment contract to be remitted can be obtained from the remittance date on the remittance calculation processing screen, and the remittance calculation room work shown in Figure 12 is output. Furthermore, the target contract can be obtained from the remittance calculation room work, and the remittance calculation contract work shown in Figure 13 is output. The remittance calculation room work shown in Figure 12 consists of the room number for the property code, the management consignment contract number, and the consignment type. As shown in Figure 13, the remittance calculation contract work consists of the room number for the property code, the contract number, the contract status code, the management consignment contract number, and the consignment type.

[0040] Figure 14 shows an example of payment request data to be paid to the landlord, Figure 15 shows an example of collection data to be billed to the landlord, Figure 16 shows an example of collection data to be billed to the tenant, and Figure 17 shows an example of collection data after approval.

[0041] Next, payment request data is created from the target collection schedule data. In the remittance calculation process, the collection schedule data for regular months (contracts under occupancy) of properties with delinquent payments must meet the following conditions. 1. The remittance month and year on the remittance calculation processing screen match the billing month and year in the collection schedule data (if the billing type in the contract master is "0: advance rent", compare using "remittance month and year - 1 month"). 2. The contract number for the remittance calculation contract work and the management outsourcing contract number match. 3. The contract status code for the contract indicates that the tenant is currently occupied. 4. The remittance category for the data to be collected is "1: Do". The system retrieves collection schedule data that matches these conditions (collection schedule data with collection schedule Guid=KY01 and KY02), and creates payment request data.

[0042] In other words, when the remittance calculation (remittance month and year: November) is executed, the payment request data to the landlord shown in Figure 14 is created. Here, if the consignment type in the management consignment contract master is "3: Arrears Guarantee", the payment request data to the landlord is created based on the data where the remittance category of the tenant's collection schedule data is "1: Yes". Furthermore, the management fee to be billed to the landlord is calculated from the created payment request data, and the collection schedule data shown in Figure 15 is created. Here, the remittance number is issued when the remittance calculation process is executed. As shown in Figure 14, the payment request data to be paid to the landlord includes the payee code, item code, amount, contract number, management consignment 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 includes the collection schedule data creation category, billing month and year, relevant month, contract number, billing customer code, management consignment contract number, item code, amount, remittance category, remittance number, and remittance status category for the collection schedule Guid.

[0043] The management fee to be charged to the landlord is calculated using the following method: The amount in the "Management fee calculation target = 1: Yes" item in the room rent master, which is part of the payment request data created during the remittance calculation process, is multiplied by the "Management fee rate" in the management consignment contract master. (100,000 + 5,000) × 5% = 5,250 (100,000 + 5,000) is the sum of the amounts for payment request GUIDs SI01 (¥100,000) and SI02 (¥5,000) in the payment request data. 5% is the management fee rate in the management outsourcing contract master.

[0044] Then, as shown in Figure 16, the remittance number is set in the borrower's collection schedule data. The collection schedule data that was the source of the payment request data has the remittance number set, the remittance status category becomes "1: Calculating", and it is treated as being subject to remittance. As shown in Figure 16, the collection schedule data to be billed to the borrower includes the collection schedule data creation category for the collection schedule GUID, billing year and month, relevant month, contract number, billing customer code, management consignment contract number, item code, amount, remittance category, remittance number, and remittance status category.

[0045] Once the amount is finalized through the remittance calculation process, approval for remittance number "SK01" is performed in the payment request approval input. This approval process changes the remittance status category of the scheduled collection data from "1: Calculating" to "2: Approved". The scheduled collection data after approval, as shown in Figure 17, includes the scheduled collection data creation category for the scheduled collection GUID, billing year and month, relevant month, contract number, billing customer code, management consignment contract number, item code, amount, remittance category, remittance number, and remittance status category.

[0046] [Cancellation Process] As shown in Figure 1, when the tenant requests to vacate the premises due to termination of the lease agreement, the control unit 11 executes the termination process. Figure 18 shows an example of the termination information input screen.

[0047] As shown in Figure 18, on the cancellation information input screen, enter the contract number, cancellation date, and prorated number of days. Also, on the cancellation information input screen, enter the next remittance month (2023 / 12) for the remittance month and execute. Then, the corresponding contract case will be output, and the prorated amount will be displayed automatically. In other words, for the target case, the amount billed to the tenant for the month of cancellation will be output as a prorated amount. Specifically, based on the contract number and cancellation date entered on the cancellation information input screen, it is checked whether there is any planned collection data for the month of cancellation (planned collection data creation category = 3: billing calculation). Here, the planned collection data for the month of cancellation refers to the billing month data of "month of cancellation date - 1 month" when the billing method in the contract master is "0: advance rent". If the corresponding planned collection data exists, data to subtract the monthly amount (planned collection data creation category = 12) will be created.

[0048] Figure 19 shows an example of move-out data, Figure 20 shows an example of collection schedule data before entering cancellation information, and Figure 21 shows an example of collection schedule data after entering cancellation information.

[0049] As shown in Figure 19, the move-out data includes the contract status code for the contract number, the date of cancellation application, the cancellation date, the prorated number of days, the date of penalty calculation, the number of days for which a penalty is due, and the month and year of payment after cancellation input. As shown in Figure 20, the planned collection data before entering the cancellation information corresponds to the monthly amount data for the cancellation month for the planned collection Guid "KY01", "KY02", and "KY03". The planned collection data before entering the cancellation information is classified as "3: Billing Calculation".

[0050] On the other hand, as shown in Figure 21, after entering cancellation information, the planned collection data is changed from collection plan creation category "3: Billing Calculation" to collection plan creation category "10: Full Amount for Cancellation Month". Then, as data to cancel collection plan creation category "10: Full Amount for Cancellation Month", collection plan creation category "12: Full Amount for Cancellation Month Minus" (deduction request data) is created. The planned collection data for collection plan creation category "12: Full Amount for Cancellation Month Minus" is the planned collection data for collection plan Guid "KY05", "KY06", and "KY07". Furthermore, as data for the prorated amount to be billed in the month of cancellation, collection plan creation category "8: Prorated Cancellation" (prorated amount data) is created. The planned collection data for collection plan creation category "8: Prorated Cancellation" is the planned collection data for collection plan Guid "KY08", "KY09", and "KY10".

[0051] The calculation of the prorated cancellation fee will be performed using the following method. "Monthly contract rent master amount × number of days for which cancellation was entered ÷ daily denominator in room master" The calculation result is then rounded down by referring to the daily calculation rounding category and daily calculation rounding unit code in the room rent master. TK011: Rent 100,000 × 25 ÷ 30 = 83,333.333... → Rounded down to the nearest yen → ¥83,333 TK012: Common area maintenance fee 5,000 × 25 ÷ 30 = ¥4,166.666... ​​→ Rounded down to the nearest yen → ¥4,166 TK013: Water bill 2,000 × 25 ÷ 30 = ¥1,666.666... ​​→ Rounded down to the nearest yen → ¥1,666

[0052] [Remittance calculation process] Figure 22 shows an example of the remittance calculation processing screen, Figure 23 shows an example of the remittance calculation processing work, and Figure 24 shows an example of the remittance calculation processing work for the relevant property.

[0053] As shown in Figure 1, the control unit 11 re-executes the remittance calculation process for the landlord and tenant. As shown in Figure 12, the remittance calculation process is executed on the remittance calculation screen. The operator enters the remittance date and remittance year and month on the remittance calculation screen and executes it. Then, the management consignment contract to be remitted can be obtained from the remittance date on the remittance calculation screen, and the remittance calculation room work shown in Figure 23 is output. The target contract can also be obtained from the remittance calculation room work, and the remittance calculation contract work shown in Figure 24 is output. As shown in Figure 24, the remittance calculation contract work changes from contract status code "2: Occupied" to contract status code "2: Terminated".

[0054] When the remittance calculation process (remittance month: December) is executed, it corresponds to the "remittance month after entry of cancellation information" in the contract termination information input. Therefore, payment request data is created based on the unremitted data from the collection data created from the contract termination (move out). This mechanism makes it possible to recover any overpayments. In addition, since the management fee is calculated even if the payment amount is a negative amount, any excess management fee billed to the landlord in the previous month can also be refunded.

[0055] Figure 25 shows an example of collection schedule data after entering cancellation information, and Figure 26 shows an example of collection schedule data that forms the basis of payment request data.

[0056] In other words, as shown in Figures 25 and 26, payment request data is created from the collection schedule data for the target rental property. In the remittance calculation process, the collection schedule data for regular months (contracts currently occupied) of properties with delinquent rent guarantees is the same as the remittance month of November mentioned above. The collection schedule data for the termination month (contracts currently terminated) is as follows: In other words, the move-out data is identified from the contract number in the contract data, and if 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 and year on the remittance calculation processing screen match the remittance month and year after termination input in the move-out data, it is determined to be a termination month. Furthermore, for remittances in the month of termination, the target is the scheduled remittance data for contract numbers determined to be in the month of termination, where the scheduled remittance data creation category is "8: Prorated termination," "10: Full amount for the month of termination," or "12: Full amount for the month of termination minus," and the remittance status category is not "2: Approved," and the data matches the contract number and management consignment contract number in the remittance calculation contract work. From these, payment request data is created from the details of the remittances to the landlord (remittance category = 1: Yes). Here, as shown in Figure 26, the scheduled remittance data that forms the basis of the payment request data corresponds to the scheduled remittance data with scheduled remittance Guid = KY05, KY06, KY08, and KY09.

[0057] Figure 27 shows an example of payment request data after the remittance calculation process is executed, Figure 28 shows an example of collection schedule data after the remittance calculation process is executed, and Figure 29 shows an example of borrower collection schedule data after the remittance calculation process is executed.

[0058] As shown in Figure 27, the remittance calculation process described above generates payment request data based on the cancellation information. The payment request data after the remittance calculation process is executed includes the payee code, item code, amount, contract number, management consignment contract number, collection schedule GUID, and remittance number for the payment request GUID. The remittance number is issued when the remittance calculation process is executed.

[0059] As shown in Figures 25 to 27, for example, in item code TK011: Rent, the prorated amount for the month of termination is ¥83,333, but ¥100,000 was already paid in November, resulting in an overpayment of ¥16,677. In the remittance calculation for December, the collection schedule data for collection schedule Guids "KY05" and "KY08" is used as the basis for the payment request data. As a result, the payment amount becomes "-100,000 + 83,333 = -16,667", creating a negative payment for the overpayment, which allows the overpayment to be recovered.

[0060] Furthermore, as shown in Figure 28, the management fee is calculated as the expected collection data to be billed to the landlord. The calculation of the management fee to be billed to the landlord is the same as described above.

[0061] Then, as shown in Figure 29, a remittance number is set in the borrower's collection schedule data created by entering the cancellation information.

[0062] [Normal cancellation process] In the rental management method using the rental management device 10, the above example is for a case where the management company has paid the rent for the month of termination to the landlord, and then the tenant requests termination of the lease agreement, resulting in the management company having to refund the excess amount to the landlord. The example described below is for a case where the tenant requests termination of the lease agreement before the management company has paid the rent for the month of termination to the landlord.

[0063] Figure 30 shows an example of data to be collected after entering cancellation information, and Figure 31 shows an example of data to be collected by the tenant after entering cancellation information.

[0064] By executing the remittance calculation process described above, payment request data is created. This mechanism calculates the prorated amount. In other words, as shown in Figure 30, if cancellation information has already been entered before the remittance calculation for the month of November is executed, the planned collection data that serves as the source for creating the payment request data will contain planned collection Guid=KY01,KY02,KY05,KY06,KY08,KY09 (all of which do not have remittance numbers assigned), and therefore the remittance will be made on a prorated basis.

[0065] As shown in Figures 30 and 31, for scheduled collection Guid=KY01 and KY02, since the remittance number is NULL (not remitted), all data with remittance category "1: Do" will be the data to be remitted in November. Scheduled collection Guid=KY01, KY02, KY05, KY06, KY08, and KY09 are included. For example, focusing on item code TK011 (rent), the remittance target will be the scheduled collection data shown in Figure 31. Scheduled collection data creation categories 10 and 12 are offset, leaving ¥83,333 for the remaining scheduled collection data creation category 8. As a result, only the prorated amount for the month of termination will be paid to the landlord.

[0066] [Effects of this embodiment] The rental management device 10 of this embodiment includes a payment request data creation unit 41 that creates payment request data to be paid to the landlord based on the rental agreement, a collection schedule data creation unit 42 that creates collection schedule data to be billed to the tenant based on the rental agreement, and a deduction request data creation unit 43 that creates deduction request data corresponding to the payment request data based on termination information from the tenant.Therefore, when the landlord (tenant) notifies the device of termination of the rental management agreement, any overpaid rent to the landlord can be promptly settled.

[0067] The rental management device 10 of this embodiment has a daily rate data creation unit 44 that creates daily rate data for the month of termination based on the termination date in the termination information. Therefore, it is possible to promptly refund any overpaid rent to the landlord.

[0068] In this embodiment, when the tenant enters cancellation information after the rent has been paid based on the payment request data, the rental management device 10 registers the deduction request data and the prorated amount data as payment request data. Therefore, the remittance calculation process can be simplified.

[0069] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

[0070] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0071] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

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

[0073] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

[0074] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0075] Furthermore, with respect to the rental management device 10, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0076] For example, the processing functions of the rental management device 10, particularly those performed in the control unit, may be implemented entirely or partially by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the rental management device 10 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0077] Furthermore, this computer program may be stored on an application program server connected to the rental management device 10 via any network, and it is possible to download all or part of it as needed.

[0078] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0079] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0080] The various databases stored in the memory unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0081] Furthermore, the rental management device 10 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the rental management device 10 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0082] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0083] This invention is useful in various types of businesses. [Explanation of Symbols]

[0084] 10 Rental Management System 11 Control Unit 12 Communication Interface Section 13 Storage section 14 Input / Output Interface Section 21 Input device 22 Output device 31 Rental Item Master 32 Property Master 33 Room Master 34 Room Rent Master 35 Customer Master 36 Management Outsourcing Contract Master 37 Contract Master 38. Monthly Master Data for Contract Rent 41 Payment Request Data Creation Department 42 Data Collection Department 43 Subtraction Request Data Creation Department 44. Daily Rate Data Creation Department 45 Display Control Unit 100 Networks 200 servers

Claims

1. A rental management system for a rental agreement that includes a guarantee that the management company will pay the rent to the landlord on behalf of the tenant if the tenant defaults on rent payments, A payment request data creation unit that creates payment request data to be paid to the lessor based on the lease agreement, A collection schedule data creation unit that creates collection schedule data to be claimed from the tenant based on the lease agreement, When the management company pays the rent to the landlord before the tenant pays the rent to the management company, and the tenant then notifies the management company of the termination of the lease agreement, a deduction request data creation unit creates deduction request data corresponding to the payment request data based on the termination information from the tenant. A rental management device equipped with the following features.

2. The system has a daily rate data creation unit that creates daily rate data for the month of cancellation based on the cancellation date in the aforementioned cancellation information, and the aforementioned deduction request data and the aforementioned daily rate data are registered as payment request data, and the deduction request data created by the deduction request data creation unit is such that the payment request data created by the payment request data creation unit becomes negative data. Rental management device according to claim 1.

3. When the tenant notifies the management company of the termination of the lease agreement before the management company pays the landlord the rent for the month of termination, the prorated amount data is registered as payment request data. The rental management device according to claim 2.

4. A rental management method for a rental agreement that includes a guarantee that the management company will pay the rent to the landlord on behalf of the tenant if the tenant defaults on rent payments, A computer executes The steps include creating payment request data to be paid to the lessor based on the lease agreement, The steps include creating data on the planned collections to be claimed from the tenant based on the lease agreement, When the management company pays the rent to the landlord before the tenant pays the rent to the management company, and the tenant then notifies the management company of the termination of the lease agreement, the steps include creating a deduction request data corresponding to the payment request data based on the termination information from the tenant, A rental management method that includes [specific features / features].

5. A rental management program for a rental agreement that includes a guarantee that the management company will pay the rent to the landlord on behalf of the tenant if the tenant defaults on rent payments, On the computer, The steps include creating payment request data to be paid to the lessor based on the lease agreement, The steps include creating data on the planned collections to be claimed from the tenant based on the lease agreement, When the management company pays the rent to the landlord before the tenant pays the rent to the management company, and the tenant then notifies the management company of the termination of the lease agreement, the steps include creating a deduction request data corresponding to the payment request data based on the termination information from the tenant, A rental management program designed to implement this.

Citation Information

Patent Citations

  • Money transfer management support device, money transfer management support method and money transfer management support program

    JP2020004216A

  • Rent management device, rent management method, and rent management program

    JP2020057086A

  • 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