Management support system, management support method, and program

Abstract

To efficiently perform a real estate transaction.SOLUTION: A management support system includes: management company terminals provided in management companies managing construction properties; intermediary company terminals provided in intermediary companies mediating real estate transactions of the construction properties; and management support devices connected to the management company terminals and the intermediary company terminals. The management support system comprises: a document name registration unit for registering document names of documents which can be transmitted from the management companies to the intermediary companies with respect to each of the management companies; a presentation unit for presenting the document names registered by the document name registration unit to the intermediary company terminals; a receiving unit for receiving transmission requests of document data corresponding to the document names received by the intermediary company terminals on the basis of the document names presented by the presentation unit; and a transmission unit for transmitting a request notification indicating the receipt of the transmission request, to the management company terminals when the receiving unit receives the transmission request. The presentation unit presents the document data acquired from the management company terminals in response to the request notification, to the intermediary company terminals.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to a management support system, a management support method, and a program.

Background Art

[0002] Conventionally, in real estate transactions, a brokerage company has been involved and contracts have been made. The brokerage company conducts brokerage services. The brokerage services include services related to sales that connect a person wishing to purchase and the owner of a building, and services related to rentals that connect a person wishing to move in and the owner of a building. The building is, for example, a condominium (dwelling unit) or a detached house. As a related technology, Patent Document 1 discloses a system in which property data is publicly disclosed on a website among a lender, a borrower, and a brokerage firm, and when the lender and the borrower who is a person wishing to move in directly negotiate and reach an agreement, the brokerage firm mediates the lease contract (see, for example, Patent Document 1 below).

[0003] In addition, the owner of a building may entrust the management company with the management of the building. The management services include management of the occupants (for example, collection of rent, renewal of contracts, etc.) and maintenance management of the building. Also, when selling a building, the owner of the building may entrust a brokerage company with the sale. The brokerage company requests the management company to submit a request document, and the management company obtains the request document. Thus, real estate transactions include transactions of request documents in which the brokerage company requests the management company to submit a request document, and the management company sends the request document to the brokerage company in response to the request.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the transaction of request documents, communication between the intermediary company and the management company was carried out by phone, fax, or mail, which was time-consuming and laborious for both parties and prone to errors. Therefore, in the prior art, there was a problem that the transaction of request documents could not be carried out quickly, accurately, and easily, that is, the real estate transaction could not be carried out efficiently.

[0006] In view of the above circumstances, an object of the present invention is to provide a technology capable of efficiently conducting real estate transactions.

Means for Solving the Problems

[0007] A management support system according to an aspect of the present invention includes a management company terminal provided by a management company that manages construction properties, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of construction properties, and a management support device connected to the management company terminal and the brokerage company terminal. The management support system includes a document name registration unit that registers, for each management company, the document names of documents that can be sent from the management company to the brokerage company, a presentation unit that presents the document names registered by the document name registration unit to the brokerage company terminal, a reception unit that receives a request for sending document data corresponding to the document name received by the brokerage company terminal based on the document name presented by the presentation unit, and a transmission unit that, when the reception unit receives the sending request, transmits a request notification indicating that fact to the management company terminal. The presentation unit is a management support system that presents the document data acquired from the management company terminal to the brokerage company terminal in response to the request notification.

[0008] A management support method according to one aspect of the present invention includes a management company terminal provided by a management company that manages a building property, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of the building property, and a management support device connected to the management company terminal and the brokerage company terminal. A computer of the management support system executes a document name registration step of registering, for each management company, the document names of documents that can be sent from the management company to the brokerage company, a presentation step of presenting the document names registered in the document name registration step to the brokerage company terminal, a reception step of receiving a request for sending document data corresponding to the document names received by the brokerage company terminal based on the document names presented in the presentation step, and a transmission step of, when receiving the sending request in the reception step, transmitting a request notification indicating that fact to the management company terminal. In the presentation step, the document data acquired from the management company terminal in response to the request notification is presented to the brokerage company terminal. It is a management support method.

[0009] A program according to one aspect of the present invention causes a computer of a management support system including a management company terminal provided by a management company that manages a building property, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of the building property, and a management support device connected to the management company terminal and the brokerage company terminal to function as a document name registration unit that registers, for each management company, the document names of documents that can be sent from the management company to the brokerage company, a presentation unit that presents the document names registered by the document name registration unit to the brokerage company terminal, a reception unit that receives a request for sending document data corresponding to the document names received by the brokerage company terminal based on the document names presented by the presentation unit, and a transmission unit that, when the reception unit receives the sending request, transmits a request notification indicating that fact to the management company terminal. The presentation unit presents the document data acquired from the management company terminal in response to the request notification to the brokerage company terminal.

Effects of the Invention

[0010] According to the present invention, real estate transactions can be efficiently performed.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13A

Figure 13B

Figure 14

Figure 15

Figure 16

Figure 17

Mode for Carrying Out the Invention

[0012] (Embodiment) (Network Configuration of Management Support System 1) FIG. 1 is an explanatory diagram showing the network configuration of the management support system 1 according to the embodiment. As shown in FIG. 1, the management support system 1 includes a management support server 100, a brokerage company terminal 110, and a management company terminal 120. Each device is communicably connected by a network 140 (for example, a network based on TCP / IP, a mobile network, etc.). Further, each device is a computer device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like.

[0013] (Management Support Server 100) The management support server 100 is an example of a management support device. The management support server 100 is managed by a system provider that provides the management support system 1. The management support server 100 manages the transaction of request documents exchanged between the brokerage company and the management company. The brokerage company conducts brokerage business. The brokerage business includes a business related to buying and selling that connects a person who wishes to purchase and the owner of a construction property, and a business related to leasing that connects a person who wishes to move in and the owner of a construction property. The management company conducts management business that substitutes for the owner of a construction property (building) to manage residents (for example, collecting rent, renewing contracts, etc.) and to perform maintenance management of the construction property. The construction property includes apartment houses such as condominiums (residential units of condominiums) and detached houses. When selling a building, the owner of the construction property may entrust the brokerage company with the sale. The brokerage company requests the management company to submit request documents, and the management company obtains the request documents. Thus, in real estate transactions, a transaction of request documents is conducted in which the brokerage company requests the management company to submit documents, and in response to the request, the management company sends the documents to the brokerage company. The request documents are, for example, documents necessary in real estate transactions such as an important matters investigation report, a management regulation, a repair plan, and general meeting materials.

[0014] The management support server 100 manages the transaction of request documents on a predetermined Web (World Wide Web) site or on a predetermined application (management support application) installed on the brokerage company terminal 110 or the management company terminal 120. The management support server 100 manages, for example, various documents that the management company can send to the brokerage company. More specifically, the management support server 100 includes a management support DB 101 and manages the properties handled by the management company, the persons in charge of each property in the management company, the documents that can be sent, the sending fees, and the like. In addition, the management support server 100 manages the request documents for each property desired by the brokerage company and the persons in charge of each property in the brokerage company. Details of the information stored in the management support DB 101 will be described later with reference to FIGS. 6 to 10.

