KR102586003B1 - A real estate risk management method determining double contracks based on real estate information and a real estate risk manegement server performing the same - Google Patents

Abstract

A real estate risk management method for determining dual contracts based on real estate information and a real estate risk management server that performs the same are disclosed. A method of informing contract risks for real estate subject to a contract according to the technical idea of the present disclosure includes the steps of receiving contract information for the real estate, receiving the moving-in household viewing details of the real estate, and the moving-in household viewing details. It may include extracting a move-in date from and determining a contract risk for the real estate based on the contract information and the move-in date, and transmitting the contract risk.

Description

Real estate risk management method for determining double contracts based on real estate information and real estate risk management server that performs the same

The present invention relates to a real estate risk management method for determining dual contracts based on real estate information and a real estate risk management server that performs the same.

Among the essential conditions for human life, food, clothing, and shelter, real estate transactions related to one's place of residence involve a large amount of money, so objective and detailed information is needed in the transaction. In the case of a sales contract, the rights are transferred through an objectively announced registration, so objective information can be confirmed, but in the case of a lease contract such as a jeonse or monthly rent, registration is not essential, and the right to residence is transferred through a contract between the parties. Therefore, when a contracting party harbors malicious intent, fraudulent activities such as writing the contents of a contract differently from the actual one often occur.

In particular, a contract in which an owner enters into two contracts for the same object with different contents is called a double contract. As there are increasing cases where lessees who cannot obtain objective information suffer damage due to double contracts, it is necessary for lessees to prevent double contracts. The need to provide objective information is increasing.

The purpose of the present invention is to provide a real estate risk management method that provides objective information to real estate contract parties based on real estate information, and a real estate risk management server that performs the same.

A method of informing contract risks for real estate subject to a contract according to the technical idea of the present disclosure includes the steps of receiving contract information for the real estate, receiving the moving-in household viewing details of the real estate, and the moving-in household viewing details. It may include extracting a move-in date from and determining a contract risk for the real estate based on the contract information and the move-in date, and transmitting the contract risk.

In one embodiment, the contract information is the contract start date for the real estate, and the step of determining the contract risk for the real estate includes determining the first risk when the difference between the contract start date and the transfer date is less than the first value. and determining a second risk when the difference between the contract start date and the transfer date is greater than or equal to the first value, and the first risk may indicate that the first risk is more contractually risky than the second risk.

In one embodiment, the contract information is the contract start date for the real estate, and the step of determining the contract risk for the real estate includes determining the first risk when the difference between the contract start date and the transfer date is less than the first value. A step of determining a second risk if the difference between the contract start date and the transfer date is greater than or equal to the first value and less than a second value greater than the first value, and the difference between the contract start date and the transfer date is the second risk. If it is greater than or equal to the value, it includes the step of determining it as a third risk, wherein the first risk indicates that it is contractually riskier than the second risk, and the second risk indicates that it is contractually riskier than the third risk. It can be characterized as:

In one embodiment, the contract information is the contract date for the real estate, and the step of determining the contract risk for the real estate includes determining the first risk when the difference between the contract date and the transfer date is less than a first value. And if the difference between the contract date and the transfer date is greater than or equal to the first value, determining it to be a second risk, wherein the first risk may be characterized as indicating that it is more contractually risky than the second risk. .

In one embodiment, extracting the name of the head of the household from the moving-in household viewing details, receiving the status of granting a confirmed date for the real estate, extracting the name of the head of the household from the granting status of the fixed date, and extracting the name of the head of the household from the viewing details of the moving-in household. A step of determining the contract risk may be further included based on the extracted name of the head of the household and the name of the head of the household extracted from the status of granting the fixed date.

In one embodiment, the step of determining the contract risk based on the name of the head of the household includes, when the name of the head of the household extracted from the move-in household viewing details and the name of the head of the household extracted from the status of granting the confirmed date are inconsistent, It may include calculating the difference between the transfer date and the fixed date grant date extracted from the confirmed date grant status and transmitting the calculated difference between the transfer date and the fixed date grant date.

