Accounting support device, accounting support method, and accounting support program

Abstract

To provide an accounting support device, a method, and a program that reduce the burden of data registration and avoid the risk of budget compilation omission.SOLUTION: A PC 100 (accounting support device) includes: a prime cost amount adding unit that adds up a totalized prime cost amount up to the current month; a budget amount determination unit that extracts, if corresponding budget amounts exist, a latest corresponding budget amount from the corresponding budget amounts, and determines the extracted budget amount as a current budget amount; an attainment expectation amount determination unit that determines, according to a preselected attainment expectation amount determination method, the current budget amount as a final attainment expectation amount for the current month, or determines the current budget amount as the final attainment expectation amount for the current month if a final attainment expectation amount for the previous month does not exist, and determines the final attainment expectation amount for the previous month as the final attainment expectation amount for the current month if the final attainment expectation amount for the previous month exists; and a planned prime cost calculation unit that calculates a future planned prime cost for the current month by subtracting the totalized prime cost amount up to the current month from the final attainment expectation amount for the current month.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] In creating landing prediction data for a project, it is necessary to centrally manage contract information, budget information, various cost information associated with the project, etc. However, there has been a problem that it takes time and cost to consider the landing prediction while referring to the budget, cost information, etc. for each project. Also, when the budget, cost information, etc. increase or decrease after the consideration of the landing prediction and data registration, there has been a problem that the cost of re-examining the landing prediction reflecting the increase or decrease occurs. Further, when the budget and cost of a project do not match, there is a risk that a control risk such as an omission in budget preparation may be overlooked without an easy-to-review mechanism.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] Therefore, an object of the present invention is to provide a new system that can reduce the load of data registration by automatically creating landing prediction data with reference to budget / cost information, etc. for each project, and can avoid risks such as omissions in budget preparation.

Means for Solving the Problems

[0005] In order to solve the above-described problems and achieve the object, an accounting support apparatus according to the present invention is an accounting support apparatus including a control unit, wherein the control unit includes: a cost amount aggregating means for aggregating the cumulative cost amount up to the current month by order identification information and cost item; a budget amount determining means for, for each order identification information and each cost item, when there is a corresponding budget amount, extracting the latest corresponding budget amount from the corresponding budget amounts, determining the extracted budget amount as the current-stage budget amount, and when there is no corresponding budget amount, determining 0 as the current-stage budget amount; a landing forecast amount determining means for, according to a previously selected landing forecast amount determination method, for each order identification information and each cost item, (1) determining the current-stage budget amount determined by the budget amount determining means as the final landing forecast amount for the current month, or (2) when there is no final landing forecast amount for the previous month, determining the current-stage budget amount determined by the budget amount determining means as the final landing forecast amount for the current month, and when there is a final landing forecast amount for the previous month, determining the final landing forecast amount for the previous month as the final landing forecast amount for the current month; and a planned cost calculating means for, for each order identification information and each cost item, subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregating means from the final landing forecast amount for the current month determined by the landing forecast amount determining means to calculate the planned cost for the future at the current-month stage.

[0006] Further, in the accounting support apparatus according to the present invention, the control unit includes a detail table updating means for, for each order identification information and each cost item, newly storing in a landing forecast detail table a landing forecast detail record including the final landing forecast amount for the current month determined by the landing forecast amount determining means, the planned cost for the future at the current-month stage calculated by the planned cost calculating means, and the accounting year and month with the current month as the accounting year and month.

[0007] Further, the accounting support device according to the present invention is characterized in that the control unit extracts a combination of order identification information and cost items for which a cumulative cost amount exceeding 0 has been aggregated by the cost amount aggregation means, and for which the current-stage budget amount determined by the budget amount determination means is 0 and the final landing forecast amount for the current month determined by the landing forecast amount determination means is 0, and includes a hold determination means for determining that the order identification information corresponding to the extracted combination is unapproved or on hold.

[0008] Further, the accounting support device according to the present invention is characterized in that the hold determination means extracts a combination having a current-stage budget amount determined by the budget amount determination means of 0, a final landing forecast amount for the current month determined by the landing forecast amount determination means of 0, and a cost item of a hold determination target selected in advance from among the combinations, and determines that the order identification information corresponding to the extracted combination is unapproved or on hold.

[0009] Further, the accounting support device according to the present invention is characterized in that the control unit includes a check result output means for outputting a notification that there is order identification information for which the hold determination means has determined to be unapproved or on hold.

[0010] Further, the accounting support device according to the present invention is characterized by further comprising a budget reception means for the control unit to receive a budget amount for each order identification information and each cost item, and being capable of receiving the budget amount a plurality of times for the same order identification information and the same cost item.

[0011] In addition, the accounting support device according to the present invention further includes a budget variance calculation means for calculating a monthly budget variance by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination means from the current stage budget amount determined by the budget amount determination means for each order identification information and each cost item. The detailed table update means newly stores in the landing forecast detail table a landing forecast detail record including the final landing forecast amount for the current month, the planned future cost at the current month stage, and the accounting year and month, as well as the monthly budget variance calculated by the budget variance calculation means, for each order identification information and each cost item.

[0012] In addition, the accounting support device according to the present invention further includes a change reception means for receiving an application for a change in the final landing forecast amount in the landing forecast detail record including the latest accounting year and month stored in the landing forecast detail table for each order identification information and each cost item, together with the order identification information, the cost item, and the change application amount. The detailed table update means updates the final landing forecast amount in the landing forecast detail record including the latest accounting year and month corresponding to the order identification information and the cost item received by the change reception means to the change application amount received by the change reception means.

[0013] Further, the accounting support method according to the present invention is an accounting support method executed in an accounting support apparatus including a control unit, and includes a cost amount aggregation step of aggregating the cumulative cost amount up to the current month by order identification information and cost item, which is executed by the control unit; a budget amount determination step of, for each order identification information and cost item, when there is a corresponding budget amount, extracting the latest corresponding budget amount from the corresponding budget amounts, determining the extracted budget amount as the current-stage budget amount, and when there is no corresponding budget amount, determining 0 as the current-stage budget amount; a landing forecast amount determination step of, according to a preselected landing forecast amount determination method, for each order identification information and cost item, (1) determining the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, or (2) when there is no final landing forecast amount for the previous month, determining the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, and when there is a final landing forecast amount for the previous month, determining the final landing forecast amount for the previous month as the final landing forecast amount for the current month; and a planned cost calculation step of, for each order identification information and cost item, subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation step from the final landing forecast amount for the current month determined by the landing forecast amount determination step to calculate the planned cost for the future at the current month stage.

[0014] Also, an accounting support program according to the present invention is an accounting support program for causing an accounting support device including a control unit to execute, and includes a cost amount aggregation step of aggregating the cumulative cost amount up to the current month for each order identification information and each cost item for execution by the control unit; a budget amount determination step of, for each order identification information and each cost item, when there is a corresponding budget amount, extracting the latest corresponding budget amount from the corresponding budget amounts, determining the extracted budget amount as the budget amount at the current stage, and when there is no corresponding budget amount, determining 0 as the budget amount at the current stage; a landing prediction amount determination step of, according to a previously selected landing prediction amount determination method, for each order identification information and each cost item, (1) determining the budget amount at the current stage determined by the budget amount determination step as the final landing prediction amount for the current month, or (2) when there is no final landing prediction amount for the previous month, determining the budget amount at the current stage determined by the budget amount determination step as the final landing prediction amount for the current month, and when there is a final landing prediction amount for the previous month, determining the final landing prediction amount for the previous month as the final landing prediction amount for the current month; and a planned cost calculation step of, for each order identification information and each cost item, subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation step from the final landing prediction amount for the current month determined by the landing prediction amount determination step to calculate the planned cost for the current month stage.

Effect of the Invention

[0015] According to the system of the present invention, by referring to budget and cost information for each project and automatically creating landing prediction data, the load of data registration can be reduced and risks such as omissions in budget preparation can be avoided.

Brief Description of the Drawings

[0016]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5A

Figure 5B

Figure 5C

Figure 5D

Figure 5E

Figure 5F

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 7A

Figure 7B

DETAILED DESCRIPTION OF THE INVENTION

[0017] Embodiments of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to these embodiments.

[0018] [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 implemented with the configuration of this embodiment. Also, in the following description regarding the configuration, duplicate descriptions may be omitted.

[0019] FIG. 1 is a block diagram showing an example of the configuration of the 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 communicably connected via a network 300 (for example, the Internet, an intranet, a LAN (Local Area Network), etc.) to a server 200 (for example, a Web server, etc.) that stores various data (for example, various data described later that are stored in the storage unit 106).

[0020] Each unit included in the PC 100 is communicably connected via an arbitrary communication path.

[0021] Note that the 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 Assistants), a smartphone, or a tablet personal computer.