[0015] (Brokerage company terminal 110) The brokerage company terminal 110 is provided in the brokerage company. The brokerage company terminal 110 is a portable terminal device carried by the staff of the brokerage company or a personal computer installed in the brokerage company. The portable terminal device is, for example, a smartphone, a tablet terminal, a notebook computer, etc. A management support app (application software) is installed in the brokerage company terminal 110 in advance. The brokerage company terminal 110 activates the management support app and displays the names of documents that can be sent for each construction property of each management company. When the brokerage company terminal 110 receives a request to send a request document according to the operation of the person in charge, it acquires the document data of the request document from the management company via the management support server 100.

[0016] (Management company terminal 120) The management company terminal 120 is arranged, for example, in the management company. The management company manages a plurality of construction properties. The management company terminal 120 is arranged, for example, in each business office (each branch) of the management company. The management company terminal 120 is, for example, a personal computer, but may also be a smartphone or a tablet terminal. In the management company terminal 120, a management support program (or a management support app) is activated to display the request status and creation status of request documents for various properties. The management company terminal 120 accepts various inputs, performs various edits and outputs according to the operations of the persons in charge of the management company. One management company terminal 120 may be arranged in the branch of the management company, or a plurality of management company terminals 120 may be arranged. In response to a sending request from the brokerage company terminal 110 via the management support server 100, the management company terminal 120 transmits the document data of the request document to the management support server 100. The management support server 100 stores the document data received from the management company terminal 120 in the management support DB 101 and transmits it to the brokerage company terminal 110.

[0017] (Hardware configuration of the management support server 100) FIG. 2 is a block diagram showing an example of the hardware configuration of the management support server 100. In FIG. 2, the management support server 100 includes a CPU 201, a memory 202, and a communication I / F (interface) 203. Each part is connected by a bus 220.

[0018] The CPU 201 controls the overall operation of the management support server 100. The memory 202 includes, for example, a ROM and a RAM. For example, the ROM stores various programs such as the management support program according to the present embodiment. The RAM is used as a work area for the CPU 201. The programs stored in the memory 202 are loaded into the CPU 201 to cause the CPU 201 to execute the coded processes. The memory 202 includes a USB (Universal Serial Bus) flash memory, an SSD (Solid State Drive), a magnetic disk, and an optical disk.

[0019] The communication I / F 203 is connected to a network 140 such as the Internet through a communication line and is connected to other devices (for example, the agency company terminal 110 and the management company terminal 120) via the network 140. Also, the communication I / F 203 serves as an interface between the network 140 and the inside of the device itself and controls the input and output of data from other devices.

[0020] (Hardware Configuration of Agency Company Terminal 110 and Management Company Terminal 120) FIG. 3 is a block diagram showing an example of the hardware configuration of the agency company terminal 110 and the management company terminal 120. In FIG. 3, the agency company terminal 110 and the management company terminal 120 each include a CPU 301, a memory 302, a communication I / F 303, an input device 304, a display 305, an output device 306, and a storage medium I / F 307. Each unit is connected by a bus 320. Hereinafter, the configuration of the agency company terminal 110 will be described, and the description of the management company terminal 120 will be omitted, but the management company terminal 120 has a similar configuration.

[0021] The CPU 301 controls the overall operation of the agency company terminal 110. The memory 302 includes, for example, a ROM and a RAM. For example, the ROM stores various programs such as the management support program (or management support application) according to this embodiment.

[0022] The RAM is used as a work area of the CPU 301. The programs stored in the memory 302 are loaded into the CPU 301 to cause the CPU 301 to execute the coded processes. The memory 302 includes a USB flash memory, an SSD, a magnetic disk, and an optical disk.

[0023] The communication I / F 303 is connected to a network 140 such as the Internet through a communication line and is connected to other devices (for example, the management support server 100) via the network 140. Further, the communication I / F 303 manages the interface between the network 140 and the inside of the device itself and controls the input and output of data from other devices.

[0024] The input device 304 includes a touch panel, operation buttons, a keyboard, a mouse, a microphone, a camera, etc. The input device also includes a camera and a scanner. The display 305 displays images. The display 305 includes a touch panel type display unit.

[0025] The output device 306 is an output device excluding the display 305 and includes, for example, a speaker and a printer. The storage medium I / F 307 controls the reading and writing of data to various storage media of an external memory (for example, a USB flash memory, etc.) according to the control of the CPU 301.

[0026] (Problems when conducting transactions of request documents based on paper, etc.) Here, in the transaction of request documents, communication was carried out between the brokerage company and the management company by phone, fax, mail, email, etc. Specifically, for example, when the brokerage company obtains an important matter investigation report, it requests the management company by phone or fax. The management company estimates the requested documents and sends the transfer form to the brokerage company. After the brokerage company makes the transfer, it sends a transfer slip indicating that the transfer has been completed to the management company by fax, mail, etc. The management company confirms the deposit from the transfer slip, prepares the requested documents, and sends them to the brokerage company. For this reason, the management of various documents was complicated and there was a risk of document loss.

[0027] In addition, since the request documents are prepared following a predetermined business process (for example, document creation → redundant approval → shipping preparation), if any of the operations stops, it may take time to send the documents. Also, each staff member sometimes had to go to the office to check their own work.

[0028] Furthermore, in the case of transactions based on paper, etc., since the confirmation of deposits was carried out one by one, it was time-consuming. Also, when there was a discrepancy in the request content, a refund might be made from the management company to the brokerage company. The handling of refunds sometimes required a lot of time and effort.

[0029] As described above, when conducting the transaction of request documents based on paper, etc., there were problems such as it being time-consuming and laborious for both parties and mistakes also occurring. In other words, there was a problem that the transaction of request documents could not be carried out quickly, accurately, and easily, and the transaction of request documents could not be carried out efficiently. Therefore, in this embodiment, the complicated transaction of request documents is made online, enabling the efficiency of the transaction to be improved. Hereinafter, the outline of the management support system 1 will be described with reference to FIG. 4.

[0030] (Outline of the online transaction performed by the management support system 1) FIG. 4 is a sequence diagram showing an overview of the online transaction performed by the management support system 1. Hereinafter, first, in the management support system 1, the flow from the request for sending documents (step S401) to the presentation of document data to the intermediary company (step S411) will be described.

[0031] Step S401: The person in charge of the intermediary company makes a request for sending documents from a smartphone or a personal computer. Specifically, when the intermediary company terminal 110 receives the registration of the request for sending documents and the registration of the request information (for example, credit card in online payment) of the fee (issuing fee) required for presenting the requested documents after identifying the management company, the received information (request information) is transmitted to the management support server 100.

[0032] Step S402: When the management support server 100 receives the request information from the intermediary company terminal 110, it transmits a request notification indicating the sending request to the management company terminal 120 to have the management company confirm acceptance.

