JP7614128B2 - Real estate management device, real estate management method, and real estate management program - Google Patents

Description

The present invention relates to a real estate management device, a real estate management method, and a real estate management program.

Patent Document 1 (JP Patent Publication 2002-109198) discloses a management efficiency improvement system. This management efficiency improvement system has a process for inputting performance data from balance sheets and profit and loss statements into a computer, a process for inputting performance data related to pension management, a process for inputting performance data related to real estate management, and a process for inputting management (profit) plans as data.

The system also includes a process for inputting capital investment plans, a process for estimating forecast (simulation) data in which a computer is used to calculate future balance sheets and profit and loss statements for each selected simulation in the case where a management (profit) plan is implemented based on the actual data, a process for storing and managing forecast data, and a process for outputting forecast data.

This allows you to incorporate pensions, real estate holdings, assets or liabilities of subsidiaries, etc. into the comparison tables and income statements to determine future management plans, and you can estimate future balance sheets and income statements for each type of pension or real estate management, as well as provide management support for the entire group of companies.

JP 2002-109198 A

Here, property management fees (PM fees) for real estate properties (tenants) are known to be one of the sources of revenue loss for real estate management companies. Except in cases where PM fees are recorded as a fixed amount, they are often calculated based on the amount of payment collected from tenants. For this reason, it has been difficult to calculate and record PM fees before the payment deadline, such as at the end of the month. Such delays in the calculation and recording of PM fees cause delays in monthly accounting procedures.

The present invention has been made in consideration of the above-mentioned problems, and aims to provide a real estate management device, a real estate management method, and a real estate management program that enable calculation and recording of real estate management fees before the payment due date.

In order to solve the above-mentioned problems and achieve the object, the real estate management device of the present invention has a provisional management fee data generation unit that generates provisional management fee data indicating provisional management fees for a real estate property before a specified payment due date based on the rent to be charged for the real estate property, a pre-payment journal data generation unit that generates provisional journal voucher data indicating revenue and negative transfer voucher data for after the payment due date corresponding to the provisional journal voucher data based on the generated provisional management fee data, a management fee data generation unit that generates management fee data corresponding to the rent for the real estate property that has been deposited after the payment due date, and a journal data generation unit that generates journal data for recording management fees based on the generated management fee data .

In addition, in order to solve the above-mentioned problems and achieve the object, the real estate management method of the present invention includes a provisional management fee data generation step in which a provisional management fee data generation unit generates provisional management fee data indicating a provisional management fee for a real estate property before a specified payment due date based on the rent to be charged for the real estate property; an advance journal entry data generation step in which an advance journal entry data generation unit generates provisional journal entry voucher data indicating revenue and negative transfer voucher data for after the payment due date corresponding to the provisional journal entry voucher data based on the generated provisional management fee data; a management fee data generation step in which the management fee data generation unit generates management fee data corresponding to the rent for the real estate property that has been deposited after the payment due date; and a journal entry data generation step in which a journal entry data generation unit generates journal entry data for recording the management fee based on the generated management fee data .

In addition, in order to solve the above-mentioned problems and achieve the objective, the real estate management program of the present invention is characterized by having a computer function as a provisional management fee data generation unit that generates provisional management fee data indicating a provisional management fee for a real estate property before a specified payment due date based on the rent to be charged for the real estate property, a pre-payment journal data generation unit that generates provisional journal voucher data indicating revenue and negative transfer voucher data for after the payment due date corresponding to the provisional journal voucher data based on the generated provisional management fee data, a management fee data generation unit that generates management fee data corresponding to the rent for the real estate property that has been deposited after the payment due date, and a journal data generation unit that generates journal data for recording management fees based on the generated management fee data .

The present invention makes it possible to calculate and record real estate management fees before the payment due date.

