JP7853199B2 - Common expense allocation processing device, common expense allocation processing method, and common expense allocation processing program - Google Patents

Description

This invention relates to a common expense allocation processing device, a common expense allocation processing method, and a common expense allocation processing program.

In today's industries, such as construction, IT (Information Technology), and advertising, it's necessary to allocate common costs for each project to each contract unit within that project. Traditionally, common costs were recognized for each project, and then allocated according to a specified allocation standard, with each contract within the project being identified.

Furthermore, the accounting processing system disclosed in Patent Document 1 (Japanese Patent Publication No. 2022-117133) uses a journal entry means to assign at least a first expense item, a second expense item, and a third expense item to multiple items of accounting detail data based on the names of the items. The apportionment means apportions the amount of each item to which the first expense item is assigned to each item to which the second expense item and/or third expense item is assigned, based on the apportionment rate of the apportionment amount ratio, and outputs the apportionment result amounts. The proposed means proposes one or more candidate detailed information items for each item from which the apportionment result has been output, based at least on the name of the item. This enables increased efficiency in accounting processing, standardization of work, and improved quality.

Japanese Patent Publication No. 2022-117133

However, when common costs are recognized for each project and allocated according to designated allocation criteria, as in the conventional method, there are problems such as inappropriate allocation for each contract, resulting in common costs being recorded for contracts that should not be subject to such allocation, and making accurate budget and actuals management for each contract difficult.

This invention has been made in view of the above-mentioned problems, and aims to provide a common cost allocation processing device, a common cost allocation processing method, and a common cost allocation processing program that enable accurate budget-to-actual management by appropriately allocating common costs for each contract.

To solve the above-mentioned problems and achieve the objective, the common cost allocation processing device according to the present invention includes: an acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common costs set for the project; a calculation unit that calculates the planned allocated on-site common costs, which are expenses equivalent to the planned allocation rate of the incurred direct costs for each contract; and a data generation unit that generates project cost detail data including the incurred direct costs for each contract and the planned allocated on-site common costs corresponding to the calculated incurred direct costs for each contract. The data generation unit generates journal entry data in which the planned allocated on-site common costs are debited as work-in-progress expenses and the planned allocated on-site common costs are credited as cost allocation transfers.

Furthermore, in order to solve the above-mentioned problems and achieve the objective, the common cost allocation processing method of the common cost allocation processing device according to the present invention includes an acquisition step in which an acquisition unit acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common costs set for the project; a calculation step in which a calculation unit calculates the planned allocated on-site common costs, which are expenses equivalent to the planned allocation rate of the incurred direct costs for each contract; and a data generation step in which a data generation unit generates project cost detail data including the incurred direct costs for each contract and the planned allocated on-site common costs corresponding to the calculated incurred direct costs for each contract. In the data generation step, journal entry data is generated in which the planned allocated on-site common costs are debited as work-in-progress expenses and the planned allocated on-site common costs are credited as cost allocation transfers.

Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the common cost allocation processing program according to the present invention functions as follows: an acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common costs set for the project; a calculation unit that calculates the planned allocated on-site common costs, which are expenses equivalent to the planned allocation rate of the incurred direct costs for each contract; and a data generation unit that generates project cost detail data including the incurred direct costs for each contract and the planned allocated on-site common costs corresponding to the calculated incurred direct costs for each contract . The data generation unit generates journal entry data in which the planned allocated on-site common costs are debited as work-in-progress expenses and the planned allocated on-site common costs are credited as cost allocation transfers.

This invention enables accurate budget-versus-actual management by appropriately allocating common costs for each contract.

