Purchase order / contract checking device, purchase order / contract checking method, and purchase order / contract checking program

Abstract

To strengthen control over revenue recognition for contracts and purchase orders with minimal workload. [Solution] The order form / contract checking device includes: a contract information input means that registers contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount in response to operator operations on the contract input screen; an order form registration means that registers order form information including contract number, storage location, order form presence / absence classification specifying whether or not an order form is attached, line, receipt date, actual construction period, and order form amount in response to operator operations on the order form registration screen; and a sales input means that, in response to operator operations on the sales input screen, when recording sales for the target project number and contract number, refers to the registered contract information and the order form information to check whether the contract amount and the order form amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met.

Description

Technical Field

[0006] , , ,

[0005] , ,

[0001] The present invention relates to an order / contract checking device, an order / contract checking method, and an order / contract checking program.

Background Art

[0002] For example, in the construction industry and the IT industry, when recognizing the revenue for each order recipient, it is necessary to link the order document to the contract information and correctly record the revenue. Conventionally, as a system for managing revenue, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, conventionally, there has been no method for efficiently checking the consistency with the content of the order document, including the presence or absence of the contract to be recorded as revenue and the corresponding order document, and it has been necessary to perform individual management checks, resulting in a large workload.

[0005] The present invention has been made in view of the above, and an object thereof is to provide an order / contract checking device, an order / contract checking method, and an order / contract checking program that can strengthen control during revenue recording with a low workload for contracts and order documents.

Means for Solving the Problems

[0007] Furthermore, according to one aspect of the present invention, the sales input means may display an error if the above conditions are not met.

[0008] Furthermore, according to one aspect of the present invention, the sales input means may display a pop-up indicating the error content when displaying the error.

[0009] Furthermore, according to one aspect of the present invention, the control unit may be provided with inquiry means that, in response to an operator's operation on the inquiry screen, refers to the contract information and order information registered in the storage area, displays information including the presence or absence of an order on a contract number basis, and transitions to the order registration screen when a predetermined operation is performed by the operator.

[0010] Furthermore, according to one aspect of the present invention, the sales input means may display the contract information for contract numbers where the order form exists / exists "Yes" as a sales candidate.

[0011] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides an order and contract checking method executed by an information processing device equipped with a control unit, comprising: a contract information input step performed by the control unit, in which, in response to an operator's operation on a contract input screen, contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount is registered in a storage area; an order registration step, in response to an operator's operation on an order registration screen, registering order information including contract number, storage location, order presence / absence classification specifying whether or not an order is attached, line, receipt date, actual construction period, and order amount in the storage area; and a sales input step, in response to an operator's operation on a sales input screen, in which, when recording sales for the target project number and contract number, the contract information and order information registered in the storage area are referred to, checks whether the contract amount and the order amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met.

[0012] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the present invention provides an order form / contract check program to be executed by an information processing device equipped with a control unit, wherein the control unit is configured to perform the check. The program is characterized by its ability to perform the following steps: a contract information input step, in response to an operator's operation on the contract input screen, registers contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount in a storage area; an order registration step, in response to an operator's operation on the order registration screen, registers order information including contract number, storage location, order presence / absence classification (specifying whether an order is attached or not), line, receipt date, actual construction period, and order amount in the aforementioned storage area; and a sales input step, in response to an operator's operation on the sales input screen, when recording sales for the target project number and contract number, refers to the contract information and order information registered in the aforementioned storage area to check whether the contract amount and order amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met. [Effects of the Invention]

[0013] According to the present invention, it is possible to strengthen control over revenue recognition with low workload for contracts and purchase orders. [Brief explanation of the drawing]

[0014] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the order form / contract checking device in this embodiment. [Figure 2] Figure 2 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 3] Figure 3 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 4] Figure 4 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 5] Figure 5 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 6] Figure 6 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 7] Figure 7 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 8A] Figure 8A is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 8B] Figure 8B is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 8C] Figure 8C is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 9] Figure 9 is a diagram illustrating a specific example of the processing performed by the control unit of the order form / contract checking device in this embodiment. [Figure 10]FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 13A] FIG. 13A is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 13B] FIG. 13B is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 14A] FIG. 14A is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment. [Figure 14B] FIG. 14B is a diagram for explaining a specific example of the processing of the control unit of the order form / contract check device in the present embodiment.

Embodiments for Carrying Out the Invention

[0015] Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited by these embodiments.

[0016] [1. Overview] The overview of the present invention will be described in the order of [1-1. Background and Problems], [1-2. Solution Method], and [1-3. Outline of Processing].