FIG. 1 is a block diagram showing a hardware configuration of a real estate management device according to an embodiment. FIG. 2 is a diagram showing an overview of the PM fee accounting process in the real estate management device according to the embodiment. FIG. 3 is a flowchart showing the flow of the operation for creating PM fee provisional billing detail data. FIG. 4 is a diagram showing an example of an owner remittance procurement data creation screen. FIG. 5 is a diagram showing PM fee provisional billing detail data and the like created on a billing basis. FIG. 6 is a flow chart showing the flow of operations for creating accounting data at the end of the month. FIG. 7 is a diagram showing an example of the accounting data creation screen. FIG. 8 is a diagram illustrating an example of provisional appropriation voucher data and transfer voucher data generated by the real estate management apparatus according to the embodiment. FIG. 9 is a flowchart showing the flow of the operation for creating deposit-based PM fee billing detail data. FIG. 10 is a diagram showing an example of an owner remittance procurement data creation screen. FIG. 11 is a diagram showing an example of PM fee billing detail data created on a payment basis. FIG. 12 is a flowchart showing the flow of the operation for creating the final PM fee accrual journal entry. FIG. 13 is a diagram showing an example of the accounting data creation screen. FIG. 14 is a diagram showing an example of the final appropriation voucher data.

Below, a real estate management device according to 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.

(Hardware configuration)
Fig. 1 is a block diagram showing a hardware configuration of a real estate management device 1 according to an embodiment. As shown in Fig. 1, the real estate management device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 may be a display unit such as a monitor device (including a home television). The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function.

The memory unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive). The memory unit 2 stores an expense item master 11, which is a storage area. The memory unit 2 also stores a real estate management program that enables calculation and recording of real estate management fees (PM fees) before the due date. The memory unit 2 also stores billing source detail data, PM fee provisional billing detail data, billing increase/decrease table data, provisional recording voucher data, transfer voucher data, PM fee billing detail data, recording data, etc., which are generated by executing the real estate management program.

(Functional configuration of real estate management device)
The control unit 3 executes the real estate management program stored in the memory unit 2, thereby functioning as an input processing unit 21, a data generation unit 22, a provisional management fee data generation unit 23, and an advance journal data generation unit 24. The control unit 3 also executes the real estate management program, thereby functioning as a management fee data generation unit 25, a journal data generation unit 26, a comparison unit 27, and a display control unit 28.

The input processing unit 21 performs input processing corresponding to input operations by business operators, etc., via an owner remittance procurement data creation screen or an accounting data creation screen, etc., which will be described later. The data generation unit 22 generates billing-based and deposit-based calculation source detail data including the expected payment date, billing amount, payment date, and paid amount for each tenant. The provisional management fee data generation unit 23 generates PM fee provisional billing detail data indicating the PM fee for each tenant, based on the calculation source detail data generated on a billing basis, before a specified payment due date, for example the end of the month.

The pre-due journal data generation unit 24 generates provisional accounting voucher data as journal data for the negative amount for provisional accounting based on the provisional PM fee billing detail data generated by the provisional management fee data generation unit 23, and also generates transfer voucher data for the next month that corresponds to this provisional accounting voucher data. The management fee data generation unit 25 generates PM fee billing detail data based on the deposit-based calculation source detail data after the deposit due date, for example on the first day of the month.

The journal data generation unit 26 generates accounting voucher data based on the PM fee billing detail data. The comparison unit 27 also compares the provisional PM fee for each real estate property for the current month with the PM fee for each real estate property billed in the previous month. The business operator determines whether there is an abnormality in the provisional PM fee based on the comparison result of the displayed PM fees. The display control unit 28 displays an owner remittance procurement data creation screen, an accounting data creation screen, etc. on the output device 7.

(Outline of PM fee accounting)
FIG. 2 is a diagram showing an overview of the PM fee accounting process in the real estate management device 1 of the embodiment. In the case of the real estate management device 1 of the embodiment, as shown in FIG. 2(a), in order to calculate provisional PM fees at the end of the month, billing source detail data is generated for all tenants, including unpaid amounts, including the scheduled payment date, billing amount, payment date, and paid amount. This billing source detail data indicates the rent (office rent) to be billed to each tenant. Based on this billing source detail data, PM fee provisional billing detail data is generated that indicates the PM fee for each tenant before the end of the month, which is the specified payment due date. In addition, the PM fee provisional billing detail data generated in the previous month is compared with the PM fee provisional billing detail data generated this time to check for the presence or absence of abnormal values.

Next, the real estate management device 1 of the embodiment creates provisional PM fee accounting entries and transfer entries at the beginning of the month based on the provisional PM fee billing detail data, as shown in FIG. 2(b).

Next, the real estate management device 1 of the embodiment calculates the final PM fees at the beginning of the following month when the payments from each tenant are finalized, as shown in FIG. 2(c), and creates an accounting entry for the final PM fees, as shown in FIG. 2(d).

(Details of PM fee accounting process)
The process for recording such PM fees will be described in detail below.