Figure 1 is a block diagram showing the hardware configuration of the common expense allocation processing device according to the embodiment. Figure 2 shows the relationship between a project and a contract. Figure 3 shows an example of a planned allocation rate set for a project. Figure 4 shows an example of on-site common costs calculated for each contract based on the predetermined allocation rate set for the project. Figure 5 shows an example of direct costs recorded for each contract and actual on-site common expenses incurred. Figure 6 shows an example of the planned allocation process for on-site common expenses. Figure 7 shows an example of journal entry data for on-site common expenses that have been allocated according to a predetermined schedule. Figure 8 shows an example of an indirect cost variance, which is the difference between the actual on-site common costs incurred and the on-site common costs that were allocated according to a predetermined plan. Figure 9 shows an example of a departmental planned allocation rate master where planned allocation rates are set. Figure 10 shows an example of the format for project basic data. Figure 11 shows an example of a project order data format. Figure 12 shows an example of basic project data. Figure 13 shows an example of project order data for construction 001 with contract information entered. Figure 14 shows an example of project order data for construction 002 with contract information entered. Figure 15 shows an example of project order data for construction 003 with contract information entered. Figure 16 shows an example of project order data for construction 004 with contract information entered. Figure 17 shows an example of budget data for construction project 001 for which budget input has been performed. Figure 18 shows an example of budget data for construction project 002 for which budget input has been performed. Figure 19 shows an example of budget data for construction project 003 for which budget input has been performed. Figure 20 shows an example of procurement data for construction project 001 for which procurement input has been performed. Figure 21 shows an example of procurement data for construction project 002, for which procurement input has been performed. Figure 22 shows an example of procurement data for construction project 003, for which procurement input has been performed. Figure 23 shows an example of procurement data for common site expenses. Figure 24 shows the main material costs and planned allocated site common costs for each construction project. Figure 25 shows an example of journal entry data generated based on the results of the planned allocation process. Figure 26 shows an example of the output of the construction ledger.

The following describes in detail, based on the drawings, a common expense allocation processing device that is an embodiment of the present invention. However, the present invention is not limited to the following embodiments.

(Hardware configuration)
As shown in Figure 1, the common expense allocation processing device 1 of this embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 may be a display unit such as a monitor device (including a household television), a speaker device, etc. The input device 6 may be a keyboard device, a mouse device, a microphone device, etc., or a monitor device that works in cooperation with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network such as a wide-area network such as the Internet or a private network such as a LAN (Local Area Network).

The memory unit 2 can use, for example, a ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive). The memory unit 2 stores a common cost allocation processing program that appropriately allocates common costs for each contract of a given project, enabling accurate budget-to-actual management.

Furthermore, the memory unit 2 stores the departmental planned allocation rate master 11. The memory unit 2 also stores project basic data, project order data, budget data, procurement data, project cost detail data, journal entry data, and indirect cost variance data, as described later.

(Functional configuration of the common expense allocation processing device)
Next, the control unit 3 executes the common expense allocation processing program stored in the storage unit 2, and functions as an acquisition unit 21, calculation unit 22, data generation unit 23, display control unit 24, storage control unit 25, and communication control unit 26, as shown in Figure 1.

The acquisition unit 21 acquires, for example, the incurred direct costs recorded as costs for one or more construction contracts performed in a single project involving construction work at a specified site, and the planned allocation rate for site common expenses set for the project.

The calculation unit 22 calculates the planned allocation site common expenses, which are the amount of expenses corresponding to the planned allocation rate of the direct costs incurred for each contract.

The data generation unit 23 generates project cost detail data, including the direct costs incurred for each contract and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each contract.

Furthermore, the data generation unit 23 generates journal entry data where the planned allocated site common expenses are debited as work-in-progress expenses, and the planned allocated site common expenses are credited as cost allocation transfers.

Furthermore, the calculation unit 22 calculates the amount of indirect cost variance, which is the difference between the actual on-site common costs incurred and the total amount of planned allocated on-site common costs for each contract. The data generation unit 23 generates indirect cost variance data showing the calculated amount of indirect cost variance.

The display control unit 24 displays the cost detail data, journal entry data, and indirect cost variance data generated by the data generation unit 23 via the output device 7, which is an example of a display unit. The storage control unit 25 stores the cost detail data, journal entry data, and indirect cost variance data generated by the data generation unit 23 in the storage unit 2. The communication control unit 26 records the journal entry data generated by the data generation unit 23 into the accounting system of a server device on the network connected to the communication interface unit 4. Note that the journal entry data may also be recorded in an accounting system provided within the storage unit 2.

