Project-specific income / expense management device, project-specific income / expense management method, and project-specific income / expense management program

The project-specific income and expenditure management device addresses the challenge of separate cost and income management by automating journal entry creation and completion transfer, facilitating efficient cost aggregation and simplified accounting for construction projects.

JP7579191B2Active Publication Date: 2024-11-07OBIC CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2021054126
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-26
Publication Date
2024-11-07
Estimated Expiration
2041-03-26

AI Technical Summary

Technical Problem

Existing systems fail to automatically synchronize journal entry creation and execute complete transfer on a contract-by-contract basis, making it difficult to manage construction work costs and income separately, especially for small-scale projects.

Method used

A project-specific income and expenditure management device that includes a storage section and control section, enabling separate management of billing units (contracts) and in-house units (projects), allowing for automated journal entry creation and completion transfer based on project identifiers and contract data.

Benefits of technology

Enables efficient cost aggregation and simplified accounting for construction projects of various scales, reducing input load and facilitating accurate cost management, even for small-scale works, by automating the process of creating and updating journal entries.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579191000001
    Figure 0007579191000001
  • Figure 0007579191000002
    Figure 0007579191000002
  • Figure 0007579191000003
    Figure 0007579191000003
Patent Text Reader

Abstract

To provide a project-based balance management device, a project-based balance management method and a project-based management program capable of performing balance management in a project unit by dividing a billing unit and a balance management unit in a company, and executing completion transfer in a contract unit by interlocking journaling creation.SOLUTION: A project-based balance management device acquires project order reception state data including a dummy record, sets an order reception record set by associating an order reception identifier different from a project identifier and sales completion section to project order reception state data when contract data is inputted, acquires cost specification data obtained by setting the same order reception identifier as the project identifier, a cost subject and cost, creates an incomplete journal entry, acquires project sales data, updates a sales completion section set in the project order reception state data, and creates complete transfer journal entry data.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a project-by-project income and expenditure management device, a project-by-project income and expenditure management method, and a project-by-project income and expenditure management program. [Background technology]

[0002] Patent Document 1 discloses a configuration for implementing appropriate project design by registering virtual projects, which are imaginary project units rather than actual project units, creating budgets for each virtual project, simulating total income and expenditures and total budget / actual, and comparing them with the actual project. [Prior art documents] [Patent documents]

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

[0004] However, the invention described in the above Patent Document 1 had a problem in that it was not possible to automatically link the creation of journal entries and execute complete transfers on a contract basis.

[0005] The present invention has been made in consideration of the above problems, and aims to provide a project-specific income and expenditure management device, project-specific income and expenditure management method, and project-specific income and expenditure management program that separates the billing unit (contract unit) from the in-house income and expenditure management unit (project unit), enables income and expenditure management on a project basis, and can perform completion transfer on a contract basis by linking the creation of accounting entries. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a project-by-project income and expenditure management device comprising a storage unit and a control unit, the storage unit comprising project storage means for storing project basic data in which a project identifier for a project is set, the control unit comprising project acquisition means for acquiring project order status data including a dummy record set in association with the project identifier and a sales completion classification based on the project basic data, and when contract data including a contract amount linked to the project is input, a project acquisition means for acquiring project order status data including a dummy record set in association with the project identifier, an order identifier different from the project identifier, and the sales completion classification based on the project basic data and the contract data, the cost input data in which the project identifier, cost item, and cost are set is input, a cost detail acquisition means for acquiring cost detail data in which the project identifier, the order identifier identical to the project identifier, the cost item, and the cost are set; an uncompleted journal entry creation means for creating uncompleted journal entry data based on the cost detail data; a sales acquisition means for acquiring project sales data in which the sales amount for each contract is set; an update means for updating the sales completion classification set in the project order status data based on the contract data and the project sales data; and a completion journal entry creation means for creating completion transfer journal entry data based on the project order status data, the cost detail data, and the project sales data.

