Asset management system, asset management method, and asset management program

Abstract

To provide an asset management system, an asset management method, and an asset management program capable of performing journal entry at the time of occurrence of sales and payment at an owner side when an asset management company performs management of property owned by an owner.SOLUTION: An asset management system includes: billing input means for inputting billing schedule data including a billing destination, management items, a billing amount, and an accounting date about target property; payment input means for inputting payment schedule data including a payment destination, management items, a payment amount, and an accounting date about the target property; and correction data output means for outputting correction data including management items, an accounting date and an amount based on the billing schedule data and the payment schedule data. The owner side system captures the correction data as transfer settlement data and creates a correction journal based on the captured transfer adjustment data.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an asset management system, an asset management method, and an asset management program. [Background technology]

[0002] For example, when a real estate owner entrusts tenant management, repair management, and complaint handling to a PM company, the PM company performs billing and payment management for tenants and order and payment management for contractors on behalf of the owner, settles the results of payments and makes payments (billing) to the owner. Conventional PM company systems include, for example, those described in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-160144 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above-mentioned Patent Document 1, there is a problem that the owner cannot make accounting entries at the time when sales and payments occur.

[0005] 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 property owned by the owner. [Means for solving the problem]

[0006] 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 owners, which is equipped with a control unit and is configured to be able to cooperate with an owner-side system, and which comprises: a billing input means for inputting scheduled billing data for the target property, including a billing destination, management items, billing amount, and accounting date; a payment input means for inputting scheduled payment data for the target property, including a payee, management items, payment amount, and accounting date; and a correction data output means for outputting correction data including the 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.

[0007] According to another 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.

[0008] In addition, 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 apportion the ownership ratio for the target owner based on the ownership ratio master, the scheduled billing data, and the scheduled payment data, and output the correction data.

[0009] In addition, 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 referring to the management item master based on the transfer settlement data.

[0010] According to another 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.

[0011] According to another aspect of the present invention, the asset management company may be a property management (PM) company.

[0012] In addition, 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 cooperate 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, the method including: 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 executed by the control unit, 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 that outputs correction data including the management items, accounting date, and amount based on the scheduled billing data and the scheduled payment data, and is characterized in that 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.

[0013] In addition, in order to solve the above-mentioned problems and achieve the objective, the present invention provides an asset management program that has a control unit and is configured to be able to cooperate with an owner's system, and is to be executed in an asset management system of an asset management company that manages properties owned by an owner, wherein the control unit executes a billing input process for inputting scheduled billing data for the target property, including a billing destination, management item, billing amount, and accounting date; a payment input process for inputting scheduled payment data for the target property, including a payee, management item, payment amount, and accounting date; and a correction data output process for outputting correction data including the management item, accounting date, and amount based on the scheduled billing data and the scheduled payment data, and wherein 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. Effect of the Invention

[0014] According to the present invention, when an asset management company manages a property owned by an owner, the owner can record accounting entries at the time when sales and payments occur. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram for explaining a conventional settlement scheme between a PM company and an owner company. [Diagram 2] FIG. 2 is a diagram for explaining the procedure for creating journal entries according to this embodiment. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of the asset management system according to the present embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of the ownership ratio master. [Diagram 5] FIG. 5 is a diagram illustrating an example of the configuration of the management item master. [Figure 6] FIG. 6 is a diagram showing an outline of the overall processing of the asset management system and the owner side system in this embodiment. [Figure 7] 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. [Figure 8] 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. [Figure 9] 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. [Figure 10] 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. [Figure 11] 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. [Figure 12] 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. [Figure 13] 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.

[0017] [1. Overview] First, an overview of the present invention will be described with reference to FIGS.

[0018] 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 their 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, for the property, a tenant used a conference room in May and received 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 in July in the form of a PM report based on the deposits and withdrawals in June.