(Operation overview)
Next, we will explain the general operation of the common expense allocation processing device 1 having the above configuration. The terms used here have the following meanings.

Site: Agreement with the project System screen: Input basic construction information Table name: Project basic data Construction: Example of a contract System screen: Input contract information Table name: Project order header, Project order details Direct cost: System screen: Input purchases Indirect cost: Site common expenses Project: System screen: Input basic project information Contract: Agreement with contract information

First, a "project" refers to a project in fields such as construction, IT (Information Technology), or advertising, while a "contract" is one or more contracts performed within that project. As shown in Figure 2, the relationship between a project and contracts is such that, for example, a project might include multiple contracts, such as Contract 001 to Contract 003. The contract amount for each contract is entered by the business operator when the contract information is entered. In the example in Figure 2, the contract amounts for Contract 001 to Contract 003 are "1 million yen," "2 million yen," and "3 million yen," respectively. Note that at the time of entering this contract information, the common site expenses 004 are entered as "0 yen."

Next, the planned allocation rate for common expenses for the project is registered in the Department Planned Allocation Rate Master 11, as shown in Figure 3. Figure 3 shows an example where a planned allocation rate of "5%" is set for the XX project.

Next, as shown in Figure 4, an execution budget is registered for each contract. In the example in Figure 4, the execution budgets for contracts 001 to 003 are "840,000 yen," "1,680,000 yen," and "2,520,000 yen," respectively. Of these execution budgets, the breakdown of the "840,000 yen" budget for contract 001 is "800,000 yen" for direct costs and "800,000 yen x 5% = 40,000 yen" for on-site common expenses. Similarly, the breakdown of the "1,680,000 yen" budget for contract 002 is "1,600,000 yen" for direct costs and "1,600,000 yen x 5% = 80,000 yen" for on-site common expenses. Likewise, the breakdown of the "2,520,000 yen" budget for contract 003 is "2,400,000 yen" for direct costs and "2,400,000 yen x 5% = 120,000 yen" for on-site common expenses.

Next, as shown in Figure 5, costs are accounted for for each contract. The example in Figure 5 shows that "400,000 yen" is accounted for as direct cost for contract 001, "1,000,000 yen" for contract 002, and "2,000,000 yen" for contract 003. Furthermore, Figure 5 shows an example where "300,000 yen" was incurred as site-wide common expenses, and this "300,000 yen" was accounted for as direct cost of site-wide common expenses.

Next, as shown in Figure 6, site-wide common costs are allocated using cost accounting. As shown in Figure 6, in the case of contract 001, the incurred direct costs are "400,000 yen," so "400,000 yen x 5% = 20,000 yen" is allocated as site-wide common costs. Similarly, in the case of contract 002, the incurred direct costs are "1,000,000 yen," so "1,000,000 yen x 5% = 50,000 yen" is allocated as site-wide common costs. Similarly, in the case of contract 003, the incurred direct costs are "2,000,000 yen," so "2,000,000 yen x 5% = 100,000 yen" is allocated as site-wide common costs.

Next, as shown in Figure 7, journal entries are generated for the planned and actual on-site common expenses allocated per contract. For the planned and allocated on-site common expenses, a journal entry is generated with a debit to work-in-progress expenses and a credit to cost allocation transfer. For the actual on-site common expenses, a journal entry is generated with a debit to on-site common expenses and a credit to accounts payable.

Next, as shown in Figure 8(a), the total amount of site-wide common expenses allocated to contracts 001 to 003 is "170,000 yen" in the debit side of the journal entry data for work-in-progress expenses. Also, as shown in Figure 8(c), the total amount of site-wide common expenses allocated to contracts 001 to 003 is "170,000 yen" in the credit side of the journal entry data for cost allocation transfers. In contrast, in this example, as shown in Figure 8(b), the actual site-wide common expenses incurred were "300,000 yen".

