JP7589124B2 - Asset management system, asset management method, and asset management program - Google Patents

Description

The present invention relates to an asset management system, an asset management method, and an asset management program.

For example, if a real estate owner entrusts tenant management, repair management, and complaint handling to a PM company, the PM company will manage billing payments to tenants and orders and payments to contractors on the owner's behalf, settle the results of payments and payments, and make payments (billing) to the owner. For example, Patent Document 1 shows a conventional PM company system.

JP 2019-160144 A

However, in the above-mentioned Patent Document 1, there is an issue that the owner cannot record accounting entries at the time when sales and payments occur.

The present invention has been made in consideration of the above, and aims to provide an asset management system, an asset management method, and an asset management program that enable an owner to record accounting entries at the time sales and payments occur when an asset management company manages properties owned by the owner.

In order to solve the above-mentioned problems and achieve the objective, the present invention provides an asset management system for an asset management company that manages properties owned by an owner, and that is equipped with a control unit and configured to be able to link with an owner-side system, the control unit being equipped with billing input means for inputting scheduled billing data for the target property, including billing destination, management item, billing amount, and accounting date, payment input means for inputting scheduled payment data for the target property, including payee, management item, payment amount, and accounting date, and correction data output means for outputting correction data including management item, accounting date, and amount based on the scheduled billing data and the scheduled payment data, and the owner-side system imports the correction data as transfer settlement data and creates a correction journal entry based on the imported transfer settlement data.

Furthermore, according to one aspect of the present invention, the correction data may include records in which the amount is a positive value and records in which the amount is a negative value.

According to one aspect of the present invention, the control unit is configured to be able to access an ownership ratio master that sets the ownership ratio of each owner for a property owned by multiple owners, and the correction data output means may be configured to output the correction data by apportioning the ownership ratio for the target owner based on the ownership ratio master, the scheduled billing data, and the scheduled payment data.

According to one aspect of the present invention, the owner-side system is configured to be able to access a management item master in which management items and account items are registered in association with each other, and may create corrective journal entries by referencing the management item master based on the transfer settlement data.

According to one aspect of the present invention, the owner system may create performance data based on the billing schedule data, the payment schedule data, and the transfer settlement data.

According to one aspect of the present invention, the asset management company may be a PM (Property Management) company.

In order to solve the above-mentioned problems and achieve the objective, the present invention provides an asset management method that is equipped with a control unit and configured to be able to link with an owner-side system, and is executed by an asset management system of an asset management company that manages properties owned by an owner, and includes a billing input process executed by the control unit for inputting scheduled billing data for the target property, including a billing destination, management items, billing amount, and accounting date; a payment input process for inputting scheduled payment data for the target property, including a payee, management items, payment amount, and accounting date; and a correction data output process for outputting correction data including management items, accounting date, and amount based on the scheduled billing data and the scheduled payment data, and the owner-side system imports the correction data as transfer settlement data, and creates a correction journal entry based on the imported transfer settlement data.

In order to solve the above-mentioned problems and achieve the objective, the present invention provides an asset management program that includes a control unit and is configured to be able to link with an owner's system, and is executed by an asset management system of an asset management company that manages properties owned by an owner. The control unit executes a billing input process for inputting scheduled billing data for the target property, including a billing destination, management items, billing amount, and accounting date; a payment input process for inputting scheduled payment data for the target property, including a payee, management items, payment amount, and accounting date; and a correction data output process for outputting correction data including management items, accounting date, and amount based on the scheduled billing data and the scheduled payment data. The owner's system imports the correction data as transfer settlement data, and creates a correction journal entry based on the imported transfer settlement data.

The present invention has the effect of enabling the owner to record accounting entries at the time sales and payments occur when an asset management company manages a property owned by an owner.

FIG. 1 is a diagram for explaining a conventional settlement scheme between a PM company and an owner company. FIG. 2 is a diagram for explaining the procedure for creating journal entries according to this embodiment. FIG. 3 is a block diagram showing an example of the configuration of the asset management system according to the present embodiment. FIG. 4 is a diagram showing an example of the configuration of the ownership ratio master. FIG. 5 is a diagram showing an example of the configuration of the management item master. FIG. 6 is a diagram showing a flow for explaining an outline of the overall processing of the asset management system and the owner side system in this embodiment. FIG. 7 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 8 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 9 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 10 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 11 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 12 is a diagram for explaining a specific example of the processing of the asset management system and the owner side system in this embodiment. FIG. 13 is a diagram for explaining a specific example of the processing of the asset management system and the owner side 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]
First, an overview of the present invention will be described with reference to FIG. 1 and FIG.

