JP7701411B2 - Accounting support device, accounting support method, and accounting support program - Google Patents

Description

The present invention relates to an accounting support device, an accounting support method, and an accounting support program.

When creating project end-of-life forecast data, it is necessary to centrally manage project contract information, budget information, various cost information linked to the project, and so on. However, there was an issue of the time and cost involved in reviewing end-of-life forecasts for each project while referring to budgets and cost information. There was also the issue of the cost of re-examining the end-of-life forecast to reflect any increases or decreases in budget or cost information after reviewing end-of-life forecasts and registering the data. Furthermore, if there was no system for easily reviewing project budgets and costs when they did not match, there was also the risk that control risks such as missed budgets could be overlooked.

JP 2022-27251 A JP 2021-140737 A

The object of the present invention is therefore to provide a new system that can reduce the burden of data registration by referencing budget and cost information for each project and automatically creating final forecast data, while also avoiding the risk of missing budget information.

In order to solve the above-mentioned problems and achieve the object, the accounting support device of the present invention is an accounting support device equipped with a control unit, the control unit comprising: a cost amount aggregation means for aggregating the accumulated cost amount up to the current month by order identification information and by cost item; a budget amount determination means for, if a corresponding budget amount exists for each order identification information and cost item, extracting the latest corresponding budget amount from the corresponding budget amounts and determining that the extracted budget amount is the current budget amount, and, if a corresponding budget amount does not exist, determining that 0 is the current budget amount; and a cost amount determination means for determining, according to a preselected method of determining the expected final amount, (1) a cost amount aggregation means for aggregating the accumulated cost amount up to the current month by order identification information and by cost item, The system is characterized by comprising: a final estimate determining means for determining the determined current budget amount as the final estimated amount for the current month, or (2) if there is no final estimated amount for the previous month, determining the current budget amount determined by the budget amount determining means as the final estimated amount for the current month, and if there is a final estimated amount for the previous month, determining the final estimated amount for the previous month as the final estimated amount for the current month; and a planned cost calculating means for calculating the future planned cost for the current month by subtracting the accumulated cost amount up to the current month compiled by the cost amount compiling means from the final estimated amount for the current month determined by the final estimated amount determining means for each order identification information and each cost item.

The accounting support device according to the present invention is also characterized in that the control unit includes a detail table update means for newly storing in the forecasted detail table a forecasted detail record including the final forecasted amount for the current month determined by the forecasted amount determination means, the future planned cost for the current month calculated by the planned cost calculation means, and the fiscal year and month, for each order identification information and each cost item, with the current month being the fiscal year and month.

The accounting support device according to the present invention is also characterized in that the control unit includes a hold determination means for extracting combinations of order identification information and cost items for which the cost amount calculation means has calculated a cumulative cost amount exceeding zero, where the current budget amount determined by the budget amount determination means is zero and the final forecast amount for the current month determined by the forecast amount determination means is zero, and determining that the order identification information corresponding to the extracted combination is unapproved or on hold.

The accounting support device according to the present invention is also characterized in that the hold determination means extracts combinations from the combinations in which the current budget amount determined by the budget amount determination means is 0, the final forecast amount for the current month determined by the forecast amount determination means is 0, and the combinations have a preselected cost item that is subject to hold determination, and determines that the order identification information corresponding to the extracted combination is unapproved or on hold.

The accounting support device according to the present invention is also characterized in that the control unit includes a check result output means for outputting a notification that there is order identification information that has been determined by the hold determination means to be unapproved or on hold.

The accounting support device according to the present invention is also characterized in that the control unit further includes a budget acceptance means for accepting budget amounts by order identification information and by cost item, and for accepting multiple budget amounts for the same order identification information and the same cost item.

The accounting support device according to the present invention further comprises a budget variance calculation means for calculating the budget variance for the current month by subtracting the final estimated amount for the current month determined by the estimated amount determination means from the current budget amount determined by the budget amount determination means, for each order identification information and each cost item, and the detail table update means newly stores in the estimated amount detail table a final estimated amount for the current month, the future planned cost for the current month, and the accounting year and month, as well as the budget variance for the current month calculated by the budget variance calculation means, for each order identification information and each cost item.

The accounting support device according to the present invention further comprises a change acceptance means for accepting an application for change of the final forecast amount in the forecast amount detail record including the latest accounting year and month stored in the forecast amount detail table by order identification information and by cost item, together with the order identification information, cost item, and change application amount, and the detail table update means updates the final forecast amount in the forecast amount detail record including the latest accounting year and month corresponding to the order identification information and cost item accepted by the change acceptance means to the change application amount accepted by the change acceptance means.

The accounting support method according to the present invention is an accounting support method executed in an accounting support device equipped with a control unit, and includes a cost amount aggregation step executed by the control unit, in which the cumulative cost amount up to the current month is aggregated by order identification information and by cost item, a budget amount determination step, in which, if there are corresponding budget amounts by order identification information and by cost item, the latest corresponding budget amount is extracted from the corresponding budget amounts and the extracted budget amount is determined to be the current budget amount, and if there is no corresponding budget amount, 0 is determined to be the current budget amount, and a budget amount determination step, in which, according to a preselected method for determining the expected final amount, (1) the budget amount determined by the budget amount determination step, by order identification information and by cost item The method includes a final estimate determination step in which the current budget amount determined in the budget amount determination step is determined to be the final estimated amount for the current month, or (2) if there is no final estimated amount for the previous month, the current budget amount determined in the budget amount determination step is determined to be the final estimated amount for the current month, and if there is a final estimated amount for the previous month, the final estimated amount for the previous month is determined to be the final estimated amount for the current month; and a planned cost calculation step in which, for each order identification information and each cost item, the cumulative cost amount up to the current month compiled in the cost amount compilation step is subtracted from the final estimated amount for the current month determined in the final estimated amount determination step to calculate the future planned cost for the current month.

The accounting support program according to the present invention is an accounting support program to be executed by an accounting support device having a control unit, and includes a cost amount aggregation step for tallying up the cumulative cost amount up to the current month by order identification information and by cost item to be executed by the control unit, a budget amount determination step for, if there is a corresponding budget amount by order identification information and by cost item, extracting the latest corresponding budget amount from the corresponding budget amounts and determining that the extracted budget amount is the current budget amount, and if there is no corresponding budget amount, determining that 0 is the current budget amount, and a budget amount determination step for, according to the order identification information and cost item according to a preselected method for determining the expected final amount, (1) the budget amount determination step (2) if there is no final forecast amount for the previous month, the current budget amount determined by the budget amount determination step is determined to be the final forecast amount for the current month, and if there is a final forecast amount for the previous month, the final forecast amount for the previous month is determined to be the final forecast amount for the current month; and (3) if there is no final forecast amount for the previous month, the current budget amount determined by the budget amount determination step is determined to be the final forecast amount for the current month; and (4) if there is a final forecast amount for the previous month, the final forecast amount for the previous month is determined to be the final forecast amount for the current month, the cumulative cost amount up to the current month calculated by the cost amount calculation step is subtracted from the final forecast amount for the current month determined by the estimated amount determination step by order identification information and by cost item, to calculate the future planned cost for the current month.

The system of the present invention references budget and cost information for each project and automatically creates final forecast data, reducing the burden of data registration and avoiding the risk of missing budget information.

FIG. 1 is a block diagram showing an example of the configuration of a PC 100 according to an embodiment. FIG. 2 is a diagram showing an example of the flow of information processing for automatically creating a landing prediction in one embodiment. FIG. 3 is a diagram illustrating an example of a project basic information master and a PJ cost item classification master according to an embodiment. FIG. 4 is a diagram illustrating an example of a project information table and a contract information table according to an embodiment. FIG. 5A is a diagram illustrating an example of a budget information table and a cost information table according to an embodiment. FIG. 5B is a diagram illustrating an example of a temporary work table according to one embodiment. FIG. 5C is a diagram showing an example of a landing prediction header table and a landing prediction detail table in one embodiment. FIG. 5D is a diagram illustrating an example of a check result notification screen according to an embodiment. FIG. 5E is a diagram showing an example of a landing prediction header table and a landing prediction detail table in one embodiment. FIG. 5F is a diagram showing an example of a landing prediction header table and a landing prediction detail table in one embodiment. FIG. 6A is a diagram illustrating an example of a budget information table and a cost information table according to an embodiment. FIG. 6B is a diagram illustrating an example of a temporary work table according to one embodiment. FIG. 6C is a diagram showing an example of a landing prediction header table and a landing prediction detail table in one embodiment. FIG. 6D is a diagram illustrating an example of a check result notification screen according to an embodiment. FIG. 7A is a diagram illustrating an example of a temporary work table according to one embodiment. FIG. 7B is a diagram showing an example of a landing prediction header table and a landing prediction detail table in one embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Configuration]
Here, an example of the configuration of a PC (personal computer) 100 according to this embodiment including the accounting support device of the present invention will be described with reference to Fig. 1. Note that the configuration of this embodiment is merely an example, and the present invention is not limited to being realized with the configuration of this embodiment. Also, in the following description of the configuration, duplicated explanations may be omitted.