Therefore, as shown in Figures 8(b) and 8(c), the total amount of planned allocated on-site common expenses, "170,000 yen," is subtracted from the actual on-site common expenses incurred, "300,000 yen" (300,000 yen - 170,000 yen = 130,000 yen), resulting in an indirect cost variance of "130,000 yen." This indirect cost variance is recorded as an accounting item.

Here, Figure 9 illustrates the departmental planned allocation rate master 11 in which the aforementioned planned allocation rates are set. As shown in Figure 9, the departmental planned allocation rate master 11 stores the department code, cost classification type, allocation rate, allocation project code, allocation project cost account, accrual basis classification, and planned allocation classification.

The cost classification type is the cost classification that displays the planned allocation amount. The example in Figure 9 shows an example where the planned allocation amount is specified to be displayed under the cost classification "4: Direct Costs (Expenses)". As an example, a planned allocation rate of "5%" is set. If a planned allocation rate is not specified in the project, "Adopted" is set for this allocation rate.

The allocated project code and allocated project cost item are expense items that display the planned allocated amount, respectively. The example in Figure 9 shows an example where the planned allocated amount is specified as "Field Common Costs." The accrual basis category is the item used to calculate the planned allocation rate. The example in Figure 9 shows an example where "0: Cost" is set as the accrual basis category. The planned allocation category specifies whether the planned allocation of common costs is calculated on a project basis or on a departmental basis. In the example in Figure 9, it is set to "1: By Project," meaning the planned allocation of common costs is calculated on a project basis.

Furthermore, the common expense allocation processing device 1 of this embodiment can also calculate the planned allocation of common expenses on a departmental basis by setting "2: Departmental" to this planned allocation category.

(Specific actions)
Next, the operation of the common cost allocation processing device 1 of the embodiment will be explained using a specific example. For the purposes of this explanation, the project will be assumed to be a construction project, such as "Air Conditioning Work for XX Building," and will include multiple construction works as an example of a contract. However, the project could also be an IT (Information Technology) project or an advertising project, etc.

First, Figure 10 shows an example of the format of the project basic data generated by inputting the basic construction information. As shown in Figure 10, the project basic data consists of the project number, project name, customer code, person in charge code, start date, end date, and the aforementioned planned allocation rate.

Furthermore, Figure 11 shows an example of a format for project order data generated by inputting contract information for each construction project. Figure 11(a) shows the header data (project order header data), and Figure 11(b) shows the detail data (project order detail data).

The project order header data shown in Figure 11(a) includes project number, order number, accounting year and month, customer code, invoice sales amount, invoice sales consumption tax amount, invoice cost amount, and invoice gross profit amount, etc.

The project order details data shown in Figure 11(b) includes the order number, order line number, product code, product name, receivable account classification, consumption tax rate classification, quantity ordered, sales price, sales amount, sales consumption tax amount, cost per unit, cost amount, and gross profit amount, etc.

Next, the common expense allocation processing device 1 of this embodiment, based on the common expense allocation processing project stored in the storage unit 2, has the control unit 3 execute the following steps.

Step S1 → Process to generate project basic data based on the entered basic construction information Step S2 → Process to generate project order data based on the entered contract information for each construction Step S3 → Process to generate budget data based on the entered execution budget for each construction Step S4 → Process to generate purchase data based on purchase input Step S5 → Process to calculate the planned allocation of common costs based on the planned allocation rate Step S6 → Process to generate journal entry data Step S7 → Process to generate indirect cost variance data

In other words, in step S1, the acquisition unit 21 acquires the basic construction information entered by the business operator via the input device 6, and the data generation unit 23 generates the project basic data shown in Figure 12. As shown in Figures 10 and 12, the project basic data includes a planned allocation rate, such as "5%".