[0022] The control unit 102 is a CPU or the like that comprehensively controls the PC 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs defining various processing procedures, and required data, and executes various information processes based on these stored programs.

[0023] Functionally conceptually, the control unit 102 includes an aggregation target identification unit 102a, a cost amount aggregation unit 102b, a detail table update unit 102c, a budget amount determination unit 102d, a landing prediction amount determination unit 102e, a planned cost calculation unit 102f, a budget difference calculation unit 102g, a hold determination unit 102h, a check result output unit 102i, a change reception unit 102j, a budget reception unit 102k, etc.

[0024] The aggregation target identification unit 102a identifies the order identification information to be aggregated. The order identification information to be aggregated can be set in advance, and for example, it can be order identification information whose completion status is contract incomplete and whose approval status is contract approved. Such order identification information can be extracted from a contract information table in which the completion status, approval status, etc. are stored together with the order identification information.

[0025] The cost amount aggregation unit 102b aggregates the cumulative cost amount up to the current month by order identification information and cost item. The cost amount aggregation unit 102b can aggregate the cumulative cost amount up to the current month from the cost amounts registered by fiscal year and month in the cost information table. The cost amount aggregation unit 102b aggregates the cost amounts by fiscal year and month by order identification information and cost item based on the cost-related voucher information such as purchase information stored in the voucher information database, and stores them in the cost information table. The cost amount to be aggregated by the cost amount aggregation unit 102b is the cost amount corresponding to the order identification information specified by the aggregation target identification unit 102a.

[0026] When there is a corresponding budget amount 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, determines the extracted budget amount as the current stage budget amount, and when there is no corresponding budget amount, determines 0 as the current stage budget amount.

[0027] The budget amount determination unit 102d can determine whether there is a corresponding budget amount by checking whether the corresponding budget amount is stored in the budget information table, and can identify whether it is the latest corresponding budget amount based on the change identification information for identifying the newness and oldness of the budget amount.

[0028] The budget amount to be determined by the budget amount determination unit 102d is the budget amount corresponding to the order identification information specified by the aggregation target specifying unit 102a. Also, the budget amount to be determined by the budget amount determination unit 102d is the budget amount corresponding to the accounting year and month before the current month, and is also the budget amount whose budget approval status is budget approved.

[0029] The budget reception unit 102k receives budget amounts by order identification information and cost item, and it is possible to 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 the budget amounts in the budget information table, the budget reception unit 102k registers the budget amount registration together with the change identification information for identifying the newness and oldness of the budget amount.

[0030] The landing forecast amount determination unit 102e, according to the pre-selected landing forecast amount determination method, for each order identification information and cost item, (1) determines whether the current-stage budget amount determined by the budget amount determination unit 102d is the final landing forecast amount for the current month, or (2) if there is no final landing forecast amount for the previous month, determines that the current-stage budget amount determined by the budget amount determination unit 102d is the final landing forecast amount for the current month, and if there is a final landing forecast amount for the previous month, determines that the final landing forecast amount for the previous month is the final landing forecast amount for the current month.

[0031] The landing forecast amount determination unit 102e can determine whether there is a final landing forecast amount for the previous month by checking whether the final landing forecast amount corresponding to the accounting year and month of the previous month is stored in the landing forecast detail table.

[0032] The planned cost calculation unit 102f calculates the future planned cost at the current month stage by subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b from the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e for each order identification information and each cost item.

[0033] The budget variance calculation unit 102g calculates the budget variance for the current month by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e from the budget amount for the current stage determined by the budget amount determination unit 102d for each order identification information and each cost item.

[0034] The detail table update unit 102c newly stores in the landing forecast detail table the landing forecast detail records including the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e, the future planned cost at the current month stage calculated by the planned cost calculation unit 102f, and the accounting year and month for each order identification information and each cost item with the current month as the accounting year and month.

[0035] The landing forecast detail records stored in the landing forecast detail table by the detail table update unit 102c may include the budget amount for the current stage determined by the budget amount determination unit 102d, the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b, and the budget variance for the current month calculated by the budget variance calculation unit 102g.

[0036] The change reception unit 102j receives, for each order identification information and each cost item, an application for changing the final landing forecast amount in the landing forecast detail record including the latest accounting year and month stored in the landing forecast detail table, together with the order identification information, the cost item, and the change application amount.

[0037] The detail table update unit 102c updates the final landing forecast amount in the landing forecast detail record including the latest accounting year and month corresponding to the order identification information and the cost item received by the change reception unit 102j to the change application amount received by the change reception unit 102j.

[0038] The reservation determination unit 102h extracts, from combinations of order identification information and cost items for which the cumulative cost amount exceeding 0 has been aggregated by the cost amount aggregation unit 102b, combinations where the current-stage budget amount determined by the budget amount determination unit 102d is 0 and the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e is 0, and determines that the order identification information corresponding to the extracted combinations is unapproved or on hold.

[0039] When there are cost items subject to reservation determination and cost items not subject to reservation determination that have been selected in advance, the reservation determination unit 102h extracts, from combinations of order identification information and cost items for which the cumulative cost amount exceeding 0 has been aggregated by the cost amount aggregation unit 102b, combinations where the current-stage budget amount determined by the budget amount determination unit 102d is 0, the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e is 0, and that have the cost items subject to reservation determination selected in advance, and determines that the order identification information corresponding to the extracted combinations is unapproved or on hold.

[0040] The identification of whether a cost item is subject to reservation determination by the reservation determination unit 102h can be made based on the PJ cost item classification master in which the reservation determination classification indicating whether a cost item is subject to reservation determination or not subject to reservation determination is registered in advance for each cost item.

[0041] The check result output unit 102i outputs a notification indicating the existence of order identification information determined by the reservation determination unit 102h 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 of whether there is order identification information determined by the reservation determination unit 102h to be unapproved or on hold.

[0042] The check result output unit 102i can also output a notification indicating the existence of order identification information for which the contract approval status is unapproved or on hold. 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 for which the contract approval status is unapproved or on hold.

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

[0044] The communication interface unit 104 communicably 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 a communication line.

[0045] The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records a computer program for giving instructions to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory)·ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

[0046] Conceptually, the storage unit 106 includes a project basic information master storage unit 106a, a PJ cost item classification master storage unit 106b, a project information table storage unit 106c, a contract information table storage unit 106d, a budget information table storage unit 106e, a cost information table storage unit 106f, a landing prediction header table storage unit 106g, a landing prediction detail table storage unit 106h, and the like.

[0047] The project basic information master storage unit 106a stores the project basic information master. In the project basic information master, a landing forecast amount determination method is registered. Before automatically creating the landing forecast, the landing forecast amount determination method is selected and set in advance. The landing forecast amount determination method includes: when there is no final landing forecast amount for the previous month, determining the current stage budget amount as the final landing forecast amount for the current month; when there is a final landing forecast amount for the previous month, determining the final landing forecast amount for the previous month as the final landing forecast amount for the current month (the "previous month's landing forecast" method); regardless of whether there is a final landing forecast amount for the previous month, determining the current stage budget amount as the final landing forecast amount for the current month (the "latest budget" method). At least two landing forecast amount determination methods can be included.

[0048] The PJ cost item classification master storage unit 106b stores the PJ cost item classification master. In the PJ cost item classification master, for each cost item, a retention judgment target classification indicating whether the cost item is a retention judgment target or a non-retention judgment target is registered. Before automatically creating the landing forecast, the retention judgment target classification is selected and set in advance for each cost item.

[0049] The project information table storage unit 106c stores the project information table. In the project information table, for each project, project information such as project identification information and project name is stored. The project identification information is assigned one for each project and is composed of, for example, unique numbers and symbols.

[0050] The contract information table storage unit 106d stores the contract information table. In the contract information table, for each order received, contract information such as project identification information, order received identification information, order received name (contract name), accounting year and month, contract period, contract amount, contract approval status, and contract completion classification is stored. The order received identification information is assigned one for each order received (contract) and is composed of, for example, unique numbers and symbols. One project includes one or more orders received. Therefore, there is one or more order received identification information corresponding to one project identification information.

[0051] The budget information table storage unit 106e stores a budget information table. In the budget information table, budget information such as project identification information, order identification information, budget amount change identification information, accounting year and month, cost item, budget amount, budget approval status, etc. is stored by order identification information and cost item. In the budget information table, multiple budget amounts can be stored for the same order identification information and the same cost item. The change identification information is information for identifying their new and old, and is composed of, for example, unique numbers and symbols.

