JP2024046461A - Real estate support system, real estate support method, and real estate support program - Google Patents

Abstract

[Problem] To streamline settlement procedures between real estate maintenance businesses and real estate management businesses by linking data on claims receivables and payment payables that arise between the two businesses.
[Solution] A real estate support system constructed with a maintenance system for supporting maintenance work for multiple properties and a management system for supporting management work for multiple properties, wherein the maintenance system outputs billing data including invoice number, billing destination, maintenance content, and billing amount, the management system imports the billing data as debt data and outputs payment data including invoice number, billing destination, and payment amount, the maintenance system imports the payment data and compares the billing amount of the billing data with the payment amount of the payment data on an invoice number basis, and if the amounts match, it settles the billing amount of the billing data.
[Selected Figure] Figure 1

Description

The present invention relates to a real estate support system, a real estate support method, and a real estate support program.

For example, in the building maintenance industry, both the condominium maintenance business and the condominium management association support business may be carried out by the same company or by a group of companies. For example, when condominium management operations are entrusted to the same company's maintenance business and condominium association support business, the condominium association support business pays the condominium association support business in response to the maintenance business claims made to the condominium association. Transactions may occur. Conventionally, as a system for supporting condominium management associations, there is, for example, Patent Document 1.

Japanese Patent Application Publication No. 2015-125452

However, the above-mentioned Patent Document 1 does not state anything about streamlining the settlement process between real estate maintenance businesses and real estate management businesses (e.g., condominium management association support businesses).

The present invention has been made in view of the above, and by linking the data of claim receivables and payment obligations generated between the real estate maintenance business and the real estate management business. The purpose of the present invention is to provide a real estate support system, a real estate support method, and a real estate support program that can streamline settlement operations.

In order to solve the above-mentioned problems and achieve the objectives, the present invention is constructed of a maintenance system for supporting maintenance operations for multiple properties, and a management system for supporting management operations for multiple properties. The maintenance system outputs billing data including a billing number, billing destination, maintenance content, and billing amount, and the management system imports the billing data as debt data and generates a bill. The maintenance system outputs payment data including a number, billing address, and payment amount, and the maintenance system imports the payment data, collates the billed amount in the billing data and the payment amount in the payment data for each bill number, and calculates the amount. If they match, the billing amount of the billing data is cleared.

According to one aspect of the present invention, the maintenance system may output an error list for billing data details with discrepant amounts.

Further, according to one aspect of the present invention, the billing data and the payment data may be imported by relaying a server between the maintenance system and the management system.

Further, according to one aspect of the present invention, the real estate is a condominium, the maintenance work of the maintenance system includes cleaning management work, building/equipment maintenance work, or security and disaster prevention work, and the management system is a condominium. You may decide to support the management of the management association's accounts and payments related to management expenses.

In order to solve the above-mentioned problems and achieve the objective, the present invention provides a real estate support method executed by a real estate support system constructed with a maintenance system for supporting maintenance work for multiple real estate properties and a management system for supporting management work for multiple real estate properties, the method comprising the steps of: the maintenance system outputting billing data including an invoice number, billing destination, maintenance content, and billing amount; the management system importing the billing data as debt data and outputting payment data including an invoice number, billing destination, and payment amount; and the maintenance system importing the payment data, comparing the billing amount of the billing data with the payment amount of the payment data on an invoice number basis, and, if the amounts match, clearing the billing amount of the billing data.

Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides a maintenance system for supporting maintenance operations for a plurality of properties, a management system for supporting management operations for a plurality of properties, A real estate support program to be executed by a real estate support system constructed with , a step of importing the billing data as debt data and outputting payment data including an invoice number, a billing party, and a payment amount; A real estate support program for causing a computer to execute a step of comparing the billed amount with the payment amount of the payment data and, if the amounts match, writing off the billed amount of the billing data. do.

According to the present invention, by linking data on claims and payables arising between real estate maintenance businesses and real estate management businesses, it is possible to streamline settlement operations between real estate maintenance businesses and real estate management businesses.