[0017] [1-1. Background and Problems] For example, in the construction and IT industries, in order to recognize revenue for each client, it is necessary to link purchase orders to contract information and correctly record revenue (for "performance obligations satisfied over a period of time" under the new revenue recognition standards, if the progress can be reasonably estimated, revenue including profit can be recorded according to the progress). Purchase order collection management is necessary to demonstrate whether the progress can be reasonably estimated.

[0018] Furthermore, at the following points in time when revenue is recognized, a control function is needed to check and record the order amount and contract amount, and the order period and contract period. • Work-by-work sales and completed sales under the completed method. • Progress sales based on percentage-of-completion method

[0019] However, traditionally, there was no efficient method for checking the consistency between contracts eligible for revenue recognition and the content of corresponding purchase orders, including whether or not such orders existed. This required individual management and checks, which resulted in a significant workload and was a major challenge.

[0020] [1-2. Solution] This invention links contract information with purchase order registration and checks it at the time of revenue recognition, thereby achieving enhanced control at the time of revenue recognition with a low workload.

[0021] In this invention, the following are controlled conditions at the time of sale (revenue recognition). • The project purchase order has been received. • The purchase order amount and the contract amount must match (the purchase order amount is linked to the purchase order, and the contract amount is linked to the project). • The order date and the contract date must be consistent (the order date is linked to the order, and the contract date is linked to the project).

[0022] [1-3. Overview of the process] 1. About data registration (1) Register the contract information for the construction work. (2) When the purchase order is collected, the relevant contract information and the purchase order information will be linked. The amount and construction period stated in the linked purchase order will be registered (registered to compare with the contract amount, contract period, and construction period in the contract information). (3) If multiple contract information is linked to a single purchase order, register the relevant contract information (to compare the amount of each purchase order with the contract information).

[0023] 2. The specific timing (program) in which this mechanism functions. (1) At the time of sale (sales entry in this system). (2) The system checks the status of purchase order collection for contract information to be recorded as sales, and whether the contract information and the contents of the purchase order match, and controls the registration of sales. The logic for checking whether a sale is possible or not is as follows.

[0024] Check the following: If OK, the sale is permitted; otherwise, the sale is not permitted. • The purchase order for the sales contract information has been collected (the purchase order is attached). • The amount in the contract information matches the amount on the purchase order. • The construction period in the contract information is included in the construction period in the purchase order.

[0025] The purchase order and contract checking device of the present invention is widely applicable in industries such as construction and IT media.

[0026] [2. Structure] An example of the configuration of the order form / contract checking device 100 according to this embodiment will be described with reference to Figures 1 and 2. Figure 1 is a block diagram showing an example of the configuration of the order form / contract checking device 100 in this embodiment.

[0027] The order form / contract checking device 100 is a commercially available desktop personal computer. However, the order form / contract checking device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0028] The purchase order / contract checking device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the purchase order / contract checking device 100 is connected to communicate via any communication path.

[0029] The communication interface unit 104 connects the order / contract checking 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 via communication lines. Here, the network 300 has the function of connecting the order / contract checking 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).

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

[0031] The memory unit 106 stores various databases, tables, and files. The memory 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 memory 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.

[0032] The memory unit (memory area) 106 stores project basic information, contract information (contract information header data, contract information detail data), purchase order information (purchase order information header data, purchase order information detail data, breakdown information detail data), sales information, etc.

[0033] Project basic information data may include the project number and project name.

[0034] Contract information consists of contract information header data and contract information detail data. The contract information header data may include project number, contract number, contract status, customer, project name, contract period, order date, and planned sales date. The contract information detail data may include contract number, line, product, contract amount excluding tax, contract consumption tax amount, and contract amount including tax.

[0035] Purchase order information consists of purchase order information header data, purchase order information detail data, and breakdown information detail data. The purchase order information header data may include the contract number, registration department, storage location, purchase order presence / absence classification indicating whether a purchase order is attached, and the purchase order registration contract number. The purchase order information detail data may include the contract number, line number, receipt date, work period (from), work period (to), purchase order amount excluding tax, purchase order consumption tax amount, and purchase order amount including tax. The breakdown information detail data may include the header contract number, line number, contract number, purchase order amount excluding tax, purchase order consumption tax amount, and purchase order amount including tax.

[0036] The control unit 102 is a CPU or similar component that comprehensively controls the order form / contract checking device 100. The control unit 102 has 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.

[0037] The control unit 102 is configured to access project basic information, contract information (contract information header data, contract information detail data), purchase order information (purchase order information header data, purchase order information detail data, breakdown information detail data), sales information, etc., which are stored in the storage unit 106. Note that project basic information, contract information (contract information header data, contract information detail data), purchase order information (purchase order information header data, purchase order information detail data, breakdown information detail data), sales information, etc. may be stored in another location (for example, server (storage area) 200), as long as the control unit 102 can access it.

