Business support device, business support method, and business support program

Abstract

We provide business support devices that can easily compile full-year profit and loss forecasts based on the likelihood of receiving orders. [Solution] The business support device includes an acquisition unit that acquires information on the amount of an order associated with the planned order date and the probability of receiving the order; an extraction unit that extracts information on the amount of the order in which the probability of receiving the order satisfies a first condition related to the probability of receiving the order, and information on the amount of the order in which the probability of receiving the order satisfies a second condition related to the probability of receiving the order, and the planned order date satisfies a third condition related to the period; and an input / output unit that outputs information calculated based on the information on the amount of the order.

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] Patent Document 1 discloses a technique capable of outputting a KPI (Key Performance Indicator) in response to an instruction from a user. In this technique, the total sales of project budget information and the outlook amount by probability are displayed on a screen. In the display column of the screen, the total sales of project budget information is displayed as a bar graph, the outlook amount by probability is displayed as a stacked graph, and the budget and the outlook amount are also displayed in a table.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In industries that perform project-based revenue and expenditure management, such as the construction industry and the information technology industry, it is required to timely grasp the expected profit and loss through ventilation. At that time, it was difficult to associate the information related to orders input in a business system such as a project management system with the actual results related to sales and costs managed on a management accounting system.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a business support device, a business support method, and a business support program capable of easily aggregating the expected profit and loss for the current fiscal year according to the order accuracy.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention includes: an acquisition unit that acquires information on the amount of an order associated with the planned order date and the probability of receiving the order; an extraction unit that extracts information on the amount of the order in which the probability of receiving the order satisfies a first condition relating to the probability of receiving the order, and information on the amount of the order in which the probability of receiving the order satisfies a second condition relating to the probability of receiving the order and the planned order date satisfies a third condition relating to the period; and an input / output unit that outputs information calculated based on the information on the amount of the order.

[0007] Furthermore, the business support method according to the present invention is a business support method performed by a business support device equipped with a control unit, wherein the control unit performs an acquisition step of acquiring information on the amount of an order associated with the planned order date and the probability of receiving the order; an extraction step of extracting information on the amount of the order in which the probability of receiving the order satisfies a first condition relating to the probability of receiving the order; and information on the amount of the order in which the probability of receiving the order satisfies a second condition relating to the probability of receiving the order and the planned order date satisfies a third condition relating to the period; and an output step of outputting information calculated based on the information on the amount of the order.

[0008] Furthermore, the business support program according to the present invention is a business support program to be executed by a business support device equipped with a control unit, wherein the control unit is caused to execute an acquisition step to acquire information on the amount of an order associated with the planned order date and the probability of receiving the order; an extraction step to extract information on the amount of the order in which the probability of receiving the order satisfies a first condition relating to the probability of receiving the order, and information on the amount of the order in which the probability of receiving the order satisfies a second condition relating to the probability of receiving the order and the planned order date satisfies a third condition relating to the period; and an output step to output information calculated based on the information on the amount of the order. [Effects of the Invention]

[0009] According to the present invention, it is possible to easily compile full-year profit and loss forecasts based on the probability of receiving orders. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a schematic diagram showing an example of order information extracted in this embodiment. [Figure 2] Figure 2 is a block diagram showing an example of a business support system according to the embodiment. [Figure 3] Figure 3 shows an example of an account master stored in the master storage unit of the business support device according to the embodiment. [Figure 4] Figure 4 shows an example of an order probability master and a system control master stored in the master storage unit of the project management device according to the embodiment. [Figure 5] Figure 5 shows an example of the information stored in the data storage unit of the project management device according to this embodiment. [Figure 6] Figure 6 shows an example of order data stored in the data storage unit of the project management device according to the embodiment. [Figure 7] Figure 7 shows an example of sales forecast data stored in the data storage unit of the project management device according to this embodiment. [Figure 8] Figure 8 shows an example of budget data stored in the data storage unit of the project management device according to the embodiment. [Figure 9] Figure 9 shows an example of sales data stored in the data storage unit of the project management device according to the embodiment. [Figure 10] Figure 10 shows an example of procurement data stored in the data storage unit of the project management device according to the embodiment. [Figure 11] Figure 11 shows an example of the conditions and content to be transferred for extracting data linked from order data to journal entry data according to the embodiment. [Figure 12] Figure 12 shows an example of the conditions and content of data to be extracted from order data and linked to journal entry data according to the embodiment. [Figure 13]FIG. 13 is a diagram showing an example of conditions for extracting data linked from sales forecast data to journal data and posting details according to the embodiment. [Figure 14] FIG. 14 is a diagram showing another example of conditions for extracting data linked from sales data to journal data and posting details according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of conditions for extracting data linked from budget data to journal data and posting details according to the embodiment. [Figure 16] FIG. 16 is a diagram showing an example of conditions for extracting data linked from purchase data to journal data and posting details according to the embodiment. [Figure 17] FIG. 17 is a diagram showing an example of journal data stored in the data storage unit of the business support device according to the embodiment. [Figure 18] FIG. 18 is a diagram showing an example of the condition input screen according to the embodiment. [Figure 19] FIG. 19 is a diagram showing an example of conditions for extracting data linked from journal data and extraction details according to the embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the result output screen according to the embodiment. [Embodiment for Implementing the Invention]