Figure 1 is a diagram for explaining the conventional settlement scheme of PM companies and owner companies. In many cases, owner companies entrust the management of properties they own to PM (Property Management) companies. In general, PM companies settle accounts with the owner company in the month following the deposits and withdrawals for the property. As a method of sharing information with the owner company, the settlement results are shared in the settlement month as a PM report. Since the settlement month is the month following the actual deposits and withdrawals with tenants and contractors, the owner company cannot record the actual occurrence timing, which causes a discrepancy. To be more specific, for example, in Figure 1, assume that a tenant used a conference room for the property in May and received a payment from the tenant in June. Also assume that the cost of the May inspection was paid to the contractor in June. The PM company settles accounts in July in the form of a PM report based on the deposits and withdrawals in June.

In this case, it would be desirable for the owner company to be able to recognize the costs of the May inspection and the revenue associated with the use of the conference room in May. However, the owner company processes the information in its own system based on the July settlement results, and the information is not registered until July.

As such, previously there was no system for PM companies to share information with the owner company, and the owner company could only record transaction data such as sales and payment data, meaning that it was not possible to record entries at the time of occurrence.

Therefore, in this embodiment, we have created a system that can share and import information from the PM company's system that can be accounted for in the owner's system at the time of occurrence, eliminating this discrepancy and allowing the owner to correctly recognize sales expenses at the time of occurrence and use this information to make accurate management decisions.

More specifically, the PM company's system generates correction data based on the expected payment data and expected payment data so that the owner's system can record sales and expenses based on the expected payment data and payment data. The owner's system then imports the correction data as transfer settlement data and creates corrective journal entries based on the transfer settlement data, allowing the owner to record journal entries at the time of occurrence.

Figure 2 is a diagram for explaining the flow of journal entries in this embodiment. That is, Figure 2 is a diagram for explaining the flow of journal entries that the owner wants to create. When May inspection/June payment - May usage/June deposit is settled in July, the flow of journal entries that the owner wants to create for May to July is as shown in Figure 2. In May, journal entries for "accounts receivable/sales" and "expenses/accounts payable" are created. In June, journal entries for "sales/accounts receivable" and "accounts payable/expenses" are created. These journal entries are corrective journal entries in this embodiment. In addition, in June, journal entries for "accounts receivable/sales" and "expenses/accounts payable" are created, and in July, journal entries for "deposit/accounts receivable" and "accounts payable/deposit" are created. These journal entries are final journal entries.

As the actual settlement timing for the May inspection and May usage entries has not been determined, a "corrective entry" is created as a reverse entry in the month following the month of recording. In order to achieve this, the data that is the basis for the corrective entry is not recognized as receivable/payable data, but rather as correction data (transfer settlement data) for creating the "corrective entry," and is linked from the PM company's system to the owner's system.

The July settlement will be determined based on the PM company's cash flow status as of the end of June. Rather than using the "corrective journal entries" mentioned above, the owner company can create receivables and payables information based on the PM company's cash flow information, making it possible to handle the July settlement. In this way, in this embodiment, corrective journal entries and final journal entries are generated on a planned basis, allowing the owner to use the management company's data to perform income and expenditure analysis on two axes: the accrual axis and the finalization axis.

The asset management system of this embodiment can be used in industries where asset management is outsourced to other companies, etc., and where there is a discrepancy between the timing of sales and expenses and the timing of deposits and payments, and is ideal for use by asset management companies such as PM companies, but the present invention is not limited to this and can also be applied to other types of asset management companies other than PM companies.

2. Configuration
An example of the configuration of the asset management system (PM company system) 100 according to this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the configuration of the asset management system 100 according to this embodiment.