(PM fee provisional billing detail data creation operation)
First, the flow of the operation for creating PM fee provisional billing detail data is shown in the flowchart of Figure 3. When creating PM fee provisional billing detail data, the business operator performs a display operation of the owner remittance procurement data creation screen via the input device 6. When this display operation is detected, the display control unit 28 displays the owner remittance procurement data creation screen shown in Figure 4 on the output device 7 in step S1. This owner remittance procurement data creation screen includes an input field for the accumulation year and month, a selection field for calculation criteria, an input field for the calculation date, and an input field for the property code, etc.

The calculation basis selection field is a selection field for selecting whether the PM fee billing statement data will be based on past billings (scheduled billings) (billing-based) or on the payment results (payment-based). The example in Figure 4 shows an example in which "billing-based" has been selected. The calculation date input field is an input field for inputting the period for which the PM fee billing statement data is to be created, such as "October 1, 2021 to October 31, 2021". The property code input field is an input field for inputting the tenant (property) for which the PM fee billing statement data is to be created.

Next, in step S2, the provisional management fee data generation unit 23 determines whether or not "billing base" has been selected by referring to the selection state of the calculation basis selection field on the owner remittance procurement data creation screen. If "deposit base" has been selected, the processing of the flowchart in Figure 3 ends there. On the other hand, if "billing base" has been selected (step S2: Yes), the processing proceeds to step S3.

In step S3, the provisional management fee data generation unit 23 generates PM fee provisional billing detail data based on the billing source detail data. Specifically, prior to generating this PM fee provisional billing detail data, the data generation unit 22 generates billing source detail data indicating the office rent to be billed to each tenant, including unpaid amounts. As shown in FIG. 5(a), this billing source detail data is composed of billing destination information indicating a tenant-specific tenant code such as "T0001" and a tenant name such as "Tenant A", and property information indicating a property code such as "B0001" and a property name such as "A Building (A Building)".

The billing detail data also includes an expense code such as "H01" and expense information indicating office rent. The billing detail data also includes a scheduled payment date such as "October 31, 2021", a billed amount for office rent such as "10,000 yen", an actual payment date such as "October 31, 2021", and an amount already paid such as "10,000 yen".

Based on such billing source detail data, the provisional management fee data generation unit 23 generates the provisional PM fee billing detail data illustrated in FIG. 5(c), which is provisional detail data of the PM fees to be billed to the owners of each building. As shown in FIG. 5(c), this provisional PM fee billing detail data includes billing destination information including an owner code such as "O0001" and an owner name such as Owner A, and property information including a property code such as "B0001" and a property name such as "A Building". In addition, the provisional PM fee billing detail data includes expense item information including an expense item code such as "H11" and an expense item name such as "Property Management Fee: PM Fee", a posting date such as "October 31, 2021", and an amount such as "1,000 yen".

The expense item code and expense name are input by referring to the expense item master 11 illustrated in FIG. 5(b). That is, as shown in FIG. 5(b), the expense item master 11 stores, in association with each other, expense codes such as "H11", expense names such as "Property Management Fee: PM Fee", unpaid completed accounts such as "Accounts Receivable", sales account items such as "PM Fee Income", and PM fee categories such as "1: PM Fee". The provisional management fee data generation unit 23 inputs the expense item code and expense name of the provisional PM fee billing detail data by referring to this expense item master 11.

The "amount" of the PM fee provisional billing detail data shown in FIG. 5(c) is the amount of PM fee for each property. That is, in the example of FIG. 5(a), a real estate agent who owns the real estate management device 1 of the embodiment manages Tenant A and Tenant B of "Building A" with property code "B0001". For example, the rent for Tenant A and Tenant B is "10,000 yen" each, and 5% of this rent, or "500 yen", is to be billed to Owner A as a PM fee. Therefore, the "amount" of the PM fee provisional billing detail data is the sum of the PM fees for Tenant A and Tenant B (500 yen + 500 yen = 1,000 yen), which is input as the amount of PM fee to be billed to the owner of Building A for Tenant A and Tenant B.

Similarly, in the example of FIG. 5(a), a real estate agent who owns the real estate management device 1 of the embodiment manages Tenants E and F of "Building C" with property code "B0003". For example, the rent for Tenants E and F is "30,000 yen" each, and 5% of this rent, or "1,500 yen", is planned to be charged to Owner C as a PM fee. Therefore, the "amount" in the PM fee provisional billing detail data is the sum of the PM fees for Tenants E and F (1,500 yen + 1,500 yen = 3,000 yen), which is entered as the amount of PM fees to be charged to the owner of Building C for Tenants E and F.

