Approval necessity determination device, approval necessity determination method, and approval necessity determination program

Abstract

To provide an approval necessity determination device, an approval necessity determination method, and an approval necessity determination program capable of reducing the load of approval work while maintaining business control when correcting contract information.SOLUTION: The approval necessity determination device according to an embodiment is provided with: a master in which a reason for change and an approval necessity are registered in association with each other; contract information input means for specifying a reason for change in response to an operator's operation on a contract input screen and changing contract information in a storage area; and approval necessity determination means for acquiring approval necessity from the master using the specified reason for change as a key, applying for approval for the changed contract information when the acquired approval necessity is "necessary", and not applying for approval for the changed contract information when the acquired approval necessity is "unnecessary".SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an approval necessity determination device, an approval necessity determination method, and an approval necessity determination program. [Background technology]

[0002] For example, contract information is frequently revised, and generally, when a person in charge modifies the contract information, approval from a superior is required. Conventionally, an approval system for contract information is disclosed, for example, in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7237217 Summary of the Invention [Problem to be solved by the invention]

[0004] However, because the criteria by which the person in charge of amending contract information determines whether approval is necessary are unclear, even minor amendments are always sent to an approval process (for example, an approval WF (Workflow)), which creates the issue of a heavy workload for contract information approval work. On the other hand, approval processes are sometimes necessary from the perspective of business control, such as reducing the risk of inputting contract information incorrectly, and it is difficult from an operational standpoint to omit the approval process itself.

[0005] The present invention has been made in consideration of the above, and aims to provide an approval necessity determination device, an approval necessity determination method, and an approval necessity determination program that can reduce the load of approval work while maintaining business control when modifying contract information. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an approval necessity determination device equipped with a control unit, the control unit being configured to be able to access a memory area that stores a master in which reasons for change and whether approval is required are registered in association with each other, and contract information, and is characterized by comprising: a contract information input means that specifies the reason for change in accordance with an operator's operation on a contract input screen and changes the contract information in the memory area; and an approval necessity determination means that obtains whether approval is required from the master using the specified reason for change as a key, and if the obtained approval necessity is "required", submits an approval request for the modified contract information, and if the obtained approval necessity is "not required", does not submit an approval request for the modified contract information.

[0007] Furthermore, according to one aspect of the present invention, the master registers the reason for the change and whether approval is required, as well as the presence or absence of an invoice difference amount, which is the amount after the change in the invoice amount minus the amount before the change, in association with each other, and the approval requirement determination means obtains the approval requirement from the master using the reason for the change in the contract information and the presence or absence of the invoice difference amount as keys, and if the obtained approval requirement is "required", it submits an approval request for the changed contract information, and if the obtained approval requirement is "not required", it does not submit an approval request for the changed contract information.

[0008] According to another aspect of the present invention, the contract information may include contract information relating to orders from the construction industry.

[0009] In order to solve the above-mentioned problems and achieve the object, the present invention provides a method for determining whether approval is required, which is executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a storage area that stores a master in which reasons for change and whether approval is required are registered in association with each other, and contract information, and the control unit executes a contract information input process of specifying the reason for change in response to an operator's operation on a contract input screen and changing the contract information in the storage area; The method is characterized by including an approval necessity determination step of obtaining approval necessity from the master using the specified reason for change as a key, and if the obtained approval necessity is "necessary", submitting an approval request for the changed contract information, and if the obtained approval necessity is "not required", not submitting an approval request for the changed contract information.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention provides an approval necessity determination program to be executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a memory area that stores a master in which reasons for change and whether approval is required are registered in association with each other, and contract information, and causes the control unit to execute a contract information input step of specifying the reason for change in accordance with an operator's operation on a contract input screen and changing the contract information in the memory area, and an approval necessity determination step of obtaining the approval necessity from the master using the specified reason for change as a key, and if the obtained approval necessity is "required", submitting an approval request for the modified contract information, and if the obtained approval necessity is "not required", not submitting an approval request for the modified contract information. [Effects of the Invention]