As shown in FIG. 2, the asset management system 100 is a commercially available desktop personal computer. Note that the asset management system 100 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 asset management system 100 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 asset management system 100 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 asset management system 100 to the network 300 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 300 has a function of connecting the asset management system 100 to the server 200 and the owner-side system 400 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The asset management system 100 and the owner-side system 400 are configured to be able to cooperate with each other.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

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 commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 may 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 an ownership ratio master 106a, a management item master 106b, and a data file 106c. FIG. 4 is a diagram showing an example of the configuration of the ownership ratio master 106a. FIG. 5 is a diagram showing an example of the configuration of the management item master 106b.

The equity ratio master 106a is a master that sets the equity ratio of each owner for properties owned by multiple owners. For example, as shown in FIG. 4, the equity ratio master 106a can be configured as a table that associates and registers the property (e.g., property code and/or property name), equity ratio code, owner (e.g., owner business partner code and/or owner name), and equity ratio.

The management item master 106b is a master for setting the accounting format, and an account item is set for each management item. For example, as shown in FIG. 5, the management item master 106b can be configured as a table or the like in which management items, sales accounts, accounts receivable, purchase accounts, and accounts payable are associated and registered.

Data file 106c is a file for storing various data such as transaction data, such as billing schedule data, payment schedule data, deposit data, and deposit reconciliation data, as well as correction data.

The billing schedule data may include data such as billing number, item, billing destination, management item, accounting date, invoice issue date, expected payment date, billing amount, and ownership ratio code (see Figure 8).

The payment schedule data may include data on the payment number, property, payee, management item, accounting date, scheduled payment date, payment amount, and ownership ratio code (see Figure 9).

The correction data may include data on provisional settlement number, transfer correction category, property, counterparty, management item, recording date, and amount (see Figure 10).

The control unit 102 is a CPU or the like that performs overall control of the asset management system 100. 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 executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes a billing processing unit 102a, a payment processing unit 102b, a correction data output unit 102c, a deposit processing unit 102d, a screen display control unit 102e, and a master maintenance unit 102f.

The billing processing unit 102a inputs planned billing data for the target property, including the billing destination, management item, billing amount, and accounting date, in response to, for example, the operator's operations on the billing input screen (see Figure 8) displayed on the monitor 114, and registers this in the data file 106c.

The payment processing unit 102b inputs payment schedule data for the target property, including the payee, management item, payment amount, and accounting date, in response to, for example, the operator's operations on the billing input screen (see FIG. 9) displayed on the monitor 114, and registers the data in the data file 106c.

The correction data output unit 102c creates correction data including management items, accounting dates, and amounts for the target owner based on the planned billing data and planned payment data in response to, for example, the operator's operation on the correction data output screen for the owner company (see FIG. 10) displayed on the monitor 114, and registers the data in the data file 106c and outputs the data to the owner-side system 400 of the target owner. The correction data output unit 102c may also perform proportional allocation based on the ownership ratio for the target owner based on the ownership ratio master 106a, the planned billing data, and the planned payment data, and output the correction data. The correction data may include records in which the amount is a positive value and records in which the amount is a negative value.

When a payment is made for the scheduled billing data, the payment processing unit 102d inputs the payment data and payment reconciliation data in response to, for example, the operator's operations on the payment/reconciliation screen (not shown) displayed on the monitor 114, and registers the data in the data file 106c.

The screen display control unit 102e controls the display and input of various screens (e.g., contract input screen, sales input screen, billing input screen, etc.) displayed on the monitor 114.

The master maintenance unit 102f performs settings such as inputting, adding, deleting, and changing data in the equity ratio master 106a and the management item master 106b in response to, for example, the operator's operations on a master maintenance screen (not shown) displayed on the monitor 114.

The owner-side system 400 is, for example, a system of an owner company. The owner-side system 400 includes a control unit, a memory unit, an input device, an output device, a communication interface unit, an input/output interface unit, etc., and is configured to be capable of data communication with the asset management system 100 via the network 300, and is configured to be able to access the management item master 106b and data file 106c of the asset management system 100. The basic functions of the control unit, memory unit, input device, output device, communication interface unit, and input/output interface unit are similar to those of the asset management system 100 described above. The control unit of the owner-side system 400 includes, functionally and conceptually, a data import unit 401, a performance data aggregation unit 402, and an accounting data creation unit 403.

The data import unit 401, for example, converts the format of a correction data file specified by an operator on the transfer settlement data import screen (see FIG. 11) into transfer settlement data and imports it.