[0007] In addition, in the project-specific income and expenditure management device of the present invention, the update means is characterized in that it updates the sales completion classification set in the dummy record included in the project order status data from incomplete to completed based on the contract data and the project sales data.

[0008] In addition, in the project-specific income and expenditure management device of the present invention, the project acquisition means is further characterized in that it acquires dummy order data that is set in association with the project identifier, the order identifier that is identical to the project identifier, a dummy contract amount, and an order status based on the project basic data.

[0009] In addition, in the project-by-project income / expense management device of the present invention, the contract input means is further characterized in that, when the contract data is input, it acquires project order data that is set by linking the project identifier, an order identifier different from the project identifier, the contract amount, and the order status based on the project basic data and the contract data.

[0010] In addition, in the project-by-project income / expense management device of the present invention, the contract input means is further characterized in that it updates the order status set in the dummy order data from inquiry to order based on the project order data.

[0011] In addition, in the project-by-project income / expense management device of the present invention, the control unit is characterized by further comprising a list acquisition means for acquiring project list data setting the project identifier, the contract amount, the cost item, the cost, and / or the gross profit based on the contract data and the cost detail data.

[0012] In addition, in the project-by-project income and expenditure management device according to the present invention, the dummy contract amount is 0 yen.

[0013] In addition, in the project-specific income and expenditure management device of the present invention, the update means is characterized in that it updates the sales completion classification set in the order record contained in the project order status data from incomplete to completed based on the contract data and the project sales data.

[0014] In the project-by-project income and expenditure management device according to the present invention, the uncompleted journal entry data is characterized in that the debit account item is an uncompleted item and the credit account item is a current liability item.

[0015] Further, a project-by-project income and expenditure management method according to the present invention is a project-by-project income and expenditure management method to be executed by a project-by-project income and expenditure management device having a storage unit and a control unit, the storage unit having a project storage means for storing project basic data in which a project identifier of a project is set, and the control unit is configured to execute a project acquisition step of acquiring project order status data including a dummy record set in association with the project identifier and a sales completion classification based on the project basic data, when contract data including a contract amount linked to the project is input, acquiring an order record set in association with the project identifier, an order identifier different from the project identifier, and the sales completion classification based on the project basic data and the contract data, the step of acquiring cost detail data in which the project identifier, the order identifier identical to the project identifier, the cost item, and the cost are set when cost input data in which the project identifier, the cost item, and the cost are set is input; the step of creating uncompleted journal entry data based on the cost detail data; the step of acquiring project sales data in which the sales amount for each contract is set; the step of updating the sales completion classification set in the project order status data based on the contract data and the project sales data; and the step of creating completed transfer journal entry data based on the project order status data, the cost item, and the project sales data.

[0016] Further, a project-specific income and expenditure management program according to the present invention is a project-specific income and expenditure management program to be executed by a project-specific income and expenditure management device having a storage unit and a control unit, the storage unit having a project storage means for storing project basic data in which a project identifier of a project is set, the control unit having a project acquisition step of acquiring project order status data including a dummy record set in association with the project identifier and a sales completion classification based on the project basic data, when contract data including a contract amount linked to the project is input, acquiring an order record set in association with the project identifier, an order identifier different from the project identifier, and the sales completion classification based on the project basic data and the contract data, as the project acceptance step. the cost input data in which the project identifier, cost item, and cost are set is input, a cost detail acquisition step for acquiring cost detail data in which the project identifier, the order identifier that is the same as the project identifier, the cost item, and the cost are set; an uncompleted journal entry creation step for creating uncompleted journal entry data based on the cost detail data; a sales acquisition step for acquiring project sales data in which the sales amount for each contract is set; an update step for updating the sales completion category set in the project order status data based on the contract data and the project sales data; and a completion journal entry creation step for creating completion transfer journal entry data based on the project order status data, the cost detail data, and the project sales data. Effect of the Invention