Fig. 1 is a block diagram showing an example of the configuration of a PC 100. The PC 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108, and is communicatively connected to a server 200 (e.g., a web server, etc.) that stores various data (e.g., data stored in the storage unit 106, which may be described later) via a network 300 (e.g., the Internet, an intranet, a LAN (Local Area Network), etc.).

Each component of PC100 is connected to enable communication via any communication path.

Note that PC 100 may be a stationary type such as a desktop personal computer, or may be a portable type such as a notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

The control unit 102 is a CPU or the like that performs overall control of the PC 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various types of information processing based on these stored programs.

In terms of function and concept, the control unit 102 includes a calculation target identification unit 102a, a cost amount calculation unit 102b, a detail table update unit 102c, a budget amount determination unit 102d, a final estimated amount determination unit 102e, a planned cost calculation unit 102f, a budget variance calculation unit 102g, a reservation determination unit 102h, a check result output unit 102i, a change acceptance unit 102j, a budget acceptance unit 102k, etc.

The aggregation target specification unit 102a specifies the order identification information to be aggregated. The order identification information to be aggregated can be set in advance, and can be, for example, order identification information whose completion category is contract incomplete and whose approval status is contract approved. Such order identification information can be extracted from a contract information table that stores the completion category, approval status, etc. along with the order identification information.

The cost amount tallying unit 102b tallys up the cumulative cost amount up to the current month by order identification information and by cost item. The cost amount tallying unit 102b can tally up the cumulative cost amount up to the current month from the cost amounts registered by accounting year and month in the cost information table. The cost amount tallying unit 102b tallys up the cost amount by accounting year and month by order identification information and by cost item based on the voucher information that becomes the cost, such as purchase information stored in the voucher information database, and stores the cost amount in the cost information table. The cost amount tallying unit 102b targets the cost amount tallying unit 102b for the cost amount corresponding to the order identification information identified by the target identification unit 102a.

If a corresponding budget amount exists for each order identification information and cost item, the budget amount determination unit 102d extracts the latest corresponding budget amount from the corresponding budget amounts and determines that the extracted budget amount is the current budget amount, and if no corresponding budget amount exists, determines that 0 is the current budget amount.

The budget amount determination unit 102d can determine whether a corresponding budget amount exists by checking whether the corresponding budget amount is stored in the budget information table, and whether the latest corresponding budget amount is identified by change identification information for identifying whether the budget amount is new or old.

The budget amount determination unit 102d determines the budget amount for the order identification information identified by the target identification unit 102a. The budget amount determination unit 102d determines the budget amount for the accounting month and year prior to the current month, and for the budget amount whose approval status is "approved."

The budget reception unit 102k receives budget amounts by order identification information and by cost item, and can receive budget amounts multiple times for the same order identification information and the same cost item. The budget reception unit 102k registers the received budget amounts in the budget information table. When registering a budget amount in the budget information table, the budget reception unit 102k registers the budget amount together with change identification information for identifying whether the budget amount is new or old.

The estimated final amount determination unit 102e, depending on the preselected estimated final amount determination method, determines, for each order identification information and each cost item, (1) the current budget amount determined by the budget amount determination unit 102d as the estimated final amount for the current month, or (2) if there is no estimated final amount for the previous month, determines the current budget amount determined by the budget amount determination unit 102d as the estimated final amount for the current month, and if there is an estimated final amount for the previous month, determines the estimated final amount for the previous month as the estimated final amount for the current month.

The estimated landing amount determination unit 102e can determine whether a final estimated landing amount exists for the previous month by checking whether a final estimated landing amount corresponding to the fiscal year and month of the previous month is stored in the estimated landing amount details table.

The planned cost calculation unit 102f calculates the future planned cost for the current month by subtracting the accumulated cost amount up to the current month, which has been collected by the cost amount collection unit 102b, from the final estimated cost for the current month, which has been determined by the estimated cost determination unit 102e, by order identification information and by cost item.

The budget variance calculation unit 102g calculates the budget variance for the current month by subtracting the final estimated amount for the current month determined by the estimated amount determination unit 102e from the current budget amount determined by the budget amount determination unit 102d, by order identification information and by cost item.

The detail table update unit 102c stores new forecast detail records in the forecast detail table by order identification information and by cost item, with the current month as the accounting month, including the final forecast amount for the current month determined by the forecast amount determination unit 102e, the future planned cost for the current month calculated by the planned cost calculation unit 102f, and the accounting month.

The forecasted arrival detail records stored in the forecasted arrival detail table by the detail table update unit 102c may include the current budget amount determined by the budget amount determination unit 102d, the accumulated cost amount up to the current month calculated by the cost amount calculation unit 102b, and the budget variance for the current month calculated by the budget variance calculation unit 102g.

The change acceptance unit 102j accepts requests for changes to the final forecast amount in the forecasted arrival detail record including the latest accounting year and month stored in the forecasted arrival detail table, by order identification information and cost item, along with the order identification information, cost item, and change request amount.

The detail table update unit 102c updates the final forecast amount in the forecast amount detail record that includes the order identification information and the latest accounting year and month corresponding to the cost item accepted by the change acceptance unit 102j to the change application amount accepted by the change acceptance unit 102j.

The hold determination unit 102h extracts combinations of order identification information and cost items for which the cost amount calculation unit 102b has tallied a cumulative cost amount exceeding zero, where the current budget amount determined by the budget amount determination unit 102d is zero and the final estimated amount for the current month determined by the estimated amount determination unit 102e is zero, and determines that the order identification information corresponding to the extracted combination is unapproved or on hold.

When there are preselected cost items that are subject to a hold judgment and cost items that are not subject to a hold judgment, the hold judgment unit 102h extracts combinations of order identification information and cost items for which a cumulative cost amount exceeding 0 has been accumulated by the cost amount accumulation unit 102b, in which the current budget amount determined by the budget amount determination unit 102d is 0, the final forecast amount for the current month determined by the forecast amount determination unit 102e is 0, and which have preselected cost items that are subject to a hold judgment, and judges the order identification information corresponding to the extracted combination to be unapproved or on hold.

The reservation determination unit 102h can identify whether a cost item is subject to reservation determination based on the project cost item classification master in which the reservation determination target classification of whether the cost item is subject to reservation determination or not is registered in advance for each cost item.

The check result output unit 102i outputs a notification that there is order identification information that the hold determination unit 102h has determined to be unapproved or on hold. The notification output by the check result output unit 102i may be in a form that includes a notification as to whether there is order identification information that the hold determination unit 102h has determined to be unapproved or on hold.

The check result output unit 102i can also output a notification that there is order identification information whose contract approval status is unapproved or pending. The notification output by the check result output unit 102i may be in a form that includes a notification of whether there is order identification information whose contract approval status is unapproved or pending.

The check result output unit 102i can also output a notification that there is order identification information whose budget approval status is budget unapproved or budget pending. The notification output by the check result output unit 102i may be in a form that includes a notification of whether there is order identification information whose budget approval status is budget unapproved or budget pending.

The communication interface unit 104 communicatively connects the PC 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, 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.

The memory unit 106 conceptually includes a project basic information master memory unit 106a, a project cost item classification master memory unit 106b, a project information table memory unit 106c, a contract information table memory unit 106d, a budget information table memory unit 106e, a cost information table memory unit 106f, a final forecast header table memory unit 106g, a final forecast detail table memory unit 106h, etc.

Project basic information master storage unit 106a stores project basic information master. The project basic information master has a method for determining the estimated final amount registered, and the method is selected and set in advance before automatic creation of the estimated final amount. The estimated final amount determination method may include at least two types of estimated final amount determination methods: "Previous month's estimated final amount", which determines the current budget amount as the estimated final amount for the current month if there is no estimated final amount for the previous month, and determines the previous month's estimated final amount as the estimated final amount for the current month if there is an estimated final amount for the previous month, and "Latest budget", which determines the current budget amount as the estimated final amount for the current month regardless of whether there is an estimated final amount for the previous month.

