Contract support system and contract support method

Abstract

To reduce the burden of insurance contracts taken out in connection with the transfer or lease of real estate properties. [Solution] The contract support system accepts registration of real estate information necessary for the transfer or lease of real estate from a first user who has the authority to transfer, lease, or broker real estate property. The contract support system accepts registration of personal information from a second user. When the second user enters into a contract for the transfer or lease of real estate property, the contract support system associates the second user with the real estate property. Using the personal information of the second user, which was registered before the association between the second user and the real estate property, and the real estate information of the real estate property, the contract support system generates contract document information for an insurance contract related to the real estate property.

Description

Technical Field

[0001] The present invention relates to a contract support system and a contract support method for real estate.

Background Art

[0002] Patent Document 1 discloses a system that supports real estate contracts.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problem to be Solved by the Invention

[0004] By the way, after a contract concerning the sale or rental (transfer or lease) of a real estate property is concluded, the contractor is usually required to take out insurance such as fire insurance. Therefore, for example, in the case of a newly built condominium for sale, an insurance contract is often processed with an insurer at a venue such as an important matters explanation meeting. However, when entering into an insurance contract, it is necessary to fill in information on the real estate property and information on the contractor, which poses a problem of being time-consuming. An object of the present invention is to provide a contract support system and a contract support method that can reduce the burden related to insurance contracts taken out upon the transfer or lease of a real estate property.

Means for Solving the Problem

[0005] According to a first aspect of the present invention, the contract support system is a contract support system that supports contracts relating to real estate, and comprises: a first registration unit that receives registration of real estate information necessary for the transfer or lease of real estate from a first user who has first user authority to transfer or lease or mediate the transfer or lease of real estate; a first presentation unit that presents the real estate information to a second user who has second user authority to receive the transfer or lease of real estate; a second registration unit that receives registration of the personal information of the second user; an association unit that associates the second user with the real estate when the second user enters into a contract for the transfer or lease of the real estate; and a generation unit that generates contract document information for an insurance contract relating to the real estate using the personal information of the second user and the real estate information of the real estate, which were registered before the association between the second user and the real estate.

[0006] According to a second aspect of the present invention, in the contract support system according to the first aspect, the real estate information includes items necessary for display for transfer and items necessary for an insurance contract, the first presentation unit presents the real estate information when the items necessary for display for transfer are satisfied, and the generation unit generates the contract document information when the items necessary for an insurance contract are satisfied.

[0007] According to a third aspect of the present invention, the contract support system according to the first or second aspect may include a third registration unit that, when the real estate information lacks items necessary for an insurance contract, receives input of the missing items from a third user who has third-user authority to conduct insurance business related to real estate properties.

[0008] According to a fourth aspect of the present invention, the contract support system according to any of the first to third aspects may be a computer that can access an internal system that performs processing related to the insurance business relating to the third user, and which includes an RPA unit that, when the contract document information is created, instructs the internal system to create predetermined document data using the contract document information.

[0009] According to a fifth aspect of the present invention, a contract support system for supporting contracts relating to real estate properties includes the steps of: receiving registration of real estate information necessary for the transfer or lease of real estate properties from a first user who has first user authority to transfer or lease or mediate the transfer or lease of real estate properties; presenting the real estate information to a second user who has second user authority to receive the transfer or lease of real estate properties; receiving registration of the personal information of the second user; associating the second user with the real estate property when the second user enters into a contract for the transfer or lease of the real estate property; and generating contract document information for an insurance contract relating to the real estate property using the personal information of the second user and the real estate information of the real estate property that were registered before the second user and the real estate property were associated. [Effects of the Invention]

[0010] According to at least one of the above methods, the burden of insurance contracts to be taken out in connection with the transfer or lease of real estate property can be reduced. [Brief explanation of the drawing]