A method of informing contract risks for real estate subject to a contract according to the technical concept of the present disclosure includes the steps of receiving contract information for the real estate, receiving the status of granting a confirmed date for the real estate, and the status of granting the confirmed date. It may include extracting a fixed date grant date from , determining a contract risk for the real estate based on the contract information and the fixed date grant date, and transmitting the contract risk.

In one embodiment, the contract information is the contract start date for the real estate, and the step of determining the contract risk for the real estate includes determining the first risk when the difference between the contract start date and the transfer date is less than the first value. A step of determining a second risk if the difference between the contract start date and the transfer date is greater than or equal to the first value and less than a second value greater than the first value, and the difference between the contract start date and the transfer date is the second risk. If it is greater than or equal to the value, it includes the step of determining it as a third risk, wherein the first risk indicates that it is contractually riskier than the second risk, and the second risk indicates that it is contractually riskier than the third risk. It can be characterized as:

In one embodiment, the contract information is a contract period for the real estate, and the method includes extracting a lease period from the fixed date grant status, determining whether the lease period and the contract period overlap, and A step of transmitting whether or not there is a duplicate may be further included.

In one embodiment, the contract information is contract rent for the real estate, and the method includes extracting a rent from the fixed date grant status, calculating a ratio of the contract rent and the rent extracted from the fixed date grant status. and, if the ratio is greater than or equal to a predetermined threshold, transmitting a contract risk indicating that the contract is risky.

According to the technical idea of the present invention, by warning the real estate contracting party (e.g., lessee) of the risk of a double contract using objective real estate information such as the moving-in unit viewing history or the status of granting a fixed date, the real estate contracting party can enter into a double contract. Real estate risks such as these can be confirmed, and as a result, the number of real estate contracting parties suffering damage due to double contracts can be reduced.

1 is a block diagram of a real estate risk management system according to an exemplary embodiment of the present disclosure.
Figure 2 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 3 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 4 is a diagram showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 5 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 6 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 7 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure.
Figure 8 is a block diagram illustrating a computing system including a management server according to an exemplary embodiment of the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the technical idea of the present disclosure is not limited to the following embodiments and may be implemented in various different forms. The following examples are merely intended to complete the technical idea of the present disclosure and to be used in the technical field to which the present disclosure belongs. It is provided to fully inform those skilled in the art of the scope of the present disclosure, and the technical idea of the present disclosure is only defined by the scope of the claims.

When adding reference numerals to components in each drawing, it should be noted that identical components are given the same reference numerals as much as possible even if they are shown in different drawings. Additionally, in describing the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present disclosure, the detailed description will be omitted.

Unless otherwise defined, all terms (including technical and scientific terms) used in this specification may be used with meanings that can be commonly understood by those skilled in the art to which this disclosure pertains. Additionally, terms defined in commonly used dictionaries are not interpreted ideally or excessively unless clearly specifically defined. The terminology used herein is for the purpose of describing embodiments and is not intended to limit the disclosure. As used herein, singular forms also include plural forms, unless specifically stated otherwise in the context.

Additionally, in describing the components of the present disclosure, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, or order of the component is not limited by the term. When a component is described as being “connected,” “coupled,” or “connected” to another component, that component may be directly connected or connected to that other component, but there is another component between each component. It will be understood that elements may be “connected,” “combined,” or “connected.”

As used in this disclosure, “comprises” and/or “comprising” refers to a referenced component, step, operation and/or element that includes one or more other components, steps, operations and/or elements. Does not exclude presence or addition.

Components included in one embodiment and components including common functions may be described using the same name in other embodiments. Unless stated to the contrary, the description given in one embodiment can be applied to other embodiments, and detailed description will be omitted to the extent of overlap or to the extent that it can be clearly understood by a person skilled in the art. You can.

Hereinafter, the present invention will be described in detail with reference to preferred embodiments of the present invention and the accompanying drawings.

1 is a block diagram of a real estate risk management system according to an exemplary embodiment of the present disclosure.

Referring to FIG. 1, the real estate risk management system 10 may include a management server 100 and a contract terminal 200.