The project cost item classification master storage unit 106b stores the project cost item classification master. In the project cost item classification master, a reservation judgment target category is registered for each cost item, indicating whether the cost item is subject to reservation judgment or not, and the reservation judgment target category is selected and set in advance for each cost item before automatically creating a final forecast.

The project information table storage unit 106c stores a project information table. The project information table stores project information such as project identification information and project name for each project. Project identification information is assigned to each project and is composed of, for example, a unique number or symbol.

The contract information table storage unit 106d stores a contract information table. The contract information table stores contract information for each order, such as project identification information, order identification information, order name (contract name), fiscal year and month, contract period, contract amount, contract approval status, and contract completion category. Order identification information is assigned to each order (contract) and is composed of, for example, unique numbers or symbols. One project includes one or more orders. Therefore, there are one or more order identification information corresponding to one project identification information.

The budget information table storage unit 106e stores a budget information table. The budget information table stores budget information such as project identification information, order identification information, budget amount change identification information, accounting year and month, cost item, budget amount, and budget approval status, organized by order identification information and cost item. The budget information table can store multiple budget amounts for the same order identification information and the same cost item, and the change identification information is information for identifying whether the information is new or old, and is composed of, for example, unique numbers or symbols.

The cost information table storage unit 106f stores a cost information table. The cost information table stores cost information such as cost accounting identification information, project identification information, order identification information, accounting year and month, cost item, and cost amount by order identification information and cost item. Cost accounting identification information is assigned to one cost accounting, and is composed of, for example, a unique number or symbol.

The arrival forecast header table storage unit 106g stores an arrival forecast header table. The arrival forecast header table stores, for each order identification information, an arrival forecast header record including the approval status of the final arrival forecast, along with project identification information, order identification information, accounting year and month, and final arrival forecast creation category.

The estimated arrival details table storage unit 106h stores an estimated arrival details table. The estimated arrival details table stores estimated arrival details records including the final estimated arrival amount for the current month and the future planned costs for the current month, along with project identification information, order identification information, accounting year and month, and cost items, sorted by order identification information and cost item, and the estimated arrival details records may further include the current budget amount, the accumulated cost amount up to the current month, and the budget variance for the current month.

The input/output interface unit 108 is connected to an input device 400 and an output device 500. The output device 400 includes display devices such as displays and projectors, audio devices such as speakers, printing devices such as printers, as well as devices that allow downloading in data file format. The data file format may be a file format known in the field, such as PDF, CSV, document files, spreadsheet files, text files, etc. The input device 500 may include a keyboard, mouse, and microphone, as well as a monitor that cooperates with a mouse to realize a pointing device function.

2. Specific Examples
Hereinafter, using a specific example, the information processing for automatically creating a forecast result by the accounting support device according to the present invention and the information processing when applying for a change to the final forecast result amount after the automatic creation of the forecast result will be described.

Figure 2 shows the flow of information processing for automatically creating landing predictions in this specific example.

The aggregation target specification unit 102a specifies the order number (i.e., order identification information) to be aggregated (S01), the cost amount aggregation unit 102b aggregates the accumulated cost amount up to the current month by order number and by project cost item classification (i.e., cost item) (S02), and the budget amount determination unit 102d determines the current budget amount (S03).

When the automatic forecast creation category (i.e., forecast amount determination method) is preset to "previous month's forecast" (S04-YES) and a final forecast amount for the previous month exists (S05-YES), the final forecast amount determination unit 102e determines the previous month's final forecast amount as the final forecast amount for the current month by order number and project cost item category (S06a).

On the other hand, if the automatic final forecast creation category is preset to "previous month's final forecast" (S04-YES), but there is no final forecast amount for the previous month (S05-NO), or if the automatic final forecast creation category is preset to "latest budget" (S04-NO), the final forecast amount determination unit 102e determines the current budget amount by order number and project cost item category as the final forecast amount for the current month (S06b).

The planned cost calculation unit 102f calculates the future planned costs for the current month by order number and by project cost item category (S07), and the budget variance calculation unit 102g calculates the budget variance for the current month (S08).

If there is a temporary work record with a budget amount of 0 and a final estimated amount of 0 among the temporary work records with a cumulative cost amount exceeding 0 (S09-YES), the hold determination unit 102h determines the approval status for the order number held by this temporary work record to be "hold" (estimated amount hold), and determines the approval status for the other order number "JU001" to be "approved" (estimated amount approved) (S10a).

On the other hand, if there are no temporary work records with a budget amount of 0 and a final estimated amount of 0 among the temporary work records W11-W14/W16 whose accumulated cost amount exceeds 0 (S09-NO), the reservation determination unit 102h determines that the approval status for all order numbers "JU001" and "JU002" is "Approved" (estimated amount approved) (S10b).

The check result output unit 102i outputs the judgment result (check result notification screen) (S11).

Figure 3 shows the project basic information master and project cost item classification master in this specific example. In the project basic information master in this specific example, three types of automatic forecast creation classifications (method of determining the final forecast amount) are registered: "0 (not automatically created)", "1 (last month's forecast)", and "2 (latest budget)". "0 (not automatically created)" is a setting that does not implement automatic creation of the final forecast at all. In the project cost item classification master in this specific example, four project cost item classifications, "material costs", "outsourcing costs", "labor costs", and "expenses", and the corresponding reservation registration classifications at the time of automatic planned cost creation (reservation judgment target classifications) of "0: not subject to reservation judgment" or "1: subject to reservation judgment" are registered by project cost item classification.

Figure 4 shows the project information table and contract information table in this specific example. The project information table in this specific example stores project information records that store the project number (i.e., project identification information) and the corresponding project name for each project. The contract information table in this specific example stores contract information that stores the project number, order number (i.e., order identification information), contract name, fiscal year and month, contract period, contract amount, approval status, and completion category for each order number.

Figures 5A and 6A are diagrams showing the budget information table and cost information table in this specific example. Figure 5A shows the budget information table, cost information table, and cost information table for the first month after the start of automatic creation of a final forecast (April 2023), and Figure 6A shows the budget information table, cost information table, and cost information table for the month after the start of automatic creation of a final forecast (May 2023).

In this specific example, the budget information table stores the project number, order number, number of changes (i.e., change identification information), accounting year and month, project cost item category, budget amount, and approval status, sorted by order number (i.e., order identification information) and by project cost item category (i.e., cost item). In this specific example, the contract information table stores the contract information records, sorted by order number and by project cost item category, that store the cost accounting number, project number, order number, accounting year and month, project cost item category, and cost amount.

Figures 5B, 6B, and 7A are diagrams showing temporary work tables in this specific example. Figure 5B shows a temporary work table for the first month (April 2023) after automatic creation of a landing forecast begins, Figure 6B shows a temporary work table for the month after (May 2023) after automatic creation of a landing forecast begins when "Previous month's landing forecast" is selected, and Figure 7A shows a temporary work table for the month after (May 2023) after automatic creation of a landing forecast begins when "Latest budget" is selected.

In this specific example, the temporary work table stores temporary work records in which project numbers, order numbers, and project cost item categories are stored by order number and project cost item category, and each temporary work record can store the budget amount, accumulated cost amount, previous month's final forecast, final forecast, future planned cost, budget variance, and approval status. In Figures 5B, 6B, and 7A, temporary work table A shows the storage stages of the budget amount, accumulated cost amount, and previous month's final forecast, temporary work table B shows the storage stages of the final forecast, future planned cost, and budget variance, and temporary work table C shows the storage stages of the approval status, in the order of temporary work table A to temporary work table C.

Figures 5C, 5E, 5F, 6C, and 7B are diagrams showing the landing forecast header table and landing forecast detail table in this specific example. Figure 5C shows the landing forecast header table and landing forecast detail table in the first month (April 2023) of the start of automatic landing forecast creation, Figure 6C shows the landing forecast header table and landing forecast detail table in the next month (May 2023) after the start of automatic landing forecast creation when "Previous month landing forecast" is selected, and Figure 7B shows the landing forecast header table and landing forecast detail table in the next month (May 2023) after the start of automatic landing forecast creation when "Latest budget" is selected. Also, Figure 5E shows the landing forecast header table and landing forecast detail table at the change application stage of the final landing forecast amount in the first month (April 2023) of the start of automatic landing forecast creation, and Figure 5F shows the landing forecast header table and landing forecast detail table after the change is approved.