[0017] According to the present invention, by being able to manage construction invoices and cost management separately, it is possible to handle constructions of various scales, from large-scale constructions to small-scale constructions. In addition, according to the present invention, in the construction industry, in order to obtain sales results by segment, it is sometimes necessary to register multiple details for one contract, and in the case of small constructions, contracts for sales in the same month are registered together in anticipation of simplification of input, but in such cases, since it is difficult to register the costs separately in the field operation, it is possible to efficiently perform cost aggregation. In addition, according to the present invention, it is possible to reduce the input load on the business personnel and to realize appropriate accounting. In addition, according to the present invention, in the income and expenditure management of project credits and costs, it is possible to allocate material costs such as detergents and labor costs for each creditor, even though the creditors vary by floor, not only for small constructions but also for cleaning businesses. [Brief description of the drawings]

[0018] [Figure 1] FIG. 1 is a diagram showing an example of a conventional project structure. [Diagram 2] FIG. 2 is a diagram showing an example of a project structure in this embodiment. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of a project-by-project income / expense management device in this embodiment. [Figure 4] FIG. 4 is a flowchart showing an example of the process of the project-by-project income and expenditure management device in this embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. [Figure 9]FIG. 9 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the project-by-project income / expense management process in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0020] [1. Overview] First, an overview of the present invention will be described with reference to Fig. 1 and Fig. 2. Fig. 1 is a diagram showing an example of a conventional project structure. Fig. 2 is a diagram showing an example of a project structure in this embodiment.

[0021] Traditionally, for cleaning work on an entire building, orders are received for each floor, but there are cases where the labor and material costs for cleaning the building are managed on a building-wide basis rather than on an order (contract) basis, or when additional work such as exterior wall work is required during the construction of an apartment building, the orders (contracts) are separated but the costs are managed as one project. There are also cases where small-scale construction work, construction work on the same site despite separate contracts, additional work during construction, etc., where the contracts are separate but the costs must be managed together in order to make operations difficult.

[0022] However, in the past, it was not possible to manage the billing unit (contract) to the business partner and the internal income and expenditure management unit (project) separately. In addition, although costs such as material costs, outsourcing costs, labor costs, expenses, and indirect costs were generated, they were all managed on a contract basis.

[0023] Therefore, as shown in Figure 1, previously when including costs, it was necessary to select the project, select the contract, and then select the details.

[0024] Therefore, in this embodiment, a mechanism is provided that enables cost inclusion on a project-by-project basis (a unit that groups together multiple contracts) and enables income and expenditure management on a project-by-project basis (a unit that groups together multiple contracts), on the premise that contracts linked to a project are sales in the same month. Also, in this embodiment, by creating a checklist, it is possible to confirm whether the same-month sales conditions are met at the end of the month (whether the sales completion status of contracts linked to a project is the same).

[0025] For example, as shown in Fig. 2, in this embodiment, all costs are consolidated into a dummy contract, making it possible to manage income and expenditures for one project. That is, as shown in Fig. 2, in this embodiment, a dummy contract is automatically created, and when all other linked contracts are completed, the dummy contract is changed to a completed state, so that all linked costs for that month can be transferred to the completion state. Also, as shown in Fig. 2, in this embodiment, costs can be included by selecting only the project.

[0026] [2. Configuration] An example of the configuration of the project-by-project income and expenditure management device 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 project-by-project income and expenditure management device 100 according to this embodiment.

[0027] 3, the project-specific income and expenditure management device 100 is a commercially available desktop personal computer. Note that the project-specific income and expenditure management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and 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.

[0028] The project-by-project income and expenditure management device 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 project-by-project income and expenditure management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0029] The communication interface unit 104 communicably connects the project-by-project income and expenditure management 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 the communication line. Here, the network 300 has a function of connecting the project-by-project income and expenditure management device 100 and the server 200 to each other so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

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

[0031] 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 a project database 106a.