FIG. 1 is a diagram showing an example of the configuration of a real estate support system according to this embodiment. FIG. 2 is a block diagram showing an example of the configuration of the maintenance system of FIG. FIG. 3 is a diagram showing an example of the configuration of the billing destination master. FIG. 4 is a block diagram showing an example of the configuration of the management system shown in FIG. 1. As shown in FIG. FIG. 5 is a diagram for explaining an outline of the overall processing of the real estate support system in this embodiment. FIG. 6 is a diagram for explaining a specific example of processing of the real estate support system in this embodiment. FIG. 7 is a diagram for explaining a specific example of processing of the real estate support system in this embodiment. FIG. 8 is a diagram for explaining a specific example of processing of the real estate support system in this embodiment. FIG. 9 is a diagram for explaining a specific example of processing of the real estate support system in this embodiment. FIG. 10 is a diagram for explaining a specific example of the processing of the real estate support system in this embodiment. FIG. 11 is a diagram for explaining a specific example of the processing of the real estate support system in this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. overview]
For example, in the building maintenance industry, both the condominium maintenance business and the condominium management association support business may be carried out by the same company or by a group of companies. For example, when condominium management operations are contracted out to the same company's maintenance business and condominium association support business, the condominium association support business pays the condominium association support business in response to the maintenance business claims made to the condominium association. Transactions may occur.

The characteristics of this transaction are: (1) there is no fluctuation in the billing amount or payment date because the transaction is completed within the same company, and (2) the transaction volume can be large because it is conducted on a managed condominium unit basis. Conventionally, the billing process in the maintenance business, the payment process in the condominium management association support business, and the deposit and reconciliation process in the maintenance business had to be processed manually, which resulted in an enormous amount of time required for reconciling billing and payment and for reconciliation processing.

In this embodiment, by linking data between the billing receivables and payment obligations that occur between the real estate maintenance business and the real estate management support business (for example, condominium management association support business), the maintenance business and the management support business can be linked. Streamline payment operations.

More specifically, in this embodiment, a maintenance system that supports a real estate maintenance business passes billing data generated in the maintenance business, which is an in-house transaction, to a management system that supports the real estate management business. , saving you the trouble of manually registering payment data. In addition, payment data is sent from the management system to the maintenance system, making it possible to process payments against billing data all at once. This makes it possible to simplify tasks related to billing/payment reconciliation and reconciliation processing.

2. Configuration
An example of the configuration of a real estate support system 1 according to this embodiment will be described with reference to FIGS. 1 to 4. FIG.

(2-1. Example of real estate support system configuration)
An example of the configuration of a real estate support system 1 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration of the real estate support system 1 according to this embodiment. In Fig. 1, the real estate support system 1 is composed of a maintenance system 10, a management system 20, and a server 30, which are configured to be able to communicate data with each other via a network 40.

The maintenance system 10 is a system for supporting maintenance work for multiple real estate properties, such as apartment buildings. For example, the maintenance work includes cleaning management work, building and equipment maintenance work, and security and disaster prevention work.

The management system 20 is a system for supporting management work for a plurality of real estate properties such as condominiums. Management work includes, for example, support for accounting and income and expenditure management related to management fees of condominium management associations.

The server 30 is, for example, a data storage server for storing (relaying) information such as files and data. The maintenance system 10 and the management system 20 upload data to the server 30 and download data from the server 30.

The maintenance system 10 generates billing data including the invoice number, billing destination, maintenance content, and billing amount, and uploads it to the server 30. The management system 20 downloads the billing data from the server 30, imports the billing data as debt data, generates payment data including the invoice number, billing destination, and payment amount based on the debt data, and uploads it to the server 30. The maintenance system 10 downloads and imports the payment data from the server 30, compares the billing amount in the billing data with the payment amount in the payment data on an invoice number basis, and if the amounts match, settles the billing amount of the billing data.