The actual data aggregation unit 402 creates actual data for the aggregation month and year specified by the operator on the actual data aggregation screen (see FIG. 12), for example, based on the billing schedule data, payment schedule data, and imported transfer settlement data of the asset management system 100.

The accounting data creation unit 403 creates accounting data (journal entries) for a voucher date specified by an operator on the accounting data creation screen (see FIG. 13), for a specified linked event, by referencing the asset management system 100's management item master 106b based on the asset management system 100's billing schedule data, payment schedule data, deposit data, deposit reconciliation data, and imported transfer settlement data. When "transfer" is selected as the linked event, the accounting data creation unit 403 creates a correction journal entry (transfer journal entry) by referencing the management item master 106b based on the imported transfer settlement data.

3. Specific Examples
Specific examples of the processing of the asset management system 100 and the owner-side system 400 in this embodiment will be described with reference to Figures 3 to 13. First, an overview of the overall processing of the asset management system 100 and the owner-side system 400 in this embodiment will be described with reference to Figure 6. Figure 6 is a diagram showing a flow for explaining an overview of the overall processing of the asset management system 100 and the owner-side system 400 in this embodiment.

In FIG. 6, the master maintenance unit 102f of the asset management system 100 executes ownership ratio registration (step S1) and registers data in the ownership ratio master 106a, for example, in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

The billing processing unit 102a of the asset management system 100 executes billing input (step S2), and, for example, in response to the operator's operations on the billing input screen (see FIG. 8) displayed on the monitor 114, inputs planned billing data for the target property, including the billing destination, management item, billing amount, and accounting date, and registers the data in the data file 106c.

The payment processing unit 102b of the asset management system 100 executes payment input (step S3), and, for example, in response to an operator's operation on the billing input screen (see FIG. 9) displayed on the monitor 114, inputs payment schedule data for the target property, including the payee, management item, payment amount, and accounting date, and registers the data in the data file 106c.

The correction data output unit 102c of the asset management system 100 executes correction data output for the owner company (step S4), creates correction data including management items, accounting dates, and amounts for the target owner based on the planned billing data and planned payment data, registers the data in the data file 106c, and outputs the correction data to the owner-side system 400 of the target owner. The correction data output unit 102c may also perform proportional allocation by ownership ratio for the target owner based on the ownership ratio master 106a, planned billing data, and planned payment data, and output the correction data. The correction data may include records in which the amount is a positive value and records in which the amount is a negative value.

The data import unit 401 of the owner system 400 executes the import of transfer settlement data (step T1), and imports, for example, a file of correction data specified by the operator on the transfer settlement data import screen, by changing the format of the file into transfer settlement data.

The actual data aggregation unit 402 of the owner system 400 executes actual data aggregation (step T2) and creates actual data for, for example, the aggregation month and year specified by the operator on the actual data aggregation screen, based on the billing schedule data, payment schedule data, and imported transfer settlement data of the asset management system 100.

The accounting data creation unit 403 creates a correction journal entry (transfer journal entry) for the invoice date specified by the operator on the accounting data creation screen, based on the imported transfer settlement data, and by referencing the management item master 106b.

Next, a specific example of the processing of the asset management system 100 and the owner-side system 400 in this embodiment will be described with reference to Figures 7 to 13. Figures 7 to 13 are diagrams for explaining a specific example of the processing of the asset management system 100 and the owner-side system 400 in this embodiment.

(S1: Ownership ratio registration)
7 is a diagram for explaining the ownership ratio registration (S1). The master maintenance unit 102f of the asset management system 100 sets data in the ownership ratio master 106a in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114. In the ownership ratio registration (S1), the owner's ownership ratio for each property is set in the ownership ratio master 106a.

The owner's settlement ratio for each transaction is determined by the equity ratio master 106a. In the case of owner-owned properties, the equity ratio master 106a transfers the tenant rent to the owner. In cases where there are multiple owners, the owner's equity is declared at the time of invoicing the tenant, and is apportioned at the time of transfer. The following describes an example of outputting correction data for the owner company in the case of joint ownership of the Kyobashi Building.

