WO2022224101A1 - Method and system for managing rental risks - Google Patents

Method and system for managing rental risks Download PDF

Info

Publication number
WO2022224101A1
WO2022224101A1 PCT/IB2022/053526 IB2022053526W WO2022224101A1 WO 2022224101 A1 WO2022224101 A1 WO 2022224101A1 IB 2022053526 W IB2022053526 W IB 2022053526W WO 2022224101 A1 WO2022224101 A1 WO 2022224101A1
Authority
WO
WIPO (PCT)
Prior art keywords
lessor
lessee
fulfilment
report
rental
Prior art date
Application number
PCT/IB2022/053526
Other languages
French (fr)
Inventor
Cataldo BOCCUNI
Original Assignee
A Future Company Holding S.R.L.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by A Future Company Holding S.R.L. filed Critical A Future Company Holding S.R.L.
Publication of WO2022224101A1 publication Critical patent/WO2022224101A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0645—Rental transactions; Leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the present invention relates, in general, to the real-estate field.
  • the present invention relates to a method and a system for managing rental risks.
  • rental contracts are subject to considerable risks as to payments and/or proper preservation of the goods that are present in the rented property.
  • lessors letting their real properties cannot adequately protect themselves by means of insurance and/or surety guarantees.
  • insurance and/or surety guarantees do not ensure full refund for damages suffered by the property or by the goods associated therewith.
  • the present invention provides a system for managing rental risks, comprising a computer equipped with a memory medium, said computer being configured for: obtaining a non-fulfilment report comprising: a reporter identification code associated with a lessee or a lessor; a contract identification code associated with a respective rental contract; accessing a contracts database, stored in the memory medium, to identify information associated with said rental contract; wherein said information associated with said rental contract comprises at least: a first identification key that univocally identifies said rental contract; a second identification key that univocally identifies said lessor; a third identification key that univocally identifies said lessee; identifying a non-fulfilling party as a function of said non-fulfilment report and said second identification key or said third identification key; obtaining a reliability coefficient associated with said non-fulfilling party; wherein said reliability coefficient is representative of the non-fulfilment risk associated with said non-fulfilling party;
  • said reporter identification code is associated with a lessor and said non-fulfilment notification further comprises a first document concerning at least one of the following events: non-payments; unauthorized and/or unlawful occupation of the property; partial or total subletting of the property to third parties; deterioration of the property and/or of goods associated with the property; theft of goods associated with the property;
  • said reporter identification code is associated with a lessee and said non-fulfilment notification further comprises a first document concerning at least one of the following events: verification of non-compliant property; failure to comply with contractual times; failure to comply with the period of notice of termination; presence of hidden defects; failure to comply with contractual terms; delayed or non-execution of works lying within the lessor's province; charging of undue expenses; unregistered rental contract; no communication of the data concerning the registration of the rental contract; caution money not returned or only partially returned.
  • said computer is further configured for: notifying said non-fulfilment report to said lessor associated with said second identification key; notifying said non-fulfilment report to said lessee associated with said third identification key; receiving a reply to said notification from said non fulfilling party; waiting a predefined time interval for receiving, from said non-fulfilling party, at least one second document demonstrating the resolution of the events reported in said first document.
  • said computer is configured for waiting a predefined time interval of 15 to 30 days for receiving said second document from said non-fulfilling party.
  • said non-fulfilling party is a lessor and said reliability coefficient is representative of the lessor's real estate and/or the number of rented real properties associated with the lessor.
  • said non-fulfilling party is a lessee and said reliability coefficient is representative of one or more of the following parameters: lessee's personal information, history of rental contracts associated with the lessee, lessee type.
  • said computer is configured for updating the reliability coefficient associated with said non-fulfilling party as a function of each non-fulfilment report received within a time interval of 5 to 10 years from the current date.
  • Figure 1 shows a block diagram of a system for managing rental risks according to the present invention
  • Figure 2 shows an exemplary databank for managing rental risks
  • Figure 3 is a partial flow chart of a method for managing rental risks in accordance with the present invention.
  • reference numeral 100 designates a system for managing rental risks.
  • the system 100 comprises a computer 10 having access to a memory medium 20.
  • the computer 10 is, for example, a server.
  • the memory medium 20 stores a lessors database 21 and a lessees database 22.
  • a lessor or a lessee can access the server 10 via the Internet network.
  • a lessor or a lessee can access the server 10 by means of a user device 1, 2, 3, preferably subject to authentication.
  • the user devices 1, 2, 3 may be a laptop, a personal computer, or a smartphone.
  • the lessors database 21 comprises a plurality of lessor records; the lessees database 22 comprises a plurality of lessee records.
  • each record in the lessors database 21 comprises: a name; a tax code or a VAT number; a mail address (e.g. an e-mail address or a certified mail address); cadastral and commercial data concerning the rented real properties; a detailed description of the rented real properties.
  • the detailed description of the rented real properties comprises one or more of the following pieces of information: condition of use, available systems, system condition, state of preservation of the property as a whole.
  • each record in the lessees database 22 comprises: a name; a tax code and/or a VAT number; a mail address (e.g. an e-mail address or a certified mail address); personal and/or family and/or income data.
  • a name e.g. an e-mail address or a certified mail address
  • a mail address e.g. an e-mail address or a certified mail address
  • the personal and/or family and/or income data may comprise a payslip, a family status declaration or, for a legal person, a company registration report.
  • each record in the lessees database 22 comprises one or more of the following: a letter of recommendation and/or introduction by previous lessors registered in the lessors database; a letter of recommendation by credit and/or financing institutions.
  • the server 10 is configured for associating a lessor reliability coefficient with each lessor.
  • each record in the lessors database 21 comprises a respective lessor reliability coefficient.
  • each lessor reliability coefficient is computed as a function of the cadastral and/or commercial data of the rented real properties and/or the detailed description of the rented real properties.
  • the server 10 preferably receives and evaluates the following parameters:
  • the server 10 assigns a score of 80 points to areas up to 200 square metres, and for every additional 50 square meters the server 10 assigns 2.5 additional points, up to a maximum of 100 points).
  • real property category e.g. 50 points for a luxury property, 20 points for a popular property
  • - number of years of activity as a lessor e.g. 20 points for 1 to 5 years of activity, 40 points for 6 to 10 years of activity, 60 points for 11 to 15 years of activity, 80 points for 16 to 20 years of activity, 100 points for 20 or more years of activity.
  • - lessor type e.g. single natural person, group of natural persons, legal person in a partnership or a corporation, a score being assigned according to the lessor's professionality (e.g. a higher score is assigned to companies, while a lower score is assigned to a single natural person).
  • the lessor can provide one or more letters of recommendation.
  • a positive score e.g. 10 points
  • a positive score is assigned to each favourable letter of recommendation.
  • the server 10 preferably receives information about the following categories: lessor's real estate, lessor's history, and any letters of recommendation.
  • the server 10 assigns a numerical score to each one of such categories and computes a respective lessor reliability coefficient as a function of such numerical scores.
  • the server 10 may assign a different weight to each category (lessor's real estate, lessor's history, and any letters of recommendation) associated with a respective lessor.
  • the server 10 receives, via a user device 1 of the lessor, the information necessary for computing the respective lessor reliability coefficient.
  • the lessor can remotely access the server 10 by means of a laptop (user device 1) and upload the information necessary for computing the lessor reliability coefficient by filling in a suitable on-line form.
  • the server 10 associates an alphanumerical code with such coefficient.
  • an alphanumerical code may consist of, for example, the following characters A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, E, associated with decreasing numerical intervals (e.g. A+ corresponds to the 1,000 to 900 point interval, A corresponds to the 1,000 to 900 point interval, and so forth).
  • the server 10 is further configured for associating a respective lessee reliability coefficient with each record in the lessees database 22.
  • each record in the lessees database 22 comprises a respective lessee reliability coefficient computed as described above.
  • each lessee reliability coefficient is computed as a function of the personal and/or family and/or income data. Even more preferably, each lessee coefficient is computed also on the basis of the letter of recommendation and/or introduction by previous lessors registered in the lessors database and/or the letter of recommendation by credit and/or financing institutions.
  • the lessee can remotely access the server 10 by means of a laptop (user device 2) and upload the information necessary for computing the lessee reliability coefficient by filling in a suitable on-line questionnaire.
  • the server 10 preferably receives and evaluates the following parameters:
  • - personal and/or income data e.g. a single-income large family is assigned a lower score than a family of two individuals having two distinct incomes
  • the server 10 will assign 20 points for 1 to 5 years, 40 points for 6 to 10 years, 60 points for 11 to 15 years, 80 points for 16 to 20 years, 100 points for 20 or more years);
  • the server 10 will assign 20 points for every group of 10 contracts, up to a maximum of 100 points);
  • the lessee can send one or more letters of recommendation to the server 10.
  • the server 10 will assign additional points for each favourable letter of recommendation by: previous and current lessors; credit institutions; insurance companies.
  • the server 10 will associate additional points with such letters of recommendation sent by a lessee only if they can be verified.
  • the server 10 preferably receives information about the following categories: lessee's personal information, history of rental contracts associated with the lessee, lessee type, and any letters of recommendation.
  • the server 10 preferably assigns a numerical score to each one of such categories and computes a respective lessee reliability coefficient as a function of such numerical scores.
  • the server 10 may assign a different weight to each category associated with the lessee.
  • the server 10 receives from the lessee the information necessary for computing the respective lessee reliability coefficient.
  • the server 10 associates an alphanumerical code with such coefficient.
  • an alphanumerical code may consist of, for example, the following characters A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, E, associated with decreasing numerical intervals (e.g. A+ corresponds to the 1,000 to 900 point interval, A corresponds to the 1,000 to 900 point interval, and so forth).
  • the server 10 is configured for registering a rental contract.
  • the server 10 is configured for accessing a rental contracts database 22.
  • the rental contracts database 23 comprises a plurality of rental contract records.
  • each rental contract record is associated with at least one lessor record and at least one lessee record, respectively.
  • the rental contracts database 23 is preferably stored in the memory medium 20.
  • a lessee and/or a lessor can:
  • a copy in digital format of the rental contract is uploaded to the server 10.
  • the server 10 stores it into the contracts database 23.
  • the server 10 creates a rental contract record containing:
  • the first identification key is an alphanumerical code.
  • the second identification key corresponds to the lessor's tax code.
  • the third identification key corresponds to the lessee's tax code.
  • the server 10 stores into the contracts database the available contractual details and associates them with the respective contract record.
  • the rental contract and its contractual details are entered by the lessor associated with such contract.
  • the server 10 will send a notification to the lessee (e.g. the server 10 will send an e-mail confirming the registration of the contract).
  • the server 10 is configured to receive a non-fulfilment report (step 101).
  • a non-fulfilment report can be sent to the server 10.
  • reporter the lessor or the lessee who sends a non-fulfilment report.
  • the non-fulfilment report comprises: a reporter identification code associated with a lessee or a lessor (e.g. the reporter identification code may correspond to either the second identification key (for a lessor) or the third identification key (for a lessee); a contract identification code associated with a respective rental contract (e.g. the contract identification code corresponds to the first identification key).
  • the non-fulfilment report comprises also a first document.
  • the reporter identification code is associated with a lessor and comprises also the first document, such first document concerns at least one of the following events: non-payments by the lessee; unauthorized and/or unlawful occupation of the property; partial or total subletting of the property to third parties; deterioration of the property and/or of goods associated with the property; theft of goods associated with the property;
  • the reporter identification code when associated with a lessee and comprises also the first document, such first document concerns at least one of the following events: verification of non-compliant property; failure to comply with contractual times; failure to comply with the period of notice of termination; presence of hidden defects; failure to comply with contractual terms; delayed or non-execution of works lying within the lessor's province; charging of undue expenses; unregistered rental contract; no communication of the data concerning the registration of the rental contract; caution money not returned or only partially returned.
  • the first document associated with a non- fulfilment report is a document that certifies the failure to comply with the contractual details recorded in the contracts database 23 by either the lessee or the lessor.
  • non-fulfilment reports can only be accepted by the server 10 if they can be verified within sixty days from the event date.
  • the server 10 identifies - by means of the contract identification code - the lessee and the lessor associated with the rental contract (step 102), and notifies the non-fulfilment report to both the lessee and the lessor associated with the rental contract (step 103).
  • the server 10 will send - by means of the respective mail address - a communication containing the non-fulfilment report and the first document (when available).
  • the non-fulfilling lessee or the non-fulfilling lessor can send a reply to the above-mentioned notification.
  • a non-fulfilling lessee or a non-fulfilling lessor will be generally referred to as "non-fulfilling party”.
  • the non-fulfilling party can attach to its reply a second document demonstrating the resolution of the event referred to in the non-fulfilment report.
  • the server 10 is configured for receiving the reply sent by the non-fulfilling party.
  • the reply may be sent via electronic mail (e.g. by means of a certified mail address), or may be uploaded to a reserved area by means of the user terminal owned by the non-fulfilling party.
  • the server 10 is configured for waiting a predefined time interval for receiving the second document (step 104).
  • the predefined time interval is in the range of 15 to 30 days from the notification transmission date.
  • the server 10 is configured for sending a second notification asking for the second document, and will then wait a second time interval from the date of transmission of such second notification.
  • the second predefined time interval is in the range of 10 to 30 days from the date of transmission of the second notification.
  • the server 10 will make such documents available to an operator.
  • the server starts a step of verifying the non- fulfilment report 105, wherein an operator compares the first document, the second document, and the contractual details associated with the lessee and the lessor identified in step 102. Based on such comparison, the operator will then determine whether to approve or cancel the non-fulfilment report.
  • the server 10 is configured for re computing the reliability coefficient associated with the non fulfilling party (step 106).
  • the server 10 will start a step of re-computing the reliability coefficient associated with the non-fulfilling party 106.
  • the server 10 is configured for obtaining the reliability coefficient associated with the non-fulfilling party (lessee or lessor) and for associating a score to the approved non-fulfilment report.
  • the server 10 associates a score to the non- fulfilment report as a function of the seriousness of the event that generated the non-fulfilment report.
  • score associated with a respective approved non-fulfilment report, will then be used in order to reduce the (lessee or lessor) reliability coefficient associated with the non-fulfilling party.
  • the reliability coefficient associated with the non-fulfilling party is reduced by 100 points.
  • the server 10 will reduce by half, or set to zero, the reliability coefficient associated with such non-fulfilling party.
  • each reliability coefficient associated with a respective lessee or a respective lessor is computed as a function of each non-fulfilment report received within a time interval of 5 to 15 years, more preferably 10 years.
  • the present invention preferably allows knowing the lessee reliability coefficient of a lessee associated with a lessee record in the lessees database 22 prior to signing a rental contract.
  • the present invention preferably allows knowing the lessor reliability coefficient of a lessor associated with a lessor record in the lessors database 21 prior to signing a rental contract.
  • the present invention provides access to the server 10 to third parties, e.g. credit institutions, financing organizations and/or insurance companies.
  • third parties e.g. credit institutions, financing organizations and/or insurance companies.
  • Such third parties can, subject to authentication, gain access to the lessor reliability coefficient or the lessee reliability coefficient.
  • such third parties can reduce the risk of proposing insurance and/or loan contracts to potentially defaulting customers.
  • the present invention offers some important advantages.
  • the system 100 makes for a more transparent, more honest, qualitatively better and more secure rental market.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Coin-Freed Apparatuses For Hiring Articles (AREA)

Abstract

Described herein is a system for managing rental risks, comprising a computer equipped with a memory medium and configured for : obtaining a non-fulfilment report comprising : a reporter identification code associated with a lessee or a lessor; a contract identification code associated with a respective rental contract; accessing a contracts database, stored in said memory medium, to identify information associated with said rental contract and comprising at least : a first identification key that univocally identifies said rental contract; a second identification key that univocally identifies said lessor; a third identification key that univocally identifies said lessee; identifying a non- fulfilling party as a function of said non-fulfilment report and said second identification key or said third identification key; obtaining a reliability coefficient associated with said non-fulfilling party and representative of the non-fulfilment risk associated with said non-fulfilling party; updating said reliability coefficient as a function of said non-fulfilment report.

Description

Description of Industrial Invention:
"METHOD AND SYSTEM FOR MANAGING RENTAL RISKS"
DESCRIPTION
Field of the invention
The present invention relates, in general, to the real-estate field. In particular, the present invention relates to a method and a system for managing rental risks.
Description of the prior art
As is known, the real-estate market is very important.Nowadays, natural and legal persons rent real properties by signing short-term or long-term rental contracts.
The Applicant has noticed that real-estate rental contracts suffer from a number of criticalities.
For example, rental contracts are subject to considerable risks as to payments and/or proper preservation of the goods that are present in the rented property. Moreover, lessors letting their real properties cannot adequately protect themselves by means of insurance and/or surety guarantees. As a matter of fact, insurance and/or surety guarantees do not ensure full refund for damages suffered by the property or by the goods associated therewith.
Disadvantageously, when a rental contract is entered into, the lessor can only ask the lessee to provide some guarantee documents such as, for example, their payslip, information about their bank account average daily balance, etc., in order to evaluate the risks incurred prior to signing the rental contract.
Brief description of the invention It is the object of the present invention to provide a method and a system for managing rental risks which can overcome the above- mentioned problems.
In particular, the present invention provides a system for managing rental risks, comprising a computer equipped with a memory medium, said computer being configured for: obtaining a non-fulfilment report comprising: a reporter identification code associated with a lessee or a lessor; a contract identification code associated with a respective rental contract; accessing a contracts database, stored in the memory medium, to identify information associated with said rental contract; wherein said information associated with said rental contract comprises at least: a first identification key that univocally identifies said rental contract; a second identification key that univocally identifies said lessor; a third identification key that univocally identifies said lessee; identifying a non-fulfilling party as a function of said non-fulfilment report and said second identification key or said third identification key; obtaining a reliability coefficient associated with said non-fulfilling party; wherein said reliability coefficient is representative of the non-fulfilment risk associated with said non-fulfilling party;
- updating said reliability coefficient associated with said non-fulfilling party as a function of said non-fulfilment report.
Preferably, said reporter identification code is associated with a lessor and said non-fulfilment notification further comprises a first document concerning at least one of the following events: non-payments; unauthorized and/or unlawful occupation of the property; partial or total subletting of the property to third parties; deterioration of the property and/or of goods associated with the property; theft of goods associated with the property;
- damages to the property and/or to third parties; failure to comply with the period of notice of termination; unauthorized registration of personal and tax residences. Alternatively, said reporter identification code is associated with a lessee and said non-fulfilment notification further comprises a first document concerning at least one of the following events: verification of non-compliant property; failure to comply with contractual times; failure to comply with the period of notice of termination; presence of hidden defects; failure to comply with contractual terms; delayed or non-execution of works lying within the lessor's province; charging of undue expenses; unregistered rental contract; no communication of the data concerning the registration of the rental contract; caution money not returned or only partially returned. Preferably, said computer is further configured for: notifying said non-fulfilment report to said lessor associated with said second identification key; notifying said non-fulfilment report to said lessee associated with said third identification key; receiving a reply to said notification from said non fulfilling party; waiting a predefined time interval for receiving, from said non-fulfilling party, at least one second document demonstrating the resolution of the events reported in said first document.
Preferably, said computer is configured for waiting a predefined time interval of 15 to 30 days for receiving said second document from said non-fulfilling party.
Preferably, said non-fulfilling party is a lessor and said reliability coefficient is representative of the lessor's real estate and/or the number of rented real properties associated with the lessor.
Preferably, said non-fulfilling party is a lessee and said reliability coefficient is representative of one or more of the following parameters: lessee's personal information, history of rental contracts associated with the lessee, lessee type.
Preferably, said computer is configured for updating the reliability coefficient associated with said non-fulfilling party as a function of each non-fulfilment report received within a time interval of 5 to 10 years from the current date.
Brief description of the drawings
The invention will become more apparent in light of the following detailed description, provided merely by way of non limiting example, wherein reference will be made to the annexed drawings, wherein:
Figure 1 shows a block diagram of a system for managing rental risks according to the present invention;
Figure 2 shows an exemplary databank for managing rental risks; Figure 3 is a partial flow chart of a method for managing rental risks in accordance with the present invention.
Detailed description of some preferred embodiments
With reference to Figure 1, reference numeral 100 designates a system for managing rental risks.
The system 100 comprises a computer 10 having access to a memory medium 20. The computer 10 is, for example, a server.
Preferably, the memory medium 20 stores a lessors database 21 and a lessees database 22.
Preferably, a lessor or a lessee can access the server 10 via the Internet network. For example, a lessor or a lessee can access the server 10 by means of a user device 1, 2, 3, preferably subject to authentication.
Secure authentication methods for connecting to a server are known and will not be described in detail hereinafter.
The user devices 1, 2, 3 may be a laptop, a personal computer, or a smartphone.
Preferably, as shown in Figure 2, the lessors database 21 comprises a plurality of lessor records; the lessees database 22 comprises a plurality of lessee records.
Preferably, each record in the lessors database 21 comprises: a name; a tax code or a VAT number; a mail address (e.g. an e-mail address or a certified mail address); cadastral and commercial data concerning the rented real properties; a detailed description of the rented real properties.
For example, the detailed description of the rented real properties comprises one or more of the following pieces of information: condition of use, available systems, system condition, state of preservation of the property as a whole.
Preferably, each record in the lessees database 22 comprises: a name; a tax code and/or a VAT number; a mail address (e.g. an e-mail address or a certified mail address); personal and/or family and/or income data.
For example, the personal and/or family and/or income data may comprise a payslip, a family status declaration or, for a legal person, a company registration report.
Even more preferably, each record in the lessees database 22 comprises one or more of the following: a letter of recommendation and/or introduction by previous lessors registered in the lessors database; a letter of recommendation by credit and/or financing institutions.
Preferably, the server 10 is configured for associating a lessor reliability coefficient with each lessor. In other words, each record in the lessors database 21 comprises a respective lessor reliability coefficient.
Preferably, each lessor reliability coefficient is computed as a function of the cadastral and/or commercial data of the rented real properties and/or the detailed description of the rented real properties.
For example, in order to compute the lessor reliability coefficient, the server 10 preferably receives and evaluates the following parameters:
- real estate, assessed on the basis of one or more of the following parameters:
- rented/rentable square meters (e.g. the server 10 assigns a score of 80 points to areas up to 200 square metres, and for every additional 50 square meters the server 10 assigns 2.5 additional points, up to a maximum of 100 points).
- real property category (e.g. 50 points for a luxury property, 20 points for a popular property);
- additional services associated with the real property (e.g. air conditioning system, home automation system, etc.; 10 points are assigned for each available service);
- geographic area where the real property is located;
- information about the lessor's history, assessed on the basis of one or more of the following parameters:
- number of years of activity as a lessor (e.g. 20 points for 1 to 5 years of activity, 40 points for 6 to 10 years of activity, 60 points for 11 to 15 years of activity, 80 points for 16 to 20 years of activity, 100 points for 20 or more years of activity).
- number of managed rental contracts (e.g. 20 points are assigned for every group of 10 contracts);
- lessor type, e.g. single natural person, group of natural persons, legal person in a partnership or a corporation, a score being assigned according to the lessor's professionality (e.g. a higher score is assigned to companies, while a lower score is assigned to a single natural person).
Preferably, the lessor can provide one or more letters of recommendation. A positive score (e.g. 10 points) is assigned to each favourable letter of recommendation.
In other words, for each lessor the server 10 preferably receives information about the following categories: lessor's real estate, lessor's history, and any letters of recommendation. The server 10 assigns a numerical score to each one of such categories and computes a respective lessor reliability coefficient as a function of such numerical scores. Optionally, the server 10 may assign a different weight to each category (lessor's real estate, lessor's history, and any letters of recommendation) associated with a respective lessor.
Preferably, the server 10 receives, via a user device 1 of the lessor, the information necessary for computing the respective lessor reliability coefficient. For example, the lessor can remotely access the server 10 by means of a laptop (user device 1) and upload the information necessary for computing the lessor reliability coefficient by filling in a suitable on-line form.
Preferably, after having computed the lessor reliability coefficient of a respective lessor, the server 10 associates an alphanumerical code with such coefficient. For example, considering a range from 1 to 1,000 points for the lessor reliability coefficient, the server 10 will associate an alphanumerical code with such lessor reliability coefficient. Such alphanumerical code may consist of, for example, the following characters A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, E, associated with decreasing numerical intervals (e.g. A+ corresponds to the 1,000 to 900 point interval, A corresponds to the 1,000 to 900 point interval, and so forth).
Advantageously, such alphanumerical code ensures an immediate understanding of the lessor's reliability.
Preferably, the server 10 is further configured for associating a respective lessee reliability coefficient with each record in the lessees database 22.
In other words, each record in the lessees database 22 comprises a respective lessee reliability coefficient computed as described above.
Preferably, each lessee reliability coefficient is computed as a function of the personal and/or family and/or income data. Even more preferably, each lessee coefficient is computed also on the basis of the letter of recommendation and/or introduction by previous lessors registered in the lessors database and/or the letter of recommendation by credit and/or financing institutions.
For example, the lessee can remotely access the server 10 by means of a laptop (user device 2) and upload the information necessary for computing the lessee reliability coefficient by filling in a suitable on-line questionnaire.
For example, in order to compute the lessee reliability coefficient, the server 10 preferably receives and evaluates the following parameters:
- lessee's personal information:
- personal and/or income data (e.g. a single-income large family is assigned a lower score than a family of two individuals having two distinct incomes);
- lessee's history:
- how long the lessee has been renting property (e.g. the server 10 will assign 20 points for 1 to 5 years, 40 points for 6 to 10 years, 60 points for 11 to 15 years, 80 points for 16 to 20 years, 100 points for 20 or more years);
- number of rental contracts not interrupted prior to their natural termination (e.g. the server 10 will assign 20 points for every group of 10 contracts, up to a maximum of 100 points);
- lessee type:
- single natural person, group of natural persons, legal person in a partnership or a corporation (e.g. a higher score is assigned to companies, while a lower score is assigned to a single natural person).
Preferably, the lessee can send one or more letters of recommendation to the server 10. The server 10 will assign additional points for each favourable letter of recommendation by: previous and current lessors; credit institutions; insurance companies.
Preferably, the server 10 will associate additional points with such letters of recommendation sent by a lessee only if they can be verified.
In other words, for each lessee the server 10 preferably receives information about the following categories: lessee's personal information, history of rental contracts associated with the lessee, lessee type, and any letters of recommendation. The server 10 preferably assigns a numerical score to each one of such categories and computes a respective lessee reliability coefficient as a function of such numerical scores. Optionally, the server 10 may assign a different weight to each category associated with the lessee.
Preferably, the server 10 receives from the lessee the information necessary for computing the respective lessee reliability coefficient.
Preferably, after having computed the lessee reliability coefficient of a respective lessee, the server 10 associates an alphanumerical code with such coefficient. For example, considering a range from 1 to 1,000 points for the lessee reliability coefficient, the server 10 will associate an alphanumerical code with such lessee reliability coefficient. Such alphanumerical code may consist of, for example, the following characters A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, E, associated with decreasing numerical intervals (e.g. A+ corresponds to the 1,000 to 900 point interval, A corresponds to the 1,000 to 900 point interval, and so forth).
Advantageously, such alphanumerical code ensures an immediate understanding of the lessee's reliability.
It should be noted that both the lessor reliability coefficient and the lessee reliability coefficient are representative of the non-fulfilment risk associated with the lessor and the lessee, respectively. According to the present invention, the server 10 is configured for registering a rental contract. In particular, the server 10 is configured for accessing a rental contracts database 22.
The rental contracts database 23 comprises a plurality of rental contract records. Preferably, each rental contract record is associated with at least one lessor record and at least one lessee record, respectively.
The rental contracts database 23 is preferably stored in the memory medium 20.
For example, after having entered into a rental contract (e.g. a real property rental contract), a lessee and/or a lessor can:
- access the server 10 by means of a personal device 1, 2, 3;
- enter the information necessary for creating a respective record in the lessees database 22 and/or a respective record in the lessors database 21, if not already present; and/or
- enter contractual terms, such as, for example, property code, contract duration, agreed rent, etc.
Preferably, a copy in digital format of the rental contract is uploaded to the server 10.
Hereafter, the contractual terms and/or the copy of the rental contract will be generally referred to as "contractual details".
Once the above-mentioned information about a rental contract has been entered, the server 10 stores it into the contracts database 23. In other words, the server 10 creates a rental contract record containing:
- a first identification key that univocally identifies the rental contract;
- a second identification key that univocally identifies the lessor registered in the lessors database;
- a third identification key that univocally identifies the lessee registered in the lessees database. Preferably, the first identification key is an alphanumerical code.
Preferably, the second identification key corresponds to the lessor's tax code.
Preferably, the third identification key corresponds to the lessee's tax code.
Preferably, the server 10 stores into the contracts database the available contractual details and associates them with the respective contract record.
Preferably, the rental contract and its contractual details are entered by the lessor associated with such contract. When a new rental contract is entered into the contracts database, the server 10 will send a notification to the lessee (e.g. the server 10 will send an e-mail confirming the registration of the contract).
According to the present invention, with reference to Figure 3, the server 10 is configured to receive a non-fulfilment report (step 101). In particular, in the event of non-fulfilment of the terms of a rental contract by either a lessee or a lessor, a non-fulfilment report can be sent to the server 10.
Hereafter, the lessor or the lessee who sends a non-fulfilment report will be generally referred to as "reporter".
The non-fulfilment report comprises: a reporter identification code associated with a lessee or a lessor (e.g. the reporter identification code may correspond to either the second identification key (for a lessor) or the third identification key (for a lessee); a contract identification code associated with a respective rental contract (e.g. the contract identification code corresponds to the first identification key).
Preferably, the non-fulfilment report comprises also a first document. Preferably, when the reporter identification code is associated with a lessor and comprises also the first document, such first document concerns at least one of the following events: non-payments by the lessee; unauthorized and/or unlawful occupation of the property; partial or total subletting of the property to third parties; deterioration of the property and/or of goods associated with the property; theft of goods associated with the property;
- damages to the property and/or to third parties; failure to comply with the period of notice of termination; unauthorized registration of personal and tax residences.
Alternatively, when the reporter identification code is associated with a lessee and comprises also the first document, such first document concerns at least one of the following events: verification of non-compliant property; failure to comply with contractual times; failure to comply with the period of notice of termination; presence of hidden defects; failure to comply with contractual terms; delayed or non-execution of works lying within the lessor's province; charging of undue expenses; unregistered rental contract; no communication of the data concerning the registration of the rental contract; caution money not returned or only partially returned.
In other words, the first document associated with a non- fulfilment report is a document that certifies the failure to comply with the contractual details recorded in the contracts database 23 by either the lessee or the lessor. Preferably, non-fulfilment reports can only be accepted by the server 10 if they can be verified within sixty days from the event date.
Preferably, after receiving a non-fulfilment report, the server 10 identifies - by means of the contract identification code - the lessee and the lessor associated with the rental contract (step 102), and notifies the non-fulfilment report to both the lessee and the lessor associated with the rental contract (step 103).
For example, once it has identified the lessee and the lessor associated with the rental contract referred to in the non-fulfilment report, the server 10 will send - by means of the respective mail address - a communication containing the non-fulfilment report and the first document (when available).
Preferably, the non-fulfilling lessee or the non-fulfilling lessor can send a reply to the above-mentioned notification. Hereafter, a non-fulfilling lessee or a non-fulfilling lessor will be generally referred to as "non-fulfilling party".
In particular, the non-fulfilling party can attach to its reply a second document demonstrating the resolution of the event referred to in the non-fulfilment report.
Preferably, the server 10 is configured for receiving the reply sent by the non-fulfilling party. For example, the reply may be sent via electronic mail (e.g. by means of a certified mail address), or may be uploaded to a reserved area by means of the user terminal owned by the non-fulfilling party.
Preferably, the server 10 is configured for waiting a predefined time interval for receiving the second document (step 104). In particular, the predefined time interval is in the range of 15 to 30 days from the notification transmission date.
Alternatively, if the non-fulfilling party sends a reply before sending the second document, the server 10 is configured for sending a second notification asking for the second document, and will then wait a second time interval from the date of transmission of such second notification. For example, the second predefined time interval is in the range of 10 to 30 days from the date of transmission of the second notification.
Preferably, at the end of step 104, once both the first document and the second document have been received, the server 10 will make such documents available to an operator.
Preferably, the server starts a step of verifying the non- fulfilment report 105, wherein an operator compares the first document, the second document, and the contractual details associated with the lessee and the lessor identified in step 102. Based on such comparison, the operator will then determine whether to approve or cancel the non-fulfilment report.
When a non-fulfilment report is approved at step 104, or if the non-fulfilling party has not sent the above-mentioned second document in time or at all, then the server 10 is configured for re computing the reliability coefficient associated with the non fulfilling party (step 106).
For example, in the case wherein a lessee, associated with a respective lessee reliability coefficient, has been reported as being a non-fulfilling lessee by means of a non-fulfilment report, and such report has been approved at step 105, then the server 10 will start a step of re-computing the reliability coefficient associated with the non-fulfilling party 106. In particular, the server 10 is configured for obtaining the reliability coefficient associated with the non-fulfilling party (lessee or lessor) and for associating a score to the approved non-fulfilment report.
Preferably, the server 10 associates a score to the non- fulfilment report as a function of the seriousness of the event that generated the non-fulfilment report. Such score, associated with a respective approved non-fulfilment report, will then be used in order to reduce the (lessee or lessor) reliability coefficient associated with the non-fulfilling party.
For example, the reliability coefficient associated with the non-fulfilling party is reduced by 100 points. Preferably, if a lessee or a lessor is identified as a non-fulfilling party within a time interval of 6 to 12 months, then the server 10 will reduce by half, or set to zero, the reliability coefficient associated with such non-fulfilling party.
Preferably, each reliability coefficient associated with a respective lessee or a respective lessor is computed as a function of each non-fulfilment report received within a time interval of 5 to 15 years, more preferably 10 years.
According to a further aspect, the present invention preferably allows knowing the lessee reliability coefficient of a lessee associated with a lessee record in the lessees database 22 prior to signing a rental contract.
According to a further aspect, the present invention preferably allows knowing the lessor reliability coefficient of a lessor associated with a lessor record in the lessors database 21 prior to signing a rental contract.
Preferably, the present invention provides access to the server 10 to third parties, e.g. credit institutions, financing organizations and/or insurance companies. Such third parties can, subject to authentication, gain access to the lessor reliability coefficient or the lessee reliability coefficient. In this manner, advantageously, such third parties can reduce the risk of proposing insurance and/or loan contracts to potentially defaulting customers.
The present invention offers some important advantages.
In particular, the system 100 makes for a more transparent, more honest, qualitatively better and more secure rental market.
Furthermore, by means of the lessee reliability coefficient and the lessor reliability coefficient it is possible to reduce the risk of entering into a rental contract with a potentially non-fulfilling party.

Claims

1. A system (100) for managing rental risks, comprising a computer (10) equipped with a memory medium (20), said computer (10) being configured for:
- obtaining a non-fulfilment report comprising:
- a reporter identification code associated with a lessee or a lessor;
- a contract identification code associated with a respective rental contract;
- accessing a contracts database (23), stored in said memory medium (20), to identify information associated with said rental contract; wherein said information associated with said rental contract comprises at least:
- a first identification key that univocally identifies said rental contract;
- a second identification key that univocally identifies said lessor;
- a third identification key that univocally identifies said lessee;
- identifying a non-fulfilling party as a function of said non- fulfilment report and said second identification key or said third identification key;
- obtaining a reliability coefficient associated with said non fulfilling party; said reliability coefficient being representative of the non- fulfilment risk associated with said non-fulfilling party; wherein said reliability coefficient has a numerical value which is computed, for a respective lessor, as a function of said lessor's real estate and/or the number of rented real properties associated with said lessor and/or the history of rental contracts associated with said lessor; or for a respective lessee, as a function of said lessee's personal information and/or the history of rental contracts associated with said lessee and/or the type of said lessee;
- updating said reliability coefficient associated with said non-fulfilling party as a function of said non-fulfilment report.
2. The system (100) according to the preceding claim, wherein said reporter identification code is associated with a lessor and said non-fulfilment notification further comprises a first document concerning at least one of the following events:
- non-payments;
- unauthorized and/or unlawful occupation of the property;
- partial or total subletting of the property to third parties;
- deterioration of the property and/or of goods associated with the property;
- theft of goods associated with the property;
- damages to the property and/or to third parties;
- failure to comply with the period of notice of termination;
- unauthorized registration of personal and tax residences.
3. The system (100) according to claim 1, wherein said reporter identification code is associated with a lessee and said non- fulfilment report further comprises a first document concerning at least one of the following events:
- verification of non-compliant property;
- failure to comply with contractual times;
- failure to comply with the period of notice of termination;
- presence of hidden defects;
- failure to comply with contractual terms;
- delayed or non-execution of works lying within the lessor's province; - charging of undue expenses;
- unregistered rental contract;
- no communication of the data concerning the registration of the rental contract;
- caution money not returned or only partially returned.
4. The system (100) according to any one of claims 2 or 3, wherein said computer (10) is further configured for:
- notifying said non-fulfilment report to said lessor associated with said second identification key;
- notifying said non-fulfilment report to said lessee associated with said third identification key;
- receiving a reply to said notification from said non fulfilling party;
- waiting a predefined time interval for receiving, from said non-fulfilling party, at least one second document demonstrating the resolution of the events reported in said first document.
5. The system (100) according to the preceding claim, wherein said computer (10) is configured for waiting a predefined time interval of 15 to 30 days for receiving said second document from said non-fulfilling party.
6. The system (100) according to any one of the preceding claims, wherein said computer (10) is configured for updating the reliability coefficient associated with said non-fulfilling party as a function of each non-fulfilment report received within a time interval of 5 to 10 years from the current date.
PCT/IB2022/053526 2021-04-20 2022-04-14 Method and system for managing rental risks WO2022224101A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IT102021000009911 2021-04-20
IT102021000009911A IT202100009911A1 (en) 2021-04-20 2021-04-20 METHOD AND SYSTEM FOR THE MANAGEMENT OF RENTAL RISKS

Publications (1)

Publication Number Publication Date
WO2022224101A1 true WO2022224101A1 (en) 2022-10-27

Family

ID=77021870

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/053526 WO2022224101A1 (en) 2021-04-20 2022-04-14 Method and system for managing rental risks

Country Status (2)

Country Link
IT (1) IT202100009911A1 (en)
WO (1) WO2022224101A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060184440A1 (en) * 2005-01-26 2006-08-17 Britti Michael A Risk-based pricing for rental property

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060184440A1 (en) * 2005-01-26 2006-08-17 Britti Michael A Risk-based pricing for rental property

Also Published As

Publication number Publication date
IT202100009911A1 (en) 2022-10-20

Similar Documents

Publication Publication Date Title
KR100282750B1 (en) E-commerce system
US9292854B2 (en) Method and apparatus for enabling purchasers of products to obtain return information and to initiate product returns via an on-line network connection
US7752124B2 (en) System and method for automated loan compliance assessment
US7908210B2 (en) Systems and method for managing dealer information
US8086525B2 (en) Methods and systems for providing risk ratings for use in person-to-person transactions
US20090254476A1 (en) Method and system for managing personal and financial information
US20080114663A1 (en) Product resale system and method
US20100281535A1 (en) Electronic message delivery with estimation approaches
US20100106534A1 (en) Certification and risk-management system and method for a rental agreement
US20020116308A1 (en) Computerized asset verification system and method
US7953607B2 (en) Integrated mail, internet, and telephony event tracking system
EP1836592B1 (en) Using associated knowledge databases for providing additional information in the mailing process
WO2022224101A1 (en) Method and system for managing rental risks
WO2003077164A1 (en) Anonymous gifting
KR101171379B1 (en) Method and System for Providing Early Warning Service
Abbasi et al. White Paper-Standard Operating Procedure for Digital Commerce in Least Developed Countries
CN114971561A (en) Loan system transaction data automatic integration processing method and device
AU2002311384B2 (en) Anonymous Gifting
Linquanti Issues with the Condominium Unit Exemption in ILSA
KR101735156B1 (en) Method for Relaying the Integrated Issue of Confirm Letter of Bank Deposit
CN115049416A (en) Data processing method and device based on block chain and electronic equipment
CA2585585A1 (en) Systems and methods for managing dealer information
US20100125469A1 (en) Methods and a system for remotely authorizing and monitoring financial transactions
Ngeno Electronic land registry for Kenya
Mull Key Considerations for Home Mortgage Debt Collectors under the Consumer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22722350

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22722350

Country of ref document: EP

Kind code of ref document: A1