JP7514730B2 - Credit and Debt Linkage Device, Credit and Debt Linkage Method, and Credit and Debt Linkage Program - Google Patents

Description

The present invention relates to a credit/debt linking device, a credit/debt linking method, and a credit/debt linking program.

Patent Document 1 discloses a configuration in which rent and other payments for a property owned by multiple owners are apportioned according to the apportionment ratio of each owner, and journal entries are made for the apportioned amounts using account items set for each owner.

JP 2019-160144 A

However, the invention described in Patent Document 1 above had the problem that the asset management company (PM company) could not switch between creating journal entries and outputting receivables and payables data depending on the event selected each time a voucher was issued.

The present invention has been made in consideration of the above problems, and aims to provide an account receivable/payable linking device, an account receivable/payable linking method, and an account receivable/payable linking program that can switch between acting on behalf of the owner's accounting work by linking journal entry data created from the results of transactions as an asset management company (PM company) to the owner's system, or linking the results of transactions as a PM company to the owner's system as account receivable/payable data for reconciling payments for each owner, depending on the selected event.

In order to solve the above-mentioned problems and achieve the object, the receivables-payables linkage device of the present invention is a receivables-payables linkage device having a memory unit and a control unit, the memory unit having an equity ratio storage means for storing an equity ratio master that sets the equity ratio of each owner for a property owned by multiple owners, and a management item storage means for storing a management item master that is set by linking management items and account items for journal entry creation for each owner, and the control unit has a property-specific deposit and payment acquisition means for acquiring property-specific deposit and payment data for deposits and payments related to the property, an owner-specific payment creation means for creating owner-specific payment data for each owner based on the equity ratio master and the property-specific deposit and payment data, a linked event acquisition means for acquiring a selection instruction for a linked event that is an event for which journal entries are to be created, and a journal entry creation means for creating journal entry data for each owner based on the managed item master, the owner-specific payment data, and the selection instruction.

In addition, in the receivables/payables linkage device according to the present invention, the journal entry creation means creates the journal entry data for the owner-specific payment data of the account item linked to the management item corresponding to the linked event based on the management item master and the selection instruction.

In addition, in the receivables/payables linking device according to the present invention, the control unit is further characterized by having a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data for events that are not subject to journal entry creation based on the selection instruction.

In addition, in the receivables/payables linkage device according to the present invention, the storage unit further includes an owner linkage setting storage means for storing an owner linkage setting master that links and sets the management items of the asset management company that manages the property, which are the company's management items, and the owner management items, which are the management items of the owner who has entrusted the management of the property to the asset management company, and the owner-specific payment creation means creates the owner-specific payment data for each owner based on the owner linkage setting master, the ownership ratio master, and the property-specific deposit payment data.

In addition, in the receivables/payables linkage device according to the present invention, the owner linkage setting master further sets a linkage method between the asset management company and the owner, and the linkage event acquisition means acquires the selection instruction when the linkage method is journal entry linkage.

In addition, in the receivables/payables linkage device according to the present invention, the owner linkage setting master further sets a linkage method between the asset management company and the owner, and the control unit further includes a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data for events that are not subject to journal entry creation based on the selection instruction when the linkage method is journal entry linkage.

In addition, in the receivables/payables linkage device according to the present invention, the owner linkage setting master further sets a linkage method between the asset management company and the owner, and the control unit further includes a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data when the linkage method is receivables/payables linkage.

In addition, in the receivables/payables linking device according to the present invention, the owner linking setting master further sets a linking method between the asset management company and the owner, and the owner-specific payment creation means further creates an asset management report for each owner based on the owner-specific payment data when the linking method is not linked, and sends the asset management report to the owner.

In addition, in the receivables/payables linking device according to the present invention, the management item master includes a self-managed item master that links the self-managed items of the asset management company, which is the owner, to the account items, and/or an owner-managed item master that links the owner-managed items to the account items.

In addition, in the receivables/payables linkage device according to the present invention, the linkage event acquisition means is further characterized in that it displays a journal entry data creation screen on which the selection instruction can be input.

In addition, in the receivables/payables linkage device according to the present invention, the linked event acquisition means is characterized in that, when the asset management company is the owner, it acquires the selection instruction for all the linked events as targets for journal entry creation.

