Order management device, order management method, and order management program

Abstract

We provide order management equipment and other devices that make it easy to grasp the revenue of the construction division. [Solution] The order management device according to the present invention comprises an order processing unit, a cost processing unit, a journal entry processing unit, and a completion processing unit. The order processing unit creates project information, including source identification information, for each department for each order. The cost processing unit receives input of information regarding the cost of interdepartmental transactions associated with the project information. The journal entry processing unit registers the information regarding the interdepartmental transactions as incomplete items in the first accounting data for each department. The completion processing unit receives input of information accompanying the completion of the interdepartmental transactions. In the second accounting data on which the contents of the first accounting data have been transferred, the journal entry processing unit generates a journal entry to transfer the incomplete items to completed items in accordance with the information accompanying the completion of the interdepartmental transactions, at the time when sales for the project have not yet been recorded.

Description

Technical Field

[0001] The present invention relates to an order reception management device, an order reception management method, and an order reception management program.

Background Art

[0002] For example, in the construction industry, etc., the sales department that contracts orders from outside the company and the construction department that is responsible for the actual work of the construction are managed separately. At that time, although the actual sales related to the order occur in the sales department, no sales occur in the construction department, so it is difficult to grasp the profit in the construction department.

[0003] For example, in the in-house order reception department (construction department), there is a known technology that automatically recognizes the costs in progress / raw costs associated with the cases in the order reception department according to the sales status of the cases in the in-house order issuing department (sales department).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the above technology, the processing may become complicated, such as the need for a journal entry to transfer the costs once recorded as the cost of sales to the work-in-progress cost.

[0006] The present invention has been made in view of the above, and an object thereof is to provide an order reception management device, an order reception management method, and an order reception management program capable of easily grasping the profit in the construction department.

Means for Solving the Problems

[0007] To solve the above-mentioned problems and achieve the objective, the order management device according to the present invention comprises an order processing unit, a cost processing unit, a journal entry processing unit, and a completion processing unit. The order processing unit creates project information, including source identification information, for each department for each order. The cost processing unit receives input of information regarding the cost of interdepartmental transactions associated with the project information. The journal entry processing unit registers the information regarding the interdepartmental transactions as incomplete items in the first accounting data for each department. The completion processing unit receives input of information accompanying the completion of the interdepartmental transactions. In the second accounting data on which the contents of the first accounting data have been transferred, the journal entry processing unit generates a journal entry to transfer the incomplete items to completed items at the time when sales for the project have not yet been recorded, in accordance with the information accompanying the completion of the interdepartmental transactions.

[0008] Furthermore, the order management method according to the present invention includes the steps of: creating order information including order source identification information for each department for each order; receiving input of information regarding the cost of interdepartmental transactions associated with the order information; registering the information regarding interdepartmental transactions as incomplete items in first accounting data for each department; receiving input of information accompanying the completion of the interdepartmental transactions; and in second accounting data on which the contents of the first accounting data have been transferred, generating a journal entry to transfer the incomplete items to completed items in accordance with the information accompanying the completion of the interdepartmental transactions, at a time when sales for the order have not yet been recorded.

[0009] Furthermore, the order management program according to the present invention performs the following steps: creating order information including source identification information for each department for each order; receiving input of cost information for interdepartmental transactions associated with the order information; registering the interdepartmental transaction information as an incomplete item in the first accounting data for each department; receiving input of information accompanying the completion of the interdepartmental transaction; and in the second accounting data on which the contents of the first accounting data have been transferred, generating a journal entry to transfer the incomplete item to a completed item at the time when the sales for the order have not been recorded, in accordance with the information accompanying the completion of the interdepartmental transaction. [Effects of the Invention]

[0010] According to the present invention, it becomes possible to easily grasp the revenue of the construction department for projects that include internal transactions. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 shows an example of the relationship between the main contract and interdepartmental transactions in an embodiment. [Figure 2] Figure 2 shows an example of the configuration of an order management system according to the present invention. [Figure 3] Figure 3 shows an example of an order management system according to an embodiment. [Figure 4] Figure 4 shows an example of a project cost account classification master and a product-specific account account master stored in the master storage unit of the order management device according to the embodiment. [Figure 5] Figure 5 shows an example of the information stored in the data storage unit of the order management device according to this embodiment. [Figure 6] Figure 6 shows an example of project data stored in the data storage unit of the order management device according to the embodiment. [Figure 7] Figure 7 shows an example of contract information data stored in the data storage unit of the order management device according to the embodiment. [Figure 8]FIG. 8 is a diagram showing an example of cost data stored in the data storage unit of the order management apparatus according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of journal entry data stored in the data storage unit of the order management apparatus according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of information stored in the accounting data stored in the data storage unit of the order management apparatus according to the embodiment. [Figure 11] FIG. 11 is a diagram showing an example of accounting data according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of sales data stored in the data storage unit of the order management apparatus according to the embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a contract information input screen according to the embodiment. [Figure 14] FIG. 14 is a diagram showing another example of a contract information input screen according to the embodiment. [Figure 15] FIG. 15 is a diagram showing another example of a contract information input screen according to the embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a journal entry data creation screen according to the embodiment. [Figure 17] FIG. 17 is a diagram showing another example of a journal entry data creation screen according to the embodiment. [Figure 18] FIG. 18 is a diagram showing another example of journal entry data according to the embodiment. [Figure 19] FIG. 19 is a diagram showing another example of cost data according to the embodiment. [Figure 20] FIG. 20 is a diagram showing another example of a journal entry data creation screen and journal entry data according to the embodiment. [Figure 21] FIG. 21 is a diagram showing another example of a journal entry data creation screen and journal entry data according to the embodiment. [Figure 22] FIG. 22 is a diagram showing another example of accounting data according to the embodiment. [Figure 23] FIG. 23 is a diagram showing another example of sales data according to the embodiment. [Figure 24] Figure 24 shows another example of journal entry data according to the embodiment. [Figure 25] Figure 25 shows another example of cost data according to the embodiment. [Figure 26] Figure 26 shows another example of journal entry data according to the embodiment. [Figure 27] Figure 27 shows another example of journal entry data according to the embodiment. [Figure 28] Figure 28 shows another example of accounting data according to the embodiment. [Figure 29] Figure 29 shows another example of sales data according to the embodiment. [Figure 30] Figure 30 shows another example of journal entry data according to the embodiment. [Figure 31] Figure 31 shows another example of journal entry data according to the embodiment. [Figure 32] Figure 32 shows another example of accounting data according to the embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to these embodiments.