[0052] The cost information table storage unit 106f stores a cost information table. In the cost information table, cost information such as cost accounting identification information, project identification information, order identification information, accounting year and month, cost item, cost amount, etc. is stored by order identification information and cost item. The cost accounting identification information is assigned one for each cost accounting, and is composed of, for example, unique numbers and symbols.

[0053] The landing prediction header table storage unit 106g stores a landing prediction header table. In the landing prediction header table, landing prediction header records including the approval status of the final landing prediction are stored by order identification information, together with project identification information, order identification information, accounting year and month, creation classification of the final landing prediction, etc.

[0054] The landing prediction detail table storage unit 106h stores a landing prediction detail table. In the landing prediction detail table, landing prediction detail records including the final landing prediction amount for the current month and the planned future cost at the current month stage are stored by order identification information and cost item, together with project identification information, order identification information, accounting year and month, and cost item. The landing prediction detail records may further include the budget amount at the current stage, the cumulative cost amount up to the current month, and the budget difference for the current month.

[0055] An input / output interface unit 108 is connected to an input device 400 and an output device 500. The output device 400 includes a display device such as a display or a projector, an audio device such as a speaker, a printing device such as a printer, and also a device that can be downloaded in a data file format. The data file format can adopt a file format known in the art, such as PDF, CSV, document file, spreadsheet file, text file, etc. The input device 500 can use a monitor that realizes a pointing device function in cooperation with a mouse, in addition to a keyboard, a mouse, and a microphone.

[0056] [2. Specific Example] Hereinafter, using specific examples, the information processing for automatically creating a landing prediction by the accounting support device according to the present invention and the information processing at the time of applying for a change in the final landing prediction amount after automatically creating the landing prediction will be described.

[0057] FIG. 2 is a diagram showing the flow of the information processing for automatically creating a landing prediction in this specific example.

[0058] The aggregation target specifying unit 102a specifies the order number to be aggregated (i.e., order identification information) (S01), and the cost amount aggregation unit 102b aggregates the cumulative cost amount up to the current month by order number and by PJ cost item classification (i.e., cost item) (S02), and the budget amount determination unit 102d determines the current-stage budget amount (S03).

[0059] If the landing prediction amount determination unit 102e is pre-set such that the landing prediction automatic creation classification (i.e., landing prediction amount determination method) is "previous month's landing prediction" (S04 - YES), and further, if there is a final landing prediction amount for the previous month (S05 - YES), then by order number and by PJ cost item classification, the final landing prediction amount for the previous month is determined to be the final landing prediction amount for the current month (S06a).

[0060] On the other hand, when the landing prediction automatic creation classification is preset to "previous month's landing prediction" in the landing prediction amount determination unit 102e (S04 - YES), but there is no final landing prediction amount for the previous month (S05 - NO), or when the landing prediction automatic creation classification is preset to "latest budget" (S04 - NO), the budget amount at the current stage is determined as the final landing prediction amount for the current month by order number and PJ cost item classification (S06b).

[0061] The planned cost calculation unit 102f calculates the future planned cost at the current month stage by order number and PJ cost item classification (S07), and the budget difference calculation unit 102g calculates the budget difference for the current month (S08).

[0062] When there is a temporary work record in which the cumulative cost amount exceeds 0 and the budget amount is 0 and the final landing prediction amount is 0 (S09 - YES), the hold determination unit 102h determines that the approval status for the order number of this temporary work record is "on hold" for the predicted amount hold, and determines that the approval status for the other order number "JU001" is "approved" for the predicted amount approved (S10a).

[0063] On the other hand, when there is no temporary work record among W11 - W14·W16 in which the cumulative cost amount exceeds 0 and the budget amount is 0 and the final landing prediction amount is 0 (S09 - NO), the hold determination unit 102h determines that the approval status for all order numbers "JU001" and "JU002" is "approved" for the predicted amount approved (S10b).

[0064] The check result output unit 102i outputs the determination result (check result notification screen) (S11).

[0065] Figure 3 is a diagram showing the project basic information master and the PJ cost item classification master in this specific example. In the project basic information master in this specific example, three types of landing forecast automatic creation classifications (landing forecast amount determination methods), namely, "0 (not automatically created)", "1 (previous month's landing forecast)", and "2 (latest budget)", are registered. "0 (not automatically created)" is a setting that does not perform the implementation of landing forecast automatic creation itself. In the PJ cost item classification master in this specific example, four types of PJ cost item classifications, namely, "material cost", "outsourcing cost", "labor cost", and "expenses", and the corresponding suspense registration classification (suspense determination target classification) of "0: no" for non-target suspense determination or "1: yes" for target suspense determination at the time of planned cost automatic creation are registered for each PJ cost item classification.

[0066] Figure 4 is a diagram showing the project information table and the contract information table in this specific example. In the project information table of this specific example, project information records storing the project number (i.e., project identification information) and the corresponding project name for each project are stored. In the contract information table of this specific example, contract information storing the project number, order receipt number (i.e., order receipt identification information), contract name, accounting month, contract period, contract amount, approval status, and completion classification for each order receipt number are stored.

[0067] Figures 5A and 6A are diagrams showing the budget information table and the cost information table in this specific example. Figure 5A shows the budget information table, the cost information table, and the cost information table for the first month (April 2023) at the start of landing forecast automatic creation, and Figure 6A shows the budget information table, the cost information table, and the cost information table for the month following the start of landing forecast automatic creation (May 2023).

[0068] In the budget information table of this specific example, a budget information table storing project number, order number, number of changes (i.e., change identification information), accounting year and month, PJ cost item classification, budget amount, and approval status is stored by order number (i.e., order identification information) and by PJ cost item classification (i.e., cost item). In the contract information table of this specific example, a contract information record storing cost accounting number, project number, order number, accounting year and month, PJ cost item classification, and cost amount is stored by order number and by PJ cost item classification.

[0069] Figures 5B, 6B, and 7A are diagrams showing the temporary work table in this specific example. Figure 5B shows the temporary work table for the first month (April 2023) when the automatic creation of landing prediction starts. Figure 6B shows the temporary work table for the month following the start of automatic creation of landing prediction (May 2023) when "previous month's landing prediction" is selected. Figure 7A shows the temporary work table for the month following the start of automatic creation of landing prediction (May 2023) when "latest budget" is selected.

[0070] In the temporary work table of this specific example, a temporary work record storing project number, order number, and PJ cost item classification is stored by order number and by PJ cost item classification. In each temporary work record, budget amount, cumulative cost amount, previous month's final landing prediction, final landing prediction, future planned cost, budget difference, and approval status can be stored. In Figures 5B, 6B, and 7A, temporary work table A shows the storage stage of budget amount, cumulative cost amount, and previous month's final landing prediction. Temporary work table B shows the storage stage of final landing prediction, future planned cost, and budget difference. Temporary work table C shows the storage stage of approval status, showing the passage of time in the order from temporary work table A to temporary work table C.

[0071] Figures 5C, 5E, 5F, 6C, and 7B are diagrams showing the landing prediction header table and the landing prediction details table in this specific example. Figure 5C shows the landing prediction header table and the landing prediction details table for the first month (April 2023) when the automatic creation of the landing prediction starts. Figure 6C shows the landing prediction header table and the landing prediction details table for the month following the start of the automatic creation of the landing prediction (May 2023) when "previous month's landing prediction" is selected. Figure 7B shows the landing prediction header table and the landing prediction details table for the month following the start of the automatic creation of the landing prediction (May 2023) when "latest budget" is selected. Also, Figure 5E shows the landing prediction header table and the landing prediction details table at the stage of applying for a change in the final landing prediction amount for the first month (April 2023) when the automatic creation of the landing prediction starts. Figure 5F shows the landing prediction header table and the landing prediction details table after the change is approved.

[0072] In the landing prediction header table of this specific example, landing prediction header records storing the project number, order number, accounting month, approval status, and creation classification are stored by order number. In the landing prediction details table of this specific example, landing prediction details records storing the project number, order number, accounting month, PJ cost item classification, budget amount, cumulative cost amount, final landing prediction, planned future cost, and budget difference are stored by order number and PJ cost item classification.

[0073] Figures 5D and 6D are diagrams showing the check result notification screen in this specific example. Figure 5D shows the check result notification screen for the first month (April 2023) when the automatic creation of the landing prediction starts. Figure 6D shows the check result notification screen for the month following the start of the automatic creation of the landing prediction (May 2023).

[0074] Hereinafter, based on the first to third cases, the details of the information processing flow for the automatic creation of the landing prediction and the information processing flow at the time of applying for a change in the final landing prediction amount after the automatic creation of the landing prediction will be described with reference to Figures 2 to 7B.