The management server 100 may collectively refer to a server that manages a real estate risk management system and an operating computer that operates the server. In one embodiment, the management server 100 may operate a real estate risk management system using an application such as a website or application, and in this specification, the management server 100 or the management server 100 The operations performed by the included components may actually be operations performed by the management server 100 using an application program built into the storage device of the management server 100. The storage device may include non-volatile memory, volatile memory, flash-memory, hard disk drive (HDD), or solid state drive (SSD). Additionally, the processor may include at least one of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Neural Processing Unit (NPU), RAM, ROM, a system bus, and an application processor. The management server 100 may be connected to the contract terminal 200 through a wired or wireless communication network, and the management server 100 may operate as a communication hub for the contract terminal 200.

The contract terminal 200 is a terminal operated by a party to a real estate contract. In one example, the contract terminal 200 may be operated by a lessee executing a lease contract with the owner of the real estate, but is not limited to this. The contract terminal 200 includes a laptop, PC (Personal Computer), navigation, PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), and PDA. (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), Wibro (Wireless Broadband Internet) terminal, smartpad , it may be comprised of a tablet PC, a cellular phone, or a smart phone. In this specification, the contract terminal 200 is disclosed as an example implemented through a terminal, but this is only an example, and each configuration may be implemented through a communication hub such as a server.

The management server 100 may receive contract information (Info_Ct) from the contract terminal 200 and obtain real estate information (Info_Pr) based on the contract information (Info_Ct). In this specification, contract information (Info_Ct) may represent various information related to a real estate contract, and in one example, the location (address) of the object subject to the contract, the scheduled contract period, and the scheduled rent (deposit and/or rent) It may include, and in one embodiment, the management server 100 may acquire contract information (Info_Ct) directly entered by the contract terminal 200, and in another embodiment, receive the contract from the contract terminal 200. And, the above-described contract information (Info_Ct) can be obtained from the contract through OCR (optical character recognition) on the contract.

Additionally, in this specification, real estate information (Info_Pr) may represent objective information about the subject of the contract, and in one example, may include the viewing details of the moving-in household and the granting status of the confirmed date. The moving-in household viewing details may include information about the household that moved into the address of the contract subject, and may include the name of the head of the household that moved in and information on the first moving-in date. The status of granting a confirmed date may include information on the status of receiving a confirmed date for the object of the contract, the name of the head of the household who received the confirmed date, the grant date of the confirmed date, the period of the lease contract subject to the confirmed date, and the rent (deposit amount) and/or chime).

In one embodiment of the present disclosure, the management server 100 obtains an address for the contract object from contract information (Info_Ct) and uses the address to retrieve real estate from the database of a public institution (e.g., government, local government, court). Information (Info_Pr) can be obtained. Additionally, the management server 100 may determine the risk of the contract using real estate information (Info_Pr) and output the determined risk information (Rsk) to the contract terminal 200. Risk information (Rsk) may include detailed information on various risks related to real estate contracts, and may also include additional consulting information (law/case law information, matching consulting companies, etc.) to resolve risks.

To this end, the management server 100 may include a period risk determination unit 110, a householder risk determination unit 120, and a price risk determination unit 130. The period risk determination unit 110 may determine the risk for the contract period based on real estate information (Info_Pr) and contract information (Info_Ct). The householder risk determination unit 120 can determine risks that may occur when the householder is different based on real estate information (Info_Pr) and contract information (Info_Ct). The price risk determination unit 130 may determine the risk of contract rent based on real estate information (Info_Pr) and contract information (Info_Ct).

According to the technical idea of the present disclosure, the management server 100 acquires real estate information (Info_Pr) from the database of a public institution with public trust based on the contract information (Info_Ct) received from the contract terminal 200, and real estate information (Info_Pr) ) and contract information (Info_Ct) to review the risk of the contract (for example, the possibility of a double contract), allowing contracting parties to check the risk of a double contract in advance and minimize the damage that may arise from a double contract. You can.

Additionally, in one embodiment, the real estate information (Info_Pr) and contract information (Info_Ct) are encrypted and processed, and the corresponding information may be deleted after sending the risk information (Rsk), and thus the personal information of the contracting party It can prevent leakage to the outside.

Figure 2 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 2 shows a method for determining whether there is a double contract based on the contract start date and move-in date.