[0013] [1. Overview] In the construction industry, a contract secured by the sales department may lead to the conclusion of other contracts in interdepartmental transactions with the construction department. The relationship between the contract information in this embodiment will be explained using Figure 1. Figure 1 is a diagram showing an example of the relationship between the main contract and interdepartmental transactions in this embodiment. In the following explanation, Sales Department Section 1 is an example of a sales department, and Engineering Department Section A and Engineering Support Section are examples of construction departments.

[0014] For example, as shown in Figure 1, Sales Department 1, which is part of the sales division, receives a contract with order number "JU0001" as the main contract for a "completed construction project" that is not an interdepartmental transaction.

[0015] In this embodiment, Sales Department Section 1 places an order for a portion of the construction work under contract number "JU0001" with Technical Department Section A, which is the construction department, and Technical Department Section A accepts the order as contract number "JU0002". This contract is subordinate to the main contract, and the construction work associated with this contract is considered "internal sales" as an interdepartmental transaction. In this embodiment, the explanation of construction work that Sales Department Section 1 performs itself or outsources is omitted.

[0016] Technical Department Section A further associates the order number "JU0001" from Sales Department Section 1, the ordering party, with the contract with order number "JU0002".

[0017] In this embodiment, Engineering Department Section A, which received the contract with order number "JU0002", further subcontracts a portion of the work associated with the contract to another construction department, the Technical Support Section, which then receives the contract with order number "JU0003". This contract is also subordinate to the main contract, and the work associated with this contract also constitutes "internal sales" as an interdepartmental transaction.

[0018] In this case, the Technical Support Section further associates the order number "JU0002" of the Technical Department A Section, which is the ordering party, with the contract with order number "JU0003".

[0019] As shown in Figure 1, the contract with order number "JU0003" is subordinate to the contract with order number "JU0002," and the contract with order number "JU0002" is subordinate to the contract with order number "JU0001." In this embodiment, a common project number "PJ0001" is assigned to each contract that has a master-subordinate relationship with the others. Note that the project number is an example of the source identification information. The order details for each contract shown in Figure 1 will be explained in detail later.

[0020] Note that while Figure 1 illustrates an example where two interdepartmental transaction contracts are subordinate to the main contract corresponding to the completed construction work, there may be only one interdepartmental transaction contract corresponding to the completed construction work, or there may be three or more. Also, for example, the Technical Support Section may receive orders directly from Sales Section 1 rather than from Technical Section A.

[0021] [2. Structure] Referring to Figures 2 and 3, an example of the configuration of the order management system according to this embodiment will be described. Figure 2 is a diagram showing an example of the configuration of the order management system 1 according to this embodiment. Figure 3 is a diagram showing an example of the order management device 100 according to this embodiment. The order management system according to this embodiment can be used in companies such as construction companies, where sales and construction departments are managed separately.

[0022] In Figure 2, the order management system 1 is configured, for example, as a server-client system, with an order management device 100 that functions as a server and multiple terminal devices 200 that are able to communicate with each other via a network 300.

[0023] The order management device 100 provides various input screens to the terminal device 200 in response to requests from the terminal device 200, accepts information input from the terminal device 200 on these screens, and centrally manages the received information using various data in the storage unit. In addition, the order management device 100 provides information on various data and generated accounting processes (end-of-month processing, management accounting, financial accounting, etc.) in response to requests from the terminal device 200, allowing the terminal device 200 to view the information on various data and the processed accounting information.

[0024] The order management device 100 can be configured, for example, as a workstation or a personal computer.

[0025] Terminal devices 200 are deployed in various departments within the company (for example, Sales Department Section 1, Engineering Department Section A, Technical Support Section, Management Department, etc.). Each terminal device 200 is equipped with a monitor, keyboard, printer, etc., and displays various input screens provided by the order management system 100 on the monitor, allowing the person in charge (operator) to perform various inputs. In addition, each terminal device 200 can display information on various data stored by the order management system 100 and information on generated accounting processes (end-of-month processing, management accounting, financial accounting, etc.) on the monitor, allowing users to view this information.

[0026] Terminal device 200 may be, for example, a commercially available desktop personal computer, and 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, and tablet personal computers. In the following, when distinguishing between terminal devices 200, for example, one located in Sales Department Section 1 may be referred to as terminal device 201. Similarly, one located in Technical Department Section A may be referred to as terminal device 202, one located in Technical Support Section as terminal device 203, and one located in the Management Department as terminal device 204.

[0027] In Figure 3, the order management 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 order management device 100 is connected to communicate via any communication path.