[0033] Step S403: The management company terminal 120 receives whether to accept from the person in charge of acceptance. If accepted, it receives the registration of the scheduled delivery date and transmits the received various information (acceptance information) to the management support server 100. Also, if accepted, the person in charge is registered for each task (workflow) related to the preparation of the requested documents.

[0034] Step S404: The management support server 100 receives the acceptance information from the management company terminal 120. Then, when the online payment of the issuing fee in the intermediary company terminal 110 is completed, the management support server 100 issues a receipt. The receipt is, for example, a qualified invoice (described later).

[0035] Step S405: When the management support server 100 issues a receipt, it notifies the management company terminal 120 of the start of creating a request document. As a result, the document creator starts creating the document. Note that messages can be exchanged between the agency company terminal 110 and the management company terminal 120 using the chat function. Therefore, it is possible to exchange messages between the person in charge of each task and the person in charge of the agency company. For example, in the task (status) of creating a document, it is possible to exchange messages between the creator and the person in charge of the agency company.

[0036] Step S406: The management company terminal 120 uploads the document data of the document created by the creator to the management support server 100.

[0037] Step S407: The management support server 100 issues a notice to approve the created document as a notice indicating the next task.

[0038] Step S408: The management company terminal 120 obtains the document data from the management support server 100 by the operation of the approver, accepts the approval result, and sends it to the management support server 100. The approval result is either approval or rejection. When the approver receives a rejection, the management support system 1 returns to Step S405. On the other hand, when the approver receives approval, the management support system 1 proceeds to Step S409.

[0039] Step S409: The management support server 100 issues a notice to request the sending of the approved document as a notice indicating the next task.

[0040] Step S410: The management company terminal 120 uploads the approved document data to the management support server 100 by the operation of the sender.

[0041] Step S411: The agency terminal 110 downloads the document data of the request document from the management support server 100 according to the operation of the person in charge of the agency. As a result, the agency terminal 110 can display the document data of the request document for which the sending request was made.

[0042] In this way, in the management support system 1, the agency can make a request for sending documents online and can download the document data of the request document uploaded by the management company. That is, the management support system 1 can perform the transaction of the request document quickly, accurately, and easily.

[0043] Next, the case where the request information is used for invoice settlement and the payment of the usage fee of the management company will be described.

[0044] Step S421: The management support server 100 issues an invoice according to the monthly order quantity of the request document and transmits it to the agency terminal 110.

[0045] Step S422: The agency pays the issuance fee to the system provider by a predetermined date every month. The notice of payment is transmitted from the agency terminal 110 or from the financial institution of the payment destination to the management support server 100.

[0046] Step S423: The management support server 100 causes the management company terminal 120 to display a screen showing the monthly order quantity and the sales amount. The screen can be viewed by, for example, the accounting staff of the management company. Step S424: The system provider pays the sales amount to the management company. The notice of payment is transmitted from the management company terminal 120 or from the financial institution of the payment destination to the management support server 100.

[0047] Step S425: The management support server 100 causes the management company terminal 120 to display the usage details and the invoice details screen of the management support system 1. The invoice details screen can be viewed by, for example, the accounting staff of the management company.

[0048] Step S426: The management company pays the usage fee of the management support system 1 to the system provider. The usage fee is, for example, an amount corresponding to the sales amount of the management company, specifically, an amount obtained by multiplying a predetermined ratio by the sales amount.

[0049] In this way, in the management support system 1, the brokerage company can perform online settlement in transaction units or invoice settlement on a monthly basis with respect to the system provider. Also, the management company can obtain the monthly sales amount through the system provider by paying the usage fee to the system provider.

[0050] (Functional configuration of the management support system 1) FIG. 5 is a block diagram showing an example of the functional configuration of the management support system 1. In FIG. 5, the management support system 1 includes a document name registration unit 501, a presentation unit 502, a reception unit 503, a transmission unit 504, a settlement unit 505, an authority registration unit 506, and an issuance unit 507. Each functional unit is provided, for example, in the management support server 100. For this reason, each functional unit is realized by the CPU 201 provided in the management support server 100. That is, each functional unit is realized by the CPU 201 of the management support server 100 executing a management support program stored in the memory 202.

[0051] (Document name registration unit 501) The document name registration unit 501 registers the names of documents (hereinafter sometimes referred to as "sendable documents") that can be sent from the management company to the brokerage company. The sendable documents are, for example, various documents used in real estate transactions such as important matter investigation reports, management regulations, repair plans, and general meeting materials. The sendable documents vary for each management company. For example, the sendable documents are determined by the contract between the management company and the owner of the building property. Therefore, for example, even if "general meeting materials" are included in the sendable documents of Company A, "general meeting materials" may not be included in the sendable documents of Company B. The names of the sendable documents (hereinafter sometimes referred to as "sendable document names") are registered for each management company. The registration of the sendable document names is registered as master data.

[0052] Note that the sendable documents are appropriately updated. Also, the management company does not know when a sending request will come from the brokerage company. For this reason, it is not suitable to always hold the document data of the sendable documents. It is suitable to prepare the document data when a request is made and send it to the brokerage company.

[0053] (Presentation unit 502) The presentation unit 502 presents the sendable document names registered by the document name registration unit 501 to the brokerage company terminal 110. Specifically, the presentation unit 502 displays a list of sendable document names or displays the sendable document names narrowed down by the search function on the display 305 of the brokerage company terminal 110. The timing of the presentation by the presentation unit 502 is the timing when an operation indicating the presentation of the sendable document names is received from the staff operating the brokerage company terminal 110. The brokerage company terminal 110 receives the name of the requested document from among the sendable document names presented by the presentation unit 502. When the brokerage company terminal 110 receives the name of the requested document, it sends a request for sending the document data corresponding to the document name to the management support server 100.

[0054] (Receiving unit 503 and transmitting unit 504) The receiving unit 503 receives a sending request from the brokerage company terminal 110. When the receiving unit 503 receives a sending request, the sending unit 504 sends a request notification indicating that fact to the management company terminal 120. When the management company terminal 120 receives the request notification from the sending unit 504, it displays that it has received the request notification. When the management company terminal 120 displays that it has received the request notification, it accepts the input of the document data indicated by the request notification from the person in charge of creating the document. The management company terminal 120 sends the received document data to the management support server 100.

[0055] The management support server 100 stores the document data received from the management company terminal 120 in the management support DB 101. The presenting unit 502 sends the document data to the brokerage company terminal 110 in response to a request from the brokerage company terminal 110.

[0056] (Registration of construction properties and transactions of request documents in units of construction properties) The document name registration unit 501 registers by associating each construction property managed by the management company with the name of the document that can be sent. The name of the document that can be sent has been previously registered (master registration) in the document name registration unit 501 for each management company. Then, in the registration of each construction property, the document name registration unit 501 registers by associating the name of the document that can be sent of the management company that has already been registered with each construction property. As a result, for each management company, it is possible to register each construction property by uniformly associating it with the name of the document that can be sent.