[0011] [Figure 1] This diagram shows the configuration of the contract support system according to the first embodiment. [Figure 2] This diagram shows the functional configuration of the contract support server according to the first embodiment. [Figure 3] This is a flowchart showing the flow of a real estate contract according to the first embodiment. [Figure 4] This is an example of a property list screen according to the first embodiment. [Figure 5] This is an example of a common insurance information setting screen according to the first embodiment. [Figure 6] This is an example of an information provision permission screen according to the first embodiment. [Figure 7] This is an example of the subscriber list screen according to the first embodiment. [Figure 8]This is an example of an individual insurance information setting screen according to the first embodiment. [Figure 9] This is an example of a policyholder information setting screen according to the first embodiment. [Figure 10] This is a schematic block diagram showing the configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0012] <First Embodiment> Hereinafter, embodiments will be described in detail with reference to the drawings. FIG. 1 is a diagram showing the configuration of a contract support system according to the first embodiment. The contract support system 1 supports contracts related to real estate. Examples of contracts related to real estate include contracts concerning the transfer or lease of real estate (property contracts), insurance contracts such as fire insurance that compensates for damages occurring on real estate, and the like.

[0013] The contract support system 1 includes a contract support server 10 and an RPA terminal 20. The contract support server 10 is a web server for supporting contracts related to real estate. The RPA terminal 20 is a terminal connected to the internal network of an insurance company and installed with an RPA (robotic process automation) program. The RPA terminal 20 automatically operates the insurance system S connected to the internal network of the insurance company, and automatically creates documents related to insurance contracts. The RPA terminal 20 is an example of an RPA unit.

[0014] The contract support system 1 is accessed by real estate agents (real estate dealers, real estate lessors, real estate brokers, etc.), insurance providers (insurance companies, insurance agencies, etc.), and consumers (persons who purchase or rent real estate properties) using terminals such as PCs. Hereinafter, the terminal of a real estate agent is referred to as a real estate agent terminal T1, the terminal of an insurance provider as an insurance provider terminal T2, and the terminal of a consumer as a consumer terminal T3.

[0015] FIG. 2 is a diagram showing the functional configuration of the contract support server 10 according to the first embodiment. The contract support server 10 includes a database 11, a web interface 12, and a controller 13. The database 11 of the contract support server 10 has a user table 111 that stores user information, a property table 112 that stores property information, an insurance table 113 that stores insurance information, a real estate contract table 114 that stores information related to real estate contracts, and an insurance contract table 115 that stores information related to insurance contracts.

[0016] The user table 111 stores information such as user IDs, authentication information, user authorities, names, and addresses. The user authority is information for identifying whether a user uses the contract support system 1 as a real estate agent, as an insurance agent, or as a consumer. The contract support server 10 provides services corresponding to the user authority to the user. The user table 111 includes personal information of users (at least users with consumer authority).

[0017] The property table 112 includes property IDs, property names, locations, building ages, offered fees, exclusive areas, and the like. The property table 112 records at least real estate information to be displayed on web pages for consumers. The information to be displayed on the web pages for consumers is input by a real estate agent. When the real estate property is an apartment house, the property table 112 may further include room information such as room numbers and resident floors. When the real estate property is an apartment house, the property table 112 may store building information and room information separately, and may have a structure in which the room information references the building information. The property table 112 also records real estate information related to insurance, such as fire resistance standards and building structures (types of columns). The real estate information related to insurance may be input by an insurance agent or by a real estate agent.

[0018] The insurance table 113 stores information on insurance related to real estate properties, such as the presence or absence of insurance discounts and types of insurance special provisions, in association with property IDs. The insurance information is input by an insurance agent. The real estate contract table 114 stores information about the real estate contract, such as the real estate agent's user ID, the consumer's user ID, the property ID of the property covered by the contract, the contract price, and the contract status, as well as an agreement flag indicating whether the consumer has agreed to provide the insurance company with information about the real estate contract. The insurance contract table 115 stores information related to insurance contracts, such as the insurance company's user ID, the consumer's user ID, the property ID of the insured property, the contract details, and the payment status.