In the following explanation, the maintenance system 10 supports condominium maintenance work (cleaning management work, building/equipment maintenance work, or security and disaster prevention work), and the management system 20 supports the payments and payments related to management expenses of the condominium management association. Although the real estate support system of the present invention will be described as an example of supporting management, the real estate support system of the present invention is not limited to this, and can also be applied to managing other real estate such as commercial buildings.

Note that billing data and payment data are exchanged between the maintenance system 10 and the management system 20 via the server 30 here, but the data may be exchanged directly without going through the server 30. .

(Example of configuration of maintenance system 10)
An example of the configuration of the maintenance system 10 in FIG. 1 will be described with reference to FIG. 2. FIG. 2 is a block diagram showing an example of the configuration of the maintenance system 10 of FIG. 1. As shown in FIG.

The maintenance system 10 is a commercially available desktop personal computer. Note that the maintenance system 10 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The maintenance system 10 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the maintenance system 10 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the maintenance system 10 to the network 40 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 40 has a function of connecting the maintenance system 10 to the management system 20 and the server 30 so that they can communicate with each other, and is, for example, an in-house LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108 . As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Note that hereinafter, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112. Furthermore, displaying information on the monitor 114 and having the user operate the input device 112 may be referred to as "user operation via the UI."

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a data file 106a, a billing destination master 106b, and the like. FIG. 3 is a diagram showing an example of the configuration of the billing destination master 106b.

As shown in FIG. 3, the billing master 106b can be configured as a table that associates and registers the customer code, billing name, and management association classification (e.g., 1: management association, 0: non-management association).

The data file 106a is a file for storing various data such as billing data (receivables data) and acquisition error data (error list). The billing data may include the debt number, the name of the billing party, the name of the work content (maintenance content), the billed amount (tax-included amount), the bill number, the scheduled payment date, and the amount to be written off.

Returning to FIG. 2, the control unit 102 is a CPU or the like that centrally controls the maintenance system 10. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and performs various information processing based on these stored programs. Execute.

The control unit 102 is configured to be able to access the data file 106a, the billing master 106b, and the like stored in the memory unit 106. Note that the data file 106a and the billing master 106b may be provided in another location (e.g., the server 200) as long as they are accessible by the control unit 102.

The control unit 102 conceptually comprises a billing data output unit 102a, a payment reconciliation processing unit 102b, and a screen display control unit 102c.

The billing data output unit 102a, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, references the billing destination master 106b, creates billing data including the invoice number, billing destination (billing destination code and/or billing destination name), maintenance details, and billing amount, and stores the data in the data file 106a. The billing data output unit 102a also uploads the created billing data to the server 30.

The payment reconciliation processing unit 102b downloads payment data from the server 30, stores it in the data file 106a, imports the payment data (deposit data), compares (matches) the receivable amount of the billing data with the payment amount of the payment data for each invoice number, and reconciles the billing amount of the billing data where the amounts match. The payment reconciliation processing unit 102b may also output an error list for details of billing data where the amounts do not match.

The screen display control unit 102c controls the display and input of various screens displayed on the monitor 114.

(2-3. Example of management system configuration)
An example of the configuration of the management system 20 in Fig. 1 will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the management system 20.

Management system 20 is a commercially available desktop personal computer. Note that the management system 20 is not limited to stationary information processing devices such as desktop personal computers, but also portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers. It may also be a processing device.

The management system 20 includes a control section 202, a communication interface section 204, a storage section 206, and an input/output interface section 208. Each unit included in the management system 20 is communicably connected via an arbitrary communication path.

The communication interface unit 204 communicatively connects the management system 20 to the network 40 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 204 has a function of communicating data with other devices via the communication line. Here, the network 40 has a function of connecting the management system 20 to the maintenance system 10 and the server 30 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 212 and an output device 214 are connected to the input/output interface section 208 . As the output device 214, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 212, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Note that, below, the output device 214 may be described as a monitor 214, and the input device 212 may be described as a keyboard 212 or a mouse 212. Further, displaying information on the monitor 214 and having the user operate the input device 212 may be referred to as "user operation via the UI."