[0075] (First case: Automatic creation of the landing prediction when "previous month's landing prediction" is selected) Taking April 2023 as the first month to start automatically creating the landing forecast, the information processing flow of automatically creating the landing forecast in April 2023, the first month, and May 2023, the following month, when "1 (previous month's landing forecast)" is selected as the landing forecast automatic creation classification (landing forecast amount determination method) will be described in detail.

[0076] In this first case, the landing forecast automatic creation classification (landing forecast amount determination method) in the project basic information master shown in Figure 3 is preset to "1 (previous month's landing forecast)". Therefore, when a landing forecast detail record including the previous month's accounting year and month is stored in the landing forecast detail table, the previous month's final landing forecast amount in the landing forecast detail record is determined to be the current month's final landing forecast amount.

[0077] In this first case, as shown in Figure 3, for the planned cost automatic creation suspension registration classification (suspension determination target classification) in the PJ cost item classification master, among the PJ cost item classifications, for "material cost", "outsourced cost", and "labor cost", the suspension determination target is preset to "1: do", and for "expenses", the suspension determination target is preset to "0: do not" (not subject to suspension determination). Therefore, "material cost", "outsourced cost", and "labor cost" are subject to suspension determination, and "expenses" are not subject to suspension determination.

[0078] As of April 2023, one project has been launched with the project number "PJ001". As shown in the project information table in Figure 4, a project information record A01 storing this project number and the corresponding project name is stored in the project information table.

[0079] For the project with project number "PJ001", there are two orders with order numbers (i.e., order identification information) "JU001" and "JU002". As shown in the contract information table of Figure 4, as contract information records corresponding to these orders, contract information records B01 and B02 storing these order numbers and the corresponding contract names, accounting years and months, contract periods, contract amounts, contract approval statuses, and contract completion classifications are stored in the contract information table.

[0080] "Approved" in the approval status of the contract information record indicates that the order has been contract-approved, and "Incomplete" in the completion classification indicates that the order is contract-incomplete.

[0081] For the order with order number "JU001", a budget with accounting year and month "2023 / 04" has been allocated individually for each of the three PJ cost item classifications (i.e., cost items) of "material cost", "outsourcing cost", and "expenses". As shown in the budget information table of Figure 5A, as budget information records corresponding to these three PJ cost item classifications, three budget information records C01 - C03 storing the project number, order number, number of changes to the budget amount (i.e., change identification information), accounting year and month, PJ cost item classification, budget amount, and approval status are stored in the budget information table. Similarly, for the order with order number "JU002", a budget with accounting year and month "2023 / 04" has been allocated individually for each of the three PJ cost item classifications (cost items), and as shown in the budget information table of Figure 5A, three budget information records C04 - C06 are stored in the budget information table.

[0082] "Approved" in the approval status of the budget information record indicates that the budget has been budget-approved.

[0083] The number of changes in the budget amount of the budget information record is used to distinguish between old and new budget information records when the budget amount is accepted multiple times for the same order number and the same PJ cost item classification. When a new budget information record is stored separately, the number of changes is the number obtained by adding 1 to the number of changes in the latest budget information record having the same order number and the same PJ cost item classification. Therefore, the budget amount of the budget information record with the largest number of changes becomes the latest 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.

[0084] First, based on the contract information table in FIG. 4, the aggregation target specifying unit 102a specifies the order numbers "JU001" and "JU002" to be aggregated as the order numbers for which the completion status is "uncompleted" for contract uncompleted and the approval status is "approved" for contract approved (S01).

[0085] Next, based on the voucher information serving as the cost such as the purchase information stored in the voucher information database, the cost amount aggregating unit 102b aggregates the cost amount for the accounting month "2023 / 04" by order number and by PJ cost item classification, and stores cost information records D01 to D05 in which the project number, order number, order number, accounting month, PJ cost item classification, and cost amount are stored in the cost information table as shown in the cost information table of FIG. 5A.

[0086] The cost amount aggregation unit 102b sums up the cost amounts stored in the cost information records D01 to D05 corresponding to the order numbers "JU001" and "JU002" specified by the aggregation target identification unit 102a, and having an accounting year and month before the current month "2023 / 04", for each order number and for each PJ cost item classification, and aggregates the cumulative cost amount up to the current month (S02). Note that in the cost information table of Fig. 5A, there are no cost information records having an accounting year and month before the previous month "2023 / 03", and only the cost information records D01 to D05 having the accounting year and month of the current month "2023 / 04" are stored. Therefore, the cost amounts of the cost information records D01 to D05 respectively become the cumulative cost amounts up to the current month as they are.

[0087] As shown in the temporary work table A of Fig. 5B, the detail table update unit 102c stores the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b in each of the temporary work records W11 to W16, for each order number and for each PJ cost item classification.

[0088] Note that for the combination of the order number "JU002" and the PJ cost item classification "outsourcing cost", as there is a corresponding budget information record stored in the budget information table of Fig. 5A, the budget is allocated. However, since there is no cost information record having an accounting year and month up to the current month "2023 / 04" in the cost information table, the cumulative cost amount is stored in the temporary work table as "￥0", like in the temporary work record W15.

[0089] The budget amount determination unit 102d extracts the latest budget information records C01 to C06 with the largest number of change times among the budget information records that correspond to the order numbers "JU001" and "JU002" specified by the aggregation target specification unit 102a stored in the budget information table of FIG. 5A, have an accounting year before the current month "2023 / 04", and have an approval status of budget approval completed "Approved", for each order number and for each PJ cost item classification. Note that in the budget information table of FIG. 5A, "0" has the largest number of change times for each combination of order number and PJ cost item classification.

[0090] The budget amount determination unit 102d determines, for each order number and for each PJ cost item classification, that the latest budget amounts included in the extracted latest budget information records C01 to C06 are the budget amounts at the current stage as they are (S03).

[0091] As shown in the temporary work table A of FIG. 5B, the detail table update unit 102c stores the budget amounts at the current stage determined by the budget amount determination unit 102d in each of the temporary work records W11 to W16, for each order number and for each PJ cost item classification.

[0092] Since it is the first month of automatic landing prediction, and there are no landing prediction detail records including the accounting year of the previous month stored in the landing prediction detail table, the detail table update unit 102c stores "NULL" as the previous month's final landing prediction amount in each of the temporary work records W11 to W16, as shown in the temporary work table A of FIG. 5B.

[0093] In the first case, the landing prediction amount determination unit 102e has the landing prediction automatic creation classification (landing prediction amount determination method) preset to "1 (previous month's landing prediction)" (S04 - YES). However, since it is the first month of automatic landing prediction creation, there is no landing prediction detail record containing the previous month's accounting year and month stored in the landing prediction detail table (S05 - NO). Also, since the previous month's final landing prediction amount in the temporary work table A in Fig. 5B is "NULL", the budget amount at the current stage determined by the budget amount determination unit 102d for each order number and PJ cost item classification (i.e., the budget amounts stored in each temporary work record W11 - W16) is directly determined as the final landing prediction amount for the current month (S06b).

[0094] As shown in the temporary work table B in Fig. 5B, the detail table update unit 102c stores the final landing prediction amount for the current month determined by the landing prediction amount determination unit 102e in each of the temporary work records W11 - W16 for each order number and PJ cost item classification.

[0095] The planned cost calculation unit 102f calculates the future planned cost at the current month stage by subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b from the final landing prediction amount for the current month determined by the landing prediction amount determination unit 102e for each order number and PJ cost item classification (i.e., by subtracting the cumulative cost amount from the final landing prediction amounts of the temporary work records W11 - W16 in the temporary work table B in Fig. 5B) (S07).

[0096] As shown in the temporary work table B in Fig. 5B, the detail table update unit 102c stores the future planned cost at the current month stage calculated by the planned cost calculation unit 102f in each of the temporary work records W11 - W16 for each order number and PJ cost item classification.

[0097] The budget variance calculation unit 102g calculates the budget variance for the current month (S08) by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e from the budget amount at the current stage determined by the budget amount determination unit 102d for each order number and for each PJ cost item classification (that is, by subtracting the final landing forecast amount from the budget amounts of the temporary work records W11 to W16 in the temporary work table B in FIG. 5B). As shown in the temporary work table B in FIG. 5B, since the budget amount at the current stage and the final landing forecast amount for the current month are the same for each combination of order number and PJ cost item classification, the budget variance is "￥0" for all combinations.

[0098] As shown in the temporary work table B in FIG. 5B, 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 for each order number and for each PJ cost item classification.

[0099] Since there is no temporary work record among W11 to W14 and W16 in which the cumulative cost amount exceeds 0 and the budget amount is 0 and the final landing forecast amount is 0 (S09 - NO), the hold determination unit 102h determines that the approval status is "approved" with the forecast amount approved for all order numbers "JU001" and "JU002" (S10b).