In the example of the equity ratio master 106a shown in FIG. 7, the first line has the property code "PJ0001", property name "Kyobashi Building", equity ratio code "1", owner client code "A0001", owner name "Owner Company", and equity ratio "20%". The second line has the property code "PJ0001", property name "Kyobashi Building", equity ratio code "1", owner client code "A0002", owner name "Ginza Real Estate", and equity ratio "35%". The third line has the property code "PJ0001", property name "Kyobashi Building", equity ratio code "1", owner client code "A0003", owner name "Shinbashi Asset Management", and equity ratio "45%".

(S2: Invoice input)
8 is a diagram for explaining the billing input (S2) in detail. The billing processing unit 102a of the asset management system 100 inputs billing schedule data including billing destination, management item, billing amount, and recording date for the target property in response to, for example, an operator's operation on the billing input screen displayed on the monitor 114, and registers the data in the data file 106c.

8A is a diagram showing an example of a billing input screen. The billing input screen has a header area for specifying the property (property code, property name), invoice issue date, billing destination, and expected payment date,
It is equipped with a details area for specifying the management item, posting date, billing amount, and ownership ratio code, and a register button (not shown). When data is entered into the header area and details area and the register button is pressed, scheduled billing data corresponding to the entered data is registered in the data file 106c. When data as shown in Fig. 8 (A) is entered and the register button is pressed, scheduled billing data as shown in Fig. 8 (B) is registered.

Figure 8 (B) shows an example of scheduled billing data. In the example of scheduled billing data shown in Figure 8 (B), the first line contains the billing number "1", property "PJ0001: Kyobashi Building", billing destination "SEI001: □△ Industry", management item "C001: Conference room usage fee", accounting date "2021/05/31", invoice issue date "2021/06/01", expected payment date "2021/06/25", billing amount "1,500,000", Ownership ratio "1", the second line is invoice number "1", property "PJ0001: Kyobashi Building", invoice destination "SEI001: □△ Industry", management item "C002: Hall usage fee", recording date "2021/05/31", invoice issue date "2021/06/01", expected payment date "2021/06/25", invoice amount "600,000", ownership ratio "1".

(S3: Payment input)
9 is a diagram for explaining the payment input (S3) in detail. The payment processing unit 102b of the asset management system 100 inputs payment schedule data including the payee, management item, payment amount, and accounting date for the target property in response to, for example, an operator's operation on the bill input screen displayed on the monitor 114, and registers the data in the data file 106c.

Figure 9 (A) is a diagram showing an example of the sales input screen. The sales input screen has a header area for specifying the property, payee, and scheduled payment date, a details area for specifying the management item, accounting date, payment amount, and ownership ratio code, and a register button (not shown). When data is entered into the header area and details area and the register button is pressed, scheduled payment data corresponding to the entered data is registered in data file 106c. When data as shown in Figure 9 (A) is entered and the register button is pressed, scheduled payment data as shown in Figure 9 (B) is registered.

Figure 9 (B) shows an example of payment schedule data. In the example of payment schedule data shown in Figure 9 (B), the first line is payment number "1", property "PJ0001: Kyobashi Building", payee "SHI001: XX security", management item "S001: daily security fee", accounting date "2021/05/31", scheduled payment date "2021/06/25", payment amount "900,000", and ownership ratio code "1". The second line is payment number "1", property "PJ0001: Kyobashi Building", payee "SHI001: XX security", management item "S002: temporary security fee", accounting date "2021/05/31", scheduled payment date "2021/06/25", payment amount "200,000", and ownership ratio code "1".

(S4: Output of correction data for the owner company)
FIG. 10 is a diagram for explaining the correction data output for the owner company (S4) in detail. The correction data output unit 102c of the asset management system 100 performs proportional allocation by the ownership ratio based on the ownership ratio master 106a, the billing schedule data, and the payment schedule data, using the period of the accounting date specified by the operator on the correction data output designation screen for the owner company as a search condition for the target owner company, creates correction data including the management item, the accounting date, and the amount, registers it in the data file 106c, and outputs it to the owner side system 400 of the target owner company, and stores it, for example, in a predetermined storage location (for example, C: ¥Users ¥manager ¥Desktop ¥Correction data import.xlsx) of the owner side system 400 of the owner company. Here, the correction data is stored in the owner side system 400, but the owner side system 400 may import it from the asset management system 100.