[0011] Hereinafter, embodiments of the business support device, business support method, and business support program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0012] [1. Overview] First, information on the amount related to an order, which is extracted in the embodiment, will be described with reference to FIG. 1. FIG. 1 is a schematic diagram showing an example of information related to an order extracted in the embodiment. Note that the "information on the amount related to an order" in the embodiment includes, in addition to the credit amount related to the order described later, the credit amount related to sales and the debit amount related to the cost described later.

[0013] In this embodiment, a "reference date," such as the present time, and a "rank criterion" relating to the period to be extracted are set. Furthermore, two levels of likelihood of securing a project are set, such as "high rank" and "medium rank," to indicate the probability of winning the project. The reference date, rank criterion, and high and medium ranks can be specified, for example, in the condition input screen shown in Figure 18, which will be explained later. The following describes the case where the "rank criterion" is "2 months."

[0014] As shown in Figure 1, for the period from the beginning of the fiscal year to the reference date, only the order amount for projects that have already been confirmed, or the sales amount that has already been made, i.e., actual results, are included in the calculation.

[0015] Furthermore, prior to the "rank criteria," for example, if the reference date is set to the first month, only projects with a "high rank" probability of being awarded will be included in the calculation for the period up to the "second month."

[0016] Furthermore, for the period after the "rank criteria," that is, from the "third month" (when the reference date is the first month) to the end of the period, in addition to projects with a "high rank" probability of securing a contract, projects with a "medium rank" probability of securing a contract will also be included in the calculation. Projects that do not fall into either the "high rank" or "medium rank" probability of securing a contract will not be included in the calculation, regardless of the period.

[0017] [2. Structure] An example of the configuration of a business support system including the business support device according to this embodiment will be described with reference to Figure 2, etc. Figure 2 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a business support system. As shown in Figure 2, the business support system 1 according to this embodiment has a business support device 100 and a project management device 600 connected via a network 300. Note that the project management device 600 is an example of an external device.

[0018] The business support device 100 and project management device 600 shown in Figure 2 are commercially available desktop personal computers. However, the business support device 100 and project management device 600 are not limited to stationary information processing devices such as desktop personal computers; they may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0019] The business support device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each component of the business support device 100 is connected to communicate via any communication path.

[0020] The communication interface unit 104 connects the business support device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 has the function of communicating data with other devices and via communication lines. Here, the network 300 has the function of connecting the business support device 100 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). The data stored in the storage unit 106 may be stored in, for example, the server 200.

[0021] The input / output interface unit 108 is connected to an input device 400 and an output device 500. The output device 500 can be a monitor (including a home television), a speaker, or a printer. The input device 400 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. In the following, the output device 500 may be referred to as the monitor 500, and the input device 400 as the keyboard 400 or mouse 400.

[0022] The storage unit 106 stores various databases, tables, and files. The storage unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used. As shown in Figure 2, the storage unit 106 has a master storage unit 106a and a data storage unit 106b. The data storage unit 106b stores the journal entry data 106ba, which will be explained later.

[0023] As shown in Figure 3, the master storage unit 106a stores the account master 106aa. Figure 3 is a diagram showing an example of the account master 106aa stored in the master storage unit 106a of the business support device 100 according to this embodiment. The account master 106aa stores the account name, ordering source, rank, and budget / actual classification associated with the account code. The "account code" is assigned to the data stored by the project management device 600, which will be described later. The "account name" indicates the name of the account corresponding to the account code. The "source" indicates the data stored by the project management device 600, which will be described later, that is associated with the account code. The "rank" indicates the rank of the order probability registered in the source data. The "budget / actual classification" indicates whether the data registered in the source is an estimate or a confirmed actual.

[0024] For example, the account code "S0101" shown in the first row of Figure 3 is named "Order Scheduled_Rank A" and is assigned to data in the "Order Data" (Order Data 606ba), which will be explained later, where the rank is "Rank A" and the forecast / actual classification is "Forecast". Similarly, the account code "S0601" shown in the last row of Figure 3 is named "Actual Cost" and is assigned to data in the "Purchase Data" (Purchase Data 606be), which will be explained later, where the forecast / actual classification is "Actual". Note that, as will be explained later, "Rank" is not registered in Purchase Data 606be.