[0100] As shown in the temporary work table C in FIG. 5B, the detail table update unit 102c stores "approved" with the forecast amount approved as the approval status in the temporary work records W11 to W16 having the order numbers "JU001" and "JU002" determined by the hold determination unit 102h to have the forecast amount approved.

[0101] As shown in the landing prediction header table of Fig. 5C, the detail table update unit 102c newly stores in the landing prediction detail table the landing prediction header records E11 and E12, which consist of the project number, order number, accounting month "2023 / 04 (current month)", approval status "approved" determined by the hold determination unit 102h, and creation classification "automatically created" indicating that the final landing prediction amount has been automatically determined, for each order number.

[0102] As shown in the landing prediction detail table of Fig. 5C, the detail table update unit 102c newly stores in the landing prediction detail table, as landing prediction detail records F11 to F16, the records obtained by adding the accounting month "2023 / 04 (current month)" to each combination of the project number, order number, PJ cost item classification, budget amount, cumulative cost amount, final landing prediction amount, planned future cost, and budget difference stored in the temporary work records W11 to W16.

[0103] As shown in the contract information table of Fig. 4, the check result output unit 102i determines that the approval status in all contract information records B01 and B02 is "approved", as shown in the budget information table of Fig. 5A, the approval status in all budget information records C01 to C06 is "approved", and as shown in the temporary work table C of Fig. 5B, the approval status in all landing prediction header records E11 and E12 is "approved". Based on this determination result, as shown in Fig. 5D, with the accounting month as the current month "2023 / 04", for all of the unapproved slip checks (contract), unapproved slip checks (budget), and unapproved slip checks (landing prediction), it outputs a check result notification screen with the check result as "〇" and the error count as "0" (S11).

[0104] In the following month, May 2023, the landing prediction automatic creation classification (landing prediction amount determination method) in the project basic information master shown in Figure 3 has not been changed since the first month, April 2023, and remains set to "1 (previous month's landing prediction)". Also, regarding the project information table and contract information table in Figure 4, as of May 2023, there have been no changes since April 2023.

[0105] On the other hand, regarding the budget information table, due to changes in the budgets for each order with order numbers "JU001" and "JU002", a new budget with the accounting month "2023 / 05" has been allocated. As shown in the budget information table in Figure 6A, the budget receiving section 102k has newly stored budget information records C07 - C12 with a change count of "1" and an accounting month of "2023 / 05" in the budget information table, separate from the budget information records C01 - C06 with a change count of "0" and an accounting month of "2023 / 04".

[0106] First, in May 2023 as well, the aggregation target specifying section 102a specifies the order numbers "JU001" and "JU002" of the aggregation targets based on the contract information table in Figure 4, similar to April 2023 (S01).

[0107] Next, the cost amount aggregation section 102b aggregates the cost amounts for the accounting month "2023 / 05" based on the cost - related voucher information such as the purchase information stored in the voucher information database, by order number and by PJ cost item classification. As shown in the cost information table in Figure 6A, cost information records D06 - D12 containing the project number, order number, order number, accounting month, PJ cost item classification, and cost amount are stored in the cost information table.

[0108] The cost amount aggregation 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" specified by the aggregation target specifying unit 102a, are classified by order number and PJ cost item classification, and have an accounting year and month prior to the current month "2023 / 05", and aggregates the cumulative cost amount up to the current month (S02). In the cost information table of Fig. 6A, cost information records D01 to D05 with the accounting year and month of the previous month "2023 / 04" and cost information records D06 to D12 with the accounting year and month of the current month "2023 / 05" are stored, and cost information records with an accounting year and month prior to the month before last "2023 / 03" are not stored. Therefore, the sum of the cost amount of the cost information record of the previous month "2023 / 04" and the cost amount of the cost information record of the current month "2023 / 05", classified by order number and PJ cost item classification, becomes the cumulative cost amount up to the current month.

[0109] Specifically, for the combination of the order number "JU001" and the PJ cost item classification "material cost", the cumulative cost amount is the sum of the cost amount of "￥200,000" in the cost information record D01 for the previous month "2023 / 04" and the cost amount of "￥300,000" in the cost information record D06 for the current month "2023 / 05", which is "￥500,000". For the combination of the order number "JU001" and the PJ cost item classification "outsourcing cost", the cumulative cost amount is the sum of the cost amount of "￥200,000" in the cost information record D02 for the previous month "2023 / 04" and the cost amount of "￥500,000" in the cost information record D07 for the current month "2023 / 05", which is "￥700,000". For the combination of the order number "JU001" and the PJ cost item classification "expenses", the cumulative cost amount is the sum of the cost amount of "￥50,000" in the cost information record D03 for the previous month "2023 / 04" and the cost amount of "￥150,000" in the cost information record D08 for the current month "2023 / 05", which is "￥200,000". For the combination of the order number "JU002" and the PJ cost item classification "material cost", the cumulative cost amount is the sum of the cost amount of "￥200,000" in the cost information record D04 for the previous month "2023 / 04" and the cost amount of "￥300,000" in the cost information record D09 for the current month "2023 / 05", which is "￥500,000". For the combination of the order number "JU002" and the PJ cost item classification "outsourcing cost", since there is no cost information record for the previous month "2023 / 04", the cost amount of "￥1,000,000" in the cost information record D10 for the current month "2023 / 05" becomes the cumulative cost amount as it is. For the combination of the order number "JU002" and the PJ cost item classification "expenses", the cumulative cost amount is the sum of the cost amount of "￥20,000" in the cost information record D05 for the previous month "2023 / 04" and the cost amount of "￥200,000" in the cost information record D11 for the current month "2023 / 05", which is "￥220,000". For the combination of the order number "JU002" and the PJ cost item classification "labor cost", since there is no cost information record for the previous month "2023 / 04", the cost amount of "￥100,000" in the cost information record D12 for the current month "2023 / 05" becomes the cumulative cost amount as it is.

[0110] As shown in the temporary work table A of FIG. 6B, the detail table update unit 102c stores the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b in each of the temporary work records W21 to W27 by order number and by PJ cost item classification.

[0111] The budget amount determination unit 102d corresponds to the order numbers "JU001" and "JU002" specified by the order number specification unit 102a stored in the budget information table of FIG. 6A by order number and by PJ cost item classification, has an accounting month before the current month "2023 / 05", and among the budget information records with an approval status of budget approved "approved", extracts the latest budget information records C07 to C12 having the largest number of change times. In the budget information table of FIG. 6A, "1" is the largest number of change times for each combination of order number and PJ cost item classification.

[0112] The budget amount determination unit 102d determines, by order number and by PJ cost item classification, that the latest budget amount included in the extracted latest budget information records C07 to C12 is the current stage budget amount as it is (S03).

[0113] As shown in the temporary work table A of FIG. 5B, the detail table update unit 102c stores the current stage budget amount determined by the budget amount determination unit 102d in each of the temporary work records W21 to W27 by order number and by PJ cost item classification.

[0114] Note that for the combination of order number "JU002" and PJ cost item classification "labor cost", since a cost information record having the accounting month of the current month "2023 / 05" is stored in the cost information table of FIG. 6A, the cumulative cost amount up to the current month "2023 / 05" has been calculated. However, since there is no corresponding budget information record in the budget information table, the budget amount is set to "￥0" and stored in the temporary work table like the temporary work record W27.

[0115] As shown in Fig. 5C, since the landing prediction detail records F11 - F16 including the accounting month of the previous month "2023 / 04" are stored in the landing prediction detail table, as shown in the temporary work table A in Fig. 6B, in each of the temporary work records W21 - W27, the final landing prediction amounts in the landing prediction detail records F11 - F16 including the accounting month of the previous month "2023 / 04" in the landing prediction detail table in Fig. 5C are stored as the final landing prediction amounts of the previous month, by order number and by PJ cost item classification.

[0116] Note that for the combination of order number "JU002" and PJ cost item classification "labor cost", since there is no corresponding landing prediction detail record including the accounting month of the previous month "2023 / 04" in the landing prediction detail table in Fig. 5C, the final landing prediction amount of the previous month is stored in the temporary work table as "￥0", like the temporary work record W27.

[0117] In this first case, for the landing prediction amount determination part 102e, the landing prediction automatic creation classification (landing prediction amount determination method) is preset to "1 (previous month's landing prediction)" (S04 - YES), and further, the landing prediction detail records F11 - F16 including the accounting month of the previous month "2023 / 04" are stored in the landing prediction detail table (S05 - YES). Since the final landing prediction amounts of the previous month in each of the temporary work records W21 - W27 in the temporary work table A in Fig. 6B are not "NULL", the final landing prediction amounts in the landing prediction detail records F11 - F16 including the accounting month of the previous month "2023 / 04" in the landing prediction detail table in Fig. 5C (that is, the final landing prediction amounts of the previous month stored in each of the temporary work records W21 - W27) are directly determined as the final landing prediction amounts of the current month (S06a).