[0032] The project database 106a stores project data of a project. Here, the project database 106a may store basic project data in which a project identifier of the project is set. The project database 106a may also store contract data, dummy order data, project order status data, project order data, cost input data, cost detail data, journal data, project list data, and / or project sales data, etc. Here, the journal data may include uncompleted journal data and / or completed transfer journal data, etc.

[0033] The control unit 102 is a CPU or the like that comprehensively controls the project-by-project income / expense management 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, and the like, and executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes a project acquisition unit 102a, a contract input unit 102b, a cost detail acquisition unit 102c, a list acquisition unit 102d, a sales acquisition unit 102e, an update unit 102f, and an accounting entry creation unit 102g.

[0034] The project acquisition unit 102a acquires project data. Here, the project acquisition unit 102a may acquire project order status data. Furthermore, the project acquisition unit 102a may acquire dummy order data set by linking a project identifier, an order identifier identical to the project identifier, a dummy contract amount, and an order status based on the project basic data. Here, the dummy contract amount may be 0 yen. Furthermore, the project acquisition unit 102a may register the project data, the project order status data, and / or the dummy order data, etc., in the project database 106a.

[0035] The contract input unit 102b sets the project receipt status data to an order record in which the project identifier, the order identifier different from the project identifier, and the sales completion category are linked together. Here, when contract data including a contract amount linked to a project is input, the contract input unit 102b may set the project receipt status data to which the project identifier, the order identifier different from the project identifier, and the sales completion category are linked together. In addition, when contract data is input, the contract input unit 102b may acquire project receipt data in which the project identifier, the order identifier different from the project identifier, the contract amount, and the order status are linked together. In addition, the contract input unit 102b may update the order status set in the dummy receipt data from inquiry to received based on the project receipt data. In addition, the contract input unit 102b may register the contract data, etc., in the project database 106a.

[0036] The cost detail acquisition unit 102c acquires cost detail data in which a project identifier, an order identifier identical to the project identifier, a cost item, and a cost are set. Here, when cost input data in which a project identifier, a cost item, and a cost are set is input, the cost detail acquisition unit 102c may acquire cost detail data in which a project identifier, an order identifier identical to the project identifier, a cost item, and a cost are set. In addition, the cost detail acquisition unit 102c may register the cost input data and / or the cost detail data in the project database 106a.

[0037] The list acquisition unit 102d acquires project list data. Here, the list acquisition unit 102d may acquire project list data in which a project identifier, a contract amount, a cost item, a cost, and / or a gross profit is set based on the contract data and the cost detail data. The list acquisition unit 102d may also register the project list data and the like in the project database 106a.

[0038] The sales acquisition unit 102e acquires project sales data. Here, the sales acquisition unit 102e may acquire project sales data in which the sales amount for each contract is set. In addition, the sales acquisition unit 102e may register the project sales data, etc. in the project database 106a.

[0039] The update unit 102f updates the project order status data. Here, the update unit 102f may update the sales completion classification set in the project order status data based on the contract data and the project sales data. Also, the update unit 102f may update the sales completion classification set in the dummy record included in the project order status data from "uncompleted" to "completed" based on the contract data and the project sales data. Also, the update unit 102f may update the sales completion classification set in the order record included in the project order status data from "uncompleted" to "completed" based on the contract data and the project sales data.

[0040] The journal entry preparation unit 102g prepares journal entry data. Here, the journal entry preparation unit 102g may prepare uncompleted journal entry data based on the cost detail data. Here, the uncompleted journal entry data may have a debit account item of an uncompleted account and a credit account item of a current liability item (e.g., accounts payable, accounts payable, construction accounts payable, unpaid expenses, etc.). Furthermore, the journal entry preparation unit 102g may prepare completion transfer journal entry data based on the project order status data, the cost detail data, and the project sales data. Furthermore, the journal entry preparation unit 102g may register the journal entry data, etc. in the project database 106a.

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