[0011] According to the present invention, when contract information is modified, it is possible to reduce the load of approval work while maintaining business control. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an approval necessity determination device according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the change reason master. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the approval setting master. [Figure 4] FIG. 4 is a flowchart illustrating the overall processing flow of the control unit of the approval necessity determination device according to this embodiment. [Figure 5]FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the approval necessity determination device in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the approval necessity determination device in this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the approval necessity determination device in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the approval necessity determination device in this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the approval necessity determination device in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0014] [1. Overview] The outline of the present invention will be explained in detail in the order of [1-1. Background], [1-2. Problems], and [1-3. Solution].

[0015] [1-1. Background] For example, the construction industry differs from industries such as retail in that the amount per order is high, construction periods are long, and a large amount of information is retained for each order. Furthermore, in the construction industry, contract status is divided into two stages: an inquiry stage before an order is placed, and the items that need to be managed and the items that can be determined at the inquiry stage differ from those at the order stage. Since some details (such as the exact construction period and area) cannot be registered correctly at the time of inquiry or order placement, item revisions are more frequent after contract information is registered than in other industries. Some revisions require approval for important changes, while others are minor and do not require approval, and it would be desirable to be able to choose between them operationally.

[0016] [1-2. Issues] Contract information is a type of work that requires frequent revisions, and because the criteria for determining whether approval is necessary for the person who modifies the information are unclear, even minor revisions are always sent to an approval step (for example, approval workflow), which increases the workload for contract information approval work. On the other hand, approval steps are sometimes necessary from the perspective of business control, reducing the risk of input errors in contract information, and it is difficult from a business perspective to omit the approval step itself.

[0017] In this embodiment, an object is to reduce the load of approval work when contract information is changed while maintaining business control.

[0018] [1-3. Solution] In this embodiment, the reason (content) for changing contract information and whether approval is required are managed in a master, and when contract information is changed (modified), the need for approval is automatically determined based on the reason for the change, thereby reducing the workload of approval work when changing contract information while maintaining business control.

[0019] In addition, the difference between the contract amount at the time of previous registration and the contract amount at the time of current registration has been added to the master as an approval branching condition, and by combining this with the reason for the change, it is possible to determine whether approval is required or not, making it possible to set up a system where an approval request is made when there is a change in amount that requires approval, thereby enabling business control over amount changes.

[0020] The present invention is widely applicable to industries and sectors such as the construction industry, which are large in scale and have long construction periods (delivery dates).

[0021] [2. Configuration] An example of the configuration of the approval necessity determination device 100 according to this embodiment will be described with reference to Fig. 1. As an example, the approval necessity determination device 100 according to this embodiment will be described for a case where the contract information is contract information related to orders from the construction industry. Fig. 1 is a block diagram showing an example of the configuration of the approval necessity determination device 100.

[0022] The approval necessity determination device 100 is a commercially available desktop personal computer. Note that the approval necessity determination device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0023] The approval necessity determination device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the approval necessity determination device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicably connects the approval necessity determination device 100 to a network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of communicably connecting the approval necessity determination device 100, the server 200, and the terminals 400..., and is, for example, the Internet or a LAN (Local Area Network). The terminals 400... are terminals used by the person in charge and the approver (superior).

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0026] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that cooperate with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 stores a change reason master 106a, an approval setting master 106b, and contract information. Figure 2 is a diagram showing an example of the configuration of the change reason master 106a. Figure 3 is a diagram showing an example of the configuration of the approval setting master 106b.

[0027] As shown in Fig. 2, the reason-for-change master 106a can be configured as a table or the like in which reason-for-change codes and reason-for-change names are registered in association with each other. The reason-for-change master 106a is referenced when converting reason-for-change codes and reason-for-change names. In the example shown in the figure, the first line has reason-for-change code "0" and reason-for-change name "new order," the second line has reason-for-change code "10" and reason-for-change name "amount change," the third line has reason-for-change code "20" and reason-for-change name "construction period change," the fourth line has reason-for-change code "80" and reason-for-change name "address not entered," and the fifth line has reason-for-change code "90" and reason-for-change name "entry error."