Next, in step S4, the data generation unit 22 generates the billing increase/decrease table data shown in FIG. 5(d), which includes each item of the provisional PM fee billing detail data and the item of the previous month's PM fee billed to each tenant. The example in FIG. 5(d) is an example in which the owner A of Building A was billed "1000 yen", the owner B of Building B was billed "2000 yen", and the owner C of Building C was billed "1500 yen" as PM fees for the previous month. The example in FIG. 5(d) also shows that the owner A of Building A is scheduled to be billed "1000 yen", the owner B of Building B "2000 yen", and the owner C of Building C "1500 yen" for PM fees for the current month.

Next, in step S5, the comparison unit 27 compares, for each property, the provisional PM fee (= the PM fee included in the provisional PM fee billing detail data), which is the PM fee for the current month included in the billing increase/decrease table data, with the PM fee for the previous month, which is the PM fee deposited in the previous month (anomaly check process). In step S6, the data generation unit 22 inputs the comparison result as the "difference" between the previous month and the current month into the billing increase/decrease table data shown in FIG. 5(d) to reflect it.

The example of billing increase/decrease table data in FIG. 5(d) is an example in which the amount of the provisional PM fee for the current month for owner A of building A is "1000 yen" and the amount of the PM fee billed for the previous month was "1000 yen", so the comparison result by the comparison unit 27 is "0 yen", and the difference of "0 yen" is entered by the data generation unit 22 into the billing increase/decrease table data. Similarly, the example of billing increase/decrease table data in FIG. 5(d) is an example in which the amount of the provisional PM fee for the current month for owner B of building B is "2000 yen", and the amount of the PM fee billed for the previous month was "2000 yen", so the comparison result by the comparison unit 27 is "0 yen", and the difference of "0 yen" is entered by the data generation unit 22 into the billing increase/decrease table data.

Meanwhile, the provisional PM fee for the current month for Owner C of Building C is 3,000 yen, while the PM fee billed for the previous month was 1,500 yen. Therefore, the comparison result by the comparison unit 27 is 1,500 yen, and the difference of 1,500 yen is entered into the billing increase/decrease table data by the data generation unit 22. This billing increase/decrease table data is displayed on the output device 7 by the display control unit 28 when the business operator issues a display instruction operation. By looking at this difference, the business operator can determine whether there is an abnormality in the provisional PM fee amount calculated for the current month.

Here, the difference between the provisional PM fee for the current month for Owner C of Building C and the PM fee billed for the previous month, "1,500 yen," is assumed to be the difference due to the creation of a new contract in the current month. In this case, the business operator determines that there is "no problem" even though there is a difference of "1,500 yen." In this way, the business operator determines whether there is an abnormality in the provisional PM fee calculated for the current month based on the difference contained in the billing increase/decrease table data.

(Accounting data creation operation)
Next, the operation of creating accounting data at the end of the month, which creates a provisional PM fee posting entry and a transfer entry at the beginning of the month, will be described. The flow of the operation of creating accounting data at the end of the month is shown in the flowchart of Figure 6. When the business operator specifies the creation of accounting data, the display control unit 28 displays an accounting data creation screen on the output device 7 in step S11.

Figure 7 shows an example of an accounting data creation screen. As shown in Figure 7, the accounting data creation screen has a journal entry type selection field, a business code selection field, a date input field, etc. Of these, in the journal entry type selection field, either normal journal entry or provisional journal entry for PM fees can be selected. The flowchart in Figure 6 is an example of making a provisional journal entry for PM fees at the end of the month, so the business operator selects "provisional journal entry (PM fee)" in the journal entry type selection field.

In step S12, the provisional management fee data generation unit 23 determines whether or not "provisional journal entry (PM fee)" has been selected by referring to the journal entry type selection field on the accounting data creation screen. If "provisional journal entry (PM fee)" has not been selected (step S12: No), the processing of the flowchart in FIG. 3 ends.

If "provisional journal entry (PM fee)" is selected (step S12: Yes), the provisional management fee data generation unit 23 generates the PM fee provisional billing detail data shown in FIG. 8(a) in step S13. Note that the PM fee provisional billing detail data may use the PM fee provisional billing detail data generated when the above-mentioned "billing base" is selected (see FIG. 5(c)).