In this specific example, the final forecast header table stores final forecast header records by order number, which store the project number, order number, fiscal year and month, approval status, and creation category. In this specific example, the final forecast detail table stores final forecast detail records by order number and by project cost item category, which store the project number, order number, fiscal year and month, project cost item category, budget amount, accumulated cost amount, final final forecast, future planned cost, and budget variance.

Figures 5D and 6D are diagrams showing the check result notification screens in this specific example. Figure 5D shows the check result notification screen for the first month (April 2023) after the start of automatic landing forecast creation, and Figure 6D shows the check result notification screen for the month after the start of automatic landing forecast creation (May 2023).

Below, we will explain in detail the flow of information processing for automatically creating a price forecast and the flow of information processing when applying for a change to the final price forecast amount after the price forecast has been automatically created, based on the first to third cases, using Figures 2 to 7B.

(Example 1: Automatic creation of price forecast when "Previous month price forecast" is selected)
This section provides a detailed explanation of the information processing flow for automatically creating a landing forecast in the first month, April 2023, and the following month, May 2023, when April 2023 is set as the first month for starting automatic landing forecast creation and "1 (previous month's landing forecast)" is selected as the automatic landing forecast creation category (land forecast amount determination method).

In this first example, the automatic final forecast creation category (final forecast amount determination method) in the project basic information master shown in Figure 3 is preset to "1 (previous month's final forecast)." Therefore, when a final forecast detail record that includes the previous month's accounting year and month is stored in the final forecast detail table, the final final forecast amount for the previous month in that final forecast detail record is determined to be the final final forecast amount for the current month.

In this first example, the hold registration category (hold judgment target category) at the time of automatic creation of planned costs in the project cost item category master shown in Figure 3 is preset to hold judgment target "1: Yes" for "material costs", "outsourcing costs", and "labor costs" among the project cost item categories, and is preset to hold judgment non-target "0: No" for "expenses", as shown in Figure 3. Therefore, "material costs", "outsourcing costs", and "labor costs" are subject to hold judgment, and "expenses" are not subject to hold judgment.

As of April 2023, one project has been launched with project number "PJ001," and as shown in the project information table in Figure 4, project information record A01, which stores this project number and its corresponding project name, is stored in the project information table.

For the project with project number "PJ001", there are two orders with order numbers (i.e., order identification information) "JU001" and "JU002", and as shown in the contract information table in Figure 4, contract information records B01 and B02 are stored in the contract information table as contract information records corresponding to these orders, which store these order numbers and the corresponding contract name, fiscal year and month, contract period, contract amount, contract approval status, and contract completion category.

In the contract information record, the approval status "Approved" indicates that the order has been approved as a contract, and the completion category "Incomplete" indicates that the order has not yet been contracted.

For the order with order number "JU001", a budget with the accounting year and month "2023/04" is allocated to each of the three project cost item categories (i.e., cost items) of "material cost", "outsourcing cost", and "expenses". As shown in the budget information table in FIG. 5A, three budget information records C01 to C03, which store the project number, order number, number of changes to the budget amount (i.e., change identification information), accounting year and month, project cost item category, budget amount, and approval status, are stored in the budget information table as budget information records corresponding to these three project cost item categories. Similarly, for the order with order number "JU002", a budget with the accounting year and month "2023/04" is allocated to each of the three project cost item categories (cost items). As shown in the budget information table in FIG. 5A, three budget information records C04 to C06 are stored in the budget information table.

The approval status "Approved" in a budget information record indicates that the budget has been approved.

The number of changes to the budget amount in a budget information record is used to distinguish between old and new budget information records when budget amounts are received multiple times for the same order number and same project cost item category, and a new budget information record is stored with the number of changes added by 1 to the number of changes in the most recent budget information record with the same order number and project cost item category. Therefore, the budget amount of the budget information record with the greatest number of changes becomes the most recent budget amount at that stage. Note that the number of changes in the first budget information record is "0", as shown in budget information records C01 to C06.

First, based on the contract information table in FIG. 4, the tally target identification unit 102a identifies the order numbers "JU001" and "JU002" to be tallied as order numbers whose completion category is "incomplete" (contract incomplete) and whose approval status is "approved" (contract approved) (S01).

Next, the cost amount tallying unit 102b tally up the cost amounts for the accounting month and year "2023/04" by order number and by project cost item category based on the voucher information that is the cost, such as purchase information, stored in the voucher information database, and stores cost information records D01 to D05, which store the project number, order number, accounting month and year, project cost item category, and cost amount, in the cost information table, as shown in the cost information table in Figure 5A.

The cost amount tallying unit 102b totals the cost amounts stored in the cost information records D01 to D05 that correspond to the order numbers "JU001" and "JU002" identified by the tallying target identification unit 102a and have an accounting year and month before the current month "2023/04" among the cost information records stored in the cost information table by order number and by project cost item classification, and tallies the accumulated cost amount up to the current month (S02). Note that the cost information table in FIG. 5A does not store cost information records with accounting years and months before the previous month "2023/03", and only stores cost information records D01 to D05 with an accounting year and month of the current month "2023/04". Therefore, the cost amount of each of the cost information records D01 to D05 becomes the accumulated cost amount up to the current month.

The detail table update unit 102c stores the cumulative cost amounts up to the current month, calculated by the cost amount calculation unit 102b, in each of the temporary work records W11 to W16 by order number and project cost subject category, as shown in temporary work table A in FIG. 5B.

The detail table update unit 102c has allocated the budget for the combination of order number "JU002" and project cost item category "subcontract cost" as the corresponding budget information record is stored in the budget information table in FIG. 5A. However, since there is no cost information record in the cost information table with an accounting year and month up to the current month "2023/04", the accumulated cost amount is stored in the temporary work table as "￥0", as in temporary work record W15.

The budget amount determination unit 102d extracts the most recent budget information records C01 to C06 with the greatest number of changes from among the budget information records that correspond to the order numbers "JU001" and "JU002" identified by the aggregation target identification unit 102a stored in the budget information table of FIG. 5A, have accounting years and months before the current month "2023/04", and have an approval status of "Approved", by order number and project cost item category. Note that in the budget information table of FIG. 5A, "0" is the greatest number of changes for each combination of order number and project cost item category.

The budget amount determination unit 102d determines that the latest budget amount contained in the latest extracted budget information records C01 to C06 by order number and by project cost item category is the current budget amount (S03).

The detail table update unit 102c stores the current budget amounts confirmed by the budget amount confirmation unit 102d in each of the temporary work records W11 to W16 by order number and project cost subject category, as shown in temporary work table A in FIG. 5B.

Because this is the first month of automatic creation of the final forecast, no final forecast detail record including the previous month's accounting year and month is stored in the final forecast detail table, so the detail table update unit 102c stores "NULL" as the previous month's final forecast amount in each temporary work record W11 to W16, as shown in temporary work table A in FIG. 5B.

In this first example, the estimated final amount determination unit 102e has the automatic final forecast creation category (estimated final amount determination method) preset to "1 (previous month's estimated final amount)" (S04-YES), but since this is the first month of automatic final forecast creation, no estimated final amount detail record including the previous month's accounting year and month is stored in the estimated final amount table (S05-NO), and the previous month's final estimated final amount in temporary work table A in Figure 5B is "NULL", so the current budget amount determined by the budget amount determination unit 102d (i.e., the budget amount stored in each temporary work record W11-W16) by order number and project cost item category is determined to be the final estimated final amount for the current month (S06b).

The detail table update unit 102c stores the final estimated amount for the current month determined by the estimated amount determination unit 102e in each of the temporary work records W11 to W16 by order number and project cost item classification, as shown in temporary work table B in FIG. 5B.

The planned cost calculation unit 102f calculates the future planned cost for the current month by order number and project cost item classification, by subtracting the accumulated cost amount up to the current month compiled by the cost amount compilation unit 102b from the final estimated amount for the current month determined by the estimated amount determination unit 102e (i.e., by subtracting the accumulated cost amount from the final estimated amount of the temporary work records W11 to W16 in the temporary work table B in Figure 5B) (S07).

The detail table update unit 102c stores the future planned costs for the current month calculated by the planned cost calculation unit 102f in each of the temporary work records W11 to W16 by order number and project cost subject category, as shown in temporary work table B in Figure 5B.

