KR20230019621A - Managing system for real estate lease contract - Google Patents

Abstract

The present invention relates to the management of rental contracts for real estate. Provided is a real estate rental contract management system, which includes: a contract management module which converts rental contracts for rental units into data and generates a power of attorney to process lease and monthly rent reports to a real estate transaction management server; a rental management module which manages data on the current status of rent collection for rental units; and a session management unit which controls the interface of a lessor terminal by switching the contract management module and the rental management module when the set contract conditions are established.

Description

Real estate lease contract management system {MANAGING SYSTEM FOR REAL ESTATE LEASE CONTRACT}

The present invention relates to real estate lease contract management, and more specifically, to a real estate lease contract management system that enables efficient management of information such as conclusion, change, and maintenance of a lease contract through a user terminal. it's about

In general, in the case of a tenant who leases and uses all or part of a building, he/she pays a deposit and uses the contracted part of the building while paying usage fees including rent and management fees for the building. Responsible for maintenance/repair, such as cleaning or repairing defects.

As is well known, a lease agreement has been made between contractors through real estate brokerage information provided by a real estate agency. Recently, a number of mobile platforms are being developed, and this trend is also affecting the real estate brokerage market. Real estate agencies also upload real estate rental properties through mobile applications or web programs, and tenants check them online and make transactions. . Recently, a number of such real estate brokerage platforms have appeared and are uploading and checking properties in a relatively easy way.

Korean Patent Publication No. 2000-0050095 discloses a real estate brokerage service method using the Internet of the prior art, and FIG. 1 is a configuration diagram thereof.

Looking at this in detail, the seller 10 is connected to the site provided by the mediation server 12 for real estate mediation through the Internet. Then, they are registered as members of the mediation server 12 and receive information related to selling/purchasing real estate from the mediation server 12 with priority. In addition, a member broker 14 that mediates real estate transactions is connected, and there are buyers 16 and 18 who connect to the brokerage server 12 and inquire information for purchasing real estate. When the seller 10 accesses the site provided by the brokerage server 12 for real estate brokerage through the Internet, the member broker 14 that brokers the real estate transaction accesses the brokerage server 12 to purchase real estate. Buyers 16 and 18 inquiring about are connected. The mediation server 12 is connected to a database 20 that stores various texts related to real estate/members or video information containing the inside/outside and location of real estate.

Currently, when trading or brokerage products are uploaded on a predetermined brokerage site or database, consumers or brokers can easily access them and check the sales conditions, so convenience has increased.

However, despite the emergence of a number of brokerage platforms for real estate transactions as described above, actual contracts are often made offline. This is because it is necessary to actually check the location, structure, defects, etc. of the building in order to actually live in it, and it is more dependent on meeting offline to stamp and check documents than online mediation without face-to-face.

Recently, attempts have been made to introduce electronic contracts in real estate transactions in order to solve the above inefficiencies beyond the simple online introduction of properties. It is a concept that mainly introduces a standard lease agreement into a database, converts it into an electronic document, and then enables the lessor and the lessee to sign an electronic signature so that the lease agreement can be concluded online.

Despite the above attempts, it is difficult to accommodate various types of contracts and individualized special contract conditions with only standard terms and conditions, and because landlords who manage a large number of real estate prefer real document contracts due to the nature of the situation, they are not popularized.

However, since reporting of real estate cheonsei and monthly rental contracts is compulsory, there is a demand for a new lease contract platform that meets the requirements of the law and enables online documents to be prepared in a simple way while harmonizing with the traditional contract method.

The present invention was made to solve the above-mentioned problems of the prior art, and provides user convenience and reliability of system operation by enabling realistic harmony between the conventional offline rental contract method and the recently emerging electronic contract method. Its purpose is to provide a rental contract management system for real estate that can be guaranteed.

As a means for solving the above-described technical problem, the present invention receives input from a communication unit 2010 connected to a lessor terminal, a database 2100 for converting and storing information on a rental contract into data, and matters related to the conclusion or renewal of a contract. Real estate including a contract management module 2300 that manages, a lease management module 2200 that manages the payment due date and receipt of rent, and a session management unit 2500 that switches functions between the contract management module and the lease management module according to set conditions. of rental contract management system.

Preferably, the contract management module includes an input unit 2310 that receives a contract image from the lessor terminal and a report processing unit 2340 that reports the rental contract information extracted from the contract received from the input unit to the real estate transaction management server. do.

In addition, the contract management module includes a power of attorney generating unit 2320 that provides a power of attorney format for proving the delegation of the monthly rent report to the lessor terminal, and a signature unit 2330 that performs an electronic signature to prove the validity of the power of attorney. can be provided.

Meanwhile, a session management unit 2500 for converting a function from a contract management module to a rental management module may be further included after the information on the rental contract is converted into data and the monthly rent is reported in the contract management module.

The session management unit determines whether to switch to the contract management module at the expiration of the contract period while the rental management module is functioning, and a date management unit 2510 that determines whether or not to switch to the contract management module if the rent is overdue during the set period. A validity judgment unit 2520 that determines and a conversion unit 2530 that performs functional conversion between the rental management module and the contract management module may be provided.