In this way, the asset management system 100 issues an output instruction. The target is the billing schedule data and payment schedule data for which the owner company's ownership ratio is included. Pro rata division is performed according to the ownership ratio, and correction data is created and output in a format that can be imported by the owner company as transfer settlement data.

Figure 10 (A) shows an example of the display of the correction data output screen for the owner company. The example of the correction data output screen for the owner company includes a field for specifying the period of accounting dates, and an output button for instructing the output of correction data. When the period of accounting dates is specified and the output button is pressed, correction data for the period of the specified accounting dates is created and output. In the example shown in Figure 10 (A), accounting dates "2021/05/01-2021/5/31" are specified, and when the output button is pressed, correction data such as that shown in Figure 10 (B) is output.

Figure 10 (A) is a diagram showing an example of correction data. The first line has provisional settlement number "1", transfer correction category "Correction", property "PJ0001: Kyobashi Building", counterparty "SEI001: □△ Industry", management item "C001: Conference room usage fee", recording date "2021/05/31", and amount "300,000". The amount "300,000 (positive value)" is calculated by multiplying the invoice amount "1,500,000" by the equity ratio of the property "Kyobashi Building" and the owner "Owner Company" in the equity ratio master 106a by "20%" = "300,000".

The second line has provisional settlement number "1", transfer adjustment category "Adjustment", property "PJ0001: Kyobashi Building", counterparty "SEI001: □△ Industry", management item "C002: Hall usage fee", recording date "2021/05/31", and amount "120,000 (positive value)". The amount "120,000" is calculated by multiplying the invoice amount "600,000" by the equity ratio of the property "Kyobashi Building" and the owner "Owner Company" in the equity ratio master 106a, "20%", = "120,000".

The third line has provisional settlement number "1", transfer adjustment category "adjustment", property "PJ0001: Kyobashi Building", counterparty "SHI001: XX security", management item "S001: Daily security expenses", recording date "2021/05/31", and amount "180,000 (positive value)". The amount "180,000" is calculated by multiplying the payment amount "900,000" by the equity ratio of the property "Kyobashi Building" and the owner "Owner Company" in the equity ratio master 106a, "20%", = "180,000".

The fourth line has provisional settlement number "1", transfer adjustment category "adjustment", property "PJ0001: Kyobashi Building", counterparty "SHI001: XX security", management item "S002: Temporary security costs", recording date "2021/05/31", and amount "40,000 (positive value)". The amount "40,000" is calculated by multiplying the payment amount "200,000" by the equity ratio of the property "Kyobashi Building" and the owner "Owner Company" in the equity ratio master 106a, which is "20%", = "40,000".

Lines 5 to 8 show red ink details for lines 1 to 4, with the posting date set to "2021/06/01" and the amount set to a negative value.

As described below, the owner's system 400 creates journal entries for accounts receivable/sales and expenses/payable for May based on the transfer settlement data corresponding to the correction data, and creates journal entries for sales/accounts receivable and accounts payable/expenses in June that are transfer entries of these journal entries.

(T1: Import transfer settlement data)
FIG. 11 is a diagram for explaining the transfer settlement data import in detail. The data import unit 401 of the owner system 400 converts the format of the correction data file specified by the operator on the transfer settlement data import screen into transfer settlement data and imports it. In this way, the owner system 400 issues an import instruction for the transfer settlement data. The import format conforms to the format output in the correction data output for the owner company. The resulting imported data is not regarded as credit/debt data but as "transfer settlement data" that simply creates a correction journal entry.

Figure 11 (A) shows an example of the transfer settlement data import screen. The transfer settlement data import screen has a field for specifying an import file and an import button for instructing the import of transfer settlement data. In the example shown in Figure 11 (A), when the import file "C:\Users\manager\Desktop\CorrectionDataImport.xlsx" is specified and the import button is pressed, the transfer settlement data shown in Figure 11 (B) is imported.

Figure 11 (B) is a diagram showing an example of transfer settlement data. Transfer settlement data may include the property, counterparty, management item, accounting date, invoice issue date, expected payment date, amount, and transfer settlement FLG. The transfer settlement FLG is set to "1" for correction data with a transfer correction category of "correction." For transfer correction categories of "other," it is set to "0." The transfer settlement FLG being "1" serves as a marker that the data is not positioned as receivable/payable data, but rather is for creating a correction journal entry.