[0019] The web interface 12 accepts web access from real estate agent terminal T1, insurance agent terminal T2, consumer terminal T3, and RPA terminal 20, and provides web services via browser software, etc. The controller 13 operates the database 11 according to the operations of various terminals entered via the web interface 12.

[0020] Regarding the insurance system S of insurance companies An insurance company has an insurance system S for managing insurance contracts. The insurance system S has an internal interface and an external interface. The internal interface is accessed by the insurance company's employees and is used for creating quotations and contracts. The external interface is accessed by consumers and is used for reviewing contract details and applying for insurance.

[0021] Regarding the operation of Contract Support System 1 The following describes the flow of a real estate contract using the contract support system 1. Figure 3 is a flowchart showing the flow of a real estate contract according to the first embodiment. First, the real estate agent registers information about the real estate property that is the subject of the property contract with the contract support server 10 (step S1). When the real estate agent determines the consumer who will be the contracting party for the property contract, they create an account for the consumer in the contract support server 10 using contact information such as an email address obtained from the consumer, and register it in association with the real estate property (step S2). The contract support server 10 sends an invitation letter (such as an email) containing information such as a URL for accessing the contract support server 10 to the registered contact person (step S3).

[0022] The consumer logs into the contract support server 10 by referring to the guidance letter and registers the personal information necessary for the property contract in the created account (Step S4). The contract support server 10 uses the real estate property information and the consumer's personal information to create the necessary documents such as a contract and memorandum (Step S5). The real estate agent and the consumer mutually confirm the created documents, and if there are no problems, they affix their electronic signatures to the documents (Step S6). This concludes the property contract between the real estate agent and the consumer.

[0023] The contract support server 10 sends an insurance contract notification letter to the consumer's contact person, which includes information such as a URL to access the contract support server 10 (step S7). When the consumer accesses the contract support server 10, the contract support server 10 displays a screen asking whether the consumer agrees to provide information about the property contract to the insurance company for the purpose of the insurance contract (step S8). If the consumer does not agree to provide the information (step S8: NO), the contract support server 10 does not provide information about the property contract to the insurance company. In this case, the insurance company and the consumer proceed with the contract as before.

[0024] If the consumer agrees to provide information (Step S8: YES), the contract support server 10 makes the insurance contract for the real estate property related to the agreed property contract executable. The insurer logs into the contract support server 10 using the insurer terminal T2 and selects the insurance contract to be worked on. The insurer inputs information about the selected insurance contract into the contract support server 10 (Step S9). At this time, the contract support server 10 is already pre-filled with real estate information that has been registered in the property transaction. In other words, the insurer inputs any missing information from the information about the selected insurance contract into the contract support server 10. This allows the contract support server 10 to reduce the workload of the insurer in inputting information about the insurance contract.

[0025] When an insurance company registers information about an insurance contract with the contract support server 10, the contract support server 10 sends a letter to the consumer requesting them to enter the necessary information about the insurance contract (step S10). The letter includes information such as a URL to access the contract support server 10. When the consumer accesses the contract support server 10, the contract support server 10 displays an input form for the necessary information about the insurance contract on the consumer terminal T3. At this time, the contract support server 10 has already entered the personal information that has been registered in the property transaction. In other words, the consumer enters the missing information about the insurance contract into the contract support server 10 (step S11). This allows the contract support server 10 to reduce the amount of work required for the consumer to enter information about the insurance contract. Once the consumer has entered the necessary information regarding the insurance contract, the contract support server 10 becomes ready to accept registration of documents related to the insurance contract (such as quotations and contracts) from the insurance company.

[0026] The RPA terminal 20 automatically logs into the contract support server 10 at regular intervals using the RPA application and collects insurance information that is at the stage of accepting document registration (step S12). The RPA terminal 20 accesses the contract support server 10 using an account that has been pre-registered with the contract support server 10 for RPA purposes. From the collected insurance information, the RPA terminal 20 extracts the items necessary for document creation in the insurance system S and inputs the information of the extracted items into the insurance system S (step S13). As a result, the insurance system S creates documents related to the insurance contract. The RPA terminal 20 uploads the documents generated by the insurance system S to the contract support server 10 using the RPA application (step S14). As a result, the contract support system 1 can automatically obtain documents related to the insurance contract when the consumer enters the necessary information related to the insurance contract.