[0038] Functionally, the control unit 102 comprises a project information input unit 102a, a contract information input unit 102b, an order registration unit 102c, a construction status inquiry unit 102d, a sales input unit 102e, and a screen display control unit 102f.

[0039] The project information input unit 102a inputs project basic information and registers it in the storage unit 106 in response to the operator's operation on, for example, a basic information input screen (not shown) displayed on the monitor 114.

[0040] The contract information input unit 102b inputs contract information, including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount, in response to the operator's actions on the contract information input screen displayed on the monitor 114, and registers it in the storage unit 106.

[0041] The order registration unit 102c registers order information, including the contract number, storage location, order presence / absence classification (specifying whether or not an order is attached), line number, receipt date, construction period, and order amount, in the storage unit 106, for example, in response to the operator's operation on the order registration screen displayed on the monitor 114.

[0042] The construction status inquiry unit 102d, for example, in response to the operator's operation on the construction status inquiry screen displayed on the monitor 114, refers to the contract information and purchase order information registered in the storage unit 106, displays information including whether or not a purchase order exists for each contract number, and transitions to the purchase order registration screen when a predetermined operation is performed by the operator.

[0043] The sales input unit 102e, for example, in response to an operator's operation on the sales input screen displayed on the monitor 114, refers to the contract information and purchase order information registered in the storage unit 106 to check whether the contract amount and purchase order amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met.

[0044] The sales input unit 102e may output an error if the above conditions are not met, and if an error is output, it may also output a pop-up indicating the error details.

[0045] The sales input unit 102e may control the system so that sales cannot be recorded for contracts without attached purchase orders by displaying the contract information for contract numbers where the purchase order status is "Yes" as a sales candidate, and not displaying the contract information for contract numbers where the purchase order status is "No" as a sales candidate.

[0046] The screen display control unit 102g controls the display and acceptance of input for various screens displayed on the monitor 114 (for example, the basic information input screen, the contract information input screen, the order registration screen, the construction status inquiry screen, the sales input screen, etc.).

[0047] [3. Specific Examples] Referring to Figures 1 to 14B, a specific example of the processing of the control unit 102 of the order form / contract checking device 100 in this embodiment will be described. Figures 2 to 14B are diagrams illustrating a specific example of the processing of the control unit 102 of the order form / contract checking device 100 in this embodiment.

[0048] (3-1. Overall Processing) The general outline of the overall processing of the control unit 102 of the order form / contract checking device 100 in this embodiment will be described below. The general outline of the overall processing of the control unit 102 of the order form / contract checking device 100 in this embodiment is as follows (1) to (4).

[0049] 1. INPUT(1): The project information input unit 102a executes the project basic information input process and registers the project basic information. The contract information input unit 102b executes the contract information input process and registers the contract information. Project basic information and contract information are registered at the inquiry and order stages.

[0050] 2. INPUT(2): The purchase order registration unit 102c executes the purchase order registration process, attaches a purchase order for each contract information, and registers the amount, construction period, and other information stated in the purchase order as purchase order information.

[0051] 3. INPUT(3): The construction status inquiry unit 102d executes the construction status inquiry process, checks the list to see if the purchase orders have been collected, and for those that are not registered, it transitions to the purchase order registration screen and registers the purchase orders.

[0052] 4. INPUT(4): The sales input unit 102e executes the sales input process and enables sales only for contract numbers that meet the following conditions. • The order form information must show "Yes" as the order form status. • The tax-inclusive purchase price in the purchase order information should match the tax-inclusive contract price in the contract information. • The contract period in the contract information must be included in the actual construction period in the purchase order information.

[0053] (3-2. Sample Data) A specific example of the processing performed by the control unit 102 of the order form / contract checking device 100 in this embodiment will be described in detail with reference to sample data.

[0054] 1. INPUT(1) Refer to Figures 2 to 4 to explain the details of INPUT(1).

[0055] The project information input unit 102a inputs basic construction information and registers it in the storage unit 106 in response to the operator's operation on, for example, a basic information input screen (not shown) displayed on the monitor 114.

[0056] Figure 2 shows an example of project basic information data. The project basic information includes fields for project number and project name. In the example shown in the figure, the first row is project number "PJ0001" and project name "New Factory Area B Air Conditioning Work", the second row is project number "PJ0002" and project name "Kyobashi XX Building Electrical Construction Work", and the third row is project number "PJ0003" and project name "Nihonbashi ◇◇ Building Air Conditioner Replacement Work".