[0057] The presenting unit 502 presents the document name to the brokerage company terminal for each construction property. The brokerage company terminal 110 accepts a sending request for document data for each construction property from the person in charge of the brokerage company and sends the sending request for each construction property to the management support server 100. The receiving unit 503 receives the sending request for the document data received by the brokerage company terminal 110 for each construction property. The sending unit 504 sends a request notification to the management company for each construction property.

[0058] (Online payment) The document name registration unit 501 registers the fee for each sendable document name. The presentation unit 502 presents the payment fee corresponding to the send request to the intermediary company terminal. The payment fee is the amount paid from the intermediary company terminal 110 (intermediary company) to the management support server 100 (system provider).

[0059] The settlement unit 505 performs online settlement of the payment fee in response to a request from the intermediary company. The online settlement is, for example, settlement by credit card. Note that the online settlement may also include debit card settlement, online electronic money settlement, and QR (registered trademark) code settlement. Specifically, the settlement unit 505 transmits the payment fee and the credit card number obtained from the intermediary company terminal 110 to the credit card company server to request settlement from the credit card company server. When approval is obtained from the credit card company server, the settlement by credit card is completed.

[0060] When the online settlement is completed, the transmission unit 504 transmits a creation start notification (described later) indicating the start of creation of document data to the management company terminal 120.

[0061] (Notification of task) The management company prepares the requested documents through a workflow (business process) consisting of multiple tasks. The multiple tasks include an acceptance task, a creation task, an approval task, and a sending task. Note that hereinafter, the current task in the workflow may be referred to as the "status". The acceptance task is a task of accepting the send request indicated by the request notification. In the acceptance task, the person in charge of the acceptance task determines whether to accept the request and inputs the determination result into the management company terminal 120. The creation task is a task of creating the requested document after acceptance is determined in the acceptance task. The person in charge of the creation task creates the requested document and inputs the document data of the created document into the management company terminal 120. The approval task is a task for approving the documents created in the creation task. The person in charge of the approval task decides whether to approve or reject the created request documents and inputs the decision result into the management company terminal 120. The person in charge of the approval task is, for example, the supervisor of the person in charge of the creation task. The approval task is carried out by multiple persons in charge. In other words, the approval task includes approval task 1 and approval task 2 that is carried out after approval task 1. The sending task is a task for sending the document data of the documents approved in the approval task. The person in charge of the sending task operates the management company terminal 120 to send the document data of the approved documents to the management support server 100.

[0062] The authority registration department 506 registers the person in charge for each of the multiple tasks. Specifically, the authority registration department 506 registers the person in charge for each of the receiving task, the creation task, the approval task, and the sending task. The registration of the person in charge is carried out based on the operation of the staff of the management company who have a predetermined authority (for example, "property management" described later). Note that the persons in charge registered in the authority registration department 506 will be separate persons in charge in a large-scale management company, but may be overlapping persons in charge in a small-scale management company.

[0063] When each task is completed in each status, the management company terminal 120 receives the completion of the task from the staff in charge of each task. When the management company terminal 120 receives the completion of the task, it sends a completion notice indicating that the task has been completed to the management support server 100. When the transmission department 504 receives the completion notice of each task, it sends a start notice indicating the start of the next task to the management company terminal 120.

[0064] (Issuance of Eligible Invoice, etc.) The issuing department 507 issues a predetermined document indicating the fee (issuing fee) to be paid by the intermediary company terminal 110 for the sending request. The predetermined document is, for example, a receipt in the case of online settlement, or a normal invoice in the case of invoice settlement. The receipt is issued after the completion of online settlement. Specifically, the receipt includes, in addition to a normal receipt, a qualified invoice. The qualified invoice is a document based on compliance with the invoice system. Specifically, the qualified invoice is a document in which specific items necessary when the business partner conducts input tax deduction in the transaction are described. The specific items are as follows (1) to (6). Among these, if any are missing, it may not be regarded as a qualified invoice. (1) The name or title and business operator registration number of the business operator issuing the qualified invoice. (2) The date of the transaction. (3) The details of the transaction (indicating that it is an item subject to a reduced tax rate). (4) The amount of consideration (excluding tax or including tax) and the applicable tax rate, totaled separately for each tax rate. (5) The consumption tax amount, etc., separated for each tax rate. (6) The name or title of the business operator receiving the delivery of the document. However, (6) may be allowed to be omitted.

[0065] The business operator issuing the qualified invoice in the above (1) is, for example, a management company. The business operator registration number is, for example, the business operator registration number of the management company. Note that the business operator issuing the qualified invoice may also be a system provider. The management support server 100 transmits the qualified invoice issued by the issuing department 507 to the intermediary company terminal 110.

[0066] When the issuing unit 507 issues a predetermined document, the transmitting unit 504 transmits a creation start notice indicating the start of a creation task to the management company terminal 120. Specifically, when the issuing unit 507 issues an eligible invoice, the transmitting unit 504 transmits a creation start notice to the management company terminal 120. When the issuing unit 507 issues a normal invoice, the transmitting unit 504 may not transmit a creation notice. In this case, on the condition that the payment of the issuing fee indicated by the invoice is completed, the transmitting unit 504 may transmit a creation start notice to the management company terminal 120.

[0067] As a result, the system provider can obtain the payment amount from the intermediary company and pay the sales amount to the management company, thus suppressing the situation where the payment amount cannot be recovered. From the perspective that the intermediary company can be regarded as having the intention to pay, even when a normal invoice is issued, the transmitting unit 504 may transmit a creation notice to the management company terminal 120.

[0068] (Chat function) In this embodiment, the intermediary company terminal 110 and the management company terminal 120 can exchange text messages with each other through a chat function. The chat function is displayed for each case (each sending request). As a result, chatting can be performed for each case. Therefore, various communications and adjustments can be easily performed for each case, improving the convenience of the management support system 1.

[0069] (An example of various databases included in the management support DB101) An example of various databases included in the management support DB101 will be described with reference to FIGS. 6 to 10. The management support DB101 includes, for example, a management company information DB600 (FIG. 6), a property information DB700 (FIG. 7), a request information DB800 (FIG. 8), an intermediary company information DB900 (FIG. 9), and a document data DB1000 (FIG. 10).

[0070] (An example of the management company information DB600) FIG. 6 is a diagram showing an example of the management company information DB600. The management company information DB600 includes items of "management company name", "company ID", "name of documents that can be sent", "name", "management authority", "address", "login ID", and "department". By inputting data into each item, the management company information is stored as a record in the management company information DB600.

[0071] The "management company name" indicates the name of the management company. The "company ID" indicates the identification information assigned to the management company. The "name of documents that can be sent" indicates one or more names of documents that can be sent. In the illustration, it shows that ○○ Real Estate can send four documents, and ○○ Location can send three documents. The "name" indicates the name of each staff member of the management company.