[0027] When documents related to an insurance contract are registered with the contract support server 10 by the RPA terminal 20, the contract support server 10 sends a notice to the consumer requesting confirmation of the contract details (step S15). The notice includes information such as a URL for accessing the contract support server 10. When the consumer accesses the contract support server 10, the contract support server 10 displays the documents related to the insurance contract. If the uploaded document is a quotation, the consumer inputs instructions to the contract support server 10 to create a contract based on the quotation. If the uploaded document is a contract, the contract support server 10 displays a screen on the consumer terminal T3 that includes the contract data and a link to access the insurance system S screen for concluding a contract in accordance with the contract. When the consumer accesses the insurance system S via the link, they can conclude an insurance contract in accordance with the insurance system S.

[0028] Operation of Contract Support Server 10 The operation of the contract support server 10 in the above procedure will be explained below. When registering real estate property information in step S1, the web interface 12 of the contract support server 10 displays a property registration screen for registering a new real estate property on the real estate agent terminal T1. The property registration screen includes an input form for entering each item in the property table 112. The controller 13 does not display the property registration screen in step S1 if the logged-in user does not have real estate agent privileges. The controller 13 checks the contents entered in the input form to ensure that all required items are entered and that there are no formatting errors. Required items are those items in the property table 112 that are necessary for the property contract, but not all items. For example, property name, lot number, and floor area are required items, but fire resistance standards, building structure, and location do not have to be required items for real estate agents. If there are no errors in the input contents, the controller 13 records the entered items in the property table 112.

[0029] In step S2, the web interface 12 displays a property contract registration screen on the real estate agent terminal T1 for registering information about property contracts. The property contract registration screen includes input forms for specifying the real estate property to be the subject of the contract, information about the contract details including the contract price, and the name and contact information of the consumer who will be the contracting party. Once information is entered into the input forms, the controller 13 creates a user account with consumer privileges based on the consumer's name and contact information and records it in the user table 111. Specifically, the controller 13 creates a new user ID and authentication information, associates the name and contact information entered in association with the user ID with the user privileges of the consumer, and records it in the user table 111. The controller 13 also associates the real estate agent's user ID, the newly generated consumer's user ID, the property ID of the property subject to the contract, and the entered contract details information and registers them in the real estate contract table 114. The property contract registration screen is displayed when all required items related to property contracts have been registered in the property table 112. In other words, the contract support server 10 allows the association of a consumer with a real estate property if the items necessary for a transfer or lease contract among the real estate information are met.

[0030] When the controller 13 creates a consumer user account, in step S3 it generates an invitation letter for accessing the contract support server 10 based on the user ID and authentication information, and sends it to the registered contact. At this time, the controller 13 may also generate a URL that allows direct login without the user ID and authentication information to be entered, and include it in the invitation letter.

[0031] In step S4, the web interface 12 displays a user information input screen for registering personal information on the consumer terminal T3. The user registration screen includes an input form for entering each item in the user table 111. The controller 13 checks the contents entered in the input form to ensure that all required items are entered and that there are no formatting errors. Required items are those items in the user table 111 that are necessary for the property contract, but not all items. For example, date of birth, address, and employment information may be required items. The name and contact information are pre-filled in the input form. The consumer may correct the information already entered in the input form. If there are no errors in the input contents, the controller 13 overwrites and saves the information in the property table 112 associated with the logged-in consumer's user ID. In other embodiments, the contract support system 1 may have the real estate agent enter all the necessary consumer information in step S2, and the consumer's input in step S4 may be omitted.