Next, in step S14, at the end of the month, the advance journal data generation unit 24 generates a provisional accounting voucher (black voucher) as shown in FIG. 8(b) based on the PM fee provisional billing detail data as shown in FIG. 8(a).

The provisional accounting voucher shown in FIG. 8(b) is composed of the voucher number, voucher date, debit amount, debit item, credit item, credit amount, property name, and business partner. The debit amount and credit amount are entered as the amounts for Owners A to C in the PM fee provisional billing detail data shown in FIG. 8(a). The credit item is "accounts receivable" and the credit item is "PM fee income."

Next, in step S15, on the "first day of the next month", the advance journal data generation unit 24 generates a transfer voucher (red voucher) for the negative amount, as shown in FIG. 8(c), which corresponds to the provisionally recorded voucher. The transfer voucher shown in FIG. 8(c) includes the voucher number, voucher date, debit amount, debit item, credit item, credit amount, property name, and business partner. The debit amount and credit amount are entered as negative amounts, such as "-1000 yen", corresponding to the provisionally recorded voucher shown in FIG. 8(b). Additionally, the credit item will be "accounts receivable" and the credit item will be "PM fee income".

The provisionally recorded voucher data and transfer voucher data generated in this manner are recorded in the accounting system of an accounting server device connected to the real estate management device 1 of the embodiment via a network, or are recorded in the accounting system stored in the memory unit 2 of the real estate management device 1 of the embodiment.

In this way, by calculating the PM fee, which is the management fee for managed properties, before the payment is made and assuming that payment will be made, management can grasp sales at an early stage, making it possible to quickly grasp the current situation and consider countermeasures. Also, from an on-site perspective, abnormal values in the results compared to the previous month can be detected at an early stage.

In addition, vouchers provisionally recorded at the end of the month can be automatically transferred at the beginning of the following month, minimizing the impact of errors.

(Final PM fee accounting process after payment is confirmed)
Next, in the following month, rent (e.g., office rent) is received from each tenant. For this reason, "deposit-based" billing details data is created. FIG. 9 is a flowchart showing the flow of the operation for creating the deposit-based billing details data for the following month. First, the business operator performs a display specification operation for the owner remittance procurement data creation screen described above. When this display specification operation is performed, in step S21, the display control unit 28 displays the owner remittance procurement data creation screen shown in FIG. 10 on the output device 7.

Next, the business operator selects "Deposit-based" in the calculation basis selection field on the owner remittance procurement data creation screen shown in FIG. 10. In step S22, the management fee data generation unit 25 determines whether the calculation basis "Deposit-based" has been selected. When the selection of "Deposit-based" is detected (step S22: Yes), the data generation unit 22 generates the billing statement data illustrated in FIG. 11(a) at the beginning of the following month based on the rent paid by each tenant in step S23. The example in FIG. 11(a) shows an example in which the lessee of Tenant A in Building A deposits "10,000 yen" as office rent on "October 31, 2021", and the lessee of Tenant B in Building A deposits "10,000 yen" as office rent on "November 1, 2021".

The example in Figure 11(a) shows an example in which the lessee of Tenant E in Building C paid office rent of 30,000 yen on October 31, 2021, and the invoiced amount for office rent to the lessee of Tenant F in Building C was 30,000 yen, but the amount was not paid at the beginning of the month.

Next, in step S23, the management fee data generation unit 25 generates PM fee billing detail data, which is detail data of the PM fees to be billed to the owner of each building, based on the billing source detail data. Specifically, as shown in FIG. 11(b), the management fee data generation unit 25 generates PM fee billing detail data for PM fees such as "1,000 yen," "2,500 yen," and "1,500 yen" to be billed to the owner of each building, with the expense item set to "H11: Property management fee" and the accounting date set to "November 1, 2021," which is the beginning of the month.

(Final PM fee journal entry creation process)
Next, Fig. 12 is a flowchart showing the flow of the operation for creating the final PM fee journal entry. When the "deposit-based" PM fee billing detail data is generated as described above, the business operator performs a display specification operation on the accounting data creation screen. When this display specification operation on the accounting data creation screen is detected, the display control unit 28 displays the accounting data creation screen shown in Fig. 13 on the output device 7 in step S31. The business operator selects the "normal" journal entry type in the "journal entry type" selection field on this accounting data creation screen.