The storage unit 206 stores various databases, tables, files, and the like. The storage unit 206 records computer programs that work with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 206, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, and the like can be used. The storage unit 206 includes a data file 206a, and the like.

The data file 206a is a file for storing various data such as payment data. The payment data may include the payment number, management association name, payment amount, bill number, and scheduled payment date.

The control unit 202 is a CPU or the like that performs overall control of the management system 20. The control unit 202 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

The control unit 202 is configured to be able to access data files 206a and the like stored in the storage unit 206. Note that the data file 206a may be provided in another location (for example, the server 30), as long as it can be accessed by the control unit 202.

The control unit 202 conceptually comprises a debt data import unit 202a, a payment processing unit 202b, and a screen display control unit 202c.

The debt data importing unit 202a downloads the billing data uploaded to the server 30, stores it in the data file 206a, and imports this billing data as debt data.

The payment processing unit 202b creates payment data including the invoice number, billing destination, and payment amount based on the imported debt data, and stores the data in the data file 206a. The payment processing unit 202b also uploads the created payment data to the server 30.

The screen display control unit 202c controls the display and input of various screens displayed on the monitor 214.

[3. Concrete example]
A specific example of processing in the real estate support system 1 according to the present embodiment will be described with reference to FIGS. 1 to 12. FIG. 5 is a diagram showing a flow for explaining an outline of the overall processing of the real estate support system 1.

(3-1. Overall processing)
With reference to FIG. 5, an overview of the overall processing of the real estate support system 1 will be explained. In FIG. 5, the billing data output unit 102a of the maintenance system 10 executes billing data output processing (step S1). Specifically, in the billing data output process, the billing data output unit 102a refers to the billing destination master 106b in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example. Billing data including the billing number, billing destination, maintenance details, and billing amount is created and stored in the data file 106a. Further, the billing data output unit 102a uploads the created billing data to the server 30. In this way, in the billing data output process, billing data for each condominium management association is output.

The debt data import unit 202a of the management system 20 executes debt data import processing (step S2). Specifically, in the debt data import process, the debt data import unit 202a downloads the billing data uploaded to the server 30, stores it in the data file 206a, and converts this billing data into debt data (payment schedule data). ).

The payment processing unit 202b of the management system 20 executes a payment confirmation process (step S3). Specifically, in the payment confirmation process, the payment processing unit 202b creates payment data including the invoice number, the billing customer, and the payment amount based on the imported debt data.

The payment processing unit 202b of the management system 20 executes payment data output processing (step S4). Specifically, in the payment data output process, the payment processing unit 202b stores the created payment data in the data file 206a, and also uploads the created payment data to the server 30.

The deposit reconciliation processing unit 102b of the maintenance system 10 executes a deposit data import process (step S5). Specifically, in the deposit data import process, the deposit reconciliation processing unit 102b downloads the payment data from the server 30, stores it in the data file 106a, and imports the payment data (deposit data).

The deposit reconciliation processing unit 102b of the maintenance system 10 executes deposit reconciliation processing (step S6). Specifically, in the deposit reconciliation process, the deposit reconciliation processing unit 102b compares the billed amount in the billing data with the payment amount in the payment data for each invoice number, and deletes the billed amount in the billing data that matches the amount. Include Further, the deposit reconciliation processing unit 102b may output an error list for details of billing data with inconsistent amounts.

(3-2. Sample data)
6 to 12 are diagrams showing sample data for explaining specific examples of processing of the real estate support system 1. A specific example of the processing of the real estate support system 1 will be described with reference to FIGS. 6 to 12.

(Billing data output processing: S1)
Details of billing data output processing will be explained with reference to FIG. 6. The billing data output unit 102a of the maintenance system 10 refers to the billing destination master 106b and outputs a bill to a creditor number and a business partner in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example. Billing data including the billing number, billing destination, maintenance details, and billing amount, which are the units for carrying out the process, is created and stored in the data file 106a, and the billing data (billing file) is uploaded to the server 30.