[0028] As shown in Figure 3, the approval setting master 106b can be composed of a table or the like that associates and registers the reason for change (change reason code and / or change reason name), the voucher difference amount, which is the amount after change of the voucher amount of the contract information minus the amount before change, and whether approval is required (required or not). In the example shown in the same figure, the first line has the change reason code "0", invoice difference amount "- (irrelevant)", and approval required "Yes", the second line has the change reason code "10", invoice difference amount "- (irrelevant)", and approval required "Yes", the third line has the change reason code "20", invoice difference amount "- (irrelevant)", and approval required "Yes", the fourth line has the change reason code "80", invoice difference amount "Yes", and approval required "Yes", the fifth line has the change reason code "80", invoice difference amount "No", and approval required "No", the sixth line has the change reason code "90", invoice difference amount "Yes", and approval required "Yes", and the seventh line has the change reason code "90", invoice difference amount "No", and approval required "No".

[0029] The contract information may include a project number, an order number, a project name, a construction location, a construction period, a change reason code, a change reason name, a voucher amount, and whether approval is required.

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

[0031] The control unit 102 is configured to be able to access the change reason master 106a, the approval setting master 106b, the contract information, etc. stored in the storage unit 106. Note that the change reason master 106a, the approval setting master 106b, the contract information, etc. may be provided in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0032] The control unit 102 conceptually includes a contract information input unit 102a, an approval necessity determination unit 102b, a master maintenance unit 102c, and a screen display control unit 102d.

[0033] The contract information input unit 102a, for example, provides a contract information input screen (see Figures 5 to 9) in response to access from the terminal 400 of the person in charge, and in response to operations on the contract information input screen from the terminal 400 of the person in charge, specifies the reason for the change and performs new input or change of the contract information.

[0034] The approval necessity determination unit 102b provides a system for the approval WF. The approval necessity determination unit 102b acquires approval necessity from the approval setting master 106b using the specified reason for change as a key, and if the acquired approval necessity is "necessary," it submits an approval request for the changed (including new input) contract information in the approval WF, displays the changed (including new input) contract information on the approval list screen, and notifies the approver's terminal 400. When the approver approves on the unapproved list screen at the approver's terminal 400, the approval necessity determination unit 102b updates the contract information in the storage unit 106 to the changed contract information (in the case of new input, it registers the contract information in the storage unit 106). On the other hand, if the acquired approval necessity is "not required," the approval necessity determination unit 102b does not submit an approval request for the changed contract information, and updates the contract information in the storage unit 106 to the changed contract information (in the case of new input, it registers the contract information in the storage unit 106).

[0035] In addition, the approval necessity determination unit 102b may acquire the approval necessity from the approval setting master 106b using the reason for the change in the contract information as well as the presence or absence of a difference amount in the invoice as a key, and if the acquired approval necessity is "necessary," it may submit an approval request for the changed contract information, but if the acquired approval necessity is "not required," it may not submit an approval request for the changed contract information.

[0036] The master maintenance unit 102c is capable of editing the change reason master 106a and the approval setting master 106b, such as registering, adding, modifying, and deleting data, in response to an operator's operation on the master maintenance screen displayed on the monitor 114, for example.

[0037] The screen display control unit 102d controls the display and input of various screens (for example, a contract input screen, an unapproved list screen, a master maintenance screen, etc.) displayed on the monitor 114 and provided to the terminals 400 .

[0038] [3. Specific Examples] A specific example of the processing performed by the control unit 102 of the approval necessity determination device 100 in this embodiment will be described with reference to FIGS.

[0039] (3-1. Overall processing) Fig. 4 is a diagram showing a flow for explaining an outline of the overall processing flow of the control unit 102 of the approval necessity determination device 100 in this embodiment. With reference to Fig. 4, an outline of the overall processing flow of the control unit 102 of the approval necessity determination device 100 in this embodiment will be described.