The budget variance calculation unit 102g calculates the budget variance for the current month by subtracting the final forecast amount for the current month determined by the forecast amount determination unit 102e from the current budget amount determined by the budget amount determination unit 102d (i.e., by subtracting the final forecast amount from the budget amounts of temporary work records W11 to W16 in temporary worktable B in FIG. 5B) for each order number and project cost item category (S08). Note that as shown in temporary worktable B in FIG. 5B, the current budget amount and the final forecast amount for the current month are the same for each combination of order number and project cost item category, so the budget variance is "￥0" for all combinations.

The detail table update unit 102c stores the budget variance for the current month calculated by the budget variance calculation unit 102g in each of the temporary work records W11 to W16 by order number and project cost subject category, as shown in temporary work table B in FIG. 5B.

The hold determination unit 102h determines that the approval status for all order numbers "JU001" and "JU002" is "Approved" (estimated amount approved) (S10b), since there are no temporary work records with a budget amount of 0 and a final estimated amount of 0 among the temporary work records W11-W14/W16 whose accumulated cost amount exceeds 0 (S09-NO).

The detail table update unit 102c stores the estimated amount approved "Approved" as the approval status in the temporary work records W11 to W16 having the order numbers "JU001" and "JU002" that have been determined by the hold determination unit 102h to be estimated amount approved "Approved" as shown in temporary work table C in FIG. 5B.

The detail table update unit 102c newly stores in the forecast arrival detail table the forecast arrival header records E11 and E12, which are composed of the project number, order number, accounting year and month "2023/04 (current month)", approval status "Approved" determined by the reservation determination unit 102h, and creation category "Automatic Creation" indicating that the final forecast arrival amount has been automatically determined, by order number, as shown in the forecast arrival header table of FIG. 5C.

The detail table update unit 102c adds the accounting year and month "2023/04 (current month)" to each of the combinations of project number, order number, project cost item category, budget amount, accumulated cost amount, final forecast amount, future planned cost, and budget variance stored in the temporary work records W11 to W16, and stores these records as new forecast detail records F11 to F16 in the forecast detail table, as shown in the forecast detail table of FIG. 5C.

The check result output unit 102i determines that the approval status in all contract information records B01 and B02 is contract approved (approved) as shown in the contract information table of FIG. 4, that the approval status in all budget information records C01 to C06 is budget approved (approved) as shown in the budget information table of FIG. 5A, and that the approval status in all final forecast header records E11 and E12 is forecast amount approved (approved) as shown in the temporary work table C of FIG. 5B. Based on this determination result, as shown in FIG. 5D, the fiscal year and month is set to the current month (2023/04), and the check results are all set to "O" for the unapproved voucher check (contract), unapproved voucher check (budget), and unapproved voucher check (final forecast), and the number of errors is set to "0" (S11).

In the following month, May 2023, the automatic forecast creation category (method of determining the forecast amount) in the project basic information master shown in FIG. 3 has not been changed since the first month, April 2023, and remains set to "1 (previous month's forecast)." In addition, as of May 2023, the project information table and contract information table in FIG. 4 have not been changed since April 2023.

Meanwhile, in the budget information table, due to a change in the budget for each order with order numbers "JU001" and "JU002", a new budget with the accounting year and month "2023/05" has been allocated, and as shown in the budget information table in FIG. 6A, the budget receiving unit 102k has newly stored in the budget information table budget information records C07 to C12 with the number of changes "1" and the accounting year and month "2023/05" in addition to budget information records C01 to C06 with the number of changes "0" and the accounting year and month "2023/04".

First, in May 2023, the tally target identification unit 102a identifies the order numbers "JU001" and "JU002" to be tallied based on the contract information table in FIG. 4, just like in April 2023 (S01).

Next, the cost amount tallying unit 102b tally up the cost amounts for the accounting month and year "2023/05" by order number and by project cost item category based on the voucher information that is the cost, such as purchase information, stored in the voucher information database, and stores cost information records D06 to D12, which store the project number, order number, accounting month and year, project cost item category, and cost amount, in the cost information table, as shown in the cost information table in Figure 6A.

The cost amount aggregation unit 102b totals the cost amounts stored in cost information records D01 to D12 that correspond to the order numbers "JU001" and "JU002" identified by the aggregation target identification unit 102a and have accounting months prior to the current month "2023/05" among the cost information records stored in the cost information table, by order number and by project cost item classification, and aggregates the cumulative cost amount up to the current month (S02). In addition, the cost information table in FIG. 6A stores cost information records D01-D05 with the accounting year and month of the previous month "2023/04" and cost information records D06-D12 with the accounting year and month of the current month "2023/05". Since no cost information records with accounting years and months before the previous month "2023/03" or earlier are stored, the cumulative cost amount up to the current month is the sum of the cost amount of the cost information record for the previous month "2023/04" and the cost amount of the cost information record for the current month "2023/05", sorted by order number and project cost item category.

Specifically, for the combination of order number "JU001" and project cost item category "material cost", the accumulated cost amount is "500,000 yen", which is the sum of the cost amount "200,000 yen" in cost information record D01 for the previous month "2023/04" and the cost amount "300,000 yen" in cost information record D06 for the current month "2023/05". For the combination of order number "JU001" and project cost item category "subcontract cost", the accumulated cost amount is "700,000 yen", which is the sum of the cost amount "200,000 yen" in cost information record D02 for the previous month "2023/04" and the cost amount "500,000 yen" in cost information record D07 for the current month "2023/05". For the combination of order number "JU001" and project cost item category "expenses", the accumulated cost amount is "200,000 yen", which is the sum of the cost amount "50,000 yen" in cost information record D03 for the previous month "2023/04" and the cost amount "150,000 yen" in cost information record D08 for the current month "2023/05". For the combination of order number "JU002" and project cost item category "material cost", the accumulated cost amount is "500,000 yen", which is the sum of the cost amount "200,000 yen" in cost information record D04 for the previous month "2023/04" and the cost amount "300,000 yen" in cost information record D09 for the current month "2023/05". For the combination of order number "JU002" and project cost item category "subcontract cost", since there is no cost information record for the previous month "2023/04", the cost amount "¥1,000,000" in cost information record D10 for the current month "2023/05" becomes the accumulated cost amount as is. For the combination of order number "JU002" and project cost item category "expense", the accumulated cost amount is the sum of the cost amount "¥20,000" in cost information record D05 for the previous month "2023/04" and the cost amount "¥200,000" in cost information record D11 for the current month "2023/05", resulting in "¥220,000". For the combination of order number "JU002" and project cost item category "Labor Costs," since there is no cost information record for the previous month "2023/04," the cost amount "¥100,000" in cost information record D12 for the current month "2023/05" becomes the accumulated cost amount as is.

The detail table update unit 102c stores the cumulative cost amounts up to the current month, which have been collected by the cost amount collection unit 102b, in each of the temporary work records W21 to W27 by order number and by project cost subject category, as shown in temporary work table A in FIG. 6B.

The budget amount determination unit 102d extracts the most recent budget information records C07 to C12 with the greatest number of changes from among the budget information records that correspond to the order numbers "JU001" and "JU002" identified by the aggregation target identification unit 102a stored in the budget information table of FIG. 6A by order number and by project cost item category, have accounting years and months prior to the current month "2023/05", and have an approval status of "Approved". Note that in the budget information table of FIG. 6A, "1" is the greatest number of changes for each combination of order number and project cost item category.

The budget amount determination unit 102d determines that the latest budget amount contained in the latest extracted budget information records C07 to C12 by order number and by project cost item category is the current budget amount (S03).

The detail table update unit 102c stores the current budget amounts confirmed by the budget amount confirmation unit 102d in each of the temporary work records W21 to W27 by order number and project cost item classification, as shown in temporary work table A in FIG. 5B.

In addition, for the combination of order number "JU002" and project cost item category "labor cost", the detail table update unit 102c has calculated the cumulative cost amount up to the current month "2023/05" since a cost information record with the corresponding accounting year and month of the current month "2023/05" is stored in the cost information table of FIG. 6A. However, since there is no corresponding budget information record in the budget information table, the budget amount is stored in the temporary work table as "￥0", as in temporary work record W27.

As shown in FIG. 5C, the detail table update unit 102c stores the final forecast amount in the forecast detail records F11 to F16 including the accounting year and month of the previous month "2023/04" in the forecast detail table of FIG. 5C as the final forecast amount for the previous month in the forecast detail table of FIG. 5C, by order number and by project cost subject category, in each temporary work record W21 to W27, as shown in temporary work table A of FIG. 6B.