The rental management module includes a rental account management unit 2210 that manages the payment due date of the rental fee and whether or not the rental payment is received for each rental unit, and a bill management unit that creates a bill page for each rental unit and transmits it to the lessee terminal according to the selection of the lessor terminal ( 2220) may be provided.

Preferably, the interface control unit 2400 for displaying the rental contract by the contract management module and the rent by the rental management module on the lessor's terminal is further included.

In addition, the interface displayed on the landlord terminal includes a payment date display unit 1111 displaying the due date of the rent, a unit display unit 1112 displaying identification information on the rental unit, and a monthly rent display unit 1113 displaying the rent value And, the status can be changed to the receipt display (1121) by the receipt input of the lessor terminal, but the scheduled display (1123) or non-payment display (1122) is switched and displayed according to whether the delivery date for each rental unit has passed in the schedule management unit A rent toggle unit 1120 waiting for input is provided.

According to the configuration of the present invention described above, user convenience can be increased because offline contracts and online information input, reporting, and delegation management can be effectively converged and operated on one platform, and nationally, There is an effect that can be accurately managed for.

In addition, lease management such as contract signing and maintenance as well as rent collection can be performed in an integrated manner, and the system load is small because the contract management module and the lease management module can be distributed and operated on one platform according to predetermined conditions. Efficiency is dramatically improved.

In addition, even for multiple rental units, it is possible to intuitively check the arrival of rent payment, rent, and non-payment items in a lump sum, but it is possible to simply receive payment for each rental unit, change the status of non-payment, and update data. Convenience and efficiency are further improved.

1 is a block diagram of a real estate brokerage service method using the Internet in the prior art.
Figure 2 is a conceptual diagram for explaining the basic configuration of the real estate rental contract management system of the present invention.
Figure 3 is a block diagram for explaining the management server in the rental contract management system for real estate of the present invention.
4 is a block diagram showing the configuration of a database constituting a management server.
5 is a block diagram for explaining a contract management module constituting a management server.
6 is a block diagram illustrating a session management unit constituting a connection relationship between modules in a management server.
7 is a view showing an embodiment of the rental book management unit in the rental management module of the management server.
8 is a view showing an embodiment of the bill management unit in the rental management module of the management server.
9 is a diagram for explaining a user interface displayed on a terminal by a rental management module.
10 is a view of an embodiment of a non-payment management unit in a user interface for rental management.
11 is a diagram of an embodiment of a bill integrated management unit in a user interface for rental management.

Hereinafter, a rental contract management system for real estate according to the present invention will be described in more detail with reference to the accompanying drawings.

However, the embodiments described below are only intended to be described in detail so that those skilled in the art can easily practice the invention, thereby limiting the scope of protection of the present invention. doesn't mean

In the following description, when a part is said to be 'connected' to another part, this includes not only the case where it is directly connected but also the case where it is connected with another element or device in between. In addition, when a certain part 'includes' a certain component, this means that it may further include other components without excluding other components unless otherwise stated.

'Units' defined in the present invention may mean physically distinct memories or devices, and include cases implemented as algorithms as virtual devices.

Basically, the present invention is a contract management module that converts rental contracts for rental units into data and creates a power of attorney to perform the rental report processing on the real estate transaction management server, a rental management module that manages data on the current status of rental payments of rental units, and In the event that the set contract conditions are established, a real estate lease contract management system including a session management unit for switching the contract management module and the lease management module to control the interface of the lessor terminal is provided.

The object of rental applied in the present invention is usually described as an embodiment of a collective building having a plurality of divided living spaces, but various types of buildings such as apartments, residential and commercial buildings, offices, farms, factories, etc. It can be understood to include real estate and movable property capable of performing a cheonsei or monthly rental contract in any form.

In addition, the rental units described in the present invention may mean a unit for which one rental contract is made, for example, one room in a building. In addition, a rental group may be understood as a set of a plurality of rental units associated with one lessor or a lessor terminal, for example, one building or one floor having a plurality of rooms.

In addition, in the concept of the present invention, the conversion of the function of the contract management module and the rental management module is basically based on the management of the contract and the management of the rent for one rental unit, but depending on the case, the lessee or the rental unit It would be possible to make it work flexibly for sets as well.

Figure 2 is a conceptual diagram for explaining the rental contract management system for real estate of the present invention.

The management server 2000 functions to store, manage, and update information on the lease contract, information on the lessor and lessee, and information on the rental unit, and at the same time, the lessor terminal 100 and/or the lessee terminal 200 ) to visualize and implement the user interface.

The components of the management server 2000 can be implemented as computer readable codes on a computer readable recording medium, and the computer readable recording medium is any type of data that can be read by a computer system. includes a recording device of Examples of computer-readable recording media include ROM, RAM, CD-ROM, optical data storage devices, flash memories, and the like. The management server 2000 may be a server, PC, or microprocessor capable of exchanging information by being connected to one or more terminals by default, and may be a master server that performs management in a specific building or area in a management office and performs integrated processing. It may be configured including the case of being connected, and each component may be configured in one server in one embodiment, and may be configured in a plurality of servers or one or more servers and mobile terminals in another embodiment. am.