In the example of transfer settlement data shown in FIG. 11(B), the transfer settlement data shown in FIG. 10(B) is rearranged in the order of counterparty and recording date.

(T2: Performance data collection)
12 is a diagram for explaining the details of the actual data collection. The actual data collection section 402 of the owner side system 400 creates actual data for the collection month and year specified by the operator on the actual data collection screen, based on the billing schedule data, payment schedule data, and imported transfer settlement data of the asset management system 100.

Figure 12 (A) is a diagram showing an example of the display of the actual data aggregation screen. The actual data aggregation screen has a field for specifying the aggregation month and year, and a tally button. When the aggregation month and year are specified and the tally button is pressed, actual data is created for the aggregation month and year based on the billing schedule data, payment schedule data, and imported transfer settlement data of the asset management system 100. In the example shown in Figure 12 (A), when the aggregation month and year "2021/05/01-2021/05/31" are specified and the tally button is pressed, the aggregated data shown in Figure 12 (C) is created.

Figure 12 (B) shows the data to be aggregated to create the performance data. A distinctive feature of this embodiment is that transfer settlement data is the data to be aggregated.

Figure 12 (C) is a diagram showing an example of actual performance data. Actual performance data may include the property, management item, collection date, amount, and source. The source "Billing" is collected based on billing schedule data. The source "Payment" is collected based on payment schedule data.

(T3: Creating accounting data)
13 is a diagram for explaining the accounting data creation (T3) in detail. The accounting data creation unit 403 of the owner side system 400 creates accounting data (journalization) for the voucher date and the specified linked event specified by the operator on the accounting data creation screen, by referring to the management item master 106b of the asset management system 100, based on the billing schedule data, payment schedule data, deposit data, deposit reconciliation data, and imported transfer settlement data of the asset management system 100.

Figure 13 (A) is a diagram showing an example of the accounting data creation screen. The accounting data creation screen has a field for specifying the invoice date, boxes for selecting linked events (sales, deposit, deposit clearing, purchase, payment, transfer), and a Create button (not shown). When the invoice date and linked event are specified and the Create button is pressed, accounting data (journal entry) for the specified linked event (sales, deposit, deposit clearing, purchase, payment, transfer) is created for the specified invoice date, based on the data that is the subject of the specified linked event, with reference to the management item master 106b.

Figure 13 (B) is a diagram showing an example of data in the management item master 106b. In the management item master 106b, an account item is set for each management item, and the management item is used as a key to obtain the account item and create a journal entry.

In FIG. 13(B) showing an example of the management item master 106b, the first line is the management item "C001: conference room usage fee", sales account "conference room income", and unpaid account "accounts receivable", the second line is the management item "C002: hall usage fee", sales account "hall income", and unpaid account "accounts receivable", the third line is the management item "S001: routine security costs", purchase account "routine security costs", and unpaid account "accounts payable", and the fourth line is the management item "S002: special security costs", purchase account "special security costs", and unpaid account "accounts payable".

In the example shown in FIG. 13(A), when the invoice date "2021/05/01-2021/05/31" and the linkage event "Transfer" are specified and the Create button is pressed, the management item master 106b shown in FIG. 13(B) is referenced based on the imported transfer settlement data, and the transfer journal entry shown in FIG. 13(C) is created.

Figure 13 (C) is a diagram showing an example of transfer journal entry data. The transfer journal entry data includes the voucher number, voucher date, debit account, debit amount, purchase account, and credit amount. With regard to income, the first line has the voucher number "1", voucher date "2021/05/31", debit account "accounts payable", debit amount "300,000", credit account "conference room income", credit amount "300,000", and the fifth line has the voucher number "1", voucher date "2021/06/01", debit account "conference room income", debit amount "300,000", credit account "accounts receivable", and credit amount "300,000".

Regarding the payment, the third line has the document number "1", the document date "2021/05/31", the debit account "Routine security expenses", the debit amount "180,000", the credit account "Accounts payable", the credit amount "180,000", and the seventh line has the document number "1", the document date "2021/06/01", the debit account "Accounts receivable", the debit amount "180,000", the credit account "Routine security expenses", the credit amount "180,000".