[0032] In step S5, the controller 13 uses the property contract information registered in the real estate contract table 114, the user information registered in the user table 111 in association with the user ID included in the property contract information, and the property information registered in the property table 112 in association with the property ID included in the property contract information to create a document in a predetermined format. The controller 13 then adds the created document to the real estate contract table 114.

[0033] In step S6, the web interface 12 displays to the real estate agent and the consumer a contract screen that includes the document created in step S5 and a button for performing an electronic signature. The electronically signed document is registered in the real estate contract table 114. The controller 13 determines whether both the electronic signature from the real estate agent and the electronic signature from the consumer are present, and if both are present, it determines that the property contract has been concluded.

[0034] When an insurance agent logs into the contract support server 10 using the insurance agent terminal T2, the web interface 12 displays a list of properties handled by the logged-in insurance agent. Figure 4 is an example of the property list screen according to the first embodiment. The property list screen is not displayed to users who do not have user privileges as an insurance agent. The property list screen includes the property name of the property handled by the insurance agent, the name of the real estate agent, a settings button, and an insurance application start button. The settings button is for setting information for the insurance contract. The application start button is for starting the application process based on the set information. The application start button may be disabled (grayed out) until the setting of the information necessary for the insurance contract is complete. The information necessary for the insurance contract does not overlap with the information necessary for the property contract.

[0035] When the settings button is pressed, the web interface 12 displays an input screen for information regarding the insurance contract for the property. Figure 5 is an example of a common insurance information setting screen according to the first embodiment. As shown in Figure 5, the common insurance information setting screen is a screen for setting information common to the building among the information necessary for the insurance contract. Information common to the building refers to information about the building, not individual units, among the information necessary for the insurance contract of real estate properties. For example, the sale or rental of an apartment building is done for each unit of the apartment building, so the room number and floor area differ for each unit. On the other hand, the name of the property, postal code, address, building structure, etc. are common to multiple real estate properties related to the same building. The common insurance information setting screen includes an input form for building information. When the controller 13 displays the common insurance information setting screen, it reads the information related to the property from the property table 112 and sets it as the initial value of the input form on the common insurance information setting screen. When the save button on the common insurance information setting screen is pressed, the controller 13 records the information entered in the input form in the property table 112.

[0036] When the controller 13 determines that the necessary information for the insurance contract has been set in the property table 112, it enables the "Start Acceptance" button on the property list screen to be pressed.

[0037] If it is determined in step S6 that a property contract has been concluded and the insurance company has pressed the button to start accepting applications for the building related to the property contract, the controller 13 sends an informational letter regarding the insurance contract to the consumer related to the property contract in step S7.

[0038] In step S8, the web interface 12 displays an information provision permission screen to the consumer terminal T3 to obtain permission to provide personal information for the insurance contract. Figure 6 is an example of the information provision permission screen according to the first embodiment. The information provision permission screen includes an explanation of providing personal information to the insurance company for the insurance contract, an explanation of the privacy policy regarding the handling of such personal information, a confirmation checkbox, and an accept button. Checking the confirmation checkbox indicates the consumer's willingness to agree to the privacy policy. The controller 13 turns on the agreement flag included in the information of the real estate contract table 114 if the confirmation checkbox is ON and the accept button is pressed. If the consumer refuses to provide information to the insurance company, they can close the screen without pressing the accept button.

[0039] In step S9, the web interface 12 displays a list of consumers (policyholders) who have consented to the provision of information on the insurance agent terminal T2. Figure 7 is an example of the policyholder list screen according to the first embodiment. The policyholder list screen is not displayed to users who do not have user privileges as an insurance agent. The policyholder list screen includes policyholder information such as the policyholder name, a common settings button, an individual settings button, a registration request button, and an application request button. The policyholder information is read from the user table 111. When the common settings button is pressed, the web interface 12 displays the common insurance information settings screen shown in Figure 5 on the insurance agent terminal T2. When the individual settings button is pressed, the web interface 12 displays the individual insurance information settings screen on the insurance agent terminal T2 for setting property information that is not common to the property, such as room number and floor area. When the registration request button is pressed, the controller 13 sends an email to the policyholder requesting them to register the information necessary for the insurance contract. When the application request button is pressed, the controller 13 sends an email to the policyholder requesting them to apply for a contract. Each button displays an icon indicating the status of the process associated with that button. For example, if the "Check" icon is set for the Common Settings button, it means that the settings for the information common to the building among the information required for the insurance contract have been completed. For example, if the "X" icon is set for the Common Settings button, it means that the information common to the building among the information required for the insurance contract is missing.