[0042] [Project-specific income and expenditure management processing] An example of the project-by-project income and expenditure management process in this embodiment will now be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of the process of the project-by-project income and expenditure management device 100 in this embodiment.

[0043] As shown in FIG. 4, the project acquisition unit 102a acquires, based on the project basic data stored in the project database 106a, dummy order data set by linking a project identifier, an order identifier that is the same as the project identifier, a dummy contract amount set to 0 yen, and an order status, and project order status data set by linking a project identifier, an order identifier that is the same as the project identifier, and a sales completion category (step SA-1).

[0044] Then, when the user inputs contract data including the contract amount linked to the project via the input device 112, the contract input unit 102b acquires project order data that is set by linking the project identifier, an order identifier different from the project identifier, the contract amount, and the order status based on the project basic data and contract data stored in the project database 106a, sets an order record that is set by linking the project identifier, an order identifier different from the project identifier, and the sales completion category to the project order status data, and updates the order status set in the dummy order data from inquiry to order based on the project order data (step SA-2).

[0045] When the user inputs cost input data setting a project identifier, a cost item, and a cost via the input device 112, the cost detail acquisition unit 102c acquires cost detail data setting the project identifier, an order identifier that is the same as the project identifier, a cost item, and a cost (step SA-3).

[0046] Then, the journal entry preparation unit 102g prepares uncompleted journal entry data based on the cost detail data (step SA-4).

[0047] Then, the list acquisition unit 102d acquires project list data that sets the project identifier, contract amount, cost item, cost, and gross profit based on the contract data and the cost detail data, and displays the list data on the output device 114 (step SA-5).

[0048] Then, the sales obtaining unit 102e obtains project sales data in which the sales amount for each contract is set, input by the user via the input device 112 (step SA-6).

[0049] Then, based on the contract data and the project sales data, the update unit 102f updates the sales completion classification set in the order record included in the project order status data from incomplete to completed, and updates the sales completion classification set in the dummy record included in the project order status data from incomplete to completed (step SA-7).

[0050] Then, the journal entry preparation unit 102g prepares completion transfer journal data based on the project order status data, the cost detail data, and the project sales data (step SA-8), and ends the process.

[0051] An example of the project-by-project income and expenditure management process in this embodiment will now be described with reference to Fig. 5 to Fig. 10. Fig. 5 to Fig. 10 are diagrams showing an example of the project-by-project income and expenditure management process in this embodiment.

[0052] As shown in Fig. 5, in this embodiment, project basic data is registered by inputting basic construction data by the user, and project dummy order data (dummy order data) and project order status data (dummy) are also created at the same time. Here, in this embodiment, an order number that can identify the project dummy order data as a dummy may be set.

[0053] Then, as shown in FIG. 6, in this embodiment, contract data is registered by the user inputting contract data, project order data and project order status data are created, and since all project order data linked to the project have an order status = ordered, the order status of the project dummy order data is updated.

[0054] As shown in FIG. 7, in this embodiment, cost data is registered on the cost input screen through various inputs by the user, such as purchase input, expense input, or daily report input, and cost detail data for the project number = order number is automatically obtained.

[0055] Then, as shown in FIG. 8, in this embodiment, work schedule data (project schedule data) is acquired based on the cost detail data.

[0056] Then, as shown in Figure 9, in this embodiment, when the user inputs project sales data in which the sales amount for each contract is set, the sales completion classification of the project order data linked to the project sales data is updated to completed, and the project order status data (dummy) is updated to be subject to completion transfer.

[0057] As shown in FIG. 10, in this embodiment, as an accounting linkage, uncompleted accounting data is created for all order records based on the cost detail data and the project order status data, and completed transfer accounting data is created for order records for which the sales completion category in the project order status data is set to completed based on the project order status data, cost detail data, and project sales data.

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

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

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

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

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

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