[0118] As shown in the temporary work table B in Fig. 6B, the detail table update part 102c stores the final landing prediction amounts of the current month determined by the landing prediction amount determination part 102e in each of the temporary work records W21 - W27, by order number and by PJ cost item classification.

[0119] Similar to April 2023, for May 2023, the planned cost calculation unit 102f calculates the planned cost for the future at the current month stage (S07) by subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b from the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e for each order number and for each PJ cost item classification (that is, by subtracting the cumulative cost amount from the final landing forecast amounts of the temporary work records W21 to W27 in the temporary work table B in FIG. 6B). Note that when the cumulative cost amount is larger than the final landing forecast amount, such as in the case of the temporary work record W27 in the temporary work table B in FIG. 6B, the planned cost for the future becomes a negative value.

[0120] As shown in the temporary work table B in FIG. 6B, the detail table update unit 102c stores the planned cost for the future at the current month stage calculated by the planned cost calculation unit 102f in each of the temporary work records W21 to W27 for each order number and for each PJ cost item classification.

[0121] The budget variance calculation unit 102g calculates the budget variance for the current month (S08) by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e from the budget amount at the current stage determined by the budget amount determination unit 102d for each order number and for each PJ cost item classification (that is, by subtracting the final landing forecast amount from the budget amounts of the temporary work records W21 to W27 in the temporary work table B in FIG. 6B).

[0122] As shown in the temporary work table B in FIG. 6B, 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 for each order number and for each PJ cost item classification.

[0123] Since there is a temporary work record W27 among the temporary work records W21 to W27 whose cumulative cost amount exceeds 0, and the budget amount is 0 and the predicted final landing amount is 0 (S09 - YES), the retention determination unit 102h identifies this, and for the order number "JU002" of the identified temporary work record W27, determines that the approval status is "reserved" for the predicted amount, and for the other order number "JU001", determines that the approval status is "approved" for the predicted amount (S10a).

[0124] As shown in the temporary work table C of FIG. 6B, the detail table update unit 102c stores "reserved" for the predicted amount as the approval status in the temporary work records W24 to W27 having the order number "JU002" determined by the retention determination unit 102h to be "reserved" for the predicted amount, and stores "approved" for the predicted amount as the approval status in the temporary work records W21 to W23 having the order number "JU001" determined to be "approved" for the predicted amount.

[0125] Similar to April 2023, as shown in the predicted landing header table of FIG. 6C, the detail table update unit 102c newly stores a predicted landing header record E21 having the accounting month "2023 / 05 (current month)", the order number "JU001", the approval status "approved" determined by the retention determination unit 102h, and the creation classification "automatically created" indicating that the final predicted landing amount was automatically determined in the predicted landing detail table for each order number. For the order number "JU002", a predicted landing header record E22 having the approval status "reserved" determined by the retention determination unit 102h and the creation classification "automatically created" indicating that the final predicted landing amount was automatically determined is newly stored in the predicted landing detail table (in the predicted landing header table of FIG. 6C, the predicted landing header records E11 and E12 for the accounting month "2023 / 04 (previous month)" are omitted).

[0126] As shown in the landing prediction details table of FIG. 6C, the details table update unit 102c newly stores, in the landing prediction details table, as landing prediction details records F21 to F27, records obtained by adding the accounting year and month "2023 / 05 (current month)" to each combination of the project number, order number, PJ cost item classification, budget amount, cumulative cost amount, final landing prediction amount, planned cost in the future, and budget difference stored in the temporary work records W21 to W27 (in the landing prediction details table of FIG. 6C, the landing prediction details records F11 to F16 for the accounting year and month "2023 / 04 (previous month)" are omitted).

[0127] As shown in the contract information table of FIG. 4, the check result output unit 102i determines that the approval status in all contract information records B01 and B02 is "approved" for contract approval, and as shown in the budget information table of FIG. 6A, the approval status in all budget information records C07 to C12 is "approved" for budget approval. However, as shown in the temporary work table C of FIG. 6B, among the two landing prediction header records E21 and E22, it is determined that the approval status in the landing prediction header record E22 is "reserved" for the prediction amount. Based on this determination result, as shown in FIG. 6D, with the accounting year and month being the current month "2023 / 05", for the unapproved voucher check (contract) and unapproved voucher check (budget), the check result is set to "〇", and for the unapproved voucher check (landing prediction), the check result is set to "×", and a check result notification screen with the error count set to "1" is output (S11).

[0128] (Second case: Automatic creation of landing prediction when "latest budget" is selected) Taking April 2023 as the first month to start automatic creation of landing prediction, the information processing flow of automatic creation of landing prediction in the first month when "2 (latest budget)" is selected as the landing prediction automatic creation classification (landing prediction amount determination method) will be described in detail.

[0129] In this second case, except for selecting "2 (latest budget)" as the landing prediction automatic creation classification (landing prediction amount determination method), the settings and conditions are exactly the same as those in the first case described above.

[0130] First, similar to April 2023 of the first case, the order number aggregation target specifying unit 102a specifies the order numbers "JU001" and "JU002" to be aggregated (S01).

[0131] Similar to April 2023 of the first case, the cost amount aggregation unit 102b aggregates the cumulative cost amount based on the order numbers "JU001" and "JU002" specified by the order number aggregation target specifying unit 102a (S02), the budget amount determination unit 102d determines the current stage budget amount (S03), and the detail table update unit 102c stores the cumulative cost amount and budget amount similar to those in April 2023 of the first case in the temporary work records W11 to W16 as shown in the temporary work table A in FIG. 5B, and further stores "NULL" similar to that in April 2023 of the first case as the previous month's final landing forecast amount.

[0132] In this second case, since the landing forecast automatic creation classification (landing forecast amount determination method) is preset to "2 (latest budget)" in the landing forecast amount determination unit 102e (S04-NO), regardless of whether there is a landing forecast detail record including the accounting month of the previous month in the landing forecast detail table, the current stage budget amount determined by the budget amount determination unit 102d (that is, the budget amount stored in each of the temporary work records W11 to W16) is directly determined as the final landing forecast amount for the current month (S06b), and the final landing forecast amount similar to that in April 2023 of the first case is stored in the temporary work records W11 to W16 as shown in the temporary work table B in FIG. 5B.