Referring to FIG. 2, the management server 100 may receive the moving-in household viewing details as contract information (Info_Ct) and real estate information (Info_Pr) (S110). In one example, the management server 100 receives contract information (Info_Ct) from the contract terminal 200, and the moving-in household viewing details are stored in the moving-in household information through an API (Application Programming Interface) operated by the government or local government. It can be obtained from the database.

The management server 100 may extract the contract start date from the contract information (Info_Ct) (S120). The contract start date may mean the date on which the contracting party begins to have the right to use the object, and in one example, it may be the balance payment date or the lease start date.

The management server 100 can extract the move-in date from the moving-in household viewing history (S130). The move-in date may mean the day the household currently using the contract object began using it, and the management server 100 may obtain the date corresponding to the first move-in date in the move-in household viewing history as the move-in date.

The management server 100 may calculate the difference (D) between the contract start date and the move-in date (S140). The management server 100 determines the contract risk as the first risk (e.g., 'risk') when the difference (D) is less than the predetermined first value (N1) (S151), and the difference (D) is the first value (N1). If it is greater than 1 value (N1) and less than the predetermined second value (N2), the contract risk is judged as a second risk (e.g., 'caution') (S152), and the difference (D) is the second value (N2). If it is N2) or more, the contract risk can be judged as a third risk (for example, 'safety') (S153). In one embodiment, the contract risk may be determined by a phrase indicating a safer contract in the order of first risk - second risk - third risk. The management server 100 may transmit the contract risk (Rsk) including the determined phrase to the contract terminal 200 (S160).

The greater the difference between the current contract start date and the transfer date for the previous contract, the higher the probability that the previous contract will end and the current contract will proceed. If the difference between the current contract start date and the transfer date for the previous contract is small, the current contract will be concluded before the previous contract ends. There is a high probability that it is a double contract. According to an embodiment of the present disclosure, a double contract is determined based on the difference between the move-in date and the contract start date obtained from the move-in report viewing details, which are credible data, and information about this is provided to the contract terminal, so that the contract terminal can enter into a double contract. You can check the possibility in advance and minimize damage to the tenant due to double contracts.

In Figure 2, an embodiment of dividing the contract risk based on two reference values (N1, N2) is shown, but this is an example, and the embodiment of dividing the contract risk based on one or three or more reference values is also shown in the present disclosure. It is natural that technical ideas can be applied.

In addition, Figure 2 discloses the feature of determining the contract risk based on the contract start date, but this is an example, and the real estate contract date, such as the contract date when the first contract is in progress, the advance payment date when the advance payment is made, and the balance payment date when the balance is made, are It should be understood that the technical idea of this disclosure can be applied even when determining contract risk using a date and transfer date that can specify.

Figure 3 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 3 shows a method of determining whether there is a double contract based on the contract start date and the fixed date grant date.

Referring to FIG. 3, the management server 100 may receive the confirmation date grant status as contract information (Info_Ct) and real estate information (Info_Pr) (S210). In one example, the management server 100 receives contract information (Info_Ct) from the contract terminal 200, and obtains the confirmation date grant status from a database on confirmation date information through an API (Application Programming Interface) operated by the court. can do.

The management server 100 may extract the contract start date from the contract information (Info_Ct) (S220). The management server 100 may extract the fixed date grant date from the fixed date grant status (S230). The date of granting a fixed date may refer to the date on which the date on which the contract was executed is notarized by a government agency such as a community center in order to secure opposition under the Lease Protection Act.

The management server 100 may calculate the difference (D) between the contract start date and the confirmed date grant date (S240). The management server 100 determines the contract risk as the first risk (e.g., 'risk') when the difference (D) is less than the predetermined first value (N1) (S251), and the difference (D) is the first risk (N1). If it is greater than 1 value (N1) and less than the predetermined second value (N2), the contract risk is judged as a second risk (e.g., 'caution') (S252), and the difference (D) is determined as the second value (N2). If it is N2) or more, the contract risk can be judged as a third risk (for example, 'safety') (S253). In one embodiment, the contract risk may be determined by a phrase indicating a safer contract in the order of first risk - second risk - third risk. The management server 100 may transmit the contract risk (Rsk) including the determined phrase to the contract terminal 200 (S260).