The management server 2000 assigns an identifier for the lessor, distinguishes the lessor terminal 100 from the rental unit, the rental group, and the lessee, forms a database, and matches the lessee and the lessee terminal for each rental unit according to the terms of the contract. can make it

Basically, the rental contract is entered into, and management of each rental unit starts at the time the contract is written and uploaded, and contract management module or rental management according to the conditions determined by the predetermined user interface input in the lessor terminal 100 or the session management unit. The operation of the module can be selected. A specific embodiment for this will be described later.

The lessor terminal 100 and the lessee terminal 200 target smart phones possessed by most of the population, and the user interface to be described in the present invention may operate on a display as an application or a web page. However, the terminals may include various devices capable of transmitting and receiving information with the management server 2000 through the relay unit 300 with a display and an input device, and may be, for example, a PC, tablet PC, laptop, etc. . In the present invention, these terminals are visualized to improve the recognition and operability of the user, more preferably the lessor, and manage each rental unit or a set of rental units grouped to the lessor or groups according to the status of rent collection, and information You can receive a command for transmission. A preferred embodiment in relation to such a user interface will be described later.

The relay unit 300 remotely stores and manages information from the lessor terminal 100 and/or the lessee terminal 200 and connects the management server 2000 for transmitting information to implement a user interface, and It may be a wired or wireless network of various types that can be connected to terminals having a display and an input device. This relay unit 3000 is a communication method provided by a mobile communication network including CDMA, WCDMA, HSDPA, GSM, Wibro, 3G, 4G, LTE, LTE CatM1, 5G, etc., Wi-Fi (Wireless Fidelity), Bluetooth (Bluetooth), Infrared (IrDA: Infrared Data Association), Wireless LAN (IEEE 802.11), SWAP (Shared Wireless Access Protocol), WPAN (Wireless Personal Area Network), Zigbee, LoRa (Long Range) Various methods such as a network may be applied.

Figure 3 is a block diagram for explaining an embodiment of the management server constituting the real estate rental contract management system according to the concept of the present invention.

The management server 2000 performs a function of communicating with one or more lessor terminals 100 and/or one or more lessee terminals 200 through the relay unit 300 and exchanging information related to the rental contract as described above. .

The communication unit 2010 may employ various communication methods for exchanging data with the lessor terminal 100, the lessee terminal 200, the relay unit 300, or an external server, and duplicate descriptions will be omitted.

The database 2100 performs a function of extracting and converting information managed in relation to a rental contract into data, matching the information, and storing the information. For one lessor identifier, one or more lessor terminals 100, one or more rental units, and/or one or more rental groups are allocated and stored. In addition, one or more rental units leased to one lessee identifier may be allocated and stored, and predetermined data nodes may be formed by matching with the lessor identifier. At this time, of course, a plurality of connection relationships may be formed by crossing between a plurality of lessors and a plurality of lessees. Information stored in the database 2100 will be described later.

In the concept of the present invention, the contract management module 2300 functions in relation to the conclusion, report, change or renewal of a contract, and inputs and outputs information from the lessor terminal 100 and/or the lessee terminal 200 through the interface control unit 2400. implements an interface for

In addition, the lease management module 2200 functions in relation to maintenance of the contract, payment of rent, payment of management fees, etc., and an interface for inputting and outputting information from the lessor terminal 100 and/or the lessee terminal 200 through the interface control unit 2400. implement

Switching between the modules can basically be determined through conditions such as a report on the conclusion of a contract or the arrival of a contract period. For this purpose, the session management unit 2500 functions. The system of the present invention provides a single lease contract and maintenance management integration platform and can manage a plurality of lease contracts. The conversion is basically a contract management module (2300) and a lease management module (2200 ), and only the contract management module functions for other lease contracts, and at the same time, only the lease management module can function for another lease contract.

The rental management module 2200 may include a rental ledger management unit 2210 for managing rental ledgers and a bill management unit 2220 capable of managing transmission of bills according to an additional concept of the present invention, and related thereto. Specific examples will be described later. The contract management module 2300 and the rental management module 2200 can share information or judgment results according to predetermined operating conditions, and this interlocking function can be achieved by the session management unit 2500.

Figure 4 is a block diagram showing an embodiment of the database in the real estate rental contract management system of the present invention.

As described above, for the functions of the contract management module 2300 and the rental management module 2200, the database 2100 performs a function of converting and managing predetermined information including contracts into data.

The database 2100 includes a document DB 2110 for storing and managing rental contracts and report-related documents, a building DB 2121 for storing and managing information on rental units and rental groups, and a lessor, lessee, and landlord terminal. 100 and the user DB 2122 for storing and managing information of the tenant terminal 200.

The document DB 2110 primarily stores contracts uploaded from the lessor terminal 100, but performs a function of managing documents related to contracts, such as a power of attorney and/or an identification card, which will be described later. Most of these document DB (2110) functions in the contract management module (2300), but the rental management module (2200) can call and manage them if necessary.