[0028] The communication interface unit 104 connects the order management device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines, enabling communication between the network and the order management device 100. 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 management device 100 and the terminal device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

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

[0030] As shown in Figure 3, the storage unit 106 includes a master storage unit 106a and a data storage unit 106b.

[0031] As shown in Figure 4, the master storage unit 106a stores the PJ cost account classification master 106aa and the product-specific account master 106ab. Figure 4 is a diagram showing an example of the PJ cost account classification master 106aa and product-specific account master 106ab stored in the master storage unit 106a of the order management device 100 according to this embodiment. The PJ cost account classification master 106aa is used when assigning accounts to items in the cost data 106bc, which will be explained later. The product-specific account master 106ab is used when assigning accounts to items in the contract information data 106bb, which will be explained later.

[0032] The PJ cost account classification master 106aa stores PJ cost account classifications, associating them with work-in-progress accounts and completed accounts.

[0033] For example, the first row of PJ Cost Account Classification Master 106aa in Figure 4 indicates that if the "PJ Cost Account Classification" item in cost data 106bc is "Materials Cost," then the work-in-progress account "Materials Cost (Unfinished)" or the completed account "Materials Cost (Completed)" will be assigned to that item.

[0034] Furthermore, the first row of the product-specific account master 106ab in Figure 4 indicates that if the "Product" item in the contract information data 106bb is "Construction Package" and the "Account Receivable Classification" item is "Accounts Receivable for Completed Construction," then the account "Completed Construction Value" is assigned.

[0035] As shown in Figure 5, the data storage unit 106b stores project data 106ba, contract information data 106bb, cost data 106bc, journal entry detail data 106bd, accounting data 106be, and sales data 106bf. Figure 5 is an example of the information stored in the data storage unit 106b of the order management device 100 according to this embodiment.

[0036] Project data 106ba stores information about the ordered project (PJ). Figure 6 shows an example of project data 106ba stored in the data storage unit 106b of the order management device 100 according to this embodiment. As shown in Figure 6, project data 106ba stores the project number, the project name, and the department that received the order for the "completed construction work" in the project in association with each other.

[0037] As shown in Figure 7, the contract information data 106bb stores information about contracts corresponding to "completed construction" and "internal sales" for a project. Figure 7 is a diagram showing an example of the contract information data 106bb stored by the data storage unit 106b of the order management device 100 according to this embodiment. As shown in Figure 7, the contract information data 106bb registers the "project number" in association with the "order number", "project name", "department", "order date", "construction period", "type of construction", "product", and "accounts receivable classification". In addition, the contract information data 106bb also registers the "contract amount", "consumption tax", "internal sales amount", "requesting order number", and "main order number". Note that the contract information registered in the contract information data 106bb is an example of case information.

[0038] The "Project Name" field will contain the information registered in project data 106ba. On the other hand, the "Department" field will contain the department that received the order for the project specified by "Order No.", rather than the contents of project data 106ba. For example, in data bb11 for order No. "JU0002," which is subordinate to order No. "JU0001," "B002: Engineering Department A" will be registered, and in data bb12 for order No. "JU0003," which is subordinate to order No. "JU0002," "B003: Technical Support Department" will be registered.

[0039] The "Type of Construction," "Product," and "Accounts Receivable Classification" fields will have different entries depending on whether or not they fall under "Interdepartmental Transactions." For example, in data bb01 for order number "JU0001," which is the main construction project, "Completed Construction," "Complete Construction Settlement," and "Accounts Receivable for Completed Construction" will be registered, as well as the "Contract Amount" and "Consumption Tax" amounts. On the other hand, in data bb11 for order number "JU0002" and data bb12 for order number "JU0003," which are subordinate to order number "JU0001," "Internal Sales" and "Internal Purchases" will be registered, as well as the "Internal Sales Amount" amount.

[0040] The "Requesting Order Number" field registers the order number of the contract to which the contract for that order number belongs. In this case, the "Requesting Order Number" is not registered in the data for order number "JU0001," which corresponds to "Completed Construction Work." On the other hand, the "Main Order Number" field registers the order number "JU0001," the main contract for the project, in all data bb01, bb11, and bb12, regardless of whether it corresponds to "Completed Construction Work" or not, and regardless of the order number of the direct requesting party.

[0041] Cost data 106bc stores information regarding costs incurred in relation to construction work associated with a contract. As shown in Figure 8, cost data 106bc stores the "voucher number" and "line number" in association with "project number," "order number" and "line number," "accounting date," "department," "project cost account category," "liability account category," and "amount." Figure 8 is an example of a diagram showing an example of cost data 106bc stored by the data storage unit 106b of the order management device 100 according to the embodiment. In addition, as shown in Figure 8, "completion transfer month and year" and "internal transfer flag" are further registered in cost data 106bc. The completion transfer month and year is the month and year in which the construction work corresponding to the cost was completed. The completion transfer flag has an initial value of "0" and is updated to "1" when the completion transfer month and year is registered. The process of updating the completion transfer flag will be explained in detail later.

[0042] As shown in Figure 8, for example, data bc11 regarding the cost of invoice number "GK001" and line number "1" shows the cost of the construction work for line number "1" in the order for project number "PJ0001" and order number "JU0002". This cost is the cost of "materials" for the construction work ordered by department "B002: Engineering Department A" and recorded on "August 1, 2024". The liability account classification is "Construction Accounts Payable" and the amount is "1 million yen". Furthermore, this construction work does not have a "Completion Transfer Year and Month" registered, meaning it is an uncompleted construction work, and the "Completion Transfer Flag" has not been updated from "0".