[0040] The contract information input unit 102a inputs contract information (step S1). Specifically, in inputting contract information, the contract information input unit 102a provides a contract information input screen (see FIGS. 5 to 9) in response to access from the terminal 400 of the person in charge, and newly inputs or changes (modifies) the contract information by specifying the reason for change in response to an operation on the contract information input screen from the terminal 400 of the person in charge.

[0041] The approval necessity determination unit 102b determines whether approval is necessary (step S2), and specifically, acquires whether approval is necessary from the approval setting master 106b using the specified reason for the change and whether there is a voucher difference amount as keys, and if the acquired approval necessity is "necessary" ("Yes" in step S2), submits an approval request for the changed (including new input) contract information in the approval WF (step S3), displays the changed (including new input) contract information on the approval list screen, and notifies the approver's terminal 400. When the approver approves on the unapproved list screen at the approver's terminal 400, the approval necessity determination unit 102b updates the contract information in the memory unit 106 to the changed contract information (in the case of new input, registers the contract information in the memory unit 106). On the other hand, if the acquired approval necessity information is "not required" ("No" in step S2), the approval necessity determination unit 102b does not request approval for the changed contract information, and updates the contract information in the memory unit 106 to the changed contract information (in the case of new input, the contract information is registered in the memory unit 106) (step S4).

[0042] (3-2. Sample data) 5 to 9 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the approval necessity determination device 100 in this embodiment. A specific example of the processing by the control unit 102 of the approval necessity determination device 100 in this embodiment will be explained with reference to FIGS. 5 to 9.

[0043] [Case 1] Case 1 will be described with reference to Fig. 5. In case 1, a case where contract information about an order is newly input (without premise data) from the contract information input will be described.

[0044] 5(A) is a diagram showing an example of the display of a contract information input screen 500. The contract information input screen 500 has input fields for the project number, order number, project name, construction location, construction period, reason for change, and amount, as well as an execute button (not shown). When the project number and order number are specified, the contract information is read from the storage unit 106 using the project number and order number as keys and displayed in the corresponding area. In this example, since this is a new input, this display is not performed.

[0045] After entering information into each input field and pressing the execute button (not shown), it is determined whether approval is required. If it is determined that approval is not required, the contract information corresponding to the input content on the screen is registered and updated in the storage unit 106. If it is determined that approval is required, the contract information corresponding to the input content on the screen is applied for approval.

[0046] In the example shown in the figure, the project number is "PJ0001," the order number is "JU0001," the project name is "New factory B district air conditioning work," the construction location is "Chuo-ku, Tokyo," the construction period is "2023 / 10 / 01~2024 / 03 / 31," the reason for change is "0: New order," and the amount is "10,000,000." When the execute button (not shown) is pressed, contract information is created and a determination is made as to whether approval is required.

[0047] FIG. 5(B) is a diagram for explaining the determination of whether approval is required. Since the change reason code is "0: New creation" and the invoice difference amount is "10,000,000", the approval setting master 106b indicates that the change reason code is "0: New creation", the invoice difference amount is "- (irrelevant)", and approval requirement is "Required", so an approval request for the changed contract information is made in the approval workflow, the status is "in application", and the information is added to the unapproved list screen. On the approver's terminal 400, approval is possible on the unapproved list screen. If approval is granted on the unapproved screen, the input contract information is registered in the memory unit 106.

[0048] Figure 5(C) shows an example of the contract information to be created. In the example shown in the figure, the project number is "PJ0001," the order number is "JU0001," the project name is "Air conditioning work in area B of the new factory," the construction location is "Chuo-ku, Tokyo," the construction period is "2023 / 10 / 01~2024 / 03 / 31," the reason for change is "0," the reason for change is "New order," the invoice amount is "10,000,000," and whether approval is required is "Yes."

[0049] [Case 2] Case 2 will be described with reference to Fig. 6. In case 2, a case where the contract information is revised because the contract amount needs to be changed will be described.