[0133] Similar to April 2023 in the first case, the planned cost calculation unit 102f calculates the future planned cost at the current month stage (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 similar to those in April 2023 of the first case in the temporary work records W11 to W16 as shown in the temporary work table B in FIG. 5B. Similar to April 2023 in the first case, the hold determination unit 102h stores "Approved" with the forecast amount approved as the approval status in the temporary work records W11 to W16 as shown in the temporary work table C in FIG. 5B (S09-NO·S10b).

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

[0135] In the next month, May 2023, the landing forecast automatic creation classification (landing forecast amount determination method) in the project basic information master shown in FIG. 3 has not been changed from the first month, April 2023, and is still set to "2 (latest budget)". Also, regarding the project information table and contract information table in FIG. 4, as of May 2023, there has been no change from April 2023.

[0136] On the other hand, regarding the budget information table, similar to May 2023 in the first case, due to changes in the budgets of each order with order numbers "JU001" and "JU002", as shown in the budget information table in FIG. 6A, the budget receiving unit 102k newly stores the budget information records C07 to C12 with the change count "1" and the accounting year and month "2023 / 05" in the budget information table.

[0137] First, in May 2023 as well, the order number identification unit 102a identifies the order numbers "JU001" and "JU002" based on the contract information table in Fig. 4, similar to April 2023 in this second case (S01).

[0138] Similar to May 2023 in the first case, the cost amount aggregation unit 102b aggregates the cost amounts for the accounting month "2023 / 05" by order number and by PJ cost item classification based on the voucher information stored in the voucher information database, and stores the cost information records D06 - D12 in the cost information table as shown in Fig. 6A in the cost information table.

[0139] Similar to May 2023 in the first case, the cost amount aggregation unit 102b sums up the cost amounts stored in the cost information records D01 - D12 corresponding to the order numbers "JU001" and "JU002" identified by the order number identification unit 102a, which have accounting months before the current month "2023 / 05", by order number and by PJ cost item classification, and aggregates the cumulative cost amount up to the current month (S02). The detail table update unit 102c stores the cumulative cost amount up to the current month in each of the temporary work records W31 - W37 as shown in the temporary work table A in Fig. 7A.

[0140] Similar to May 2023 in the first case, the budget amount determination unit 102d extracts the latest budget information records C07 - C12 with the largest number of change times from the budget information records corresponding to the order numbers "JU001" and "JU002" identified by the order number identification unit 102a, which are stored in the budget information table in Fig. 6A, have accounting months before the current month "2023 / 05", and have an approval status of budget approved "Approved", and determines the latest budget amounts included in the extracted latest budget information records C07 - C12 as the current stage budget amounts as they are (S03). The detail table update unit 102c stores the current stage budget amounts in each of the temporary work records W31 - W37 as shown in the temporary work table A in Fig. 7A.

[0141] In the second case, since the landing prediction automatic creation classification (landing prediction amount determination method) is preset to "2 (latest budget)" in the landing prediction amount determination unit 102e (S04-NO), regardless of whether a landing prediction detail record including the previous month's accounting month is stored in the landing prediction detail table as in April 2023, for each order number and for each PJ cost item classification, the budget amount at the current stage determined by the budget amount determination unit 102d (that is, the budget amount stored in each temporary work record W31 to W37) is determined as the final landing prediction amount for the current month as it is (S06b). As shown in the temporary work table B in FIG. 7A, the final landing prediction amount determined by the landing prediction amount determination unit 102e is stored in each of the temporary work records W31 to W37.

[0142] Similar to April 2023, the planned cost calculation unit 102f subtracts, for each order number and for each PJ cost item classification for May 2023, the cumulative cost amount up to the current month aggregated by the cost amount aggregation unit 102b from the final landing prediction amount for the current month determined by the landing prediction amount determination unit 102e (that is, by subtracting the cumulative cost amount from the final landing prediction amounts of the temporary work records W31 to W37 in the temporary work table B in FIG. 7A) to calculate the planned cost for the future at the current month stage (S07). As shown in the temporary work table B in FIG. 7A, the detail table update unit 102c stores the planned cost for the future at the current month stage in each of the temporary work records W31 to W37. Note that when the cumulative cost amount is larger than the final landing prediction amount, as in the case of the temporary work record W37 in the temporary work table B in FIG. 7A, the planned cost for the future becomes a negative value.

[0143] The budget difference calculation unit 102g calculates the budget difference for the current month (S08) by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination unit 102e from the current stage budget amount determined by the order number and PJ cost item classification by the budget amount determination unit 102d (that is, by subtracting the final landing forecast amount from the budget amounts of the temporary work records W31 to W37 in the temporary work table B in Fig. 7A). The detail table update unit 102c stores the budget difference for the current month in each of the temporary work records W31 to W37 as shown in the temporary work table B in Fig. 7A.

[0144] The reservation determination unit 102h identifies the temporary work record W37 among the temporary work records W31 to W37 whose cumulative cost amount exceeds 0, where the budget amount is 0 and the final landing forecast amount is 0 (S09 - YES). For the order number "JU002" of the identified temporary work record W37, it determines that the approval status is "reserved" for the forecast amount reservation, and for the other order number "JU001", it determines that the approval status is "approved" for the forecast amount approval (S10a).

[0145] The detail table update unit 102c stores "reserved" for the forecast amount reservation as the approval status in the temporary work records W34 to W37 having the order number "JU002" determined by the reservation determination unit 102h to be "reserved" for the forecast amount reservation, and stores "approved" for the forecast amount approval as the approval status in the temporary work records W31 to W33 having the order number "JU001" determined to be "approved" for the forecast amount approval, as shown in the temporary work table C in Fig. 7A.

[0146] As shown in the landing prediction header table of Fig. 7B, the detail table update unit 102c newly stores in the landing prediction detail table a landing prediction header record E31 having an accounting month "2023 / 05 (current month)", an order number "JU001", an approval status "approved" determined by the hold determination unit 102h, and a creation classification "automatically created" indicating that the final landing prediction amount has been automatically determined. For the order number "JU002", a landing prediction header record E32 having an approval status "on hold" determined by the hold determination unit 102h and a creation classification "automatically created" indicating that the final landing prediction amount has been automatically determined is newly stored in the landing prediction detail table (in the landing prediction header table of Fig. 7B, the landing prediction header records E11 and E12 for the accounting month "2023 / 04 (previous month)" are omitted).

[0147] As shown in the landing prediction detail table of Fig. 7B, the detail table update unit 102c newly stores in the landing prediction detail table records obtained by adding the accounting month "2023 / 05 (current month)" to each combination of project number, order number, PJ cost item classification, budget amount, cumulative cost amount, final landing prediction amount, future planned cost, and budget difference stored in the temporary work records W31 to W37 as landing prediction detail records F31 to F37 (in the landing prediction detail table of Fig. 7B, the landing prediction detail records F11 to F16 for the accounting month "2023 / 04 (previous month)" are omitted).

[0148] As shown in the contract information table of FIG. 4, the approval status in all contract information records B01 and B02 of the check result output unit 102i is "Approved" for contract approval. As shown in the budget information table of FIG. 6A, the approval status in all budget information records C07 to C12 is "Approved" for budget approval. However, as shown in the temporary work table C of FIG. 7C, among the two landing prediction header records E31 and E32, it is determined that the approval status in the landing prediction header record E32 is "Reserved" for the predicted amount. Based on this determination result, as shown in FIG. 7C, the accounting month is set to the current month "2023 / 05", and for the unapproved voucher check (contract) and unapproved voucher check (budget), the check result is set to "〇", and for the unapproved voucher check (landing prediction), the check result is set to "×", and an error count of "1", and a check result notification screen is output (S11).

[0149] (Case 3: Application for change of the final landing prediction amount after automatic creation of landing prediction) The information processing flow after accepting a change application when changing a specific final landing prediction amount in the landing prediction detail table of FIG. 5C finally created in the April 2023 stage of Case 1 or Case 2 will be described in detail.

[0150] First, user A inputs a change application to change the final landing prediction amount of the combination of the order number "JU002" and the PJ cost item classification "outsourcing cost" in the landing prediction detail table of FIG. 5C from "￥4,000,000" to "￥5,000,000".

[0151] Based on the input of user A's change application, the change reception unit 102j accepts the application for changing the final landing prediction amount together with the order number "JU002", the PJ cost item classification "outsourcing cost", and the change application amount "￥5,000,000".

[0152] The detail table update unit 102c updates the final landing forecast amount of the landing forecast detail record F15 corresponding to the combination of the order number "JU002" received by the change reception unit 102j and the PJ cost item classification "outsourcing cost" from "￥4,000,000" in the landing forecast detail table of FIG. 5C to the change application amount "￥5,000,000" received by the change reception unit 102j as shown in the landing forecast detail table of FIG. 5E.

[0153] The planned cost calculation unit 102f subtracts the cumulative cost amount aggregated by the cost amount aggregation unit 102b from the final landing forecast amount updated by the detail table update unit 102c to calculate the future planned cost. On the other hand, the budget variance calculation unit 102g calculates the monthly budget variance by subtracting the final landing forecast amount from the budget amount of the landing forecast detail record F15.

[0154] As shown in the landing forecast detail table of FIG. 5E, the detail table update unit 102c updates the future planned cost and the budget variance in the landing 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, respectively.

[0155] In addition, the detail table update unit 102c updates the approval status of the landing forecast header record E12 corresponding to the order number "JU002" received by the change reception unit 102j from "approved for forecast amount" (approved) in the landing forecast detail table of FIG. 5C to "application for forecast amount change" (under application) as shown in the landing forecast header table of FIG. 5E. For the creation classification, it is also updated from "automatically created" in the landing forecast detail table of FIG. 5C to the creation classification "manually entered" indicating that user A manually entered it as shown in the landing forecast header table of FIG. 5E.

[0156] Next, another user B who confirmed that the approval status of the landing forecast header record E12 of the order number "JU002" in the landing forecast header table of FIG. 5E is "under application for forecast amount change" approved the change application for the final landing forecast amount of the order number "JU002" and entered the approval of the change application.

[0157] The change reception unit 102j receives the approval of the change application for the order number "JU002" based on the input of the approval by User B.

[0158] As shown in the landing prediction header table of FIG. 5F, the detail table update unit 102c updates the approval status of the landing prediction header record E12 corresponding to the order number "JU002" received by the change reception unit 102j from "application in progress" in the prediction amount change application stage in the landing prediction detail table of FIG. 5E to "approved" with the predicted amount approved as shown in the landing prediction header table of FIG. 5F. In this way, the change based on the change application for the final landing prediction amount is finalized.

[0159] As described above, according to the system of the present invention, for projects that have not made particular progress since the last review or projects where only costs simply accumulate, the data registration cost can be reduced by automatically creating the landing prediction. Also, when changing the budget, cost information, etc. of a project, the cost of reexamining the landing prediction can be reduced by automatically updating the landing prediction based on the changed data. Further, when an unexpected cost occurs, such as in the case of a budget compilation omission, and it is detected by automatic creation, the risk such as a budget compilation omission can be reduced by forcing a review.

[0160] [3. Contribution to the United Nations Sustainable Development Goals (SDGs)] According to this embodiment, since it can contribute to improving business efficiency and promoting appropriate business judgment of the enterprise, it is possible to contribute to Goals 8 and 9 of the SDGs.

[0161] Also, according to this embodiment, since it can contribute to reducing waste loss and promoting paperless and digitalization, it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0162] Also, according to this embodiment, since it can contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