In the billing data output process, billing data for the condominium management association is output from the billing data output unit 102a of the maintenance system 10. Since there are cases where multiple claim numbers are combined into one bill, and cases where one claim number is treated as one bill, billing data like the one below is output, with a billing number inserted for each billing destination and work content. The only data that is output is data that is linked to the management system 20, i.e., only data with management association classification = 1 in the billing destination master 106b.

Figure 6 (A) shows an example of billing data. The billing data includes the following fields: claim number (number), billing destination name, work content (maintenance content) name, billing amount (amount including tax), invoice number, expected payment date, and amount to be applied. In the example shown in the figure, the first line has the claim number "SK001", billing destination name "A condominium management association", work content (maintenance content) name "management outsourcing fee", tax-inclusive amount (billing amount) "200,000", invoice number "S10001", expected payment date "2022/6/30", and amount to be applied "0", while the second line has the claim number "SK002", billing destination name "A condominium management association", work content (maintenance content) name "regular cleaning fee", billing amount "100,000", invoice number "S10001", expected payment date "2022/6/30", and amount to be applied "0".

FIG. 6(B) is a diagram showing an example of data of the billing destination master 106b. The billing destination master 106b includes items such as a customer code, a billing destination name, and a management association classification (for example, 1: management association, 0: other than management association). In the example shown in the figure, the first line is the customer code “A”, the billing customer name “A Condominium Management Association”, the management association classification “1”, and the second line is the customer code “B”, the billing customer The former name is ``B Apartment Management Association,'' and the management association classification is ``1.''

(Debt data import process: S2)
The debt data import process will be described in detail with reference to Fig. 7. The debt data import unit 202a of the management system 20 downloads the billing data (billing file) uploaded to the server 30, stores it in a data file 206a, and converts the billing data stored in the data file 206a into debt data (scheduled payment data) and imports it.

In FIG. 7, the correspondence between billing data and debt data is indicated by arrows. FIG. 7(A) shows an example of billing data, and shows billing data downloaded from the server 30 and stored in the data file 206b (same as FIG. 6(A)). FIG. 7B shows an example of debt data, and billing data stored in the data file 206a is converted into debt data and imported.

The debt data import process downloads billing data from server 30 and stores it in data file 206b, and also converts the billing data stored in data file 206b into debt data and imports it.

As shown in FIG. 7(B), the debt data includes the following items: debt number, billing party (management association name), work content name, payment amount (tax included amount), invoice number, and scheduled payment date. In the debt data, the claim number in the billing data is changed to the debt number, the scheduled payment date item is changed to the scheduled payment date, and the application amount item is deleted. In the example shown in the figure, the first line contains the debt number "SM001", the name of the management association "A Condominium Management Association", the name of the work content (maintenance content) "management commission fee", the amount "200,000", and the invoice. No. "S10001", scheduled payment date "2022/6/30", the second line is debt No. "SM002", management association name "A condominium management association", work content (maintenance content) name "regular cleaning fee", The amount is "100,000," the bill number is "S10001," and the scheduled payment date is "2022/6/30."

(Payment confirmation process: S3)
The payment settlement process will be described in detail with reference to Fig. 8. The payment processing unit 202b creates payment data including an invoice number, a billing customer, and a payment amount based on the acquired debt data.

Figure 8 (A) shows an example of debt data (similar to Figure 7 (B)), and Figure 8 (B) shows an example of payment data. In the payment confirmation process, payment data for the condominium management association is created based on the debt data. Since payments are made in bulk for each management association, payment data is compiled by tallying up the payment amount for each debt number on an invoice number (payment number) basis, that is, by management association and scheduled payment date. If payment is not made due to insufficient funds in the association, payment data is created with the payment amount set to 0 yen.