[0025] Returning to Figure 2, we will continue the explanation of the configuration of the business support device 100. The control unit 102 is a CPU or the like that comprehensively controls the business support device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 102 comprises an acquisition unit 102a, an input / output unit 102b, and an extraction unit 102c.

[0026] The acquisition unit 102a acquires various data stored in the project management device 600 and stores them in conjunction with the journal entry data 106ba. The processing performed by the acquisition unit 102a will be explained in detail later.

[0027] The input / output unit 102b displays the condition input screen and the result output screen on the monitor 500. Details of the condition input screen and the result output screen will be described later. The input / output unit 102b also outputs the conditions entered on the condition input screen, which will be described later, to the extraction unit 102c.

[0028] The extraction unit 102c uses the conditions output from the input / output unit 102b to refer to the journal entry data 106ba and extract data that matches the conditions. The extraction unit 102c also calculates the extracted data as an amount to be displayed on the result output screen and outputs it to the input / output unit 102b.

[0029] As shown in Figure 2, the project management device 600 has a control unit 602 and a storage unit 606. The project management device 600 may also have an input / output interface unit and a communication interface unit (not shown), similar to the business support device 100, and may be connected to input devices and output devices (not shown).

[0030] As shown in Figure 2, the storage unit 606 has a master storage unit 606a and a data storage unit 606b. As shown in Figure 4, the master storage unit 606a stores the order probability master 606aa and the system control master 606ab. Figure 4 is a diagram showing an example of the order probability master 606aa and system control master 606ab stored in the master storage unit 606a of the project management device 600 according to this embodiment.

[0031] The Order Probability Master 606aa stores "Order Probability Names" that categorize the likelihood of a project being awarded into ranks from A to D. The System Control Master 606ab stores the "Current Fiscal Year and Month," such as "April 2024." The Current Fiscal Year and Month stored in the System Control Master 606ab is automatically updated, for example, during monthly processing.

[0032] Order data 606ba stores various information about a project, associating it with the project number that identifies the project. Figure 6 shows an example of order data 606ba. As shown in Figure 6, order data 606ba stores the project number, associating it with the construction ID, contract status, rank, department, planned order date, order date, and order amount.

[0033] "Project No." is information used to identify the project in question, and "Construction ID" is information used to identify the construction work corresponding to that project. "Contract Status" indicates whether the project has been awarded or is in the inquiry stage. "Rank" indicates the likelihood of winning the project. "Department" indicates the department that has won or is expected to win the project. "Expected Award Date" and "Award Date" indicate the expected and actual award dates for the project, respectively. "Amount of Awarded Contract" indicates the amount of the awarded contract for the project.

[0034] In this embodiment, the order data 606ba is entered, for example, by the order-taking staff of each department. For example, the first row of the order data 606ba shown in Figure 6 stores that the project with project number "P63001" is a "construction project A" that has been "ordered" by the "head office" department, and that its rank is "A rank". The planned order date for this project is "February 1, 2024", the actual order date is "February 5, 2024", and the order amount is "30 million yen".

[0035] The sales forecast data 606bb stores information about the sales forecast for the projects stored in the order data 606ba. Figure 7 shows an example of the sales forecast data 606bb. As shown in Figure 7, the sales forecast data 606bb stores the sales forecast date, the sales forecast amount, the rank, and the sold flag, in association with the project number and construction ID.

[0036] The "Sold" flag indicates whether the project has been sold or whether the sale has not yet been recorded. For example, in the first row shown in Figure 7, it is recorded that "Project A" under project number "P63001" is "Sold".

[0037] Budget data 606bd stores the budget for costs in each project. Figure 8 shows an example of budget data 606bd. As shown in Figure 8, budget data 606bd stores the budget for each target month (April 2024 to June 2024), associated with the project number and construction ID. For example, the second row in Figure 8 stores that for project number "P64006" and "Construction F", costs of "12 million yen" are scheduled to be incurred in April 2024 and "10 million yen" in May 2024.

[0038] Sales data 606bc stores information about completed sales. Figure 9 shows an example of sales data 606bc. As shown in Figure 9, sales data 606bc stores the sales date and the sales amount, associated with the project number and construction ID. For example, in sales data 606bc, the sales date and sales amount corresponding to the project number and construction ID of projects with a sales flag of "completed" among the data stored in sales forecast data 606bb shown in Figure 7 are transferred to the sales date and sales amount fields.