[0040] When the individual settings button is pressed, the web interface 12 displays an input screen for information for insurance contracts specific to each policyholder. Figure 8 is an example of an individual insurance information setting screen according to the first embodiment. As shown in Figure 5, the individual insurance information setting screen is a screen for setting information that differs for each policyholder among the information necessary for an insurance contract. Examples of information that differs for each policyholder include information that differs for each property unit, such as the scheduled handover date, room number, floor of residence, floor area, and replacement value, as well as information related to the insurance contract, such as the details of insurance discounts and the details of various special provisions. The individual insurance information setting screen includes an input form for individual information. When the controller 13 displays the individual insurance information setting screen, it reads information related to the property from the property table 112 and the real estate contract table 114 and sets it as the initial value of the input form on the individual insurance information setting screen. For example, the room number, floor of residence, and floor area are read from the property table 112, and the contract price set for the scheduled handover date and replacement value is read from the real estate contract table 114. When the save button on the individual insurance information settings screen is pressed, the controller 13 records the information related to the real estate property from the information entered in the input form into the property table 112. The controller 13 also records the information related to the insurance contract from the information entered in the input form into the insurance contract table 115.

[0041] In step S11, the web interface 12 displays an input screen for insurance contract information on the consumer terminal T3. Figure 9 is an example of a policyholder information setting screen according to the first embodiment. As shown in Figure 9, the policyholder information setting screen is a screen for setting the policyholder's personal information and requests, which are among the information necessary for the insurance contract. Examples of personal information of the policyholder necessary for the insurance contract include the policyholder's name, date of birth, gender, telephone number, and address. Examples of the policyholder's requests include the use of the property, whether or not household contents insurance is required and the amount set, whether or not flood damage insurance is required, and whether or not personal liability insurance is required. The policyholder information setting screen includes an input form. When the controller 13 displays the policyholder information setting screen, it reads information related to the policyholder from the user table 111 and sets it as the initial value of the input form on the policyholder information setting screen. For example, name, date of birth, gender, and telephone number are read from the user table 111. The controller 13 may also allow the user to select either the property's purchase address or the property's current location as the initial address value. The user may read the property's purchase address from the user table 111 and the property's current location from the property table 112. When the application button on the policyholder information settings screen is pressed, the controller 13 records the information entered in the input form into the insurance contract table 115.

[0042] Operation of RPA terminal 20 The RPA terminal 20 automatically logs into the contract support server 10 at regular intervals via the RPA application. When the RPA terminal 20 logs in with the user privileges of an insurance company, in step S12, it presses the "CSV Download" button on the customer list screen shown in Figure 7 to collect the information necessary for the insurance contract as CSV data. When the "CSV Download" button is pressed, the controller 13 of the contract support server 10 converts the information necessary for the insurance contract related to the customer displayed on the customer list screen into CSV data and sends it to the RPA terminal 20. Specifically, the controller 13 generates the CSV data using the following procedure. First, the controller 13 reads the property information from the property table 112, and the insurance company related to the logged-in user is set as the responsible insurance company. The controller 13 then reads the property contract information from the real estate contract table 114 that has the agreement flag ON and includes the property ID read from the property table 112. This allows the controller 13 to read property contract information for buildings that the logged-in user can handle and for which the consumer has agreed to provide the information. Next, the controller 13 reads user information associated with the user ID included in the property contract information from the user table 111. The controller 13 also reads insurance contract information associated with the user ID included in the property contract information from the insurance contract table 115. The controller 13 combines the corresponding building information and user information (consumer information) with each property contract information to generate inversely normalized data. The controller 13 writes the inversely normalized data to a CSV file. The RPA terminal 20 may also obtain the CSV data directly from the controller 13 via an API without going through the web interface 12.