As shown in FIG. 8(B), the payment data includes the following items: payment number, billing party name (management association name), payment amount (tax-included amount), bill number, and scheduled payment date. In the example shown in the figure, the first line is payment number "SH001", management association name "A condominium management association", payment amount "300,000", bill number "S10001", and scheduled payment date "2022/6". /30'', the fourth line is the payment number ``SH004'', the management association name ``C Apartment Management Association'', the payment amount ``0'', the bill number ``S10004'', and the scheduled payment date ``2022/7/31''. ing.

(Payment data output process: S4)
The payment data output process will be described in detail with reference to Fig. 9. The payment processing unit 202b stores the created payment data in a data file 206a, and also uploads the created payment data (payment file) to the server 30.

(Deposit data import process: S5 and deposit reconciliation process: S6)
Details of the deposit data import process and the deposit reconciliation process will be described with reference to FIGS. 10 and 11. The deposit reconciliation processing unit 102b of the maintenance system 10 downloads payment data (payment file) from the server 30, stores it in the data file 106a, and imports the payment data (deposit data). Further, the payment reconciliation processing unit 102b compares the payment amount in the payment data with the billing amount in the billing data for each bill number, and if they match, erases the billing amount in the billing data.

FIG. 10(A) shows an example of billing data before receiving deposit data (payment data) (same as the billing data in FIG. 6(A)). FIG. 10B shows an example of payment data (deposit data) downloaded from the server 30 and stored in the data file 106a. FIG. 10(C) shows an example of billing data after importing the deposit data. In FIGS. 10(B) and 10(C), the correspondence between payment data and credit data is indicated by arrows.

The payment amount in the payment data and the invoice amount in the invoice data are compared by invoice number, and the payment settlement process is performed for items where the unsettled amounts match.

In Figures 10(B) and 10(C), for bill number "S10001", the payment amount in the payment data is "300,000", and the billed amount in the first line of the billing data is "200,000". ”, the billed amount on the second line is “100,000”, and since the total amounts match, the application amount is updated to “200,000” and “100,000”.

For invoice number "S10002", the payment amount in the payment data is "350,000", the invoice amount on the third line of the invoice data is "300,000", and the invoice amount on the fourth line is "50,000", and since the total amounts match, the application amount is updated to "300,000" and "50,000".

Regarding bill number "S10003", the payment amount in the payment data is "500,000" and the billed amount in the 5th line of the billing data is "500,000", so the total amounts match, Update the application amount to "500,000".

Regarding bill number "S10004", the payment amount in the payment data is "0" and the billed amount on the 6th line of the billing data is "500,000", so the total amount does not match, so it cannot be canceled. Do not update the amount.