[0072] The "management authority" indicates the tasks that each staff member can be in charge of among a plurality of tasks. Multiple tasks that can be taken charge of may be registered. For example, in the illustration, Saburo Ikebukuro has multiple tasks (creation task and approval task) registered in the "management authority". Note that the "property management" shown in the illustration indicates having all authorities (for example, master registration). Specifically, for example, it shows that a staff member with the "property management" authority can perform registration and modification of the names of documents that can be sent, registration and modification of the person in charge, etc. in the management company. The "address" indicates the email address of each staff member. The "login ID" indicates the identification information for logging in to the website related to the management support system 1 or the management support application. The "department" indicates the department to which each staff member belongs. In the management company information DB600, for each name of the documents that can be sent, the fee (unit price of sales) obtained by sending each document is associated.

[0073] With such a management company information DB600, the management support system 1 can collectively manage the documents that can be sent by each management company and the information of the staff.

[0074] (An example of the property information DB700) Figure 7 is a diagram showing an example of the property information DB700. The property information DB700 includes items such as "management company name", "company ID", "property name", "location", "sales representative", and "document name that can be sent". When data is input into each item, the property information is stored as a record in the property information DB700. In the following, for items that overlap with the items already described, the description will be omitted as appropriate.

[0075] The "property name" indicates the unique name of the building property. The "property ID" indicates the identification information assigned to the property. The "location" indicates the location of the property. The "sales representative" indicates the name of the staff member in charge of the property. In the illustration, for the sake of convenience, the item of "document name that can be sent" is shown, but the "document name that can be sent" stored in the management company information DB600 (Figure 6) is directly applied (linked) to this item. Note that when there are multiple property information, the linking of the "document name that can be sent" to the property information can also be performed collectively.

[0076] With such a property information DB700, the management support system 1 can collectively manage the property information of each management company.

[0077] (An example of the request information DB800) Figure 8 is a diagram showing an example of the request information DB800. The request information DB800 is generated in response to the sending request indicated by the request notification. The request information DB800 includes items such as "request property name", "property ID", "request document name", "fee", "delivery date", and "task". When data is input into each item, the request information is stored as a record in the request information DB800. "Requested Property Name" indicates the name of the building property indicated by the delivery request. "Property ID" indicates the identification information assigned to the requested property. "Requested Document Name" indicates the name of the document that is the subject of the request. "Fee" indicates the unit price of the issuance fee that the brokerage company pays to the system provider for each document delivery. "Delivery Date" indicates the period required until each document can be downloaded. "Task" indicates the person in charge of each task in the workflow related to the preparation of the document.

[0078] With such a request information DB800, the management support system 1 can manage all the request information for each brokerage company collectively.

[0079] (Example of Brokerage Company Information DB900) Figure 9 is a diagram showing an example of the brokerage company information DB900. The brokerage company information DB900 includes items such as "Brokerage Company Name", "Company ID", "Name", "Address", "Login ID", "Property Name", "Requested Document", and "Payment Method". When data is input into each item, the brokerage company information is stored as a record in the brokerage company information DB900. "Brokerage Company Name" indicates the name of the brokerage company. "Company ID" indicates the identification information assigned to the brokerage company. "Name" indicates the name of the person in charge for each requested property. "Address" indicates the email address of each person in charge. "Property Name" indicates the name of the property that is the subject of the request. "Requested Document" indicates the name of the document that is the subject of the request. "Payment Method" indicates the payment method for the issuance fee paid from the brokerage company to the system provider. The payment method indicates, for example, either online payment (credit card) or invoice.

[0080] With such an intermediary company information DB900, the management support system 1 can manage documents requested by each intermediary company and information of the intermediary company's staff in a batch.

[0081] (Example of Document Data DB1000) FIG. 10 is a diagram showing an example of the document data DB1000. The document data DB1000 includes items of "property name", "property ID", "requested document name", "document data", "destination", and "status". When data is input into each item, the document data is stored as a record in the document data DB1000. "Document data" indicates the data itself of each document. "Document data" is created in a predetermined document file format. "Destination" indicates the intermediary company that is the destination of the document data. "Status" indicates the current status of the request. For example, if the created document is approved, the status switches to "sent". When the sending of the document data is completed, the "status" switches to the next task (for example, "completed" for online payment or "awaiting payment" for invoice payment). When the status switches to "completed", the intermediary company terminal 110 can download the document data.

[0082] With such a document data DB1000, the management support system 1 can manage the preparation stages in the workflow for each received document in a batch.

[0083] (Example of Various Processes Performed by Management Support System 1) Next, with reference to FIGS. 11 to 13, an example of various processes performed by the management support system 1 will be described.

[0084] (Example of Initial Registration Process) FIG. 11 is a sequence diagram showing an example of the initial registration process performed by the management support server 100 and the management company terminal 120. Step S1101: The management company terminal 120 receives master registration. In the master registration, the management company terminal 120 receives the input of management company information (each item in FIG. 6) from a staff member having a predetermined authority (property management), and transmits the received management company information to the management support server 100.

[0085] Step S1102: When the management support server 100 receives the management company information, it stores the management company information in the management company information DB600 (FIG. 6).

[0086] Step S1103: Next, the management company terminal 120 receives property registration. In the property registration, the management company terminal 120 receives the input of property information (each item in FIG. 7) from a staff member having a predetermined authority (property management), and transmits the received property information to the management support server 100. Note that the items to be received do not include the name of the document that can be transmitted. That is, in the property registration, the management company terminal 120 does not receive the input regarding the name of the document that can be transmitted. However, for a property having a property-specific name of the document that can be transmitted, which is different from the name of the document that can be transmitted registered in the management company, the name of the document that can be transmitted may be received in the input of the property information.

[0087] Step S1104: When the management support server 100 receives the property information, it stores the property information in the property information DB700 (FIG. 7). The management support server 100 associates the name of the document that can be transmitted stored in the management company information DB600 with the name of the document that can be transmitted in the property information DB700.

[0088] (An example of the request reception process for sending) FIG. 12 is a sequence diagram showing an example of the request reception process for sending performed by the management support server 100 and the agency company terminal 110. It is assumed that the registration of the agency company information (agency company information DB900) has been completed in the previous stage of the request reception process for sending.

[0089] Step S1201: The brokerage company terminal 110 receives property search conditions on a predetermined search screen. The search conditions are, for example, keyword search, area search, history search, etc. The brokerage company terminal 110 transmits the received search conditions to the management support server 100.

[0090] Step S1202: When the management support server 100 receives the search conditions from the brokerage company terminal 110, it searches for construction properties based on the search conditions. Step S1203: The management support server 100 transmits the search results to the brokerage company terminal 110.

[0091] Step S1204: The brokerage company terminal 110 displays a screen showing the search results. Step S1205: The brokerage company terminal 110 receives a request to send documents from the screen showing the search results.