[0019] In this case, it would be desirable for the owner company to be able to recognize the cost of the May inspection and the sales from the use of the conference room in May. However, the owner company will process the information in its own system based on the July settlement results, and the information will not be registered until July.

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

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

[0022] 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 this correction data as transfer settlement data and creates corrective entries based on the transfer settlement data, allowing the owner to record entries at the time of occurrence.

[0023] FIG. 2 is a diagram for explaining the flow of journal entries in this embodiment. That is, FIG. 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 are settled in July, the flow of journal entries that the owner wants to create for May to July is as shown in FIG. 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.

[0024] For the journal entries relating to the May inspection and May usage, because the actual settlement timing has not been determined, a "corrective journal entry" will be created in the month following the month in which it was recorded, which is a reversal journal entry. In order to achieve this, the data that is the basis for the corrective journal entry will not be recognized as receivable / payable data, but will be recognized as correction data (transfer settlement data) for creating the "corrective journal entry", and will be linked from the PM company's system to the owner's system.

[0025] The July settlement will be determined based on the PM company's cash flow status as of the end of June. Instead of the "corrective journal entries" mentioned above, the owner company can create receivables and payables information based on the PM company's cash flow information, which will allow the July settlement to be handled. In this way, in this embodiment, the owner can use the management company's data to perform income and expenditure analysis on two axes, the accrual axis and the confirmation axis, by generating corrective journal entries and confirmation journal entries on a planned basis.

[0026] The asset management system of this embodiment can be used in industries where the management of assets is entrusted to other companies, etc., and there is a discrepancy between the timing of sales and expenses being generated and the timing of deposits and payments being made, 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.

[0027] [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.

[0028] 2, the asset management system 100 is a commercially available desktop personal computer. 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, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0029] The asset management system 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the asset management system 100 are communicatively connected via any communication path.

[0030] 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.

[0031] 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 cooperates with a mouse to realize 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.

[0032] The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106. 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.

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

[0034] The management item master 106b is a master for setting the format of journal entries, and an account item is set for each management item. 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, as shown in Fig. 5, for example.

[0035] The 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, and correction data.

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

[0037] The payment schedule data may include data such as payment number, property, payee, management item, accounting date, scheduled payment date, payment amount, and ownership ratio code (see FIG. 9).

[0038] The correction data may include data on provisional settlement number, transfer correction category, property, counterparty, management item, accounting date, and amount (see FIG. 10).

[0039] 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.

[0040] The billing processing unit 102a inputs scheduled 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 it in the data file 106c.

[0041] 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, an operator's operation on the billing input screen (see Figure 9) displayed on the monitor 114, and registers the data in the data file 106c.

[0042] For example, in response to an operator's operation on a correction data output screen for the owner company (see FIG. 10) displayed on the monitor 114, the correction data output unit 102c creates correction data including management items, accounting dates, and amounts for the target owner based on the billing schedule data and payment schedule 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 division by ownership ratio for the target owner based on the ownership ratio master 106a, billing schedule data, and payment schedule 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.

[0043] When a payment is made for billing scheduled data, the payment processing unit 102d inputs the payment data and payment clearing data in accordance with, for example, an operator's operation on a payment / clearance screen (not shown) displayed on the monitor 114, and registers the data in the data file 106c.

[0044] The screen display control unit 102e controls the display of various screens (eg, a contract input screen, a sales input screen, a billing input screen, etc.) displayed on the monitor 114 and the input therefor.

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

[0046] The owner's system 400 is, for example, a system of an owner company. The owner's system 400 includes a control unit, a storage 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 the data file 106c of the asset management system 100. The basic functions of the control unit, storage unit, input device, output device, communication interface unit, and input / output interface unit are similar to those of the above-mentioned asset management system 100. The control unit of the owner's system 400 conceptually includes a data import unit 401, an actual data aggregation unit 402, and an accounting data creation unit 403.

[0047] The data import unit 401 imports, for example, a file of correction data designated by an operator on a transfer settlement data import screen (see FIG. 11) by changing the format into transfer settlement data.

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