[0043] The journal entry details data 106bd stores information about journal entries generated from various data. As shown in Figure 9, the journal entry details data 106bd registers the "voucher number" and "line number," "business location," "date of occurrence," and the "account title," "business location," "department," and "amount" for both the debit and credit sides. Figure 9 is an example of a diagram showing an example of the journal entry details data 106bd stored in the data storage unit 106b of the order management device 100 according to the embodiment. Also, as shown in Figure 9, the journal entry details data 106bd also registers a "project code." The "project code" is, for example, a combination of the "project number," "order number," and "line number," as shown in Figure 9.

[0044] The journal entry detail data 106bd shown in Figure 9 is generated, for example, from the cost data 106bc shown in Figure 8. From this journal entry detail data 106bd, a journal entry bd11, for example, as shown in Figure 9, is generated through a process that will be explained later. The process for generating the journal entry detail data 106bd, and the information generated from other data and stored in the journal entry detail data 106bd, will be explained in detail later.

[0045] The accounting data 106be is data generated based on the journal entry detail data 106bd. As shown in Figures 10 and 11, the accounting data 106be includes company-wide data be10, sales department 1 data be11, technology department A data be12, and technical support department data be13. Figure 10 is a diagram showing an example of the information stored in the accounting data 106be stored in the data storage unit 106b of the order management device 100 according to this embodiment. Figure 11 is a diagram showing an example of the accounting data 106be. The data shown in Figure 11 is generated, for example, from the journal entry shown in Figure 9. In this case, as shown in Figure 11, no information is registered in the data be11 for "Sales Department 1". Also, the company-wide data be10 is the sum of the amounts in technology department A data be12 and technical support department data be13.

[0046] Furthermore, as shown in Figure 11, accounting data 106be includes financial accounting data be1 and management accounting data be2. Note that financial accounting data be1 is an example of the first accounting data, and management accounting data be2 is an example of the second accounting data.

[0047] In this embodiment, the contents of the financial accounting data be1 are registered directly in the management accounting data be2. On the other hand, as will be explained later, in this embodiment, journal entries made for the management accounting data be2 may not be reflected in the financial accounting data be1.

[0048] The sales data 106bf stores information about sales, for example, that has been input from the terminal device 200. As shown in Figure 12, the sales data 106bf stores the "invoice number" and "line number" in association with "project number," "order number" and "line number," "recording date," "department," and "contract amount," "consumption tax," and "internal sales amount." Figure 12 is a diagram showing an example of sales data 106bf stored by the data storage unit 106b of the order management device 100 according to the embodiment. As shown in Figure 12, for example, the sales information for invoice number "UR001" and line number "1" indicates the sales of the construction work for line number "1" in the order for project number "PJ0001" and order number "JU0003." This sales were recorded on "August 31, 2024" by department "B003: Technical Support Section," and the internal sales amount is "3 million yen." Furthermore, since this construction work falls under "internal sales," the "contract amount" and "consumption tax" will not be recorded.

[0049] Sales data 106bf is registered when the construction associated with each contract is completed. In this embodiment, when the construction associated with a subordinate contract is completed, data bf11 is registered in sales data 106bf even before the construction associated with the main contract is completed, as shown in Figure 12, for example.

[0050] The control unit 102 is a CPU or the like that comprehensively controls the order management 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. Functionally, the control unit 102 comprises an order processing unit 102a, a cost processing unit 102b, a completion processing unit 102c, and a journal entry processing unit 102d.

[0051] [3. Processing executed by the control unit 102] The order processing unit 102a processes project-related information and order-related information. The order processing unit 102a displays input screens as shown in Figures 13 to 15 on the terminal devices 200 of each department, and creates (generates) and updates case information in accordance with the operations of the person in charge on the input screen, and registers and updates it in the contract information data 106bb.

[0052] Figure 13 shows an example of a contract information input screen according to the embodiment. The contract information input screen S11 shown in Figure 13 is displayed, for example, on terminal device 201 of Sales Department 1. As shown in Figure 13, the contract information input screen S11 includes fields for inputting "Project Number", "Order Number - Line Number", "Department", "Order Date" and "Construction Period", "Type of Construction", "Requesting Order Number", and "Main Order Number". The contract information input screen S11 also further includes an input box S111 for inputting details of the contract information. The input box S111 is associated with the "Line" and inputs "Product", "Accounts Receivable", "Quantity" and "Unit", "Unit Price", "Contract Amount" or "Internal Sales Amount", and "Consumption Tax". In this embodiment, the information entered in the contract information input screen S11 corresponds to data bb01 of order number "JU0001" in contract information data 106bb.

[0053] In the contract information input screen S11 shown in Figure 13, the order number "JU0001" entered is related to the main contract, so the requesting order number is not entered. On the other hand, the project number "PJ0001" is entered as the main order number.

[0054] The order processing unit 102a also displays the contract information input screen S12 shown in Figure 14 and the contract information input screen S13 shown in Figure 15 on the terminal device 202 of the Technical Department A section and the terminal device 203 of the Technical Support section, respectively. Figures 14 and 15 are diagrams showing another example of the contract information input screen according to the embodiment. In the contract information input screen S12 shown in Figure 14, the contract with order number "JU0002" shown in the information entered is subordinate to the main contract with order number "JU0001", so the requesting order number is displayed as order number "JU0001". Similarly, in the contract information input screen S13 shown in Figure 15, the contract with order number "JU0003" shown in the information entered is subordinate to order number "JU0002", so the requesting order number is displayed as order number "JU0002". In this embodiment, the information entered in the contract information input screen S12 shown in Figure 14 corresponds to data bb11 of order number "JU0002" in contract information data 106bb, and the information entered in the contract information input screen S13 shown in Figure 15 corresponds to data bb12 of order number "JU0003" in contract information data 106bb. In both Figure 14 and Figure 15, the main order number is entered as project number "PJ0001," as in Figure 13.