[0092] Step S1206: The brokerage company terminal 110 receives one of the payment methods of online payment and invoice payment. Step S1207: The brokerage company terminal 110 transmits the request to send documents to the management support server 100. Step S1208: The management support server 100 receives the request to send documents from the brokerage company terminal 110. When receiving the request to send documents, it proceeds to the processing after step S1302 in Fig. 13A.

[0093] (An example of the preparation process of document data) Figs. 13A and 13B are sequence diagrams showing an example of the preparation process of document data performed by the management support server 100 and the management company terminal 120. Step S1301: The management support server 100 determines whether it has received a request to send documents from the brokerage company terminal 110. The management support server 100 waits until it receives the request to send documents (Step S1301: NO).

[0094] Step S1302: When the management support server 100 receives a document sending request (Step S1301: YES), it transmits a request notification indicating the document sending request to the management company terminal 120.

[0095] Step S1303: The management company terminal 120 determines whether it has received a request notification from the management support server 100. The management company terminal 120 waits until it receives the request notification (Step S1303: NO).

[0096] Step S1304: When the management company terminal 120 receives a request notification (Step S1303: YES), it accepts the decision result regarding whether to accept the request. Then, the management company terminal 120 determines whether the decision result indicates acceptance or rejection of acceptance. If the decision result indicates rejection of acceptance (Step S1304: NO), the management company terminal 120 ends the series of processes. In this case, the management company terminal 120 may notify the management company terminal 120 to indicate rejection of acceptance. Then, when the management support server 100 receives a notification indicating rejection of acceptance, it may end the series of processes.

[0097] Step S1305a: When the decision result indicates acceptance (Step S1304: YES), the management company terminal 120 transmits an acceptance notification to the management support server 100. Step S1305b: Then, the management company terminal 120 accepts the registration of request information. The received request information is transmitted to the management support server 100 and stored in the request information DB 800 (Figure 8).

[0098] Step S1306: The management support server 100 determines whether it has received an acceptance notification. If it has not received an acceptance notification (Step S1306), the management support server 100 ends the series of processes. Note that when the management support server 100 has not received an acceptance notification, it may end the series of processes by receiving a notification indicating rejection of acceptance.

[0099] Step S1307: The management support server 100 determines whether the issuance fee has been settled by online payment. If the issuance fee has not been settled by online payment (Step S1307: NO), that is, if invoice settlement is performed, the management support server 100 proceeds to Step S1309.

[0100] Step S1308: If online payment has been made (Step S1307: YES), the management support server 100 issues a qualified invoice. The issued qualified invoice is transmitted to the intermediary company terminal 110.

[0101] Step S1309: The management support server 100 transmits a creation start notice indicating the start of the creation task to the management company terminal 120. Step S1310: The management company terminal 120 determines whether it has received a creation start notice from the management support server 100. The management company terminal 120 waits until it receives the creation start notice (Step S1310: NO).

[0102] Step S1311: When the management company terminal 120 receives the creation start notice (Step S1310: YES), it displays, using an icon or the like, that the status of the creation task for this request information is in progress. Step S1312: The management company terminal 120 determines whether it has received notification that the task in the current status has been completed. The management company terminal 120 waits until it receives notification that the task has been completed (Step S1312: NO).

[0103] Step S1313: When the management company terminal 120 receives notification that the task has been completed (Step S1312: YES), it transmits a completion notice indicating that the task has been completed to the management support server 100.

[0104] Step S1314: The management support server 100 determines whether it has received a completion notice. The management support server 100 waits until it receives the completion notice (Step S1314: NO).

[0105] Step S1315: When the management support server 100 receives a completion notice (step S1314: YES), it sends a start notice indicating the start of the next task to the management company terminal 120. Note that when the management support server 100 receives a completion notice, it updates the status of 1000 in the document data DB to the next status. Also, when the creation task is completed, the document data of the document created by the person in charge of the creation task is sent from the management company terminal 120 and stored in the document data DB1000. The document data stored in the document data DB1000 can be viewed on the management company terminal 120 when the person in charge of the approval task downloads it in the approval task.

[0106] Step S1316: The management support server 100 determines whether the task indicated by the start notice is a sending task. If the task is not a sending task (step S1316: NO), the management support server 100 returns to step S1314. If the task is a sending task (step S1316: YES), the management support server 100 proceeds to step S1322.

[0107] Step S1317: The management company terminal 120 determines whether it has received a start notice for the next task. The management company terminal 120 waits until it receives a start notice for the next task (step S1317: NO). Step S1318: When the management company terminal 120 receives a start notice for the next task (step S1317: YES), it displays the status of the next task using an icon or the like.

[0108] Step S1319: It is determined whether the displayed task is a sending task. If the task is not a sending task (step S1319: NO), the management company terminal 120 returns to step S1312.

[0109] Step S1320: When the task is a sending task (Step S1319: YES), the management company terminal 120 determines whether it has received the document sending from the person in charge of the sending task. The management company terminal 120 waits until it receives the document sending (Step S1320: NO).

[0110] Step S1321: When the management company terminal 120 receives the document sending (Step S1320: YES), it transmits the document data to the management support server 100 and ends the series of processes.

[0111] Step S1322: The management support server 100 determines whether it has received the document data from the management company terminal 120. The management support server 100 waits until it receives the document data from the management company terminal 120 (Step S1322: NO).

[0112] Step S1323: When the management support server 100 receives the document data from the management company terminal 120 (Step S1322: YES), when it receives the document data from the management company terminal 120, it stores (updates) the received document data in the document data DB1000 (Fig. 10).

[0113] Step S1324: The management support server 100 transmits the document data stored in the document data DB1000 to the intermediary company terminal 110 in response to the transmission request from the intermediary company terminal 110 and ends the series of processes.

[0114] (An example of various screens in the management support system 1) Next, with reference to FIGS. 14 to 16, an example of various screens in the management support system 1 will be described.

[0115] (An example of a screen displayed on the management company terminal 120 in the registration of request information) FIG. 14 is a diagram showing an example of a screen displayed on the management company terminal 120 in registering the request information (FIG. 8). As shown in FIG. 14, a confirmation screen 1400 after the request information is input is displayed on the display 305 of the management company terminal 120. The input of the request information is performed by free text input or selection from a pull-down menu.

[0116] The confirmation screen 1400 includes a property summary column 1410, a sendable document column 1420, a person-in-charge setting column 1430, and a workflow setting column 1440. The property summary column 1410 includes the property name, location, property ID, etc. The sendable document column 1420 includes various document names and unit prices. The sendable document names shown in the sendable document column 1420 indicate the requested document names. The person-in-charge setting column 1430 indicates the sales staff in charge of this case. The workflow setting column 1440 indicates the staff in charge of various tasks in this case.