The payment reconciliation processing unit 102b may display an error list on the monitor 114 for details of billing data with inconsistent amounts. FIG. 11(A) is a diagram showing an example of an error list. For details for which the billed amount does not match for each invoice number, identify the target from the error list and manually (according to the operator's operation) each time payment is confirmed to check the payment amount and amount in the payment data. It is now possible to modify the amount to be applied in billing data.

As described above, according to this embodiment, the real estate support system 1 is constructed with a maintenance system 10 for supporting maintenance work for multiple real estate, and a management system 20 for supporting management work for multiple real estate. The maintenance system 10 outputs billing data including an invoice number, billing destination, maintenance content, and billing amount. The management system 20 imports the billing data as debt data and outputs payment data including an invoice number, billing destination, and payment amount. The maintenance system 10 imports the payment data, compares the billing amount of the billing data with the payment amount of the payment data on an invoice number basis, and if the amounts match, clears the billing amount of the billing data. Therefore, by linking the data of billing receivables and payment debts that arise between the real estate maintenance business and the real estate management business, it is possible to streamline the settlement work between the real estate maintenance business and the management business.

[4. Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
This embodiment can contribute to improving business efficiency and promoting appropriate business decisions of companies, and thus can contribute to Goals 8 and 9 of the SDGs.

Furthermore, this embodiment can contribute to reducing waste loss and promoting paperless and electronic systems, making it possible to contribute to Goals 12, 13, and 15 of the SDGs.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[5. Other embodiments]
In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Further, regarding the real estate support system 1, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions provided in the real estate support system 1, especially each processing function performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware using wired logic. Note that the program is recorded on a non-temporary computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processing described in this embodiment. 1 mechanically read. That is, a storage unit such as a ROM or an HDD (Hard Disk Drive) stores a computer program that cooperates with an OS to give instructions to a CPU and perform various processes. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

This computer program may also be stored in an application program server connected to the real estate assistance system 1 via any network, and all or part of it may be downloaded as needed.

Further, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPR. OM (registration) Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVDs (Digital Versatile Discs), Blu-ray (registered trademark) Discs, etc. shall include any “portable physical medium”.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The real estate support system 1 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The real estate support system 1 may be realized by implementing software (including programs or data, etc.) that causes the information processing device to realize the processing described in this embodiment.

Furthermore, the specific form of dispersion/integration of devices is not limited to what is shown in the diagram, and all or part of them can be functionally or physically divided into arbitrary units according to various additions or additions of functions. It can be configured in a distributed/integrated manner. That is, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively.

1 Real estate support system 10 Maintenance system 20 Management system 30 Server 40 Network 102 Control unit 102a Billing data output unit 102b Payment reconciliation processing unit 102c Screen display control unit 104 Communication interface unit 106 Storage unit 106a Data file 106b Billing destination master 108 Input/output Interface section 112 Input device 114 Output device 202 Control section 202a Debt data import section 202b Payment processing section 202c Screen display control section 204 Communication interface section 206 Storage section 206a Data file 208 Input/output interface section 212 Input device 214 Output device

Claims (6)

A real estate support system constructed of a maintenance system for supporting maintenance work for multiple real estate properties and a management system for supporting management work for multiple real estate properties,
The maintenance system outputs billing data including an invoice number, billing address, maintenance details, and billing amount,
The management system captures the billing data as debt data and outputs payment data including the bill number, billing destination, and payment amount,
The maintenance system imports the payment data, collates the billed amount in the billing data and the payment amount in the payment data for each bill number, and if the amounts match, erases the billed amount in the billing data. A real estate support system that is characterized by: The real estate support system according to claim 1, characterized in that the maintenance system outputs an error list for billing data details with discrepancies in amounts. 2. The real estate support system according to claim 1, wherein the billing data and the payment data are exchanged between the maintenance system and the management system via a server. The real estate is an apartment building,
The maintenance work of the maintenance system includes cleaning management work, building and facility maintenance work, or security and disaster prevention work,
4. The real estate support system according to claim 1, wherein the management system supports receipt and expenditure management and income/expenditure management related to management fees of a condominium management association. A real estate support method executed by a real estate support system constructed with a maintenance system for supporting maintenance work for a plurality of real estates and a management system for supporting management work for a plurality of real estates, comprising:
a step of the maintenance system outputting billing data including a billing number, a billing destination, a maintenance content, and a billing amount;
a step in which the management system inputs the billing data as debt data and outputs payment data including an invoice number, a billing destination, and a payment amount;
the maintenance system imports the payment data, compares the billing amount of the billing data with the payment amount of the payment data on an invoice number basis, and, if the amounts match, cancels the billing amount of the billing data;
A real estate support method comprising: A real estate support program to be executed by a real estate support system constructed with a maintenance system for supporting maintenance work for a plurality of real estate properties and a management system for supporting management work for a plurality of real estate properties,
a step of the maintenance system outputting billing data including a billing number, a billing destination, a maintenance content, and a billing amount;
a step in which the management system inputs the billing data as debt data and outputs payment data including an invoice number, a billing destination, and a payment amount;
the maintenance system imports the payment data, compares the billing amount of the billing data with the payment amount of the payment data on an invoice number basis, and, if the amounts match, cancels the billing amount of the billing data;
A real estate assistance program for running the following on a computer.

Images