The receivables/payables linking method according to the present invention is a receivables/payables linking method to be executed by a receivables/payables linking device having a memory unit and a control unit, the memory unit having an equity ratio storage means for storing an equity ratio master that sets the equity ratio for each owner for a property owned by multiple owners, and a management item storage means for storing a management item master that is set by linking management items and account items for journal entry creation for each owner, and the control unit is characterized by including a property-specific deposit/payment acquisition step for acquiring property-specific deposit/payment data for deposits and payments related to the property, an owner-specific payment creation step for creating owner-specific payment data for each owner based on the equity ratio master and the property-specific deposit/payment data, a linked event acquisition step for acquiring a selection instruction for a linked event that is an event for which journal entries are to be created, and a journal entry creation step for creating journal entry data for each owner based on the management item master, the owner-specific payment data, and the selection instruction.

The receivables/payables linking program according to the present invention is a receivables/payables linking program to be executed by an receivables/payables linking device having a memory unit and a control unit, the memory unit having an equity ratio storage means for storing an equity ratio master that sets the equity ratio of each owner for a property owned by multiple owners, and a management item storage means for storing a management item master that is set by linking management items and account items for journal entry creation for each owner, and the control unit executes a property-specific deposit/payment acquisition step for acquiring property-specific deposit/payment data for deposits and payments related to the property, an owner-specific payment creation step for creating owner-specific payment data for each owner based on the equity ratio master and the property-specific deposit/payment data, a linked event acquisition step for acquiring a selection instruction for a linked event that is an event for which journal entries are to be created, and a journal entry creation step for creating journal entry data for each owner based on the managed item master, the owner-specific payment data, and the selection instruction.

The present invention has the effect of enabling a PM company to create a new business of acting as an agent for owner accounting operations. In addition, the present invention has the effect of enabling not only accounting entry coordination but also receivables/payables coordination, so that when an owner company and a PM company are in a parent-child relationship, it is possible to propose system unification. In addition, the present invention has the effect of enabling accounting data for owners to be created from tenant contracts and business contracts managed by the PM company. In addition, the present invention has the effect of enabling, when the owner company has a core system, to simplify the reconciliation work for remittances from the PM company by using receivables/payables coordination rather than accounting entry coordination.

FIG. 1 is a diagram showing an example of a conventional credit/debt management system. FIG. 2 is a block diagram showing an example of the configuration of the credit/debt linkage device in this embodiment. FIG. 3 is a flowchart showing an example of the process of the credit/debt linkage device in this embodiment. FIG. 4 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 5 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 6 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 7 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 8 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 9 is a diagram showing an example of the credit/debt linking process in this embodiment. FIG. 10 is a diagram showing an example of the credit/debt linking process 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. Fig. 1 is a diagram showing an example of a conventional credit/debt management system.

Conventionally, when a real estate owner entrusted tenant management, repair management, and complaint handling to a PM company, the PM company would manage billing and payment to tenants and order and payment to contractors on their behalf, settle the results of the payments and payments, and make payments (billing) to the owner. Conventionally, when the owner processed the results of the settlement, the PM report from the PM company to the owner was linked to Excel (registered trademark) paper or data, and the owner had to enter data into each system while looking at the paper or data. This traditionally meant a risk of human error and an increased workload. Also, traditionally, accounting was processed from the PM company's perspective, and accounting could not be processed from the owner's perspective, making it impossible to realize accounting services on their behalf.

For example, as shown in Figure 1, in the past, the PM company settled the deposits to the PM company and the payments from the PM company, and determined the amount to be sent to the owner. When the amount to be sent was determined, the management fee agreed upon in the contract with the owner was deducted and the amount was sent to the owner. And, as shown in Figure 1, in the past, a PM report detailing the deposits and payments was attached to the transfer and sent to the owner, and the owner would check the PM report sent to them while creating journal data and receivables and payables data in the owner's system. Therefore, in the past, even though the PM company had transaction data for each item, a person would input the details of each item into the owner's system while checking the PM report, which required the time-consuming task of individually registering sales data and expense data, and the need to check the data against deposit data, which was time-consuming and prone to errors.

In this embodiment, assuming a case where the owner does not have a core system and the accounting work itself is performed by the PM company, the results of transactions performed by the PM company are linked as journal entry data for each owner, making it possible to perform accounting work on behalf of the owner, and assuming a case where the owner has a core system and the owner reconciles the linked receivables and payables data (deposits from the PM company) and creates journal entries, the results of transactions performed by the PM company are linked to the owner's system as receivables and payables data for each owner. This provides a mechanism that can do this.