In addition, the building DB (2121) basically manages information such as the address, area, number of units, type of house, and number of rooms of the rental unit or rental group, and information extracted from the contract image of the document DB (2110) can be entered.

In addition, the user DB 2122 stores and manages the subjects of rental and rental, such as names, resident (corporate) registration numbers, addresses, and phone numbers of lessors and lessees. The information of the user DB 2122 may be information extracted from the contract image of the document DB 2110.

On the other hand, a contract details DB 2131 may be further included, and information related to the start date, end date, delivery date, and maintenance/renewal/cancellation of the contract may be managed separately from the contents written in the contract. Information in the contract DB 2131 may function as a major variable when switching modules in the session management unit 2500 .

In addition, a rent DB 2132 may be further included, and information on monthly (or unit period) rent, payment due date, prepayment and postpayment among the contents of the contract may be managed. In addition, the rent DB 2132 may further include information on an account for paying rent.

This rent DB (2132) can be used to extract key information when the function of the rental management module (2200). The rent DB 2132 may be linked with a financial server through the communication unit 2010 to automatically perform management of automatic withdrawal or processing of receipt or non-payment of the rent DB 2132 upon payment confirmation.

5 is a block diagram for explaining an embodiment of a contract management module according to the concept of the present invention.

The Housing Lease Protection Act amended in 2021 stipulates the housing lease reporting system, so-called monthly rent reporting system. Be sure to report it.

In the present invention, the contract management module 2300 functions first to manage the conclusion, change, renewal, termination, etc. of the contract before the lease management module 2200 operates for lease management from the conclusion of the contract, and the In order to meet compulsory regulations, it can perform the function of reporting on the lease contract as a proxy.

According to this concept, it is possible to manage all matters from the conclusion of the contract to reporting, management, and termination, so it should be noted that the efficiency of management as well as the convenience of the lessor's management can be dramatically improved. .

To this end, the real estate rental contract management system of the present invention is provided with an input unit 2310 in order to receive the details of the contract from the lessor terminal 100 and convert them into data in the document DB 2110, and the operation of the input unit 2310 As a result, the monthly rent management is actually initiated.

It may also be considered that the input unit 2310 of the present invention provides an electronic contract by providing a contract form according to standard terms and conditions, and prepares a contract in a manner in which descriptions are input and electronic signatures are received. However, as described above, in view of the conventional real estate transaction practice, the reality is that the confirmation of the sale and the conclusion of the contract are made offline, and there are overwhelmingly many cases in which the seal is sealed.

In consideration of this, the present invention preferably receives the image of the contract 110 from the lessor terminal 100 through the input unit 2310 and turns it into data, and extracts and manages information managed in the database 2100 therefrom. However, since it is efficient in terms of management that the real estate rental contract management system performs the report as an agent without the lessor needing to report directly, we will look at an embodiment of this in more detail.

The input unit 2310 may receive an identification card 120 in addition to the contract 110, and the identification card 120 may belong to the lessor and/or the lessee. Since this may be a document necessary for reporting to the real estate transaction management server by an agent, it may be stored in the document DB 2110. The input unit 2310 operates a predetermined camera module in the lessor terminal 100 or the lessee terminal 200 through the interface control unit 2400 to enable input of the contract 110 and the identification card 120.

On the other hand, the input unit 2310 receives the contract 110 and the identification card 120 as images through the camera function of the lessor terminal 100, and automatically extracts predetermined information in the process of converting the data into the database 2100. can be further provided. For example, by designating the common area of each contract as ROI (Region of Interest), information such as landlord, lessee, contract period, rent, rental unit, etc. (2122), contract details DB (2131) and / or rent DB (2132) will be able to transfer automatically.

The power of attorney generating unit 2320 is for proving the delegation of the authority to represent the monthly rent report, and may provide a format for preparing electronic documents. The power of attorney generating unit 2320 presents a form for inputting predetermined information to the lessor terminal 100 or the lessee terminal 200 by the interface control unit 2400, receives input for information, and returns the form to the document DB 2110. data can be made.

In order to prove the validity of the power of attorney generated by the power of attorney generator 2320, the signature unit 2330 functions, and the signature unit 2330 directly receives, for example, an image of a seal such as a seal through the input unit 2310, or , It can be replaced by receiving an electronic signature through the lessor terminal 100 or the lessee terminal 200 or the like. As described above, when the signature unit 2330 performs digital signature, it may be operated in conjunction with a server of an external signature certification authority. The power of attorney generating unit 2320 may finally generate one power of attorney image by fusing the input format and the electronic signature.

As above, the contract 110, the ID card 120, and the power of attorney created by the power of attorney generator 2320 and signature unit 2330 input from the input unit 2310 into the document DB 2110 are converted into data, and the report processing unit 2340 The real estate transaction management server 400 can be performed by proxy for reporting monthly rent.

Additionally, the report processing unit 2340 will be able to present the progress and completion of the report on monthly rent to the lessor and/or lessee in a text message, app push, or user interface method.