[0055] In other words, the order processing unit 102a creates order information for each order, including the project number which is the order source identification information, for each department such as Sales Department Section 1, Technical Department Section A, and Technical Support Section.

[0056] Furthermore, the order processing unit 102a displays an input screen (not shown) on the terminal device 201 of Sales Department 1, and creates (generates) and updates case information according to the operations of the person in charge on the input screen, and registers and updates it in the project data 106ba.

[0057] The cost processing unit 102b processes cost-related information. Based on the operations of the person in charge on the input screen (not shown) of each department's terminal device 200, the cost processing unit 102b creates and updates costs, including sales numbers, case numbers, and internal sales amounts, and registers and updates them in the cost data 106bc. As a result, data bc11 to bc15, as shown in Figure 8, are registered in the cost data 106bc. In other words, the cost processing unit 102b accepts input of cost-related information for interdepartmental transactions associated with case information.

[0058] The completion processing unit 102c performs the process of registering sales information associated with the completion of construction work. The completion processing unit 102c creates and updates information including order number and sales amount in response to the operations of the person in charge on the input screen (not shown) of the terminal device 200 of each department, and registers and updates it in the sales data 106bf. As a result, data bf11 as shown in Figure 12 is registered in the sales data 106bf. Note that the information including order number and sales amount is an example of information associated with the completion of an interdepartmental transaction.

[0059] The journal entry processing unit 102d generates journal entries using cost data 106bc and sales data 106bf. The journal entry processing unit 102d also registers the data based on the generated journal entries into accounting data 106be.

[0060] The journal entry processing unit 102d performs ad-hoc journal entries when costs or sales occur, as well as monthly journal entries and internal sales adjustment journal entries performed at the end of each month. First, ad-hoc journal entries will be explained using Figures 16 to 19. Figure 16 is a diagram showing an example of the journal entry data creation screen according to the embodiment. Figure 17 is a diagram showing another example of the journal entry data creation screen according to the embodiment. Figure 18 is a diagram showing another example of the journal entry detail data 106bd according to the embodiment. Figure 19 is a diagram showing another example of the cost data 106bc according to the embodiment.

[0061] The journal entry processing unit 102d receives instructions for journal entry processing by displaying, for example, a journal entry data creation screen S21, as shown in Figure 16, on the terminal device 204 of the management department. As shown in Figure 16, if "Cost Accounting" is selected on the journal entry data creation screen S21, the journal entry processing unit 102d generates journal entry detail data 106bd, as shown in Figure 9, by applying the following rules to the cost data 106bc, as shown in Figure 8. 1. For the debit account, retrieve the work-in-progress account from PJ cost account classification master 106aa. 2. For credit accounts, retrieve the liability account classification from cost data 106bc. 3. For each debit and credit department, retrieve the department from cost data 106bc.

[0062] In this process, for example, based on the project cost account classification "Materials Cost" in data bc11 for the voucher number "GK001" of cost data 106bc, "Materials Cost (Unfinished)" is registered as the debit account, as shown in journal entry bd11 in Figure 9. In addition, the liability account classification "Construction Accounts Payable" from data bc11 is registered as the credit account, and the department "B002: Engineering Department A" from data bc11 is registered as the debit and credit departments. The same process is performed on data bc12 to bc15 shown in Figure 8, thereby forming journal entries bd12 to bd15 shown in Figure 9. These journal entries are recorded on August 31, 2024, as shown in Figure 16.

[0063] Furthermore, the journal entry processing unit 102d generates accounting data 106be as shown in Figure 11, based on the journal entries bd11 to bd15 shown in Figure 9.

[0064] Furthermore, as shown in Figure 17, for example, if "Sales" is selected on the journal entry data creation screen S22, the journal entry processing unit 102d applies the following rules to the sales data 106bf shown in Figure 12, thereby generating the journal entry detail data 106bd shown in Figure 18. 1. For the debit account, retrieve the account classification from the account master 106ab for each product, based on the product in contract information data 106bb. 2. For credit accounts, retrieve the account from the product-specific account master 106ab based on the product in contract information data 106bb. 3. For the debit department, retrieve the requesting department of contract information data 106bb based on the requesting order number of contract information data 106bb. 4. For the credit side, retrieve the department for sales data 106bf.

[0065] In this process, for example, based on the product "Internal Sales" in data bb12 of contract information data 106bb shown in Figure 7, which corresponds to the order number "JU0003" in data bf11 of sales data 106bf shown in Figure 12 (where the invoice number "UR001" is shown), "Internal Purchases" is registered as the debit account and "Internal Sales" as the credit account. In addition, the department "B002: Technical Department A" corresponding to the requesting order number "JU0002" in data bb12 is registered as the debit department, and the department "B003: Technical Support Department" of data bf11 of sales data 106bf is registered as the credit department. The journal entry for this sales is also recorded on August 31, 2024, as shown in Figure 17.

[0066] In this embodiment, internal purchases and internal sales are reflected in the data for each department in the accounting data 106be, but not in the company-wide data be10. In this case, as shown in Figure 18, the journal entry processing unit 102d generates journal entries bd21 that record internal purchases and internal sales for each department, as well as journal entries bd22 that offset internal sales and internal purchases for the entire company.