[0064] Moreover, with regard to the project-by-project income / expense management device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0065] For example, the processing functions of the project-by-project income and expenditure management 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 in a non-transient computer-readable recording medium including programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the project-by-project income and expenditure management 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 a RAM, and constitutes a control unit in cooperation with the CPU.

[0066] In addition, this computer program may be stored in an application program server connected to the project-by-project income / expense management device 100 via any network, and it is also possible to download all or a part of it as necessary.

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

[0068] 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 configuration that is distributed as a plurality of modules or libraries, and a program that achieves its function by cooperating with a separate program, such as an OS. 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, may use well-known configurations and procedures.

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

[0070] The project-by-project income and expenditure management device 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 project-by-project income and expenditure management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0071] Furthermore, the specific form of distribution and integration of the devices is not limited to that 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 functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0072] The present invention is useful in the construction industry, which has a lot of small-scale construction work, such as renewal and maintenance work for each small industry. [Explanation of symbols]

[0073] 100 Project-specific income / expense management device 102 Control section 102a Project Acquisition Department 102b Contract input section 102c Cost Detail Acquisition Department 102d List Acquisition Section 102e Sales Acquisition Department 102f Update section 102g Journal entry preparation section 104 Communication interface section 106 Storage section 106a Project Database 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A project-specific income / expense management device having a storage unit and a control unit, The storage unit is a project storage means for storing project basic data in which a project identifier of the project is set; Equipped with The control unit is a project acquisition means for assigning a dummy order identifier for each project based on the project basic data, setting a dummy record for each project that links the dummy order identifier, the project identifier, and a sales completion category that is initially set as "uncompleted," and acquiring project order status data including the dummy record; a contract input means for, when contract data including a contract amount linked to the project is input, identifying the project identifier of the project linked to the contract data from the project basic data, allocating an order identifier different from the project identifier, and setting an order record in the project order status data by linking the project identifier, the order identifier, and the sales completion category that is initially set as "uncompleted"; a cost detail acquisition means for acquiring, when cost input data in which the project identifier, cost item, and cost are set, cost detail data in which the project identifier, an order identifier identical to the project identifier, the cost item, and the cost are set; an unfinished journal entry creating means for creating unfinished journal entry data based on the cost detail data, the cost being an amount, the debit account being an unfinished cost item, and the credit account being a current liability item; a sales acquisition means for acquiring project sales data in which the project identifier and the sales amount for each contract are set; an update means for updating the sales completion classification set in the order record included in the project order status data from incomplete to completed by comparing the contract amount set in the contract data linked to the project of the project identifier set in the project sales data with the sales amount set in the project sales data; a completion journal entry creation means for creating completion transfer journal entry data based on the cost detail data in which the project identifier set in the project order status data in which the sales completion classification has been updated to "completed" is set, with the cost as an amount, and with the debit account item as the completed account of the cost item and the credit account item as the incomplete account of the cost item; A project-specific income / expenditure management device comprising:

2. The update means includes: The project-specific income / expense management device according to claim 1, characterized in that the sales completion classification set in the dummy record included in the project order status data is updated from "incomplete" to "completed" based on the contract data and the project sales data.

3. The project acquisition means includes: The project-specific income and expenditure management device according to claim 1 or 2, further comprising: acquiring dummy order data set in association with the project identifier set in the project basic data, the order identifier which is identical to the project identifier, a dummy contract amount which is initially set to 0 yen, and an order status which is initially set to inquiry.

4. The contract input means includes: Furthermore, when the contract data is input, the project-specific income and expenditure management device as described in claim 3 acquires the project identifier set in the project basic data, an order identifier different from the project identifier, the contract amount set in the contract data, and project order data set by linking the order with the order status initially set.

5. The contract input means includes:

5. The project-by-project income / expenditure management device according to claim 4, further comprising: updating the order status set in the dummy order data from the inquiry to the order based on the project order data.

6. The control unit is a list acquisition means for acquiring project list data in which the project identifier, the contract amount, the cost item, the cost, and / or the gross profit are set based on the contract data and the cost detail data; 6. The project-by-project income / expenses management device according to claim 1, further comprising:

7. The dummy contract amount is, 6. The project-by-project income and expenditure management device according to claim 3, wherein the amount is 0 yen.

8. A project-by-project income / expense management method to be executed by a project-by-project income / expense management device having a storage unit and a control unit, The storage unit is a project storage means for storing project basic data in which a project identifier of the project is set; Equipped with The control unit executes a project acquisition step of numbering a dummy order identifier for each project based on the project basic data, setting a dummy record for each project that links the dummy order identifier, the project identifier, and a sales completion category that is initially set as "uncompleted," and acquiring project order status data including the dummy record; a contract input step of, when contract data including a contract amount linked to the project is input, identifying the project identifier of the project linked to the contract data from the project basic data, allocating an order identifier different from the project identifier, and setting an order record in the project order status data by linking the project identifier, the order identifier, and the sales completion category that is initially set as "uncompleted"; a cost detail acquisition step of acquiring cost detail data in which the project identifier, the cost item, and the cost are set, when the cost input data in which the project identifier, the cost item, and the cost are set is inputted; an unfinished journal entry creating step for creating unfinished journal entry data based on the cost detail data, the cost being an amount, the debit account being an unfinished cost item, and the credit account being a current liability item; a sales acquisition step of acquiring project sales data in which the project identifier and the sales amount for each contract are set; an updating step of updating the sales completion classification set in the order record included in the project order status data from incomplete to completed by comparing the contract amount set in the contract data linked to the project of the project identifier set in the project sales data with the sales amount set in the project sales data; a completion journal entry creation step for creating completion transfer journal entry data based on the cost detail data in which the project identifier set in the project order status data in which the sales completion classification has been updated to "completed" is set, with the cost as an amount, and with the debit account item being the completed account of the cost item and the credit account item being the incomplete account of the cost item; A project-specific income / expense management method comprising:

9. A project-by-project income / expense management program to be executed by a project-by-project income / expense management device having a storage unit and a control unit, The storage unit is a project storage means for storing project basic data in which a project identifier of the project is set; Equipped with In the control unit, a project acquisition step of numbering a dummy order identifier for each project based on the project basic data, setting a dummy record for each project that links the dummy order identifier, the project identifier, and a sales completion category that is initially set as "uncompleted," and acquiring project order status data including the dummy record; a contract input step of, when contract data including a contract amount linked to the project is input, identifying the project identifier of the project linked to the contract data from the project basic data, allocating an order identifier different from the project identifier, and setting an order record in the project order status data by linking the project identifier, the order identifier, and the sales completion category that is initially set as "uncompleted"; a cost detail acquisition step of acquiring cost detail data in which the project identifier, the cost item, and the cost are set, when the cost input data in which the project identifier, the cost item, and the cost are set is inputted; an unfinished journal entry creating step for creating unfinished journal entry data based on the cost detail data, the cost being an amount, the debit account being an unfinished cost item, and the credit account being a current liability item; a sales acquisition step of acquiring project sales data in which the project identifier and the sales amount for each contract are set; an updating step of updating the sales completion classification set in the order record included in the project order status data from incomplete to completed by comparing the contract amount set in the contract data linked to the project of the project identifier set in the project sales data with the sales amount set in the project sales data; a completion journal entry creation step for creating completion transfer journal entry data based on the cost detail data in which the project identifier set in the project order status data in which the sales completion classification has been updated to "completed" is set, with the cost as an amount, and with the debit account item being the completed account of the cost item and the credit account item being the incomplete account of the cost item; A project-specific income and expenditure management program to carry out the above.

Citation Information

Patent Citations

  • Construction work management system, construction work management method, and construction work management program

    JP2006072547A

  • Accounting processing apparatus and its program for construction business

    JP2006127295A

  • Project accounting management device, project accounting management method, and project accounting management program

    JP2017091508A