2. Configuration
An example of the configuration of the credit/debt linkage device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the credit/debt linkage device 100 according to this embodiment.

As shown in FIG. 2, the receivables/debts linkage device 100 is a commercially available desktop personal computer. Note that the receivables/debts linkage device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers.

The debt-receivable linkage device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the debt-receivable linkage device 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 debt-receivable linkage device 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 a communication line. Here, the network 300 has a function of connecting the debt-receivable linkage device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

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 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes an ownership ratio master 106a, an owner linkage setting master 106b, a management item master 106c, and a transaction database 106d.

The equity ratio master 106a is a master that sets the equity ratio of each owner for properties owned by multiple owners. Here, the equity ratio master 106a may set a property identifier (e.g., a property code and/or a property name), an equity ratio identifier (e.g., an equity ratio code), an owner business partner identifier (e.g., an owner business partner code), an owner identifier (e.g., an owner name), and/or an equity ratio, etc.

The owner collaboration setting master 106b is a master that links and sets the self-managed items, which are the management items of the asset management company that manages the property, and the owner-managed items, which are the management items of the owner who has entrusted the management of the property to the asset management company. Here, the owner collaboration setting master 106b may be set with an owner code, a collaboration company code, a collaboration method self-managed item code, and/or an owner-managed item code, etc. Here, the owner collaboration setting master 106b may be set with a collaboration method between the asset management company and the owner.

The management item master 106c is a master that links management items and account items for journal entry creation for each owner. Here, the management item master 106c may include a self-managed item master that links the self-managed items and account items of the asset management company that is the owner, and/or an owner-managed item master that links the owner-managed items and account items. Here, the self-managed item master may be set with management items, sales account items, advance receipt account items, purchase account items, and/or deposit/advancement account items, etc. Also, the owner-managed item master may be set with the owner, management items, sales account items, advance receipt account items, and/or purchase account items, etc.

The transaction database 106d stores transaction data. The transaction data may include billing data by property, deposit payment data by property, payment data by owner, journal data, billing data by owner, order data, purchase data, billing data, deposit data, and/or inventory data. Here, the billing data by property may be set with a billing number, property, billing destination, management item, accounting date, invoice issue date, expected payment date, and/or billing amount share ratio. The deposit payment data by property may be set with a payment number, property, payee, management item, accounting date, payment statement issue date, expected payment date, payment amount, and/or share ratio. The payment data by owner may be set with a payment number, property, payee, management item, accounting date, payment statement issue date, expected payment date, and/or payment amount. The billing data by owner may be set with a property, billing destination, management item, accounting date, invoice issue date, expected payment date, and/or billing amount.

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 control unit 102 is a CPU or the like that provides overall control of the receivables/payables linkage device 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 function and concept, the control unit 102 includes a property-specific deposit payment acquisition unit 102a, an owner-specific payment creation unit 102b, a linkage event acquisition unit 102c, a journal entry creation unit 102d, and a billing creation unit 102e.

The property-specific deposit and payment acquisition unit 102a acquires property-specific deposit and payment data regarding deposits and payments related to properties. Here, the property-specific deposit and payment acquisition unit 102a may register the property-specific deposit and payment data in the transaction database 106d.

The owner-specific payment creation unit 102b creates owner-specific payment data for each owner. Here, the owner-specific payment creation unit 102b may create owner-specific payment data for each owner based on the ownership ratio master 106a and the property-specific deposit payment data. The owner-specific payment creation unit 102b may also create owner-specific payment data for each owner based on the owner linkage setting master 106b, the ownership ratio master 106a, and the property-specific deposit payment data. If the linkage method set in the owner linkage setting master 106b is not linked, the owner-specific payment creation unit 102b may create an asset management report for each owner based on the owner-specific payment data and send the asset management report to the owner. The owner-specific payment creation unit 102b may also register the owner-specific payment data in the transaction database 106d.

The linked event acquisition unit 102c acquires a selection instruction for a linked event, which is an event for which journal entries are to be created. Here, the linked event acquisition unit 102c may acquire a selection instruction for a linked event when the collaboration method set in the owner collaboration setting master 106b is journal entry collaboration. The linked event acquisition unit 102c may also display a journal entry data creation screen on which a selection instruction for a linked event can be entered. The linked event acquisition unit 102c may also acquire a selection instruction for all linked events for which journal entries are to be created when an asset management company is the owner.