[0067] Furthermore, in this process, the journal entry processing unit 102d updates the cost data 106bc, which corresponds to the data registered in the sales data 106bf. In the updated cost data 106bc, as shown in Figure 19, for example, the completion transfer date for the cost data bc24 for voucher number "GK004" and line number "1", and the cost data bc25 for voucher number "GK005" and line number "1" are updated to "August 31, 2024", and the "completion transfer flag" is updated to "1".

[0068] Next, monthly journal entries and internal sales adjustment journal entries by the journal entry processing unit 102d will be explained using Figures 20 to 22. Figures 20 and 21 show examples of the journal entry data creation screen and journal entry detail data according to the embodiment. Figure 22 shows an example of accounting data according to the embodiment.

[0069] The journal entry processing unit 102d receives instructions for journal entry processing by displaying a journal entry data creation screen S23, for example, as shown in Figure 20, on the terminal device 204 of the management department. As shown in Figure 20, if "Send Monthly Journal Entry" is selected on the journal entry data creation screen S23, the journal entry processing unit 102d performs processing for monthly journal entries. In this embodiment, the journal entry processing unit 102d performs monthly journal entries on the data registered in the sales data 106bf shown in Figure 12.

[0070] In this embodiment, the debit account in monthly journal entries is fixed as "Internal Profit" and the credit account as "End-of-Month Work in Progress" in the journal entry definition. The departments for the debit and credit entries are obtained from the "Department" in the sales data 106bf shown in Figure 12. The amounts for the debit and credit entries are the amounts obtained by subtracting the "Amount" in the cost data 106bc shown in Figure 8 from the "Internal Sales Amount" in the sales data 106bf.

[0071] For example, the journal entry processing unit 102d calculates "400,000 yen" by subtracting the sum of the amounts in cost data bc14 and bc15 (shown in Figure 8) from the internal sales amount of "3 million yen" in data bf11 of voucher number "UR001" registered in sales data 106bf (shown in Figure 12). Then, the journal entry processing unit 102d generates journal entry bd25 (shown in Figure 20) by registering the department "B003: Technical Support Department" for both the debit and credit sides. Note that as of August 31, 2024, sales data 106bf does not contain sales data for Sales Department 1 and Technical Department A, so only journal entries related to the Technical Support Department are generated.

[0072] Furthermore, the journal entry processing unit 102d receives instructions for journal entry processing by displaying a journal entry data creation screen S24, for example, as shown in Figure 21, on the terminal device 204 of the management department. As shown in Figure 21, if the transmission of internal sales adjustment journal entries is selected on the journal entry data creation screen S24, the journal entry processing unit 102d performs processing for monthly journal entries. Internal sales adjustment journal entries transfer costs that are currently treated as uncompleted to completed for construction work related to data bc24 and bc25, where the completion transfer flag in the cost data 106bc shown in Figure 19 is "1", i.e., completed construction work. Also, as of August 31, 2024, when the internal sales adjustment journal entries are made, the sales of the main contract have not been recorded in the sales data 106bf, i.e., the main contract has not been completed. Therefore, the journal entry processing unit 102d does not generate journal entries for financial accounting data, but only for management accounting data.

[0073] In the internal sales adjustment journal entry, as shown in journal entry bd34 in Figure 21, the debit account is set to "Outsourcing Expenses (Completed)" and the credit account is set to "Outsourcing Expenses (Incomplete)". Similarly, in journal entry bd35, the debit account is set to "Labor Expenses (Completed)" and the credit account is set to "Labor Expenses (Incomplete)". The journal entry processing unit 102d then sets the department "B003: Technical Support Department" for both the debit and credit sides. Note that as of August 31, 2024, sales data 106bf does not contain sales for Sales Department 1 and Technical Department A, so only journal entries related to the Technical Support Department are generated. In other words, the journal entry processing unit 102d generates journal entries bd34 and bd35 at a time when sales for the project have not yet been recorded. Journal entries bd34 and bd35 are examples of journal entries that transfer incomplete items to completed items.

[0074] Then, the journal entry processing unit 102d updates the accounting data 106be as shown in Figure 22 by reflecting the journal entries generated in the monthly journal entry processing into the accounting data 106be shown in Figure 11.

[0075] As shown in Figure 22, in the updated accounting data 106be, the data be23 for the Technical Support Section includes "Internal Profit," "End-of-Month Uncompleted Construction Work," and "Internal Sales," based on the journal entries shown in Figure 20. Furthermore, in the management accounting data of data be23, the cost-related items have been updated from "Outsourcing Costs (Uncompleted)" and "Labor Costs (Uncompleted)" to "Outsourcing Costs (Completed)" and "Labor Costs (Completed)," based on the journal entries bd34 and bd35 shown in Figure 21. On the other hand, the cost-related items in the financial accounting data of the Technical Support Section's data be23 and in the data be22 for Section A of the Technical Department are not updated. Also, in Figure 21 and later, the display of "Construction Accounts Payable" in accounting data 106be may be omitted.

[0076] Furthermore, in monthly journal entries, the company-wide data be20 is generated by aggregating the data be22 from Engineering Department A and the data be23 from the Technical Support Department. However, in monthly journal entries, the journal entry bd22 shown in Figure 18 is generated for the aggregated data. As a result, in the company-wide data be20, internal sales and internal purchases are offset against each other.