[0039] The procurement data 606be stores the amount of cost incurred for each project. Figure 10 shows an example of procurement data 606be. As shown in Figure 10, procurement data 606be stores the procurement date and cost amount, associated with the project number and construction ID.

[0040] [3. Processing executed by acquisition unit 102a] In this embodiment, the acquisition unit 102a of the control unit 102 of the business support device 100 stores various types of data, as shown in Figures 5 to 10, which are stored in the data storage unit 606b of the project management device 600, in conjunction with the journal entry data 106ba. Figure 11 is a diagram showing an example of the conditions for extracting data linked from order data 606ba to journal entry data 106ba and the content of the transfer according to this embodiment. The acquisition unit 102a performs data linking processing at intervals such as daily or monthly.

[0041] As shown in Figure 11, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. 1. The "Account Master.Source" is "Order Data". 2. The "Account Master - Budget / Actual Classification" is set to "Actual". 3. The "Order Data.Contract Type" is "Order". 4. The "Month of Order" is the "Current Fiscal Year and Month". In this process, the acquisition unit 102a extracts four data items ba1 from the data stored in the order data 606ba shown in Figure 6.

[0042] Then, the acquisition unit 102a transfers the "Order Date" from the order data 606ba to the "Date Occurred" field in the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Order Amount" from the order data 606ba to the "Debit Amount" and "Credit Amount" fields in the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of these data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0043] Through this process, the data ba11 shown in Figure 11 is stored in the journal entry data 106ba. For example, the first row of data ba11 contains the data for project No. "P63009" from the order data 606ba shown in Figure 6, with the department "Head Office", order date "April 10, 2024", and order amount "35 million yen". In addition, the account code "S0201: Order Results" from the account master 106aa shown in Figure 4, whose source is "Order Data" and whose budget / actual classification is "Actual", is also transferred to data ba11.

[0044] Furthermore, as shown in Figure 12, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. Figure 12 is a diagram showing an example of the conditions and content of the transfer for extracting data linked from order data 606ba to journal entry data 106ba according to the embodiment. 1. The "Account Master.Source" is "Order Data". 2. The "Account Master - Forecast / Actual Classification" is set to "Forecast". 3. The "Order Data. Contract Type" is "Inquiry". 4. "Order Data. Order Probability" is the same as "Account Master. Rank". In this process, the acquisition unit 102a extracts eight data items ba2 from the data stored in the order data 606ba shown in Figure 6.

[0045] Then, the acquisition unit 102a transfers the "Scheduled Order Date" from the order data 606ba to the "Date of Occurrence" field of the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Order Amount" from the order data 606ba to the "Debit Amount" and "Credit Amount" fields of the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of these data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0046] Through this process, the data ba21 shown in Figure 12 is stored in the journal entry data 106ba. For example, the first row of data ba21 contains the department "Head Office", the planned order date "May 5, 2024", and the order amount "2 million yen" from the project number "P63013" in the order data 606ba shown in Figure 6. In addition, the account code "S0101: Planned Order_A Rank" from the account master 106aa shown in Figure 4, whose source is "Order Data", whose budget / actual classification is "Forecast", and whose rank is "A Rank", is also transferred to data ba21.

[0047] Furthermore, as shown in Figure 13, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. Figure 13 is a diagram showing an example of the conditions and content of data to be extracted from sales forecast data 606bb to be linked to journal entry data 106ba according to the embodiment. 1. The "Account Master.Source" is "Sales Projection Data". 2. The "Account Master - Forecast / Actual Classification" is set to "Forecast". 3. The "Sales forecast data.Sales completed flag" is "Not sold". 4. "Sales forecast data.rank" is the same as "Account master.rank". In this process, the acquisition unit 102a extracts 16 data entries bb2 from the data stored in the sales forecast data 606bb shown in Figure 7.

[0048] Then, the acquisition unit 102a transfers the "Scheduled Sales Date" from the Scheduled Sales Data 606bb to the "Date of Occurrence" field of the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Scheduled Sales Amount" from the Scheduled Sales Data 606bb to the "Debit Amount" and "Credit Amount" fields of the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of these data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0049] Through this process, the data bb11 shown in Figure 13 is stored in the journal entry data 106ba. For example, the first row of data bb11 contains the planned sales date "May 31, 2024", the planned sales amount "25 million yen", and the department "Head Office" from the order data 606ba, which correspond to the project number "P63005" in the planned sales data 606bb shown in Figure 7. In addition, the account code "S0301: Planned Sales_A Rank" from the account master 106aa shown in Figure 4, which originates from "Planned Sales Data", has a forecast / actual classification of "Forecast", and has a rank of "A Rank", is transferred to data bb11.