As described above, according to this embodiment, the asset management system 100 includes a billing processing unit 102a that inputs scheduled billing data for the target property, including the billing destination, management item, billing amount, and accounting date, a payment processing unit 102b that inputs scheduled payment data for the target property, including the payee, management item, payment amount, and accounting date, and a correction data output unit 102c that outputs correction data including the management item, accounting date, and amount based on the scheduled billing data and the scheduled payment data. The owner's system 400 imports the correction data as transfer settlement data and creates corrective journal entries based on the imported transfer settlement data. Therefore, when an asset management company manages properties owned by an owner, the owner can make journal entries at the time of sales and payments.

[4. 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.

5. 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 asset management system 100, 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 asset management system 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU 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 asset management system 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in the storage unit 106, such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to configure the control unit 102.

This computer program may also be stored in an application program server connected to the asset management system 100 via any network, and may be downloaded in whole or in part as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a DVD (registered trademark) or 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 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 106 are storage devices such as memory devices such as RAM and ROM, 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 website provision.

The asset management system 100 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 asset management system 100 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 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.

100 Asset management system 102 Control unit 102a Billing processing unit 102b Payment processing unit 102c Correction data output unit 102d Deposit processing unit 102e Screen display control unit 102f Master maintenance unit 104 Communication interface unit 106 Storage unit 106a Ownership ratio master 106b Management item master 106c Data file 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network 400 Owner's system 401 Data import unit 402 Performance data compilation unit 403 Accounting data creation unit

Claims (8)

An asset management system of an asset management company that manages properties owned by an owner, the asset management system including a control unit and configured to be able to cooperate with an owner-side system,
The control unit is
a billing input means for inputting billing schedule data including a billing destination, management item, billing amount, and accounting date for the target property;
a payment input means for inputting payment schedule data including a payee, a management item, a payment amount, and a recording date for the target property;
a correction data output means for outputting correction data including a management item, a recording date, and an amount based on the billing schedule data and the payment schedule data;
Equipped with
The asset management system is characterized in that the owner's system imports the correction data as transfer settlement data and creates a correction journal entry based on the imported transfer settlement data. The asset management system according to claim 1, characterized in that the correction data includes records in which the amount is a positive value and records in which the amount is a negative value. The control unit is
The system is structured to provide access to an ownership ratio master that sets the ownership ratio of each owner for properties owned by multiple owners,
The asset management system described in claim 1 or 2, characterized in that the correction data output means, for the target owner, performs pro rata allocation based on the ownership ratio master, the billing schedule data, and the payment schedule data, and outputs the correction data. The owner side system includes:
An asset management system as described in any one of claims 1 to 3, characterized in that it is configured to be able to access a management item master in which management items and account items are registered in association with each other, and that it creates the corrective journal entry by referring to the management item master based on the transfer settlement data. An asset management system according to any one of claims 1 to 4, characterized in that the owner-side system creates performance data based on the billing schedule data, the payment schedule data, and the transfer settlement data. The asset management system according to any one of claims 1 to 5, characterized in that the asset management company includes a PM (Property Management) company. An asset management method executed by an asset management system of an asset management company that manages properties owned by an owner, the asset management method comprising:
Executed by the control unit,
a billing input process for inputting billing schedule data including billing destination, management item, billing amount, and accounting date for the target property;
A payment input process for inputting payment schedule data including a payee, a management item, a payment amount, and a recording date for the target property;
a correction data output step of outputting correction data including a management item, a recording date, and an amount based on the billing schedule data and the payment schedule data;
Including,
The asset management method is characterized in that the owner's system imports the correction data as transfer settlement data and creates a correction journal entry based on the imported transfer settlement data. An asset management program for executing an asset management system of an asset management company that manages properties owned by an owner, the asset management program including a control unit and configured to be able to cooperate with an owner-side system, the asset management program comprising:
In the control unit,
a billing input process for inputting billing schedule data including billing destination, management item, billing amount, and accounting date for the target property;
A payment input process for inputting payment schedule data including a payee, a management item, a payment amount, and a recording date for the target property;
a correction data output step of outputting correction data including a management item, a recording date, and an amount based on the billing schedule data and the payment schedule data;
The purpose of this is to carry out
The asset management program is characterized in that the owner's system imports the correction data as transfer settlement data and creates a correction journal entry based on the imported transfer settlement data.

Images