[0049] 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 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. When "transfer" is selected as the linked event, the accounting data creation unit 403 creates corrective journal entries (transfer journal entries) by referencing the management item master 106b, based on the imported transfer settlement data.

[0050] [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 Fig. 3 to Fig. 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 Fig. 6. Fig. 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.

[0051] 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.

[0052] The billing processing unit 102a of the asset management system 100 executes billing input (step S2) and, for example, in response to an operator's operation on the billing input screen (see FIG. 8) displayed on the monitor 114, inputs scheduled 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.

[0053] 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 Figure 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 it in the data file 106c.

[0054] 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 billing schedule data and payment schedule 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 perform proportional allocation by ownership ratio for the target owner based on the ownership ratio master 106a, billing schedule data, and payment schedule 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.

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

[0056] The actual data aggregation unit 402 of the owner system 400 executes actual data aggregation (step T2) and creates actual data, for example, for 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.

[0057] The accounting data creation unit 403 creates a corrective 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, with reference to the management item master 106b (step T3).

[0058] 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 Fig. 7 to Fig. 13. Fig. 7 to Fig. 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.

[0059] (S1: Ownership 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.

[0060] The owner's settlement ratio for each transaction is determined by the equity ratio master 106a. In the case of a property owned by an owner, the equity ratio master 106a remits the tenant rent to the owner. In cases where multiple owners own the property, the owner's equity is declared at the time of invoicing the tenant, and the amount is apportioned at the time of remittance. The following describes an example of outputting correction data for the owner company in the case of joint ownership of the Kyobashi Building.

[0061] In the example of the equity ratio master 106a shown in Figure 7, the first line has the property code "PJ0001", property name "Kyobashi Building", equity ratio code "1", owner customer 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 customer 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 customer code "A0003", owner name "Shinbashi Asset Management", and equity ratio "45%".

[0062] (S2: Billing entry) 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 accounting 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.

[0063] 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, accounting date, billing amount, and ownership ratio code, and a registration button (not shown). When data is entered into the header area and details area and the registration 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 registration button is pressed, scheduled billing data as shown in Fig. 8(B) is registered.

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

[0065] (S3: Payment entry) 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.

[0066] Fig. 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 the data file 106c. When data as shown in Fig. 9(A) is entered and the register button is pressed, scheduled payment data as shown in Fig. 9(B) is registered.

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

[0068] (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, billing schedule data, and payment schedule data, using the period of the accounting date specified by the operator on the correction data output specification screen for the owner company as a search condition for the target owner company, creates correction data including the management item, accounting date, and amount, registers it in the data file 106c, and also 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.

[0069] In this way, output instructions are given on the asset management system 100 side. The target is data of scheduled billing data and scheduled payment data, which includes the owner company in the ownership ratio. Pro rata division is performed according to the ownership ratio, and correction data is created and output in a format that can be imported as transfer settlement data by the owner company side.

[0070] FIG. 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 FIG. 10(A), the accounting dates "2021 / 05 / 01~2021 / 5 / 31" are specified, and when the output button is pressed, correction data such as that shown in FIG. 10(B) is output.

[0071] FIG. 10(A) is a diagram showing an example of correction data. The first line shows 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".

[0072] The second line has the 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 by "20%" = "120,000".

[0073] The third line has the 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 by "20%" = "180,000".

[0074] The fourth line has the provisional settlement number "1", transfer adjustment category "adjustment", property "PJ0001: Kyobashi Building", counterparty "SHI001: XX security", management item "S002: temporary security fee", 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 by "20%" = "40,000".

[0075] Lines 5 to 8 are red-ink details for lines 1 to 4, with the posting date listed as "2021 / 06 / 01" and the amount listed as a negative value.

[0076] 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 for June that are transfer entries of these journal entries.

[0077] (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 receivable / payable data but as "transfer settlement data" that simply creates a correction journal entry.

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

[0079] FIG. 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 transfer correction category "correction". For transfer correction category "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 that a correction entry is to be created.

[0080] In the example of the 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 accounting date.

[0081] (T2: Performance data collection) 12 is a diagram for explaining the details of the actual data collection. The actual data collection unit 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.

[0082] FIG. 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 an aggregation button. When the aggregation month and year are specified and the aggregation 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 FIG. 12(A), when the aggregation month and year "2021 / 05 / 01-2021 / 05 / 31" are specified and the aggregation button is pressed, the aggregated data shown in FIG. 12(C) is created.

[0083] 12B shows data to be tabulated to create performance data. The present embodiment is characterized in that transfer settlement data is used as the tabulation target.

[0084] Fig. 12(C) is a diagram showing an example of performance data. 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.

[0085] (T3: Creating accounting data) 13 is a diagram for explaining accounting data creation (T3) in detail. The accounting data creation unit 403 of the owner side system 400 creates accounting data (journalization) for the slip 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.

[0086] 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 target of the specified linked event, with reference to the management item master 106b.

[0087] 13B 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.

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

[0089] In the example shown in Figure 13 (A), when the invoice dates "2021 / 05 / 01-2021 / 05 / 31" and the linked event "Transfer" are specified and the Create button is pressed, the transfer journal entry shown in Figure 13 (C) is created based on the imported transfer settlement data, with reference to the management item master 106b shown in Figure 13 (B).

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

[0091] Regarding payments, 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".

[0092] As described above, according to this embodiment, the asset management system 100 comprises a billing processing unit 102a which inputs scheduled billing data for the target property, including the billing destination, management item, billing amount, and accounting date, a payment processing unit 102b which 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 which 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, so that when an asset management company manages properties owned by an owner, the owner's side can make journal entries at the time of sales and payments.

[0093] [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 contributing to goals 8 and 9 of the SDGs.

[0094] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of goals 12, 13, and 15 of the SDGs.

[0095] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0096] 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.

[0097] 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 known methods.

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

[0099] Furthermore, with regard to the asset management system 100, each of the components shown in the figures is merely a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0100] 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 in a non-transient computer-readable recording medium that includes 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 a RAM, and constitutes the control unit 102 in cooperation with the CPU.

[0101] In addition, this computer program may be stored in an application program server connected to the asset management system 100 via any network, and it is also possible to download all or part of it as needed.

[0102] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "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.

[0103] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, 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 as multiple modules or libraries, and a program that works 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, may use well-known configurations and procedures.

[0104] The various databases etc. stored in the memory unit 106 are storage means 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 etc. used for various processes and providing websites.

[0105] 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 installing software (including programs or data, etc.) that causes the information processing device to realize the processing described in this embodiment.

[0106] Furthermore, the specific form of distribution and integration of the devices is not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to 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. [Explanation of symbols]

[0107] 100 Asset Management System 102 Control section 102a Claims Processing Department 102b Payment processing unit 102c Correction data output section 102d Deposit Processing Unit 102e Screen display control unit 102f Master Maintenance Department 104 Communication interface section 106 Storage section 106a Ownership ratio master 106b Management item master 106c Data File 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network 400 Owner's System 401 Data Acquisition Section 402 Performance Data Collection Department 403 Accounting Data Creation Department

Claims

1. An asset management system of an asset management company that manages properties owned by owners, comprising: 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; An asset management system comprising:

2. 2. The asset management system according to claim 1, wherein the correction data includes records in which the amount is a positive value and records in which the amount is a negative value.

3. 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.

4. 4. The asset management system according to claim 1, wherein the asset management company includes a PM (Property Management) company.

5. 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; 13. An asset management method comprising:

6. An asset management program for causing an asset management company that manages properties owned by an owner to execute the asset management program, the asset management program comprising: 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; Asset management program to implement.

Images