Next, in step S2, the acquisition unit 21 acquires the contract information for each construction project entered by the business operator via the input device 6, and the data generation unit 23 generates project order data for each construction project, as shown in Figures 13 to 16. Figures 13(a) and 13(b) show the project order header data and project order detail data for construction project 001, which has been automatically assigned the order number "JY0001," with a sales amount of "1 million yen."

Furthermore, Figures 14(a) and 14(b) show the project order header data and project order detail data for construction project 002, which was automatically assigned the order number "JY0002," with a sales amount of "2 million yen."

Furthermore, Figures 15(a) and 15(b) show the project order header data and project order detail data for construction project 003, which was automatically assigned the order number "JY0003," with a sales amount of "3 million yen."

In contrast, Figures 16(a) and 16(b) show the project order header data and project order detail data for on-site common expenses. In the example in Figure 16, the project order data for on-site common expenses is automatically assigned the order number "JY0004". Since no on-site common expenses were incurred at the time of this contract information entry, the sales amount is registered as "0 yen".

Next, in step S3, the acquisition unit 21 acquires the execution budget entered for each project by the business operator via the input device 6, and the data generation unit 23 generates budget data for each project as shown in Figures 17 to 19. This budget data consists of budget header data shown in Figures 17(a), 18(a), and 19(a), and budget detail data shown in Figures 17(b), 18(b), and 19(b).

Figures 17(a) and 17(b) show the budget data for construction project 001 with order number "JY0001," where the budget amount is set at "840,000 yen." The breakdown of this "840,000 yen" budget is as follows: "800,000 yen" is for "main material costs," and "800,000 yen x 5% planned allocation rate = 40,000 yen" is for "site common expenses."

Figures 18(a) and 18(b) show the budget data for construction project 002 with order number "JY0002," where the budget amount is set at "1.68 million yen." The breakdown of this "1.68 million yen" budget is as follows: "1.6 million yen" is for "main material costs," and "1.6 million yen x 5% planned allocation rate = 80,000 yen" is for "site common expenses."

Figures 19(a) and 19(b) show the budget data for construction project 003 with order number "JY0003," where the budget amount is set at "2.52 million yen." The breakdown of this "2.52 million yen" budget is as follows: "2.4 million yen" for "main material costs" and "2.4 million yen x 5% planned allocation rate = 120,000 yen" for "site common expenses."

Next, in step S4, the acquisition unit 21 acquires the purchase amount entered for each construction project by the business operator via the input device 6, and the data generation unit 23 generates purchase data for each construction project as shown in Figures 20 to 23. This purchase data consists of purchase slip header data shown in Figures 20(a), 21(a), 22(a), and 23(a), and purchase detail data shown in Figures 20(b), 21(b), 22(b), and 23(b).

Figures 20(a) and 20(b) show the procurement data for construction project 001 with order number "JY0001," where the procurement amount for major materials is recorded as "400,000 yen."

Figures 21(a) and 21(b) show the procurement data for construction project 002 with order number "JY0002," where the procurement amount for major materials is recorded as "1,000,000 yen."

Figures 22(a) and 22(b) show the procurement data for construction project 003 with order number "JY0003," where the procurement amount for major materials is recorded as "2 million yen."

In contrast, Figures 23(a) and 23(b) show procurement data for site-wide common expenses with order number "JY0004," where "300,000 yen" is recorded as the procurement amount for major material costs.

Next, in step S5, the calculation unit 22 performs the calculation of the planned allocation of common costs based on the planned allocation rate, as shown in Figure 24. Specifically, first, the acquisition unit 21 acquires the direct costs of each construction project, as shown in Figure 24(a), and also acquires the planned allocation rate (in this example, "5%") set in the departmental planned allocation rate master 11, as shown in Figure 24(b).

The calculation unit 22 calculates the planned allocation amount for each construction project, as shown in Figure 24(c), by performing the following calculations based on the direct costs and planned allocation rates for each project.

Direct cost aggregation subquery cost amount × Planned allocation rate from basic construction information ÷ 100