[0043] When the RPA terminal 20 receives CSV data from the contract support server 10, it extracts information relevant to document creation by excluding documents for which insurance contracts have already been created, documents lacking necessary information for insurance contracts, and documents for which the consumer has not applied. Once the RPA terminal 20 has extracted the information relevant to document creation, it inputs this information into the insurance system S in step S13. The insurance system S creates the documents using the input data. The document file name includes, for example, the insurance contract ID.

[0044] In step S14, the RPA terminal 20 uploads documents related to the insurance contract using the API of the contract support server 10. For example, the contract support server 10 has a document upload API defined that takes the insurance contract ID and the document file as arguments, and the RPA terminal 20 can upload the documents by accessing the contract support server 10 according to the said document upload API.

[0045] "effect" In this way, the contract support system 1 accepts registration of real estate information from real estate companies and presents the real estate information to consumers. The contract support system 1 accepts registration of personal information from consumers and associates consumers with real estate properties when a property contract is made for a real estate property. The contract support system 1 generates contract document information for insurance contracts using the consumer's personal information registered in the user table 111 and the real estate information of the real estate property registered in the property table 112. The information used to create the contract document information is not information newly registered for insurance contracts, but information that was registered in the user table 111 and the property table 112 before the consumer and the real estate property were associated for the property contract. As a result, the contract support system 1 can reduce the amount of information that needs to be entered when making an insurance contract by using the information that was entered for the property contract. Therefore, the contract support system 1 can reduce the burden on consumers or insurance companies regarding insurance contracts.

[0046] Furthermore, the contract support system 1 includes an RPA terminal 20 with an RPA application specific to each insurance company installed. This allows the system to automatically operate the insurance company's unique insurance system S and automatically generate the necessary documents. As a result, the contract support system 1 can reduce the burden on insurance companies regarding insurance contracts.

[0047] <Other Embodiments> Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes are possible. In other embodiments, the order of the above-described processes may be changed as appropriate. Also, some processes may be executed in parallel. The contract support server 10 according to the above embodiment may be configured by a single computer, or the configuration of the contract support server 10 may be divided and arranged on multiple computers, and the multiple computers may cooperate with each other to function as the contract support server 10.

[0048] In the embodiments described above, the insurance company manages contracts using its own insurance system S, but is not limited to this. For example, in other embodiments, insurance contracts may be managed by attaching electronic signatures to insurance contract documents using the contract support server 10. In this case, the contract support system 1 does not need to be equipped with an RPA terminal 20.

[0049] The contract support system 1 according to the above embodiment shares the property table 112 for property contracts and insurance contracts, but is not limited to this. For example, the contract support system 1 according to another embodiment may have separate property tables 112 for property contracts and property tables 112 for insurance contracts. In this case, the controller 13 copies the information recorded in the property table 112 for property contracts to the property table 112 for insurance contracts before receiving information for insurance contracts. In addition, in the contract support system 1 according to another embodiment, the insurance contract table 115 may directly hold information such as consumer personal information and property information without referring to other tables. In this case, the controller 13 copies the necessary information from the user table 111, property table 112, and real estate contract table 114 to the insurance contract table 115 before receiving information for insurance contracts.

[0050] The contract support system 1 according to the above embodiment includes an RPA terminal 20 that can connect to the insurance company's internal network. However, in other embodiments, if the insurance system S allows access to an internal interface via the internet, the contract support server 10 may be equipped with an RPA application (RPA unit) instead of the RPA terminal 20.