[0050] 6(A) shows an example of contract information (prerequisite data) registered in the storage unit 106. In the example shown in the figure, the project number is "PJ0002," the order number is "JU0002," the project name is "Section C, equipment construction," the construction location is "Chiyoda-ku, Tokyo," the construction period is "2023 / 11 / 01 to 2024 / 06 / 30," the change reason code is "0," the reason for the change is "new order," and the invoice amount is "10,000,000."

[0051] 6(B) is a diagram showing a display example of the contract information input screen 500. In the example shown in the figure, The project number is "PJ0002", order number is "JU0002", project name is "Section C, equipment construction", construction location is "Chiyoda-ku, Tokyo", construction period is "2023 / 11 / 01~2024 / 06 / 30", change reason code is "10", change reason is "amount change", and invoice amount is "12,000,000". In this example, the change reason code is "10" and the change reason is "amount change", and the invoice amount has been changed to "12,000,000".

[0052] FIG. 6(C) is a diagram for explaining the determination of whether approval is required. Since the change reason code is "10: amount changed" and the invoice difference amount is "2,000,000 (=12,000,000-10,000,000)," the approval setting master 106b indicates that the change reason code is "10: amount changed," the invoice difference amount is "- (irrelevant)," and approval requirement is "required." Therefore, an approval request for the changed contract information is submitted in the approval workflow, and the status changes to "in application," and the contract is added to the unapproved list screen. Approval is possible on the unapproved list screen on the approver's terminal 400. When approval is granted on the unapproved screen, the contract information in the storage unit 106 is updated to the changed contract information.

[0053] Figure 6(D) shows an example of contract information to be changed. In the example shown in the figure, the project number is "PJ0002," the order number is "JU0002," the project name is "Section C, equipment construction," the construction location is "Chiyoda-ku, Tokyo," the construction period is "2023 / 11 / 01~2024 / 06 / 30," the reason for change is "10," the reason for change is "amount change," the invoice amount is "12,000,000," and whether approval is required is "required."

[0054] [Case 3] Case 3 will be described with reference to Fig. 7. In case 3, a case where the contract information is revised because a change in the contract construction period is required will be described.

[0055] 7(A) shows an example of contract information (prerequisite data) registered in the storage unit 106. In the example shown in the figure, the project number is "PJ0003," the order number is "JU0003," the project name is "renovation work at XX Station," the construction location is "Taito Ward, Tokyo," the construction period is "November 1, 2023 to March 31, 2024," the change reason code is "0," the reason for the change is "new order," and the invoice amount is "8,000,000."

[0056] 7(B) is a diagram showing a display example of the contract information input screen 500. In the example shown in the figure, The project number is "PJ0003," the order number is "JU0003," the project name is "Renovation work at XX Station," the construction location is "Taito-ku, Tokyo," the construction period is "2023 / 11 / 01 - 2024 / 05 / 31," the change reason code is "20," the reason for change is "Construction period change," and the invoice amount is "8,000,000." In this example, the change reason code is "20" and the reason for change is "Construction period change," and the construction period has been changed to "2023 / 11 / 01 - 2024 / 05 / 31."

[0057] FIG. 7(C) is a diagram for explaining the determination of whether approval is required. Since the change reason code is "20: construction period change" and the invoice difference amount is "0", the approval setting master 106b sets the change reason code to "20: construction period change", the invoice difference amount to "- (irrelevant)", and the approval requirement to "required", so an approval request for the changed contract information is made in the approval workflow, the status is changed to "application in progress", and the information is added to the unapproved list screen. On the approver's terminal 400, approval is possible on the unapproved list screen. When approval is granted on the unapproved screen, the contract information in the storage unit 106 is updated to the changed contract information.

[0058] Figure 7(D) shows an example of contract information to be changed. In the example shown in the figure, the project number is "PJ0003," the order number is "JU0003," the project name is "Renovation work at XX Station," the construction location is "Taito-ku, Tokyo," the construction period is "2023 / 11 / 01~2024 / 05 / 31," the reason for change is "20," the reason for change is "Construction period change," the invoice amount is "8,000,000," and whether approval is required is "Required."