[0050] Furthermore, as shown in Figure 14, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. Figure 14 is a diagram showing an example of the conditions for extracting data linked from sales data 606bc to journal entry data 106ba and the contents of the transfer according to the embodiment. 1. The "Account Master.Source" is "Sales Data". 2. The "Account Master - Budget / Actual Classification" is set to "Actual". 3. The "month of sales" is the "current accounting year and month." In this process, the acquisition unit 102a extracts four data points bc1 from the data stored in the sales data 606bc shown in Figure 9.

[0051] Then, the acquisition unit 102a transfers the "Sales Date" from the sales data 606bc to the "Date of Occurrence" field of the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Sales Amount" from the sales data 606bc to the "Debit Amount" and "Credit Amount" fields of the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of these data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0052] Through this process, the data bc11 shown in Figure 14 is stored in the journal entry data 106ba. For example, the first row of data bc11 contains the sales date "April 30, 2024", the sales amount "30 million yen", and the department "Head Office" from the order data 606ba corresponding to the sales data 606bc shown in Figure 9, which corresponds to project number "P63001". In addition, the account code "S0501: Sales Results" from the account master 106aa shown in Figure 4, whose source is "Sales Data" and whose budget / actual classification is "Actual", is also posted to data bc11.

[0053] Furthermore, as shown in Figure 15, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. Figure 15 is a diagram showing an example of the conditions and content of data to be extracted from budget data 606bd to be linked to journal entry data 106ba according to the embodiment. 1. The "Account Master.Source" is "Budget Data". 2. The "Account Master - Forecast / Actual Classification" is set to "Forecast". In this process, the acquisition unit 102a extracts eight data items bd1 from the data stored in the budget data 606bd shown in Figure 8.

[0054] Then, the acquisition unit 102a transfers the last day of the budget year and month in which a budget amount is entered from the budget data 606bd to the "Date of Occurrence" field of the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Budgeted Amount" from the budget data 606bd to the "Debit Amount" and "Credit Amount" fields of the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of the data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0055] Through this process, the data bd11 shown in Figure 15 is stored in the journal entry data 106ba. For example, the first row of data bd11 contains the budget amount "8 million yen" for project No. "P63005" from the budget data 606bd shown in Figure 8, the last day of the budget month in which the budget amount is entered "April 30, 2024", and the department "Head Office" from the order data 606ba corresponding to the project No. In addition, the account code "S0401: Estimated Cost" from the account master 106aa shown in Figure 4, whose source is "budget data" and whose budget / actual classification is "estimated", is also posted to data bd11.

[0056] Furthermore, as shown in Figure 16, the acquisition unit 102a extracts data from the data storage unit 606b of the project management device 600 that satisfies the following conditions. Figure 16 is a diagram showing an example of the conditions and content of data to be extracted from the purchase data 606be to be linked to the journal entry data 106ba according to the embodiment. 1. The "Account Master.Source" is "Purchase Data". 2. The "Account Master - Budget / Actual Classification" is set to "Actual". 3. The "Purchase Month" is the "Current Accounting Year and Month". In this process, the acquisition unit 102a extracts four data items be1 from the data stored in the purchase data 606be shown in Figure 10.

[0057] Then, the acquisition unit 102a transfers the "Purchase Date" from the purchase data 606be to the "Date Occurred" field of the journal entry data 106ba. Similarly, the acquisition unit 102a transfers the "Cost Amount" from the purchase data 606be to the "Debit Amount" and "Credit Amount" fields of the journal entry data 106ba. In addition, the acquisition unit 102a transfers the "Department" from the order data 606ba to the "Credit Department" field, and the "Account Code" from the account master 106aa to the "Credit Account" field. Note that in all of these data, "9990: For Management Accounting Linkage (Fixed)" is entered in the "Debit Account" field, and the "Credit Department" field is left blank.

[0058] Through this process, the data be11 shown in Figure 16 is stored in the journal entry data 106ba. For example, the first row of data be11 contains the purchase date "April 30, 2024" and the cost amount "25 million yen" from the purchase data 606be shown in Figure 10, for project number "P63009". In addition, the account code "S0601: Actual Cost" from the account master 106aa shown in Figure 4, whose source is "Purchase Data" and whose budget / actual classification is "Actual," is also transferred to data be11.

[0059] As a result of the acquisition unit 102a performing the above processing, the data storage unit 106b of the storage unit 106 of the business support device 100 stores the journal entry data 106ba shown in Figure 17. Figure 17 is a diagram showing an example of the journal entry data 106ba stored in the data storage unit 106b of the business support device 100 according to this embodiment.