In order to secure competitiveness, a confirmed date is usually received immediately after signing the contract, so the contract date of the previous contract can be estimated through the date of granting the confirmed date. In addition, the larger the difference between the fixed date grant date corresponding to the previous contract date and the current contract start date, the higher the probability that the previous contract will be terminated and the current contract will proceed. If the difference between the fixed date grant date and the current contract start date is small, the current contract will be completed before the previous contract ends. It is highly likely that the contract will be a double contract. According to an embodiment of the present disclosure, a double contract is determined through a trustworthy fixed date grant date obtained from a public institution instead of the previous contract date, and information about this is provided to the contract terminal, so that the contract terminal can confirm the possibility of a double contract in advance. This can minimize damage to tenants due to double contracts.

Figure 4 is a diagram showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 4 shows a method for determining whether there is a dual contract based on the contract start date and the previous contract related date.

Referring to FIG. 4, the management server 100 may determine the contract risk (Rsk) based on the previous contract related date (Dpre) (for example, the date of granting a fixed date or the date of transfer). In one example, if the contract start date (D1) is before the day after the first value (N1) from the previous contract related date (Dpre), the management server 100 sends 'risk' as the contract risk (Rsk) to the contract terminal. It can be sent to (200). In one example, if the contract start date (D2) is between the previous contract related date (Dpre) and the period from the day the first value (N1) passed to the day the second value (N2) passed, the management server 100 is the contract risk (Rsk) and can transmit 'caution' to the contract terminal 200. In one example, if the contract start date (D3) is after the second value (N2) from the previous contract related date (Dpre), the management server 100 sets 'safe' as the contract risk (Rsk) to the contract terminal. It can be sent to (200).

Since the previous contract related date (Dpre) is related to the previous contract date, the shorter the period between the previous contract related date and the current contract start date, the more likely it is that the current contract is a dual contract. According to the technical idea of the present disclosure, the previous contract related date (Dpre) is extracted from credible information (e.g., moving-in household viewing history or confirmed date grant status), and the previous contract related date (Dpre) is extracted between the current contract start date and the previous contract related date (Dpre). By determining the risk of a contract based on the period interval, contracting parties can be prevented from suffering losses due to double contracts.

Figure 5 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 5 shows a method of determining whether there is a double contract based on the contract period and lease period.

Referring to FIG. 5, the management server 100 may receive contract information (Info_Ct) and the status of granting a confirmed date (S310). The status of granting a fixed date may include information about the name of the head of the household, the date of granting a fixed date, the lease period, and the rent.

The management server 100 may extract the contract period from the contract information (Info_Ct) (S320). In one embodiment, the management server 100 may extract the contract period directly entered by the contract terminal 200, and in another embodiment, the management server 100 may extract OCR from the contract entered by the contract terminal 200. The contract period can be extracted through

The management server 100 can extract the lease period from the fixed date grant status (S330). The lease period may refer to the period of residence rights of the lessee who has already moved into the target property.

The management server 100 may determine whether the contract period of the contract terminal 200 and the lease period of the fixed date grant status overlap (S340). If the contract period and the lease period overlap, the management server 100 may warn the contract terminal 200 that the contract period overlaps with the previous lease period (S350), and in one embodiment, information about the overlapping period. (For example, overlapping dates and overlapping periods) can be transmitted together to the contract terminal 200.

Information on the lease period included in the contract can be obtained from the status of granting a fixed date, and information on the end date of the previous lease period can be obtained. According to an embodiment of the present disclosure, information on the end date of the rental period can be obtained from the public trust of the granting of a fixed date, and based on this, it can be determined whether it overlaps with the current contractual contract period, and accordingly, it is determined whether there is a double contract. Contracting parties can check in advance the risks of double contracts.

Figure 6 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 6 shows a method of determining whether there is a dual contract based on the name of the head of the household.

Referring to FIG. 6, the management server 100 can receive the moving-in household viewing details and the status of granting a confirmed date (S410). The moving-in household viewing history may include information about the name of the head of the household of the moving-in generation, and the status of granting a confirmed date may include information about the name of the head of the household for which a confirmed date was granted.