[0059] [Case 4] Case 4 will be described with reference to Fig. 8. In case 4, the contract information is corrected because the description of the construction site is incorrect.

[0060] 8(A) shows an example of contract information (prerequisite data) registered in the storage unit 106. In the example shown in the figure, the project number is "PJ0004", the order number is "JU0004", the project name is "△△ Building Electrical Work", the construction location is " ", the construction period is "2023 / 11 / 01 to 2024 / 05 / 31", the change reason code is "0", the reason for the change is "New order", and the invoice amount is "6,000,000".

[0061] 8(B) is a diagram showing a display example of the contract information input screen 500. In the example shown in the figure, The project number is "PJ0004," the order number is "JU0004," the project name is "△△ Building Electrical Work," the work location is "Minato Ward, Tokyo," the construction period is "2023 / 11 / 01 - 2024 / 03 / 31," the reason for change is "80," the reason for change is "missing address," and the invoice amount is "6,000,000." In this example, the reason for change is "80," the reason for change is "missing address," and the work location has been changed to "Minato Ward, Tokyo."

[0062] 8(C) is a diagram for explaining the determination of whether approval is required. Since the change reason code is "80: entry error" and the voucher difference amount is "0 (=8,000,000-8,000,000)", the approval setting master 106b shows that the change reason code is "80: address not entered", the voucher difference amount is "none", and the approval requirement is "not required", so an approval request is not required, and the contract information in the memory unit 106 is updated to the changed contract information.

[0063] Figure 8(D) shows an example of contract information to be changed. In the example shown in the figure, the project number is "PJ0004," the order number is "JU0004," the project name is "△△ Building Electrical Work," the construction location is "Minato-ku, Tokyo," the construction period is "2023 / 11 / 01~2024 / 03 / 31," the reason for change is "80," the reason for change is "address not filled in," the invoice amount is "6,000,000," and whether approval is required is "not required."

[0064] [Case 5] Case 5 will be described with reference to Fig. 9. In case 5, a case where an error has been made in the invoice amount and the contract information is corrected will be described.

[0065] 9(A) shows an example of contract information (prerequisite data) registered in the storage unit 106. In the example shown in the figure, the project number is "PJ0005," the order number is "JU0005," the project name is "□□ Center Instrumentation Work," the construction location is "Taito-ku, Tokyo," the construction period is "2023 / 11 / 01 - 2024 / 03 / 31," the change reason code is "0," the reason for the change is "new order," and the invoice amount is "8,000,000."

[0066] 9(B) is a diagram showing an example of the display of the contract information input screen 500. In the example shown in the figure, the project number is "PJ0005," the order number is "JU0005," the project name is "□□ Center Instrumentation Work," the construction location is "Taito-ku, Tokyo," the construction period is "2023 / 11 / 01 - 2024 / 03 / 31," the reason for change is "90," the reason for change is "Entry Error," and the voucher amount is "8,500,000." In this example, the reason for change is "90" and the reason for change is "Entry Error," and the voucher amount has been changed to "8,500,000."

[0067] FIG. 9(C) is a diagram for explaining the determination of whether approval is required. Since the change reason code is "90: entry error" and the invoice difference amount is "50,000 (=8,500,000-8,000,000)", the approval setting master 106b indicates that the change reason code is "90: entry error", the invoice difference amount is "yes", and approval requirement is "required", so an approval request for the changed contract information is made in the approval workflow, the request is put into an application pending state, and the information is added to the unapproved list screen. On the approver's terminal 400, approval is possible on the unapproved list screen. When approval is granted on the unapproved screen, the contract information in the storage unit 106 is updated to the changed contract information.