[0117] On the confirmation screen 1400, when the confirmation button 1450 is pressed, the registration of the request information is completed with the content shown on the confirmation screen 1400. On the other hand, when the back button 1460 is pressed, it returns to the input screen where various inputs to each column are possible. Thus, in this embodiment, request information is input and managed for each sending request.

[0118] (An example of the dashboard screen displayed on the management company terminal 120) FIG. 15 is a diagram showing an example of a dashboard screen displayed on the management company terminal 120. As shown in FIG. 15, a dashboard screen 1500 is displayed on the display 305 of the management company terminal 120. The dashboard screen 1500 is a screen that displays a list of each request information 1510 received for the request. Each request information 1510 includes a task display 1511, a request content 1512, a requester 1513, a payment method 1514, a scheduled delivery date 1515, and an unread chat notification 1516.

[0119] The task display 1511 is an icon indicating the current status. The following is an example of the notation of the task display 1511. "Assignee setting" indicating before acceptance. "Waiting for creation" indicating before starting document creation. "In progress" indicating after starting and before completing document creation. "Waiting for approval" indicating after completing and before approving document creation. "Approval in progress" indicating during approval. "Preparing for submission" indicating after approval and before sending. "Completed" indicating after sending and after payment is completed.

[0120] The request content 1512 indicates the property name and the document (request document) for which the sending request is made. The requester 1513 indicates the person in charge of the brokerage company. The settlement method 1514 indicates the character indicating whether the settlement has been completed and the total sales amount.

[0121] The scheduled delivery date 1515 indicates the scheduled delivery date of the request document and the number of days based on the scheduled delivery date. The unread notification 1516 shows an icon indicating unread when a chat message such as a question from the person in charge of the brokerage company regarding the case is received.

[0122] Also, when the display area of each request information 1510 is selected, a detailed screen of the selected request information 1510 is displayed. For example, on the detailed screen, it is possible to accept the completion of each task, view / enter / send chat messages, etc.

[0123] Also, the dashboard screen 1500 includes a status aggregation display 1520 and a screen switching button 1530. The status aggregation display 1520 shows the cumulative count of each current status. The screen switching button 1530 accepts screen switching. The screen switching button 1530 includes a dashboard button 1531, a request list button 1532, an order history button 1533, a billing content button 1534, and a settings button 1535.

[0124] The dashboard button 1531 accepts the transition to the dashboard screen 1500. The request list button 1532 accepts the transition to the list screen of the currently accepted cases. The order history button 1533 accepts the transition to the list screen of the order history. The billing details button 1534 accepts the transition to a screen showing, for example, the details of payments. The screen showing the details of payments is a screen showing payments for each predetermined unit such as a period unit or a property unit. The settings button 1535 accepts the transition to a screen where various settings can be changed.

[0125] With such a dashboard screen 1500, the staff of the management company can grasp the status of each case at a glance.

[0126] (An example of a screen related to the reception of a sending request displayed on the agency terminal 110) FIG. 16 is a diagram showing an example of a screen related to the reception of a sending request displayed on the agency terminal 110. FIG. 16(A) shows the top page 1610. The top page 1610 includes an input field 1611 and a request guide 1612. The input field 1611 is an area for accepting the input of a search keyword. The request guide 1612 shows the procedure for making a document sending request. When a keyword indicating search conditions is input into the input field 1611 and search results are received from the management support server 100, for example, a transition is made to the property details screen 1630 shown in FIG. 16(B).

[0127] FIG. 16(B) shows the property details screen 1630. The property details screen 1630 includes a property overview and a list of issuance fees for each document. When the request button 1631 is selected on the property details screen 1630, for example, a transition is made to a screen for accepting the details of the request document, and it is possible to complete the sending request on this screen.

[0128] (An example of a dashboard screen displayed on the agency terminal 110) FIG. 17 is a diagram showing an example of a dashboard screen displayed on the brokerage company terminal 110. In FIG. 17, a dashboard screen 1700 is displayed on the display 305 of the brokerage company terminal 110. The dashboard screen 1700 is a screen that lists each commissioned case 1710. Each case 1710 includes a task display 1711, a request content 1712, a request destination 1713, a settlement method 1714, a scheduled delivery date 1715, a person in charge of the request 1716, and an unread chat notification 1717.

[0129] The task display 1711 is an icon indicating the current task (status) on the management company terminal 120. As an example of the notation of the task display 1711, the following are listed. There are "request in progress" indicating before acceptance, "in preparation" indicating before sending, "completed" indicating after sending and payment completed, etc.

[0130] The request content 1712 indicates the property name and the request documents that are the target of the sending request. The request destination 1713 indicates the management company of the request destination. The settlement method 1714 indicates a character indicating whether the settlement has been completed and the issuance fee.

[0131] The scheduled delivery date 1715 indicates the scheduled delivery date of the request documents and the number of days based on the scheduled delivery date. The person in charge of the request indicates the name of the person in charge of the brokerage company that made the sending request. The unread notification 1717 displays an icon indicating unread when a chat message such as a question from the staff in charge of the management company is received for the case.

[0132] Also, when the display area of each case 1710 is selected, a detailed screen of the selected case 1710 is displayed. For example, on the detailed screen, it is possible to view / enter / send chat messages.

[0133] In addition, the dashboard screen 1700 includes a status aggregation display 1720 and a screen switching button 1730. The status aggregation display 1720 shows the cumulative count of each current status. The screen switching button 1730 accepts screen switching. The screen switching button 1730 includes a dashboard button 1731, a request list button 1732, an order history button 1733, and a billing management button 1734.

[0134] The dashboard button 1731 accepts the transition to the dashboard screen 1700. The request list button 1732 accepts the transition to the list screen of the currently requested cases. The order history button 1733 accepts the transition to the list screen of the order history. The billing management button 1734 accepts the transition to a screen showing, for example, the details of payments. The screen showing the details of payments is a screen showing payments for each predetermined unit such as a period unit or a property unit.

[0135] With such a dashboard screen 1700, the staff of the brokerage company can grasp the status of each case at a glance.

[0136] As described above, the management support server 100 according to the present embodiment presents the names of the documents that can be sent by each management company registered in advance to the brokerage company terminal 110, and when receiving a request for sending document data according to the document name received by the brokerage company terminal 110, it sends a request notification to the management company terminal 120. Then, the management support server 100 presents the document data obtained from the management company terminal 120 according to the request notification to the brokerage company terminal 110. Thereby, in the transaction of request documents, the brokerage company can make a request for sending request documents online. In addition, the management company can send document data addressed to the brokerage company online. Therefore, the transaction of request documents can be carried out quickly, accurately, and easily. Thus, the transaction of request documents can be carried out efficiently.

[0137] In addition, the management support server 100 according to the present embodiment registers by associating each building property managed by the management company with a document name, and presents the document name to the brokerage company terminal 110 for each building property. Further, the management support server 100 issues a request notice for documents to the management company for each building property. In transactions of requested documents, the requested documents often differ for each building property. Even in such cases, transactions of requested documents for each building property can be carried out quickly, accurately, and easily.