The management server 100 may extract the name of the head of the household from the moving-in household viewing history (S420) and extract the name of the head of the household from the status of granting the confirmed date (S430). The management server 100 may determine whether the names of the two extracted householders are the same (S440).

If the names of the two extracted household heads are not the same, the management server 100 calculates the difference between the move-in date in the moved-in household viewing history and the confirmed date grant date in the confirmed date grant status (S450), and determines whether there is a mismatch between the household heads and the calculated move-in date The difference between the confirmed date and the grant date can be transmitted to the management server 100 (S460).

If the names of the two extracted householders are not the same, it means that the person who moved into the destination and the person who received the confirmed date are different, so there is a risk that the previous two contracts are double contracts, and as a result, the contract performed by the contract terminal 200 is also There is a risk of a double contract. Therefore, when the two extracted householder names are not the same, the management server 100 according to an embodiment of the present disclosure transmits information about this to the contract terminal 200 so that the contractee can confirm the double contract through a broker, etc. It can be used as a clue.

In addition, if the difference between the transfer date and the grant date is large (for example, more than 2 years), the previous contractee may not have moved in or may not have been granted a fixed date even though it is a normal two contracts, and the difference between the transfer date and the grant date of the fixed date may be If the number is small (for example, the same person), even though it is one contract, the head of the household may appear differently because the head of the household who moved in from the same household is different from the head of the household who was given a fixed date. According to an embodiment of the present disclosure, by transmitting the difference between the move-in date and the date of granting the fixed date along with the discrepancy between the head of the household, the contract can be used as a clue to check whether it is a double contract based on the date difference through a broker, etc. .

Figure 7 is a flowchart showing a real estate risk management method according to an exemplary embodiment of the present disclosure. In detail, Figure 7 shows a method for determining whether there is a double contract based on the rent ratio.

Referring to FIG. 7, the management server 100 may receive contract information and confirmation date grant status (S510). The contract information may include information about the contract rent contracted by the contract terminal 200, and the confirmed date grant status may include information about the existing rent for the previous contract. The management server 100 may extract the contract rent from the contract information (S520) and extract the existing rent from the status of granting the fixed date (S530). In one embodiment, the management server 100 may receive the contract rent directly from the contract terminal 200, and in another embodiment, the management server 100 may receive the contract rent entered by the contract terminal 200 through OCR. Contract rent can be extracted. Contract rent may include a deposit paid at the time of contract and a rent paid periodically (for example, monthly).

The management server 100 may determine whether the ratio of the contract rent and the existing rent is greater than the threshold value (mth) (S540). If the ratio of the contract rent to the existing rent is greater than the threshold (mth), the management server 100 may transmit the contract risk as 'risk' to the contract terminal 200 (S550).

According to an embodiment of the present disclosure, it is possible to induce a contractor to enter into a contract at an appropriate price condition by determining whether the contract rent is at an appropriate level based on the existing rent extracted from the status of granting a fixed date.

Figure 8 is a block diagram illustrating a computing system including a management server according to an exemplary embodiment of the present invention.

Referring to FIG. 8 , the computing system 1000 may include a processor 1100, a memory device 1200, a storage device 1300, a power supply 1400, and an input/output device 1500. Meanwhile, although not shown in FIG. 8, the computing system 1000 may further include ports capable of communicating with a video card, sound card, memory card, USB device, etc., or with other electronic devices. .

As such, the processor 1100, memory device 1200, storage device 1300, power supply 1400, and input/output device 1500 included in the computing system 1000 are embodiments according to the technical idea of the present invention. You can configure a management server that performs real estate risk management methods according to the requirements. Specifically, the processor 1100 can perform the real estate risk management method described above in FIGS. 1 to 7 by controlling the memory device 1200, the storage device 1300, the power supply 1400, and the input/output device 1500. there is.

Processor 1100 may perform specific calculations or tasks. Depending on the embodiment, the processor 1100 may be a microprocessor or a central processing unit (CPU). The processor 1100 connects the memory device 1200, the storage device 1300, and the input/output device 1500 through a bus 1600 such as an address bus, a control bus, and a data bus. You can communicate with. Depending on the embodiment, the processor 1100 may also be connected to an expansion bus such as a peripheral component interconnect (PCI) bus.