[0068] Figure 9(D) shows an example of contract information to be changed. In the example shown in the figure, the project number is "PJ0005," the order number is "JU0005," the project name is "□□ Center Instrumentation Work," the construction location is "Taito-ku, Tokyo," the construction period is "2023 / 11 / 01 - 2024 / 03 / 31," the reason for change is "90," the reason for change is "incorrect entry," the invoice amount is "8,500,000," and whether approval is required is "required."

[0069] As described above, according to this embodiment, there are provided the approval setting master 106b in which the reason for change and the necessity of approval are registered in association with each other, the contract information input unit 102a which changes the contract information in the storage unit 106 by specifying the reason for change in accordance with the operation of the operator on the contract input screen, and the approval necessity determination unit 102b which acquires the necessity of approval from the approval setting master 106b using the designated reason for change as a key, and if the acquired approval necessity is "necessary", submits an approval request for the changed contract information, but if the acquired approval necessity is "not required", does not submit an approval request for the changed contract information. Therefore, when contract information is modified, it becomes possible to reduce the load of approval work while maintaining business control.

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

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

[0072] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0073] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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

[0075] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0076] Furthermore, with regard to the approval necessity determination device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0077] For example, all or any part of the processing functions of the approval necessity determination device 100, particularly the processing functions performed by the control unit 102, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the approval necessity determination device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0078] In addition, this computer program may be stored in an application program server connected to the approval necessity determination device 100 via any network, and all or part of it may be downloaded as needed.

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

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

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

[0082] The approval necessity determination device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The approval necessity determination device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to realize the processing described in this embodiment.

[0083] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0084] 100 Approval necessity determination device 102 Control section 102a Contract information input section 102b Approval necessity determination section 102c Master Maintenance Department 102d Screen display control unit 104 Communication interface unit 106 Storage section 106a Reason for Change Master 106b Approval setting master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. An approval necessity determination device including a control unit, The control unit Master data that associates the reason for change with whether approval is required, Contract information, The storage area storing the a contract information input means for specifying a reason for change in response to an operator's operation on a contract input screen and changing the contract information in the storage area; an approval necessity determination means for acquiring approval necessity from the master using the specified reason for change as a key, and making an approval request for the changed contract information if the acquired approval necessity is "necessary," and not making an approval request for the changed contract information if the acquired approval necessity is "not required," An approval necessity determination device comprising:

2. In the master, in addition to the reason for the change and whether approval is required, the presence or absence of a difference amount in the invoice, which is the amount after the change - the amount before the change, is registered in association with the change. The approval necessity determination device according to claim 1, characterized in that the approval necessity determination means acquires approval necessity from the master using the reason for the change to the contract information as well as the presence or absence of the invoice difference amount as a key, and if the acquired approval necessity is ``necessary,'' submits an approval request for the changed contract information, and if the acquired approval necessity is ``not required,'' does not submit an approval request for the changed contract information.

3. The approval necessity determination device according to claim 1 or 2, wherein the contract information includes contract information relating to orders from the construction industry.

4. An approval necessity determination method executed by an information processing device having a control unit, The control unit Master data that associates the reason for change with whether approval is required, Contract information, The storage area storing the Executed in the control unit: a contract information input step of specifying a reason for change in response to an operator's operation on a contract input screen and changing the contract information in the storage area; an approval necessity determination step of obtaining approval necessity from the master using the specified reason for change as a key, and if the obtained approval necessity is "necessary", submitting an approval request for the changed contract information, and if the obtained approval necessity is "not required", not submitting an approval request for the changed contract information; A method for determining whether approval is necessary, comprising:

5. An approval necessity determination program to be executed by an information processing device having a control unit, The control unit The control unit Master data that associates the reason for change with whether approval is required, Contract information, The storage area storing the The control unit a contract information input step of specifying a reason for change in response to an operator's operation on a contract input screen and changing the contract information in the storage area; an approval necessity determination step of obtaining approval necessity from the master using the specified reason for change as a key, and if the obtained approval necessity is "necessary", submitting an approval request for the changed contract information, and if the obtained approval necessity is "not required", not submitting an approval request for the changed contract information; A program to determine whether approval is required.

Images