Note that for the combination of order number "JU002" and project cost item category "labor cost", since no forecasted end detail record including the corresponding accounting year and month of the previous month "2023/04" is stored in the forecasted end detail table of FIG. 5C, the detail table update unit 102c stores the previous month's final forecasted end amount as "￥0" in the temporary work table, as in temporary work record W27.

In this first example, the estimated final amount determination unit 102e determines that the final forecast amount in the estimated final amount records F11 to F16 for the previous month "2023/04" in the estimated final amount table is the final forecast amount for the current month (S06a), because the estimated final amount determination unit 102e determines that the final forecast amount in the estimated final amount records F11 to F16 for the previous month "2023/04" in the estimated final amount table in FIG. 5C (i.e., the previous month's final forecast amount stored in each temporary work record W21 to W27) is the final forecast amount for the current month, by order number and by project cost item category (S06a).

The detail table update unit 102c stores the final estimated amount for the current month determined by the estimated amount determination unit 102e in each of the temporary work records W21 to W27 by order number and project cost item classification, as shown in temporary work table B in FIG. 6B.

Similarly to April 2023, for May 2023, the planned cost calculation unit 102f calculates the future planned cost for the current month by subtracting the accumulated cost amount up to the current month compiled by the cost amount compilation unit 102b from the final estimated amount for the current month determined by the estimated amount determination unit 102e (i.e., by subtracting the accumulated cost amount from the final estimated amount of temporary work records W21 to W27 in temporary worktable B in FIG. 6B) by order number and project cost item category (S07). Note that if the accumulated cost amount is greater than the final estimated amount, as in the case of temporary work record W27 in temporary worktable B in FIG. 6B, the future planned cost will be a negative value.

The detail table update unit 102c stores the future planned costs for the current month calculated by the planned cost calculation unit 102f in each of the temporary work records W21 to W27 by order number and project cost subject category, as shown in temporary work table B in Figure 6B.

The budget variance calculation unit 102g calculates the budget variance for the current month by order number and project cost item classification, by subtracting the final estimated amount for the current month determined by the estimated amount determination unit 102e from the current budget amount determined by the budget amount determination unit 102d (i.e., by subtracting the final estimated amount from the budget amount of temporary work records W21 to W27 in temporary work table B in FIG. 6B) (S08).

The detail table update unit 102c stores the budget variance for the current month calculated by the budget variance calculation unit 102g in each of the temporary work records W21 to W27 by order number and project cost subject category, as shown in temporary work table B in FIG. 6B.

Of the temporary work records W21-W27 whose accumulated cost amounts exceed 0, there is a temporary work record W27 whose budget amount is 0 and whose final estimated amount is 0 (S09-YES), so the hold determination unit 102h identifies this and determines that the approval status of the identified temporary work record W27's order number "JU002" is "hold" (estimated amount hold), and that of the other order number "JU001" is "approved" (estimated amount approved) (S10a).

As shown in temporary work table C in FIG. 6B, the detail table update unit 102c stores the estimated amount reservation "on hold" as the approval status in temporary work records W24 to W27 having order number "JU002" that has been determined by the reservation determination unit 102h to be estimated amount reservation "on hold", and stores estimated amount approved "approved" as the approval status in temporary work records W21 to W23 having order number "JU001" that has been determined to be estimated amount approved "approved".

As in April 2023, the detail table update unit 102c newly stores in the forecast arrival detail table the forecast arrival header record E21 having the fiscal year and month "2023/05 (current month)", the order number "JU001", the approval status determined by the reservation determination unit 102h as "approved", and the creation category "automatic creation" indicating that the final forecast arrival amount has been automatically determined, by order number, as shown in the forecast arrival header table of FIG. 6C, and also newly stores in the forecast arrival detail table the forecast arrival header record E22 having the approval status determined by the reservation determination unit 102h as "reserved" and the creation category "automatic creation" indicating that the final forecast arrival amount has been automatically determined, for order number "JU002" (the forecast arrival header records E11 and E12 for the fiscal year and month "2023/04 (previous month)" are omitted in the forecast arrival header table of FIG. 6C).

The detail table update unit 102c adds the accounting year and month "2023/05 (current month)" to each of the combinations of project number, order number, project cost item category, budget amount, accumulated cost amount, final estimated amount, future planned cost, and budget variance stored in the temporary work records W21 to W27 as shown in the estimated end date detail table in FIG. 6C, and stores these records as estimated end date detail records F21 to F27 in the estimated end date detail table (the estimated end date detail records F11 to F16 for the accounting year and month "2023/04 (previous month)" are omitted in the estimated end date detail table in FIG. 6C).

As shown in the contract information table of FIG. 4, the approval status of all contract information records B01 and B02 is contract approved "approved", and as shown in the budget information table of FIG. 6A, the approval status of all budget information records C07 to C12 is budget approved "approved", but as shown in the temporary work table C of FIG. 6B, the check result output unit 102i determines that of the two expected end result header records E21 and E22, the approval status of expected end result header record E22 is expected amount reserved "reserved", and based on this determination result, as shown in FIG. 6D, the fiscal year and month are set to the current month "2023/05", the check results for the unapproved voucher check (contract) and the unapproved voucher check (budget) are set to "◯", the check result for the unapproved voucher check (expected end result) is set to "×", and the number of errors is set to "1" (S11).

(Example 2: Automatic creation of forecast when "Latest Budget" is selected)
This section provides a detailed explanation of the information processing flow for automatic creation of a final forecast in the first month when April 2023 is set as the first month for starting automatic creation of a final forecast and "2 (latest budget)" is selected as the automatic final forecast creation category (method of determining final forecast amount).

In this second example, the settings and conditions are exactly the same as those in the first example described above, except that "2 (latest budget)" is selected as the automatic final forecast creation category (final forecast amount determination method).

First, the tally target identification unit 102a identifies the order numbers "JU001" and "JU002" to be tallied, similar to April 2023 in the first example (S01).

As in the case of April 2023 in the first example, the cost amount tallying unit 102b tally up the accumulated cost amount based on the order numbers "JU001" and "JU002" identified by the tallying target identification unit 102a (S02), the budget amount determination unit 102d determines the current budget amount (S03), and the detail table update unit 102c stores the accumulated cost amount and budget amount similar to those for April 2023 in the first example in temporary work records W11 to W16 as shown in temporary work table A in FIG. 5B, and further stores "NULL" as the previous month's final estimated amount, similar to that for April 2023 in the first example.

In this second example, since the automatic forecast creation category (forecasted final amount determination method) is preset to "2 (latest budget)" (S04-NO), the estimated final amount determination unit 102e determines the current budget amount determined by the budget amount determination unit 102d (i.e., the budget amount stored in each temporary work record W11 to W16) by order number and project cost item category as the final estimated final amount for the month, regardless of whether a forecasted final amount record including the previous accounting month is stored in the forecasted final amount table (S06b), and stores the same final estimated final amount as for April 2023 in the first example in the temporary work records W11 to W16, as shown in temporary work table B in FIG. 5B.

As in April 2023 in the first example, the planned cost calculation unit 102f calculates the future planned cost for the current month (S07), the budget variance calculation unit 102g calculates the budget variance for the current month (S08), and the detail table update unit 102c stores the future planned cost and budget variance in temporary work records W11 to W16, similar to those in April 2023 in the first example, as shown in temporary work table B in FIG. 5B. As in April 2023 in the first example, the reservation determination unit 102h stores the expected amount approved "Approved" as the approval status in temporary work records W11 to W16, as shown in temporary work table C in FIG. 5B (S09-NO, S10b).

Finally, the detail table update unit 102c newly stores the landing forecast header records E11 and E12 similar to those for April 2023 in the first case in the landing forecast detail table, as shown in the landing forecast detail table of FIG. 5C, and newly stores the landing forecast detail records F11 to F16 similar to those for April 2023 in the first case in the landing forecast detail table, and the check result output unit 102i outputs a check result notification screen similar to that for April 2023 in the first case, as shown in FIG. 5D (S11).

In the following month, May 2023, the automatic forecast creation category (method of determining the estimated final amount) in the project basic information master shown in FIG. 3 has not been changed since the first month, April 2023, and remains set to "2 (latest budget)." In addition, as of May 2023, the project information table and contract information table in FIG. 4 have not been changed since April 2023.

Meanwhile, in the budget information table, as in May 2023 in the first case, a change occurred to the budget for each order with order numbers "JU001" and "JU002", and as shown in the budget information table in FIG. 6A, the budget receiving unit 102k has newly stored budget information records C07 to C12 with the number of changes "1" and the accounting year and month "2023/05" in the budget information table.

First, in May 2023, the aggregation target identification unit 102a identifies the order numbers "JU001" and "JU002" based on the contract information table in FIG. 4, just like in April 2023 in the second example (S01).

As with May 2023 in the first example, the cost amount tallying unit 102b tallyes the cost amounts for the accounting year and month "2023/05" by order number and by project cost item classification based on the voucher information stored in the voucher information database, and stores cost information records D06 to D12 in the cost information table as shown in the cost information table in Figure 6A.

As in the case of May 2023 in the first example, the cost amount tallying unit 102b sums up the cost amounts stored in the cost information records D01 to D12 that correspond to the order numbers "JU001" and "JU002" identified by the tallying target identification unit 102a and have accounting months prior to the current month "2023/05" among the cost information records stored in the cost information table by order number and by project cost item classification, tallying up the accumulated cost amount up to the current month (S02), and the detail table updating unit 102c stores the accumulated cost amount up to the current month in each of the temporary work records W31 to W37, as shown in temporary work table A in FIG. 7A.

As in the case of May 2023 in the first example, the budget amount determination unit 102d extracts the latest budget information records C07 to C12 with the greatest number of changes from among the budget information records that correspond to the order numbers "JU001" and "JU002" identified by the aggregation target identification unit 102a stored in the budget information table of FIG. 6A by order number and by project cost item category, have an accounting year and month before the current month "2023/05", and have an approval status of "Approved", and determines that the latest budget amount included in the extracted latest budget information records C07 to C12 is the current budget amount (S03), and the detail table update unit 102c stores the current budget amount in each of the temporary work records W31 to W37, as shown in the temporary work table A in FIG. 7A.

In the second example, since the automatic forecast creation category (forecasted final amount determination method) is preset to "2 (latest budget)" (S04-NO), as in April 2023, regardless of whether a forecasted final amount detail record including the previous month's accounting year and month is stored in the forecasted final amount detail table, the estimated final amount determination unit 102e determines the current budget amount determined by the budget amount determination unit 102d (i.e., the budget amount stored in each temporary work record W31 to W37) by order number and project cost item category as the final estimated final amount for the month (S06b), and stores the final estimated final amount determined by the estimated final amount determination unit 102e in each of the temporary work records W31 to W37 as shown in temporary work table B in FIG. 7A.

Similarly to April 2023, for May 2023, the planned cost calculation unit 102f calculates the future planned cost for the current month by subtracting the accumulated cost amount up to the current month compiled by the cost amount compilation unit 102b from the final estimated amount for the current month determined by the estimated amount determination unit 102e (i.e., by subtracting the accumulated cost amount from the final estimated amount of the temporary work records W31 to W37 in the temporary work table B of FIG. 7A) by order number and project cost item classification (S07), and the detail table update unit 102c stores the future planned cost for the current month in each of the temporary work records W31 to W37 as shown in the temporary work table B of FIG. 7A. Note that if the accumulated cost amount is greater than the final estimated amount, as in the temporary work record W37 in the temporary work table B of FIG. 7A, the future planned cost will be a negative value.

The budget variance calculation unit 102g calculates the budget variance for the current month by order number and by project cost item category, by subtracting the final estimated amount for the current month determined by the estimated amount determination unit 102e from the current budget amount determined by the budget amount determination unit 102d (i.e., by subtracting the final estimated amount from the budget amount of temporary work records W31 to W37 in temporary work table B in FIG. 7A) (S08), and the detail table update unit 102c stores the budget variance for the current month in each of the temporary work records W31 to W37, as shown in temporary work table B in FIG. 7A.

Of the temporary work records W31 to W37 whose accumulated cost amounts exceed 0, the hold determination unit 102h identifies temporary work record W37 whose budget amount is 0 and whose final estimated amount is 0 (S09-YES), and determines that the approval status of the order number "JU002" held by the identified temporary work record W37 is "hold" (estimated amount hold), and that of the other order number "JU001" is "approved" (estimated amount approved) (S10a).

As shown in temporary work table C in FIG. 7A, the detail table update unit 102c stores the estimated amount reservation "on hold" as the approval status in temporary work records W34 to W37 having order number "JU002" that has been determined by the reservation determination unit 102h to be estimated amount reservation "on hold", and stores estimated amount approved "approved" as the approval status in temporary work records W31 to W33 having order number "JU001" that has been determined to be estimated amount approved "approved".

As shown in the forecast arrival header table of FIG. 7B, the detail table update unit 102c newly stores in the forecast arrival detail table a forecast arrival header record E31 having the fiscal year and month "2023/05 (current month)", the order number "JU001", the approval status determined by the reservation determination unit 102h as "approved", and the creation category "automatic creation" indicating that the final forecast arrival amount has been automatically determined, for each order number, and also newly stores in the forecast arrival detail table a forecast arrival header record E32 having the approval status determined by the reservation determination unit 102h as "pending" and the creation category "automatic creation" indicating that the final forecast arrival amount has been automatically determined, for order number "JU002" (the forecast arrival header records E11 and E12 for the fiscal year and month "2023/04 (previous month)" are omitted in the forecast arrival header table of FIG. 7B).

The detail table update unit 102c adds the accounting year and month "2023/05 (current month)" to each of the combinations of project number, order number, project cost item category, budget amount, accumulated cost amount, final estimated amount, future planned cost, and budget variance stored in the temporary work records W31 to W37 as shown in the estimated end date detail table in FIG. 7B, and stores these records as estimated end date detail records F31 to F37 in the estimated end date detail table (the estimated end date detail records F11 to F16 for the accounting year and month "2023/04 (previous month)" are omitted in the estimated end date detail table in FIG. 7B).

As shown in the contract information table of FIG. 4, the approval status of all contract information records B01 and B02 is contract approved "approved", and as shown in the budget information table of FIG. 6A, the approval status of all budget information records C07 to C12 is budget approved "approved", but as shown in the temporary work table C of FIG. 7C, the check result output unit 102i determines that of the two expected arrival header records E31 and E32, the approval status of expected arrival header record E32 is expected amount reserved "reserved", and based on this determination result, as shown in FIG. 7C, the fiscal year and month is set to the current month "2023/05", the check results for the unapproved voucher check (contract) and the unapproved voucher check (budget) are set to "◯", the check result for the unapproved voucher check (expected arrival) is set to "×", and the number of errors is set to "1" (S11).

(Case 3: Application for change to final forecast amount after automatic forecast creation)
We will now provide a detailed explanation of the flow of information processing after accepting a change application when changing a specific final forecast amount in the forecasted landing amount details table of Figure 5C that was finally created in April 2023 for the first or second case.

First, user A inputs a change request to change the final estimated amount for the combination of order number "JU002" and project cost item category "subcontract cost" in the estimated amount details table in Figure 5C from "￥4,000,000" to "￥5,000,000."

The change acceptance unit 102j accepts the change application for user A, along with the order number "JU002", the project cost item category "outsourcing cost", and the change application amount "￥5,000,000", to change the final estimated amount.

The detail table update unit 102c updates the final estimated value of the estimated value detail record F15 corresponding to the combination of the order number "JU002" and the project cost item category "subcontract cost" accepted by the change acceptance unit 102j from "￥4,000,000" in the estimated value detail table of FIG. 5C to the change application amount "￥5,000,000" accepted by the change acceptance unit 102j, as shown in the estimated value detail table of FIG. 5E.

The planned cost calculation unit 102f calculates the future planned cost by subtracting the accumulated cost amount compiled by the cost amount compilation unit 102b from the final estimated landing amount updated by the detail table update unit 102c, while the budget variance calculation unit 102g calculates the budget variance for the current month by subtracting the final estimated landing amount from the budget amount in the estimated landing detail record F15.

The detail table update unit 102c updates the future planned cost and the budget variance in the final forecast detail record F15 to the future planned cost calculated by the planned cost calculation unit 102f and the budget variance calculated by the budget variance calculation unit 102g, as shown in the final forecast detail table in FIG. 5E.

The detail table update unit 102c also updates the approval status of the forecast arrival header record E12 corresponding to the order number "JU002" accepted by the change acceptance unit 102j from "Approved", which indicates that the forecast amount has been approved, in the forecast arrival detail table of FIG. 5C, to "Pending", which indicates that the forecast amount change has been applied for, as shown in the forecast arrival header table of FIG. 5E, and also updates the creation category from "Automatically created" in the forecast arrival detail table of FIG. 5C to "Manually entered", which indicates that the entry was made manually by user A, as shown in the forecast arrival header table of FIG. 5E.

Next, another user B, who confirmed that the approval status of the forecast header record E12 for order number "JU002" in the forecast header table in Figure 5E was "Application in progress," which is the forecast amount change application stage, approved the application to change the final forecast amount for order number "JU002" and entered approval of the change application.

The change acceptance unit 102j accepts approval for the change request for order number "JU002" based on the approval input by user B.

The detail table update unit 102c updates the approval status of the forecast arrival header record E12 corresponding to the order number "JU002" accepted by the change acceptance unit 102j from the forecast amount change application stage "Application in progress" in the forecast arrival detail table of FIG. 5E to the forecast amount approved stage "Approved" as shown in the forecast arrival header table of FIG. 5F. In this way, the change based on the application to change the final forecast arrival amount is confirmed.

As explained above, the system of the present invention can reduce data registration costs by automatically creating final forecasts for projects that have not made any particular progress since the last review or projects where costs are simply accumulating. In addition, when changes are made to the project budget, cost information, etc., the final forecast can be automatically updated based on the changed data, reducing the cost of reconsidering the final forecast. Furthermore, if the automatic creation detects the occurrence of unexpected costs, such as when a budget is missed, a review can be forced, reducing the risk of missing a budget.

[3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

4. Other embodiments
Although the embodiments of the present invention have been described above, the present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept described in the claims.

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

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

Furthermore, with regard to the PC 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of each device constituting the PC 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by each device as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the PC 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, and may also be configured as a program first product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The PC 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 PC 100 may be realized by implementing software (including programs or data, etc.) that causes the PC 100 to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in many industries, such as the construction and IT industries, where it is necessary to calculate final results for each project by referring to budget and cost information, etc.

100 PCS
102 Control unit 102a Counting object identification unit 102b Cost amount counting unit 102c Detail table update unit 102d Budget amount determination unit 102e Estimated final amount determination unit 102f Planned cost calculation unit 102g Budget variance calculation unit 102h Hold determination unit 102i Check result output unit 102j Change acceptance unit 102k Budget acceptance unit 104 Communication interface unit 106 Memory unit 106a Project basic information master memory unit 106b PJ cost item classification master memory unit 106c Project information table memory unit 106d Contract information table memory unit 106e Budget information table memory unit 106f Cost information table memory unit 106g Estimated final header table memory unit 106h Estimated final detail table memory unit 108 Input/output interface unit 200 Server 300 Network 400 Input device 500 Output device

Claims (10)

An accounting support device including a control unit,
The control unit:
a cost amount aggregating means for aggregating the accumulated cost amount up to the current month by order identification information and by cost item;
a budget amount determination means for, when corresponding budget amounts exist for each order identification information and each cost item, extracting the latest corresponding budget amount from the corresponding budget amounts and determining that the extracted budget amount is the current budget amount, and, when no corresponding budget amount exists, determining that 0 is the current budget amount;
a final estimate determining means for determining, by order identification information and by cost item, (1) determining the current budget amount determined by said budget amount determining means as the final estimate for the current month, or (2) determining, if there is no final estimate for the previous month, the current budget amount determined by said budget amount determining means as the final estimate for the current month, and, if there is a final estimate for the previous month, determining the final estimate for the previous month as the final estimate for the current month, according to a preselected final estimate determining method;
a planned cost calculation means for calculating a future planned cost for the current month by subtracting the accumulated cost amount up to the current month, which has been collected by the cost amount collection means, from the final estimated cost for the current month, which has been determined by the estimated cost determination means, for each order identification information and each cost item;
An accounting support device comprising: The control unit:
The accounting support device according to claim 1, further comprising a detail table update means for newly storing in the forecasted arrival detail table, for each order identification information and each cost item, a forecasted arrival detail record including the final forecasted arrival amount for the current month determined by said forecasted arrival amount determination means, the future planned cost for the current month calculated by said planned cost calculation means, and the fiscal year and month, with the current month being the fiscal year and month, The control unit:
The accounting support device according to claim 1, further comprising a hold determination means for extracting combinations of order identification information and cost items for which a cumulative cost amount exceeding 0 has been accumulated by the cost amount accumulation means, the combinations being determined by the budget amount determination means to be 0 for the current stage budget amount determined by the budget amount determination means and the final forecast amount for the current month determined by the forecast amount determination means to be 0, and determining that the order identification information corresponding to the extracted combination is unapproved or on hold. The hold determination means
The accounting support device according to claim 3, characterized in that from among the combinations, combinations are extracted in which the current budget amount determined by the budget amount determination means is 0, the final forecast amount for the current month determined by the forecast amount determination means is 0, and the combination has a cost item that is a pre-selected target for hold determination, and the accounting support device determines that the order identification information corresponding to the extracted combination is unapproved or on hold. The control unit:
5. The accounting support device according to claim 3, further comprising: a check result output means for outputting a notification that there is order identification information that has been determined by the hold determination means to be unapproved or on hold. The control unit:
2. The accounting support device according to claim 1, further comprising a budget receiving means for receiving a budget amount by order identification information and by cost item, and capable of receiving a budget amount multiple times for the same order identification information and the same cost item. The control unit:
a budget variance calculation means for calculating a budget variance for the current month by subtracting the final estimated amount for the current month determined by the estimated amount determination means from the current budget amount determined by the estimated amount determination means, for each order identification information and each cost item;
The detail table updating means
The accounting support device as described in claim 2, characterized in that a forecasted arrival detail record including the final forecasted amount for the current month, the future planned cost for the current month, and the accounting year and month, as well as the budget variance for the current month calculated by the budget variance calculation means, is newly stored in the forecasted arrival detail table by order identification information and cost item. The control unit:
a change acceptance means for accepting an application for change of a final estimated amount in the estimated amount detail record including the latest accounting year and month stored in the estimated amount detail table, by order identification information and by cost item, together with the order identification information, the cost item, and the change application amount;
The detail table updating means is
The accounting support device according to claim 2, characterized in that the final forecast amount in the forecasted amount detail record including the latest accounting year and month corresponding to the order identification information and cost item accepted by the change accepting means is updated to the change application amount accepted by the change accepting means. A accounting support method executed in an accounting support device having a control unit,
Executed by the control unit,
a cost amount aggregation step for aggregating the cumulative cost amount up to the current month by order identification information and by cost item;
a budget amount determination step in which, if corresponding budget amounts exist for each order identification information and each cost item, the latest corresponding budget amount is extracted from the corresponding budget amounts, and the extracted budget amount is determined to be the current budget amount, and if no corresponding budget amount exists, 0 is determined to be the current budget amount;
a final estimate determination step for determining, by order identification information and by cost item, (1) determining the current budget amount determined by the budget amount determination step as the final estimate for the current month, or (2) determining, if there is no final estimate for the previous month, the current budget amount determined by the budget amount determination step as the final estimate for the current month, and, if there is a final estimate for the previous month, determining the final estimate for the previous month as the final estimate for the current month, depending on a preselected final estimate determination method;
a planned cost calculation step for calculating a future planned cost for the current month by subtracting the accumulated cost amount up to the current month, which has been collected in the cost amount collection step, from the final estimated cost for the current month, which has been determined in the estimated cost determination step, by order identification information and by cost item;
An accounting support method comprising: An accounting support program to be executed by an accounting support device having a control unit,
To cause the control unit to execute
a cost amount aggregation step for aggregating the cumulative cost amount up to the current month by order identification information and by cost item;
a budget amount determination step in which, if corresponding budget amounts exist for each order identification information and each cost item, the latest corresponding budget amount is extracted from the corresponding budget amounts, and the extracted budget amount is determined to be the current budget amount, and if no corresponding budget amount exists, 0 is determined to be the current budget amount;
a final estimate determination step for determining, by order identification information and by cost item, (1) determining the current budget amount determined by the budget amount determination step as the final estimate for the current month, or (2) determining, if there is no final estimate for the previous month, the current budget amount determined by the budget amount determination step as the final estimate for the current month, and, if there is a final estimate for the previous month, determining the final estimate for the previous month as the final estimate for the current month, depending on a preselected final estimate determination method;
a planned cost calculation step for calculating a future planned cost for the current month by subtracting the accumulated cost amount up to the current month, which has been collected in the cost amount collection step, from the final estimated cost for the current month, which has been determined in the estimated cost determination step, by order identification information and by cost item;
An accounting support program comprising:

Images