[0138] In addition, the management support server 100 according to the present embodiment registers the fee for each document name, presents the payment fee according to the requested document (the payment fee from the brokerage company terminal 110 to the management support server 100) to the brokerage company terminal 110, and enables online settlement of the payment fee. As a result, the brokerage company can reduce the trouble of bank transfers. In addition, the management company can reduce the trouble of confirming the receipt of funds. Also, mistakes related to bank transfers and receipt of funds can be suppressed.

[0139] In addition, the management support server 100 according to the present embodiment registers the person in charge for each task in the management company, and upon completion of each task, sends a start notice for the next task to the management company terminal 120. As a result, each task related to the preparation of the requested document can be managed by a workflow. Therefore, the management company can efficiently prepare the requested document.

[0140] In addition, the management support server 100 according to the present embodiment notifies the start of the creation task in response to the issuance of a predetermined document (for example, a qualified invoice) indicating the fee paid by the brokerage company terminal 110 for the sending request. As a result, on the condition that a contract is established between the brokerage company and the system provider, the management company can prepare for the sending of the requested document.

[0141] In addition, all or part of each function (input / output, storage, processing) in the management support system 1 described above may be realized in another device different from the device described as the execution entity of the function. Specifically, in the above description, the document name registration unit 501, the presentation unit 502, the reception unit 503, the transmission unit 504, the settlement unit 505, the authority registration unit 506, and the issuance unit 507 have been described as configurations provided in the management support server 100. However, all or part of these functional units may be provided in other computer devices. Specifically, for example, all or part of these functional units may be provided in the intermediary company terminal 110 or the management company terminal 120, or may be provided in other computer devices other than these. Also, the computer devices in which these functional units are provided may be multiple or may be one.

[0142] Note that although the embodiments have been described, the specific configuration is not limited to the above-described embodiments, and also includes designs and the like within the scope not departing from the gist of the present invention.

[0143] A program for realizing the functions of the devices and the like (for example, the management support server 100, the intermediary company terminal 110, the management company terminal 120) according to the embodiments shown above may be stored in a computer-readable storage medium, and the program stored in this storage medium may be read into a computer system and executed to perform processing. Here, the "computer system" may include an operating system (OS) or hardware such as peripheral devices. Also, the "computer-readable storage medium" refers to a writable non-volatile memory such as a USB (Universal Serial Bus) flash memory, an SSD (Solid State Drive), a flexible disk, a magneto-optical disk, a ROM (Read Only Memory), a flash memory, a portable medium such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system.

[0144] Furthermore, the "computer-readable storage medium" shall include those that hold a program for a certain period of time, such as volatile memories (e.g., DRAM (Dynamic Random Access Memory)) inside an information processing apparatus or a computer system serving as a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. Also, the above-mentioned program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication wire) such as a telephone line. Also, the above-mentioned program may be for realizing a part of the aforementioned functions. Furthermore, the above-mentioned program may be a so-called difference file (difference program) that can be realized in combination with a program already stored in the computer system for the aforementioned functions.

Explanation of Reference Numerals

[0145] 1... Management support system, 100... Management support server, 101... Management support DB, 110... Broker company terminal, 120... Management company terminal, 201... CPU, 202... Memory, 203... Communication I / F, 301... CPU, 302... Memory, 303... Communication I / F, 304... Input device, 305... Display, 306... Output device, 501... Document name registration section, 502... Presentation section, 503... Reception section, 504... Transmission section, 505... Settlement section, 506... Authority registration section, 507... Issuance section

Claims

1. A management support system including a management company terminal provided by a management company that manages construction properties, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of construction properties, and a management support device connected to the management company terminal and the brokerage company terminal, a document name registration unit that registers document names of documents that can be sent from the management company to the brokerage company for each management company, a presentation unit that presents the document names registered by the document name registration unit to the brokerage company terminal, a receiving unit that receives a request for sending document data corresponding to the document name received by the brokerage company terminal based on the document name presented by the presentation unit, a transmitting unit that, when the receiving unit receives the sending request, transmits a request notification indicating that fact to the management company terminal, comprising, the presentation unit presents the document data acquired from the management company terminal in response to the request notification to the brokerage company terminal, A management support system.

2. The document name registration unit registers by associating each construction property managed by the management company with the document name, the presentation unit presents the document name to the brokerage company terminal for each construction property, the transmitting unit transmits the request notification to the management company for each construction property, The management support system according to claim 1.

3. Comprising a settlement unit that performs settlement, the document name registration unit registers the fee for each document name, the presentation unit presents to the brokerage company terminal the payment fee corresponding to the sending request, which is the payment fee from the brokerage company terminal to the management support device, the settlement unit performs online settlement of the payment fee, The management support system according to claim 1 or 2.

4. The management company prepares the document data through a plurality of tasks including a receiving task for receiving the request notification, a creating task for creating the document data, an approving task for approving the created document data, and a sending task for sending the document data, and a permission registration unit that registers a person in charge for each of the plurality of tasks, comprising, the transmitting unit transmits a start notification for the next task to the management company terminal in response to the completion of each task, The management support system according to claim 1 or 2.

5. Comprising an issuing unit that issues a predetermined document indicating the fee paid by the brokerage company terminal for the sending request, the transmitting unit transmits a start notification for the creating task in response to the issuance of the predetermined document by the issuing unit, The management support system according to claim 4.

6. A computer of a management support system including a management company terminal provided by a management company that manages construction properties, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of construction properties, and a management support device connected to the management company terminal and the brokerage company terminal, A document name registration step of registering, for each management company, the document names of documents that can be sent from the management company to the brokerage company, A presentation step of presenting the document names registered in the document name registration step to the brokerage company terminal, A reception step of receiving a request for sending document data corresponding to the document names received by the brokerage company terminal based on the document names presented in the presentation step, A transmission step of transmitting a request notification indicating that fact to the management company terminal when the transmission request is received in the reception step, executes, In the presentation step, the document data acquired from the management company terminal in response to the request notification is presented to the brokerage company terminal. Management support method.

7. A computer of a management support system including a management company terminal provided by a management company that manages construction properties, a brokerage company terminal provided by a brokerage company that mediates real estate transactions of construction properties, and a management support device connected to the management company terminal and the brokerage company terminal, A document name registration unit that registers, for each management company, the document names of documents that can be sent from the management company to the brokerage company, A presentation unit that presents the document names registered by the document name registration unit to the brokerage company terminal, A reception unit that receives a request for sending document data corresponding to the document names received by the brokerage company terminal based on the document names presented by the presentation unit, A transmission unit that transmits a request notification indicating that fact to the management company terminal when the reception unit receives the transmission request, functions as, The presentation unit presents the document data acquired from the management company terminal in response to the request notification to the brokerage company terminal. Program.

Images