Once the planned allocation amount is calculated in this way, the data generation unit 23 generates project cost detail data including the target month, project number, order number, subject (project name), cost account category, and amount, as shown in Figure 24(c). At this time, the data generation unit 23 generates project cost detail data in which the calculated planned allocation amount is recorded as a direct expense using the cost items (allocated project type code, allocated project cost account) set in the departmental planned allocation rate master 11, as shown in Figure 24(c).

Next, in step S6, the data generation unit 23 generates journal entry data for each construction project and site common expenses, as illustrated in Figures 25(a) to 25(d), based on the results of this planned allocation process.

Of these, Figure 25(a) shows the journal entry data for construction project 001 with order number "JY0001". The data generation unit 23 generates journal entry data for the main material cost of "400,000 yen," with a debit of "400,000 yen" for uncompleted construction main material costs and a credit of "400,000 yen" for "Construction Accounts Payable." The data generation unit 23 also generates journal entry data for the site common expenses of "20,000 yen," with a debit of "20,000 yen" for uncompleted construction expenses and a credit of "20,000 yen" for "Cost Allocation Transfer."

Similarly, Figure 25(b) shows the journal entry data for construction project 002 with order number "JY0002". The data generation unit 23 generates a journal entry for the main material cost of "1 million yen," with a debit of "1 million yen" for uncompleted construction main material costs and a credit of "1 million yen" for "Construction Accounts Payable." The data generation unit 23 also generates a journal entry for the site common expenses of "50,000 yen," with a debit of "50,000 yen" for uncompleted construction expenses and a credit of "50,000 yen" for "Cost Allocation Transfer."

Similarly, Figure 25(c) shows the journal entry data for construction project 003 with order number "JY0003". The data generation unit 23 generates a journal entry for the main material cost of "2 million yen," with a debit of "2 million yen" for uncompleted construction main material costs and a credit of "2 million yen" for "Construction Accounts Payable." The data generation unit 23 also generates a journal entry for the site common expenses of "100,000 yen," with a debit of "100,000 yen" for uncompleted construction expenses and a credit of "100,000 yen" for "Cost Allocation Transfer."

In contrast, Figure 25(d) shows the journal entry data for site common expenses with order number "JY0004". The data generation unit 23 generates journal entry data for the actually incurred site common expenses of "300,000 yen," with a debit of "300,000 yen" for site common expenses and a credit of "300,000 yen" for "accounts payable for construction work."

The journal entry data generated in this manner is temporarily stored in the storage unit 2 by the storage control unit 25. At the timing of the business operator's operation, the communication control unit 26 records the data in the accounting system of a server device located on a wide-area network such as the Internet or a private network such as a LAN (Local Area Network). Alternatively, an accounting system could be installed in the storage unit 2, and the aforementioned journal entry data could be recorded in this system.

Furthermore, the display control unit 24 displays the project cost details data shown in Figure 24(c) via the output device 7, which is an example of a display unit. This allows the project operator to easily grasp and manage the costs and common expenses for each construction project.

Furthermore, the data generation unit 23 generates project ledger data for each project, as shown in Figure 26. Figure 26 is an image of the project ledger data for project 001. As shown in Figure 26, the project ledger data consists of project type, cost item, budget amount, current month's incurred costs, and direct expenses. In the case of project 001, "800,000 yen" is entered as the budget amount for major material costs, and "400,000 yen" is entered as the current month's incurred costs. In addition, "40,000 yen," calculated using the aforementioned "5%" planned allocation rate, is entered as the budget amount for site common expenses, and "20,000 yen" is entered as direct expenses.

The memory control unit 25 stores this construction ledger data in the memory unit 2. The display control unit 24 displays the construction ledger data for each construction project via the output device 7. This allows the operations operator to easily grasp and manage the costs and overhead for each construction project.

Next, the data generation unit 23 generates indirect cost variance data. As explained using Figure 8(a), the total amount of site common expenses allocated to projects 001 to 003 is "170,000 yen" in the debit side of the journal entry data for work-in-progress expenses. Also, as shown in Figure 8(c), the total amount of site common expenses allocated to projects 001 to 003 is "170,000 yen" in the credit side of the journal entry data for cost allocation transfers. In contrast, in this example, as shown in Figure 8(b), the actual site common expenses incurred are "300,000 yen".