In addition, the renewal and change unit 2350 leases according to the decision of the session management unit 2500 when there is a reason such as the expiration of the contract period after the conclusion of the contract, the change of the subject of the right, or the change of the type or area of the rental unit. The management module 2200 returns to the contract management module 2300 to perform the function, and accordingly, each data of the database 2100 can be updated and managed.

6 is a block diagram for explaining an embodiment of a session management unit for switching between the modules.

The session management unit 2500 completes the reporting of the contract and lease management initiated by the input of the contract in the contract management module 2300, extracts information necessary for maintenance and converts it into data, and then returns to the lease management module 2200. It performs management of rent and management expenses, etc., and functions to determine conversion conditions, such as being returned to the contract management module 2300 and managed again if there is a reason such as change, termination, or renewal of the contract.

To this end, the session management unit 2500 basically includes a date management unit 2510, and the date management unit 2510 calculates the contract period designated from the contract details DB 2131, precisely the contract end date from the contract start date. In case the end date of the contract arrives in comparison with the current date, or if the date entered within the set period from the end date of the contract, renewal or termination of the contract can be managed.

In addition, it further includes a validity determining unit 2520, and the validity determining unit 2520 determines the contract management module 2300 when a predetermined contract cancellation or termination condition occurs in the course of operating the rental management module 2200. It can function to verify the validity of the contract by switching to a function. For example, when the rent is overdue for a predetermined period in the rental management module 2200, the validity judgment unit 2520 may function as it is considered that the contract termination condition has been satisfied.

According to the judgment results of the date management unit 2510 and the validity judgment unit 2520, the function conversion from the contract management module 2300 to the rental management module 2200 can be performed by the conversion unit 2530, and the conversion unit ( 2530) will be able to operate by organically connecting only the necessary components for each necessary condition of the contract management module 2300 and the rental management module 2200. The switching of functions between the contract management module 2300 and the rental management module 2200 by the conversion unit 2530 may be performed for each contract, and therefore, a plurality of rental contracts operate independently of each other as described above.

Figure 7 is a block diagram for explaining the configuration of the rental ledger management unit in the rental management module.

As described above, when the conclusion and report of the rental contract are completed, the rental management module 2200 starts rental management through predetermined data, and the rental ledger management unit 2210 mainly starts managing rent collection. The process of generating and transmitting the bill according to the lessor's choice will be described later.

The rental ledger management unit 2210 and the bill management unit 2220 may have a display screen controlled through the interface control unit 2400 in each terminal. However, in some cases, when the user drives the rental management system of the present invention as a mobile application program rather than through a web program, the interface control unit 2400 transmits at least control information for implementing the rent management user interface described above. may be understood as

The rental ledger management unit 2210 basically manages matters related to rent payment with data data from the rent DB 2132, and may include a schedule management unit 2213 for this purpose. The schedule management unit 2213 calls the contract due date for each rental unit on the time table and enables conversion such as scheduled display or unpaid display in comparison with the current date. At this time, as will be described later, in the setting of automatic billing, it can be called to enable automatic sending of bills at a set time according to the arrival of a due date. Here, the date managed by the schedule management unit 2213 may be a unit of shorter date than the date managed by the date management unit 2510 . That is, the schedule management unit 2213 manages the term of regular rent payment, and the date management unit 2510 manages the contract period or renewal date.

In addition, the rental ledger management unit 2210 may include a storage state switching unit 2214, which mainly converts the scheduled display state to the storage display, and the scheduled display state to the non-payment display state. It is possible to perform a conversion function from the non-payment display state to the receipt display state. The payment status conversion unit 2214 may perform a function of counting the number of non-payments.

In addition, the rental book management unit 2210 may further include a bill activating unit 2215, and as described above, if the due date is within the period set at the current time or is not paid by the schedule management unit 2213, each rental unit With the mark you will be able to activate the billing section item. An embodiment of the appearance of the lessor terminal 100 on the interface will be described later.

In addition, a toggle control unit 2216 may be further included, and conversion and update operations of the input and display of the toggle unit displayed on the user interface of the terminal may be interlocked.

8 is a block diagram for explaining the configuration of the bill management unit in the rental management module of the present invention.

The bill management unit 2220 may include, for example, a generation unit 2221 that generates a bill page for each rental unit in a state in which the rental payment due date is scheduled, and the bill generated by the generation unit 2221 is It can mainly include matters related to the rental unit (used space), payment deadline, monthly rental fee, monthly management fee, value-added tax amount, total amount paid, or greetings.

In addition, the bill management unit 2220 further includes a transmission unit 2222, and the transmission unit 2222 sends SMS, SNS, application operation, notification, etc. to the lessee terminal 200 according to the selection of the lessor terminal 100. Recognition can be made possible through various functions of At this time, in the state in which the bill transmission unit 1140 is activated by the bill activating unit 2215 as described above, the transmission unit 2222 transmits the lessee through the communication unit 2010 according to the arrival of the due date according to the user's input or automation setting. The bill generated by the generator 2221 is transmitted to the terminal 200 .

In addition, the bill management unit 2220 may further include an accounting unit 2223, and the accounting unit 2223 may perform processing or calculation of VAT items and non-tax items, management of unpaid months, management of total payment, and the like. You will be able to.