The journal data generation unit 26 determines whether or not the "normal" journal type was selected in step S32. If the "normal" journal type is selected (step S32: Yes), the journal data generation unit 26 generates the recorded voucher data illustrated in FIG. 14(b) in step S33 based on the PM fee billing detail data illustrated in FIG. 14(a).

This accounting voucher data includes the voucher number, voucher date, debit amount, debit item, credit item, credit amount, property name, and business partner. The beginning of the month, "November 1, 2021," is entered as the voucher date. "Accounts receivable" is entered as the debit item, and "PM fee income" is entered as the credit item. In addition, the name of the owner of each building that is the business partner, such as "Owner A" or "Owner B," is entered as the business partner. The accounting voucher data generated in this manner is entered into the accounting system of the accounting server device connected via a network to the real estate management device 1 of the embodiment, or into the accounting system stored in the memory unit 2 of the real estate management device 1 of the embodiment.

(Effects of the embodiment)
As is clear from the above explanation, the real estate management device 1 of the embodiment can calculate the PM fee, which is the management fee for the managed property, before the deposit is made, assuming that the deposit will be made.

This allows management to grasp sales at an early stage, making it possible to grasp the current situation and quickly consider countermeasures. Also, from a field perspective, it allows for early detection of abnormal values in results compared to the previous month.

In addition, vouchers provisionally recorded at the end of the month can be automatically transferred at the beginning of the following month. This helps to minimize the impact of mistakes.

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

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs Goals 12, 13, and 15.

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

[Other embodiments]
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth 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.

Furthermore, with regard to the real estate management device 1, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the real estate management device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the real estate management device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to configure the control unit 3.

The real estate management program of the real estate management device 1 may also be stored in another server device connected to the real estate management device 1 via any network, and all or part of it may be downloaded as needed.

The real estate management program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

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 the real estate management device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

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

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

This invention is useful in the real estate management industry.

REFERENCE SIGNS LIST 1 Real estate management device 2 Memory unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 11 Expense item master 21 Input processing unit 22 Data generation unit 23 Provisional management fee data generation unit 24 Advance journal entry data generation unit 25 Management fee data generation unit 26 Journal entry data generation unit 27 Comparison unit 28 Display control unit

Claims (4)

a provisional management fee data generating unit for generating provisional management fee data indicating provisional management fees for the real estate property prior to a predetermined payment due date based on the rent to be charged for the real estate property;
a pre-due journal data generating unit that generates provisional journal voucher data indicating revenue and transfer voucher data for a negative amount for after the payment due date corresponding to the provisional journal voucher data based on the generated provisional management fee data;
a management fee data generating unit for generating management fee data corresponding to the rent of the real estate property that has been paid after the payment due date;
a journal data generation unit that generates journal data for recording the management fee based on the generated management fee data;
A real estate management device having the above configuration. A comparison unit that compares the provisional management fee for each real estate property indicated by the provisional management fee data with the management fee for each real estate property previously deposited;
A display control unit that displays a comparison result by the comparison unit.
2. The real estate management device according to claim 1 . a provisional management fee data generating step in which a provisional management fee data generating unit generates provisional management fee data indicating provisional management fees for the real estate property prior to a specified payment due date based on the rent to be charged for the real estate property;
a pre-due journal data generation step in which a pre-due journal data generation unit generates provisional journal voucher data indicating revenue and transfer voucher data for a negative amount for after the payment due date corresponding to the provisional journal voucher data based on the generated provisional management fee data;
a management fee data generating step of generating management fee data corresponding to the rent of the real estate property deposited by the management fee data generating unit after the deposit due date;
a journal data generation step in which a journal data generation unit generates journal data for recording the management fee based on the generated management fee data;
A real estate management method having the above. Computer,
a provisional management fee data generating unit for generating provisional management fee data indicating provisional management fees for the real estate property prior to a predetermined payment due date based on the rent to be charged for the real estate property;
a pre-due journal data generating unit that generates provisional journal voucher data indicating revenue and transfer voucher data for a negative amount for after the payment due date corresponding to the provisional journal voucher data based on the generated provisional management fee data ;
a management fee data generating unit for generating management fee data corresponding to the rent of the real estate property that has been paid after the payment due date;
a management fee data generating unit that generates management fee journal data based on the management fee data generated ;
A property management program featuring:

Images