The journal entry creation unit 102d creates journal entry data. Here, the journal entry creation unit 102d may create journal entry data for each owner based on the management item master 106c, the payment data by owner, and a selection instruction for the linked event. The journal entry creation unit 102d may also create journal entry data for the payment data by owner of an account item linked to a management item corresponding to a linked event based on the management item master 106c and a selection instruction for the linked event. The journal entry creation unit 102d may also register the journal entry data in the transaction database 106d.

The billing creation unit 102e creates billing data. Here, the billing creation unit 102e may create owner-specific billing data corresponding to the owner-specific payment data of an event that is not subject to journal entry creation based on a selection instruction for the linked event. Furthermore, when the linkage method set in the owner linkage setting master 106b is journal entry linkage, the billing creation unit 102e may create owner-specific billing data corresponding to the owner-specific payment data of an event that is not subject to journal entry creation based on a selection instruction for the linked event. Furthermore, when the linkage method set in the owner linkage setting master 106b is credit/debt linkage, the billing creation unit 102e creates owner-specific billing data corresponding to the owner-specific payment data. Furthermore, the billing creation unit 102e may register the billing data in the transaction database 106d.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Accounts and Debts Linkage Processing]
An example of the credit/debt linkage process in this embodiment will now be described with reference to Fig. 3. Fig. 3 is a flowchart showing an example of the process of the credit/debt linkage device 100 in this embodiment.

As shown in FIG. 3, the property-specific deposit and payment acquisition unit 102a acquires property-specific deposit data regarding deposits related to properties owned by multiple owners, and registers the property-specific deposit data in the transaction database 106d (step SA-1).

Then, the property-specific deposit and payment acquisition unit 102a acquires property-specific payment data regarding payments related to the property, and registers the property-specific payment data in the transaction database 106d (step SA-2).

Then, the owner-specific payment creation unit 102b creates owner-specific payment data for each owner based on the owner linkage setting master 106b, the ownership ratio master 106a, the property-specific deposit data, and the property-specific payment data (step SA-3).

Then, the linkage event acquisition unit 102c determines whether the linkage method set in the owner linkage setting master 106b is journal entry linkage (step SA-4).

Then, if the linkage event acquisition unit 102c determines that the linkage method set in the owner linkage setting master 106b is journal entry linkage (step SA-4: Yes), it transitions the process to step SA-5.

Then, the linked event acquisition unit 102c displays on the output device 114 a journal entry data creation screen on which a selection instruction can be input for the linked event, which is the event for which journal entry is to be created, and when a selection instruction is input to the journal entry data creation screen by the user via the input device 112, the linked event acquisition unit 102c acquires the selection instruction for the linked event (step SA-5).

Then, the journal entry creation unit 102d creates journal entry data for the owner-specific payment data of the account item linked to the management item corresponding to the linked event based on the management item master 106c and the selection instructions for the linked event, and the billing creation unit 102e creates owner-specific billing data or owner-specific negative billing (payment) data corresponding to the owner-specific payment data of the event not subject to journal entry creation (step SA-6), and the process ends.

On the other hand, if the linkage event acquisition unit 102c determines that the linkage method set in the owner linkage setting master 106b is not accounting linkage (step SA-4: No), it transitions the process to step SA-7.

Then, the billing creation unit 102e determines whether the collaboration method set in the owner collaboration setting master 106b is creditor-debtor collaboration (step SA-7).

Then, if the billing creation unit 102e determines that the collaboration method set in the owner collaboration setting master 106b is debt-receivable collaboration (step SA-7: Yes), it transitions the process to step SA-8.

Then, the billing creation unit 102e creates owner-specific billing data or owner-specific negative billing (payment) data corresponding to the owner-specific payment data (step SA-8) and ends the process.

On the other hand, if the billing creation unit 102e determines that the linkage method set in the owner linkage setting master 106b is not an account receivable-debt linkage (not linked) (step SA-7: No), it transitions the process to step SA-9.