[0077] Furthermore, after the internal sales adjustment journal entry, for example, at the beginning of the following month (September 1, 2024), a reverse journal entry may be made for journal entries bd34 and bd35 shown in Figure 21 to offset the journal entries incurred in management accounting.

[0078] The processing after monthly journal entries and internal sales adjustment journal entries on August 31, 2024 will be explained using Figures 23 and later. Figure 23 is a diagram showing another example of sales data according to the embodiment. For example, when the completion processing unit 102c receives input of sales information from the terminal device 202 of Section A of the Technical Department, it adds data bf21 to the second line of sales data 106bf.

[0079] Furthermore, the journal entry processing unit 102d generates journal entries bd41 and bd42, shown in Figure 24, based on the data bf21 entered into the sales data 106bf. Figure 24 is a diagram showing another example of journal entry data according to the embodiment.

[0080] Furthermore, the journal entry processing unit 102d updates the cost data 106bc, which corresponds to the data bf21 registered in the sales data 106bf, as shown in Figure 25. Figure 25 is a diagram showing another example of cost data according to the embodiment. For example, the journal entry processing unit 102d updates the completion transfer date of data bc31, bc32, and bc33 of the cost data 106bc shown in Figure 19 to "September 30, 2024" and updates the "completion transfer flag" to "1".

[0081] Next, monthly journal entries and internal sales adjustment journal entries by the journal entry processing unit 102d will be explained using Figures 26 to 28. Figures 26 and 27 show another example of journal entry data according to the embodiment. Figure 28 shows another example of accounting data according to the embodiment.

[0082] When the journal entry processing unit 102d receives a journal entry instruction, for example, it performs a monthly journal entry on data bf21 from the sales data 106bf shown in Figure 23, which has been recorded since the previous monthly journal entry. This generates the journal entry data bd45 shown in Figure 26. The amount "300,000 yen" in the journal entry data bd45 is the amount obtained by subtracting the total amount of data bc11 to bc13 in the cost data 106bc shown in Figure 8, which is "5,200,000 yen", and the amount of internal purchases shown in journal entry bd21 in Figure 18, which is "3,000,000 yen", from the internal sales amount "8,500,000 yen" for voucher number "UR002" registered in the sales data 106bf shown in Figure 23.

[0083] Furthermore, the journal entry processing unit 102d performs internal sales adjustment journal entries for the costs of construction projects where the completion transfer flag is set to "1" in the cost data 106bc. In this case, the journal entry processing unit 102d in the cost data 106bc performs internal sales adjustment journal entries for data bc31 to bc33 registered in the cost data 106bc as shown in Figure 25. In this embodiment, the journal entry processing unit 102d also performs internal sales adjustment journal entries again for data bc24 and bc25, which were offset in the reverse journal entries at the beginning of the month. This generates journal entries bd31 to bd35 as shown in Figure 27.

[0084] The journal entry processing unit 102d then updates the accounting data 106be as shown in Figure 28. Figure 28 is a diagram showing another example of accounting data according to the embodiment. As shown in Figure 28, in the updated accounting data 106be, in the data be32 of Engineering Department A, "internal profit," "end-of-month work in progress," and "internal sales" are registered based on the journal entries shown in Figure 26. In addition, in the management accounting data be32 of Engineering Department A and the data be33 of the Technical Support Department, the cost-related items are updated from "outsourcing expenses (in progress)" and "labor expenses (in progress)" to "outsourcing expenses (completed)" and "labor expenses (completed)" based on the journal entries bd31 to bd35 shown in Figure 27. On the other hand, in the financial accounting data of data be32 and be33, the cost-related items are not updated.

[0085] Furthermore, "internal purchases" are reflected in the data be31 of Sales Department 1, and the company-wide data be30 is updated to the sum of data be31, be32, and be33. As a result, as shown in Figure 28, all accounts corresponding to costs in the company-wide data be20 are updated to completed items. However, as shown in the journal entry bd42 in Figure 24, "internal purchases" and "internal sales" are offset in the company-wide data be30. In this embodiment, internal purchases and sales between the Technical Support Department and Technical Department A are also offset by the journal entry bd22 shown in Figure 18.

[0086] Furthermore, the case in which completion is recorded by Sales Department 1, that is, the case in which sales of the main contract are recorded, will be explained using Figures 29 and later. Figure 29 is a diagram showing another example of sales data according to the embodiment. As shown in Figure 29, when the terminal device 201 of Sales Department 1 receives input of information regarding completion, the completion processing unit 102c registers the data bf23 of slip number "UR003" in the sales data 106bf.

[0087] The journal entry processing unit 102d generates the journal entry bd61 shown in Figure 30 based on the data bf23. Figure 29 shows another example of journal entry data according to the embodiment. Journal entry bd61 includes the accounts receivable account category "Accounts Receivable for Completed Construction" and the account "Construction Costs" from the PJ cost account category master 106aa, which corresponds to the order number "JU0001" in the data bf23 of the sales data 106bf and the product "Construction Package" in the contract information data 106bb shown in Figure 7. Journal entry bd61 also includes "Consumption Tax" from the data bf23.

[0088] Furthermore, the journal entry processing unit 102d generates journal entries bd31 to bd35 shown in Figure 31 in the internal sales adjustment journal entries. Figure 31 is a diagram showing another example of journal entry data according to the embodiment. Note that when sales from the main contract are recorded, journal entries bd31 to bd35 are generated for the financial accounting data be1, not the management accounting data be2, as shown in Figure 31.