[0057] The contract information input unit 102b inputs contract information, including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount, in response to the operator's actions on the contract information input screen displayed on the monitor 114, and registers it in the storage unit 106.

[0058] Figure 3 shows an example of the display of the contract information input screen 400. The contract information input screen 400 includes input fields for project number and contract number, a contract information header input area (contract status, project name, department in charge, customer, order date, and planned sales date), a contract information detail input area (line number, product, contract amount excluding tax, contract consumption tax amount, and contract amount including tax), and a registration button (not shown). When the operator enters data and presses the registration button (not shown), contract information (contract information header data and contract information detail data) corresponding to the displayed content (input content) on the screen is registered in the storage unit 106.

[0059] In the example shown in the figure, data for project number "PJ0001" has been entered. Data for project numbers "PJ0002" and "PJ0003" should be entered in the same manner.

[0060] Figure 4(A) shows an example of contract information header data. The contract information header data may include items such as project number, contract number, contract status, customer, project name, contract period, order date, and planned sales date. In the example shown in the figure, the first row contains project number "PJ0001", contract number "PJ0001001", contract status "2: Ordered", customer "TOK001: ○○ Industries", project name "New Factory Area B Air Conditioning Construction", contract period "2024 / 4 / 1~2025 / 3 / 31", order date "2024 / 4 / 1", and planned sales date "2025 / 3 / 31".

[0061] Figure 4(B) shows an example of contract information details data. The contract information details data includes the following fields: contract number, line, product, contract amount excluding tax, contract consumption tax amount, and contract amount including tax. In the example shown in the diagram, the first row contains the project number "PJ0001", row "1", product "SHO001: Equipment Installation", contract amount excluding tax "1,000,000", contract consumption tax amount "100,000", and contract amount including tax "1,100,000".

[0062] 2. INPUT(2) Refer to Figures 5 to 7 to explain the details of INPUT(2). The purchase order registration unit 102c registers purchase order information, including the contract number, storage location, purchase order presence / absence classification (specifying whether or not a purchase order is attached), line number, receipt date, construction period, and purchase order amount, in the storage unit 106, for example, in response to the operator's operation on the purchase order registration screen displayed on the monitor 114. In the purchase order registration process, for each piece of contract information, a purchase order is attached (image data of the (original) purchase order is stored in the storage unit 106), and the contents such as the amount stated in the purchase order are entered as purchase order information.

[0063] Figure 5 shows an example of the display of the purchase order registration screen 500. The purchase order registration screen 500 includes a header for entering the project number and contract number, a contract information display area for displaying contract information (project name, customer, contract period, department in charge, contract amount excluding tax, contract consumption tax amount, contract amount including tax), a purchase order information input area for entering purchase order information (enter the registration department, storage location, purchase order existence status (1: Yes (if a purchase order is attached), 0: No (if a purchase order is not attached)), storage location, purchase order registration contract number, and details (line number, receipt date, actual construction period (from), actual construction period (to), purchase order amount excluding tax, purchase order consumption tax amount, purchase order amount including tax)), a breakdown information input area for entering breakdown information (line number, contract number, project name, customer, contract amount including tax, purchase order amount excluding tax, purchase order consumption tax amount, purchase order amount including tax), and a registration button (not shown).

[0064] The pre-tax order amount, order consumption tax amount, and tax-inclusive order amount are initially set to "0". The first line of the breakdown information is initially set to the contract number in the header (enter the order amount for the contract number in the header). In the contract information display area, the contract information stored in the memory unit 106 is read and displayed using the project number and contract number specified by the operator as keys. In the order information input area and the breakdown information input area, the operator enters the necessary data. The registration button (not shown) and the order information corresponding to the screen display content (input content) are registered in the memory unit 106. In the case of the input content shown in the figure, the order information as shown in Figure 6 is registered. If the total tax-inclusive order amount in the order information and the total tax-inclusive order amount in the breakdown information do not match, an error is recorded and registration is not possible. In the example shown in Figure 5, the total tax-inclusive order amount in the order information and the total tax-inclusive order amount in the breakdown information match, so registration is possible.

[0065] Figure 6 shows an example of order information data. The order information consists of order information header data, order information detail data, and breakdown information detail data.

[0066] Figure 6(A) shows an example of order information header data. The order information header data includes the following fields: contract number, registration department, storage location, order existence / existence classification, and order registration contract number. In the example shown in the figure, the contract number is "PJ0001001", registration department is "BUM001: Sales Department 1", storage location is "1: Head Office", order existence / existence classification is "1: Yes", and order registration contract number is " ".