[0060] [4. Processing performed by the input / output unit 102b and the extraction unit 102c] Next, the processes executed by the business support device 100 will be described. First, the input / output unit 102b displays a condition input screen, as shown in Figure 18, on the monitor 500 in response to instructions from a user (not shown), for example. Figure 18 is a diagram showing an example of the condition input screen S1 according to the embodiment. As shown in Figure 18, the condition input screen S1 has a section SC1 that accepts input of high-rank order probability, a section SC2 that accepts input of medium-rank order probability, a section SC3 that accepts input of rank criteria, and a section SC4 that accepts input of reference date. Each section SC1 to SC4 can take any configuration that accepts user input (not shown), such as a text box or a pull-down menu.

[0061] In Figure 18, "Reference Date" is a condition relating to the date used as the basis for calculation. "High Rank Order Probability" and "Medium Rank Order Probability" are conditions relating to the rank of the monetary information for the order being calculated. The High Rank Order Probability entered in Part SC1 is an example of the first condition relating to order probability, and the Medium Rank Order Probability entered in Part SC2 is an example of the second condition relating to order probability.

[0062] The rank criteria entered in Part SC3 are conditions related to whether to calculate only the monetary information for orders corresponding to high-rank order probability, or to calculate only the monetary information for orders corresponding to medium-rank order probability in addition to high-rank order probability. Note that the high-rank order probability entered in Part SC3 is an example of the third condition regarding the expected order timing.

[0063] For example, as shown in Figure 18, if the reference date is "April 30, 2024," then the "two months" including the reference date, i.e., "April 2024" and "May 2024," will be the period for which only monetary information related to orders corresponding to high-rank order probability will be included in the calculation. In this case, only monetary information related to orders corresponding to medium-rank order probability from "June 2024" onwards will be included in the calculation. Furthermore, data corresponding to ranks that do not fall under either high-rank or medium-rank order probability (rank D shown in Figure 3) will not be included in the calculation, regardless of whether or not it is included in the period corresponding to the rank criteria.

[0064] In addition, the condition input screen S1 may further include a section where other conditions, such as "department," can be specified.

[0065] Next, the extraction unit 102c uses the conditions entered in each part SC1 to SC4 of the condition input screen S1 to extract data that matches the conditions from the journal entry data 106ba shown in Figure 17. For example, if the conditions shown in Figure 18 are entered, the processing shown in Figure 19 will be performed. Figure 19 is a diagram showing an example of the conditions and content of data to be extracted from the journal entry data 106ba according to the embodiment. In the following, as shown in Figure 19, the target will be those in which the month and year of occurrence is "April 2024" and the "debit department" or "credit department" is "Head Office".

[0066] Furthermore, the input / output unit 102b generates a result output screen S2, as shown in Figure 20, using the amount calculated by the extraction unit 102c, and outputs it to the monitor 500. Figure 20 is a diagram showing an example of the result output screen S2 according to the embodiment. In Figure 20, an example is shown where the start date is "April 1, 2024" and the end date is "March 31, 2025". In addition, the calculation results are entered into the "Total" item JS02, the "Cost Ratio" item GR02, etc., after the amounts have been transferred to the other items.

[0067] The extraction unit 102c calculates the sum of the credit amounts for the data that meet the following conditions from the journal entry data 106ba, as the "actual" order value, for each accounting year and month. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Order Data". 3. The "Account Master - Budget / Actual Classification" is "Actual". In this process, the extraction unit 102c extracts two data entries JJ41 from the journal entry data 106ba shown in Figure 17 and calculates the total credit amount for April 2024, which is "72 million yen". The calculation result JJ42 is then displayed on the result output screen S2.

[0068] Furthermore, the extraction unit 102c calculates the total credit amounts of the data from the journal entry data 106ba that meet the following conditions, for each accounting year and month, as the "forecast (high rank)" order volume. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Order Data". 3. The "Account Master Rank" is included in the "High Rank" entered on the condition input screen S1. In the condition input screen S1 shown in Figure 18, "Rank A" and "Rank B" are entered as "High Rank" in section SC1. In this case, the extraction unit 102c extracts three data entries JH51 from the journal entry data 106ba shown in Figure 17 that correspond to "Rank A" or "Rank B". It then calculates the total credit amount of the data with an occurrence date of "May 2024", which is "55 million yen". The calculation result JH52 is output to the result output screen S2. Note that the three data entries JH51 do not include any data with an occurrence date of "June 2024" or later, so the calculation result JH62 is "0".