The information managed by the lease book management unit 2210 and the bill management unit 2220 is transmitted from the lessor terminal 100 and/or lessee terminal 200 to the user by the interface control unit 2400, and rent management of the real estate lease contract management system. It can be implemented as a user interface for

9 is a diagram for explaining a user interface displayed on a terminal by a rental management module.

As shown, each terminal, that is, the lessor terminal 100 and the lessee terminal 200 may each include a display 1000 capable of visualizing a user interface and receiving a predetermined touch input. In the display 1000, it can be implemented through a real-time reaction with the management server 2000.

Mainly, the interface visualized on the display 1000 may include a predetermined section at the bottom, which is defined as the menu display unit 1400. The menu display unit 1400 includes the rental ledger section 1410, and in particular, the lessor can check information on the rental contract and rent collection through the lessor terminal 100 and input information. The menu display unit 1400 uses the rental book section 1410 and/or the bill section and/or the section related to evidence such as tax calculators and/or the section related to coupons such as free passes and/or the use of services in the system such as connection to the customer center. It can be composed of related sections.

Each rental unit is grouped corresponding to one lessor terminal 100 or one lessor's ID, and such a rental group can be visualized and displayed as one rental management unit 1100. One rental group may be matched with the lessor terminal 100, or a plurality of rental groups may be matched in some cases. For example, one rental group can be one building unit as described above.

A building classification unit 1010 for displaying general information on rental groups may be disposed above the display area of the rental management unit 1100, and the building classification unit 1010 is not information about individual rental units, but rental. Displaying the total of the group's rent and/or administrative expenses is desirable for simplicity of information.

The total rent display unit 1011 displayed on one side of the building division unit 1010 may display, for example, the total rent collected in comparison to the sum of rents to be collected in the month in one building, and as shown, 4 If the total amount to be collected in the month is 4.87 million won, and the sum received at the present time is 1 million won, it may be displayed as 100/487.

In addition, the total management fee display unit 1012 displayed on the other side may display, for example, the total management fee to be collected in April compared to the sum of the management fee to be collected in the month in one building. If this value is 600,000 won and the sum stored at the present time is 100,000 won, it may be displayed as 10/60.

Hereinafter, the configuration of the rent management unit 1100 related to the addition of the toggle function will be reviewed.

The rent management unit 1100 arranges the rent information for each rental unit vertically and displays it on a single page, and performs the processing of rent collection and the sending of bills in a simple manner according to the lessor's choice. make it possible

In the city details, there are information rows for 6 rental units, and each rental payment period, basic information of the rental unit, rent, and confirmation items for receipt are included. In an embodiment of the present invention, rent may mean only rent agreed to be paid per predetermined time unit, and may include management fees.

In each rental unit row, the first column constitutes the payment date display unit 1111, and since monthly payment is premised in the basic embodiment of the present invention, displaying only the payment date for the month visually enhances recognition. As shown in the example, there is an intuitive advantage when the payment date and the day of the week are indicated together. The corresponding month is displayed on the total rent display unit 1011 or the total maintenance cost display unit 1012 of the building classification unit 1010.

In the next column, a unit display unit 1112 is configured, and the number of the building and the name or nickname of the tenant are memoized. A rental group, which is a set of the rental units, is displayed on the building classification unit 1010.

The payment date display unit 1111, unit display unit 1112, and monthly rent display unit 1113 are grouped and input is activated. For example, when a touch input is applied to the part, specific information of the rental unit may be activated and displayed in a pop-up manner. The popped-up information may be information such as contract details, payment date, rent, management fee, value-added tax, etc., and an embodiment thereof will be described later.

In addition, the other side of the group of the payment date display unit 1111, the unit display unit 1112, and the monthly rent display unit 1113 is configured with a rent toggle unit 1120 capable of receiving user input for rent. The rent toggle unit 1120 performs a function of immediately correcting the database of the management server 2000 while displaying the payment situation for the rent.

The payment date display unit 1111, the unit display unit 1112, the monthly rent display unit 1113, and the rent toggle unit 1120 constitute an information line, which is minimum exposure information for an individual rental unit, as one row.

The rent toggle unit 1120 defines three states, and can be divided into a receipt display 1121 in the first row, an unpaid display 1122 in the second row, and a scheduled display 1123 in the third row. . Each of the display states may be distinguished by color to improve intuition. In the illustrated embodiment, only the storage display 1121 is given a color and the other states are colorless to enhance recognition. However, the definition of the color varies depending on selection.

For example, the management server 2000 includes a schedule management unit, and when 0:00 is the payment date of the rental unit in the rental information database, it can be automatically switched to a scheduled display 1123 state and displayed on the interface. To this end, the management server 2000 may automatically switch to a scheduled display by including a storage state conversion unit. In some cases, the scheduled display 1123 may be understood as a concept of displaying the next payment date after the corresponding payment date when the payment date of the previous next meeting has elapsed and normal payment is confirmed. Regarding such a payment date, the schedule management unit 2213 functions as described above.

In addition, when 24:00 on the payment date has elapsed, the department storage state conversion unit can convert the state to non-payment indication 1122, and from this time, non-payment management is possible.