[0067] Figure 6(B) shows an example of purchase order information detail data. The purchase order information detail data includes the following items: contract number, line, receipt date, work period (from), work period (to), purchase order amount excluding tax, purchase order consumption tax amount, and purchase order amount including tax. In the example shown in the figure, the contract number is "PJ0001001", line is "1", receipt date is "2024 / 4 / 1", work period (from) is "2024 / 4 / 1", work period (to) is "2025 / 11 / 30", purchase order amount excluding tax is "3,000,000", purchase order consumption tax amount is "300,000", and purchase order amount including tax is "3,300,000".

[0068] Figure 6(C) shows an example of detailed breakdown data. Detailed breakdown data includes the following fields: header contract number, row, contract number, order amount excluding tax, order consumption tax amount, and order amount including tax. In the example shown in the figure, the first row contains: contract number "PJ0001001", row "1", contract number "PJ0001001", order amount excluding tax "1,000,000", order consumption tax amount "100,000", and order amount including tax "1,100,000".

[0069] Figure 7 illustrates the relationship between order information detail data and breakdown information detail data. The breakdown information detail data is used to input the breakdown for the total order amount including tax in the order information detail data. Row numbers are not used as conditions for the relationship. For example, Figure 7 shows an example where the order is split into two. The order information detail data and breakdown information detail data are n:m, and the design philosophy is not to specify which detail corresponds to which breakdown.

[0070] 3. INPUT(3) Refer to Figures 8A to 9 to explain the details of INPUT(3). The construction status inquiry unit 102d, for example, in response to the operator's operation on the construction status inquiry screen displayed on the monitor 114, refers to the contract information and purchase order information registered in the storage unit 106, displays information including whether or not a purchase order exists for each contract number, and transitions to the purchase order registration screen when a predetermined operation is performed by the operator. In the construction status inquiry process, it checks whether purchase orders have been collected in a list (by contract number), and for those that are not registered, it transitions to the purchase order registration screen 500 to register the purchase order.

[0071] Figure 8A shows an example of the display of the construction status inquiry screen 600. The construction status inquiry screen 600 includes an area for specifying extraction conditions, which can be set to include project number, contract number, project name, customer, order date, planned sales date, and whether or not a purchase order exists; a results display area that extracts and displays contract information and purchase order information (contract information header data, contract information detail data, purchase order information header data) that match the extraction conditions; and a display button to start the extraction and display. When the operator specifies the extraction conditions and presses the display button, the contract information and purchase order information that match the extraction conditions are extracted and displayed in the results display area. In the example shown in the figure, all extraction conditions are specified.

[0072] When you click (for example) the "Order Form Availability" option in the results display area, a pop-up will appear that will take you to the order form list screen or the order form input screen. In the pop-up, clicking "Order Form List" will take you to the order form list screen, and clicking "Register Order Form" will take you to the order form registration screen.

[0073] For records with a purchase order status of 0: None, the operator navigates from the construction status inquiry screen to the purchase order registration screen. If a purchase order has not actually been attached, the operator attaches one and updates the purchase order status to "1: Yes" on the purchase order registration screen. If a purchase order has actually been attached but there was an input error, the operator corrects (updates) the purchase order status to "1: Yes". The value set for the purchase order status is obtained from the purchase order status in the purchase order information on the purchase order registration screen. The purchase order status registered in purchase order registration only reflects the contract number listed in the purchase order registration header. It is not reflected in the contract number in the breakdown information.

[0074] Figures 8B(A)-(C) show examples of contract information header data, contract information detail data, and purchase order information header data. The contract number serves as the join key, and the project number, contract status, customer, project name, contract period, order date, and planned sales date of the contract information header data are also included. The contract information details data, including the contract amount excluding tax, the contract consumption tax amount, the contract amount including tax, and the purchase order information header data (whether or not a purchase order exists) will be displayed in the results display area.

[0075] For example, on the construction status inquiry screen 600, if you press "0: None" for the purchase order status category on the second row (project number "PJ0002", contract number "PJ0002001") and then press "Register Purchase Order", the purchase order registration screen 500 shown in Figure 8C will be displayed. When transitioning from the construction status inquiry screen 600 to the purchase order registration screen 500, the contract number information selected during the construction status inquiry is set as header information and contract information. The control of the purchase order registration screen is the same as for INPUT(2). If the operator has already registered a purchase order linked to other contract information (contract number: PJ0002001 has already been registered in INPUT(2)), they change the purchase order status category to "1: Yes" and set the contract number to which the purchase order was registered (in this example, PJ0001001) in "Contract Number to which Purchase Order is Attached". When the registration button (not shown) is pressed, the purchase order information in the storage unit 106 is updated. Do not enter purchase order information or item breakdown information.