[0163] [4. Other Embodiments] Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments.

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

[0165] In addition, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in the above documents and drawings, they can be arbitrarily changed unless otherwise specified.

[0166] Regarding the PC100, each illustrated component is a functional concept, and it is not necessarily physically configured as illustrated.

[0167] For example, regarding the processing functions provided by each device constituting the PC100, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the information processing apparatus to execute the processes described in this embodiment, and is mechanically read by each device as necessary. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving commands to the CPU in cooperation with the OS to perform various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes the control unit in cooperation with the CPU.

[0168] Further, this computer program may be stored in an application program server connected to the PC100 via an arbitrary network, and it is also possible to download all or part of it as necessary.

[0169] Also, the program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, and it can also be configured as a first program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an 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 Disk), and a Blu-ray (registered trademark) Disc.

[0170] Also, the "program" is a data processing method described in an arbitrary language or description method, and it does not matter whether it is in the form of source code or binary code, etc. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0171] The various databases and the like stored in the memory unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0172] Further, the PC 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which an arbitrary peripheral device is connected. Further, the PC 100 may be realized by mounting software (including a program or data, etc.) that realizes the processes described in this embodiment on the PC 100.

[0173] Furthermore, the specific forms of the distribution and integration of the devices are not limited to those illustrated, and all or a part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0174] The present invention is useful in many industries that need to calculate the landing prediction with reference to budget and cost information, etc. for each project, such as the construction industry and the IT industry.

Explanation of Signs

[0175] 100 PC 102 Control Unit 102a Aggregation Target Specifying Unit 102b Cost Amount Aggregation Unit 102c Detail Table Update Unit 102d Budget Amount Determination Unit 102e Landing Prediction Amount Determination Unit 102f Planned Cost Calculation Unit 102g Budget Difference Calculation Unit 102h Suspension Judgment Unit 102i Check result output section 102j Change reception section 102k Budget reception section 104 Communication interface section 106 Memory section 106a Project basic information master memory section 106b PJ cost item classification master memory section 106c Project information table memory section 106d Contract information table memory section 106e Budget information table memory section 106f Cost information table memory section 106g Landing prediction header table memory section 106h Landing prediction detail table memory section 108 Input / output interface section 200 Server 300 Network 400 Input device 500 Output device

Claims

1. An accounting support device comprising a control unit, wherein the control unit is a cost amount aggregation means for aggregating the cumulative cost amount up to the current month by order identification information and cost item; is a budget amount determination means for, for each order identification information and cost item, when there is a corresponding budget amount, extracting the latest corresponding budget amount from among the corresponding budget amounts, determining the extracted budget amount as the current-stage budget amount, and when there is no corresponding budget amount, determining 0 as the current-stage budget amount; is a landing forecast amount determination means for, according to a pre-selected landing forecast amount determination method, for each order identification information and cost item, (1) determining the current-stage budget amount determined by the budget amount determination means as the final landing forecast amount for the current month, or (2) when there is no final landing forecast amount for the previous month, determining the current-stage budget amount determined by the budget amount determination means as the final landing forecast amount for the current month, and when there is a final landing forecast amount for the previous month, determining the final landing forecast amount for the previous month as the final landing forecast amount for the current month; is a planned cost calculation means for, for each order identification information and cost item, subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation means from the final landing forecast amount for the current month determined by the landing forecast amount determination means to calculate the planned cost for the future at the current month stage; An accounting support device characterized by comprising the above.

2. wherein the control unit is a detail table update means for newly storing in the landing forecast detail table a landing forecast detail record including the final landing forecast amount for the current month determined by the landing forecast amount determination means, the planned cost for the future at the current month stage calculated by the planned cost calculation means, and the accounting year and month, for each order identification information and cost item, with the current month as the accounting year and month; The accounting support device according to Claim 1, characterized by comprising the above.

3. wherein the control unit is a hold determination means for extracting a combination of order identification information and cost item for which a cumulative cost amount exceeding 0 has been aggregated by the cost amount aggregation means and for which the current-stage budget amount determined by the budget amount determination means is 0 and the final landing forecast amount for the current month determined by the landing forecast amount determination means is 0, and determining that the order identification information corresponding to the extracted combination is unapproved or on hold; The accounting support device according to Claim 1, characterized by comprising the above.

4. wherein the hold determination means Among the combinations, extract a combination in which the current budget amount determined by the budget amount determination means is 0, the final landing forecast amount for the current month determined by the landing forecast amount determination means is 0, and which has a cost item of a hold determination target selected in advance, and determine that the order identification information corresponding to the extracted combination is unapproved or on hold. The accounting support device according to claim 3, characterized in that.

5. The control unit, A check result output means for outputting a notification that there is order identification information for which the hold determination means has determined that it is unapproved or on hold. The accounting support device according to claim 3 or 4, characterized in that it comprises.

6. The control unit, Budget reception means for receiving a budget amount for each order identification information and each cost item, and enabling reception of the budget amount multiple times for the same order identification information and the same cost item. The accounting support device according to claim 1, further comprising.

7. The control unit, Budget difference calculation means for calculating, for each order identification information and each cost item, the budget difference for the current month obtained by subtracting the final landing forecast amount for the current month determined by the landing forecast amount determination means from the current budget amount determined by the budget amount determination means. further comprising, The detail table update means, For each order identification information and each cost item, newly store in the landing forecast detail table a landing forecast detail record including the final landing forecast amount for the current month, the planned cost for the future at the current stage, and the accounting year and month, as well as the budget difference for the current month calculated by the budget difference calculation means. The accounting support device according to claim 2, characterized in that.

8. The control unit, Change reception means for receiving, for each order identification information and each cost item, an application for change of the final landing forecast amount in the landing forecast detail record including the latest accounting year and month stored in the landing forecast detail table, together with the order identification information, the cost item, and the change application amount. further comprising, The detail table update means, Update the final landing forecast amount in the landing forecast detail record including the latest accounting year and month corresponding to the order identification information and cost item received by the change reception means to the change application amount received by the change reception means. The accounting support device according to claim 2, characterized in that.

9. An accounting support method executed in an accounting support device including a control unit, Executed by the control unit, A cost amount aggregation step of aggregating the cumulative cost amount up to the current month for each order identification information and each cost item. For each order identification information and cost item, if there is a corresponding budget amount, extract the latest corresponding budget amount from the corresponding budget amounts, determine the extracted budget amount as the current-stage budget amount, and if there is no corresponding budget amount, determine 0 as the current-stage budget amount, a budget amount determination step; According to a preselected landing forecast amount determination method, for each order identification information and cost item, (1) determine the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, or (2) if there is no final landing forecast amount for the previous month, determine the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, and if there is a final landing forecast amount for the previous month, determine the final landing forecast amount for the previous month as the final landing forecast amount for the current month, a landing forecast amount determination step; For each order identification information and cost item, subtract the cumulative cost amount up to the current month aggregated by the cost amount aggregation step from the final landing forecast amount for the current month determined by the landing forecast amount determination step to calculate the planned cost for the future at the current month stage, a planned cost calculation step; An accounting support method characterized by including the above.

10. An accounting support program for causing an accounting support device provided with a control unit to execute, For causing the control unit to execute, A cost amount aggregation step of aggregating the cumulative cost amount up to the current month for each order identification information and cost item; For each order identification information and cost item, if there is a corresponding budget amount, extract the latest corresponding budget amount from the corresponding budget amounts, determine the extracted budget amount as the current-stage budget amount, and if there is no corresponding budget amount, determine 0 as the current-stage budget amount, a budget amount determination step; According to a preselected landing forecast amount determination method, for each order identification information and cost item, (1) determine the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, or (2) if there is no final landing forecast amount for the previous month, determine the current-stage budget amount determined by the budget amount determination step as the final landing forecast amount for the current month, and if there is a final landing forecast amount for the previous month, determine the final landing forecast amount for the previous month as the final landing forecast amount for the current month, a landing forecast amount determination step; A planned cost calculation step of calculating the future planned cost at the current month stage by subtracting the cumulative cost amount up to the current month aggregated by the cost amount aggregation step from the final landing forecast amount of the current month determined by the landing forecast amount determination step for each order identification information and each cost item. An accounting support program, characterized by including the above.

Images