[0069] Furthermore, the extraction unit 102c calculates the total credit amounts of the data from the journal entry data 106ba that meet the following conditions, for each accounting year and month, as the order value for "forecast (medium rank)". 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Order Data". 3. The "Journal Entry Data.Date of Occurrence" does not fall within the period corresponding to the "Rank Criteria" entered on the Condition Input Screen S1. 4. The "Account Master Rank" is included in the "Medium Rank" entered on the condition input screen S1. In the condition input screen S1 shown in Figure 18, "Rank C1", "Rank C2", and "Rank C3" are entered as "Medium Rank" in section SC1. In this case, the extraction unit 102c extracts one data entry JM61 from the journal entry data 106ba shown in Figure 17 as data for June 2024, and calculates the total credit amount of "55 million yen". The calculation result JM62 is output to the result output screen S2.

[0070] On the other hand, even if a journal entry in the 106ba data set falls under the "medium rank," if its occurrence date is "May 2024," it is included in the period corresponding to the "rank criteria" and therefore is not included in the calculation. The same applies to sales revenue that falls under the "medium rank," which will be explained later. For this reason, the result output screen S2 displays information JM52 and UM52 indicating that the data is not included in the calculation.

[0071] The input / output unit 102b then uses the amount calculated by the extraction unit 102c to generate a result output screen S2 as shown in Figure 20 and outputs it to the monitor 500. Figure 20 is a diagram showing an example of the result output screen S2 according to the embodiment. In Figure 20, an example is shown where the start date is "April 1, 2024" and the end date is "March 31, 2025". In addition, the calculation results are entered into the "Total" item JS02, the "Cost Ratio" item GR02, etc., after the amounts have been transferred to the other items.

[0072] Furthermore, orders and sales corresponding to "Rank D" are not included in the calculation, regardless of whether they are included in the "Rank Criteria," because "Rank D" is not entered in either section SC1 or SC2 shown in Figure 18.

[0073] Furthermore, the extraction unit 102c calculates the total credit amounts of the data from the journal entry data 106ba that meet the following conditions, for each accounting year and month, as the "actual" sales figures. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Sales Data". In this process, the extraction unit 102c extracts two data entries UJ41 from the journal entry data 106ba shown in Figure 17 and calculates the total credit amount for April 2024, which is "55 million yen".

[0074] Furthermore, the extraction unit 102c calculates the total credit amounts of the data from the journal entry data 106ba that meet the following conditions, for each accounting month, as "projected (high rank)" sales revenue. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Sales Projection Data". 3. The "Account Master Rank" is included in the "High Rank" entered on the condition input screen S1. In this case, the extraction unit 102c extracts five data entries UH51 from the journal entry data 106ba shown in Figure 17 as data for May 2024, and calculates a total credit amount of "130 million yen". The extraction unit 102c also extracts four data entries UH61 as data for June 2024, and calculates a total credit amount of "92 million yen". The calculation results UH52 and UH62 are then output to the result output screen S2.

[0075] Furthermore, the extraction unit 102c calculates the total credit amounts of the data from the journal entry data 106ba that meet the following conditions, for each accounting year and month, as "projected (medium rank)" sales revenue. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Sales Projection Data". 3. The "Journal Entry Data.Date of Occurrence" does not fall within the period corresponding to the "Rank Criteria" entered on the Condition Input Screen S1. 4. The "Account Master Rank" is included in the "Medium Rank" entered on the condition input screen S1. In this case, the journal entry data 106ba shown in Figure 17 does not include any data with an occurrence date of "June 2024", so the calculation result UM62 is "0". On the other hand, although not displayed on the result output screen S2, the extraction unit 102c extracts data UM91 with an occurrence date of "September 2024" from the journal entry data 106ba and calculates the total credit amount of "30 million yen".

[0076] Furthermore, the extraction unit 102c calculates both "actual" and "forecast" costs. In this embodiment, since no rank is set for the "forecast" costs, all data stored in the journal entry data 106ba is included in the calculation for the amount GY52 for May 2024, which is included in the period corresponding to the "rank criteria".

[0077] The extraction unit 102c calculates the sum of the credit amounts for the data in the journal entry data 106ba that meet the following conditions, as the "actual" cost, for each accounting year and month. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Purchase Data". In this process, the extraction unit 102c extracts two data entries GJ41 from the journal entry data 106ba shown in Figure 17, the entries whose occurrence date is "April 2024", and calculates the total credit amount for April 2024, which is "45 million yen". The calculation result GJ42 is then displayed on the result output screen S2.

[0078] Furthermore, the extraction unit 102c calculates the total credit amounts of the journal entry data 106ba that meet the following conditions, as an "estimate" of the cost, for each accounting month. 1. The "Journal Entry Data.Credit Account Code" matches the "Account Master.Account Code". 2. The "Account Master.Source" is "Budget Data". In this case, the extraction unit 102c extracts six data entries GY41 with an occurrence date of "April 2024", six data entries GY51 with an occurrence date of "May 2024", and one data entry GY61 with an occurrence date of "June 2024" from the journal entry data 106ba shown in Figure 17. The calculated results GY42, GY52, and GY62 are then output to the result output screen S2.