[0076] Figures 9(A) to 9(C) show examples of updated order information header data, order information detail data, and breakdown information detail data. As shown in Figure 9(A), a second record is added to the order information header data; as shown in Figure 9(B), no record is added to the order information detail data; and as shown in Figure 9(C), a fourth record is added to the breakdown information detail data.

[0077] 4. INPUT(4) Refer to Figures 10 to 14B to explain the details of INPUT(4). The sales input unit 102e, for example, in response to the operator's operation on the sales input screen displayed on the monitor 114, when recording sales for the target project number and contract number, refers to the contract information and purchase order information registered in the storage unit 106 to check whether the contract amount and the purchase order amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met. In the sales input process, the possibility of sales is determined by checking the amount, order period, or presence or absence of a purchase order as follows: (1) The purchase order information is marked as "Presence or Absence of Purchase Order: Yes", (2) The purchase order amount including tax in the purchase order information is equal to the contract amount including tax in the contract information, and (3) The contract period in the contract information is included in the actual construction period in the purchase order information.

[0078] Figure 10 shows an example of the sales input screen 700. The sales input screen 700 is a screen for inputting sales information and includes a header for inputting project number, contract number, responsible department, planned sales date, and customer; a sales candidate display area (selection box, where contract information is displayed) for displaying contract information as sales candidates; a display button for displaying in the sales candidate display area; and a registration button (not shown). When the display button is pressed, the contract information stored in the storage unit 106 is extracted using the project number and contract number as keys and displayed as sales candidates in the sales candidate display area. When the registration button (not shown) is pressed, if sales can be recorded, sales information corresponding to the input on the screen is stored in the storage unit 106.

[0079] Only contract numbers with a "Yes" status in the purchase order information linked by the contract number will be displayed as sales candidates. From the sales candidates displayed, the operator selects the items to be actually recorded as sales using the selection box. When registering a sale, an error occurs if the tax-inclusive purchase order amount in the breakdown information of the purchase order information does not match the tax-inclusive contract amount in the contract information. An error also occurs if the contract period in the contract information is not included in the actual work period in the purchase order information. In the event of an error, a pop-up corresponding to the error will be displayed to notify the operator. Accordingly, the operator will correct the tax-inclusive purchase order amount in the purchase order information or the tax-inclusive contract amount in the contract information, or correct the contract period in the contract information or the actual work period in the purchase order information.

[0080] In the example shown in Figure 10, since the project number and contract number are not specified, the sales candidate display area includes all contract information stored in the memory unit 106. However, the purchase order information associated with contract number "PJ0003001" is excluded because the purchase order status is "none," and the contract information for contract numbers "PJ0001001" and "PJ0002001" is displayed in the first and second rows. In this example, the first row is selected. Regarding the contract number "PJ0001001" on the first line, the contract period "2024 / 4 / 1~2025 / 3 / 32" in the contract information is included in the actual construction period "2024 / 4 / 1~2025 / 11 / 30" in the purchase order information, and the tax-inclusive contract amount "1,100,000" in the contract information matches the tax-inclusive purchase order amount "1,100,000" in the purchase order information, so there is no error and sales can be recorded, and when the "Register (Not Illustrated)" button is pressed, the sales information is registered in the storage unit 106.

[0081] Refer to Figure 11 to see an example of how a pop-up might appear in case of an error. Figure 11(A) shows an example of an error pop-up appearing on the sales entry screen 700. In the example shown, the pop-up displays the message, "Contract number PJ0001001: The contract period is not included in the actual construction period." (Note that in the example in Figure 10, no error occurs, so this example is an example of how an error would appear.)

[0082] Figure 11(B) is a diagram illustrating a pattern where sales cannot be recognized. A pop-up like the one shown in the figure may be displayed. The figure shows No., contract information data (contract number, contract period, tax-inclusive contract amount), purchase order information data (purchase order existence / absence classification), purchase order information details data (actual construction period (start), actual construction period (end)), breakdown information details data (tax-inclusive contract amount), and whether sales can be recognized or not (possible: ○, not possible: ×). In this example, the case of contract number PJ0001001 is shown, but No. "1" is an example of disclosed data, while Nos. "2" to "7" are data for explanation. In No. "1", "purchase order existence / absence classification: Yes", tax-inclusive purchase order amount = tax-inclusive contract amount, and the contract period is included in the actual construction period, so sales can be recognized (○). In Nos. "2" to "4", the contract period is not included in the actual construction period, so sales cannot be recognized (×). In No. "5", tax-inclusive purchase order amount = tax-inclusive contract amount, so sales cannot be recognized (×). Items No. "6" and "7" are marked as "No Purchase Order" and therefore cannot be recorded as sales (×).