Therefore, as shown in Figures 8(b) and 8(c), the data generation unit 23 calculates an indirect cost variance of "130,000 yen" by subtracting the total amount of planned allocated on-site common expenses, "170,000 yen," from the actual on-site common expenses incurred, "300,000 yen" (300,000 yen - 170,000 yen = 130,000 yen). Based on this calculation result, the data generation unit 23 generates indirect cost variance data showing an indirect cost variance of "130,000 yen."

The display control unit 24 displays the generated indirect cost variance data via the output device 7. This allows the operations operator to easily understand the difference between the actual on-site common expenses incurred and the total on-site common expenses calculated based on the planned allocation rate.

(Effects of the embodiment)
Common costs are considered indirect costs and allocated within departments based on actual costs. This allows for the recording of costs for each construction contract, and the recognition of work-in-progress and completed projects by accounting month. However, common costs vary from site to site, and allocating them within departments based on actual costs results in the inconvenience of not correctly reflecting common costs in each contract. Traditionally, the amount of common costs incurred was recognized for each project, and the project contracts were specified and allocated according to the designated allocation criteria. However, this method of allocation based on actual costs resulted in inappropriate allocation to each contract, such as common costs being recorded for contracts that should not be subject to them, making it difficult to recognize the revenue and expenses for each contract.

Furthermore, while a system for setting predetermined allocation rates for each department is conceivable, in reality, the amount of common expenses differs for each contract, which can lead to a large discrepancy between the predetermined allocation and the actual amount.

The common cost allocation processing device 1 of this embodiment sets a planned allocation rate on a site-by-site basis, calculates the planned allocation amount for each project contract, and records it as cost. Therefore, it is possible to allocate common costs appropriately for each contract, enabling accurate budget-to-actual management. Furthermore, the difference between the planned allocation amount and the actual amount (indirect cost variance) can be minimized.

Furthermore, since site-wide common costs largely consist of individual indirect costs at the site, the common cost allocation processing device 1 in this embodiment sets a predetermined allocation rate for each contract and performs calculations on the direct costs of each contract. Then, the actual cost of site-wide common costs is recognized in the execution budget, and the indirect cost variance is identified in accounting. This allows for appropriate recognition and management of the scope of responsibility for the actual cost of each contract and the scope of responsibility for the actual cost of each contract at the site.

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

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[Other embodiments]
In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of those described as being performed automatically can be performed manually, or all or part of those described as being performed manually can be performed automatically using known methods.

Furthermore, the processing procedures, control procedures, specific names, information including registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be modified at will unless otherwise specified.

Furthermore, regarding the common expense allocation processing device 1, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

For example, the processing functions of the common cost allocation processing device 1, particularly the control unit 3 and the various processing functions performed by the control unit 3, may be implemented entirely or partially by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the common cost allocation processing device 1 as needed. That is, a storage unit such as ROM or HDD stores a computer program that, in cooperation with the OS, gives instructions to the CPU and performs various processing. This computer program is executed by being loaded into RAM and, in cooperation with the CPU, constitutes the control unit 3.

Furthermore, the common expense allocation processing program of this common expense allocation processing device 1 may be stored on another server device connected to the common expense allocation processing device 1 via any network, and it is possible to download all or part of it as needed.

Furthermore, the common cost allocation processing program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM® (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disk), DVD (Digital Versatile Disk), and Blu-ray® Disc.

Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, standalone structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedure for reading the recording medium in the common cost allocation processing device 1 shown in the embodiment, as well as the installation procedure after reading, well-known configurations and procedures can be used.

The storage unit 2 comprises memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and web page files used for various processes and website provision.