[0089] Furthermore, the journal entry processing unit 102d updates the accounting data shown in Figure 32 based on journal entries bd61 and bd31-bd35 shown in Figures 30 and 31. Figure 32 is a diagram showing another example of accounting data according to the embodiment. As shown in Figure 32, after the revenue of the main contract is recorded, the contents of the management accounting data be2 match the contents of the financial accounting data be1.

[0090] According to the embodiment described above, sales related to interdepartmental transactions can be recorded at the monthly journal entry stage, making it easy to grasp the revenue of the construction department.

[0091] Furthermore, in this embodiment, the management accounting data be2 is generated by transferring the contents of the financial accounting data be1 and then generating additional journal entries. This eliminates the need to generate management accounting data through a separate process from financial accounting data, making it easier to grasp the revenue of the construction department.

[0092] Furthermore, after monthly journal entries and internal sales adjustment journal entries, the financial accounting data be1 and management accounting data be2 record identical content except for the transfer of incomplete items to completed items. Therefore, instead of performing a reverse journal entry for internal sales adjustment journal entries at the beginning of the following month, it is also acceptable to configure the system to transfer financial accounting data be1 to management accounting data be2.

[0093] Furthermore, the profit amount in accounting data 106be shown in Figure 32 is calculated using operating profit (1.5 million yen), which is calculated by subtracting internal purchases from completed construction work, and internal profit (700,000 yen). However, the method of calculating profit is not limited to this. For example, total profit may be calculated by subtracting costs (materials cost 1 million yen, subcontracting costs 3.5 million yen, labor costs 3.3 million yen) from completed construction work (10 million yen).

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

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

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

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

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

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

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

[0101] For example, the processing functions of the order management device 100, particularly those performed in the control unit, may be implemented entirely or partially 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 management 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.

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

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

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

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

[0106] Furthermore, the order management 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 management device 100 may be implemented by installing software (including programs or data, etc.) that realizes the processing described in this embodiment on the device.

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

[0108] This invention is useful in industries such as the construction industry, where there is a time lag between the completion of a construction project and inter-departmental transactions. [Explanation of Symbols]

[0109] 1. Order Management System 100 Order Management System 102 Control Unit 102a Order Processing Unit 102b Cost Processing Section 102c Completed Processing Unit 102d Journal Entry Processing Unit 104 Communication Interface Section 106 Storage section 106a Master Storage Unit 106aa PJ Cost Account Classification Master 106ab Master Accounts by Product 106b Data storage unit 106ba Project Data 106bb Contract Information Data 106bc Cost Data 106bd Journal entry details data 106be Accounting Data 106bf Sales Data 108 Input / Output Interface Section Terminal devices 200, 201, 202, 203, 204 300 Networks

Claims

1. An order processing unit creates order information, including order source identification information, for each department at the order unit stage, A cost processing unit that receives input of information regarding the cost of interdepartmental transactions associated with the aforementioned case information, A journal entry processing unit registers the information regarding the aforementioned interdepartmental transactions as an incomplete item in the first accounting data for each department, A completion processing unit that receives input of information related to the completion of the aforementioned interdepartmental transaction, Equipped with, The journal entry processing unit generates a journal entry in the second accounting data on which the contents of the first accounting data have been posted, in accordance with the information regarding the completion of the interdepartmental transaction, to transfer the incomplete item to a completed item at the time when the sales for the project have not yet been recorded. Order management system.

2. The aforementioned journal entry processing unit, At the end of the period, transfer processing is performed based on the journal entry to transfer to the completed item. At the beginning of the period following the transfer transaction, a reverse journal entry is generated to cancel the transfer transaction. The order management device according to claim 1.

3. The order management device according to claim 1, wherein the journal entry processing unit transfers the contents of the first accounting data to the second accounting data.

4. The aforementioned journal entry processing unit generates journal entries to record the costs and sales associated with the interdepartmental transaction when the interdepartmental transaction is completed, and reflects them in the first accounting data. The order management device according to claim 3.

5. The order management device according to claim 4, which generates a reverse journal entry to offset interdepartmental transactions in company-wide data obtained by aggregating the first accounting data for each department.

6. The order management device according to claim 1, wherein the order source identification information is associated with both the project information and the information relating to interdepartmental transactions.

7. An order management method performed by an order management device equipped with a control unit, The control unit, The steps include creating project information, including client identification information, for each department for each project order, and A step of receiving input information regarding the cost of interdepartmental transactions associated with the aforementioned case information, The steps include registering the information regarding the aforementioned interdepartmental transactions as an incomplete item in the first accounting data for each department, A step of receiving input of information accompanying the completion of the aforementioned interdepartmental transaction, In the second accounting data on which the contents of the first accounting data have been transferred, a step is to generate a journal entry to transfer the incomplete item to a completed item at the time when the sales for the project have not yet been recorded, in accordance with the information accompanying the completion of the interdepartmental transaction. An order management method characterized by performing the following actions.

8. An order management program to be executed on an order management device equipped with a control unit, The control unit, The steps include creating project information, including client identification information, for each department for each project order, and A step of receiving input information regarding the cost of interdepartmental transactions associated with the aforementioned case information, The steps include registering the information regarding the aforementioned interdepartmental transactions as an incomplete item in the first accounting data for each department, A step of receiving input of information accompanying the completion of the aforementioned interdepartmental transaction, In the second accounting data on which the contents of the first accounting data have been transferred, a step is to generate a journal entry to transfer the incomplete item to a completed item at the time when the sales for the project have not yet been recorded, in accordance with the information accompanying the completion of the interdepartmental transaction. An order management program characterized by its ability to execute certain actions.

Images