In the states of the scheduled display 1123 and non-payment display 1122, the bill delivery menu can be activated and the bill transmission unit 1140 can wait for input. It is as described above that this can be performed as a function of the bill activation unit of the management server (2000).

As shown, in the case of the first row (201), which has already been marked as receipt (1121) in the month, the bill transmission unit 1140 is inactive, and the non-payment mark (1122) and/or scheduled mark (1123). The input to send bills is activated only for tenancy units.

In one embodiment, in the case of the fourth row (No. 107), the bill transmission unit 1140 is not activated. This may be possible by setting the schedule management unit. For example, if the current date is within a set period (for example, within one week) of the individually set delivery date for the rental units, the bill transmission unit 1140 is activated so that the lessor can It is possible to enable bill transmission, and in the case of before that, only the status can be checked. The function of sending such bills can also be set as automated in individual rental ledger items, and related explanations will be given later.

In addition, the rent management unit 1100 may include an additional unit 1130 so that items for additional rental units may be added.

On the other hand, in the list of rental units, the sorting unit 1101 may be configured to sort the rental units in order of storage date or room number according to the user's selection.

10 is a diagram of an embodiment of a non-payment management unit in a user interface for rental management.

In the rental ledger section 1410, the non-payment management unit 1300 may be configured separately so that the entire object of non-payment can be checked at a glance.

From the point of view of the landlord, he will be more interested in the total amount of unpaid amount and the presence or absence of unpaid amount per month rather than the individual unpaid amount.

The total amount of receipts display unit 1301 displays the total amount to be collected in a bar form on a per-month (or quarterly or semiannual or annual) basis, and among them, the total amount received and unpaid amount are divided into areas so that they can be displayed at a glance. In the city state, the total amount of deposit is 600,000 won, and the unpaid amount is 600,000 won, which is the entire amount.

The payment, scheduled, and unpaid amounts may be displayed in different colors, eg, green for payment, yellow for scheduled, and red for unpaid, and the entire area of the bar is divided at 100%.

In addition, the non-payment management unit 1300 may include a unit division unit 1310 to display rental group information and items related to rent and management expenses in general. Here, the rental fee and the management fee may be displayed as a total amount compared to the total amount.

Below that, information on each rental unit may be displayed by configuring rows, and the payment date display unit 1111, unit display unit 1112, and monthly rent display unit 1113 may be configured in one row. The payment date display unit 1111, the unit display unit 1112, and the monthly rent display unit 1113 constitute a group and are activated with an input button, and specific inputs may be possible in individual ledger items as described above. As described above.

In addition, a non-payment toggle unit 1320 may be configured as the other side of the group of the payment date display unit 1111, unit display unit 1112, and monthly rent display unit 1113, and the non-payment toggle unit 1320 is rent toggle unit 1120 It can be operated according to the operation of the payment date display unit 1111, unit display unit 1112, and monthly rent display unit 1113, and descriptions overlapping with those of the rental management unit 1100 are omitted. At this time, it is preferable that the non-payment management unit 1300 displays the number of non-payments and/or the total amount of non-payment for each rental unit, and the bill transmission unit 1140 may display the number of non-payments together.

Unlike the rental management unit 1100, it may be desirable for the non-payment management unit 1300 to list only rental units that are in an unpaid state. Here, similarly to the rent management unit 1100, a sorting unit (reference number not indicated) may be configured to sort the rental units for unpaid management in order of storage date or room number.

In addition, the bill transmission unit 1140 may be activated and configured, and an additional unit 1130 may be added.

In some cases, it may be desirable to add a transmission button (reference number not indicated) capable of transmitting bills integrally to the lessee terminal 200 of unpaid rental units.

11 is a diagram of an embodiment of a bill integrated management unit in a user interface for rental management.

In the above, the rental ledger section 1410 has been described, and a concept that can intuitively display the rental status or storage status for each rental unit or rental group has been presented.

The bill section 1420 can perform the function of managing bills in an integrated manner, and in the case of scheduled display 1123 or unpaid display 1122 in the lease book section 1410, each bill transmission unit 1140 It is activated and individually requesting transmission is possible, and the bill management unit of the management server 2000 receives it and sends the bill to the lessee terminal 200 in various ways such as SMS or application or web page notification or SNS.

In the bill section 1420, the integrated bill management unit 1350 configures the information unit 1351 at the top to provide guidance on the types of information and input methods that are basically displayed. In the illustrated example, a guide for automatic sending of general bills or a guide for automatic generation of unpaid bills is presented, and therefore, the integrated bill management unit 1350 of the present invention provides a separate database for bills within the normal payment period and unpaid bills for which the due date has elapsed. It is possible to configure and set automatic transmission individually. Overall, it may be possible to consider sending bills in bulk, but depending on the characteristics of the rental building or the relationship between the lessor and the lessee, there may be cases where it is inappropriate to immediately notify and prompt for non-payment immediately after the due date, and considering this, the normal payment period It is better to set bills within and unpaid bills separately and individually.