[0083] Figure 11(C) corresponds to Figure 11(B) and shows the error details and remarks. No. "1" has the remark "No error as sales are possible." Nos. "2" to "4" have the error details "The contract period is not included in the actual construction period," and the remark "Correct the contract period in the contract information or the actual construction period in the purchase order registration." No. "5" has the error details "The contract period is not included in the actual construction period," and the remark "Correct the contract period in the contract information or the actual construction period in the purchase order information." Nos. "6" and "7" have the remark "The purchase order status is 'None,' so it is not displayed as a sales candidate."

[0084] Figures 12(A) to (E) show examples of contract information header data, contract information detail data, purchase order information header data, purchase order information detail data, and breakdown information detail data. The contract number and header contract number serve as join keys, and the project number, contract status, customer, project name, contract period, order date, and planned sales date in the contract information header data, the contract amount excluding tax, contract consumption tax amount, and contract amount including tax in the contract information detail data, and the purchase order existence / existence classification in the purchase order information header data become display items in the sales candidate display area.

[0085] Refer to Figures 13A and 13B to explain the steps for extracting data to be displayed in the sales candidate display area.

[0086] STEP 1: Retrieve unsold contracts and extract only those with a purchase order (i.e., only those for which purchase orders have been collected). An unsold contract refers to a contract where no sales have been made against the contract amount, or a contract where only a portion of the contract amount has been sold. The contract number in the contract information header data = the contract number in the purchase order information header data AND the purchase order status in the purchase order information header data.

[0087] Figure 13A(A) shows an example of contract information header data, and Figure 13A(B) shows an example of purchase order information header data. The third row of the contract information header data is not extracted because the purchase order status is "none".

[0088] STEP 2: Extract contract information details data, purchase order information details data, and breakdown information details data from the data extracted in STEP 1.

[0089] Figure 13B(A) shows an example of extracted contract information header data, and Figure 13B(B) shows an example of extracted purchase order information header data.

[0090] STEP 2-1: Identify the contract information details data by contract number. Figure 13B(C) shows an example of the extracted contract information details data.

[0091] STEP 2-2: Identify the order form details data by contract number. Figure 13B(D) shows an example of the extracted order information details data.

[0092] STEP 2-3: Identify the detailed breakdown data by contract number. Figure 13B(E) shows an example of the extracted breakdown information data.

[0093] Refer to Figures 14A and 14B to explain the logic for checking whether a sale can be recorded. The logic for checking whether a sale can be recorded involves checking the amount and the project duration. If both checks are OK, the sale is considered recordable.

[0094] Refer to Figure 14A to explain the amount check. In the amount check, the tax-inclusive contract amount in the contract information details data and the tax-inclusive purchase order amount in the breakdown information details data are checked, and if the amounts match, it is OK.

[0095] Figure 14A(A) shows the extracted contract information details data, and Figure 14A(B) shows the extracted breakdown information details data. The breakdown information details data is checked by summing the amounts by contract number. For each contract number, the tax-inclusive contract amount in the contract information details data and the tax-inclusive order amount in the breakdown information details data are checked. In the example shown in the figure, the amount check is OK.

[0096] Refer to Figure 14B to explain the construction period check. In the construction period check, the contract period in the contract information header data and the actual construction period (from) and actual construction period (to) in the purchase order information details data are checked. If the contract period in the contract information header data is within the construction period in the purchase order information details data, it is considered OK.

[0097] Figure 14B(A) shows the extracted contract information header data, and Figure 14B(B) shows the extracted purchase order information detail data. In this example, for contract number PJ0001001, the contract period is within the actual construction period, so the construction period check is OK.

[0098] Figure 14B(C) is a diagram to provide supplementary information regarding the actual construction period. As shown in the example in the figure, purchase order information details may consist of multiple details, so the purchase order information details should be checked by extracting the minimum value of the actual construction period (from) to the maximum value of the actual construction period (to) within the same contract. In this example, the minimum value of the actual construction period (from) is 2024 / 4 / 1, and the maximum value of the actual construction period (to) is 2025 / 11 / 30. The actual construction period from 2024 / 4 / 1 to 2025 / 11 / 30 is then compared with the contract period in the contract information header data to check for consistency of the period.

[0099] As described above, according to this embodiment, a contract information input unit 102b registers contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount in the storage unit 106 in response to the operator's operation on the contract input screen; an order registration unit 102c registers order information including contract number, storage location, order presence / absence classification specifying whether or not an order is attached, line, receipt date, actual construction period, and order amount in the storage unit 106 in response to the operator's operation on the order registration screen; and a sales input unit 102e, in response to the operator's operation on the sales input screen, checks whether the contract amount and the order amount match and whether the contract period is within the actual construction period by referring to the contract information and the order information registered in the storage unit 106 when recording sales for the target project number and contract number, and enables sales recording if the conditions are met. As such, it is possible to strengthen control over revenue recording with low workload for contracts and orders.

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

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

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