The memory device 1200 may store data necessary for the operation of the computing system 1000. For example, the memory device 1200 may be implemented with DRAM, mobile DRAM, SRAM, PRAM, FRAM, RRAM, and/or MRAM. there is. The storage device 1300 may include a solid state drive, hard disk drive, CD-ROM, etc. The memory device 1200 and the storage device 1300 may store programs related to the real estate risk management method described above with reference to FIGS. 1 to 7 .

The input/output device 1500 may include input means such as a keyboard, keypad, and mouse, and output means such as a printer and display. The power device 1400 may supply operating voltage required for operation of the computing system 1000.

As above, exemplary embodiments have been disclosed in the drawings and specification. In this specification, embodiments have been described using specific terms, but this is only used for the purpose of explaining the technical idea of the present disclosure and is not used to limit the meaning or scope of the present disclosure described in the claims. Therefore, those skilled in the art will understand that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true technical protection scope of the present disclosure should be determined by the technical spirit of the attached claims.

Claims (10)

In a method of notifying contract risks for real estate subject to a contract performed by a management server including a processor,
receiving, by the processor, contract information including a contract start date for the property;
Receiving, by the processor, a viewing history of households moving into the real estate from an API operated by the government or local government;
Extracting, by the processor, a move-in date from the move-in household viewing details;
determining, by the processor, a contract risk for the real estate based on the contract information and the move-in date;
transmitting, by the processor, the contract risk excluding the contract information;
Extracting, by the processor, the name of the head of the household from the moving-in household viewing history;
Receiving, by the processor, a status of granting a fixed date for the real estate from an API operated by a court;
Extracting, by the processor, the name of the head of household from the status of granting the fixed date;
Comparing, by the processor, the name of the head of household extracted from the moving-in household viewing details and the name of the head of household extracted from the status of granting the fixed date;
The processor grants the move-in date extracted from the moved-in household viewing details and the confirmed date extracted from the confirmed date grant status only in cases where there is a discrepancy between the name of the head of the household extracted from the moved-in household viewing details and the name of the head of household extracted from the confirmed date grant status. calculating the difference in days;
Transmitting, by the processor, the difference between the calculated move-in date and the date of granting the confirmed date along with whether there is a discrepancy between the head of the household; and
Including; deleting the contract information after transmitting the contract risk,
The step of determining the contract risk for the real estate based on the contract information and the transfer date is,
If the difference between the contract start date and the transfer date is less than a first value, determining it as a first risk; And
If the difference between the contract start date and the transfer date is greater than or equal to the first value, determining a second risk; including,
Indicates that the first risk is contractually riskier than the second risk,
The contract information further includes a contract rent for the real estate,
Extracting, by the processor, the contract rent from the fixed date grant status;
Calculating, by the processor, a ratio of the contract rent and the rent extracted from the fixed date grant status; And
transmitting, by the processor, a contract risk indicating that the contract is risky if the ratio is above a predetermined threshold.
delete According to claim 1,
The step of determining the contract risk for the real estate is:
If the difference between the contract start date and the transfer date is greater than or equal to the first value and less than a second value greater than the first value, determining the second risk; And
If the difference between the contract start date and the transfer date is greater than or equal to the second value, determining it as a third risk;
Indicates that the first risk is contractually riskier than the second risk,
A method characterized in that the second risk is contractually more risky than the third risk.

According to claim 1,
The above contract information is Includes the contract date for the above real estate,
The step of determining the contract risk for the real estate is:
If the difference between the contract date and the transfer date is less than a first value, determining the first risk; And
If the difference between the contract date and the transfer date is greater than or equal to the first value, determining the second risk;
A method characterized in that the first risk is contractually riskier than the second risk.

delete delete delete delete According to paragraph 1,
The contract information is the contract period for the real estate,
Extracting, by the processor, a lease period from the fixed date grant status;
determining, by the processor, whether the lease period and the contract period overlap; and
The method further comprising transmitting, by the processor, whether the duplicate is present.



delete