[0051] <Computer Configuration> Figure 10 is a schematic block diagram showing the configuration of a computer according to at least one embodiment. The computer 90 includes a processor 91, main memory 92, storage 93, and an interface 94. The contract support server 10 and RPA terminal 20 described above are implemented in the computer 90. The operation of each processing unit described above is stored in storage 93 in the form of a program. The processor 91 reads the program from storage 93, loads it into main memory 92, and executes the above processing according to the program. The processor 91 also allocates memory areas in main memory 92 corresponding to each of the above-mentioned storage units according to the program. Examples of the processor 91 include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a microprocessor.

[0052] The program may be for implementing some of the functions that the computer 90 is to perform. For example, the program may perform functions in combination with other programs already stored in storage, or in combination with other programs implemented on other devices. In other embodiments, the computer 90 may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to, or instead of, the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions implemented by the processor 91 may be implemented by the integrated circuit. Such an integrated circuit is also included as an example of a processor. In other embodiments, the computer 90 may be virtualized on one or more computers.

[0053] Examples of storage 93 include magnetic disks, magneto-optical disks, optical disks, and semiconductor memory. Storage 93 may be an internal medium directly connected to the bus of the computer 90, or it may be an external medium connected to the computer 90 via an interface 94 or a communication line. Furthermore, if this program is delivered to the computer 90 via a communication line, the computer 90 that receives the delivery may load the program into the main memory 92 and execute the above processing. In at least one embodiment, storage 93 is a tangible storage medium that is not temporary.

[0054] Furthermore, the program may be intended to implement some of the functions described above. In addition, the program may be a so-called differential file (differential program) that implements the functions described above in combination with other programs already stored in storage 93. [Explanation of Symbols]

[0055] 1...Contract support system 10...Contract support server 11...Database 111...User table 112...Property table 113...Insurance table 114...Real estate contract table 115...Insurance contract table 12...Web interface 13...Controller 20...RPA terminal 90...Computer 91...Processor 92...Main memory 93...Storage 94...Interface S...Insurance system T1...Real estate agent terminal T2...Insurance agent terminal T3...Consumer terminal

Claims

1. A contract support system that assists with contracts related to real estate properties, The system accepts registration of real estate information necessary for the transfer or lease of real estate properties from the first user who has the authority to transfer, lease, or act as an intermediary for real estate properties. We accept registration of personal information of a second user who has the authority to receive the transfer or lease of real estate property. When the second user enters into a contract for the transfer or lease of the real estate property, the second user and the real estate property are associated, Using the personal information of the second user and the real estate property, which were registered before the association between the second user and the real estate property, contract document information for an insurance contract relating to the real estate property is generated. Contract support system.

2. The aforementioned real estate information includes items necessary for a transfer or lease agreement and items necessary for an insurance contract. If the necessary items for a transfer or lease agreement are met among the aforementioned real estate information, permission will be granted to associate the second user with the aforementioned real estate property. The contract document information is generated when the necessary items for the insurance contract are met among the aforementioned real estate information. The contract support system according to claim 1.

3. If the aforementioned real estate information is lacking items necessary for an insurance contract, the system will accept input of the missing items from a third-party user with third-party user authority to conduct insurance business related to the real estate property. The contract support system according to claim 2.

4. A computer capable of accessing an internal system that performs processing related to insurance business pertaining to the third user, comprising an RPA unit that, when the contract document information is created, instructs the internal system to create predetermined document data using the contract document information. The contract support system according to claim 3.

5. A contract support system that assists with real estate property contracts is The first step involves receiving registration of real estate information necessary for the transfer or lease of real estate from the first user who has the authority to transfer, lease, or broker real estate properties, and Steps to accept registration of personal information of a second user who has the authority to receive the transfer or lease of real estate property, When the second user enters into a contract for the transfer or lease of the real estate property, the steps include associating the second user with the real estate property, A step of generating contract document information for an insurance contract relating to the real estate property, using the personal information of the second user and the real estate information of the real estate property, which were registered before the association of the second user and the real estate property. A contract support method that includes the following features.

Images