[0103] [5. 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.

[0104] 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.

[0105] 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.

[0106] Furthermore, with respect to the purchase order / contract checking device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0107] For example, the processing functions of the order / contract checking device 100, particularly those performed by the control unit 102, 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 the information processing device to execute the processing described in this embodiment, and is mechanically read by the order / contract checking device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0108] Furthermore, this computer program may be stored on an application program server connected to the order / contract checking device 100 via any network, and it is possible to download all or part of it as needed.

[0109] 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.

[0110] 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 this embodiment, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0111] The various databases stored in the memory unit 106 include 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.

[0112] Furthermore, the order form / contract checking device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the order form / contract checking device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the device.

[0113] 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. [Explanation of Symbols]

[0114] 100 Purchase Order / Contract Checking Device 102 Control Unit 102a Project Information Input Section 102b Contract Information Input Section 102c Order Form Registration Department 102d Construction Status Inquiry Department 102e Sales Input Section 102f Screen Display Control Unit 104 Communication Interface Section 106 Storage section 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks 400 Contract Information Input Screen 500 Order Form Registration Screen 600 Construction Status Inquiry Screen 700 Sales entry screen

Claims

1. A purchase order / contract checking device equipped with a control unit, The control unit, A contract information input means that registers contract information, including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount, in a storage area in response to the operator's actions on the contract input screen. A purchase order registration means registers purchase order information, including the contract number, storage location, purchase order presence / absence classification (specifying whether or not a purchase order is attached), line number, receipt date, construction period, and purchase order amount, in the storage area in response to the operator's operation on the purchase order registration screen. A sales input means that, in response to an operator's operation on the sales input screen, when recording sales for the target project number and contract number, refers to the contract information and purchase order information registered in the storage area to check whether the contract amount and purchase order amount match and whether the contract period is within the actual construction period, and enables sales recording if the conditions are met. A purchase order / contract checking device characterized by having the following features.

2. The order form / contract checking device according to claim 1, characterized in that the sales input means displays and outputs an error if the conditions are not met.

3. The order form / contract checking device according to claim 2, characterized in that when the sales input means outputs the error, it outputs a pop-up indicating the error details.

4. The control unit, The order form / contract checking device according to claim 1, characterized in that it includes an inquiry means that, in response to an operator's operation on the inquiry screen, refers to the contract information and order form information registered in the storage area, displays information including the presence or absence of the order form on a contract number basis, and transitions to the order form registration screen when a predetermined operation is performed by the operator.

5. The order form / contract checking device according to any one of claims 1 to 4, characterized in that the sales input means displays the contract information for contract numbers where the order form existence / absence classification is "Yes" as a sales candidate.

6. A method for checking purchase orders and contracts, which is performed by an information processing device equipped with a control unit, The control unit is executed as follows: A contract information input process in which, in response to the operator's actions on the contract input screen, contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount is registered in the storage area, A purchase order registration process in which, in response to the operator's operation on the purchase order registration screen, purchase order information including the contract number, storage location, purchase order presence / absence classification (specifying whether or not a purchase order is attached), line number, receipt date, construction period, and purchase order amount is registered in the aforementioned storage area, A sales entry process that, in response to operator operations on the sales entry screen, records sales for the target project number and contract number by referring to the contract information and purchase order information registered in the memory area, checking whether the contract amount and purchase order amount match and whether the contract period is within the actual construction period, and enabling sales recording if the conditions are met. A method for checking purchase orders and contracts, characterized by including the following features.

7. A purchase order / contract checking program to be executed by an information processing device equipped with a control unit, The control unit, A contract information input process in which, in response to the operator's actions on the contract input screen, contract information including project number, contract number, contract period, order date, planned sales date, line, product, and contract amount is registered in the storage area, A purchase order registration process in which, in response to the operator's operation on the purchase order registration screen, purchase order information including the contract number, storage location, purchase order presence / absence classification (specifying whether or not a purchase order is attached), line number, receipt date, construction period, and purchase order amount is registered in the aforementioned storage area, A sales entry process that, in response to operator operations on the sales entry screen, records sales for the target project number and contract number by referring to the contract information and purchase order information registered in the memory area, checking whether the contract amount and purchase order amount match and whether the contract period is within the actual construction period, and enabling sales recording if the conditions are met. A purchase order and contract checking program to enable execution.

Images