Furthermore, the common cost allocation processing device 1 may be configured as a known personal computer device or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. The information processing device may also be implemented by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the illustration. All or part of the devices can be functionally or physically distributed and integrated in any unit, depending on various additions or functional loads. In other words, the above-described embodiments may be implemented in any combination, or the embodiments may be implemented selectively.

This invention is particularly suitable for applications in industries that manage revenue and expenses in projects such as construction, IT (Information Technology), events, or advertising.

1. Common expense allocation processing device 2. Storage unit 3. Control unit 4. Communication interface unit 5. Input/output interface unit 6. Input device 7. Output device 11. Departmental planned allocation rate master 21. Acquisition unit 22. Calculation unit 23. Data generation unit 24. Display control unit 25. Storage control unit 26. Communication control unit

Claims (6)

An acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project,
A calculation unit that calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
The system includes a data generation unit that generates cost detail data for the project, including the direct costs incurred for each of the aforementioned contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the aforementioned contracts.
The data generation unit generates journal entry data in which the predetermined allocated site common expenses are debited as work-in-progress expenses and the predetermined allocated site common expenses are credited as cost allocation transfers.
A common expense allocation processing device characterized by the following . An acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project,
A calculation unit that calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
The system includes a data generation unit that generates cost detail data for the project, including the direct costs incurred for each of the aforementioned contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the aforementioned contracts.
The calculation unit calculates the amount of indirect cost variance, which is the difference between the actual on-site common costs incurred in the project and the total amount of the planned allocated on-site common costs for each of the contracts.
The data generation unit generates indirect cost variance data showing the amount of the calculated indirect cost variance.
A common expense allocation processing device characterized by the following. The acquisition step involves the acquisition unit acquiring the incurred direct costs that are recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project.
The calculation unit performs a calculation step in which it calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
The data generation unit includes a data generation step that generates cost detail data for the project, which includes the direct costs incurred for each of the contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the contracts .
In the data generation step, journal entry data is generated in which the predetermined allocated site common expenses are debited as work-in-progress expenses and the predetermined allocated site common expenses are credited as cost allocation transfers.
A common expense allocation processing method for a common expense allocation processing device characterized by the following . The acquisition step involves the acquisition unit acquiring the incurred direct costs that are recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project.
The calculation unit performs a calculation step in which it calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
The data generation unit includes a data generation step that generates cost detail data for the project, which includes the direct costs incurred for each of the contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the contracts.
In the calculation step described above, the amount of the indirect cost variance is calculated, which is the difference between the actual on-site common costs incurred in the project and the total amount of the planned allocated on-site common costs for each of the aforementioned contracts.
The data generation step involves generating indirect cost variance data that shows the amount of the calculated indirect cost variance.
A common expense allocation processing method for a common expense allocation processing device characterized by the following. Computers,
An acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project,
A calculation unit that calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
It functions as a data generation unit that generates cost detail data for the project, including the direct costs incurred for each of the aforementioned contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the aforementioned contracts.
The data generation unit generates journal entry data in which the predetermined allocated site common expenses are debited as work-in-progress expenses and the predetermined allocated site common expenses are credited as cost allocation transfers.
A common expense allocation processing program characterized by the following. Computers,
An acquisition unit that acquires the incurred direct costs recorded as costs incurred for one or more contracts performed in a single project, and the planned allocation rate of on-site common expenses set for the said project,
A calculation unit that calculates the planned allocation site common expenses, which are expenses equivalent to the planned allocation rate of the direct costs incurred for each of the aforementioned contracts,
It functions as a data generation unit that generates cost detail data for the project, including the direct costs incurred for each of the aforementioned contracts and the planned allocated site common expenses corresponding to the calculated direct costs incurred for each of the aforementioned contracts.
The calculation unit calculates the amount of indirect cost variance, which is the difference between the actual on-site common costs incurred in the project and the total amount of the planned allocated on-site common costs for each of the contracts.
The data generation unit generates indirect cost variance data showing the amount of the calculated indirect cost variance.
A common expense allocation processing program characterized by the following.