Then, the owner-specific payment creation unit 102b creates an asset management report for each owner based on the owner-specific payment data, sends the asset management report to the owner (e.g., the owner's email address) (step SA-9), and ends the process.

Here, an example of the credit/debt linking process in this embodiment will be described with reference to Figures 4 to 10. Figures 4 to 10 are diagrams showing an example of the credit/debt linking process in this embodiment.

As shown in FIG. 4, in this embodiment, when the Kyobashi Building is jointly owned by multiple owners, the owner's equity ratio for each property is set as the equity ratio registration. This master determines the settlement ratio to the owner for each transaction. Here, in the case of a transaction involving an owner-owned property, the tenant rent is remitted to the owner, but in cases where multiple owners own the property, the equity ratio master 106a is used to declare the owner's equity at the time of invoicing the tenant and to apportion it at the time of remittance.

As shown in FIG. 5, in this embodiment, property-specific billing data is created on the billing input screen, in which rent and maintenance fees for tenants of the Kyobashi Building are set, and is sent to the tenants.

As shown in FIG. 6, in this embodiment, property-specific payment data is created on the payment input screen, with the daily and emergency security fees set for security at the Kyobashi Building, and the payment is transferred to XX Security.

As shown in FIG. 7, in this embodiment, the owner remittance procurement data is created by clearing the invoice input result and processing the settlement of the payment input result, and multiplying the invoice payment performance by the ownership ratio to generate payment data by owner. Here, as shown in FIG. 7, in this embodiment, the received deposit data is displayed as a "+" payment, and the paid payment data is displayed as a "-" payment. Furthermore, as shown in FIG. 7, in this embodiment, the management fee for PM work is also displayed as a "-" payment, and the total payment amount is determined.

As shown in FIG. 8, in this embodiment, on the owner linkage setting master maintenance screen, the owner linkage setting master 106b is set by selecting from among "0: Journal entry linkage", which is a setting in which an account item is determined from the set owner management item code and a journal entry is created, "1: Receivables/payables linkage", which is a setting in which receivables/payables data is linked using the set owner management item code, and "2: Not linked", which is a setting in which no linkage is performed.

As shown in FIG. 9, in this embodiment, in the case of "0: journal entry linkage", the settlement results are linked, and based on the registered billing data, payment data, deposit data, and deposit reconciliation data, the account items set in the management item master 106c are used to convert into journal entry data according to the linkage events checked in the building management system. Here, as shown in FIG. 9, in this embodiment, the ownership ratio of the transaction data also includes the PM company's share, so journal entries for the PM company itself and journal entries for other owners are created based on the payment data, owner linkage setting master 106b, the company's own management item master, and the owner management item master, and the slips created for the company's own account are the journal entries for the company's rent and common area fee income for September based on the August deposit results, as well as the journal entries for the deposit remittance and management fee related to the September settlement results, and the slips created for the owner of Ginza Real Estate are the journal entries for the rent related to the September settlement results.

On the other hand, as shown in FIG. 10, in this embodiment, in the case of "1: Linking of receivables and payables," the settlement results are linked, and the payment data created by the PM company becomes billing data from the owner's perspective, so data is output that can be linked from the payment data to the billing data.

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

In addition, with regard to the debt-receivable linkage device 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 receivables/debts linkage device 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 receivables/debts linkage device 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 a storage unit 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 form the control unit.

In addition, this computer program may be stored in an application program server connected to the receivables/payables linkage device 100 via any network, and it is also possible to download all or part of it 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, or may 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 this embodiment, 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 providing websites.

The receivables/debts linkage device 100 may be configured as a known information processing device such as a personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The receivables/debts linkage device 100 may also be realized by implementing software (including programs or data, etc.) that causes the 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 functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in industries such as the real estate and asset management industries that perform agency services.

100 Credit/debt linkage device 102 Control unit 102a Property-specific deposit/payment acquisition unit 102b Owner-specific payment creation unit 102c Linkage event acquisition unit 102d Journal entry creation unit 102e Bill creation unit 104 Communication interface unit 106 Storage unit 106a Ownership ratio master 106b Owner linkage setting master 106c Management item master 106d Transaction database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (13)

A credit and debt linking device having a memory unit and a control unit,
The storage unit is
an ownership ratio storage means for storing an ownership ratio master that sets an ownership ratio for each owner with respect to a property owned by multiple owners;
a management item storage means for storing a management item master set by linking management items and account items for journal entry creation for each owner;
Equipped with
The control unit is
a property-specific deposit and payment acquisition means for acquiring property-specific deposit and payment data regarding deposits and payments related to the property;
an owner-specific payment creating means for creating owner-specific payment data for each of the owners based on the ownership ratio master and the property-specific payment data;
A linked event acquisition means for acquiring a selection instruction for a linked event which is an event for which a journal entry is to be created;
a journal entry creating means for creating journal entry data for each owner based on the management item master, the payment data for each owner, and the selection instruction;
A claim and debt linking device comprising: The journal entry creation means includes:
The receivables/payables linking device according to claim 1, characterized in that, based on the management item master and the selection instruction, the journal entry data for the owner-specific payment data for the account item linked to the management item corresponding to the linked event is created. The control unit is
a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data for an event not subject to journal entry creation based on the selection instruction;
3. The claim/debt linking device according to claim 1 or 2, further comprising: The storage unit is
an owner linkage setting storage means for storing an owner linkage setting master that links and sets the management items of the asset management company that manages the property to the owner management items that are the management items of the owner who has entrusted the management of the property to the asset management company;
Further comprising:
The owner-specific payment generation means includes:
3. The claim/debt linkage device according to claim 1 or 2, wherein the owner-specific payment data for each owner is created based on the owner linkage setting master, the ownership ratio master, and the property-specific deposit/payment data. The owner collaboration setting master is
Furthermore, a method of cooperation between the asset management company and the owner is set,
The linkage event acquisition means includes:
5. The claim/debt linking device according to claim 4, wherein, when the linking method is journal entry linking, the selection instruction is acquired. The owner collaboration setting master is
Furthermore, a method of cooperation between the asset management company and the owner is set,
The control unit is
a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data of an event that is not subject to journal entry creation based on the selection instruction when the collaboration method is journal entry collaboration;
5. The claim/debt linking device according to claim 4, further comprising: The owner collaboration setting master is
Furthermore, a method of cooperation between the asset management company and the owner is set,
The control unit is
a billing creation means for creating owner-specific billing data corresponding to the owner-specific payment data when the linking method is credit-debt linking;
5. The claim/debt linking device according to claim 4, further comprising: The owner collaboration setting master is
Furthermore, a method of cooperation between the asset management company and the owner is set,
The owner-specific payment generation means includes:
The receivables/payables linking device according to claim 4, further comprising, when the linking method is non-linked, creating an asset management report for each owner based on the payment data for each owner, and sending the asset management report to the owner. The management item master includes:
The receivables-payables linking device according to any one of claims 4 to 8, characterized in that it includes a self-managed item master set up by linking the self-managed items of the asset management company, which is the owner, with the account items, and/or an owner-managed item master set up by linking the owner-managed items with the account items. The linkage event acquisition means includes:
10. The credit/debt linking device according to claim 1, further comprising a journal data creation screen on which the selection instruction can be input. The linkage event acquisition means includes:
9. The receivables/payables linking device according to claim 8, wherein, when the asset management company is the owner, the selection instructions are acquired for all of the linked events as targets for journal entry creation. A claim/debt linking method to be executed by a claim/debt linking device having a memory unit and a control unit,
The storage unit is
an ownership ratio storage means for storing an ownership ratio master that sets an ownership ratio for each owner with respect to a property owned by multiple owners;
a management item storage means for storing a management item master set by linking management items and account items for journal entry creation for each owner;
Equipped with
The control unit executes
a property-specific deposit and payment acquisition step for acquiring property-specific deposit and payment data regarding deposits and payments related to the property;
an owner-specific payment creation step of creating owner-specific payment data for each owner based on the ownership ratio master and the property-specific deposit payment data;
A linked event acquisition step of acquiring a selection instruction for a linked event which is an event for which a journal entry is to be created;
a journal entry creation step of creating journal entry data for each owner based on the management item master, the payment data for each owner, and the selection instruction;
A method for linking claims and debts comprising: A credit and debt linking program to be executed by a credit and debt linking device having a memory unit and a control unit,
The storage unit is
an ownership ratio storage means for storing an ownership ratio master that sets an ownership ratio for each owner with respect to a property owned by multiple owners;
a management item storage means for storing a management item master set by linking management items and account items for journal entry creation for each owner;
Equipped with
In the control unit,
a property-specific deposit and payment acquisition step for acquiring property-specific deposit and payment data regarding deposits and payments related to the property;
an owner-specific payment creation step of creating owner-specific payment data for each owner based on the ownership ratio master and the property-specific deposit payment data;
A linked event acquisition step of acquiring a selection instruction for a linked event which is an event for which a journal entry is to be created;
a journal entry creation step of creating journal entry data for each owner based on the management item master, the payment data for each owner, and the selection instruction;
A creditor-debtor linkage program to implement this.

Images