[0079] According to the embodiment described above, the monetary information for orders with a high probability of being received is included in the calculation regardless of the expected timing of the order, while the monetary information for orders with a medium probability of being received is included in the calculation only if the third condition regarding the expected order is met. This makes it easy to aggregate the full-year profit and loss forecast according to the probability of receiving the order.

[0080] Furthermore, according to the embodiment, input of a first and second condition regarding the probability of receiving an order, and a third condition regarding the expected timing of the order, may be accepted. This makes it possible to calculate the full-year profit and loss forecast based on arbitrarily set conditions. Note that the system may also be configured to accept input of only one or two of the first to third conditions.

[0081] Furthermore, while we have described a configuration in which order amount information is linked from an external device such as the project management device 600, the configuration is not limited to this, and for example, order data such as order data 606ba may be stored in the business support device 100 in advance.

[0082] Furthermore, the business support device 100 according to this embodiment may extract only one of the information related to orders or the information related to sales, or it may further extract information related to costs.

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

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

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

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

[0087] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

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

[0089] Furthermore, with respect to the business support device 100 and the project management device 600, each component shown in the diagram is a functional concept and does not necessarily have to be physically configured as shown.

[0090] For example, the processing functions of the business support device 100 and the project management device 600, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the business support device 100 or the project management device 600 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0091] Furthermore, this computer program may be stored on an application program server connected to the business support device 100 and the project management device 600 via any network, and it is possible to download all or part of it as needed.

[0092] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

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

[0094] The various databases stored in the memory unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0095] Furthermore, the business support device 100 and the project management device 600 may be configured as known personal computers or workstations or other information processing devices, or as information processing devices to which any peripheral devices are connected. Alternatively, the business support device 100 and the project management device 600 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the devices.

[0096] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0097] This invention is useful in industries that use project-based revenue and expenditure management, such as the construction industry and the information technology industry. [Explanation of Symbols]

[0098] 1. Business support system 100 Business support equipment 102,602 Control Unit 102a Acquisition Department 102b Input / output section 102c Extraction part 104 Communication Interface Section 106,606 storage section 106a,606a Master Storage Unit 106aa Account Master 106b,606b Data storage section 106ba Journal entry data 108 Input / Output Interface Section 200 servers 300 Networks 400 Input Devices 400 keyboards 400 mice 500 Output Device 500 monitors 600 Project Management Devices 606aa Order Probability Master 606ab System Control Master 606ba Order Data 606bb Sales forecast data 606bc Sales Data 606bd Budget Data 606be Procurement Data

Claims

1. An acquisition unit that acquires information on the amount of an order associated with the expected order date and the probability of receiving the order, An extraction unit extracts information on the amount of the order for which the order probability satisfies a first condition regarding the order probability, and information on the amount of the order for which the order probability satisfies a second condition regarding the order probability, and the planned order timing satisfies a third condition regarding the period. An input / output unit that outputs information calculated based on the amount information related to the aforementioned order, A business support device equipped with the following features.

2. The input / output unit is, The system accepts input of the first condition, the second condition, and the third condition. A screen that accepts the aforementioned input is output. The business support device according to claim 1.

3. The business support device according to claim 1, wherein the acquisition unit acquires information on the amount related to the order from an external device.

4. The business support device according to claim 1, wherein the information relating to orders includes information relating to sales based on orders, the order amount for completed orders, and the order amount for ongoing inquiries.

5. The extraction unit does not extract the order amount that does not satisfy the first or second condition. The input / output unit calculates the total of the extracted order amounts. The business support device according to claim 4.

6. A business support method performed by a business support device equipped with a control unit, The control unit, An acquisition step to obtain information on the expected order timing and probability of receiving the order, and the amount of the order associated with that order, Extraction step to extract: information on the amount of the order for which the order probability satisfies a first condition regarding the order probability; and information on the amount of the order for which the order probability satisfies a second condition regarding the order probability and the planned order timing satisfies a third condition regarding the period; An output step that outputs information calculated based on the amount information related to the aforementioned order, A business support method characterized by performing the following actions.

7. A business support program to be executed by a business support device equipped with a control unit, The control unit, An acquisition step to obtain information on the expected order timing and probability of receiving the order, and the amount of the order associated with that order, Extraction step to extract: information on the amount of the order for which the order probability satisfies a first condition regarding the order probability; and information on the amount of the order for which the order probability satisfies a second condition regarding the order probability and the planned order timing satisfies a third condition regarding the period; An output step that outputs information calculated based on the amount information related to the aforementioned order, A business support program characterized by its ability to execute tasks.

Images