The integrated bill management unit 1350 may configure the entire selection unit 1353 to directly select the entire rental group in a toggle method. In addition, by individually configuring the bill toggle unit 1352 for each rental unit, automatic bill delivery can be selected and released according to a toggle button input. At this time, overlapping descriptions of the payment date display unit 1111, unit display unit 1112, and monthly rent display unit 1113 constituting one column will be omitted.

In the illustrated example, two rental groups are shown divided, and a total selection unit 1353 for individually setting automatic transmission is configured in each rental group.

In some cases, it may be considered that a toggle button is configured to enable selection of all buildings assigned to a plurality of rental groups, that is, one lessor identifier.

User convenience can be increased because the above-described real estate rental contract management system of the present invention can effectively converge and operate offline contracts and online information input, reporting, and delegation processing on one platform. Nationally, there is an advantage in being able to accurately manage rent on a monthly basis.

In addition, lease management such as contract signing and maintenance as well as rent collection can be performed in an integrated manner, and the contract management module and lease management module can be distributed and operated in one system according to predetermined conditions, so the load on the system is small. Efficiency is dramatically improved.

In addition, even for multiple rental units, it is possible to intuitively check the arrival of rent payment, rent, and non-payment items in a lump sum, while it is possible to simply receive payment for each rental unit, change the status of non-payment, and update data. Convenience and efficiency are further improved.

In the above, the present invention has been described in detail based on examples and accompanying drawings. However, the scope of the present invention is not limited by the above embodiments and drawings, and the scope of the present invention will be limited only by the content described in the claims below.

100 ... lessor terminal 110 ... contract
120 ... identification 200 ... tenant terminal
300 ... relay department 400 ... housing management server
1000 ... display 1010 ... building division
1100 ... Rent Management Department 1120 ... Rent Toggle Department
1130 ... additional part 1140 ... transmission part
1210...Tenant Registration Department 1300...Unpaid Management Department
1320...Unpaid Toggle Department 1350...Invoice Integrated Management Department
1400 ... menu display section 1410 ... rental ledger section
1420 ... bill section 2000 ... management server
2010...Ministry of Communications 2100...Database
2110 ... Document DB 2121 ... Building DB
2122...User DB 2131...Contract DB
2132...Rent DB 2200...Rent management module
2210... Rental Book Management Department 2213... Schedule Management Department
2214 ... receipt state conversion unit 2215 ... bill activation unit
2216 ... toggle control unit 2220 ... bill management unit
2221 ... generation unit 2222 ... transmission unit
2223...accounting department 2300...contract management module
2310 ... input unit 2320 ... power of attorney generation unit
2330 ... signature section 2340 ... report processing section
2350 ... update and change unit 2400 ... interface control unit
2500... Session management department 2510... Date management department
2520 ... validity judgment unit 2530 ... conversion unit

Claims (7)

A communication unit 2010 connected to the lessor's terminal;
A database (2100) that converts and stores information on a rental contract into data;
A contract management module 2300 for receiving and managing matters related to the conclusion or renewal of a contract;
A rental management module (2200) for managing the payment due date and receipt of rent;
Including; session management unit 2500 for switching the functions of the contract management module and the rental management module according to set conditions;
The contract management module,
An input unit 2310 for receiving the contract image from the lessor terminal, and a report processing unit 2340 for reporting the rental contract information extracted from the contract received from the input unit to the real estate transaction management server Real estate rental contract management system.
According to claim 1,
The contract management module,
Management of real estate rental contracts including a power of attorney generator 2320 that provides a power of attorney format for proving the delegation of the monthly rent report to the lessor terminal, and a signature unit 2330 that performs an electronic signature to prove the validity of the power of attorney. system.
According to claim 1,
A real estate rental contract management system further comprising a session management unit (2500) for converting a function from a contract management module to a rental management module after the information on the rental contract is converted into data in the contract management module and the monthly rent report is made.
According to claim 3,
The session management unit,
A date management unit 2510 that judges whether to switch to the contract management module when the contract period expires while the rental management module is functioning, and a validity judgment unit that determines whether to switch to the contract management module if the rent is overdue during the set period. (2520) and a conversion unit (2530) that performs function conversion between the rental management module and the contract management module.
According to claim 3,
The rental management module,
Real estate having a rental account management unit 2210 that manages the payment due date of rent for each rental unit and whether or not the rent is received, and a bill management unit 2220 that creates a bill page for each rental unit and transmits it to the lessee terminal according to the selection of the lessor terminal 's rental contract management system.
According to claim 5,
A real estate lease contract management system further comprising: an interface controller 2400 for displaying the lease contract by the contract management module and the rent by the lease management module on the lessor terminal.
According to claim 6,
The interface displayed on the lessor terminal is,
A payment date display unit 1111 for displaying the due date of rent, a unit display unit 1112 for displaying identification information on the rental unit, a monthly rent display unit 1113 for displaying the rent value, and storage display by receipt input of the lessor terminal (1121) to change the status, but depending on whether the due date for each rental unit has passed in the schedule management unit, the scheduled display (1123) or non-payment display (1122) is switched and displayed, and the rent toggle unit 1120 waits for receipt input. A rental contract management system for real estate.

Images